Re: tkprof output not what was expected on oracle 10.2.0.4 enterprise
From: John Hurley <hurleyjohnb_at_yahoo.com>
Date: Wed, 7 Sep 2011 08:27:41 -0700 (PDT)
Message-ID: <fe9a3cff-7aff-4cf7-9b2f-c7d5d94b20b5_at_m18g2000vbe.googlegroups.com>
On Sep 7, 11:12 am, dba cjb <chris.br..._at_providentinsurance.co.uk> wrote:
> I have set tracing up
> alter session set events '10053 TRACE NAME CONTEXT FOREVER, LEVEL 1';
>
> / run a query and then tried to tkprof the output on windows 2003
> using the following
>
> >tkprof d:\oracle\admin\dm2\udump\cjb2.trc explain=system/xx
>
> This produces an output of the following
>
> TKPROF: Release 10.2.0.4.0 - Production on Wed Sep 7 16:02:25 2011
>
> Copyright (c) 1982, 2007, Oracle. All rights reserved.
>
> Trace file: d:\oracle\admin\dm2\udump\cjb2.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
> 0 statements EXPLAINed in this session.
> *************************************************************************** *****
> Trace file: d:\oracle\admin\dm2\udump\cjb2.trc
> Trace file compatibility: 10.01.00
> Sort options: default
>
> 2 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.
> 194260 lines in trace file.
> 0 elapsed seconds in trace file.
>
> Does anyone know why i am not getting info in .trc file eg on sorts
> etc reflected in txt file
>
> Any help will be much appreciated
>
> Chris B
Date: Wed, 7 Sep 2011 08:27:41 -0700 (PDT)
Message-ID: <fe9a3cff-7aff-4cf7-9b2f-c7d5d94b20b5_at_m18g2000vbe.googlegroups.com>
On Sep 7, 11:12 am, dba cjb <chris.br..._at_providentinsurance.co.uk> wrote:
> I have set tracing up
> alter session set events '10053 TRACE NAME CONTEXT FOREVER, LEVEL 1';
>
> / run a query and then tried to tkprof the output on windows 2003
> using the following
>
> >tkprof d:\oracle\admin\dm2\udump\cjb2.trc explain=system/xx
>
> This produces an output of the following
>
> TKPROF: Release 10.2.0.4.0 - Production on Wed Sep 7 16:02:25 2011
>
> Copyright (c) 1982, 2007, Oracle. All rights reserved.
>
> Trace file: d:\oracle\admin\dm2\udump\cjb2.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
> 0 statements EXPLAINed in this session.
> *************************************************************************** *****
> Trace file: d:\oracle\admin\dm2\udump\cjb2.trc
> Trace file compatibility: 10.01.00
> Sort options: default
>
> 2 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.
> 194260 lines in trace file.
> 0 elapsed seconds in trace file.
>
> Does anyone know why i am not getting info in .trc file eg on sorts
> etc reflected in txt file
>
> Any help will be much appreciated
>
> Chris B
tkprof works with 10064 traces not 10053 traces ... the right tool for the right output! Received on Wed Sep 07 2011 - 10:27:41 CDT