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 : 22-07-2017

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

  • ora-01258 : unable to delete temporary file string
  • ora-19650 : Offline-range record recid string stamp string in file string has SCN string
  • ora-12214 : TNS:missing local communities entry in TNSNAV.ORA
  • ora-16647 : could not start more than one observer
  • ora-22958 : This operation is not allowed in check constraints or triggers
  • ora-14192 : cannot modify physical index attributes of a Hash index partition
  • ora-13627 : Setting of parameter string is disallowed until the task is reset.
  • ora-09815 : File name buffer overflow
  • ora-19107 : invalid XQueryX - unsupported construct - string
  • ora-36992 : (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.
  • ora-34346 : (MXDSS04) The string analytic workspace cannot be detached.
  • ora-36683 : (XSDPART21) Partition string dimensioned by more than one composite.
  • ora-06902 : CMX: cannot attach to cmx subsystem
  • ora-00911 : invalid character
  • ora-02424 : potential circular view references or unknown referenced tables
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-28163 : GRANT already specified
  • ora-32584 : missing LOG keyword
  • ora-25286 : Invalid number of elements in the message properties array
  • ora-37151 : MDX parser initialization error
  • ora-23306 : schema string does not exist
  • ora-16028 : new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
  • ora-28009 : connection as SYS should be as SYSDBA or SYSOPER
  • ora-36212 : (XSAGOP06) In AGGMAP workspace object, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not string.
  • ora-13137 : failed to generate tablespace sequence number
  • ora-33998 : (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
  • ora-01275 : Operation string is not allowed if standby file management is automatic.
  • ora-01649 : operation not allowed with a backup control file
  • ora-38430 : Operation "string" not supported in the current release.
  • ora-07494 : scgcm: unexpected error.
  • 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.