Actions For DST Updates When Upgrading To Or Applying The 188.8.131.52 Patchset
(Doc ID 1579838.1)
Last updated on AUGUST 04, 2018
Oracle Database - Standard Edition - Version 184.108.40.206 to 220.127.116.11 [Release 8.1.7 to 11.2] Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 8.1.7 to 11.2] Information in this document applies to any platform.
To provide a step by step flow to determine if there are DST version implications when upgrading to 126.96.36.199 or applying the 188.8.131.52 patchset on a 184.108.40.206 , 220.127.116.11 or 18.104.22.168 database home.
Oracle has 2 datatypes that may have stored data which would be affected by an update of the RDBMS DST definitions. These datatypes are TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ). Note that there is other functionality which uses these DST definitions, but this does not affect the stored information directly. Note that "sysdate" and the "date" datatype do not use the DST definitions provided by Oracle, they rely pure on the Operating System.
The Oracle Java Virtual Machine (OJVM) also has DST information, but has no internal datatypes which store that information, hence this can be updated by simply applying the latest/newest OJVM DST patch.available.
These steps should be followed before * applying 22.214.171.124 on an 126.96.36.199 , 188.8.131.52 or 184.108.40.206 database home. * upgrading from 11.1.0.x , 10.2.0.x, 10.1.0.x , 9.2.0.x or 9.0.1.x version directly to 220.127.116.11 release.
The goal is to see what actions are needed on DST information before or after upgrading to 18.104.22.168 Used abbreviations:
TZ: TimeZone TSTZ: TimeStamp with Time Zone TSLTZ: TimeStamp with Local Time Zone OJVM: Oracle Java Virtual Machine
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!