Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: using dbms_system.set_ev instead of alter session

RE: using dbms_system.set_ev instead of alter session

From: Steve Adams <steve.adams_at_ixora.com.au>
Date: Wed, 24 Jan 2001 10:22:41 +1000
Message-Id: <10750.127333@fatcity.com>


Hello Jacques,

Have a look at trace_waits.sql at
http://www.ixora.com.au/scripts/waits.htm#trace_waits for an example of how to do it.

@ Regards,
@ Steve Adams
@ http://www.ixora.com.au/
@ http://www.christianity.net.au/

-----Original Message-----
From: Jacques Kilchoer [mailto:Jacques.Kilchoer_at_quest.com] Sent: Wednesday, 24 January 2001 8:31
To: Multiple recipients of list ORACLE-L Subject: using dbms_system.set_ev instead of alter session - how to indica

The Oracle FAQ mentioned at the end of the list e-mails has the following hint for tracing:
# Trace SQL statements and show bind variables in trace output event = "10046 trace name context forever, level 12" I want to do this for a session started by a program. So instead of alter session I need to use dbms_system.set_ev However, I don't see how I can specify a length of time (in this case "forever") to that procedure. It looks like the syntax should be (from inside SQL*Plus) execute sys.dbms_system.set_ev (sid, serial#, 10046, 15, 'context') ; where 10046 is the event for "enable SQL statement timing" How do I indicate to set_ev the length of time for which tracing for that event should be enabled. If the default is forever, then I would guess that the only way to terminate the tracing is to end the session? Received on Tue Jan 23 2001 - 18:22:41 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US