Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 5058 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: When an instance was started, the DMON process on the
instance failed to access the Data Guard broker
configuration. This can happen if the DG_BROKER_CONFIG_FILE1
and DG_BROKER_CONFIG_FILE2 initialization parameters are not
set up correctly to point to the broker configuration files
shared among all instances.
Action: Set DG_BROKER_CONFIG_FILE1 and
DG_BROKER_CONFIG_FILE2 to the correct file specifications
that point to the broker configuration files shared among
all instances. Bounce the DMON process by setting
DG_BROKER_START initialization parameter to FALSE and then
to TRUE.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-29842: option not supported with the version string of the indextype interface
ORA-14152: invalid number of partitions specified in PARTITIONS clause
ORA-27125: unable to create shared memory segment
NNO-00119: line string: server not authoritative for name "string", data ignored
ORA-27007: failed to open file
TNS-00236: Failed to initialize tracing
DRG-12201: section group string already exists
PCC-02153: Open file: string
RMAN-06520: archived logs required to recover from this backup will not be kept
NNL-00018: warning: could not contact default name server
ORA-39091: unable to determine logical standby and streams status
ORA-02490: missing required file size in RESIZE clause
Oracle Errors 
