As in the case of Broker, in physical standby we need to use DGMGRL prompt using SET STATE='APPLY-OFF and SET STATE='APPLY-ON' for shutting down.Yes to shutdown only MRP Process.
For Primary database bounce can we use the following two SQL commands to before shutdown the primary ???First command will stop the broker, second command will stop sending redo data from primary to standby.
ALTER SYSTEM SET DG_BROKER_START=FALSE SCOPE=BOTH;
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER SCOPE=BOTH
After primary database bounce can we enable the standby with the below SQL commands ???Yes. It's correct.
ALTER SYSTEM SET DG_BROKER_START=TRUE SCOPE=BOTH;
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE SCOPE=BOTH;
Note : Here Physical standby is configured using Broker and we are NOT switching over, just primary database bounce.
And this did not change yet after about 20 minutes now.It may be older versions than 11gx. Its been good information to dig on this. :-)
I'm pretty sure that this was not always the behavior - in some older versions DMON did restart MRP automatically.
But I can't prove it presently, so you may take it just anecdotal.
Anyways, I think we can tell by the error message above that using recover managed standby database cancel is not the clean way to stop Redo Apply when using the Data Guard Broker.Perfect, When we are using broker then we should not operate such tasks from SQL*Plus. It's nice working with you always. Thanks for the information so far.