Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

README.md

layout default
title DBA SGA SQL Execution Plan History | Oracle EBS SQL Report
description Execution plan history for a particular SQL id from the SGA – Oracle E-Business Suite SQL report
keywords Oracle EBS, Oracle E-Business Suite, SQL report, Blitz Report, Enginatics, DBA, SGA, SQL, Execution, gv$sql_plan, v$parameter, dba_segments
permalink /DBA%20SGA%20SQL%20Execution%20Plan%20History/

DBA SGA SQL Execution Plan History – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Execution plan history for a particular SQL id from the SGA

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

Enginatics

Related Reports

DBA AWR SQL Performance Summary, DBA AWR SQL Execution Plan History, DBA Blocking Sessions, DBA SGA Blocking Session Summary, DBA SGA+PGA Memory Configuration, DBA AWR Blocking Session Summary, DBA AWR Active Session History, DBA SGA Active Session History, DBA SGA SQL Performance Summary

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

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
Full SQL 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_SEGMENTS to 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

© 2026 Enginatics