Recovery using the backup of the control file should be used as the last option as this means using the RESETLOGS option to open the database which should be avoided given the option.

The better alternative is to recreate the control file . This can be done only if all the current redo log files are available.

That is why it is very important to issue the command:

Restore only the Control files to the location specified in the init.ora along with the data files –

SVRMGR> STARTUP MOUNT

SVRMGR> RECOVER DATABASE USING BACKUP CONTROLFILE;

Apply archived redo log files;

Eventually, Oracle will request the archived log corresponding to the current online log. It does this because the (backup) controlfile has no knowledge of the current log sequence. If an attempt is made to apply the suggested log, the recovery session will exit with the following message:

ORA-00308: cannot open archived log '/sp105db04/ORACLE/rman/arch/arch41.log'

ORA-27037: unable to obtain file status

IBM AIX RISC System/6000 Error: 2: No such file or directory

SVRMGR> SELECT MEMBER FROM V$LOGFILE;

1 /sp105db04/ORACLE/rman/redo01.log

2 /sp105db04/ORACLE/rman/redo02.log

3 /sp105db04/ORACLE/rman/redo03.log

3 rows selected.

At this stage, simply restart the recovery session and apply the current online log. The best way to do this is to try applying the online redo logs one by one until Oracle completes media recovery:

SVRMGR> recover database using backup controlfile;

ORA-00279: change 211213 generated at 03/08/00 12:07:56 needed for thread 1

ORA-00289: suggestion : /sp105db04/ORACLE/rman/arch/arch41.log

ORA-00280: change 211213 for thread 1 is in sequence #41

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

Log applied.

Media recovery complete.

SVRMGR>ALTER DATABASE OPEN RESETLOGS;