ORA-00217: controlfile could not be resized for migration
from 9.0.1

Answer Posted / 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



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly

1755


ORA-16627: No standby databases support the overall protection mode.

3562


ORA-26076: cannot set or reset value after direct path structure is allocated

1480


IMP-00064: Definition of LOB was truncated by export

5893


ORA-26095: unprocessed stream data exists

2810






invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity

2862


ORA-26082: load of overlapping segments on table string.string is not allowed

1381


IMG-02003: 2FF03 - incorrect color histogram feature specification

1203


When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............

2325


ORA-26084: direct path context already finished

1488


NZE-28890: Entrust Login Failed

1411


IMP-00070: Lob definitions in dump file are inconsistent with database.

1291


ORA-26027: unique index string.string partition string initially in unusable state

6165


In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.

2331


IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

2306