Oracle Database / Data Guard & High Availability
Compare intended Data Guard protection mode with current protection level
A configuration can request a protection mode while current operating conditions reduce its actual protection. Inspect both values.
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 database_role, protection_mode, protection_level FROM v$database;Read the result
PROTECTION_MODE describes configuration and PROTECTION_LEVEL reflects the current effective level. Interpret them with destination health and the topology.
Resolve and verify
Correlate mismatches with unavailable synchronized destinations and broker errors. Restore the approved protection path and verify the recovery objective is met.
Operational precautions
Do not change protection mode as a quick availability workaround without an explicit business risk decision.