Oracle Database / Data Guard & High Availability
Use broker validation before planning a role transition
A healthy-looking standby can still have configuration or recovery gaps that complicate a switchover. Gather readiness diagnostics in advance.
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.
VALIDATE DATABASE VERBOSE 'STBY';Read the result
In DGMGRL, validation reports checks for the selected member. It can perform diagnostic work but does not execute a switchover or certify the whole application cutover.
Resolve and verify
Resolve reported issues and include service routing, backup, monitoring and rollback steps in the transition plan. Rehearse the full runbook in the supported environment.
Operational precautions
Do not treat one successful validation as authorization to transition roles or as proof of zero application downtime.