ORA-16804: one or more configuration properties in metadata have invalid values

Cause : Data Guard broker health check detected that one or more configuration properties in the broker's configuration metadata have invalid values. The property values have been changed while broker management of the database is disabled.

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

Check Data Guard broker log for more details on which properties have invalid values and reset them through the Data Guard broker.

update : 26-07-2017

ORA-16804 - one or more configuration properties in metadata have invalid values
ORA-16804 - one or more configuration properties in metadata have invalid values

  • ora-33215 : (CINSERT07) You cannot add session-only values to the workspace object dimension.
  • ora-25266 : didnt try to dequeue by message id. with the signature
  • ora-16812 : log apply service not running on apply instance recorded by the broker
  • ora-02332 : cannot create index on attributes of this column
  • ora-10943 : trace name context forever
  • ora-23542 : dependent object "string"."string" already registered
  • ora-12229 : TNS:Interchange has no more free connections
  • ora-09275 : CONNECT INTERNAL is not a valid DBA connection
  • ora-26671 : maximum number of STREAMS processes exceeded
  • ora-22309 : attribute with name "string" already exists
  • ora-01126 : database must be mounted in this instance and not open in any instance
  • ora-23363 : mismatch of mview base table "string" at master and mview site
  • ora-16030 : session specific change requires a LOG_ARCHIVE_DEST_n destination
  • ora-01519 : error while processing file 'string' near line string
  • ora-02296 : cannot enable (string.string) - null values found
  • ora-01924 : role 'string' not granted or does not exist
  • ora-33052 : (XSAGDNGL25) AGGMAP workspace object is a dimensioned AGGMAP; it can only be used to aggregate like-dimensioned variables.
  • ora-12487 : clearance labels not between DBHIGH and DBLOW
  • ora-16628 : the broker protection mode is inconsistent with the database setting
  • ora-24085 : operation failed, queue string is invalid
  • ora-26007 : invalid value for SETID or OID column
  • ora-08261 : ora_addr: cannot find name in nameserver
  • ora-24239 : object could not be invalidated
  • ora-19508 : failed to delete file "string"
  • ora-25952 : join index must only contain inner equi-joins
  • ora-12704 : character set mismatch
  • ora-25280 : complete sender information not provided to non-repudiate sender
  • ora-27475 : "string.string" must be a string
  • ora-19686 : SPFILE not restored due to string
  • ora-28353 : failed to open wallet
  • 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.