RE: 10.2.0.1 DST patchset

Update:

I did both versions of opatch again :) geez, but either I believe only affects the ORACLE_HOME that is set.  

When done this query will return 08:00 from the client if the client has NOT been upgraded itself, and will return 09:00 if logging in from the ORACLE_HOME on the server:  

select to_timestamp_tz('20070311 00:00:00 US/EASTERN','YYYYMMDD HH24:MI:SS TZR') + to_dsinterval('0 08:00:00') TEST from dual;  

The timezone file (v$timezone_file) and the patch will still show version 2 and that the patch has not been applied UNTIL the database is restarted.    

Joel Patterson
Database Administrator
joel.patterson_at_crowley.com
x72546
904 727-2546

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Joel.Patterson_at_crowley.com
Sent: Wednesday, February 07, 2007 9:07 AM To: oracle-l_at_freelists.org
Subject: 10.2.0.1 DST patchset  

I will attempt to summarize what I have gleaned and applied.  

There is no official patchset for utltzuv2.sql, patchset 5601428 before upgrading.   

There is however a 10.2.0.1 4689959 patchset for the timezone files.

After you check and save your data with the utltzuv2.sql 5601428 script (that you applied manually, note 399832.1), you apply the 4689959 patchset for 10.2.0.1 using opatch. Doing this will update the 10.2.0.1 opatch inventory showing that 4689959 has been applied. It will Not show 5601428 was applied. Then restore the data and cleanup as described in note 399832.1  

Note: I cannot remember if I used 10.2.0.1 opatch or 10.2.0.2 opatch to apply the 10.2.0.1 4689959 patch. (someone remind me).  

However when finished, you do have to use the 10.2.0.1 opatch executable to see this the 4689959 inventory listed.  

IF, before you start this, you had applied 10.2.0.2 already on the server for a 10.2.0.2 database, the 10.2.0.1 opatch will not show either patchset, but the 10.2.0.2 opatch will indicate that both patches have been applied.    

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