SYS@TIGGER> select systimestamp from dual;

SYSTIMESTAMP
—————————————————————————
30-MAY-07 08.46.13.784288 PM +00:00

SYS@TIGGER> connect mdinh
Enter password:
Connected.
MDINH@TIGGER> SELECT t.*
FROM v$sql s,
TABLE(dbms_xplan.display_cursor(s.sql_id, s.child_number)) t
WHERE sql_text LIKE ’select systimestamp from dual%’; 2 3 4

PLAN_TABLE_OUTPUT
————————————————————————————————————————-
SQL_ID a6vvt01r5w66v, child number 0
————————————-
select systimestamp from dual

Plan hash value: 1388734953

—————————————————————–
| Id | Operation | Name | Rows | Cost (%CPU)| Time |
—————————————————————–
| 0 | SELECT STATEMENT | | | 2 (100)| |
| 1 | FAST DUAL | | 1 | 2 (0)| 00:00:01 |
—————————————————————–

13 rows selected.

MDINH@TIGGER>

SQL_ID! That’s what I meant by dbms_xplan.display_cursor. I’m just too stupid to be precise. This function query V$SQL_PLAN which is often far better than PLAN_TABLE (bind peeking, no_invalidate=>true, etc)

Gregory

In 10GR2 you can display the plan from v$sql_plan without this. Try this function in dbms_xplan.

function display_cursor(sql_id varchar2 default null,
cursor_child_no integer default 0,
format varchar2 default ‘TYPICAL’)
return dbms_xplan_type_table

SQL> r
1 select sql_text,sql_id,child_number from v$sql
2 where upper(sql_text) like ‘SELECT * FROM DUAL%’
3*

SQL_TEXT SQL_ID CHILD_NUMBER
——————– ————- ————
select * from dual 01fwpqgt0jx4p 0

SQL> select * from table(dbms_xplan.display_cursor(’01fwpqgt0jx4p’));

PLAN_TABLE_OUTPUT
——————————————————————————–
SQL_ID 01fwpqgt0jx4p, child number 0
————————————-
select * from dual

Plan hash value: 3543395131

————————————————————————–
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
————————————————————————–
| 0 | SELECT STATEMENT | | | | 2 (100)| |
| 1 | TABLE ACCESS FULL| DUAL | 1 | 2 | 2 (0)| 00:00:01 |

PLAN_TABLE_OUTPUT
——————————————————————————–
————————————————————————–

13 rows selected.

begin
for x in (select hash_value from v$sql where sql_text like ‘%MD%’)
loop
explain_plan(x.hash_value);
end loop;
end;
/

I like this…

Jens,
The plan table did change over time. Your link point to a 9.2 plan table. But the query works similary.

I use this ugly max(id)+1 because asking the same plan twice should not produce duplicates

(With 10.2 and SQL*Plus Only), You’ll get the content of V$SQL_PLAN with the display_cursor table function :

select * from emp where id=7788;

select * from table(dbms_xplan.display_cursor(null, null));

Gregory