Control file needs recovery when
When one control file becomes corrupted, oracle database automatically stops running. One can determine which control file is causing a problem by looking into alert log file. Then remove the corrupted control file and copy good control file to the corrupted location
- Any one control file specified in a parameter file is lost due to media failure or corrupted
- New control file is needed when changing the database
When one control file becomes corrupted, oracle database automatically stops running. One can determine which control file is causing a problem by looking into alert log file. Then remove the corrupted control file and copy good control file to the corrupted location
-
rm -f /u10/oradata/controlfile01.ctl
-
cp /u20/oradata/controlfile02.ctl /u10/oradata/controlfile01.ctl
- Then mount the database
STARTUP MOUNT;
- and open it
ALTER DATBASE OPEN;
- Shutdown the database:
SHUTDOWN ABORT;
-
cp /u20/oradata/controlfile02.ctl /u10/oradata/controlfile04.ctl
- modify PFILE:
CONTROL_FILE='/u20/oradata/controlfile02.ctl', '/u21/oradata/controlfile03.ctl', '/u30/oradata/controlfile04.ctl'
-
Then mount and open the database:
STARTUP MOUNT; ALTER DATBASE OPEN;
No comments:
Post a Comment