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 max availability; 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;
DGMGRL> show configuration;
Configuration – config2
Protection Mode: MaxPerformance
Databases:
prim – Primary database
stdby2 – Snapshot standby database
stdby1 – Snapshot standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL> edit configuration set protection mode as maxavailability;
Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode
DGMGRL> edit database stdby1 set property logxptmode = ‘sync’;
Property “logxptmode” updated
DGMGRL> edit configuration set protection mode as maxavailability;
Succeeded.
E is a valid answer
D is also valid, fastsync is allowed in maxavailability.
And, as shown in the example code, it’s not necessary to change to physical standby mode.
D,E
Converting either sheep or cats would also work, right?
So…
A, B, D, E ???
Primary was convert to max avali.
DGMGRL> edit configuration set protection mode as maxavailability;
–PRIMARY
SQL> select PROTECTION_MODE,PROTECTION_LEVEL from v$database;
PROTECTION_MODE PROTECTION_LEVEL
——————– ——————–
MAXIMUM AVAILABILITY RESYNCHRONIZATION
But snapshot database was with max performance yet.
SQL> select PROTECTION_MODE,PROTECTION_LEVEL from v$database;
PROTECTION_MODE PROTECTION_LEVEL
——————– ——————–
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
After convert one snapshot to physical then change protection:
SQL> select PROTECTION_MODE,PROTECTION_LEVEL from v$database;
PROTECTION_MODE PROTECTION_LEVEL
——————– ——————–
MAXIMUM AVAILABILITY MAXIMUM AVAILABILITY
If have to analyse only error ORA-16627 to fix is D,E
But if analyse all configuration then A,B,D,E.
D, E
Tested in lab env
If you convert any of the databases to physical STBY and they dont have LogXptMode equal to SYNC or FASTSYNC. The protection mode can be activated.
So D and E are correct
Correction: Protection mode CANNOT be activated