Active Data Guard Broker Hangs
(Doc ID 2391641.1)
Last updated on MARCH 14, 2019
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The Active Data Guard broker command hung. The rsm0 process was killed as suggested in Doc ID 2007507.1, however, the Active Data Guard broker command hangs again.
To avoid killing the rsm0 process every time that you need to run a data guard broker command, follow the steps below:
DGMGRL for IBM/AIX RISC System/6000: Version 11.2.0.4.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys
Password:
Connected.
DGMGRL> show configuration;
Error:
Configuration - <broker_config>
Protection Mode: MaxPerformance
Databases:
<PRIMARY> - Primary database
<STANDBY> - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
ORA-01013: user requested cancel of current operation
ORA-06512: at "SYS.DBMS_DRS", line 173
ORA-06512: at line 1
DGM-17017: unable to determine configuration status
DGMGRL> show configuration;
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |