Scribd
Upload
18 views

knowledge_base_trace

Uploaded by

kapil Jadhav
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
18 views

knowledge_base_trace

Uploaded by

kapil Jadhav
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

Kindly take trace of the session(sid:5053,serial#:20196, INST_ID:2) for 5 minutes.

connect / as sysdba
oradebug setospid 16569
oradebug unlimit
oradebug event 10046 trace name context forever,level 12

oradebug event 10046 trace name context off

If you are unable to identify the operating system process identifier (spid) from
the query in step 2, you can issue the following query to help identify the correct
session:

SELECT s.sid, s.serial#, p.spid, p.pid


FROM v$process p, v$session s
WHERE p.addr = s.paddr
AND s.username = 'CHURAMANI';

SPID VARCHAR2(24) Operating system process identifier

SQL> oradebug setospid 16569


Oracle pid: 483, Unix process pid: 16569, image: oracle@cordbp1 (J002)
SQL> oradebug unlimit
Statement processed.
SQL>

SQL> SELECT s.sid, s.serial#, p.spid, p.pid


FROM v$process p, v$session s
WHERE p.addr = s.paddr
AND s.username = 'CHURAMANI'; 2 3 4

SID SERIAL# SPID PID


------ -------- ------------------------ ----------
4731 34648 16569 483

You might also like