db_unique_name

Oracle 11.1.0:

Oracle 10.2.0:

Oracle 10.1.0:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: Some other ASM instance used the lock name space in a conflicting mode.

Action: Shut down the other instance or start up in compatible mode. Alternatively, set the DB_UNIQUE_NAME initialization parameter to avoid the conflict.//

ORA-16047: DGID mismatch between destination setting and standby

Cause: The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination.

Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination.

ORA-16052: DB_UNIQUE_NAME attribute is required

Cause: The DB_UNIQUE_NAME attribute is required when DG_CONFIG is enabled.

Action: Use the DB_UNIQUE_NAME attribute to specify a valid Data Guard Name for the destination. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view.

ORA-16053: DB_UNIQUE_NAME %s is not in the Data Guard Configuration

Cause: The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.

Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance.

ORA-16184: DB_UNIQUE_NAME %s hashes to the same value as DB_UNIQUE_NAME %s

Cause: The internal hash value generated for one DB_UNIQUE_NAME collided with the hash value of another DB_UNIQUE_NAME.

Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different value.

ORA-16194: Modifying DB_UNIQUE_NAME requires SID='*' qualifier

Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID='*' qualifier is required.

Action: Re-enter the command using the SID='*' qualifier.

ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined

Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined.

Action: Explicitly define a valid DB_UNIQUE_NAME.

ORA-16197: Invalid DB_UNIQUE_NAME parameter specification

Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The DB_UNIQUE_NAME parameter has a maximum length of 30 characters and the only characters allowed are alpha-numeric characters and "_", "$" and "#".

Action: Check the documentation and re-enter the parameter.

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: 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.

ORA-16642: db_unique_name mismatch

Cause: The expected db_unique_name value did not match the actual db_unique_name value for the database that the broker contacted using the connect identifier that was associated with that database.

Action: Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database that the broker expects to find via that connect identifier matches the actual db_unique_name for that database.

ORA-16651: requirements not met for enabling Fast-Start Failover

Cause: The attempt to enable Fast-Start Failover could not be completed because one or more requirements have not been met: - The Data Guard configuration must be in MaxAvailability protection mode. - The LogXptMode property for both the primary database and the Fast-Start Failover target standby database must be SYNC. - The primary database and the Fast-Start Failover target standby database must both have flashback enabled. - No valid target standby database was specified in the primary database's FastStartFailoverTarget property prior to the attempt to enable Fast-Start Failover, and more than one standby database exists in the Data Guard configuration.

Action: Retry the attempted command after correcting the issue: - Set the Data Guard configuration to MaxAvailability protection mode. - Ensure that the LogXptMode property for both the primary database and the Fast-Start Failover target standby database are SYNC. - Ensure that both the primary database and the Fast-Start Failover target standby database have flashback enabled. - Set the primary database's FastStartFailoverTarget property to the db_unique_name value of the desired target standby database add the desired target standby database's FastStartFailoverTarget property to the db_unique_name value of the primary database.

ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full

Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add a new DB_UNIQUE_NAME to the list.

Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.

ORA-16745: unable to add DB_UNIQUE_NAME %s into the DG_CONFIG list because it is full

Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add the specified DB_UNIQUE_NAME to the list.

Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.

ORA-16784: the database name in Dependency property is incorrect

Cause: The database name, which should be the value of the DB_UNIQUE_NAME initialization parameter, specified in property Dependency is incorrect.

Action: Reset the Dependency property to the correct name of the database.

ORA-16814: incorrect redo transport setting for AlternateLocation for standby database

Cause: The Data Guard broker detected that an incorrect redo transport setting for a standby database's AlternateLocation property. The incorrect setting could be one of the following: one of the following: (1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting; (2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting; (3) the AlternateLocation property does not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute; (4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE; (5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error.

Action: Reenable the primary database to clear the error.

ORA-16815: incorrect redo transport setting for AlternateLocation for standby database \"%s\"

Cause: The Data Guard broker detected that the redo transport setting for the standby database regarding its AlternateLocation property value is incorrect. The incorrect setting could be one of the following: (1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting; (2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting; (3) the AlternateLocation property does not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute; (4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE; (5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error.

Action: Reenable the primary database to clear the error.

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ db_unique_name ] on the Oracle FAQ.