My Oracle Support Banner

Applying the DSTv26 update for the Oracle Database (Doc ID 2143254.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Standard Edition - Version to [Release 10.1 to 12.1]
Oracle Database - Enterprise Edition - Version to [Release 10.1 to 12.1]
Information in this document applies to any platform.


There are no "PSU DST patches" , for example an Oracle DST patch for can be applied using Opatch on *any* PSU (same goes for any other Oracle RDBMS version)

Note that backports to versions who are NOT in Premier Support are possible / available for download only for customers with a valid Extended Support .
Exceptions for other version/platform combination are only possible for customers with an existing Extended Support contract for the specific version/platform combination or platforms with Extended Support Fee Waiver Period.
Please log a SR if you need a backport to such a platform / version (if you need several log 1 SR clearly stating which version/platforms you have Extended Support contract for and need ).
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.
If you log a SR requesting a backport or the password for versions in Extended Support and there is no Extended Support contract in place the patch cannot be provided.

The RDBMS DSTv26 update includes the timezone information from the IANA ( ) data tzdata2016d.tar and contains all previous Oracle RDBMS DST updates.

A complete overview of timezone updates is found in <Note 412160.1> Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches.


The changes included in DSTv26 patch (and not included in DSTv25) are:

America/Cayman will not observe daylight saving in 2016.
Asia/Chita switches from +0800 to +0900 on 2016-03-27 at 02:00
Asia/Tehran has DST predictions for the year 2038 and later
Haiti will not observe DST in 2016.
Palestine's spring-forward transition on 2016-03-26 is at 01:00, not 00:00
Azerbaijan no longer observes DST
Chile reverts from permanent to seasonal DST (2016)
America/Caracas switches from -0430 to -04 on 2016-05-01 at 02:30.
Asia/Magadan switches from +10 to +11 on 2016-04-24 at 02:00.


Compared to DSTv25 this is the list of updated timezones in DSTv26 for non historical dates ( meaning update to the timezone after 1970):

Asia/Tehran, Asia/Chita, Asia/Magadan, Asia/Baku, Asia/Gaza, Asia/Hebron, America/Caracas, America/Santiago, Pacific/Easter.


This note will give an overview on what checks to perform before applying the DSTv26 update.
Note that all DST patches are always cumulative, which means they contain also ALL the previous DST changes / corrections.

Please note that SYSDATE is NOT affected by "Oracle DST patches" seen SYSDATE is purely depending on the OS to get the time.
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 1627439.1> How to diagnose wrong time ( SYSDATE and SYSTIMESTAMP) after DST change , server reboot , database restart or installation when connecting to a database on an Unix server
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 RDBMS DST version?
 1.a) for Oracle RDBMS 12gR1 and 11gR2
 1.b) For Oracle RDBMS 10g and 11gR1:
 2) Oracle RDBMS 12cR1 : Applying the RDBMS DSTv26 patch 22873635 on Oracle RDBMS 12cR1 ( and .
 2.a) Applying the RDBMS DSTv26 patch 22873635 on the server side in Oracle RDBMS 12cR1.
 2.b) Applying the RDBMS DSTv26 patch 22873635 on the client side in Oracle RDBMS 12cR1.
 3) Oracle RDBMS 11gR2 : Applying the RDBMS DSTv26 patch 22873635 on Oracle RDBMS 11gR2 ( , , or
 3.a) Applying the RDBMS DSTv26 patch 22873635 on the server side in Oracle RDBMS 11gR2
 3.b) Applying the RDBMS DSTv26 patch 22873635 on the client side in Oracle RDBMS 11gR2.
 4) 10g and 11.1 only:  What to check before applying the RDBMS DSTv26 patch 22873635.
 4a) Check if you have stored TSLTZ (TIMESTAMP WITH LOCAL TIME ZONE) data.
 4b) Check if you have stored affected TSTZ (TIMESTAMP WITH TIME ZONE) data.
 5) 10g and 11.1 only: You have affected TSTZ data stored (sys_tzuv2_temptab returns rows).
 6) 10g and 11.1 only: Applying the RDBMS DSTv26 patch 22873635 .
 6a) 10g and 11.1 only: Supported versions and platforms.
 6b) 10g and 11.1 only: RDBMS DSTv26 patch 22873635 needs Patch 7695070 installed using Opatch.
 6c) 10g and 11.1 only: Applying the RDBMS DSTv26 patch 22873635 on the server side.
 6d) 10g and 11.1 only: After the server apply of RDBMS DSTv26 patch 22873635 and restart of the database:
 6e) 10g and 11.1 only: Applying the RDBMS DSTv26 patch 22873635 on clients
 7) The OJVM DSTv26 patch 22873666 .
 8) Other Oracle products:
 8.a) Enterprise Manager (Grid Control, OMS, Repository and Agents )
 8.b) Grid Infrastructure home.
 8.c) Oracle Applications
 8.d) Java in the Database home
 8.e) Oracle solaris

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.