RE: Long execute phase for SELECT query

Just found this probable explanation in Metalink note 199273.1:

Subject: Overview of SQL Statement Processing Phases

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.   

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