The Redo Generation Rate alert notifies you when its configured condition is met on Oracle instances so you can investigate and respond.
Mini DBA describes this alert as: Redo log generation rate (MB per second) High redo generation indicates heavy DML activity May impact standby database apply rates in Data Guard environments 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.
This alert shows unusually high Oracle redo generation, usually from heavy DML or bulk activity. Sustained growth can increase log-switch, archive, backup, and Data Guard apply pressure.
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 meaning: MB/sec. Major threshold: 100 MB/sec. Minor threshold: 50 MB/sec. 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.
Identify the sessions, SQL, jobs, or deployments generating redo and confirm whether the workload is expected. Reduce unnecessary DML or write amplification, reschedule bulk work, and verify that redo logs, archiving, and standby apply have enough throughput for legitimate demand.
Storage alerts should usually stay enabled even on quiet systems because the impact of missing them is high. Tune warning thresholds to leave enough time for approval, provisioning, and validation, especially when storage changes are handled by another infrastructure team.