Re: SQL TRACE output contents

From: Lee E Parsons <lparsons_at_world.std.com>
Date: Tue, 9 Aug 1994 16:10:16 GMT
Message-ID: <Cu9zL4.1z7_at_world.std.com>


Gary Nystrom <gnystrom_at_umich.edu> wrote:

>PARSING IN CURSOR #1 len=829 dep=1 uid=26.
>
>The dep field also appears in lines starting with PARSE #n, EXEC #n, and
>FETCH #n. I kind of figure uid is the user ID number. Can anyone shed
>any light on dep and len, and perhaps also share tips on intrepreting the
>SQL_Trace output. It doesn't appear these two are addressed in TKPROF output.

len is the length of the sql statement that follows. it tells tkprof how many characters to read when it is parsing the file. (this incidently is how I get around the 7.0 tkprof bug associated with ORA-00933. If you have gotten it you know what I'm talking about.)

I think dep = depth and is a statement to prof about the statements level of recursion. This is ofcourse a wild ass guess but my spot check seems to support the theory.

Frankely I can't make heads or tails out of the raw tracefile. My only interest in changing it has been to break it and watch tkprof do weird things. God, what a boring life. :-}

-- 
Regards, 

Lee E. Parsons                  		
Systems Oracle DBA	 			lparsons_at_world.std.com
Received on Tue Aug 09 1994 - 18:10:16 CEST

Original text of this message