Comments on: How to display the explain plan of a query using dbms_xplan table funtion? http://oraqa.com/2006/01/16/how-to-display-the-explain-plan-of-a-query-using-dbms_xplan-table-funtion/ Oracle Question and Answer Mon, 19 Dec 2011 14:21:07 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: stbu http://oraqa.com/2006/01/16/how-to-display-the-explain-plan-of-a-query-using-dbms_xplan-table-funtion/comment-page-1/#comment-113 stbu Wed, 08 Feb 2006 20:32:17 +0000 http://oraqa.com/2006/01/16/how-to-display-the-explain-plan-of-a-query-using-dbms_xplan-table-funtion/#comment-113 A new feature of Oracle 10g Release 2 is that <pre>set autotrace traceonly explain</pre> is using DBMS_XPLAN now. Quote from <i>http://www.oracle.com/technology/oramag/oracle/05-sep/o55asktom.html</i> <pre>SQL> set autotrace traceonly explain SQL> select * 2 from emp, dept 3 where emp.deptno = dept.deptno 4 and emp.job = 'CLERK'; Execution Plan - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Plan hash value: 877088642 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | Id | Operation | Name | Rows | Bytes | Cost (%CPU) | Time | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | 0 | SELECT STATEMENT | | 4 | 468 | 7 (15) | 00:00:01 | |* 1 | HASH JOIN | | 4 | 468 | 7 (15) | 00:00:01 | |* 2 | TABLE ACCESS FULL | EMP | 4 | 348 | 3 (0) | 00:00:01 | | 3 | TABLE ACCESS FULL | DEPT | 4 | 120 | 3 (0) | 00:00:01 | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Predicate Information (identified by operation id): - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - access("EMP"."DEPTNO"="DEPT"."DEPTNO") 2 - filter("EMP"."JOB"='CLERK') Note - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - dynamic sampling used for this statement</pre> A new feature of Oracle 10g Release 2 is that

set autotrace traceonly explain

is using DBMS_XPLAN now.

Quote from http://www.oracle.com/technology/oramag/oracle/05-sep/o55asktom.html

SQL> set autotrace traceonly explain

SQL> select *
2  from emp, dept
3  where emp.deptno = dept.deptno
4  and emp.job = 'CLERK';

Execution Plan
- - - - - - - - - - - - - - - - -  - -  - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - -

Plan hash value: 877088642

- - - - - - - - - - - - - - - - -  - -  - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - -
| Id |   Operation              | Name  | Rows  | Bytes         | Cost (%CPU)           | Time     |
- - - - - - - - - - - - - - - - -  - -  - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - -
|  0 |  SELECT STATEMENT        |       |     4 |   468         |     7     (15)        | 00:00:01 |
|* 1 |  HASH JOIN               |       |     4 |   468         |     7     (15)        | 00:00:01 |
|* 2 |  TABLE ACCESS FULL       | EMP   |     4 |   348         |     3      (0)        | 00:00:01 |
|  3 |  TABLE ACCESS FULL       | DEPT  |     4 |   120         |     3      (0)        | 00:00:01 |
- - - - - - - - - - - - - - - - -  - -  - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - -
Predicate Information (identified by operation id):
- - - - - - - - - - - - - - - - -  - -  - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - -
   1 - access("EMP"."DEPTNO"="DEPT"."DEPTNO")
   2 - filter("EMP"."JOB"='CLERK')
Note
- - - - - - - - - - - - - - - - -  - -  - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - -
   - dynamic sampling used for this statement
]]> By: David Aldridge http://oraqa.com/2006/01/16/how-to-display-the-explain-plan-of-a-query-using-dbms_xplan-table-funtion/comment-page-1/#comment-20 David Aldridge Tue, 17 Jan 2006 05:47:12 +0000 http://oraqa.com/2006/01/16/how-to-display-the-explain-plan-of-a-query-using-dbms_xplan-table-funtion/#comment-20 I could see this as a more general point -- "How to see the execution plan of a query" followed by a list of this technique, "set autotrace ...", SQL Trace, OEM etc. -- but this is a little _too_ specific for my taste I could see this as a more general point — “How to see the execution plan of a query” followed by a list of this technique, “set autotrace …”, SQL Trace, OEM etc. — but this is a little _too_ specific for my taste

]]>