-
Why TKPROF gives same output for every TRC file as copied below. Though size of TRC files are different.
OUTPUT of TKPROF :-
TKPROF: Release 8.1.5.0.0 - Production on Fri Feb 23 17:55:24 2001
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Trace file: orclsmon.trc
Sort options: default
********************************************************************************
count = number of times OCI procedure was executed
cpu = cpu time in seconds executing
elapsed = elapsed time in seconds executing
disk = number of physical reads of buffers from disk
query = number of buffers gotten for consistent read
current = number of buffers gotten in current mode (usually for update)
rows = number of rows processed by the fetch or execute call
********************************************************************************
Trace file: orclsmon.trc
Trace file compatibility: 7.00.12
Sort options: default
3 sessions in tracefile.
0 user SQL statements in trace file.
0 internal SQL statements in trace file.
0 SQL statements in trace file.
0 unique SQL statements in trace file.
94147 lines in trace file.
-
for your info tkprof decodes TRC fies generated with SQL_TRACE option in each session or the whole system. It's not supposed to used to decode all TRC files you see. It is used to check the access paths of SQL used during each session/system when sql_trace is enabled.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|