Validate the standby with the broker before switchover/failover (VALIDATE DATABASE)
OracleData GuardCommand
VALIDATE DATABASE '<standby_db_unique_name>';
VALIDATE DATABASE VERBOSE '<standby_db_unique_name>';
# spfile parameter differences between the two sides:
VALIDATE DATABASE '<standby_db_unique_name>' SPFILE;
# Network and static listener registrations (18c+):
VALIDATE NETWORK CONFIGURATION FOR ALL;
VALIDATE STATIC CONNECT IDENTIFIER FOR ALL;What it does
Checks whether the standby is ready for a role change ("Ready for Switchover / Failover: Yes"), the number/size of standby redo logs, flashback and apply state, spfile differences, and the static services the broker needs to restart instances.
When to use it
As a mandatory step before every planned switchover; after building a new standby and after network/listener changes.
Caution
Read-only. If you see "Ready for Switchover: No" or a standby redo log warning, do not proceed with the switchover. A static connect identifier error means the broker cannot start the instance during a switchover, which forces manual intervention.
Related
- Show the Data Guard broker configuration and database status (DGMGRL)
- Check primary/standby role and switchover readiness with SQL
- Measure transport/apply lag, apply rate and Data Guard processes on the standby
- Perform a planned switchover (DGMGRL, role change without data loss)
- Perform a failover after losing the primary (DGMGRL)
- Recover the old primary as a standby after a failover (REINSTATE)