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 : 24-04-2017

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-19581 : no files have been named
  • ora-24146 : rule string.string already exists
  • ora-09204 : sfotf: error opening temporary file
  • ora-22872 : OID INDEX clause not allowed on tables with primary key based object identifiers
  • ora-13271 : error allocating memory for geometry object
  • ora-17508 : I/O request buffer ptr is not alligned
  • ora-32612 : invalid use of FOR loop
  • ora-25532 : MTTR specified is too large: string
  • ora-12992 : cannot drop parent key column
  • ora-01781 : UNRECOVERABLE cannot be specified without AS SELECT
  • ora-31033 : Requested number of XML children string exceeds maximum string
  • ora-14183 : TABLESPACE DEFAULT can be specified only for Composite LOCAL index
  • ora-23468 : missing string string
  • ora-09817 : Write to audit file failed.
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-37060 : (XSMCSESS08) number is not a valid custom member in dimension workspace object.
  • ora-19228 : XP0008 - undeclared identifier: prefix 'string' local-name 'string'
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-12052 : cannot fast refresh materialized view string.string
  • ora-10668 : Inject Evil Identifiers
  • ora-32158 : Invalid type passed
  • ora-29931 : specified association does not exist
  • ora-38774 : cannot disable media recovery - flashback database is enabled
  • ora-16797 : database is not using a server parameter file
  • ora-40208 : duplicate or multiple algorithm settings for function string
  • ora-00250 : archiver not started
  • ora-27414 : Invalid BY value type
  • ora-32631 : illegal use of objects in MODEL
  • ora-32311 : materialized view definition query selects an unsupported user-defined type
  • ora-23319 : parameter value string is not appropriate
  • 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.