My Oracle Support Banner

Apply lag has NULL value in v$dataguard_stats (Doc ID 2323661.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.2.0.1 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

Primary and standby databases are in sync but we see error "ORA-16854: apply lag could not be determined" in DGMGRL:

Check if there is lag:

Primary:
SQL> select thread#, max(sequence#) "Last Primary Seq Generated" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;

THREAD# Last Primary Seq Generated
---------- --------------------------
1 68982

Standby:
SQL> select thread#, max(sequence#) "Last Standby Seq Received" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;

THREAD# Last Standby Seq Received
---------- -------------------------
1 68982

SQL> select thread#, max(sequence#) "Last Standby Seq Applied" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# and val.applied in ('YES','IN-MEMORY') group by thread# order by 1;

THREAD# Last Standby Seq Applied
---------- ------------------------
1 68982

there is no lag, but DataGuard Broker show error:

DGMGRL> show configuration

Configuration - broker

Protection Mode: MaxPerformance
Members:
chicago - Primary database
boston - Physical standby database
Warning: ORA-16854: apply lag could not be determined

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!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.