Oracle Hard Parse Ratio Alert


Use the Hard Parse Ratio alert in Mini DBA to monitor Oracle instances and make this condition visible before it becomes a wider database incident.

Screenshot pending: Mini DBA Oracle Hard Parse Ratio alert screenshot placeholder

Alert Summary

  • Platform: Oracle
  • Alert category: Query
  • Default enabled: true
  • Default evaluation frequency: Minute
  • Threshold label: % hard parses
  • Unit: %

What Mini DBA Checks

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 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.

Why This Alert Is Helpful

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.

When To Enable It

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 Guidance

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. 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.

Remediation For An Active Alert

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.

Investigation Workflow

  1. Confirm the alert is still active and note the first seen time, affected instance, and severity.
  2. Review the top consumers, host counters, service tier or instance size, and recent workload changes in Mini DBA before changing configuration or ending sessions.
  3. Compare the current value with the normal baseline for the same time of day or maintenance window.
  4. Record the cause, corrective action, and whether thresholds or routing should be adjusted after the incident.

Avoiding Alert Noise

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.

Related Pages