Oracle Database / Data Guard & High Availability
ORA-16853: investigate an apply-lag threshold warning
A broker apply-lag warning can indicate a real recovery delay or a threshold misaligned with the intended design. Measure fresh lag first.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT name, value, datum_time FROM v$dataguard_stats WHERE name IN ('apply lag','transport lag');Read the result
Compare the metrics and freshness on the standby. A configured apply delay can be intentional and must be considered separately from unexpected backlog.
Resolve and verify
Inspect recovery progress and workload capacity. Fix sustained delay, or review the threshold against the approved recovery objective after understanding the evidence.
Operational precautions
Do not increase the warning threshold merely to make monitoring green.