ORA-16009: 远程归档日志目标必须为备用数据库

安装oracle10g dataguard for windows 平台,在做switchover时,
归档日志传送不过去,通过查询日志
在alert_orcl.log 日志中会出现以下错误内容
Thu Nov 27 10:19:12 2008Redo Shipping Client Connected as PUBLIC-- Connected User is ValidRFS[2]: Assigned to RFS process 1292RFS[2]: Database mount ID mismatch [0x4781d95f:0x47823be1]RFS[2]: Client instance is standby database instead of primaryRFS[2]: Not using real application clustersThu Nov 27 10:19:12 2008Errors in file d:\oracle\product\10.2.0\admin\orcl\udump\orcl_rfs_1292.trc:ORA-16009: 远程归档日志目标必须为备用数据库通过查询metalink

* fact: Oracle Server - Enterprise Edition 9
* fact: Data Guard (DATAGUARD)
* symptom: Errors appears in alert.log on primary database
* symptom: RFS: Destination database mount ID mismatch
* symptom: RFS: client instance is standby database instead of primary
* symptom: RFS: Not using real application clusters
* symptom: RFS: Possible network disconnect with primary database
* symptom: Errors appear in alert.log on standby database
* symptom: ARC0: Error 16009 Creating archive log file to 'ORCL'
* symptom: ORA-16009: remote archive log destination must be a STANDBY database
* symptom: LOG_ARCHIVE_DEST_2='SERVICE=ORCL LGWR SYNC AFFIRM' on the standby database
* symptom: LOG_ARCHIVE_DEST_2='SERVICE=STBY LGWR SYNC AFFIRM' on the primary database
* symptom: Standby redo log files are defined on the standby database
* cause: The standby redo log files are synchronously filled with redo from the primary database. When a logswitch occur on the primary database, those files are archived on the standby database before being applyed on it. The archiving process on the standby database should only archive to the local disks on the standby database and not transmit them to the primary database.
fix:
Disable the remote archiving on the standby database.
Example: alter system set log_archive_dest_2 = ''
是因为没有把standby 上的log_archive_dest_2 清空导致的。
使用 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) 也可以避免16009另外也有可能是bug 导致16009
bug 4676659
Standby may not be recognised (ORA-16009)
When the log transport is LGWR ASYNC and logical standby has
LOG_ARCHIVE_DEST setting VALID_FOR=(ONLINE_LOGFILE, PRIMARY_ROLE),
ORA-16009 is reported at both primary and standby alert.log at
regular intervals.
Workaround:
There is no workaround to prevent ORA-16009 from appearing in alert logs.
However, even though there are errors in alert log no functionality is
lost.