DBCA Ignores OS Timezone EUROPE/HELSINKI While Setting STIME And/Or DBMS_SCHEDULER.GET_SYS_TIME_ZONE_NAME Yields Wrong Output
(Doc ID 2202879.1)
Last updated on FEBRUARY 23, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Configuration Assistant - Version 11.2.0.1 and later
Oracle 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
Information in this document applies to any platform.
Symptoms
- In a 11g database that is installed in system where Operating System timezone is Europe/Helsinki, scheduler's timezone is set to AFRICA/CAIRO when database is created using DBCA.
- Similarly, in a 12c database (with same OS timezone) is set to Asia/Nikosia. This issue is specific to the timezone - Europe/Helsinki
- If the TZ variable is set, the STIME is set properly to EUROPE/HELSINKI
- Another Symptom is that DBMS_SCHEDULER.GET_SYS_TIME_ZONE_NAME yeilds wrong output, if Operating System timezone is Europe/Helsinki and TZ variable is not set.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |