This content has been marked as final. Show 4 replies
Broker automatically enables real-time apply on standby databases if the standby database has standby redo logs configured.
Stop redo apply
Restart redo apply broker
DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-OFF';
So get rid of the standby redo logs would be one way. I would leave it alone myself. Real time apply helps prevent data loss.
DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-ON';
Standby database configured with broker and applying the redo in really time; however, I want to change this to archive log apply mode without losing the broker configuration. Is it possible? If it is not possible to use broker to do archive log apply, can I remove the broker and use data guard to set up the standby to use archive log apply?
I think mseberg is answered correct, you can use enable/disable apply log with change of state on standby database with DGMGRL, as writen mseberg.
or you can disable recover standby database with following script from SQL*Plus.
SQL> alter database recover managed standby database cancel;
Mahir M. Quluzade
Thank you Msegerg and Mahir for your time.
why do you need to disable realtime apply in the first place.
Again removing standby redo logs will affect your protection, redo information from primary will be shipped only when they are archived which means that you will lose the transactions in the redologs which are yet to be archived on primary in case of a real disaster scenario.
DGMGRL allows you to set a number of properties for the database to control the behaviour of various services like log shipping and apply, i guess you can turn of one of the parameter to disable realtime apply. Check the output of "SHOW DATABASE VERBOSE <standby_dbname>" the property names are self explanatory.