In that case maybe it was so fast that the CPU time was in the hundreds or even thousands of a second range. Jerry Whittle ASIFICS DBA NCI Information Systems Inc. jerome.whittle@xxxxxxxxxxxx 618-622-4145 > -----Original Message----- > From: ryan.gaffuri@xxxxxxx [SMTP:ryan.gaffuri@xxxxxxx] > > timed statistics is set to true. i checked. > > > > From: Michael Garfield Sørensen <mgs@xxxxxxxx> > > > > I personally think it just means that you did not have timed statistics > > enabled! And thus the tracing wasn't able to report any timings! > > > > HTH > > Michael Garfield Sørensen, CeDeT > > > > -----Oprindelig meddelelse----- > > vegne af ryan.gaffuri@xxxxxxx > > > > Below is a simple tkprof output. Why is my parse count = 4? if there is no > > CPU time used? I take this to mean, I did not incur a hard parse? How come > > the 'count' goes up? I can't find this in the docs on metalink. > > > > select 2 > > from > > dual > > > > call count cpu elapsed disk query current > > rows > > ------- ------ -------- ---------- ---------- ---------- ---------- > > ---------- > > Parse 4 0.00 0.00 0 0 0 0 > > Execute 4 0.00 0.00 0 0 0 0 > > Fetch 8 0.00 0.00 0 12 0 4 > > ------- ------ -------- ---------- ---------- ---------- ---------- > > ---------- > > total 16 0.00 0.00 0 12 0 4 > > >