V$ARCHIVE_GAP doesn't show a existing GAP (Doc ID 974730.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.8 [Release 10.1 to 11.1]
Information in this document applies to any platform.
Affected Database:

***Checked for relevance on 06-Aug-2014***


Symptoms

After  "ALTER DATABASE OPEN RESETLOGS" queries on V$ARCHIVE_GAP doesn't return
correct results.

eg.

SQL> select * from v$archive_gap;
returns no rows selected

even when GAPs are actually there.

Changes

This can happen when the standby database has different incarnations.
Database creates a new incarnation whenever a database is opened with the RESETLOGS option (eg. flashback, failover).

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms