Applying the DSTv42 update for the Oracle Database (Doc ID 2941491.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database - Standard Edition - Version 11.2.0.4 and later
Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Information in this document applies to any platform.

Purpose

RDBMS DSTv42 Patch 35220732 32327201 32327201 32327201 32327201 32327201 32327201 3232720132327201 32327201 32327201 32327201 32327201 32327201 32327201 32327201 32327201 32327201 32327
and OJVM DSTv42 Patch 35239280 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 customers with a valid Extended Support can download the backports to versions that are NOT in Premier 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 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 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 for 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 DSTv42 update includes the timezone information from the IANA ( http://www.iana.org/time-zones ) data TZDATA2023C.tar.gz contains all previous Oracle RDBMS DST updates.

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

The changes included in the DSTv42 patch (and not included in DSTv42) are listed below

Changes included in TZDATA2023C

Full details are here

https://mm.icann.org/pipermail/tz-announce/2023-March/subject.html

Release 2023ai - 2023-03-28 12:42:14 -0700

Changes to past and future timestamps

Model Lebanon's DST chaos by reverting data to tzdb 2023a.

Release 2023b - 2023-03-23 19:50:38 -0700

Changes to future timestamps

This year Lebanon springs forward April 20/21 not March 25/26.

[This was reverted in 2023ai.]

Release 2023a - 2023-03-22 12:39:33 -0700

Briefly:

Egypt now uses DST again, from April through October.

This year Morocco springs forward April 23, not April 30.

Palestine delays the start of DST this year.

Much of Greenland still uses DST from 2024 on.

America/Yellowknife now links to America/Edmonton.

tzselect can now use current time to help infer timezone.

The code now defaults to C99 or later.

Fix use of C23 attributes.

Scope

This note will give an overview of what checks needs to be performed before applying the DSTv42 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 as 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 the wrong time ( SYSDATE and SYSTIMESTAMP) after DST change, server reboot, database restart, or installation when connecting to a database on a Unix server

For more information about Timestamp with (local) Time Zone please check Note 340512.1 Timestamps & time zones - Frequently Asked Questions