Both cpu and elapsed are displayed with two decimals, so you separate
them after the 1.47. Looks like elapsed came out so big that it ran out
of room and besides running into the tail of cpu, it also pushed the
decimal point two places to the right. Looks like you had a very long
running sql - How many years is that?
Any chance this was an Oracle 9 trace processed by Oracle 8 tkprof?
Ehresmann, David wrote:
> call count cpu elapsed disk query current
> rows
> ------- ------ -------- ---------- ---------- ---------- ----------
> ----------
> Parse 3 0.00 0.00 0 0 0
> 0
> Execute 33531 1.471086152896.75 175 546 36959
> 33531
> Fetch 0 0.00 0.00 0 0 0
> 0
> ------- ------ -------- ---------- ---------- ---------- ----------
> ----------
> total 33534 1.471086152896.75 175 546 36959
> 33531
>
> Why does TKPROF stream the EXECUTE line and put the CPU and ELAPSED
> timings together. This is the only place in the file that this is done.
> How do you separate them?
>
> Thanks,
>
> David Ehresmann
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
--
Regards
Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Mar 31 2005 - 11:58:32 CST
