ORA-30012: undo tablespace '~' does not exist or o...

jiawang

ORA-30012: undo tablespace '~' does not exist or of wrong type                (Doc ID 1429423.1)              


Applies to:  Oracle Database - Enterprise Edition - Version 11.1.0.7 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
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.SymptomsWhen attempting to create a DB, the following error are reported in the alert log:


Sun Mar 04 15:31:18 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =605
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in client-side pfile ....<>
System parameters with non-default values:
processes = 5000
sessions = 5505
memory_target = 1504M
control_files = "...control01.ctl"
control_files = "...control02.ctl"
control_files = "...control03.ctl"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "...flash_recovery_area"
db_recovery_file_dest_size= 1G
undo_management = "AUTO"
undo_tablespace = "~"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=ORAEGRCXDB)"
audit_file_dest = "/u01.../adump"
audit_trail = "DB"
db_name = "XXXX"
open_cursors = 5000
Sun Mar 04 15:31:18 2012
PMON started with pid=2, OS id=17927
Sun Mar 04 15:31:18 2012
VKTM started with pid=3, OS id=17929
VKTM running at (100ms) precision
Sun Mar 04 15:31:18 2012
DIAG started with pid=4, OS id=17933
Sun Mar 04 15:31:18 2012
DBRM started with pid=5, OS id=17935
Sun Mar 04 15:31:18 2012
PSP0 started with pid=6, OS id=17937
Sun Mar 04 15:31:18 2012
DIA0 started with pid=7, OS id=17939
Sun Mar 04 15:31:18 2012
MMAN started with pid=8, OS id=17941
Sun Mar 04 15:31:18 2012
DBW0 started with pid=9, OS id=17943
Sun Mar 04 15:31:18 2012
LGWR started with pid=10, OS id=17945
Sun Mar 04 15:31:18 2012
CKPT started with pid=11, OS id=17947
Sun Mar 04 15:31:18 2012
SMON started with pid=12, OS id=17949
Sun Mar 04 15:31:18 2012
RECO started with pid=13, OS id=17951
Sun Mar 04 15:31:19 2012
MMON started with pid=14, OS id=17953
Sun Mar 04 15:31:19 2012
MMNL started with pid=15, OS id=17955
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE not set in environment. It is recommended
that ORACLE_BASE be set in the environment
Sun Mar 04 15:31:26 2012
CREATE DATABASE XXXX
..
UNDO TABLESPACE UNDOTBS1 DATAFILE '/u01/..UNDOTBS01.DBF' SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
CHARACTER SET AL32UTF8
...
Database mounted in Exclusive Mode
Lost write protection disabled
Successful mount of redo thread 1, with mount id 450331662
Assigning activation ID 450331662 (0x1ad7840e)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /u01/CONTROLS/ORAEGRC/data/REDO01.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
processing ?/rdbms/admin/dcore.bsq
...
CREATE UNDO TABLESPACE UNDOTBS1 DATAFILE '..UNDOTBS01.DBF' SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED

ORA-30012 signalled during: CREATE UNDO TABLESPACE UNDOTBS1 DATAFILE '/u01../UNDOTBS01.DBF' SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED

...
Errors in file /u01..trace/xxxx_ora_17960.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-30012: undo tablespace '~' does not exist or of wrong type

ORA-01501: CREATE DATABASE failed
ORA-01519: error while processing file '?/rdbms/admin/dtxnspc.bsq' near line 5
ORA-00604: error occurred at recursive SQL level 1
ORA-30012: undo tablespace '~' does not exist or of wrong type
Error 1519 happened during database creation, shutting down database
USER (ospid: 17960): terminating the instance due to error 1519
Instance terminated by USER, pid = 17960
ORA-1092 signalled during: CREATE DATABASE
..
...
ORA-1092 : opiodr aborting process unknown ospid (17960_47415454424256)
Sun Mar 04 15:31:35 2012
ORA-1092 : opitsk aborting process


Note that the init.ora file had the correct setting for the UNDO_MANAGEMENT and UNDO_TABLESPACE:


undo_management = 'AUTO'
undo_tablespace = 'UNDOTBS1'