ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 4566 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-31439: subscription is already active
PCC-00077: Colon usage with numeric label in WHENEVER statement is not ANSI
ORA-37032: (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode.
ORA-13285: Geometry coordinate transformation error
ORA-01989: role 'string' not authorized by operating system
LRM-00117: syntax error at 'string' at the start of input
DRG-12515: cannot specify language for stopwords in a BASIC_STOPLIST
NNO-00272: line string; invalid DIT/DN
NNL-00203: Scheduled shutdown to occur in string
ORA-04002: INCREMENT must be a non-zero integer
ORA-16016: archived log for thread string sequence# string unavailable
ORA-30464: no summaries exist
Oracle Errors 
