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 : 30-04-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-12597 : TNS:connect descriptor already in use
  • ora-39170 : Schema expression string does not correspond to any schemas.
  • ora-06566 : invalid number of rows specified
  • ora-12226 : TNS:operating system resource quota exceeded
  • ora-02051 : another session in same transaction failed
  • ora-19266 : XQ0046 - invalid URI
  • ora-00056 : DDL lock on object 'string.string' is already held in an incompatible mode
  • ora-29348 : You must specify the datafiles to be plugged in
  • ora-04016 : sequence string no longer exists
  • ora-07637 : smsdbp: buffer protect option not specified when sga created
  • ora-38425 : attribute set used for an index object may not be unassigned
  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-14050 : invalid ALTER INDEX MODIFY PARTITION option
  • ora-32125 : Attribute type is not appropriate
  • ora-00070 : command string is not valid
  • ora-07803 : slpdtb: invalid packed decimal nibble
  • ora-26062 : Can not continue from previous errors.
  • ora-00437 : ORACLE feature is not licensed. Contact Oracle Corp. for assistance
  • ora-36271 : (XSCGMDLAGG11) workspace object is not in the dimension list of valueset workspace object.
  • ora-07860 : osnsoi: error setting up interrupt handler
  • ora-23476 : cannot import from string to string
  • ora-02179 : valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-14150 : missing SUBPARTITION keyword
  • ora-06761 : TLI Driver: error sending orderly release
  • ora-00072 : process "string" is not active
  • ora-38780 : Restore point 'string' does not exist.
  • ora-10259 : get error message text from remote using explicit call
  • ora-30385 : specified attribute relationship ('string' determines 'string') exists
  • ora-29865 : indextype is invalid
  • ora-19029 : Cannot convert the given XMLType to the required type
  • 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.