Oracle redo write wait pressure alert

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

The Redo Write Wait Pressure alert notifies you when its configured condition is met on Oracle instances so you can investigate and respond.

Screenshot pending: Mini DBA Oracle Redo Write Wait Pressure alert screenshot placeholder

Alert summary

Platform: Oracle
Alert category: Disk
Default enabled: true
Default evaluation frequency: Minute
Threshold label: % of DB time
Unit: % of DB time

What Mini DBA checks

Mini DBA describes this alert as: Oracle log file parallel/single write waits as a percentage of current database time Sustained redo write waits point at LGWR or redo-log storage pressure. Check redo log disk latency, storage saturation, checkpoint pressure, and synchronous Data Guard transport. Mini DBA evaluates this alert once a minute so changes are detected quickly. Because duration is used, Mini DBA can avoid treating a single short spike as a full incident when the condition clears quickly.

How this alert helps

This alert measures Oracle redo-write waits as a share of database time. Sustained waits point to LGWR, redo-log storage, checkpoint, or synchronous Data Guard transport pressure.

When to enable it

Enable it once the instance has a normal workload baseline. It is especially useful on busy OLTP, reporting, and integration systems where resource pressure can quickly become user-visible.

Threshold guidance

Threshold meaning: % of DB time. Major threshold: 20 % of DB time. Minor threshold: 10 % of DB time. Comparison direction: over. Duration is used, so prefer requiring the condition to persist before paging people for transient spikes. For an over-threshold alert, decreasing a threshold makes that severity fire sooner; increasing it tolerates more load or pressure. Set the minor threshold as an early-warning level and the major threshold at the highest acceptable value for the service.

Remediation for an active alert

Compare redo-write waits with log-file latency, redo volume, checkpoints, storage saturation, and synchronous Data Guard transport. Correct the measured log-write bottleneck or transport delay rather than treating the condition as free-space exhaustion.

Investigation workflow

Record the redo-write wait percentage, dominant events, redo volume, and affected time window.
Compare redo-log latency, storage throughput, checkpoints, and Data Guard transport.
Check recent workload, configuration, and infrastructure changes that increased redo or slowed LGWR.
Confirm that redo-write waits return to baseline after remediation.

Avoiding alert noise

If this alert is noisy, check whether the workload naturally has short bursts. Raise the duration or threshold for expected batch windows, but keep a lower route for production systems where user-facing latency matters. Avoid simply disabling the alert until you know whether the noise is caused by threshold choice or by a real capacity trend.