Databases Reference
In-Depth Information
If a failure is detected, it will be recorded in the ADR. Once a failure is recorded in the ADR, then you can use the
advise failure
and
repair failure
commands to resolve the issue.
Failures with a
critical
status usually make your database unavailable and are typically diagnosed when
attempting to start the database. For example, a missing control file would be considered a
critical
failure.
A
high
failure is an issue that makes your database partially unavailable, such as a damaged or missing non-system
data file.
If you want to see more detail about a given failure, then use the
list failure ... detail
command.
In this example, we are listing more details on a failure with an ID of 62:
RMAN> list failure 62 detail;
Here is some sample output:
Database Role: PRIMARY
List of Database Failures
=========================
Failure ID Priority Status Time Detected Summary
---------- -------- --------- ------------- -------
62 HIGH OPEN 15-JUL-12 One or more non-system
data files are missing
Impact: See impact for individual child failures
List of child failures for parent failure ID 62
Failure ID Priority Status Time Detected Summary
---------- -------- --------- ------------- -------
445 HIGH OPEN 15-JUL-12 Data file 4:
'/u01/dbfile/o12c/users01.dbf' is missing
Impact: Some objects in tablespace USERS might be unavailable
If you want to see all failures that have been resolved and closed, then use the
closed
clause:
RMAN> list failure closed;
Table
20-1
describes the types of failures that can be reported from the
list failure
command.
Table 20-1.
Data Recovery Advisor List Failure Options
Failure Type
Description
all
Lists all failures
critical
Lists only critical failures with an
open
status
high
Lists only high-priority failures with an
open
status
low
Lists only low-priority failures with an
open
status
closed
Lists failures with a
closed
status
exclude failure
Excludes failures by a specified failure number
detail
Provides verbose description of the failure
