Standby: V$ARCHIVE_DEST_STATUS.APPLIED_SEQ# has incorrect value

Problem

SQL> select dest_id, RECOVERY_MODE, DATABASE_MODE, PROTECTION_MODE, ARCHIVED_SEQ#, APPLIED_SEQ#  from v$archive_dest_status where dest_id=2;

DEST_ID RECOVERY_MODE           DATABASE_MODE   PROTECTION_MODE      ARCHIVED_SEQ# APPLIED_SEQ#
———- ———————– ————— ——————– ————- ————
2 MANAGED REAL TIME APPLY MOUNTED-STANDBY MAXIMUM PERFORMANCE          84671        84671

SQL> select sequence#, applied, archived from v$archived_log;
….

SEQUENCE# APP ARC
———- — —
….
84696 YES YES
84696 YES YES
84697 YES YES
84697 YES YES
84698 NO  YES
84698 YES YES
84699 NO  YES
84699 YES YES
84700 YES YES
84700 YES YES
84701 YES YES
84701 YES YES

where 84701 > 84671

Cause

Bug 8822832 – V$ARCHIVE_DEST_STATUS has incorrect value for APPLIED_SEQ# [ID 8822832.8]
Modified 17-JUN-2011     Type PATCH     Status PUBLISHED

Bug 8822832  V$ARCHIVE_DEST_STATUS has incorrect value for APPLIED_SEQ#
This note gives a brief overview of bug 8822832.
The content was last updated on: 17-JUN-2011
Click here for details of each of the sections below.
Affects:

Product (Component)    Oracle Server (Rdbms)
Range of versions believed to be affected     Versions >= 9 but BELOW 12.1
Versions confirmed as being affected

11.2.0.1
11.1.0.7
10.2.0.4

Platforms affected    Generic (all / most platforms affected)

Fixed:

This issue is fixed in

12.1 (Future Release)
11.2.0.2 (Server Patch Set)
11.2.0.1.2 (Patch Set Update)
11.2.0.1 Bundle Patch 6 for Exadata Database
11.2.0.1 Patch 2 on Windows Platforms

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: