Re: Time zones calculation - browser apps
From: Jeremy <jeremy0505_at_gmail.com>
Date: Thu, 28 May 2009 14:11:30 +0100
Message-ID: <MPG.24889dd854de9b8b98972a_at_News.Individual.NET>
In article <e386ff07-b194-46db-a04d-
a294a4415d2d_at_i28g2000prd.googlegroups.com>, wizofoz2k_at_gmail.com says...>
> On May 28, 2:23 am, joel garry <joel-ga..._at_home.com> wrote:
>
> > choose. I would be concerned about not being on a recent patchset.
>
> Same here. When we upgraded one of our dbs from 10.2.0.1 to
> 10.2.0.3, one of the things that broke straight away was the
> dbms scheduler. Timezone handling and its datatypes changed
> with 10.2.0.3 and a script was needed - provided by Metalick - to fix
> things up at dictionary level. Dunno about user data, but I suspect
> the same problem would apply.
> I'd move away from 10.2.0.1 pronto, if using timezone data.
Date: Thu, 28 May 2009 14:11:30 +0100
Message-ID: <MPG.24889dd854de9b8b98972a_at_News.Individual.NET>
In article <e386ff07-b194-46db-a04d-
a294a4415d2d_at_i28g2000prd.googlegroups.com>, wizofoz2k_at_gmail.com says...>
> On May 28, 2:23 am, joel garry <joel-ga..._at_home.com> wrote:
>
> > choose. I would be concerned about not being on a recent patchset.
>
> Same here. When we upgraded one of our dbs from 10.2.0.1 to
> 10.2.0.3, one of the things that broke straight away was the
> dbms scheduler. Timezone handling and its datatypes changed
> with 10.2.0.3 and a script was needed - provided by Metalick - to fix
> things up at dictionary level. Dunno about user data, but I suspect
> the same problem would apply.
> I'd move away from 10.2.0.1 pronto, if using timezone data.
Thanks for that, will follow that advice.
-- jeremyReceived on Thu May 28 2009 - 08:11:30 CDT