This content has been marked as final. Show 2 replies
You could do:
ALTER DATABASE DISABLE THREAD 3;
check status of the groups in the thread, if any of them <> UNUSED, then archive them:
ALTER SYSTEM ARCHIVE LOG GROUP x;
Then drop the groups.
My question has to do with the logs needed between primary and standby. What I’m seeing is that the greatest number of threads are needed on each side, but not quite sure why if they are UNUSED. Can anyone elaborate on this? I can find no documentation that talks about this.Actually a RAC standby can work with just 1 instance started, because the MRP process runs only on 1 instance. Opening the standby is another story.
But of course you should have enough standby redo logs on the standby site to receive redo from the primary site.
Hi. Thank you for the quick response!
We are not running Active Data Guard and don't plan on opening the standby for read-write, and we have enough standby logs.
Right now my STANDBY is 3-node and PRIMARY is 2-node, but the PRIMARY shows 3 threads of redo of which thread 3 is UNUSED.
Is this needed for something in the Data Guard implementation? Should I go ahead and drop thread 3 from my PRIMARY? Sometimes what we CAN do as opposed to what we SHOULD do are not the same. Eventually we are going to un-Data Guard this environment so it not be an issue then, but I'm trying to understand. Maybe it's something that I should just safely ignore for now.