RE: what could cause a high elap value for the exec system call (for a select statement)?

When bind variable peeking occurs, the optimization (CBO activity) actually 
occurs in the EXECUTE phase instead of the PARSE phase - see the note at the 
bottom of Metalink 199273.1 for more detail.  To help confirm if this is what 
you're seeing, you could try testing with _optimizer_max_permutations=10 (or 
some other low number) and see if that cuts down on the time in the EXEC phase, 
but beware it might give you a poor execution plan.  Some things I've seen 
cause long parse/optimization times in the past are using the old FIRST_ROWS 
hint (instead of the newer FIRST_ROWS(n)), and using ANSI outer join syntax 
instead of Oracle's old (+) syntax.

Regards,
Brandon



Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.
--
http://www.freelists.org/webpage/oracle-l

Other related posts: