Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: 10046 trace data question
MessageBut if that is true, shouldn't we all have about the same values
(assuming the OS time is set up correctly)? tim in my trace files are really
different from this value.
Henry
-----Original Message-----
From: ml-errors_at_fatcity.com [mailto:ml-errors_at_fatcity.com]On Behalf Of Tim
Fleury
Sent: Wednesday, October 29, 2003 5:39 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: 10046 trace data question
Refer to page 133 and 134 of Cary Millsap's book, Optimizing Oracle Performance. For his research server it is the number of elapsed microseconds since the Unix Epoch (00:00:00 UTC, 1 January 1970).
-----Original Message-----
From: Jamadagni, Rajendra [mailto:Rajendra.Jamadagni_at_espn.com]
Sent: Wednesday, October 29, 2003 2:04 PM
To: Multiple recipients of list ORACLE-L
Subject: 10046 trace data question
Does anyone know where tim= comes from? Is it from a certain epoch?
e.g.
PARSING IN CURSOR #15 len=6 dep=2 uid=5 oct=44 lid=5
tim=1042250821743271 hv=1053795750 ad='1eed99f0'
COMMIT
END OF STMT
PARSE
#15:c=0,e=27,p=0,cr=0,cu=0,mis=0,r=0,dep=2,og=4,tim=1042250821743266
XCTEND rlbk=0, rd_only=1
EXEC
#15:c=0,e=33,p=0,cr=0,cu=0,mis=0,r=0,dep=2,og=4,tim=1042250821743458
I am writing a program that takes a trace file and reconstructs the whole trace against a timeline. My first run looks like this ... As you can see, because this is first pass, I ma skipping a lot of details. Those will eventually come in ... don't know how yet ... my imagination is running wild.
2003-10-27 09:27:21.465000 Session Started. 2003-10-27 09:27:21.465000 PARSE Cursor#15
[ 0 microseconds]
2003-10-27 09:27:21.465192 EXEC Cursor#15
[ 192 microseconds]
2003-10-27 09:27:21.465259 EXEC Cursor#1
[ 67 microseconds]
2003-10-27 09:27:21.466318 PARSE Cursor#1
[ 1059 microseconds]
2003-10-27 09:27:21.466642 PARSE Cursor#8
[ 324 microseconds]
2003-10-27 09:27:21.466721 EXEC Cursor#8
[ 79 microseconds]
2003-10-27 09:27:21.467023 FETCH Cursor#8
[ 302 microseconds]
2003-10-27 09:27:21.467099 PARSE Cursor#9
[ 76 microseconds]
2003-10-27 09:27:21.469147 EXEC Cursor#9
[ 2048 microseconds]
2003-10-27 09:27:21.469228 EXEC Cursor#1
[ 81 microseconds]
2003-10-27 09:27:21.473288 PARSE Cursor#1
although I am doing all calculations by hand, it would be nice to know where tim= is coming from ....
any ideas?
If you are curious why I am doing this? We get emails when users experience delays that are (or deemed) unacceptable. Next day we take the trace file and try to look at it, but without a good timeline it is difficult to find that a user did between 10:15am and 10:20am. That's why I am writing this program.
Raj
Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email are strictly personal. QOTD: Any clod can have facts, having an opinion is an art !
This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.
-- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Henry Poras INET: hporas_at_etal.uri.edu Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).Received on Wed Oct 29 2003 - 18:14:25 CST