OracleData Guard
Data Guard errors and warnings, last 24 hours
Messages Data Guard wrote to V$DATAGUARD_STATUS, filtered to warnings and errors. Run on both sides.
Not yet verified. How scripts are tested
1CLEAR COLUMNS2SET LINESIZE 180 PAGESIZE 100 TRIMOUT ON TAB OFF3COLUMN at_time HEADING "TIME" FORMAT A194COLUMN facility FORMAT A245COLUMN severity FORMAT A86COLUMN error_code HEADING "ERROR" FORMAT 999997COLUMN message FORMAT A90 WORD_WRAPPED8 9SELECT TO_CHAR(timestamp, 'YYYY-MM-DD HH24:MI:SS') AS at_time,10 facility, severity, error_code, message11FROM v$dataguard_status12WHERE timestamp > SYSDATE - 113 AND severity IN ('Warning', 'Error', 'Fatal')14ORDER BY timestamp DESC;Save it as ora-dg-messages.sql and run it with SQL> @ora-dg-messages.
Part of these runbooks
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.
- 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.
- Broker health checks (DGMGRL)The broker's own view of the configuration. VALIDATE DATABASE is the best single readiness check before a switchover.