Alert Log Reports "WARNING: DBTIMEZONE Is Not Set. Using System Default Timezone" Message From 11.2.0.4 Onwards
(Doc ID 2116721.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 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 Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The message "WARNING: DBTIMEZONE is not set. using system default timezone" is reported in the database alert log after upgrade from 11.2.0.3 to 12.1.0.2.
Tue Mar 08 09:47:32 2016
SMON: enabling cache recovery
Tue Mar 08 09:47:32 2016
[28901434] Successfully onlined Undo Tablespace 101.
Undo initialization finished serial:0 start:1816534844 end:1816534975 diff:131 ms (0.1 seconds)
Verifying minimum file header compatibility (11g) for tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
Tue Mar 08 09:47:32 2016
SMON: enabling tx recovery
Starting background process SMCO
Tue Mar 08 09:47:32 2016
SMCO started with pid=31, OS id=19661038
Tue Mar 08 09:47:33 2016
Database Characterset is WE8ISO8859P1
WARNING: DBTIMEZONE is not set. using system default timezone <==============================
No Resource Manager plan active
Starting background process AQPC
Tue Mar 08 09:47:33 2016
AQPC started with pid=34, OS id=11272424
Starting background process CJQ0
Tue Mar 08 09:47:34 2016
CJQ0 started with pid=35, OS id=39256086
Completed: alter DATABASE OPEN
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 |