Restore and recovery with RMAN

The (DRA) Data Recovery Advisor

• DRA is capable of generating scripts to repair damage to datafiles and (in some circumstances) the controlfile: it does not advise on problems with the spfile or with the online redo log files.
• It is dependent on the Automatic Diagnostic Repository (the ADR) and the Health Monitor.
  • HM is not stored in the database, but in the file system.
  • ADR is located in the directory specified by the DIAGNOSTIC_DEST instance parameter.
• HM types

  • nomount --- DB Structure Integrity --- check the integrity of the controlfile.

  • mount --- DB Structure Integrity --- check the integrity of the controlfile, and of the online redo log files and the datafile headers.

                                       --- Redo Integrity Check --- check the online and archive log files

• • open --- scan every data block for corruption, and check the integrity of the data dictionary and the undo segments.

Using the Data Recovery Advisor

• Assess data failures --- The Health Monitor, running reactively or on demand, will write error details to the ADR.
  

• List failures --- The DRA will list all failures, classified according to severity.

• Advise on repair --- The DRA will generate RMAN scripts to repair the damage.

• Execute repair --- Run the scripts.

Database Restore and Recovery

The critical files are

• Any copy of the controlfile
• A datafile that is part of the SYSTEM tablespace
• A datafile that is part of the current undo tablespace
  

Noncritical files are

• Multiplexed online log files
• Tempfiles
• Datafiles that are not part of the SYSTEM or current undo tablespaces

Restore database in noarchivelog mode

• The last backup must have been a whole, offline backup

Recovery nocritical file in archivelog mode

Recovery critical datafile

Incomplete Recovery

• An incomplete recovery means losing data
• A special case of incomplete recovery is recovery of the controlfile