Question on FAL (Fetch Archive log) on Data guard
edited Sep 25, 2025 3:34PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) Question
DB version: 19.11
OS : RHEL 8.10
DB_UNIQUE_NAME of Primary : CDB_05P
DB_UNIQUE_NAME of Physical standby : CDB_05PS
I have an Active dataguard setup with a 2-node RAC DB as primary and a standalone DB as the standby.
Its in maximum availability mode. Its a busy production DB.
Today, I noticed that there is a gap of around 12 hours on standby. I mean, there was a gap of 900+ sequences for Thread 1 and a gap of 600+ sequences for Thread 2.
On standby, the v$managed_standby view was showing the following. Sorry for the empty lines seen in the query output below. The code block thing isn't working well (at least for me)
Tagged:
0