Oracle Database / Data Guard & High Availability
Read primary-side archive destination errors before changing transport
A standby connection issue often leaves a useful error at the sending destination. Inspect enabled destinations on the primary.
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 dest_id, status, destination, error FROM v$archive_dest WHERE status <> 'INACTIVE';Read the result
The status and error distinguish unusable configuration, connection failure and other transport problems. They must be matched to the intended standby.
Resolve and verify
Compare the descriptor, service, authentication and remote availability with the reported error. Repair the specific dependency and confirm redo transmission advances.
Operational precautions
Do not disable a mandatory destination without reviewing protection mode and business availability requirements.