V$ARCHIVE_GAP doesn't show a existing GAP
(Doc ID 974730.1)
Last updated on FEBRUARY 01, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.8 [Release 10.1 to 11.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Affected Database:
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
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |