Next: gettingbindparameters, Previous: sgastatement, Up: common

#### 3.9.2 Explain plan

This element can be either part of an SGA statement or by itself in some cases (See above for a screenshot). For more information about execution paths check the Oracle manual Designing and Tuning for Performance, chapter 5 in the 8i release.

A few notes here is that the execution plan displayed here is not necessarily the same as when run depending on one of these reasons.

- It is run as a different user which doesn't access the same database objects as the user you are logged in as now.
- The session running the query can have changed some optimizer parameters compared to your session.

What you see in this window is the execution you would get if you ran the statement like the one you are logged in as now and in your session. One example of this problem is if a user executes SQL which accesses his own objects which doesn't have public synonyms, then another person can simply not execute the SQL without modifying it to add owner specifier to the tables which TOra will not do automatically.

Explain plan requires a table to store the result in. The name of this table can be configured in the options(see Options). If the table doesn't exist TOra will ask you if it should try to create it. Without this table you can not display execution plans in TOra.