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 : 26-09-2017
ORA-16603

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

  • ora-06815 : TLI Driver: could not link SPX and IPX streams
  • ora-09819 : Number exceeds maximum legal value
  • ora-12043 : invalid CREATE MATERIALIZED VIEW option
  • ora-16140 : standby online logs have not been recovered
  • ora-14084 : you may specify TABLESPACE DEFAULT only for a LOCAL index
  • ora-13016 : specified topology [string] is invalid
  • ora-15105 : missing or invalid FAILGROUP name
  • ora-06547 : RETURNING clause must be used with INSERT, UPDATE, or DELETE statements
  • ora-26017 : global indexes not allowed for direct path load of table partition string
  • ora-16503 : site ID allocation failure
  • ora-06258 : NETNTT: cannot allocate context area
  • ora-32622 : illegal multi-cell reference
  • ora-25128 : No insert/update/delete on table with constraint (string.string) disabled and validated
  • ora-26529 : local store callback term phase failed for 'string.string'
  • ora-01346 : LogMiner processed redo beyond specified reset log scn
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-27165 : tried to join thread that does not exist
  • ora-24335 : cannot support more than 1000 columns
  • ora-00033 : current session has empty migration password
  • ora-16577 : corruption detected in Data Guard configuration file
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-00096 : invalid value string for parameter string, must be from among string
  • ora-01297 : redo version mismatch between dictionary string and logfiles
  • ora-14282 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-30018 : Create Rollback Segment failed, USN string is out of range
  • ora-02225 : only EXECUTE and DEBUG privileges are valid for procedures
  • ora-29284 : file read error
  • ora-22323 : error table "string"."string" does not exist
  • ora-19711 : cannot use reNormalizeAllFileNames while database is open
  • ora-25301 : Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2
  • 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.