RE: Oracle and DST changes
- From: "Malpass, Nancy" <nancy.malpass@xxxxxxxxxxxx>
- To: <joseph.armstrong-champ@xxxxxxxxx>, <Brandon.Allen@xxxxxxxxxxx>
- Date: Thu, 25 Jan 2007 15:45:19 -0600
That would be great to no have to restart each database.
Anyone else do this and found that a restart is not necessary?
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Armstrong-Champ
Sent: Thursday, January 25, 2007 3:32 PM
To: Brandon.Allen@xxxxxxxxxxx
Cc: Mercadante, Thomas F (LABOR); oracle-l@xxxxxxxxxxxxx
Subject: Re: Oracle and DST changes
This actually turns out not to be true. I just applied the patch to a
test db without shutting down and when I ran the confirmation sql I got
the updated results:
SQL> select to_timestamp_tz('20070311 00:00:00 US/EASTERN','YYYYMMDD
HH24:MI:SS TZR') + to_dsinterval('0 08:00:00') TEST from dual;
TEST
------------------------------------------------------------------------
---
11-MAR-07 09.00.00.000000000 AM US/EASTERN
(solaris 64-bit/oracle 10.1.0.4)
Joe
Allen, Brandon wrote:
It also confirms that the timezone files are in
> fact only read at startup, so a restart is necessary for the new rules
> to take effect.
>
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
