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 : 25-06-2017
ORA-16598

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

  • ora-01673 : data file string has not been identified
  • ora-10979 : trace flags for join index implementation
  • ora-31673 : worker process interrupt for normal exit by master process
  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • ora-01718 : BY ACCESS | SESSION clause not allowed for NOAUDIT
  • ora-06732 : TLI Driver: cannot alloc t_discon
  • ora-31425 : subscription does not exist
  • ora-25962 : join index prevents multitable insert or merge
  • ora-23368 : name string cannot be null or the empty string
  • ora-13369 : invalid value for etype in the 4-digit format
  • ora-02223 : invalid OPTIMAL storage option value
  • ora-02147 : conflicting SHARED/EXCLUSIVE options
  • ora-09360 : Windows 3.1 Two-Task driver unable to allocate context area
  • ora-08311 : sllfop: bad value for maxrecsize
  • ora-09756 : osnpns: no port in the name server.
  • ora-13200 : internal error [string] in spatial indexing.
  • ora-19003 : Missing XML root element name
  • ora-35078 : (QFHEAD05) An EIF extension file header for string is not in the correct format.
  • ora-25295 : Subscriber is not allowed to dequeue buffered messages
  • ora-30001 : trim set should have only one character
  • ora-25351 : transaction is currently in use
  • ora-14039 : partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-31154 : invalid XML document
  • ora-14111 : creation of a GLOBAL partitioned index on clustered tables is not supported
  • ora-07594 : spiip: $GETJPIW failure
  • ora-02061 : lock table specified list of distributed tables
  • ora-21700 : object does not exist or is marked for delete
  • ora-13802 : failed to purge SQL Tuning Base entry from sql$
  • ora-13632 : The user cancelled the current operation.
  • ora-00394 : online log reused while attempting to archive it
  • 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.