Applying the DSTv32 update for the Oracle Database (Doc ID 2463100.1)

Last updated on JUNE 13, 2023

Applies to:

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

Purpose

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

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

RDBMS DSTv32 Patch 28125601 and OJVM DSTv32 Patch 28127287 are proactively done for all supported versions and platforms

Scope

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