Last Applied SCN Becomes Greater Than V$DATABASE.STANDBY_BECAME_PRIMARY_SCN When Standby Database Performs Failover
(Doc ID 3060182.1)
Last updated on NOVEMBER 27, 2024
Applies to:
Gen 2 Exadata Cloud at Customer - Version N/A and laterOracle GoldenGate - Version 19.1.0.0.0 and later
Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Goal
STANDBY_BECAME_PRIMARY_SCN of V$DATABASE is explained as below in Database Reference Document.
This SCN is useful for converting a failed primary database into a physical standby database after a forced failover.
But when standby database performs failover, last applied SCN becomes greater than V$DATABASE.STANDBY_BECAME_PRIMARY_SCN.
For example, Standby database is recovered until SCN 2225233(*1), but STANDBY_BECAME_PRIMARY_SCN is 2225193(*2) at below case.
STANDBY_BECAME_PRIMARY_SCN(*2) is smaller than the latest applied SCN (*1).
<< alert.log of Standby Database >>
2024-11-11T15:47:45.260195+09:00
SVCB started with pid=8, OS id=164663
Standby terminal recovery start SCN: 2225194
RESETLOGS after incomplete recovery UNTIL CHANGE 2225233 time 11/11/2024 15:47:11 <==(*1)
NET (PID:164634): ORL pre-clearing operation disabled by switchover
Online log <onlie redo log 1>: Thread 1 Group 1 was previously cleared
Online log <onlie redo log 2>: Thread 1 Group 2 was previously cleared
Online log <onlie redo log 3>: Thread 1 Group 3 was previously cleared
Standby became primary SCN: 2225193 <==(*2)
Solution
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
| Goal |
| Solution |
| References |