The DB version is 11.2.0.4.
I was looking at the TKP output of a concurrent job which was traced with waits
turned on from an Oracle E-Business Suite environment. The PL/SQL lock timer
wait showed up as the most time consuming event. However, when I looked at the
raw trace file, I did not see DBMS_LOCK.SLEEP call anywhere in the trace file,
which I was hoping to see. I was wondering what might have caused this event to
appear in the trace file.
OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 29 0.00 0.00 0 0 0 0
Execute 979 186.42 2259.07 2 73 245 964
Fetch 13 0.00 0.00 0 59 0 12
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 1021 186.42 2259.07 2 132 245 976
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
SQL*Net message to client 3 0.00 0.00
SQL*Net message from client 3 0.00 0.00
library cache lock 19 0.00 0.00
library cache pin 35 0.00 0.01
utl_file I/O 2196972 0.04 7.03
row cache lock 61 0.00 0.06
PL/SQL lock timer 2067 1.28 2067.53
enq: IV - contention 127 0.00 0.11
gc current grant busy 3 0.00 0.00
gc current block 3-way 5 0.00 0.00
gc cr grant 2-way 1 0.00 0.00
db file sequential read 1 0.00 0.00
********************************************************************************
Thanks,
Amir