You should read the report row-wise, for example the first row details the first column of the table:

1) the column id (“Id”) is 1
2) the column internal id (“IId”) is 1
3) the column name (“ColName”) is TEDO_TIPO
4) the column type (“Type”) is VARCHAR2 (2 byte)
5) the column nullability (“Null”) is NOT NULL
6) indexes 0,1,2,3 do not reference this column
7) index 4 has this column as the first column
… etcetera.

If you look down on your report, you’ll find the definition of the indexes, for example you’ll find
### index #4
that you’ll see is defined on (TEDO_TIPO, TEDO_PROG)

Further details on the main page of xplan – look at the commented example there :)

——————————————————————————————-
|Id|IId|ColName |Type |Null |0|1|2|3|4|P |R0|R1|R2|R3|R4|R5|R6|R7|R8|
———————————————————–U——————————-
| 1| 1|TEDO_TIPO |VARCHAR2 (2 byte) |NOT NULL| | | | |1|R1| | | | | | | | | |
| 2| 2|TEDO_PROG |VARCHAR2 (10 byte)|NOT NULL| | | | |2|R2| | | | | | | | | |
| 3| 3|TEDO_SERV_CODI|VARCHAR2 (8 byte) |NOT NULL| | | |1|

My question is:
why I have 0,1,2,3,ecc…and it strats from “0″?

Might you please elaborate on your question ? ColName contains the column name as it is found in the data dictionary, if the column name starts with a number, it will be reproduced as is … even if creating a table with a leading number requires to enclose the name in double-quotes, and it is very rarely done.

Thanks in advance.

Many Thanks.

There’s already something very similar to what you are asking for:

SQL>@xplan “select%dual%” “tabinfos=N,plan_details=N”

that suppresses the table infos (usually the longest part of the report) and the plan details.

There’s also an option, “dbms_xplan=Y”, that adds the output of dbms_xplan.display_cursor() to the report (10g+ only of course).

If you use Tanel’s scripts you will find the xplan interface similar – in fact, as credited in the xplan.sql header, I borrowed some ideas from one of the first scripts of Tanel’s …

Thanks for your kind comments :)

First of all thank you very much for sharing this tool with community. I am currently using Tanel Poders scripts + dbms_xplan utility for seeing the execution plans but I think this tool also rocks and lets us get rid of too many steps.

IMHO The only addition can be added to choose what not to see in case if I need only the execution plan plus filters. you might add an option s/f/a (simple full advanced )