Applying the DSTv41 update for the Oracle Database (Doc ID 2930097.1)

Last updated on APRIL 17, 2023

Applies to:

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

Purpose

RDBMS DSTv41 Patch 35099667 32327201 32327201 32327201 32327201 32327201 32327201 3232720132327201 32327201 32327201 32327201 32327201 32327201 32327201 32327201 32327201 32327201 32327
and OJVM DSTv41 Patch 35099674 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 DSTv41 update includes the timezone information from the IANA ( http://www.iana.org/time-zones ) data tzdata2022g.tar.gz, tzdata2022g.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 DSTv41 patch (and not included in DSTv41) are listed below

Changes included in tzdata2022f & tzdata2022g

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

https://mm.icann.org/pipermail/tz-announce/2022-October/000075.html

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

change for Chihuahua, Mexico which affects timestamps starting Sunday.

Briefly:

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.

https://mm.icann.org/pipermail/tz-announce/2022-November/000076.html

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

Scope

This note will give an overview of what checks needs to be performed before applying the DSTv41 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