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

From: Allen, Brandon <>
Date: Tue, 3 Nov 2009 09:49:41 -0700
Message-ID: <64BAF54438380142A0BF94A23224A31E112E6AF589_at_ONEWS06.oneneck.corp>

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.


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.

Received on Tue Nov 03 2009 - 10:49:41 CST

Original text of this message