Oracle Database / Data Guard & High Availability
ORA-16766: investigate why redo apply stopped
The broker can report stopped apply while the underlying database log contains the real failure. Capture the exact apply error.
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
On the standby, process state helps confirm whether apply is active. An absent process does not explain whether a gap, corruption or administrative action stopped it.
Resolve and verify
Read the standby alert log and broker details, repair the specific cause, then resume apply through the configuration's normal management path. Confirm backlog decreases.
Operational precautions
Do not repeatedly restart apply over an unresolved corruption or missing-redo error.