My Oracle Support Banner

Applying the DSTv27 update for the Oracle Database (Doc ID 2163470.1)

Last updated on FEBRUARY 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.5 to 12.1.0.2 [Release 10.1 to 12.1]
Oracle Database - Standard Edition - Version 10.1.0.5 to 12.1.0.2 [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
Information in this document applies to any platform.

Purpose


To see if you NEED DSTv27 for the time zone change in Asia/Novosibirsk in 2016, please see <note 2152421.1> - Asia/Novosibirsk (Russia) switch from +06 to +07 on July 2016 - Impact on Oracle RDBMS

NO Proactive backports of the RDBMS DSTv27 <patch 23614158> are done. All supported versions can be requested .
Please log a SR if you need a backport to a platform or current version not released yet.

NO Proactive backports of the OJVM DSTv27 <patch 23614160> are done. All supported versions can be requested .
Please log a SR if you need a backport . Note that the OJVM DST patch is platform generic.

There are no "PSU DST patches" , for example an Oracle DST patch for 11.2.0.4 can be applied using Opatch on *any* 11.2.0.4 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 DSTv27 update includes the timezone information from the IANA ( http://www.iana.org/time-zones ) data tzdata2016f.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 DSTv26patch (and not included in DSTv27) are:

Asia/Novosibirsk switches from +0600 to +0700 on 2016-07-24 at 02:00

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

Asia/Novosibirsk

Scope

This note will give an overview on what checks to perform before applying the DSTv27 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

Details

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
Purpose
Scope
Details
 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 DSTv27 patch 23614158 on Oracle RDBMS 12cR1 ( 12.1.0.1 and 12.1.0.2) .
 2.a) Applying the RDBMS DSTv27 patch 23614158 on the server side in Oracle RDBMS 12cR1.
 2.b) Applying the RDBMS DSTv27 patch 23614158 on the client side in Oracle RDBMS 12cR1.
 3) Oracle RDBMS 11gR2 : Applying the RDBMS DSTv27 patch 23614158 on Oracle RDBMS 11gR2 ( 11.2.0.4 , 11.2.0.3 , 11.2.0.2 or 11.2.0.1)
 3.a) Applying the RDBMS DSTv27 patch 23614158 on the server side in Oracle RDBMS 11gR2
 3.b) Applying the RDBMS DSTv27 patch 23614158 on the client side in Oracle RDBMS 11gR2.
 4) 10g and 11.1 only:  What to check before applying the RDBMS DSTv27 patch 23614158.
 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 DSTv27 patch 23614158 .
 6a) 10g and 11.1 only: Supported versions and platforms.
 6b) 10g and 11.1 only: RDBMS DSTv27 patch 23614158 needs Patch 7695070 installed using Opatch.
 6c) 10g and 11.1 only: Applying the RDBMS DSTv27 patch 23614158 on the server side.
 6d) 10g and 11.1 only: After the server apply of RDBMS DSTv27 patch 23614158 and restart of the database:
 6e) 10g and 11.1 only: Applying the RDBMS DSTv27 patch 23614158 on clients
 
 7) The OJVM DSTv27 patch 23614160 .
 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
References

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