Use the Host CPU % 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: Percentage of host CPU utilization Sustained high usage may indicate poor SQL, missing indexes, or insufficient hardware The default evaluation frequency is Minute, so the alert is intended to be close enough to operational reality for live triage. Because duration is used, Mini DBA can avoid treating a single short spike as a full incident when the condition clears quickly.
This alert highlights sustained CPU pressure. CPU saturation usually means queries, background tasks, or host contention are competing for scheduler time and can cause broad latency across the monitored workload.
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: % CPU. Major threshold: 95 %. Minor threshold: 85 %. Comparison direction: "over". Duration is used, so prefer requiring the condition to persist before paging people for transient spikes. 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.
Find the top CPU queries, jobs, and host processes. Review recent deployments and plan changes, then tune indexes or queries, adjust schedules, reduce concurrency, or increase compute where the workload is legitimately larger than the instance can handle.
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.