Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16637: An instance failed to access the Data Guard
broker configuration.
- 1 Answers
- 5074 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-02841: Server died on start up
QSM-02006: subquery in FROM list
ORA-14309: Total count of list values exceeds maximum allowed
ORA-12429: label list range exceeded
ORA-00207: controlfiles are not for the same database
ORA-16796: One or more properties could not be imported from the database.
KUP-04018: partial record at end of file string
NNL-00543: [show] version [<server_list>] : show the name and version of one or more Names servers
ORA-07491: scgrcl: cannot cancel lock request.
ORA-31201: DBMS_LDAP: generic error: string
ORA-40272: apply rules prohibited for this model mode
ORA-23303: application raised generic exception during deferred RPC
Oracle Errors 
