ORA-00216: controlfile could not be resized for migration
from 8.0.2
- 1 Answers
- 2540 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 |
TNS-01103: Protocol specific component of the address is incorrectly specified
SQL*Loader-00563: bad length for VAR record
ORA-13121: layer type type mismatch with topo_geometry layer type
DRG-11716: attempt to add Narrower Term string for non-Preferred Term string
ORA-37014: (XSACQUIRE_ACQUIRED) Object workspace object is already acquired.
IMG-00925: unable to write to the ORDImageSignature object
RMAN-02003: unrecognized character: string
ORA-00910: specified length too long for its datatype
EXP-00033: Could not find environment character set
RMAN-06110: changed controlfile copy unavailable
ORA-10614: Operation not allowed on this segment
QSM-01084: materialized view, string, has anchor, string, not found in query
Oracle Errors 
