ORA-00216: controlfile could not be resized for migration
from 8.0.2
- 1 Answers
- 2834 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Controlfiles created by release 8.0.2 were missing
some records. These records are automatically added by
resizing the contolfile when attempting to run a later
release. The resize failed.
Action: Look in the alert log for the reason that the resize
failed. If it can be fixed by giving the controlfile more
space, then do that. Otherwise, use the CREATE CONTROLFILE
script dumpped to the trace file to create a new controlfile.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
PCC-02307: void can only be used when single parameter
NPL-00103: unusable ASN.1 context
TNS-12160: TNS:internal error: Bad error number
ORA-23488: propagation mode "string" for "string" is not allowed for this operation
PCC-00139: Cannot change MAXLITERAL after an EXEC SQL statement
ORA-19211: column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
ORA-13412: invalid scale parameter
ORA-27124: unable to detach from shared memory segment
ORA-31018: Error deleting XML document
ORA-01937: missing or invalid role name
SQL*Loader-00125: specified value for readsize(number) less than max_record_size(number)
ORA-33046: (XSAGDNGL22) In AGGMAP workspace object, you can specify only one SCREENBY clause.
Oracle Errors 
