With a Data Guard Configuration in Maximum Performance protection mode, don’t go to Maximum Protection directly, because that leads to a restart of the primary database:
DGMGRL> show configuration; Configuration - myconf Protection Mode: MaxPerformance Databases: prima - Primary database physt - Physical standby database physt2 - Physical standby database (receiving current redo) Fast-Start Failover: DISABLED Configuration Status: SUCCESS DGMGRL> edit configuration set protection mode as maxprotection; Operation requires shutdown of instance "prima" on database "prima" Shutting down instance "prima"... Database closed. Database dismounted. ORACLE instance shut down. Operation requires startup of instance "prima" on database "prima" Starting instance "prima"... ORACLE instance started. Database mounted. Database opened.
Instead, go to Maximum Availability first and then to Maximum Protection:
DGMGRL> edit configuration set protection mode as maxperformance; Succeeded. DGMGRL> edit configuration set protection mode as maxavailability; Succeeded. DGMGRL> edit configuration set protection mode as maxprotection; Succeeded.
The demo was done with 12c, involving a cascading standby database, but the behavior is the same in 11g already. The odd thing about it is that DGMGRL will restart the primary without warning. Wanted to share that with the Oracle community for years but always got over it somehow.