A FULL BACKUP IS TAKEN AT 8:30 AM ON 3rd Jan, 2000. A DATAFILE IS ADDED AT 9:00 AM. AND THERE WAS A MEDIA FAILURE AT 10:30 AM. or a tablespace has been dropped.

Remember, the current control file should match the physical structure of the database at the intended time of recovery. Review the list of files which correspond to the control file backup as well as the current control file so as to determine whether to use the current control file for recovery or the backup of the control file.

If the datafile is not needed for recovery because it corresponds to a point in time after which we want to recover, do not restore it.

SVRMGR> STARTUP MOUNT

SVRMGR> RECOVER DATABASE UNTIL TIME '2000-01-03:10:00:00' USING BACKUP CONTROLFILE;

(Apply Archive Logs)

Apply archived logs as requested. 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> RECOVER DATABASE UNTIL TIME '2000-01-03:10:00:00' 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}

Media recovery cancelled.

SVRMGR> ALTER DATABASE OPEN RESETLOGS;

RESETLOGS option should be used when backup of control file is used or if it is incomplete recovery.