My Oracle Support Banner

Applying the DSTv31 update for the Oracle Database (Doc ID 2331554.1)

Last updated on FEBRUARY 22, 2019

Applies to:

Oracle Database - Standard Edition - Version 11.2.0.1 to 12.2.0.1 [Release 11.2 to 12.2]
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.2.0.1 [Release 11.2 to 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Purpose


To see if you NEED DSTv31,  please see the documents :

  • Northern Cyprus Reintroduces DST in October 2017 - Impact on Oracle RDBMS <Note 2331529.1>
  • Sudan switch from +03 to +02 on November 2017 - Impact on Oracle RDBMS <Note 2331552.1>
  • Fiji ends DST on 14 January 2018 - Impact on Oracle RDBMS <Note 2331560.1>
  • Turks and Caicos Islands Reintroduce DST on 11 March 2018 - Impact on Oracle RDBMS <Note 2331545.1>


RDBMS DSTv31 Patch 27015449 and OJVM DSTv31 Patch 27015468 are proactively done for all supported versions and platforms



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 DSTv31 update includes the timezone information from the IANA ( http://www.iana.org/time-zones ) data tzdata2017c.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 DSTv31 patch (and not included in DSTv30) are:

- Northern Cyprus has decided to resume EU rules starting 2017-10-29.

- Fiji ends DST 2018-01-14 instead of the 2018-01-21 previously predicted.

- Namibia will switch from +01 with DST to +02 all year on 2017-09-03 at 02:00.

- Sudan will switch from +03 to +02 on 2017-11-01. South Sudan is not switching.

- Tonga cancels DST and will not adjust its clocks on 2017-11-05.

- Turks & Caicos will switch from -04 all year to -05 with US DST on 2018-03-11 at 03:00.

 


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

  Africa/Khartoum, Africa/Windhoek, America/Grand_Turk, Pacific/Fiji, Pacific/Tongatapu

New timezone introduced in this DSTv31 patch:

  Asia/Famagusta

Scope

This note will give an overview on what checks to perform before applying the DSTv31 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 12c and 11gR2
 1.b) For Oracle RDBMS 10g and 11gR1:
 2) Oracle RDBMS 12c : Applying the RDBMS DSTv31 patch 27015449 on Oracle RDBMS 12c ( 12.1.0.1 , 12.1.0.2 and 12.2.0.1) .
 2.a) Applying the RDBMS DSTv31 patch 27015449 on the server side in Oracle RDBMS 12c.
 2.b) Applying the RDBMS DSTv31 patch 27015449 on the client side in Oracle RDBMS 12c.
 3) Oracle RDBMS 11gR2 : Applying the RDBMS DSTv31 patch 27015449 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 DSTv31 patch 27015449 on the server side in Oracle RDBMS 11gR2
 3.b) Applying the RDBMS DSTv31 patch 27015449 on the client side in Oracle RDBMS 11gR2.
 4) 10g and 11.1 only: 
 5) The OJVM DSTv31 patch 27015468 .
 6) Other Oracle products:
 6.a) Enterprise Manager (Grid Control, OMS, Repository and Agents )
 6.b) Grid Infrastructure home.
 6.c) Oracle Applications
 6.d) Java in the Database home
 6.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.