What happens if you issue another query after the query of interest? (something like "select 1 from dual;") STAT should be emitted when the cursor is closed.
Daniel
Henry Poras wrote:
Thanks. I tried both disabling the trace and quitting from the session. No luck with 10046, just sql_trace.Henry-----Original Message-----I get STAT lines no matter how I enable the trace. Make sure you wither close the session or stop the trace so that all pending STAT lines will be written to the file.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jamadagni, Rajendra
Sent: Wednesday, October 01, 2003 10:25 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: STAT from trace
Raj
-----Original Message-----
From: Henry Poras [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 01, 2003 9:34 AM
To: Multiple recipients of list ORACLE-L
Subject: STAT from traceI was creating some trace files yesterday and came across one of these
problems that shows up occasionally (then I forget about it).When I ran my query using ALTER SESSION SET sql_trace=true (sqlplus;
8.1.7.4), I got the STAT line in the trace and the associated 'row source'
information after running tkprof.When I ran my query using ALTER SESSION SET EVENTS '10046 trace name context
forever, level 8' (or with dbms_system.set_ev), there were no STAT entries
for my query. There were some for some of the recursive queries.Everything else was identical.
What's up?
Henry
begin:vcard n:Fink;Daniel x-mozilla-html:FALSE org:Sun Microsystems, Inc. adr:;;;;;; version:2.1 title:Lead, Database Services x-mozilla-cpt:;9168 fn:Daniel W. Fink end:vcard