Which statement describes the significance of the CHANGE FAILURE command in RMAN?

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

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.



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Jake from SF

Jake from SF

A and D are correct

http://docs.oracle.com/cd/E36909_01/backup.1111/e10642/rcmrepai.htm

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 HIGH priority, 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 to CLOSED or to PRIORITY HIGH or PRIORITY LOW.