The Concurrency Wait Pressure alert notifies you when its configured condition is met on Oracle instances so you can investigate and respond.
Mini DBA describes this alert as: Oracle Concurrency waits as a percentage of current database time Sustained concurrency pressure points to hot blocks, library/cache contention, row contention, or serialization points that may need SQL, schema, or transaction design review 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 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 on any monitored Oracle instance where this condition would require an administrator to investigate or communicate with the application team. Tune noisy development systems after you have a short baseline.
Threshold meaning: % of DB time. Major threshold: 25 % of DB time. Minor threshold: 10 % of DB time. 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.
Open the related Mini DBA page for the instance, compare the current value with the recent baseline, identify whether the change is caused by workload, configuration, host capacity, or maintenance, then record the corrective action in the incident notes.
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.