Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 4964 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 |
PCC-02310: formal parameter VARCHARs should be declared as pointers
ORA-00365: the specified log is not the correct next log
DRG-12515: cannot specify language for stopwords in a BASIC_STOPLIST
ORA-00348: single-process redo failure. Must abort instance
QSM-02051: subquery using the NOT EXISTS clause in mv
ORA-32107: internal OCI memory allocation failure
TNS-00137: Failed to get TNS error message file entry
PCC-02018: found end-of-file while scanning comment
RMAN-06092: error while looking up backup piece
DRG-11304: function-based indexes are not supported by this indextype
NNL-00020: warning: no TNSNAMES.ORA file and no preferred name servers in SQLNET.ORA
ORA-30082: datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
Oracle Errors 
