SQL Optimizer provides a variety of formats for displaying an execution plan. After selecting a plan format, you can customize the plan display and the Execution Plan window.
To select a plan format
Select a SQL statement.
Select one of the following formats:
To use the Tree Plan
Right-click an execution plan and select View Plan | As Tree Plan.
Select a layout style for the tree plan from the Execution Plan toolbar (right panel). Each style displays different plan details (operators, predicates, statistics).
To select which items/columns to display in the execution plan, right-click the plan and select Plan Options. The settings will apply to the current module only.
In the Actual Plan tab, to display a comparison of Oracle estimates and actual statistics, click the Plan Comparison button in the Execution Plan toolbar.
To use DBMS_XPlan
To select a display level for DBMS_XPlan (Formatted), click the arrow beside the Switch DBMS_XPlan level button and select an option.
To use the Plain Language Plan
Right-click an execution plan and select View Plan | As Plain Language Plan.
To use Graphic Plan
Right-click an execution plan and select View Plan | As Graphic Plan.
To use MS Graphic Plan
Right-click an execution plan and select View Plan | As MS Graphic Plan.
To return to previous view
To return to your previous view, click the Switch View Plan button at the bottom of the Execution Plan toolbar. Use this button to easily toggle between two views. Click the arrow to select a different view.
To customize font style and color
To display step description in footer
To display additional plan information
You can animate each step in the execution plan in the order SQL Optimizer executes them.
To animate the execution plan or cancel the animation
|»||Right-click the execution plan and select Animate Plan Steps.|
You can copy an execution plan from the Execution Plan pane and paste it into another file as text or a bitmap image.
To copy an execution plan
You can remove all saved SQL statements from Oracle's SGA by flushing the shared pool before using Inspect SGA to collect SQL. Flushing the shared pool before starting a job collecting currently running SQL can be useful because SQL statistics retrieved are for SQL collected during the specified monitoring time.
Caution: Flushing the shared pool can impact the performance of your production server while the server repopulates its memory buffers.
To flush the shared pool
Right-click a job in the Job List pane and select Flush Shared Pool.
You need to have the privileges to execute the ALTER SYSTEM command to flush the shared pool.
Flushing the shared pool before starting a job collecting executed SQL from the SQL area can decrease the number of statements collected.