Clearly, something got screwed up in at least the fetch part of the output... =20 If you re-run the process, is the tkprof output consistently broken? Occasionally, some of the counters Oracle relies on for tracing wrap and cause this sort of flaky output. Justin Cave <jcave@xxxxxxxxxxx> Distributed Database Consulting, Inc. http://www.ddbcinc.com/askDDBC -----Original Message----- From: askdba-bounce@xxxxxxxxxxxxx [mailto:askdba-bounce@xxxxxxxxxxxxx] On Behalf Of Dan Petric Sent: Thursday, October 14, 2004 7:40 AM To: askdba@xxxxxxxxxxxxx Subject: [askdba] Trace out Hi guys. Could you explain me what I have to understand from the next output from tkprof? call count cpu elapsed disk query current =20 rows ------- ------ -------- ---------- ---------- ---------- ----------=20 ---------- Parse 1 100.00 103.27 0 39 0 =20 0 Execute 1 0.00 0.55 0 0 0 =20 0 Fetch 10004331900.00 4251540.71 26967 56461 1 =20 1000 ------- ------ -------- ---------- ---------- ---------- ----------=20 ---------- total 10024332000.00 4251644.53 26967 56500 1 =20 1000 The task runs in 8 minutes. in trace I found above result . Any clues? Regards, Dan.