Automatic Failover
edited Feb 28, 2020 9:25AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 11 commentsAnswered ✓
Hello Gurus,
We have FSFO setup in our DG configuration this morning we had the primary DB instance got restarted few times and to my surprise it did not get failed over automatically.
Why primary did not get failedover to standby ?
Observer.log
[W000 02/25 11:21:13.84] Try to connect to the primary.[W000 02/25 11:22:27.23] Primary database cannot be reached.[W000 02/25 11:24:42.66] The primary database has requested a transition to the UNSYNC/LAGGING state with the standby database OPE541_S.[W000 02/25 11:24:42.69] Permission granted to the primary database to transition to UNSYNC/LAGGING state with the standby database OPE541_S.[W000 02/25 11:24:45.69] The primary database returned to SYNC/NOT LAGGING state with the standby database OPE541_S.[W000 02/25 11:25:27.89] Reconnect interval expired, create new connection to primary database.[W000 02/25 11:26:23.36] Primary database cannot be reached.[W000 02/25 11:28:42.33] The primary database has requested a transition to the UNSYNC/LAGGING state with the
0