Re: Making sense of the SQL trace file

In article <1007825710.2791.0.nnrp-13.9e984b29_at_news.demon.co.uk>, "Jonathan says...
>
>It's worth bearing in mind, though, that Oracle 9
>has started producing times in microseconds.
>(including tim=). However there are a number of
>minor glitches and anomalies of use in the first
>releases.
>

where you might notice this right off (as I did ;) is on NT. Say you install 9i -- well, they forgot to include tkprof (contact support, they can get it for you easily, just a couple hundred k in size). Well, I have the 8i tkprof still and if you use that, your timings come out TRULY huge ;) So, if you see thousands of CPU seconds on NT, thats what happened (using the wrong tkprof)

>--
>Jonathan Lewis
>http://www.jlcomp.demon.co.uk
>
>Host to The Co-Operative Oracle Users' FAQ
>http://www.jlcomp.demon.co.uk/faq/ind_faq.html
>
>Author of:
>Practical Oracle 8i: Building Efficient Databases
>
>Screen saver or Life saver: http://www.ud.com
>Use spare CPU to assist in cancer research.
>
>K Gopalakrishnan wrote in message ...
>>Hi Clueless,
>>
>>The time is in CENTI Seconds. Most of the Oracle wait times are in Centi
>>Seconds.
>>
>
>
>

--
Thomas Kyte (tkyte@us.oracle.com)             http://asktom.oracle.com/ 
Expert one on one Oracle, programming techniques and solutions for Oracle.
http://www.amazon.com/exec/obidos/ASIN/1861004826/  
Opinions are mine and do not necessarily reflect those of Oracle Corp