North Korea switches back from +0830 to +09 on May 2018- Impact on Oracle RDBMS
(Doc ID 2428170.1)
Last updated on JUNE 13, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Purpose
North Korea will revert its time zone from UTC+8:30 (PYT; Pyongyang Time) back to UTC+9 (KST; Korea Standard Time) on 2018-05-05.
The affected timezones are :
For Questions/official statements about the timezone change itself, please contact the North Korea Government .
IANA has updated Time Zone Database to reflect this change (tzdata2018c) http://www.iana.org/time-zones
This change is included in DSTv32.
Scope
Anyone who may be using the affected North Korea Timezone
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?
Used abbreviations:
TZ: TimeZone
TSTZ: TimeStamp with Time Zone
TSLTZ: TimeStamp with Local Time Zone
Details
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
| Purpose |
| Scope |
| Details |
| 1) The DATE dataype and SYSDATE / SYSTIMESTAMP |
| 2) Storing data in the TimeStamp with (Local) Time Zone datatype. |
| 3) TimeStamp with Time Zone columns are used, how do I see if the affected Korean Timezones are stored? |
| 4) Database timezone , Session timezone and CURRENT_DATE , LOCALTIMESTAMP , CURRENT_TIMESTAMP functions |
| 5) Oracle DST patches and this change. |
| 6) The OJVM dst information |
| 7) Java in the Database home |
| 8) Other Oracle software (Enterprise Manager , Oracle Applications etc) |
| 9) Will any data stored in DATE, TIMESTAMP, TIMESTAMP WITH (LOCAL) TIMEZONE columns be affected by changing the server OS timezone? |
| References |