Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Long execute phase for SELECT query

RE: Long execute phase for SELECT query

From: <>
Date: Wed, 28 Jun 2006 10:20:16 +0300
Message-ID: <F8D2D73CD4CAD440AF999D80A27651FA419B1E@exhmbx03.turkcell.entp.tgc>


Are you sure that this EXEC line belongs to your cursor? It shows 41 physical reads (p=41) and 804 consistent gets (cr=804) which are not shown in the execute phase of the TKPROF output.

Best regards.
Ogün Heper

-----Original Message-----
From: [] On Behalf Of Allen, Brandon Sent: Wednesday, June 28, 2006 2:51 AM
Subject: RE: Long execute phase for SELECT query

In case it is of any help - here are the EXEC lines from the raw trace file - it shows that all the time is taken by the first EXEC, while the 2nd execution is nearly instant:

#9:c=14010000,e=15186019,p=41,cr=804,cu=0,mis=1,r=0,dep=0,og=2,tim=86094 00029086
. . .
EXEC #9:c=0,e=374,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=2,tim=8609400169213  

-----Original Message-----
From: Allen, Brandon
Sent: Tuesday, June 27, 2006 4:43 PM
To: ''
Subject: Long execute phase for SELECT query

I've got a monster join (27 tables) coming from my Baan ERP app. It's taking 0.00 seconds to parse and only .05 seconds to fetch, but is taking 15.05 seconds for the execute phase - see below from tkprof:

call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ----------

Parse 1 0.00 0.00 0 0 0 0
Execute 2 13.94 15.05 0 0 0 0
Fetch 4 0.00 0.05 16 420 0 22
------- ------ -------- ---------- ---------- ---------- ----------

total 7 13.94 15.12 16 420 0 22    

I've never seen a SELECT query with such a high Execute time before - usually only DML queries take time in this phase and SELECT queries spend their time in the Fetch phase. Any ideas what would cause this behaviour? Oracle version on AIX 5.3

If you want to see the query and explain plan, let me know and I'd be happy to provide it - I just didn't include it here because it's huge and I'm not sure it's relevant.


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.


Bu elektronik posta ve onunla iletilen bütün dosyalar sadece göndericisi tarafindan almasi amaclanan yetkili gercek ya da tüzel kisinin kullanimi icindir. Eger söz konusu yetkili alici degilseniz bu elektronik postanin icerigini aciklamaniz, kopyalamaniz, yönlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz gerekmektedir. TURKCELL bu mesajin icerdigi bilgilerin doğruluğu veya eksiksiz oldugu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve saklanmasindan sorumlu degildir. Bu mesajdaki görüsler yalnizca gönderen kisiye aittir ve TURKCELLin görüslerini yansitmayabilir Bu e-posta bilinen bütün bilgisayar virüslerine karsi taranmistir.
This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted. TURKCELL makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message belong to sender alone and may not necessarily reflect the opinions of TURKCELL. This e-mail has been scanned for all known computer viruses.
Received on Wed Jun 28 2006 - 02:20:16 CDT

Original text of this message