ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 4276 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-36980: (XSRELGID02) Variable workspace object must have a numeric data type.
ORA-00162: external dbid length string is greater than maximum (string)
NNC-00003: error opening stream string
ORA-24411: Session pool already exists.
ORA-13863: Statistics aggregation for service(module/action) string is not enabled
PLW-07204: conversion away from column type may result in sub-optimal query plan
QSM-01113: HAVING clause of mv, string, is more restrictive than query
ORA-12711: this CREATE CONTROLFILE character set is not allowed
QSM-01002: no query rewrite when OPTIMIZER_MODE is rule based
ORA-22617: error while accessing the image handle collection
ORA-13335: LRS measure information not defined
PCC-02384: Missing array length specifier
Oracle Errors 
