Interesting - I'll test it too when I install the patch. I wonder if maybe the timezone files are read dynamically for function calls such as those in your test, but only loaded at startup time for the processing that is done for inserting and selecting timestamp values in tables. Thanks -----Original Message----- From: Joe Armstrong-Champ [mailto:joseph.armstrong-champ@xxxxxxxxx] Sent: Thursday, January 25, 2007 2:32 PM To: Allen, Brandon 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. > Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. -- //www.freelists.org/webpage/oracle-l