OracleData Guard

Broker health checks (DGMGRL)

The broker's own view of the configuration. VALIDATE DATABASE is the best single readiness check before a switchover.

OS prompt

Not yet verified. How scripts are tested

ora-dg-broker.sh

1-- From the OS prompt, not SQL*Plus2dgmgrl /3 4SHOW CONFIGURATION;5SHOW DATABASE VERBOSE <db_unique_name>;6VALIDATE DATABASE <db_unique_name>;7SHOW CONFIGURATION LAG;

Run these at the operating system prompt.

Open in denrepo

More Oracle scripts: Data Guard

Transport and apply lagHow far behind the standby is in receiving and applying redo. A growing apply lag with no transport lag points at the apply process, not the network.
Redo apply and transport processesWhich Data Guard processes are running and what they're doing. No MRP0 row means redo is arriving but not being applied. Before 12.2, query…
Redo destinations and transport errorsEvery active archive destination with its status, gap state and last error. Any text in the ERROR column means redo isn't reaching that standby.
Archive gaps and last applied sequenceMissing log sequences the standby is waiting for, then the last applied sequence per thread. Compare with the current sequence on the primary.
Data Guard errors and warnings, last 24 hoursMessages Data Guard wrote to V$DATAGUARD_STATUS, filtered to warnings and errors. Run on both sides.
Standby redo log configurationStandby redo logs by thread. You want one more group per thread than you have online log groups, all the same size as the online logs.