ops$tkyte%ORA10GR2> set autotrace traceonly explain
ops$tkyte%ORA10GR2> select * from dual;
Execution Plan
----------------------------------------------------------
Plan hash value: 272002086
--------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
--------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1 | 2 | 2 (0)| 00:00:01 |
| 1 | TABLE ACCESS FULL| DUAL | 1 | 2 | 2 (0)| 00:00:01 |
--------------------------------------------------------------------------
it is there, make sure you have a current plan table - if you have an old one from years gone by - you are missing out on things.
ops$tkyte%ORA10GR2> @?/rdbms/admin/utlxplan
ops$tkyte%ORA10GR2> rem
ops$tkyte%ORA10GR2> rem $Header: utlxplan.sql 08-may-2004.12:53:19 bdagevil Exp $ xplainpl.sql
ops$tkyte%ORA10GR2> rem
ops$tkyte%ORA10GR2> Rem Copyright (c) 1988, 2004, Oracle. All rights reserved.
ops$tkyte%ORA10GR2> Rem NAME
ops$tkyte%ORA10GR2> REM UTLXPLAN.SQL
ops$tkyte%ORA10GR2> Rem FUNCTION
ops$tkyte%ORA10GR2> Rem NOTES
ops$tkyte%ORA10GR2> Rem MODIFIED
ops$tkyte%ORA10GR2> Rem bdagevil 05/08/04 - add other_xml column
ops$tkyte%ORA10GR2> Rem bdagevil 06/18/03 - rename hint alias to object_alias
ops$tkyte%ORA10GR2> Rem ddas 06/03/03 - increase size of hint alias column
ops$tkyte%ORA10GR2> Rem bdagevil 02/13/03 - add plan_id and depth column
ops$tkyte%ORA10GR2> Rem ddas 01/17/03 - add query_block and hint_alias columns
ops$tkyte%ORA10GR2> Rem ddas 11/04/02 - revert timestamp column to DATE (PL/SQL problem)
ops$tkyte%ORA10GR2> Rem ddas 10/28/02 - change type of timestamp column to TIMESTAMP
ops$tkyte%ORA10GR2> Rem ddas 10/03/02 - add estimated_time column
ops$tkyte%ORA10GR2> Rem mzait 04/16/02 - add row vector to the plan table
ops$tkyte%ORA10GR2> Rem mzait 10/26/01 - add keys and filter predicates to the plan table
ops$tkyte%ORA10GR2> Rem ddas 05/05/00 - increase length of options column
ops$tkyte%ORA10GR2> Rem ddas 04/17/00 - add CPU, I/O cost, temp_space columns
ops$tkyte%ORA10GR2> Rem mzait 02/19/98 - add distribution method column
ops$tkyte%ORA10GR2> Rem ddas 05/17/96 - change search_columns to number
ops$tkyte%ORA10GR2> Rem achaudhr 07/23/95 - PTI: Add columns partition_{start, stop, id}
ops$tkyte%ORA10GR2> Rem glumpkin 08/25/94 - new optimizer fields
ops$tkyte%ORA10GR2> Rem jcohen 11/05/93 - merge changes from branch 1.1.710.1 - 9/24
ops$tkyte%ORA10GR2> Rem jcohen 09/24/93 - #163783 add optimizer column
ops$tkyte%ORA10GR2> Rem glumpkin 10/25/92 - Renamed from XPLAINPL.SQL
ops$tkyte%ORA10GR2> Rem jcohen 05/22/92 - #79645 - set node width to 128 (M_XDBI in gendef)
ops$tkyte%ORA10GR2> Rem rlim 04/29/91 - change char to varchar2
ops$tkyte%ORA10GR2> Rem Peeler 10/19/88 - Creation
ops$tkyte%ORA10GR2> Rem
ops$tkyte%ORA10GR2> Rem This is the format for the table that is used by the EXPLAIN PLAN
ops$tkyte%ORA10GR2> Rem statement. The explain statement requires the presence of this
ops$tkyte%ORA10GR2> Rem table in order to store the descriptions of the row sources.
ops$tkyte%ORA10GR2>
ops$tkyte%ORA10GR2> create table PLAN_TABLE (
2 statement_id varchar2(30),
3 plan_id number,
4 timestamp date,
5 remarks varchar2(4000),
6 operation varchar2(30),
7 options varchar2(255),
8 object_node varchar2(128),
9 object_owner varchar2(30),
10 object_name varchar2(30),
11 object_alias varchar2(65),
12 object_instance numeric,
13 object_type varchar2(30),
14 optimizer varchar2(255),
15 search_columns number,
16 id numeric,
17 parent_id numeric,
18 depth numeric,
19 position numeric,
20 cost numeric,
21 cardinality numeric,
22 bytes numeric,
23 other_tag varchar2(255),
24 partition_start varchar2(255),
25 partition_stop varchar2(255),
26 partition_id numeric,
27 other long,
28 distribution varchar2(30),
29 cpu_cost numeric,
30 io_cost numeric,
31 temp_space numeric,
32 access_predicates varchar2(4000),
33 filter_predicates varchar2(4000),
34 projection varchar2(4000),
35 time numeric,
36 qblock_name varchar2(30),
37 other_xml clob
38 );
Table created.