SAP Knowledge Base Article - Preview

2777824 - Insufficient Interested Transaction List (ITL) of an SAP table result in ORA-00060

Symptom

Your system receives ORA-00060. After checking user trace of the ORA-00060, the deadlock graph is similar as below.
*********************
<SID>_ora_<xxxxx>.trc
->
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-<> <> <> X <><>S
TX-<>-<> <> X <><>S
*********************

According to SAP Note 84348, the system will immediately display further information about the object that caused the deadlock after the deadlock graph:

*********************
Rows waited on:
Session 39: obj - rowid = 000016F2 - 0003BC42.0000.0093
Session 46: obj - rowid = 000018C2 - 0001012D.004B.0016
*********************

Although the select statement of the session terminated by the deadlock is usually also displayed, you can also refer to these two lines to see which table is involved:

*********************
000016F2 [hex value] corresponds to 5874 [decimal]
000018C2 [hex value] corresponds to 6338 [decimal]
*********************

Use the command below to check the affected object:

sqlplus "sapr3/<passwd>"
SQL> SELECT owner, object_name, object_id FROM DBA_OBJECTS
        WHERE object_id=5874;
SQL> SELECT owner, object_name, object_id FROM DBA_OBJECTS
        WHERE object_id=6338;

If the affected object is table. Then the issue could be caused by the Insufficient Interested Transaction List.


Read more...

Environment

 Oracle Single instance

Product

SAP ERP 6.0

Keywords

ORA-00060, deadlock,  Interested Transaction List, ITL; , KBA , BC-DB-ORA , Oracle , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.