My Oracle Support Banner

Physical standby failover created an archivelog gap after Reinstate Operation fails with ORA-16724 (Doc ID 2813475.1)

Last updated on NOVEMBER 05, 2021

Applies to:

Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Information in this document applies to any platform.

Symptoms

Context:
    Primary  : PRIM
    Standby : STDBY



1. Failover to DR (Disaster Recovery) site (STDBY)
2. Wait for 2 or more days and make some changes in Primary database (STDBY)
3. Reinstate Disabled Standby database (PRIM)

 

 

Changes

Once Failover has completed, Old primary database (PRIM) was left in shutdown state for 2 or more days.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.