ORA-16622: two or more broker database objects resolve to one physical database

Cause : The Data Guard broker determined that there were multiple database objects referring to the same physical database.

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

Examine the details of all databases in the broker configuration and verify that there are not two or more databases that indicate the same physical database. If you detect this situation, remove and readd the erroneously defined database(s) to resolve the ambiguity.

update : 20-09-2017

ORA-16622 - two or more broker database objects resolve to one physical database
ORA-16622 - two or more broker database objects resolve to one physical database

  • ora-19121 : duplicate attribute definition - string
  • ora-22313 : cannot use two versions of the same type "string"
  • ora-04940 : unsupported optimization of Oracle binary, check alert log for more info
  • ora-33046 : (XSAGDNGL22) In AGGMAP workspace object, you can specify only one SCREENBY clause.
  • ora-22870 : ALTER TYPE with REPLACE option a non-object type
  • ora-30505 : system triggers should not reference a column in a WHEN clause
  • ora-24309 : already connected to a server
  • ora-37082 : Invalid percent
  • ora-31157 : Invalid Content-Type charset
  • ora-29294 : A data error occurred during compression or uncompression.
  • ora-16039 : RFS request version mismatch
  • ora-28045 : SSL authentication between database and OID failed
  • ora-07562 : sldext: extension must be 3 characters
  • ora-39753 : unsupported use of subquery in PARTITIONED OUTER JOIN condition
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-23398 : user name "string" at database link "string" does not match local user name "string"
  • ora-28233 : double encryption not supported
  • ora-29928 : duplicate default selectivity specified
  • ora-24805 : LOB type mismatch
  • ora-30977 : invalid Value Index option for XML Index
  • ora-36886 : (XSSRF05) Error rewritting OLAP DML expression. Rewritten expression is greater than number bytes
  • ora-19683 : real and backup blocksize of file string are unequal
  • ora-01653 : unable to extend table string.string by string in tablespace string
  • ora-12223 : TNS:internal limit restriction exceeded
  • ora-07631 : smcacx: $EXPREG failure
  • ora-23463 : flavor incompatible with object "string"."string"
  • ora-28354 : wallet already open
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-08117 : Index Organized Table operation released its block pin
  • ora-28537 : no more result sets
  • 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.