Mini DBA Oracle execution plan controls help you inspect plan text and parsed operator data for selected Oracle SQL. Use this page when an Oracle query is expensive, blocked behind an access path problem, or needs plan evidence before a DBA or developer changes SQL, indexes, statistics, or application logic.
Where To Open Oracle Plans
Oracle plan review usually starts from Oracle Activity or Oracle Queries. Activity helps when the statement is active now and you need session, wait, and SQL context. Queries helps when you are reviewing expensive SQL_IDs, elapsed time, executions, and repeated workload.
When plan data is available, Mini DBA can open an Oracle plan modal for the selected SQL. Plan retrieval depends on Oracle permissions, SQL_ID, child cursor, available dynamic performance views, and whether the statement has a plan that can be fetched. If the plan cannot be loaded, continue with Activity, Waits, SQL_ID evidence, query summary metrics, and object statistics checks.
Oracle Plan Modal Controls
The Oracle plan modal can show loading state while Mini DBA fetches plan information, then display:
- Plan Text for the formatted Oracle execution plan.
- Operators for parsed plan operations.
- AI Assistant for plan-specific analysis.
The Operators tab is the main drill-down control. It lists operation, object, cost percent, cost, rows, bytes, access predicates, and filter predicates. This table helps you move from "this SQL_ID is expensive" to "this object, predicate, join, or access path should be investigated first."
Cost percent is useful for prioritization, but it should be interpreted with runtime evidence. Oracle optimizer cost is an estimate. Bind values, stale statistics, adaptive features, skewed data, cardinality errors, concurrent workload, and wait events can make a plan perform differently from the estimate.
How To Review Oracle Operators
Start with the highest-cost operators and the operators that touch large objects. Then look at access and filter predicates. Access predicates help explain how Oracle reaches rows. Filter predicates help show where rows are discarded after access. A plan that filters many rows after a broad scan may need index, predicate, statistics, or SQL rewrite review.
Investigate:
- Full table scans on large tables when a selective predicate should use an index.
- Index range scans that still process many rows.
- Nested loops that repeatedly access a large inner object.
- Hash joins that may be reasonable for large sets but expensive during a user-facing transaction.
- Sorts, group by operations, or temp-heavy operations.
- Cardinality estimates that seem inconsistent with known data volume.
- Access predicates that do not match existing indexes.
- Filter predicates that suggest functions or implicit conversions are preventing efficient access.
Use Oracle Waits to decide whether the query is CPU-bound, I/O-bound, waiting on locks, or delayed by another resource. Use Oracle Memory when large sorts, hash operations, or memory pressure may be part of the symptom.
Plan Text Versus Operator Table
Plan Text is best for preserving the familiar Oracle plan format and sharing evidence with DBAs who already use Oracle tools. The Operators tab is better for scanning and triage because it exposes object names, costs, rows, bytes, and predicates in a sortable review style.
Use both views together. The plan text gives full context, while the operator table helps identify the part of the plan to discuss. For example, if a high-cost table access operation has a filter predicate that applies after the access, the next step may be to review indexing, predicate form, data distribution, or statistics.
Tuning Decisions From Oracle Plans
Oracle tuning should be controlled and evidence led. A plan may suggest an index, statistics refresh, SQL rewrite, bind variable review, or application change, but production action should be validated against workload impact.
Before making a change, capture:
- SQL_ID and child number where available.
- PDB or service context.
- Elapsed time, executions, rows, CPU, reads, and wait evidence.
- Plan text and the operator rows that support the recommendation.
- Related object, index, and statistics evidence.
- The expected success metric after the change.
If your organization uses licensed Oracle performance packs or advanced diagnostics, follow your internal licensing policy before relying on external Oracle tools outside Mini DBA.
Ask AI About An Oracle Plan
The Oracle plan modal can pass plan text and parsed operator rows to the Mini DBA AI Assistant. This is useful when you want help explaining a plan, ranking risky operators, or writing a DBA handover note.
Useful prompts include:
Which Oracle plan operator should I investigate first and why?Explain the access predicates and filter predicates that matter most in this plan.Create a safe tuning checklist for this SQL_ID using the plan and waits as evidence.Validate AI suggestions against Oracle statistics, object size, application behavior, and change control.
Related Pages
- Execution Plan Analysis
- Oracle Activity
- Oracle Queries
- Oracle Waits
- Oracle Memory
- Oracle Performance Tuning