Oracle data guard

Start Here

Manual Home Installation Windows Installation Linux Engine Container Linux Console Container Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Mode Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Performance History Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

Use the Oracle Data Guard page to check standby readiness, redo transport/apply lag, archive destination errors, and managed recovery process state.

Screenshot pending: Mini DBA Oracle Data Guard screenshot placeholder

What Mini DBA shows

Database role, open mode, protection mode, maximum sampled lag, destination error count, and managed standby process count.
Lag statistics from V$DATAGUARD_STATS, including transport lag, apply lag, datum time, and time computed.
Archive/Data Guard destination status from V$ARCHIVE_DEST_STATUS, including destination, recovery mode, gap status, and error text.
Managed standby process state from V$MANAGED_STANDBY.
Configuration members from V$DATAGUARD_CONFIG.

How to use it

Start with the summary row. A non-zero maximum lag does not always mean an incident, but sustained transport or apply lag should be investigated before it threatens recovery point or failover readiness.

Use Destinations when the page reports destination errors. The error text usually points at network, listener, disk, archive destination, or authentication problems.

Use Managed Standby on standby databases to confirm recovery processes are present and applying redo. A standalone or primary-only database may legitimately show no managed standby rows.

Permissions

The monitoring login needs read access to the Data Guard dynamic performance views. The Oracle permissions modal includes Data Guard-specific checks and DBA SQL guidance.

For Oracle 12c+ multitenant systems, connect Mini DBA to the CDB/root service with a common monitoring user when you want full instance-level HA/DR visibility.