Oracle Database / Data Guard & High Availability
Check Flashback Database readiness before planning standby reinstatement
A failover runbook may depend on flashback capability and retained flashback logs. Verify current state and available window before promising reinstatement.
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 flashback_on FROM v$database;
SELECT oldest_flashback_scn, oldest_flashback_time, retention_target FROM v$flashback_database_log;Read the result
Enabled flashback and an available window are necessary context, not proof that the exact reinstatement point is reachable or that all broker prerequisites are met.
Resolve and verify
Compare the required SCN and role-transition history with retained data. Follow the supported broker or recovery procedure and plan a rebuild if prerequisites are absent.
Operational precautions
Do not flash back a database or change roles from this checklist alone.