ORA-01804: Failure To Initialize Timezone Information when migrating timezone
(Doc ID 2660220.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.2.0.1 [Release 11.2 to 12.2]Oracle Cloud Infrastructure - Exadata Cloud Service
Information in this document applies to any platform.
Symptoms
This error could occur with any timezone version upgrade when using the scripts in Doc ID 1585343.1. Not limited to the v32 to v34 upgrade example described in this document.
Customer migrated a database from timezone file v32 DB home (Server A) to v34 DB home (Server B).
On the target server B, there are multiple database instances sharing the same Oracle DB home. All of them have the correct v34 when querying v$timezone_file except the newly migrated database:
Existing database instances:
v34 timezone files are present ($ORACLE_HOME/oracore/zoneinfo) with proper permission at server B, :
timezone_32.dat
timezlrg_32.dat
All other checks in Doc ID 365558.1 are verified with no issue.
Changes
Migrated a database from timezone file v32 DB home (Server A) to 34 DB home (Server B).
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 |