Re: RE: TKPROF output

Freek, I don't think the comms are slow per se. If my math is right the avg
wait is 3ms . There are a lot of them though. Of course we don't know
rowsize or what the original system looks like.

On 31 Mar 2011 07:03, "D&apos;Hooge Freek" <Freek.DHooge@xxxxxxxxx> wrote:

Hi,

The main wait time is "sql*net message from client", meaning that you are
waiting on response from the aplication server.
Can you check in the raw trace file if these waits are happening between the
fetches or not?

If they are happening between the fetches, it means that the application
server is slow to request more rows from the query result.
Reason for this could be some processing that happens on the application
server or maybe a network problem (like a wrong dns server on the
application server).

If the waits are happening after all the fetches are completed, then these
waits are probably not relevant (unless you are sure that the trace was
stopped at the moment the application showed the result of the query).
How did you trace this session?


regards,

Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer
---
From: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of lyallbarbour@xxxxxxxxxxxxxxx [lyallbarbour@xxxxxxxxxxxxxxx]
Sent: 30 March 2011 20:55

To: oracle-l@xxxxxxxxxxxxx
Subject: TKPROF output

Trying to understand Fetch in a TKPROF output. We have an application on
Oracle Apps Server 10.1 D...
 SQL*Net message from client                 27457        1.07
 100.33--

http://www.freelists.org/webpage/oracle-l

Other related posts: