ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 4627 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 |
SQL*Loader-00426: count of elements in VARRAY string comes after the data for the varray
ORA-29856: error occurred in the execution of ODCIINDEXDROP routine
ORA-23407: object name string must be shaped like "schema"."object" or "object"
ORA-31029: Cannot bind to unsaved resource
ORA-07242: slembfn: translation error, unable to translate error file name.
SQL*Loader-00279: Only APPEND mode allowed when parallel load specified.
ORA-39121: Table string can't be replaced, data will be skipped. Failing error is: string
ORA-27088: unable to get file status
ORA-02708: osnrntab: connect to host failed, unknown ORACLE_SID
ORA-25004: WHEN clause is not allowed in INSTEAD OF triggers
NNL-00536: set|show requests_enabled [<on|off>] [<server_list>] : enable, disable or show server request processing
ORA-02383: illegal cost factor
Oracle Errors 
