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 : 28-05-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-16536 : unknown object type
  • ora-14251 : Specified subpartition does not exist
  • ora-09746 : smscre: shared memory attach address incorrect.
  • ora-09799 : File label retrieval failed.
  • ora-39776 : fatal Direct Path API error loading table string
  • ora-14270 : table is not partitioned by Range or Hash or List method
  • ora-23495 : serial propagation can not be used for "string"
  • ora-13262 : geometry column string does not exist in table string
  • ora-24347 : Warning of a NULL column in an aggregate function
  • ora-29974 : Internal event for PL/SQL debugging
  • ora-04086 : trigger description too long, move comments into triggering code
  • ora-22309 : attribute with name "string" already exists
  • ora-12225 : TNS:destination host unreachable
  • ora-31669 : Worker process string violated startup protocol.
  • ora-30944 : Error during rollback for XML schema 'string' table string column 'string'
  • ora-38859 : instance string (thread string) is not ready to be disabled
  • ora-13008 : the specified date format has an invalid component
  • ora-30033 : Undo tablespace cannot be specified as default user tablespace
  • ora-07235 : slemcw: fwrite error.
  • ora-32503 : Mapping SGA from file failed
  • ora-02802 : No idle servers available in parallel mode
  • ora-25199 : partitioning key of a index-organized table must be a subset of the primary key
  • ora-31670 : Username argument must be specified and non-null.
  • ora-10690 : Set shadow process core file dump type (Unix only)
  • ora-16084 : an apply engine is already running
  • ora-28368 : cannot auto-create wallet
  • ora-13234 : failed to access R-tree-index table [string]
  • ora-27008 : function called with invalid file structure
  • ora-34487 : (MXMAINT08) You cannot string values of non-unique concat dimension workspace object.
  • ora-29382 : validation of pending area failed
  • 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.