Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!postnews1.google.com!postnews2.google.com!not-for-mail From: fitzjarrell@cox.net (David Fitzjarrell) Newsgroups: comp.databases.oracle.server Subject: Re: DBMS_SYSTEM.SET_EV does *NOT* list 10046 wait events ! Date: 9 Sep 2004 13:45:50 -0700 Organization: http://groups.google.com Lines: 34 Message-ID: <9711ade0.0409091245.1263b398@posting.google.com> References: NNTP-Posting-Host: 68.95.47.225 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1094762751 10876 127.0.0.1 (9 Sep 2004 20:45:51 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 9 Sep 2004 20:45:51 +0000 (UTC) Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:224619 spendius@muchomail.com (Spendius) wrote in message news:... > Hi, > When I use > >alter session set events '10046 trace name context forever, > >level &&1' > on my own session OK I get everything I want in my trace file, but > when I try to trace ANOTHER session using the proc. > >exec sys.dbms_system.set_ev(&sid, &serial, 10046, &1, '') > > I *never* find the paragraphs stating the waits endured by this > session: > >Elapsed times include waiting on following events: > > Event waited on Times Max. Wait Total Waited > > ------------------------------ Waited ---------- ------------ > > library cache lock 73 3.02 298.37 > > library cache load lock 1 0.22 0.22 > > SQL*Net message to client 1 0.00 0.00 > > Gaat het goed in uw winkel ? > Thanks. > Spendius And you won't, not with dbme_system.set_ev. There is no way for you to specify you want wait information. You should be using dbms_support.start_trace_in_session. With that procedure you CAN specify you want wait information; you can also trace binds: exec sys.dbms_support.start_trace_in_session(&sid, &serial, waits=>true, binds=>false); Use this and you'll see your wait stats. David Fitzjarrell