ORA-16598: Data Guard broker detected a mismatch in configuration

Cause : The Data Guard broker detected a significant mismatch in configuration validation between two or more databases in the broker configuration. This can occur when the primary database has a stale broker configuration file.

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

Contact Oracle Support Services.

update : 29-04-2017

ORA-16598 - Data Guard broker detected a mismatch in configuration
ORA-16598 - Data Guard broker detected a mismatch in configuration

  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-10973 : backout evet for 2619509
  • ora-28363 : buffer provided not large enough for output
  • ora-01143 : cannot disable media recovery - file string needs media recovery
  • ora-24336 : invalid result set descriptor
  • ora-36972 : (XSRELTBL13) Relation workspace object must be dimensioned by workspace object.
  • ora-07235 : slemcw: fwrite error.
  • ora-02224 : EXECUTE privilege not allowed for tables
  • ora-32303 : mviews with user-defined types cannot reference multiple master sites
  • ora-28505 : cannot get non-Oracle system capabilities from string
  • ora-13421 : null or invalid cell value
  • ora-01495 : specified chain row table not found
  • ora-22309 : attribute with name "string" already exists
  • ora-36902 : (XSAGDNGL43) In AGGMAP workspace object, the MODEL workspace object is not a model over a base dimension of the AGGMAP.
  • ora-16520 : unable to allocate resource id
  • ora-17619 : max number of processes using I/O slaves in a instance reached
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-12532 : TNS:invalid argument
  • ora-31209 : DBMS_LDAP: PL/SQL - LDAP count_entry error.
  • ora-07753 : slemcf: fseek before write failure
  • ora-12060 : shape of prebuilt table does not match definition query
  • ora-16130 : supplemental log information is missing from log stream
  • ora-15062 : ASM disk is globally closed
  • ora-37113 : OLAP API initialization error: (string)
  • ora-06746 : TLI Driver: cannot alloc t_call
  • ora-13041 : failed to compare tile with element string.string.string
  • ora-12345 : user string lacks CREATE SESSION privilege in database link (linkname string)
  • ora-02056 : 2PC: string: bad two-phase command number string from string
  • ora-25208 : RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE
  • ora-28046 : Password change for SYS disallowed
  • 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.