转 How to Resolve ORA-16009: remote archive log destination must be a STANDBY

###sample

A primary

B STANDBY

C STANDBY

 

问题A 库一直报错 ORA-16009: remote archive log destination must be a STANDBY 

 

经过检查，B库的容灾库归档指向有问题。导致一直向着A库写归档日志。

SQL> show parameter log_archive_dest_2

NAME TYPE
------------------------------------ --------------------------------
VALUE
------------------------------
log_archive_dest_2 string
SERVICE=db lgwr async noaffirm reopen=60 valid_for=(standby_logfiles,standby_role) db_unique_name=db

SQL> show parameter log_archive_dest_state_2

NAME TYPE
------------------------------------ --------------------------------
VALUE
------------------------------
log_archive_dest_state_2 string
ENABLE

 

解决方法：

B库：

SQL> alter system set log_archive_dest_state_2=defer scope=both sid='*';

System altered.

 

###

http://logic.edchen.org/how-to-resolve-ora-16009-remote-archive-log-destination-must-be-a-standby-database/

POSTED MARCH 22, 2015 ED CHEN

Saw an error in the alert log.
... Sat Mar 21 10:28:48 2015
Errors in file /oracle/admin/ORCL/bdump/orcl_arc0_9548203.trc:
ORA-16009: remote archive log destination must be a STANDBY database
There may be a misunderstanding between the primary and the standby databases, we could have two primary databases with the same database name in the same time.

I know that’s essentially wrong to have two primary databases in the same data guard environment. Somehow, you may activate the standby database to the primary role for a short time for some reasons.

The workaround is to defer the transportation on both sides.
SQL> alter system set log_archive_dest_state_2=defer scope=memory;

ACTIVATE STANDBY DATABASELOG_ARCHIVE_DEST_STATE_2ORA-16009ORACLE - DATABASE - DATA GUARD

Post navigation

⟵How to Hide an HTML Element after a Few Seconds