今天用10.2.0.1的一套物理DG 转 逻辑 standby 出现大量错误:

primary 端:

— Connected User is Valid
RFS[2]: Assigned to RFS process 30286
RFS[2]: Database mount ID mismatch [0x9a9ac2b3:0x9a9a1a16]
RFS[2]: Destination database ID mismatch [0x2593781616:0x2592975883]
RFS[2]: Not using real application clusters
Fri Dec 2 19:27:39 2011
Errors in file /u01/app/oracle/admin/liu/udump/liu_rfs_30286.trc:
ORA-16009: remote archive log destination must be a STANDBY database
Fri Dec 2 19:30:16 2011
Thread 1 advanced to log sequence 24
Current log# 2 seq# 24 mem# 0: /u01/app/oracle/oradata/liu/redo02.log
Fri Dec 2 19:30:17 2011
LNS: Standby redo logfile selected for thread 1 sequence 24 for destination LOG_ARCHIVE_DEST_2

standby 端:

0x0000.000a997d, PID 29187, oracle@yang (P005)
Fri Dec 2 19:11:29 2011
LOGMINER: Log Auto Delete – deleting: /u01/arch/1_21_767998669.dbf
Deleted file /u01/arch/1_21_767998669.dbf
LNS1 started with pid=33, OS id=30088
Fri Dec 2 19:28:22 2011
Thread 1 advanced to log sequence 4
Current log# 3 seq# 4 mem# 0: /u01/app/oracle/oradata/liu/redo03.log
Fri Dec 2 19:28:23 2011
Errors in file /u01/app/oracle/admin/liu/bdump/liu_lns1_30088.trc:
ORA-16009: remote archive log destination must be a STANDBY database
Fri Dec 2 19:28:23 2011
LGWR: Error 16009 creating archivelog file ‘liu’
LNS: Failed to archive log 3 thread 1 sequence 4 (16009)

但是日志apply 正常 查找metalink

Bug 4676659 – ORA-16009 in alert log with standby and LGWR ASYNC [ID 4676659.8]
Modified 24-SEP-2008 Type PATCH Status PUBLISHED
Bug 4676659 ORA-16009 in alert log with standby and LGWR ASYNC

This note gives a brief overview of bug 4676659.
The content was last updated on: 03-APR-2008
Click here for details of each of the sections below.
Affects:

Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions >= 10.2 but < 11 Versions confirmed as being affected 10.2.0.2 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 10.2.0.3 (Server Patch Set) 11.1.0.6 (Base Release)

解决方法:升级数据库到10.2.0.5