You administer a Data Guard environment consisting of a primary and three physical standby databases.
One physical standby database is used for disaster recovery, one is used for reporting, and one is used as a
replica for testing.
The standby database used for testing is occasionally converted into a snapshot standby database and then
converted back to a physical standby.
The physical standby database is the only standby that is a mandatory destination.
The broker configuration operates in MAXIMUM PERFORMANCE mode.
Which ARCHIVELOG DELETION POLICY should be set, so that archive logs generated on the primary
database are not deleted before they are consumed appropriately on each of the standby databases, but which
allows them to be deleted form the primary as soon as it is safe to do so?
A.
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
B.
CONFIGURE ACHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
C.
CONFIGURE ACHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY;
D.
CONFIGURE ACHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;
E.
CONFIGURE ACHIVELOG DELETION POLICY TO NONE;
Explanation:
You can change this default deletion policy using the following RMAN command:
CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
Use the APPLIED ON STANDBY clause so that archived redo log files that have been applied on all mandatory
standby destinations will be deleted.
Incorrect Answers:
A: APPLIED ON ALL STANDBY is not valid.
C, D: SHIPPED TO is not valid.
E: Use the NONE clause so that archived redo logs in flash recovery area that were backed up or obsolete as
per the RMAN retention policy are eligible for deletion. This is the default configuration. Archived redo log files
that are backed up or obsolete are deleted to make space if the disk space in the flash recovery area becomes
full.
https://docs.oracle.com/cd/B19306_01/server.102/b14239/rman.htm#i1031870
Correct Ans: A
https://docs.oracle.com/database/121/SBYDB/rman.htm#GUID-38EB0163-6F07-4F89-9A17-FC21FD779785
If you want archive logs to be deleted only after applied on mandatory standby then APPLIED ON STANDBY is correct. Here it needs to be deleted on PRIMARY after consumed appropriately on each of the standby databases so APPLIED ON ALL STANDBY.
Recommended RMAN settings for 12c:
Primary:
CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY;
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Standby (where backups are happening):
CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP n TIMES TO DEVICE TYPE | ;
Standby (not part of RMAN backup):
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
are you sure with A? since one of the databases will be converted into a snapshot standby every now and then, the archivelogs will not be deleted on primary site until the database is converted back into a physical standby (logs cannot be applied when the database is a snapshot standby) – and with the text “…(they should) not (be) deleted before they are consumed appropriately on each of the standby databases…” I tend to choose C
C