Oracle Database / Data Guard & High Availability
Inspect Data Guard recovery processes using the current process view
A standby may be mounted correctly while redo apply is stopped or waiting. Inspect the Data Guard processes in the appropriate database.
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, role, action FROM v$dataguard_process;Read the result
Rows identify active Data Guard process roles and actions. A wait can be normal when there is no new redo, so compare it with transport and apply evidence.
Resolve and verify
Check alert-log messages and fresh lag metrics, then restore apply through the environment's broker or manual management procedure as appropriate.
Operational precautions
Do not mix broker-managed and ad hoc recovery commands without understanding which component owns the configuration.