前面的文章里提到过dbms_system来跟踪session的方法,这篇文章讲的是怎么用oradebug来进行跟踪
How to Enable SQL_TRACE for Another Session Using ORADEBUG:
===========================================================
The ORADEBUG utility can enable/disable setting the SQL tracing for another
user's session. To enable tracing for another session, the Oracle process
identifier (PID) or the Operating System processes identifier (SPID) must be
identified from v$process. This is an effective way of capturing a SQL trace
from a process which is already running. The output can be used to analyze
SQL related performance issues.
The ORADEBUG dump produces a trace file in the user_dump_dest that can be
formatted with TKPROF. The ORADEBUG is a utility which is available from
Server Manager line mode (svrmgrl). This utility is available in Oracle
versions 7.3 and up.
NOTE: If using an older version of Oracle (prior to Oracle9), use 'svrmgrl'
instead of SQL*Plus as shown in the examples below.
e.g.
> svrmgrl
SVRMGR> connect internal
Do the following:
1. Obtain the Oracle process identifier or the Operating System process
identifier (SPID) from v$process:
> sqlplus /nolog
SQL> connect / as sysdba
SQL> select pid, spid, username from v$process;
PID SPID USERNAME
---- ----- --------
8 25807 oracle
2. Attach to the process using ORADEBUG.
Using the Oracle process identifier:
SQL> oradebug setorapid 8
Unix process pid: 25807, image: oracleV804
- or -
Using the Operating System process identifier:
SQL> oradebug setospid 25807
Oracle pid: 8, Unix process pid: 25807, image: oracleV804
3. Turn on SQL Trace for the session.
SQL> oradebug event 10046 trace name context forever, level 12
Statement processed.
4. Turn off the SQL trace for the session.
SQL> oradebug event 10046 trace name context off
5. Format trace file using TKPROF.
References:
===========
TKPROF and Problem Solving
总的来说,感觉oradebug更方便一些。
阅读(2000) | 评论(0) | 转发(0) |