In this post, you’ll learn more about the Oracle ErrorORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration with the details on why you receive this error and the possible solution to fix it.
Oracle Error Description
ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration
Reason for the Error ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration
The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.
How to fix the Error ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration ?
You can fix this error in Oracle by following the below steps
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.