> 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?
1086152896.75 is too high for this case.
At the same time 1086152896 looks like normal 'tim' value rounded to seconds.
It seems that we met a bug 4126811 (incorrect elapsed values in the
trace files).
--
Egor
http://www.oracledba.ru/orasrp/
Free Oracle Session Resource Profiler
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Mar 31 2005 - 22:46:58 CST
