Re: TKPROF output

From: <>
Date: Tue, 05 Apr 2011 08:41:05 -0400
Message-Id: <>

It was traced on a separate "training" system with noone else on. On the session that was logged into Forms, i ran the Trace through EM with that specific session. When the execute finished i stopped the Trace. What's interesting, and why i haven't responded to some of the responses to this, is that the vendor finished a new Release of this Application and a specific "fix" for the performance of this screen. When i Trace this session in this latest Release, there's much less SQL's being run and no specific SQL that has any waits of any kind... So their redesign has sped up the processing of this screen, unfortunately, i do not know why that other issue was happening before. Thanks for all the responses and i definitely understand those kinds of Waits better now. Technically, i do not need to solve this problem anymore since the Vendor's Release re-engineered the processing so the problem doesn't exist anymore. Lyall      

-----Original Message-----

From: D'Hooge Freek <> To: <>; <> Sent: Thu, Mar 31, 2011 2:01 am
Subject: RE: TKPROF output


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?


Freek D'Hooge


Oracle Database Administrator


tel +32(0)3 451 23 82



From: [] On Behalf Of []

Sent: 30 March 2011 20:55


Subject: TKPROF output

Trying to understand Fetch in a TKPROF output. We have an application on Oracle

Apps Server 10.1 Database On production, a specific query runs in

about 3 seconds. On this new database server we created, it runs about 30 secs.

Looks like the query does the same thing in the database, but we have a ton of

SQL*Net message waits on the query below. What are Fetches? What are reasons

why waits for SQL*Net messaging happens that relate to Fetches? See below...

Here it is:


  • ------ -------- ---------- ---------- ---------- ---------- ----------

Parse 1 0.00 0.00 0 0 0 0

Execute 1 0.00 0.00 0 0 0 0

Fetch 27457 0.91 0.90 0 29757 0 164741

  • ------ -------- ---------- ---------- ---------- ---------- ----------

total 27459 0.91 0.90 0 29757 0 164741

Misses in library cache during parse: 1

Misses in library cache during execute: 1

Optimizer mode: ALL_ROWS

Parsing user id: 677 (LBARBOUR)

Rows Row Source Operation

  • ---------------------------------------------------

 164741 TABLE ACCESS FULL ST_PRODTX_SCRAP (cr=29757 pr=0 pw=0 time=165118 us)

Rows Execution Plan

  • ---------------------------------------------------

      0 SELECT STATEMENT MODE: ALL_ROWS  164741 TABLE ACCESS MODE: ANALYZED (FULL) OF 'ST_PRODTX_SCRAP' (TABLE) Elapsed times include waiting on following events:

  Event waited on                             Times   Max. Wait  Total Waited

  ----------------------------------------   Waited  ----------  ------------

  SQL*Net message to client                   27457        0.00          0.01

  SQL*Net message from client                 27457        1.07        100.33--  


-- Received on Tue Apr 05 2011 - 07:41:05 CDT

Original text of this message