Use the Long Running Sessions 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: Active sessions that have been running the same SQL batch for a long period Heavy queries may be consuming too much of the database resources The threshold represents the number of minutes the batch must run to trigger the alert 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 concurrency pressure. Blocking, long sessions, and lock waits can turn a healthy server into a slow user experience, so the alert gives administrators an early route to the sessions, statements, and applications involved.
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: Minutes running. Major threshold: 60 minutes. Minor threshold: 30 minutes. 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.
Open the activity, blocking, and query views to identify the lead blocker, SQL text, wait type, login, host, and application. Prefer fixing the query or transaction pattern, but kill or cancel the blocking session when the business impact is higher than the rollback risk.
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.