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

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

  • ora-01903 : EVENTS keyword expected
  • ora-13636 : The specified value provided for parameter string is not valid for this advisor.
  • ora-08231 : smscre: unable to attach to SGA
  • ora-12585 : TNS:data truncation
  • ora-00317 : file type string in header is not log file
  • ora-12213 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-16039 : RFS request version mismatch
  • ora-13467 : unsupported GeoRaster metadata specification: string
  • ora-36269 : (XSCGMDLAGG10) 'workspace object' does not exist or is not a dimension.
  • ora-12413 : labels do not belong to the same policy
  • ora-01117 : adding file 'string' with illegal block size: string; limit is string
  • ora-30002 : SYS_CONNECT_BY_PATH function is not allowed here
  • ora-16557 : the database is already in use
  • ora-06407 : NETCMN: unable to set up break handling environment
  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-38782 : cannot flashback database to non-guaranteed restore point 'string'
  • ora-04930 : open sequence number failed or initial state is valid
  • ora-24049 : invalid agent name string, names with AQ$_ prefix are not valid
  • ora-12324 : cannot use the ROM: link type on a private database link
  • ora-12317 : logon to database (link name string) denied
  • ora-00830 : cannot set statistics_level to BASIC with auto-tune SGA enabled
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-10243 : simulated error for test string of K2GTAB latch cleanup
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-00450 : background process 'string' did not start
  • ora-30931 : Element 'string' cannot contain mixed text
  • ora-09741 : spwat: error waiting for a post.
  • ora-04069 : cannot drop or replace a library with table dependents
  • ora-29257 : host string unknown
  • ora-16618 : response document of size "string" bytes is too large
  • 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.