OCI-16053
DB_UNIQUE_NAME string is not in the Data Guard Configuration
Cause
The specified DB_UNIQUE_NAME was not in the Data Guard Configuration. Also, this problem could occur if a non-standby destination was specified with a DB_UNIQUE_NAME attribute that did not match the DB_UNIQUE_NAME initialization parameter for the current instance.
Action
Specify a valid DB_UNIQUE_NAME if the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view.
OCI-16053
DB_UNIQUE_NAME string 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.
OCI-16053
DB_UNIQUE_NAME string 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.
