Applying the DSTv21 update for the Oracle Database
(Doc ID 1583376.1)
Last updated on MARCH 16, 2021
Applies to:Oracle Database - Standard Edition - Version 10.1.0.5 to 126.96.36.199 [Release 10.1 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
* 188.8.131.52, 184.108.40.206, 220.127.116.11 , 18.104.22.168 and 22.214.171.124 for the following platforms: Linux X86, Linux X86-64 , Microsoft Windows X86 (32-BIT) , Microsoft Windows X86-64 (64-BIT) , Oracle Solaris on Sparc (64-BIT) , Oracle Solaris on Intel X86-64 (64-BIT) IBM AIX on Power Systems (64-BIT) , HP-UX Itanium (64-BIT), HP-UX PA-RISC (64-BIT) .
* 126.96.36.199 for HP OpenVMs on Itanium and Alpha.
Please log a SR if you need a backport to a platform or current version not mentioned.
Note that backports to 188.8.131.52 are available for download only for customers with a valid Extended Support . See <Note 412160.1> , section "G) For what versions are DST patches provided / there is no DST version X for my Oracle RDBMS version?"
Please consult your Sales representative to enroll in an Extended Support contract if required.
Proactive backports of the OJVM DSTv21 <patch 17443054> are done for 184.108.40.206 , 220.127.116.11 , 18.104.22.168. Other supported versions can be requested .
The OJVM DST patch is platform generic.
The RDBMS DSTv21 update includes the timezone information from the IANA ( http://www.iana.org/time-zones ) data tzdata2013e.tar and contains all previous Oracle RDBMS DST updates.
The OJVM DSTv21 update includes the timezone information from the IANA (http://www.iana.org/time-zones ) data tzdata2013e.tar and contains all previous Oracle OJVM DST updates.
This is archived content. The note covers the "DSTv21" update, newer DST updates are available.
Please see <Note 412160.1> Updated Time Zones in Oracle Time Zone File patches for information on the newer DST patches.
All DST patches are always cumulative, which means they contain also ALL the previous DST changes / corrections.
This means that:
- if there is a requirement to apply DST version 21 it's a good idea to apply the latest available for your Oracle RDBMS version seen the newer DST patch this will have the same fixes and more. *
- a newer DST patch for a certain RDBMS version can be used if the older DST patch is not available for this version (for example using DSTv22 instead of using DSTv21 for 22.214.171.124). *
- any application that works correctly with DST version x will work fine with a database using a DST version higher than DST version x **
- the database and client DST version does not need to be the same. If a client uses DSTv4 for example (and all used timezones by the application are correct in DSTv4) then there is no problem using this client against a database using a higher DST version.
- in 126.96.36.199 and lower Optach will report a conflict when applying a new DST patch when an older is already installed, this can be ignored. There is no need to ask for a "merge" seen the newer dst patch has already all the fixes of the old one.
- There are no "PSU DST patches" , for example an Oracle DST patch for 188.8.131.52 can be applied (manually or using Opatch) on *any* 184.108.40.206 psu (same goes for any other Oracle RDBMS version)
* When doing an Oracle RDBMS version upgrade there might be a requirement to apply an exact DST patch/version on the new Oracle RDBMS version home , check the notes in point C.1.a) and C.1.b) of <Note 412160.1> Updated DST transitions and new Time Zones in Oracle Time Zone File patches.
** This statement is true for DSTv4 and higher. The only exception are very old DST versions like 1, 2 or 3 and timezones are actually used (!) in the application.
In 11gR2 and higher the time to update to a new RDBMS DST version is depending 99% on the dataset size, not the target DST version.
For example if the current RDBMS DST version 14 then going from DSTv14 to DSTv21 will take the roughly the same amount of time as going from DSTv14 to DSTv21 .
Compared to DSTv20 this is the list of updated timezones in DSTv21 for non historical dates ( meaning update to the timezone after 1970):
This note will give an overview on what checks to perform before applying the DSTv21 update.
So even an "unpatched database" will return a correct SYSDATE if the server (OS) time is correct.
For "sysdate" you do not need any DST patch <Note 227334.1> Dates & Calendars - Frequently Asked Questions
For more information about Timestamp with (local) Time Zone please check <Note 340512.1> Timestamps & time zones - Frequently Asked Questions
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1) What is my current installed DST version?|
|2) 10g and 11.1 only: What to check before applying the RDBMS DSTv21 patch 17432124 .|
|3) 10g and 11.1 only: You have affected TSTZ data stored (sys_tzuv2_temptab returns rows).|
|4) 10g and 11.1 only: Applying the RDBMS DSTv21 patch 17432124 .|
|4a) 10g and 11.1 only: Supported versions and platforms.|
|4b) 10g and 11.1 only: RDBMS DSTv21 patch 17432124 needs Patch 7695070 installed using Opatch.|
|4c) 10g and 11.1 only: Applying the RDBMS DSTv21 patch 17432124 on the server side.|
|4d) 10g and 11.1 only: After the server apply of RDBMS DSTv21 patch 17432124 and restart of the database:|
|4e) 10g and 11.1 only: Applying the RDBMS DSTv21 patch 17432124 on clients|
|5) Oracle RDBMS 11gR2 : Applying the RDBMS DSTv21 patch 18759211 on Oracle RDBMS 11gR2 ( 220.127.116.11 , 18.104.22.168 , 22.214.171.124 or 126.96.36.199)|
|5.a) Applying the RDBMS DSTv21 patch 17432124 on the server side on Oracle RDBMS 11gR2.|
|5.b) Applying the RDBMS DSTv21 patch 17432124 on the client side on Oracle RDBMS 11gR2.|
|6) Oracle RDBMS 12cR1 : Applying the RDBMS DSTv21 patch 17432124 on Oracle RDBMS 12cR1 ( 188.8.131.52 and 184.108.40.206).|
|6.a) Applying the RDBMS DSTv21 patch 17432124 on the server side on Oracle RDBMS 12cR1 .|
|6.b) Applying the RDBMS DSTv21 patch 17432124 on the client side on Oracle RDBMS 12cR1.|
|7) The OJVM DSTv21 patch 17443054.|