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 : 30-04-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-28120 : driving context already exists
  • ora-13604 : The specified parameter string cannot be fetched as a SQL table.
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-10668 : Inject Evil Identifiers
  • ora-39122 : Unprivileged users may not perform string remappings.
  • ora-25101 : duplicate REBUILD option specification
  • ora-13786 : missing SQL text of statement object "string" for tuning task "string"
  • ora-16756 : resource guard could not open standby database read-only
  • ora-12597 : TNS:connect descriptor already in use
  • ora-25314 : a commit-time queue table cannot be migrated to 8.0
  • ora-01049 : Bind by name is not spupportted in streamed RPC
  • ora-10633 : No space found in the segment
  • ora-08432 : raw data has invalid floating point data
  • ora-23413 : table "string"."string" does not have a materialized view log
  • ora-36174 : (XSMXAGGR23) workspace object must be either a VARIABLE, a RELATION or a FORMULA.
  • ora-00373 : online log version string incompatible with ORACLE version string
  • ora-38435 : missing elementary attribute value or invalid name-value pairs
  • ora-30012 : undo tablespace 'string' does not exist or of wrong type
  • ora-25187 : specified exceptions table form incorrect
  • ora-01774 : Dump undo option specified more than once
  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-39217 : object type "string"."string" typeid mismatch
  • ora-30645 : reject limit out of range
  • ora-16080 : invalid LogMiner session string for APPLY
  • ora-01924 : role 'string' not granted or does not exist
  • ora-06435 : ssaio: write error, unable to write requested block to database file.
  • ora-25301 : Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2
  • ora-13267 : error reading data from layer table string
  • ora-02067 : transaction or savepoint rollback required
  • ora-27121 : unable to determine size of shared memory segment
  • 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.