ORA-16053 mongouard master database logs cannot be transmitted to the physical standby Database

A friend configures the DG of the master database and the physical slave database. After the configuration is complete, he finds that there is a slave database which cannot receive the archive logs of the master database.

Logs cannot be transmitted to the slave database normally. Many of them are due to archiving destination configuration problems or network configuration problems.

The process is generally to first view the v $ archive_dest_status view, obtain the summary information, and then view the alert. log file of the master database and slave database.

When viewing the v $ archive_dest_status of a friend's master database, the error message "ARCHIVE Destination 3" is displayed:

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

Check the log_archive_config parameter again. Only the master database and slave database are configured:

Log_archive_config = 'dg _ CONFIG = (primary, standby )'

Add the second slave database to DG_CONFIG, restart the database, and the logs will be transmitted normally.

Alter system set log_archive_config = 'dg _ CONFIG = (primary, standby, standby2) 'scope = spfile;