Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-00217: controlfile could not be resized for migration
from 9.0.1
- 1 Answers
- 3282 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Controlfiles created by release 9.0.1 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 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 |
ORA-07621: smscre: illegal redo block size
ORA-13375: the layer is of type [string] while geometry inserted has type [string]
TNS-12207: TNS:unable to perform navigation
ORA-30121: 'string' is not an allowable value for 'string'
ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
QSM-01077: materialized view, string, is grouping at a higher level than query
ORA-32339: cannot alter materialized view with the PMOP
LPX-00113: element "~1S" ID attribute "~2S" must be #IMPLIED or #REQUIRED
ORA-19677: RMAN configuration name exceeds maximum length of string
ORA-00300: illegal redo log block size string specified - exceeds limit of string
ORA-09890: osnTXtt: malloc failed
ORA-30200: Wrong NLS item was passed into OCINlsGetInfo()
Oracle Errors 
