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
