Database Restore and Recovery Procedure: Outline

The basic procedure for performing restore and recovery with RMAN is as follows:
1. Determine which database files must be restored from backup, and which backups
(which specific tapes, or specific backup sets or image copies on disk) to use for
the restore operation. The files to be restored may include the control file, SPFILE,
archived redo log files, and datafiles.

2. Place the database in the state appropriate for the type of recovery that you are
performing. For example, if you are recovering a single tablespace or datafile, then
you can keep the database open and take the tablespace or datafile offline. If you
are restoring all datafiles, then you must shut down the database and then mount
it before you can perform the restore.

3. Restore lost database files from backup with the RESTORE command. You may
restore files to their original locations, or you may have to restore them to other
locations if, for instace, a disk has failed. You may also have to update the SPFILE
if you have changed the control file locations, or the control file if you have
changed the locations of datafiles or redo logs.

4. Perform media recovery on restored datafiles, if any, with the RECOVER command.

5. Perform any final steps required to make the database available for users again .
For example, re-open the database if necessary, as happens when restoring lost
control files, or bring offline tablespaces online if restoring and recovering
individual tablespaces.

This outline is intended to encompass a wide range of different scenarios. Depending
upon your situation, some of the steps described may not apply. (For example, you do
not need to perform media recovery if the only file restored from backup is the
SPFILE.) You will have to devise your final recovery plan based on your situation.