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 : 23-06-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-27163 : out of memory
  • ora-19713 : invalid copy number: string
  • ora-01195 : online backup of file string needs more recovery to be consistent
  • ora-32774 : more than one file was specified for bigfile tablespace string
  • ora-13638 : The user interrupted the current operation.
  • ora-29746 : Cluster Synchronization Service is being shut down.
  • ora-26055 : Invalid buffer specified for direct path unload
  • ora-13115 : [string]_EDGE$ table does not exist
  • ora-03203 : concurrent update activity makes space analysis impossible
  • ora-16723 : setting AlternateLocation property conflicts with the redo transport setting
  • ora-26742 : Maximum number of ignored transactions exceeded
  • ora-19236 : XQ0016 - module declaration or import not supported
  • ora-30681 : improper value for argument EXTENSIONS_CMD_SET
  • ora-36982 : (XSRELGID03) The grouping variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object that have more than one value in status.
  • ora-06519 : active autonomous transaction detected and rolled back
  • ora-13226 : interface not supported without a spatial index
  • ora-13519 : Database id (string) exists in the workload repository
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • ora-12724 : regular expression corrupt
  • ora-08195 : Flashback Table operation is not supported on partitions
  • ora-23533 : object "string"."string" can not be cached
  • ora-06435 : ssaio: write error, unable to write requested block to database file.
  • ora-19659 : incremental restore would advance file string past resetlogs
  • ora-34841 : (OPCREATE02) The string option must be declared with the READONLY attribute.
  • ora-22875 : cannot drop primary key of an object table whose object identifier is primary key based
  • ora-07841 : sllfop: SYS$OPEN failure
  • ora-29272 : initialization failed
  • ora-29262 : bad URL
  • ora-12162 : TNS:net service name is incorrectly specified
  • ora-31437 : duplicate change set string
  • 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.