Examine the Data Guard configuration:
DGMGRL > show configuration;
Configuration-Animals
Protection Mode: MaxPerformance
Databases:
dogs-Primary database
sheep-Snapshot standby database
cats-Snapshot standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
You receive an error while attempting to raise the protection mode to Maximum Availability:
DGMGDRL> edit configuration set protection mode as maxavailability;
Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode
Failed.
Identify two statements that you can execute, either one of which will enable successful raising of the
protection mode to Maximum Availability.
A.
DGMGRL> convert database sheep to physical standby;
B.
DGMGRL> convert database cats to physical standby;
C.
DGMGRL> edit database dogs set property LogXptMode= fastsync;
D.
DGMGRL> edit database sheep set property LogXptMode= fastsync;
E.
DGMGRL> edit database cats set property LogXptMode= sync;
Explanation:
The MAXAVAILABILITY protection mode requires that there be at least one standby database configured to
use standby redo log files, with its LogXptMode configurable database property set to SYNC.
https://docs.oracle.com/cd/B28359_01/server.111/b28295/cli.htm
Correct Ans: D, E
Snapshot standby receives redo but do not apply. Here you are changing protection mode from MaxPerformance to MaxAvailability NOT MaxProtection so no need to convert to physical standby when using DGMGRL commands.
***Question is either one of which will enable successful raising of the protection mode to Maximum Availability
– When the database running in MaxPerformance mode standby receiving redo in ASYNC NOAFFIRM.
– In order to convert to Maximum Availability it should be either,
sync – SYNC AFFIRM or
fastsync – SYNC NOAFFIRM
You can still change protection mode when the configuration only contains Snapshot standby databases as long as it receives redo in SYNC mode either AFFIRM or NOAFFIRM.
Here dogs is a primary database, and LogXptMode should be changed for standby service so it will have no effect unless changed for the standby database.
Either one of the following commands will fix the problem.
D. DGMGRL> edit database sheep set property LogXptMode= fastsync;
E. DGMGRL> edit database cats set property LogXptMode= sync;
I have tested this as well.