Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 4943 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-31010: XML element index string exceeds maximum insertion index string
ORA-32826: Messaging Gateway agent has already been started
ORA-01213: MAXINSTANCES may not exceed string
ORA-26080: file "string" is not part of table string.string partition string
ORA-13220: failed to compare tile with the geometry
ORA-00054: resource busy and acquire with NOWAIT specified
ORA-07234: slemcw: fseek error.
ORA-27548: Unable to unprepare IPC buffer
ORA-31403: change table string already contains a column string
LFI-00150: Error on creating hash table in function string
ORA-00001: unique constraint (string.string) violated
ORA-02209: invalid MAXTRANS option value
Oracle Errors 
