Oracle Database / Data Guard & High Availability
Inspect a specific Data Guard broker member in detail
A configuration-wide warning may originate from only one member or property. Collect the detailed state before changing transport settings.
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.
SHOW DATABASE VERBOSE 'STBY';Read the result
In DGMGRL, replace STBY with the actual DB_UNIQUE_NAME. The output exposes member properties, status and reported errors.
Resolve and verify
Compare the member's intended role, connect identifiers and lag with actual database state. Correct a demonstrated mismatch and recheck configuration health.
Operational precautions
Broker properties and connection information can be sensitive. Do not copy another database's property values indiscriminately.