The Hard Parse Ratio alert notifies you when its configured condition is met on Oracle instances so you can investigate and respond.
Mini DBA describes this alert as: Percentage of SQL executions requiring hard parse High ratio indicates SQL not using bind variables or cursor_sharing issues Hard parsing is CPU-intensive and should be minimized 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 helps reveal query and workload pressure. It points you toward expensive statements, plan changes, inefficient access patterns, or bursts of work that need investigation before they affect service levels.
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: % hard parses. Major threshold: 20 %. Minor threshold: 10 %. 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.
Use the query, wait, and performance views to find the statement or subsystem behind the pressure. Compare against the recent baseline, update statistics, tune indexes, adjust application batching, and move maintenance work away from peak periods where possible.
If the alert creates repeated noise, review whether it is enabled on the correct instances, whether maintenance windows are configured, and whether the minor and major routes match the real business impact. Keep enough history to prove the new setting before changing it broadly.