Last updated on OCTOBER 31, 2016
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 23-Feb-2012***
The Data Recovery Advisor automatically gathers data failure information when an error is encountered.
Data Failure: Examples
• Not accessible components, for example:
– Missing data files at the OS level <<<< Here is our example where one datafile lost
– Incorrect access permissions
– Offline tablespace, and so on
• Physical corruptions, such as block checksum failures or invalid block header field values
• Logical corruptions, such as inconsistent dictionary, corrupt row piece, corrupt index entry, or corrupt transaction
• Inconsistencies, such as control file is older or newer than the data files and online redo logs
• I/O failures, such as a limit on the number of open files exceeded, channels inaccessible, network or I/O error
If you suspect or know that a database failure has occurred, then use the LIST FAILURE command to obtain information about these failures. You can list all or a subset of failures and restrict output in
various ways. Failures are uniquely identified by failure numbers.
Note that these numbers are not consecutive, so gaps between failure numbers have no significance.
The ADVISE FAILURE command displays a recommended repair option for the specified failures.It prints a summary of the input failure and
implicitly closes all open failures that are already fixed.The default behavior when no option is used is to advise on all the CRITICAL and HIGH priority
failures that are recorded in ADR. (Automatic Diagnostic Repository)
The REPAIR FAILURE command is used after an ADVISE FAILURE command within the same RMAN session.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms