Thursday, January 24, 2013

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


Cause : DB_UNIQUE_NAME is not in the Data Guard Configuration. We can check current DB_UNIQUE_NAME in the configuration.
SQL> show parameter log_archive_config;

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.
Action:
Amend the   DB_UNIQUE_NAME in LOG_ARCHIVE_CONFIG parameter . Below example shows  physical standby database as ORCL_STBY
1) ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(ORCL, ORCL_STBY)';
2)  Re – enable Standby Archive Location Parameter;
ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE= ORCL_STBY  REOPEN=5 NOAFFIRM  ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME= ORCL_STBY;

ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_3=ENABLE;
3) Check that status of the  standby destination.
SQL>  select dest_name,status,error from v$archive_dest_status where dest_id=2;


Cheers !!!

3 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. This fixed my issue. Thanks and keep up!

    ReplyDelete
  3. Thanks! you helped me solve an annoying issue on an OS Patch/restart

    ReplyDelete