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 : 20-09-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-31056 : The document being inserted does not conform to string
  • ora-19601 : output file is string string (string)
  • ora-25267 : didnt specify the signature for a reciever non-repudiable queue
  • ora-24007 : invalid value string, MAX_RETRIES should be non-negative integer
  • ora-19595 : archivelog string already included in backup conversation
  • ora-09361 : Windows 3.1 Two-Task driver unable to lock context area
  • ora-22912 : specified column or attribute is not a nested table type
  • ora-31406 : change source string is referenced by a change set
  • ora-03279 : invalid INSTANCE specified
  • ora-08437 : invalid picture type in picture mask
  • ora-27457 : argument string of job "string.string" has no value
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-16754 : resource guard could not activate standby database
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-15009 : ASM disk "string" does not exist
  • ora-01165 : MAXDATAFILES may not exceed string
  • ora-07599 : spwat: $SCHDWK failure
  • ora-16622 : two or more broker database objects resolve to one physical database
  • ora-36210 : (XSAGOP05R) In AGGMAP workspace object, you can only specify the REMOPERATOR string with the PROPORTIONAL, EVEN, or HEVEN operators, not string.
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-01781 : UNRECOVERABLE cannot be specified without AS SELECT
  • ora-32773 : operation not supported for smallfile tablespace string
  • ora-38496 : Expression Filter index is not in a valid state
  • ora-02723 : osnpui: cannot send break signal
  • ora-19285 : FODC0002 - error retrieving resource
  • ora-24276 : function 'string' output 'string' maximum value exceeded
  • ora-02161 : invalid value for MAXLOGFILES
  • ora-32592 : all columns in log group can not be no log columns
  • ora-14451 : unsupported feature with temporary table
  • 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.