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 : 20-09-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-24160 : name string already exists in the name value pair list
  • ora-09811 : Unable to initialize package.
  • ora-06911 : CMX: t_event returns ERROR
  • ora-36835 : (XSLMGEN05) Dimension string.string!string hierarchy string level string is missing a COLUMNNAME property value
  • ora-02264 : name already used by an existing constraint
  • ora-23488 : propagation mode "string" for "string" is not allowed for this operation
  • ora-22291 : Open LOBs exist at transaction commit time
  • ora-23466 : flavor requires missing object "string"."string"
  • ora-23448 : duplicate user parameter value
  • ora-14186 : number of sub-partitions of LOCAL index must equal that of the underlying table
  • ora-12632 : Role fetch failed
  • ora-10387 : parallel query server interrupt (normal)
  • ora-16037 : user requested cancel of managed recovery operation
  • ora-09774 : osnmui: cannot send break message
  • ora-02773 : Invalid maximum client wait time
  • ora-27191 : sbtinfo2 returned error
  • ora-39129 : Object type string not imported. Name conflicts with the master table
  • ora-13791 : cannot resume a tuning task created to tune a single statement
  • ora-13290 : the specified unit is not supported
  • ora-32610 : missing SINGLE REFERENCE or DIMENSION keyword in MODEL clause
  • ora-16001 : database already open for read-only access by another instance
  • ora-01541 : system tablespace cannot be brought offline; shut down if necessary
  • ora-02147 : conflicting SHARED/EXCLUSIVE options
  • ora-28157 : Proxy user 'string' forbidden to set role 'string' for client 'string'
  • ora-09292 : sksabln: unable to build archive file name
  • ora-00469 : CKPT process terminated with error
  • ora-30089 : missing or invalid
  • ora-01598 : rollback segment 'string' is not online
  • ora-32591 : connect string too long
  • ora-29861 : domain index is marked LOADING/FAILED/UNUSABLE
  • 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.