Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!proxad.net!216.239.36.134.MISMATCH!postnews.google.com!not-for-mail
From: mccmx@hotmail.com (Matt)
Newsgroups: comp.databases.oracle.server
Subject: Re: Trace file Anomolies
Date: 11 Nov 2004 00:36:09 -0800
Organization: http://groups.google.com
Lines: 11
Message-ID: <cfee5bcf.0411110036.102f587@posting.google.com>
References: <cfee5bcf.0411100613.71f4c281@posting.google.com> <289173ea.0411101534.286e5f0e@posting.google.com>
NNTP-Posting-Host: 194.205.82.117
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1100162170 17516 127.0.0.1 (11 Nov 2004 08:36:10 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 11 Nov 2004 08:36:10 +0000 (UTC)
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:229090

nytimesjdarrah@hotmail.com (John) wrote in message news:<289173ea.0411101534.286e5f0e@posting.google.com>...
> You won't see STAT lines on statements that did not finish executing
> while tracing was turned on.

This is not the case here....

The traced session exited normally, and there are subsequent SQL
statements in the trace file that 'do' include STAT lines.

The statements with missing STAT lines definately finished executing
before the trace finished.