Applying the DSTv39 update for the Oracle Database (Doc ID 2893289.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database - Standard Edition - Version 11.2.0.4 to 21.7 [Release 11.2 to 21.0]
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 21.7 [Release 11.2 to 21.0]
Information in this document applies to any platform.

Purpose

RDBMS DSTv39 Patch 32327201 32327201 32327201 32327201 32327201 32327201 3232720132327201 32327201 32327201 32327201 32327201 32327201 32327201 32327201 32327201 32327201 32327
and OJVM DSTv39 Patch 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 that are NOT in Premier Support are possible/available for download only for customers with a valid Extended Support.
Exceptions for another version/platform combinations are only possible for customers with an existing Extended Support contract for the specific version/platform combination or platforms with an Extended Support Fee Waiver Period.

Please log an 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 an 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 an 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 DSTv39 update includes the timezone information from the IANA ( http://www.iana.org/time-zones ) data tzdata2022b.tar.gz, tzdata2022c.tar.gz 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 the DSTv39 patch (and not included in DSTv39) are listed below

Changes included in tzdata2022c & tzdata2022b

The change by Chile Govt. was included in timezone data 2022b, so it will also be in 2022c.
2022b:

Briefly:
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

Changes to future timestamps

Chile's 2022 DST start is delayed from September 4 to September 11.

Iran plans to stop observing DST permanently, after it falls back on 2022-09-21.

2022c:

Briefly:
Workaround awk bug in FreeBSD, macOS, etc.
Improve tzselect on intercontinental Zones.

Changes to code

Work around a bug in onetrueawk that broke commands like 'make traditional_tarballs' on FreeBSD, macOS, etc.

Add code to tzselect that uses experimental structured comments in zone1970.tab to clarify whether Zones like Africa/Abidjan and Europe/Istanbul cross-continent or ocean boundaries.

Fix bug with 'zic -d /a/b/c' when /a is unwritable but the directory /a/b already exists.

Remove zoneinfo2tdf.pl, as it was unused and triggered false malware alarms on some email servers.

Scope

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