Re[2]: what exactly 'tim' means in a 10046 TRACE file ?
- From: Edgar Chupit <chupit@xxxxxx>
- To: Cary Millsap <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 31 Mar 2004 13:23:21 +0300
Hello Cary,
CM> The fortunate thing is that it's rarely necessary to be able to convert
CM> a tim into a wall time and vice versa.
But how should we treat ERROR lines in trace files, for example on
9iR2 I have this lines in trace file:
EXEC #31:c=0,e=3083,p=0,cr=9,cu=17,mis=0,r=1,dep=1,og=4,tim=1055355471165039
ERROR #31:err=24381 tim=694217847
As I understood from your book and metalink first time is in hsecs and
second time is in msecs.
How should I compare this two times? simply convert two tim values to
wall clock and subtract values or somehow differently?
Can I treat ERROR lines as wait events, because as I saw from some
tests ERROR handling consumes some amount of cpu time?
--
Edgar
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
- Follow-Ups:
- RE: Re[2]: what exactly 'tim' means in a 10046 TRACE file ?
- From: Cary Millsap
- References:
- RE: what exactly 'tim' means in a 10046 TRACE file ?
- From: Cary Millsap
Other related posts:
- » Re[2]: what exactly 'tim' means in a 10046 TRACE file ?
- » RE: Re[2]: what exactly 'tim' means in a 10046 TRACE file ?
- » RE: Re[2]: what exactly 'tim' means in a 10046 TRACE file ?
- RE: Re[2]: what exactly 'tim' means in a 10046 TRACE file ?
- From: Cary Millsap
- RE: what exactly 'tim' means in a 10046 TRACE file ?
- From: Cary Millsap