Databases Reference
In-Depth Information
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
Second, change the priority from
high
to
low
with the
change failure
command:
RMAN> change failure 62 priority low;
You will be prompted to confirm that you really do want to change the priority:
Do you really want to change the above failures (enter YES or NO)?
If you do want to change the priority, then type
YES
, and hit the
Enter
key. If you run the
list failure
command
again, you'll see that the priority has now been changed to
low
:
RMAN> list failure low;
Here is some sample output:
Failure ID Priority Status Time Detected Summary
---------- -------- --------- ------------- -------
62 LOW OPEN 15-JUL-12 One or more non-system
data files are missing
How It Works
For most problems, you should never have to change the priority or status of a failure. However, sometimes you may
want to change the status or priority of a failure. In those cases, you can use the
change failure
command. For
example, you may have a data file missing that is in a tablespace that you know is not being used. In that case, you can
change the priority to
low
.
The priority of a failure can be one of the following:
critical
,
high
, or
low
. The status of failure can be
open
or
closed
.
If you fix a problem manually without using the
repair failure
command, the Data Recovery Advisor will
detect that the problem has been resolved when the next
list failure
command is issued. At that time, the Data
Recovery Advisor will change the status of any fixed failures to
closed
.
If you want to manually change the status of a failure from
open
to
closed
, then you can use the
closed
clause as
shown here:
RMAN> change failure 62 closed;
