Implementing Data Guard - Expert Consolidation in Oracle Database 12c - page 351

Protection Mode: MaxAvailability
Databases:
CDB1DCA - Primary database
CDB1DCB - Physical standby database
CDB1DCC - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
The configuration is now changed to maximum availability. You could read in the previous chapter that Data
Guard redo can be shipped to the standby, which acknowledges that it received the redo in a memory buffer but has
not written it to disk yet. This mode is only available in Maximum Availability and is called “fastsync”. It corresponds to
the options “SYNC NOAFFIRM” in the log_archive_dest_n initialization parameter. Before Oracle 12c you could only
have ASYNC NOAFFIRM (logXptMode “async”) or SYNC AFFIRM (logXptMode “sync”). Refer back to the previous
chapter for a discussion of the fastsync transport mode.
Enabling Flashback on the standby
With the Broker active and managed recovery running you cannot add standby redo logs or enable flashback on the
standby database. Trying to do so results in an error:
SQL> select flashback_on, open_mode from v$database;
FLASHBACK_ON OPEN_MODE
------------------ --------------------
NO MOUNTED
SQL> alter database flashback on;
alter database flashback on
*
ERROR at line 1:
ORA-01153: an incompatible media recovery is active
Please do not issue the SQL command to stop managed recovery manually! All Data Guard related maintenance
has to be performed via the Broker. Change the state of the standby database to “apply-off ” using the Broker
command line interface again. This will stop managed recovery.
DGMGRL> edit database "CDB1DCB" set state="apply-off";
Succeeded.
You can then enable the flashback database feature, and enable managed recovery again:
DGMGRL> edit database "CDB1DCB" set state="apply-on";
Succeeded.