Oracle Database / Data Guard & High Availability
Check archived-log apply evidence without confusing duplicate records
A log can have several control-file records because it was archived or registered through different paths. Inspect role-appropriate metadata carefully.
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 thread#, sequence#, registrar, applied, completion_time FROM v$archived_log WHERE registrar = 'RFS' ORDER BY completion_time DESC FETCH FIRST 30 ROWS ONLY;Read the result
On a physical standby, RFS-registered records help inspect applied state. APPLIED semantics and duplicate records require care; a maximum sequence alone is not a complete lag measure.
Resolve and verify
Compare thread coverage, fresh Data Guard lag metrics and recovery process progress. Investigate missing ranges rather than only the largest displayed sequence.
Operational precautions
Do not delete archived logs based solely on one APPLIED value; backup and other standby dependencies may still require them.