ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 4255 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-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration
NZE-28804: Data source cannot close.
ORA-19713: invalid copy number: string
DGM-16934: You must start instance "string" manually.
IMG-00833: boundary queue size exceeds expected size
DRG-12606: error encountered while parsing COLUMNS list
ORA-13415: invalid or out of scope point specification
ORA-31209: DBMS_LDAP: PL/SQL - LDAP count_entry error.
ORA-09873: TASDEF_OPEN: open error when opening tasdef@.dbf file.
ORA-24002: QUEUE_TABLE string does not exist
ORA-26565: Call to <type>_arg made before calling dbms_defer.call
ORA-28538: result set not found
Oracle Errors 
