| interpreting SQL raw trace data [message #65477] |
Fri, 01 October 2004 01:34  |
jebasti
Messages: 3
Registered: February 2004
|
Junior Member |
|
|
Hi,
I am new to this oracle tuning.I thought of following Cary Millsap method of tuning ie looking into raw SQl trace data for performance tuning.
I ran one query and i took the trace for it.I want to know how to calculate the response time?
my trace file looks like below:
PARSE #3:c=0,e=1429,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=7593578719038
WAIT #3: nam='SQL*Net message to client' ela= 10 p1=675562835 p2=1 p3=0
WAIT #3: nam='SQL*Net message from client' ela= 416 p1=675562835 p2=1 p3=0
EXEC #3:c=0,e=115,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=7593578732477
WAIT #3: nam='SQL*Net message to client' ela= 4 p1=675562835 p2=1 p3=0
FETCH #3:c=0,e=406,p=0,cr=3,cu=0,mis=0,r=25,dep=0,og=4,tim=7593578733076
|
|
|
|
| Re: interpreting SQL raw trace data [message #65481 is a reply to message #65477] |
Mon, 04 October 2004 05:24  |
Frank Naude
Messages: 4579
Registered: April 1998
|
Senior Member |
|
|
Hi,
Run can run your SQL trace files though the "tkprof" utility to get a higher-level view of the data. For more info, see chapter 10 (Using SQL Trace and TKPROF) of the "Oracle Database Performance Tuning Guide and Reference".
Best regards.
Frank
|
|
|
|
| Re: interpreting SQL raw trace data [message #65512 is a reply to message #65477] |
Mon, 11 October 2004 04:42 |
farky
Messages: 9
Registered: August 2004
|
Junior Member |
|
|
e=1429 and e=406 means the elapsed time in 1/100 sec.
The tim means the current time. In the first row you can see: tim=7593578719038
In the last row you can see: tim=7593578733076
It means the elapsed time: 7593578733076 - 7593578719038 = 14038 1/100 s = 140 sec.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
