Use the RMAN Backup Age 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: Hours since last successful RMAN backup Default warning is 168 hours (7 days), matching the no-backup-found message. System-container-only Oracle installs are ignored until a user database/PDB exists, and alerts identify the affected database/PDB. Critical for disaster recovery, compliance requirements, and data protection Remediation: Run RMAN backup immediately, check backup schedule, and investigate failures 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 on systems with recovery objectives and on any database where a missed backup or archive problem would require business escalation. Test and lab systems can use looser settings if they are recreated from source control or seed data.
Threshold meaning: Hours since backup. Minor threshold: 168 hours. 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.
Run or restart the missing backup after checking storage and job history. Confirm that restore requirements are met, clear failed schedules, and make sure backup monitoring reports the next successful run.
For recovery and replication alerts, route notifications to the people who own recovery objectives. Higher thresholds can be reasonable for reporting replicas, but production failover paths normally need tighter settings and explicit escalation.