You are on page 1of 1

Long runnig concurrent requests ?

1.DB locks
2.what it is waiting for (toad)
3.take the sid and check its status & explain plan (going for full table scan or
index scan)
4. stale data and statistics on table(gather stats on schemas)
===================================================================================
=====

This post covers overview of How to troubleshoot long running concurrent request in
Oracle Apps 11i/R12

Step 1 : Check Concurrent Request ID of long running concurrent request from front
end
Step 2 : Find SID, SERIAL# and SPID by running SQL (given below)
Step 3 : Enable event 10046 trace with level 12 using oradebug ( for 15-20 minute)
Step 4 : Disable trace (once you are happy with trace size)
Step 5 : Convert raw trace to TKPROF using various sort options like fchela,
prsela, execpu
Step 6 : Check TKPROF out file to find root cause of slow concurrent request

You might also like