ORA-16621: database name for ADD DATABASE must be unique

Cause : An attempt was made to add a database to the broker configuration that already includes a database with the specified name. The database names must be unique.

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

Verify that you have specified a unique name for the new database you wish to add. This can be done by checking that there is no database with the same name. Also note that the database name must match the DB_UNIQUE_NAME initialization parameter of the database.

update : 26-05-2017
ORA-16621

ORA-16621 - database name for ADD DATABASE must be unique
ORA-16621 - database name for ADD DATABASE must be unique

  • ora-31018 : Error deleting XML document
  • ora-31640 : unable to open dump file "string" for read
  • ora-27198 : skgfpvl: sbtpcvalidate returned error
  • ora-12662 : proxy ticket retrieval failed
  • ora-01016 : This function can be called only after a fetch
  • ora-01177 : data file does not match dictionary - probably old incarnation
  • ora-12450 : LOB datatype disabled in LBAC initialization file
  • ora-23355 : object string.string does not exist or is invalid at master site
  • ora-01987 : client os username is too long
  • ora-30066 : test support - drop rollback segment wait
  • ora-02706 : osnshs: host name too long
  • ora-00487 : CTWR process terminated with error
  • ora-28200 : IDENTIFIED USING already specified
  • ora-25125 : BUFFER_POOL storage option not allowed
  • ora-27089 : unable to release advisory lock
  • ora-15124 : ASM file name 'string' contains an invalid alias name
  • ora-02057 : 2PC: string: bad two-phase recovery state number string from string
  • ora-16758 : the specified apply instance is not running
  • ora-12071 : definition query of "string"."string" is invalid for offline instantiation
  • ora-23427 : deferred purge queue argument string out of range
  • ora-09945 : Unable to initialize the audit trail file
  • ora-24415 : Missing or null username.
  • ora-07824 : sspain: $SETIMR failure
  • ora-27548 : Unable to unprepare IPC buffer
  • ora-38777 : database must not be started in any other instance.
  • ora-06106 : NETTCP: socket creation failure
  • ora-25328 : %s argument size string is smaller than array size
  • ora-12921 : database is not in force logging mode
  • ora-12560 : TNS:protocol adapter error
  • ora-32588 : supplemental logging attribute string exists
  • 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.