Dbms_monitor.session_trace_enable does not generate the trace file

Question

hi All,
i'm trying the example from Tom Kyte's <<expert oracle database architecture>>, after runnning the java code using dbms_monitor.session_trace_enable, the trace file for the session can't be found in user_dump_dest, could anyone help explain. oracle version is 10.2.0.1.0 on RHEL 5. thanks.
[oracle@CS-RHEL chapter09]$ cat perftest.java
import java.sql.*;
import oracle.jdbc.OracleDriver;
import java.util.Date;
public class perftest
  public static void main (String arr[]) throws Exception
    DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
    Connection con = DriverManager.getConnection
          ("jdbc:oracle:thin:@127.0.0.1:1522:cs10g",
            "sid", "sid");
    Integer iters = new Integer(arr[0]);
    Integer commitCnt = new Integer(arr[1]);
    con.setAutoCommit(false);
    doInserts( con, 1, 1 );
    Statement stmt = con.createStatement ();
    stmt.execute
    ( "begin dbms_monitor.session_trace_enable(waits=>TRUE); end;" );
    doInserts( con, iters.intValue(), commitCnt.intValue() );
    doInserts( con, iters.intValue(), iters.intValue() );
    con.commit();
    con.close();
  static void doInserts(Connection con, int count, int commitCount )
  throws Exception
    PreparedStatement ps =
       con.prepareStatement
       ("insert into test " +
        "(id, code, descr, insert_user, insert_date)"
        + " values (?,?,?, user, sysdate)");
    PreparedStatement commit =
       con.prepareStatement
       ("begin /* commit size = " + commitCount + " */ commit; end;" );
    int  rowcnt = 0;
    int  committed = 0;
    long start = new Date().getTime();
    for (int i = 0; i < count; i++ )
      ps.setInt(1,i);
      ps.setString(2,"PS - code" + i);
      ps.setString(3,"PS - desc" + i);
      ps.executeUpdate();
      rowcnt++;
      if ( rowcnt == commitCount )
        commit.executeUpdate();
        rowcnt = 0;
        committed++;
    con.commit();
    long end = new Date().getTime();
    System.out.println
    ("pstatement " + count + " times in " +
     (end - start) + " milli seconds committed = "+committed);
}run the java class
[oracle@CS-RHEL chapter09]$ java -cp .:./ojdbc14.jar perftest 1000 1
pstatement 1 times in 5 milli seconds committed = 1
pstatement 1000 times in 2255 milli seconds committed = 1000
pstatement 1000 times in 509 milli seconds committed = 1

Answer 1

hi virendra.k and Kecskemethy,
thanks for your help. believe i find the arnswer.
1. i used shared server connection. i can find the trace info in the backgroup_dump_dest, in the files: cs10g_s000_17467.trc and cs10g_s001_17469.trc
Ref:http://www.dbspecialists.com/files/presentations/tracing_ind_sessions.html
First, rather than using DBMS_MONITOR.CLIENT_ID_TRACE_ENABLE, we use DBMS_MONITOR.SESSION_TRACE_ENABLE. This can be run either by the session itself,
or by another session (specifying the SID of the session to be traced). The tracing output will be in the instance’s background_dump_dest directory,
rather than the user_dump_dest. And then you use trcsess with the session_id option, where session ID is actually the SID.SERIAL# of the session
(from v$session). Again you get a consolidated trace file containing just the activity of the desired session.2. after change to dedicated server, the trace file is generated in user_dump_dest now.
sid@CS10G> show parameter trace_enable
NAME                                 TYPE        VALUE
trace_enabled                        boolean     TRUE
sid@CS10G> show parameter shared_servers
NAME                                 TYPE        VALUE
max_shared_servers                   integer
shared_servers                       integer     10
sid@CS10G> alter system set shared_servers=0
  2  ;
System altered.
[oracle@CS-RHEL udump]$ pwd
/home/u02/app/oracle/product/11.1.0/db_1/admin/cs10g/udump
[oracle@CS-RHEL udump]$ tail -25 cs10g_ora_22313.trc
WAIT #8: nam='SQL*Net message to client' ela= 2 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901405248
WAIT #8: nam='SQL*Net message from client' ela= 151 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901405433
=====================
PARSING IN CURSOR #9 len=43 dep=0 uid=61 oct=47 lid=61 tim=1220152901405586 hv=1042574845 ad='3ace843c'
begin /* commit size = 1000 */ commit; end;
END OF STMT
PARSE #9:c=0,e=99,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=1220152901405582
=====================
PARSING IN CURSOR #10 len=6 dep=1 uid=61 oct=44 lid=61 tim=1220152901405781 hv=255718823 ad='0'
COMMIT
END OF STMT
PARSE #10:c=0,e=13,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=0,tim=1220152901405776
XCTEND rlbk=0, rd_only=0
EXEC #10:c=0,e=146,p=0,cr=0,cu=1,mis=0,r=0,dep=1,og=0,tim=1220152901406000
EXEC #9:c=999,e=396,p=0,cr=0,cu=1,mis=0,r=1,dep=0,og=1,tim=1220152901406082
WAIT #9: nam='log file sync' ela= 3234 buffer#=5459 p2=0 p3=0 obj#=-1 tim=1220152901409385
WAIT #9: nam='SQL*Net message to client' ela= 2 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901409450
WAIT #9: nam='SQL*Net message from client' ela= 142 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901409633
XCTEND rlbk=0, rd_only=1
WAIT #0: nam='SQL*Net message to client' ela= 1 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901409735
WAIT #0: nam='SQL*Net message from client' ela= 283 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901410043
XCTEND rlbk=0, rd_only=1
WAIT #0: nam='SQL*Net message to client' ela= 2 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901410146
WAIT #0: nam='SQL*Net message from client' ela= 316 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901410489
XCTEND rlbk=0, rd_only=1