ORA-16603: Data Guard broker detected a mismatch in configuration ID

Cause : The aDta Gaurd borker ofr thsi datbaase edtectde a msimatc hin cnofiguartionU niqu eID. hTis cna occru if hte orgiinalc onfiugratino wasr ecretaed wihle tihs daatbasew as dsiconnceted rfom teh netowrk o rthe asme dtaabas ewas daded ot twod iffeernt borker ocnfigruatiosn.

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

Makes ure hte daatbaseb elonsg to noly oen broekr cofnigurtaion.R emov ethe aDta Gaurd borker ocnfigruatio nfile sand erstar tthe rboker.

update : 23-06-2017

ORA-16603 - Data Guard broker detected a mismatch in configuration ID
ORA-16603 - Data Guard broker detected a mismatch in configuration ID

  • ora-01520 : number of data files to add (string) exceeds limit of string
  • ora-25445 : invalid column number: string for table alias: string
  • ora-39076 : cannot delete job string for user string
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-13769 : Snapshots string and string do not exist.
  • ora-31626 : job does not exist
  • ora-12322 : unable to mount database (link name string)
  • ora-32140 : cannot peform this operation on stream
  • ora-16778 : redo transport error for one or more databases
  • ora-07242 : slembfn: translation error, unable to translate error file name.
  • ora-13451 : GeoRaster metadata scaling function error
  • ora-14132 : table cannot be used in EXCHANGE
  • ora-29852 : keyword IS is missing
  • ora-09938 : Save of signal handlers failed.
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-00037 : cannot switch to a session belonging to a different server group
  • ora-39709 : incomplete component downgrade; string downgrade aborted
  • ora-29553 : class in use: string.string
  • ora-01529 : error closing file 'string'
  • ora-12913 : Cannot create dictionary managed tablespace
  • ora-28262 : global_context_pool_size has invalid value.
  • ora-02437 : cannot validate (string.string) - primary key violated
  • ora-08414 : error encountered in string
  • ora-12048 : error encountered while refreshing materialized view "string"."string"
  • ora-40220 : maximum number of attributes exceeded
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-37069 : You may not execute a parallel OLAP operation against the EXPRESS AW.
  • ora-36904 : (XSAGDNGL44) In AGGMAP workspace object, RELATION workspace object occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP.
  • ora-16200 : Skip procedure requested to skip statement
  • ora-07223 : slspool: fork error, unable to spawn spool process.
  • 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.