This content has been marked as final. Show 3 replies
Hello;1 person found this helpful
The command :
DGMGRL> EDIT DATABASE 'StandBy2' SET PROPERTY 'LogShipping'='OFF';
The other option is
My concern is this will remove all TRANSPORT and you only want to do this for one location.
DGMGRL> EDIT DATABASE 'Primary' SET STATE='TRANSPORT-OFF';
I think I might consider
DISABLE DATABASE 'StandBy2';
Thanks mseberg! That is the correct command to disable a lone backup. That said, it's been well over an hour now and the primary is still trying to connect to the backup (I think).
In Cloud Control, Data Guard Admin page, I can see that 'StandBy2' is clearly disabled. This is great. However, the primary database is still being bogged down with "network" wait events. When I research I find that the wait events are "ARCH wait on ATTACH" which implies that the primary is still trying to connect to StandBy2. Do you have any insight into why it would be doing this?
Normally I never experience any "ARCH wait on ATTACH" wait events.
And it suddenly dropped off just now, after a couple hours. I can only hope that there was some sort of lingering process that hadn't expired yet...?
Thanks again for the help mse