Home > bug > primary v$archived_log applied不准确

primary v$archived_log applied不准确

SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE    10.2.0.1.0      Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production

偶然发现,当主备恢复连接,在resolve gap的时候,相应几个GAP的v$archived_log applied 这个字段还是NO,但是从standby的视图上查是YES,日志里面也显示apply了,查了下,确定是BUG。貌似跟applied字段相关的BUG还挺多的。

Bug 4538727:
Bug 4538727 – Applied column is not updated in V$ARCHIVED_LOG [ID 4538727.8]
Fixed:

This issue is fixed in
10.2.0.4 (Server Patch Set)
11.1.0.7 (Server Patch Set)
Symptoms:

Related To:

Wrong Results
Physical Standby Database / Dataguard
RMAN (Recovery Manager)
V$ARCHIVED_LOG

Description

The APPLIED column in v$archived_log is not updated properly.
v$archived_log shows the wrong value of APPLIED on some of
the archive logs so RMAN fails to delete them.

eg:
archive log filename=/arc2/1_0000000157.arc thread=1 sequence=157
WARNING: archive log not deleted, not yet applied by standby

Moreover, in primary database, the customer can not confirm
the latest archive log applied on the standby database.

Categories: bug Tags:
  1. No comments yet.
  1. No trackbacks yet.