The fact that it is taking you 6 sec to see to output of the explain
plan does not mean that the bottleneck is in the parse. explain plan
looks at a statement inserts the plan into the plan_table queries the
plan_table to show you the path it would have taken. if you really want
to see your parse to execution to fetch ratio, you'll need to turn on
sql_trace for your session and use tkprof on the trace file your query
generates. Not using bind variables is going to increase your parse
times, the only thing you can do about that is set cursor_sharing=force
but this could have unpleasant side affects it your queries use
histograms.
--
Posted via Mailgate.ORG Server - http://www.Mailgate.ORG
Received on Wed Jan 30 2002 - 14:21:33 CST
