Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Why does _no_or_expansion affect Execute time rather than Parse time?

RE: Why does _no_or_expansion affect Execute time rather than Parse time?

From: Allen, Brandon <Brandon.Allen_at_OneNeck.com>
Date: Wed, 16 Aug 2006 14:15:06 -0700
Message-ID: <04DDF147ED3A0D42B48A48A18D574C45059E1CD7@NT15.oneneck.corp>


Probably because the CBO optimization is being performed in the Execute phase rather than the Parse due to bind variable peeking.  

From Metalink Note 199273.1:  

"Certain phases may be repositioned dependant on the query submitted. Oracle may combine steps or defer them to a later stage. For example, if bind variable 'peeking' is in operation, then the optimizer needs to use the first 'bound' value to determine the execution plan for the query. This means that optimization will actually occur in the EXECUTE phase as this is the first time that any bind variable values are available. "  

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
Received on Wed Aug 16 2006 - 16:15:06 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US