ORA-19735: wrong creation SCN - control file expects initial
plugged-in datafile
- 1 Answers
- 2285 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 converted datafile.
Action: Either restore the initial version of the plugged-in
datafile, or continue database recovery, which will recover
the control file.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-13346: the coordinates defining an arc are collinear
ORA-39056: invalid log file specification.
SQL*Loader-00408: Physical record stack overflow
TNS-12222: TNS:no support is available for the protocol indicated
ORA-15047: ASM file name 'string' is not in multiple-file creation form
PLS-01412: Use of 'EXP' token
ORA-33004: (XSAGDNGL01) workspace object is not a relationship array.
ORA-22330: cannot alter a type that is not valid
IMG-00517: height or width not present in parameter string
ORA-02269: key column cannot be of LONG datatype
ORA-19716: error processing format string to generate name for backup
ORA-32135: Cannot assign FILEs
Oracle Errors 
