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 : 21-07-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-36610 : (XSLMS00) Unable to locate a message file for OLAP message: value
  • ora-07820 : sspscn: SYS$CRELNM failure
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-12689 : Server Authentication required, but not supported
  • ora-31501 : change source string is not an AutoLog change source
  • ora-13644 : The user "string" is invalid.
  • ora-16639 : specified instance inactive or currently unavailable
  • ora-24130 : table string does not exist
  • ora-01979 : missing or invalid password for role 'string'
  • ora-16552 : an error occurred when generating the CLIENT OPERATION table
  • ora-12652 : String truncated
  • ora-02484 : Invalid _trace_buffers parameter specification (string)
  • ora-01955 : DEFAULT ROLE 'string' not granted to user
  • ora-31643 : unable to close dump file "string"
  • ora-22875 : cannot drop primary key of an object table whose object identifier is primary key based
  • ora-26501 : RepAPI operation failure
  • ora-01256 : error in locking database file string
  • ora-31081 : name not specified for global declaration
  • ora-12217 : TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
  • ora-29394 : session id string and serial# string do not exist
  • ora-01659 : unable to allocate MINEXTENTS beyond string in tablespace string
  • ora-01002 : fetch out of sequence
  • ora-31094 : incompatible SQL type "string" for attribute or element "string"
  • ora-00401 : the value for parameter string is not supported by this release
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-30016 : undo tablespace 'string' is already in use by this instance
  • ora-09807 : Conversion of label from string to binary failed.
  • ora-02246 : missing EVENTS text
  • ora-13826 : empty SQL profile not allowed for create or update SQL profile
  • ora-12590 : TNS:no I/O buffer
  • 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.