OCP-1Z0-053-V13.02-125题

125.Which statement describes the significance of the CHANGE FAILURE command in RMAN? (Choose all that apply.)

A. It is used to change failure priority only for HIGH or LOW priorities.

B. It is used to execute the advised repair script.

C. It is used to change failure priority only for the CRITICAL priority.

D. It is used to explicitly close the open failures.

E. It is used to inform the database about the repair after the repair script executes.

Answer: AD

答案解析：

参考：http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmrepai.htm#BRADV89736

If appropriate, you can use CHANGE FAILURE command at any time in the Data Recovery Advisor workflow to change the priority of a failure from LOW to HIGH orHIGH to LOW, or close a failure that has been fixed manually. 

Changing Failure Status and Priority

In some situations, you may want to use the CHANGE FAILURE command to alter the status or priority of a failure. For example, if a block corruption has HIGHpriority, you may want to change it to LOW temporarily if the block is in a little-used tablespace.

If you repair a failure by a means other than the REPAIR FAILURE command, then Data Recovery Advisor closes it implicitly the next time you execute LIST FAILURE. For this reason, you do not normally need to execute the CHANGE FAILURE ... CLOSED command. You should need to use this command only if the automatic failure revalidation fails, but you believe the failure no longer exists. If you use CHANGE FAILURE to close a failure that still exists, then Data Recovery Advisor re-creates it with a different failure ID when the appropriate data integrity check is executed.

Typically, you specify the failures by failure number. You can also change failures in bulk by specifying ALL, CRITICAL, HIGH, or LOW. You can change a failure toCLOSED or to PRIORITY HIGH or PRIORITY LOW.

To change the status or priority of a failure:

1. List failures as described in "Listing All Failures".

   The following example lists one failure involving corrupt data blocks.

   RMAN> LIST FAILURE;

    

   List of Database Failures

   =========================

    

   Failure ID Priority Status    Time Detected Summary

   ---------- -------- --------- ------------- -------

   142        HIGH     OPEN      23-APR-07     One or more non-system datafiles

                                               are missing

   101        HIGH     OPEN      23-APR-07     Datafile 25: '/disk1/oradata/prod/example01.dbf' contains one or more corrupt blocks

    

2. Execute CHANGE FAILURE with the desired options.

   The following example changes the priority of a block corruption failure from HIGH to LOW.

   RMAN> CHANGE FAILURE 101 PRIORITY LOW;

    

   List of Database Failures

   =========================

    

   Failure ID Priority Status    Time Detected Summary

   ---------- -------- --------- ------------- -------

   101        HIGH     OPEN      23-APR-07     Datafile 25: '/disk1/oradata/prod/example01.dbf' contains one or more corrupt blocks

    

   Do you really want to change the above failures (enter YES or NO)?

   YESchanged 1 failures to LOW priority

3. Optionally, execute LIST FAILURE ALL to view the change.

   If you execute LIST FAILURE without ALL, then the command lists failures with LOW priority only if no CRITICAL or HIGH priority failures exist.

   RMAN> LIST FAILURE ALL;

    

   List of Database Failures

   =========================

    

   Failure ID Priority Status    Time Detected Summary

   ---------- -------- --------- ------------- -------

   142        HIGH     OPEN      23-APR-07     One or more non-system datafiles

                                               are missing

   101        LOW      OPEN      23-APR-07     Datafile 25: '/disk1/oradata/prod/example01.dbf' contains one or more corrupt blocks