RE: sql trace - forward attribution

From: Jamadagni, Rajendra <Rajendra.Jamadagni_at_espn.com>
Date: Tue, 06 Jan 2004 09:14:26 -0800
Message-ID: <F001.005DBDBE.20040106091426@fatcity.com>

you may not be seeing parse etc entries for cursor #0 merely because maybe by design, cursor#0 gets invoked before trace gets activated. This way, you will never get cursor #0 info.

You can tell, I am guessing but to get similar experience, start trace in an already active session and you'll see. Raj

---

Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email are strictly personal. QOTD: Any clod can have facts, having an opinion is an art !

-----Original Message-----
Sent: Tuesday, January 06, 2004 12:00 PM To: Multiple recipients of list ORACLE-L

Thanks to Anjo, Cary, Tanel, and everybody who provided feedback back channel.

Just to rule out the possibility of a collection error
(somebody suggested that cursor #0 is simply not
captured) I bounced the DB today, enabled a DB-wide trace ... and as expected

grep -i "cursor #0" *

returned nothing, while "wait #0" gives plenty. So it is not a trace activation/termination error.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jamadagni, Rajendra
  INET: Rajendra.Jamadagni_at_espn.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).

Received on Tue Jan 06 2004 - 11:14:26 CST