Standby Database Not Automatically Reinstating in Fast-Start Failover Configuration
(Doc ID 3072631.1)
Last updated on FEBRUARY 20, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 19.25.0.0.0 and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version All Versions and later
Information in this document applies to any platform.
Symptoms
The standby database in a Fast-Start Failover configuration fails to reinstate automatically after a shutdown abort on the primary database.
The DG Auto-reinstate parameter is set to TRUE, but the standby database remains in a non-reinstated state.
Observer log entries indicate continuous attempts to connect and reinstate the old standby, with the following messages:
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 |
Cause |
Solution |
References |