I created a tar with oracle.
One weird thing is during second switchover, the dg broker only brought one instance up, another one is down. That is the issue. I just don't know why the other one won't bring up.
Agreed. That why I thought trying the switchover and status from SQL might either either shake out the clue we need or allow the switchover from SQL. In the latter case I think that this means a broker has a bug. I search the Oracle support notes looking for exactly that, but came up empty.
The reason I thought try with no Broker is Broker will add parameters to your INIT file. So if we created a Pfile from spfile and checked it for those and then removed and created a new spfile. The the SQL
switchover attempt could be tried.
My notes on that are here :
But broker has to be removed because you cannot mix SQL command with broker command or the two configures get out of sync and cause issues.
"properties are inconsistent between the Data Guard configuration file or database"
Edited by: mseberg on Jul 23, 2012 11:00 AM
I created a tar with oracle on Monday, they could not figure out why. but I finally figured out how.
In listener file, added : INBOUND_CONNECT_TIMEOUT_LISTENER = 120
Fixed the issue.
Bingo. Hope this can help others next time around.