ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 4648 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-14639: SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table/partition
ORA-24272: initialization value must be either F or T
NNL-01059: Region data reload check failures: number
ORA-06540: PL/SQL: compilation error
ORA-07244: ssfccf: create file failed, file size limit reached.
ORA-00068: invalid value string for parameter string, must be between string and string
LFI-00120: Unable to parse root filename string.
ORA-07584: spdcr: invalid value for ORA_sid_(proc_)PQL$_item
ORA-28669: bitmap index can not be created on an IOT with no mapping table
NCR-03021: NCRO: Reset the in-band line
TNS-12235: TNS:Failure to redirect to destination
DRG-11216: length of datastore data exceeds limit
Oracle Errors 
