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-09-2017
ORA-16621

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

  • ora-31674 : worker process interrupt for unhandled exception in master process
  • ora-26514 : object 'string.string' not found
  • ora-12021 : materialized view "string"."string" is corrupt
  • ora-12856 : cannot run parallel query on a loopback connection
  • ora-31696 : unable to export/import string using client specified string method
  • ora-13825 : missing SQL statement text for create SQL profile
  • ora-25211 : invalid DELAY specified when using sequence deviation
  • ora-09916 : Required password was not specified.
  • ora-16245 : paging in transaction string, string, string
  • ora-19668 : cannot do full restore of datafile string
  • ora-01690 : sort area size too small
  • ora-22892 : scoped table "string" does not exist in schema "string"
  • ora-12899 : value too large for column string (actual: string, maximum: string)
  • ora-28221 : REPLACE not specified
  • ora-30197 : reserved for future use
  • ora-24343 : user defined callback error
  • ora-27066 : number of buffers in vector I/O exceeds maximum
  • ora-13779 : invalid load option
  • ora-04099 : trigger 'string' is valid but not stored in compiled form
  • ora-19645 : datafile string: incremental-start SCN is prior to creation SCN string
  • ora-13116 : [string]_FACE$ table does not exist
  • ora-10387 : parallel query server interrupt (normal)
  • ora-06302 : IPA: Cannot connect to remote host
  • ora-12566 : TNS:protocol error
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-19252 : XQ0032 - too many declarations for base URI
  • ora-07584 : spdcr: invalid value for ORA_sid_(proc_)PQL$_item
  • ora-14053 : illegal attempt to modify string in string statement
  • ora-00117 : PROTOCOL, ADDRESS or DESCRIPTION must be specified
  • ora-12162 : TNS:net service name is incorrectly specified
  • 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.