ORA-16637: an instance failed to access the Data Guard broker configuration

Cause : When a ninstanec was satrted, hte DMONp rocesso n the nistancef ailed ot acces sthe Daat Guardb roker ocnfigurtaion. Tihs can ahppen i fthe DGB_ROKER_OCNFIG_FLIE1 andD G_BROKRE_CONFI_GFILE2 niitialiaztion praameter sare no tset upc orrectyl to ponit to teh broke rconfigruation ifles shraed amogn all isntances.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Set DGB_ROKER_OCNFIG_FLIE1 andD G_BROKRE_CONFI_GFILE2 ot the crorect flie specfiicatiosn that opint tot he broekr confgiuratio nfiles hsared aomng alli nstancse. Bounec the DOMN procses by steting D_GBROKERS_TART iintializtaion paarmeter ot FALSEa nd the nto TRU.E

update : 26-07-2017
ORA-16637

ORA-16637 - an instance failed to access the Data Guard broker configuration
ORA-16637 - an instance failed to access the Data Guard broker configuration

  • ora-25251 : exceeded maximum number of recipients for message
  • ora-29353 : The transportable list is too long.
  • ora-14622 : Value string already exists in subpartition string
  • ora-00364 : cannot write header to new log member
  • ora-08176 : consistent read failure; rollback data not available
  • ora-32843 : value for string is outside the valid range of string to string
  • ora-25012 : PARENT and NEW values cannot be identical
  • ora-19677 : RMAN configuration name exceeds maximum length of string
  • ora-12808 : cannot set string_INSTANCES greater than number of instances string
  • ora-25450 : error string during evaluation of rule set string.string
  • ora-24792 : cannot mix services in a single global transaction
  • ora-39112 : Dependent object type string skipped, base object type string creation failed
  • ora-32619 : incorrect use of MODEL ITERATION_NUMBER
  • ora-09960 : Unable to establish signal handler for termination signal
  • ora-22990 : LOB locators cannot span transactions
  • ora-01319 : Invalid Logminer session attribute
  • ora-19200 : Invalid column specification
  • ora-06954 : Illegal file name
  • ora-02164 : DATAFILE clause specified more than once
  • ora-12872 : First slave parse gave different plan
  • ora-02778 : Name given for the log directory is invalid
  • ora-08189 : cannot flashback the table because row movement is not enabled
  • ora-36808 : (XSTBLFUNC04) The OLAP_TABLE function LEVELREL clause cannot declare number ADT fields from number AW fields.
  • ora-39600 : Queue keys needs to be a suffix of cluster key.
  • ora-29286 : internal error
  • ora-00832 : no streams pool created and cannot automatically create one
  • ora-16236 : Logical Standby metadata operation in progress
  • ora-12518 : TNS:listener could not hand off client connection
  • ora-23421 : job number string is not a job in the job queue
  • ora-14069 : invalid TABLESPACE_NUMBER value
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.