DB provisioning fails on existing home:ORA-01804,but succeeds from new home with same RU.
(Doc ID 2911014.1)
Last updated on APRIL 29, 2024
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/AInformation in this document applies to any platform.
Symptoms
DB provisioning on an existing home with other running databases, fails with the following error in dbda execution
l; create temporary tablespace temp1 tempfile size 100m; alter database default temporary tablespace temp1; shutdown abort; startup; alter system set encrypt
_new_tablespaces=ddl; drop tablespace temp INCLUDING CONTENTS AND DATAFILES; create bigfile temporary tablespace temp tempfile '+DATAC1/cp1xyz/TEMPFILE/temp'
size 1000M autoextend on next 16g maxsize 512g; alter database default temporary tablespace temp; select name from v$tempfile; create spfile='+DATAC1/cp1xyz
/spfilecp1xyz.ora' from pfile='/u02/app/oracle/product/19.0.0.0/dbhome_15/dbs/initcp1xyz.ora'; quit
2022-10-17 08:50:40.242869 - ORACLE instance shut down.
ORACLE instance started.
Total System Global Area 7969176000 bytes
Fixed Size 9157056 bytes
Variable Size 1409286144 bytes
Database Buffers 6476005376 bytes
Redo Buffers 74727424 bytes
Database mounted.
Database opened.
drop tablespace temp INCLUDING CONTENTS AND DATAFILES
*
ERROR at line 1:
ORA-04088: error during execution of trigger 'SYS.DELETE_ENTRIES'
ORA-00604: error occurred at recursive SQL level 1
ORA-01804: failure to initialize timezone information
+ As a test, customer tried provisioning a new home with same RU and tried provisioning a database in it and it succeeds.
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 |
| Cause |
| Solution |
| References |