My Oracle Support Banner

Primary Note DST FAQ : Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches (Doc ID 412160.1)

Last updated on MARCH 03, 2023

Applies to:

Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database - Standard Edition - Version and later
Oracle Database - Personal Edition - Version and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.



To give an overview of all existing Oracle RDBMS DST updates and the related notes.

Note that "sysdate" or "systimestamp" has no relation with the Oracle RDBMS DST patches, sysdate/systimestamp is pure depending on the Operating system clock.
So if you have a "wrong database time" after a DST transition updating Oracle RDBMS DST patches will NOT solve your issue, please see <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 a Unix server.
The Oracle kernel itself is also not impacted by the OS/system clock changes (or for that matter Oracle DST patches). <Note:1013279.6> How Does Daylight Savings Time Affect The Database Kernel?

Please DO note that even if you are located in a country that has changed the DST start or end day in many cases there is no need to "update the Oracle RDBMS DST information".

If your OS has been patched or correctly configured the the "oracle time" (= sysdate) will be correct.
Only if the actual timezone is used in (PL)SQL an "Oracle RDBMS DST" update is needed.

An excellent introduction to what DST (Daylight Saving Time) is, is found in this video.
A map of the world timezones is found on
A list with the unambiguous "Macro-region/Region" timezone name for a most country's /locations:
A nice conversion website is

There are currently 41 versions of the Oracle RDBMS Time Zone files.

Latest DST released version: DSTv41: RDBMS Patch 35099667 and OJVM Patch 35099674

<Note 2930097.1> Applying the DSTv41 update for the Oracle Database

To apply the latest see point "C.1.c) To update a database to a new DST version please check the relevant advisory note:" in this note.

All time zone file updates are cumulative, meaning a newer Oracle RDBMS / OJVM DST patch has all the changes of the previous updates.

All information is derived from the IANA Timezone (Olson) database  (mailing list archive is here and release archive is here)
This information is offered "as is".


The changes included in the DSTv41 patch (and not included in DSTv40) are listed below:

Changes included in tzdata2022f & tzdata2022g
--The 2022f release of the tz code and data is available.

This release contains the following changes. The most urgent one is the

change for Chihuahua, Mexico which affects timestamps starting Sunday.


Mexico will no longer observe DST except near the US border.

Chihuahua moves to year-round -06 on 2022-10-30.

Fiji no longer observes DST.

Move links to 'backward'.

In vanguard form, GMT is now a Zone and Etc/GMT a link.

zic now supports links to links, and vanguard form uses this.

Simplify four Ontario zones.

Fix a Y2438 bug when reading TZif data.

Enable 64-bit time_t on 32-bit glibc platforms.

Omit large-file support when no longer needed.

In C code, use some C23 features if available.

Remove no longer-needed workaround for Qt bug 53071.

Changes to future timestamps

Mexico will no longer observe DST after 2022, except for areas

near the US border that continues to observe US DST rules.

On 2022-10-30 at 02:00 the Mexican state of Chihuahua moves

from -07 (-06 with DST) to year-round -06, thus not changing

its clocks that day. The new law states that Chihuahua

near the US border no longer observes US DST.

Fiji will not observe DST in 2022/3.

For now, assume DST is suspended indefinitely.

--The 2022g release of the tz code and data is available.

The northern edge of Chihuahua changes to US timekeeping. Much of Greenland stops changing clocks after March 2023.


The changes included in the DSTv40 patch (and not included in DSTv39) are listed below:

Changes included in TZDATA2022E & TZDATA2022D

Jordan and Syria are abandoning the DST regime and are changing to permanent +03, so they will not fall back from +03 to +02 on 2022-10-28.


Palestine now springs forward and fall back at 02:00 on the first Saturday on or after March 24 and October 24, respectively.


The changes included in the DSTv39 patch (and not included in DSTv38) are listed below:

Chile's DST is delayed by a week in September 2022.
Iran no longer observes DST after 2022.
Rename Europe/Kiev to Europe/Kyiv.
New zic -R option
Vanguard form now uses %z.
Finish moving duplicate-since-1970 zones to 'backzone'.
New build option PACKRATLIST
New tailored_tarballs target, replacing rearguard_tarballs
Workaround awk bug in FreeBSD, macOS, etc.
Improve tzselect on intercontinental Zones.


The changes included in the DSTv38 patch (and not included in DSTv37) are listed below:


Changes included in tzdata2022a
Palestine will spring forward on 2022-03-27, not -03-26.
zdump -v now outputs better failure indications.
Bug fixes for code that reads corrupted TZif data.


 The changes included in the DSTv37 patch (and not included in DSTv36) are listed below:


Changes to future timestamps
++ Palestine will fall back 10-29 (not 10-30) at 01:00.


The changes included in the DSTv36 patch (and not included in DSTv35) are:


+ Volgograd switches to Moscow time on 2020-12-27 at 02:00.
+ Volgograd changes time zone from +04 to +03 on 2020-12-27 at 02:00.


The changes included in the DSTv35 patch (and not included in DSTv34) are:

++ Morocco springs forward on 2020-05-31, not 2020-05-24.
++ Canada's Yukon advanced to -07 year-round on 2020-03-08.
++ America/Nuuk renamed from America/Godthab.
++ zic now supports expiration dates for leap second lists.


Current non-historical changes to the start and end date of DST for some regions / country's that are not included in DSTv34 (  IANA Timezone (Olson) database tzdata2019b update) , if any , can be found here:


To see if your system is affected when a times changes from DST start and/or stop date please use the respective documents. For example:

North Korea switches back from +0830 to +09 on May 2018- Impact on Oracle RDBMS <Note 2428170.1>

Brazil to Start DST on November From 2018 Onwards- Impact on Oracle RDBMS <Note 2331560.1>

Fiji ends DST on 14 January 2018 - Impact on Oracle RDBMS <Note 2331560.1>

For other Timezones than the ones in the notes you can edit the provided script with the timezone name that you want to check.


This note
* Shows how to see the currently installed version of the RDBMS / OJVM patch on your server
* Lists the current available DST advisories
* Answers some common questions.
* Lists the updated time zones between each version of the RDBMS DST updates.

We strongly recommend to have a look at these 2 FAQ's:
<NOTE:340512.1> - Timestamps & time zones - Frequently Asked Questions
<NOTE:227334.1> - Dates & Calendars - Frequently Asked Questions

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!

In this Document
 A) How to find the currently installed version of the RDBMS DST patch ?
 A.1) 8.1.7 and lower have no database support for Timezones.
 A.2) for 9i you can use the utltzver.sql script
 A.3) for 10g and 11gR1 query v$timezone_file  
 A.4) for 11gR2 and higher query v$timezone_file or DATABASE_PROPERTIES 
 A.5) possible confusing outputs in 11gR2 and higher:
 B) How can I see what OJVM DST patch is applied?
 C) Notes covering the current DST available updates
 C.1) Oracle RDBMS and OJVM DST related notes
 C.1.a) If you upgrade to,,, ,, , , , or,18.x, 19.x, 21.x  please see:
 C.1.b) If you apply the , ,, ,, or,18.x, 19.x, 21.x patch set please see:
 C.1.c) To update a database to a new DST version please check the relevant advisory note:
 C.1.d) DST patches list including Latest DST released Version
 C.1.e) How to monitor DST progress and estimate the time it takes
 C.2) Enterprise Manager (Grid Control OMS, Repository and Agents )
 C.3) Oracle Applications
 C.4) Java in the Database home
 C.5) Oracle solaris
 D) Do I need to reapply DST patches each year?
 E) I'm on DSTv <insert current version of your db or client> , do I NEED to apply newer DST patches?
 E.1) For the Oracle RDBMS DST patches:
 E.2) For the OJVM DST patches
 E.3) Can I "downgrade" to a lower DST version?
 F) Can I rely on the Oracle Timezone data?
 G) For what versions are DST patches provided / there is no DST version X for my Oracle RDBMS version?
 G.1) for what Oracle RDBMS versions are DST patches provided?
 G.2) How to apply RDBMS DST patches manually for versions who are not provided:
 G.2.a) for versions lower than ( and lower):
 G.2.b) for version 11gr2 ( and higher):
 G.2.c) for version 12cR1 ( or
 H) Overview of what DST version is by default used/included in what Oracle RDBMS version and all DST patch numbers
 I) What timezones are known / I'm missing timezones in the Oracle Database / should I use acronym timezone names like CET, PST, NZ etc ?
 J) List of updated Timezones in RDBMS DST updates
 K) List of synonyms known in the Olson database

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