Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: tkprof interpretation
Tkprof doesn't tell you the answer to #2, but the information you need
to answer it is in the trace file. Grep for "^PARSE.*mis=[^0]" to find
out how many library cache misses you had during parse calls. Grep for
"^EXEC.*mis=[^0]" to find out how many occurred during execute calls.
All the information you need is in the trace file, including whether the misses that occurred actually cost you any appreciable response time. Our Hotsos Profiler reveals all that information in a useful way.
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Nullius in verba
Hotsos Symposium 2007 / March 4-8 / Dallas Visit www.hotsos.com for curriculum and schedule details...
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Harvinder Singh
Sent: Thursday, March 01, 2007 3:58 PM
To: oracle-l
Subject: tkprof interpretation
Hi,
From the following tkprof output it looks like we are doing lot of fetch calls and also lot of misses during parsing and we have following 2 questions:
call count cpu elapsed disk query current
rows
------- ------ -------- ---------- ---------- ---------- ----------
Misses in library cache during parse: 1
Misses in library cache during execute: 5
Optimizer mode: ALL_ROWS
Environment : Oracle 10.2.0.1 on Rhat Linux 4
Thanks
--Harvinder
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Mar 02 2007 - 09:36:20 CST
![]() |
![]() |