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 : 24-07-2017
ORA-16622

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-07706 : error in archive text: need disk file name
  • ora-12815 : value for INSTANCES must be greater than 0
  • ora-02052 : remote transaction failure at string
  • ora-09805 : conversion of category number to string failed.
  • ora-02320 : failure in creating storage table for nested table column string
  • ora-28302 : User does not exist in the LDAP directory service.
  • ora-29393 : user string does not exist or is not logged on
  • ora-15094 : attempted to write to file opened in read only mode
  • ora-30120 : 'string' is not a legal oracle number for 'string'
  • ora-25154 : column part of USING clause cannot have qualifier
  • ora-09316 : szrpc: unable to verify password for role
  • ora-01596 : cannot specify system in string parameter
  • ora-29525 : referenced name is too long: 'string'
  • ora-09938 : Save of signal handlers failed.
  • ora-03214 : File Size specified is smaller than minimum required
  • ora-31696 : unable to export/import string using client specified string method
  • ora-36914 : (XSAGDNGL50) In AGGMAP workspace object, LOAD_STATUS valueset workspace object contains both a child and it's ancestor.
  • ora-10269 : Don't do coalesces of free space in SMON
  • ora-30178 : duplicate flag used in a format specification
  • ora-01942 : IDENTIFIED BY and EXTERNALLY cannot both be specified
  • ora-02822 : Invalid block offset
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-32120 : Buffer size is less than amount specified
  • ora-13459 : GeoRaster metadata SRS error
  • ora-27212 : some entrypoints in Media Management Library are missing
  • ora-25002 : cannot create INSTEAD OF triggers on tables
  • ora-06707 : TLI Driver: connection failed
  • ora-34514 : (MXOPERR) You cannot string string data in the expression that begins with 'string'.
  • ora-37114 : OLAP API bootstrap error: (string)
  • ora-13615 : The task or object string is greater than the maximum allowable length of 30 characters.
  • 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.