ORA-19734: wrong creation SCN - control file expects
converted plugged-in datafile
- 1 Answers
- 3201 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: When a tablespace is plugged into a database, the
tablespace is initially read-only. Oracle converts the
header of the plugged-in datafiles (assign them a new
creation SCN) when the tablespace is first made read-write.
This error occurs when the creation SCN in the file header
is different from the creation SCN in the controlfile,
possibly because this is the initial version of plugged-in
datafile.
Action: Either restore the converted datafile or continue
recovering the datafile.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-09791: slembdf: translation error, unable to translate error file name.
ORA-23471: template not authorized for user
PLS-01902: : hex to raw conversion error
ORA-30035: Undo tablespace cannot be specified as default temporary tablespace
ORA-34179: (MXCHGDCL20) workspace object is not a PARTITION TEMPLATE.
ORA-01653: unable to extend table string.string by string in tablespace string
RMAN-06521: archived logs required to recover from this backup will expire when this backup expires
DRG-10850: CTXRULE indextype does not support the operator
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
ORA-32005: error while parsing size specification [string]
PCC-02439: FOR clause not allowed in this COLLECTION statement
RMAN-06534: KEEP ... CONSISTENT option is not supported
Oracle Errors 
