Home » Server Options » Data Guard » DG broker switchover problem (10.2.0.4.0,RHEL 5.4)
DG broker switchover problem [message #485520] Wed, 08 December 2010 12:28 Go to next message
knight
Messages: 111
Registered: January 2009
Senior Member
I am having setup of 2 node 10.2.0.4.0 RAC setup on ASM with Single Instance Physical standby on File System (OS: RHEL 5.4). I configured DG Broker without any major issues. Getting all output of 'show configuration' and all DG related logs are clear. Archives are getting transferred from both Primary nodes.

DGMGRL> show configuration

Configuration
Name: dg_rac
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
livestdby - Primary database
livedg - Physical standby database

Current status for "dg_rac":
SUCCESS


Now I am getting error Error: ORA-16535: CRS is preventing execution of a broker operation.

DGMGRL> switchover to livedg;
Performing switchover NOW, please wait...
Error: ORA-16535: CRS is preventing execution of a broker operation

Oracle Says

Quote:
Cause
A broker operation was underway that required CRS to stop managing the instances of this database, but CRS management could not be stopped on behalf of the broker"s request on

at least some of the instances, so the broker operation was canceled.

Action
Suspend CRS management of this database using SRVCTL STOP DATABASE -D <name> -O NONE. Then reissue the broker request.


But this command is not working as it's given to stop the database.

One more thing, it's nowhere said to stop CRS while performing Switchover / Switchback using DG Broker. When we do Switchover / Switchback we keep open only one of the Primary instance.

Anybody knows regarding this error????(is it bug ???)

is there any documentation / link available to switchover of RAC database using dgmgrl (DG Broker)

[Updated on: Wed, 08 December 2010 12:39] by Moderator

Report message to a moderator

Re: DG broker switchover problem [message #485526 is a reply to message #485520] Wed, 08 December 2010 12:39 Go to previous messageGo to next message
Michel Cadot
Messages: 67295
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Do not confuse code tags with quote one.
Use code tags for code and quote one when you quote something.
See your post now.

ORA-16535: CRS is preventing execution of a broker operation
 *Cause:  A broker operation was underway that required CRS to stop
          managing the instances of this database, but CRS management
          could not be stopped on behalf of the broker's request on at
          least some of the instances, so the broker operation was canceled.
 *Action: Suspend CRS management of this database using
          SRVCTL STOP DATABASE -D <name> -O NONE. Then reissue the
          broker request.


Regards
Michel

[Updated on: Wed, 08 December 2010 12:40]

Report message to a moderator

Re: DG broker switchover problem [message #485614 is a reply to message #485520] Thu, 09 December 2010 01:10 Go to previous messageGo to next message
knight
Messages: 111
Registered: January 2009
Senior Member
michel,

SRVCTL STOP DATABASE -D <name> -O NONE stops the database.

i also stopped crs on one node and then tried switchover but was not successfull and again got error

ORA-16535: CRS is preventing execution of a broker operation

what could be the solution/workaround for this ?




will avoid the confusion regarding tags

Re: DG broker switchover problem [message #485695 is a reply to message #485614] Thu, 09 December 2010 08:53 Go to previous message
BlackSwan
Messages: 26730
Registered: January 2009
Location: SoCal
Senior Member
16535, 00000, "Oracle Restart or Oracle Clusterware prevented completion of broker operation"
// *Cause:  The broker could not complete the operation because Oracle Restart
//          (for single instance databases) or Oracle Clusterware (for RAC
//          databases) could not stop services or instances on this database.
// *Action: Check the Data Guard broker log file for more information and
//          stop the appropriate services or instances using SRVCTL. Then
//          retry the broker operation.
Previous Topic: Error ORA-01078
Next Topic: FAL_SERVER and FAL_CLIENT (merged)
Goto Forum:
  


Current Time: Tue Aug 11 16:58:23 CDT 2020