Use the Redo Log Switches Per Hour alert in Mini DBA to monitor Oracle instances and make this condition visible before it becomes a wider database incident.
Mini DBA describes this alert as: Excessive redo log switches per hour High frequency (>4-6/hour) indicates undersized redo logs causing checkpoint storms and performance degradation Remediation: Increase redo log file size The default evaluation frequency is Minute, so the alert is intended to be close enough to operational reality for live triage.
This alert protects storage and recovery capacity. It helps you find growth, retention, and backup conditions that can stop writes, break recovery objectives, or leave the server without enough working space for normal database activity.
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: Switches/hour. Major threshold: 6 switches/hour. Minor threshold: 4 switches/hour. Comparison direction: "over". Use higher thresholds on batch-heavy, development, or intentionally bursty systems where brief pressure is expected. Use lower thresholds on latency-sensitive production systems, small instances with little headroom, and services with strict recovery or availability commitments.
Free space by removing safe-to-delete files, expanding the volume or tablespace, moving growth-heavy objects, correcting retention settings, or shrinking only after a documented one-off event. For recovery-related areas, verify that backups and log shipping or archiving are healthy before deleting anything.
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.