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 : 27-05-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-13003 : the specified range for a dimension is invalid
  • ora-26518 : push queue synchronization error detected
  • ora-32742 : Hang analysis initialize failed
  • ora-26674 : Column mismatch in 'string.string' (LCR: string type=string; DB: string type=string)
  • ora-00352 : all logs for thread string need to be archived - cannot enable
  • ora-32586 : multiple specification of a supplemental logging attribute
  • ora-19212 : no key columns specified before call to DBMS_XMLSTORE.updateXML()
  • ora-02449 : unique/primary keys in table referenced by foreign keys
  • ora-28263 : Insufficient memory in global context pool
  • ora-13429 : invalid xCoefficients or yCoefficients parameter(s)
  • ora-38718 : Invalid thread number specified in the DUMP FLASHBACK command.
  • ora-23364 : Feature not enabled: Advanced replication
  • ora-01946 : DEFAULT TABLESPACE already specified
  • ora-09981 : skxfqdreg: Error Adding a page to the SDI buffer pool
  • ora-31033 : Requested number of XML children string exceeds maximum string
  • ora-30183 : invalid field width specifier
  • ora-12542 : TNS:address already in use
  • ora-19321 : Could not open HTTP connection to host (string): port (string)
  • ora-39172 : Cannot remap transportable tablespace names with compatibility of string.
  • ora-34481 : (MXMAINT07) You cannot string values of PARTITION TEMPLATE workspace object.
  • ora-16566 : unsupported document type
  • ora-01495 : specified chain row table not found
  • ora-25115 : duplicate BLOCK option specification
  • ora-01023 : Cursor context not found (Invalid cursor number)
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-36992 : (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.
  • ora-06702 : TLI Driver: cannot allocate context area
  • ora-16535 : CRS is preventing execution of a broker operation
  • ora-36261 : (XSAGPARTDEP00) Can not Aggregate PARTITION TEMPLATE %J because the path of aggregation would recursively enter partition %J.
  • ora-39060 : table(s) dropped because of conflict with master 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.