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-04-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-01924 : role 'string' not granted or does not exist
  • ora-03119 : two-task detected inconsistent datatype specification
  • ora-30183 : invalid field width specifier
  • ora-32586 : multiple specification of a supplemental logging attribute
  • ora-31205 : DBMS_LDAP: PL/SQL - Invalid LDAP Auth method.
  • ora-25185 : index column other than last can not be specified for INCLUDE clause
  • ora-12844 : cluster reconfiguration in progress
  • ora-06527 : External procedure SQLLIB error: string
  • ora-13145 : failed to generate range list
  • ora-28049 : the password has expired
  • ora-19650 : Offline-range record recid string stamp string in file string has SCN string
  • ora-22307 : operation must be on a user-defined type
  • ora-14700 : Object(s) owned by SYS cannot be locked by non-SYS user
  • ora-32004 : obsolete and/or deprecated parameter(s) specified
  • ora-10266 : Trace OSD stack usage
  • ora-12483 : label not in OS system accreditation range
  • ora-38794 : Flashback target time not in current incarnation
  • ora-14260 : incorrect physical attribute specified for this partition
  • ora-31697 : aborting operation at process order number string
  • ora-01279 : db_files too large
  • ora-01687 : specified logging attribute for tablespace 'string' is same as the existing
  • ora-02463 : Duplicate HASH IS option specified
  • ora-02421 : missing or invalid schema authorization identifier
  • ora-37111 : Unable to load the OLAP API sharable library: (string)
  • ora-24233 : argument passed to DBMS_UTILITY.VALIDATE is not legal
  • ora-39110 : error deleting worker processes
  • ora-12477 : greatest lower bound resulted in an invalid OS label
  • ora-13759 : User "string" cannot remove reference "string".
  • ora-12704 : character set mismatch
  • ora-04074 : invalid REFERENCING name
  • 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.