DBA SGA SQL Execution Plan History – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™. Oracle EBS module: Database Administration · all Database Administration reports
Overview
Execution plan history for a particular SQL id from the SGA
Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.
Report Parameters
SQL Id, Plan Hash Value, SQL Text contains, Module contains, Using Index, Object Name, Options, Objects larger than x GB, Show Object Size
Oracle EBS Tables Used
gv$sql_plan, v$parameter, dba_segments
Report Categories
Related Reports
DBA AWR SQL Performance Summary, DBA AWR SQL Execution Plan History, DBA Sessions, DBA SGA+PGA Memory Configuration, DBA Blocking Sessions, DBA SGA Blocking Session Summary, DBA AWR Blocking Session Summary, DBA AWR Active Session History, DBA SGA Active Session History
Running This SQL Without Blitz Report
The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | DBA SGA SQL Execution Plan History 20-Sep-2021 140214.xlsx |
| Blitz Report™ XML Import | DBA_SGA_SQL_Execution_Plan_History.xml |
| SQL Source | DBA SGA SQL Execution Plan History.sql |
| Full Report on Enginatics | www.enginatics.com/reports/dba-sga-sql-execution-plan-history/ |
Case Study & Technical Analysis
Abstract
The DBA SGA SQL Execution Plan History report retrieves the actual execution plans for SQL statements currently residing in the library cache (SGA). Unlike the theoretical plan generated by EXPLAIN PLAN, this report shows the plan that the optimizer actually chose and compiled. It enriches this data by joining with segment statistics to display the size of the tables and indexes involved in the query, providing immediate context on the cost of full table scans.
Technical Analysis
Core Features
- Actual vs. Theoretical: Displays the plan from
GV$SQL_PLAN, which represents the compiled bytecode in memory. - Object Sizing: Integrates with
DBA_SEGMENTSto show the physical size (in GB) of every object accessed in the plan. This is crucial for distinguishing between a harmless full scan on a lookup table vs. a disastrous full scan on a 500GB transaction table. - Predicate Information: Shows access and filter predicates, helping to diagnose why an index was or wasn’t used.
Key View
GV$SQL_PLAN: The row-source generation plan stored in the Shared Pool.
Operational Use Cases
- Plan Flipping: Diagnosing why a query suddenly changed performance by comparing its current plan hash value against historical knowledge.
- Index Validation: Verifying if a newly created index is actually being picked up by the application code without needing to bounce the application.
- Cost Analysis: Understanding the optimizer’s estimated cardinality and cost for each step.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© Enginatics GmbH