Re: Oracle and DST changes

I just applied the patch in a dev/test environment and the databases picked
up the new timezone rules without bouncing them.  I'm still going to bounce
the databases for good measure, but it doesn't appear necessary.
10.1.0.5on Solaris 9.

Mark Strickland


On 1/26/07, Sam Bootsma <sbootsma@xxxxxxxxxxxxxx> wrote:


According to Oracle FAQ#223 in Metalink Note 402742.1, the timezone
files are picked up whenever database or client software is started up.
So the act of stopping and restarting sqlplus would cause the files to
be re-read.  Here is the FAQ:

223. Is any relinking needed after the patches are applied?
No.
The time zone file patch only gives you 2 new time zone files. These are
picked up automatically by the database or client software the next time
they start up.
The JVM patch requires the JVM in the database to be updated after the
patch has been installed, but this is a action "inside" the database.
For details refer to the readme files of the JVM patches.


Sam Bootsma
Oracle Database Administrator
Information Technology Services
George Brown College
Phone: 416-415-5000 x4933
Fax: 416-415-4836
E-mail: sbootsma@xxxxxxxxxxxxxx

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Mercadante, Thomas F
(LABOR)
Sent: January 26, 2007 7:49 AM
To: Chandra.Pabba@xxxxxxx; nancy.malpass@xxxxxxxxxxxx;
joseph.armstrong-champ@xxxxxxxxx; Brandon.Allen@xxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: Oracle and DST changes

This is crazy.  It looks like a new session gets the new information.

I connect to the database with the old files in place in the zoneinfo
directory.  I ran the script and the results were wrong.
I loaded the new files without disconnecting from sqlplus and ran the
script again.  The results were wrong.

I restarted sqlplus and ran the script and the results were correct.

It looks like a new database session reads the zoneinfo files?

Another great testing job from Oracle support.  At least they are
consistent.


--------------------------------------------------------
This transmission may contain confidential, proprietary, or privileged
information which is intended solely for use by the individual or entity
to whom it is addressed.  If you are not the intended recipient, you are
hereby notified that any disclosure, dissemination, copying or
distribution of this transmission or its attachments is strictly
prohibited.  In addition, unauthorized access to this transmission may
violate federal or State law, including the Electronic Communications
Privacy Act of 1985.  If you have received this transmission in error,
please notify the sender immediately by return e-mail and delete the
transmission and its attachments.


-----Original Message-----

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Pabba, Chandra
Sent: Thursday, January 25, 2007 4:49 PM
To: nancy.malpass@xxxxxxxxxxxx; joseph.armstrong-champ@xxxxxxxxx;
Brandon.Allen@xxxxxxxxxxx
Cc: Mercadante, Thomas F (LABOR); oracle-l@xxxxxxxxxxxxx
Subject: RE: Oracle and DST changes

Yes,  I did notice the same thing.  Without restarting the instance, I
was able to see the updated results.


Thanks
Chandra


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Malpass, Nancy
Sent: Thursday, January 25, 2007 3:45 PM
To: joseph.armstrong-champ@xxxxxxxxx; Brandon.Allen@xxxxxxxxxxx
Cc: Mercadante, Thomas F (LABOR); oracle-l@xxxxxxxxxxxxx
Subject: RE: Oracle and DST changes

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.
>
--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l




--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l

Other related posts: