Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 5172 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-31521: CDC subscription string already subscribes to publication ID string column string
ORA-12715: invalid character set specified
NNO-00071: cannot construct cache checkpoint file name
ORA-02816: Unable to kill a process
ORA-29399: user string does not have privilege to switch to consumer group string
ORA-22879: cannot use the LOB INDEX clause for partitioned tables
PCC-02407: Object and REF types do not match
ORA-25245: agent name cannot be specified if address is a single-consumer queue or an exception queue
ORA-09770: pws_look_up: translation failure.
NPL-00300: maximum ASN.1 element nesting depth string exceeded on read
NNL-00555: Displays meta data statistics
ORA-28169: unsupported certificate type
Oracle Errors 
