MAX(SEQUENCE#) from V$ARCHIVED_LOG is showing a wrong sequence#
edited Jul 25, 2013 9:23AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 4 commentsAnswered
Dear Experts,
We are working on DataGuard setup in 11.2.0.2 (Windows 2008) with FSFO.
Due to a crash in Primary DB, observer failed over the database to the standby. Before the failover Max(sequence#) from v$archived_Log is 18926.
Immediately within 10 m ins after the failover, we reinstated the primary to function as secondsry and in the very next downtime we switchover the configuration. I see a problem right from then on though there is no problem with the Recovery process at standby.
The below is difference I see
At the standby site, I see the max(sequence#) as 18926, where as the applying log is 1653.
0