Hi Tom,

I'm not sure I understand the root cause of the following deadlock trace. Assuming I'm reading it correctly the trace is showing two different sql sessions attempting to delete the same row in the AAA_WF_OPERAND table. However, I do not see this behavior in our application log. Can you help me understand the root cause of this deadlock?

thanks,
Rob


DEADLOCK DETECTED ( ORA-00060 )

[Transaction Deadlock]

The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:

Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TM-00015d50-00000000 37 138 SX SSX 38 266 SX SSX
TM-00015d50-00000000 38 266 SX SSX 37 138 SX SSX

session 138: DID 0001-0025-00000004 session 266: DID 0001-0026-00000002
session 266: DID 0001-0026-00000002 session 138: DID 0001-0025-00000004

Rows waited on:
Session 138: no row
Session 266: no row

----- Information for the OTHER waiting sessions -----
Session 266:
sid: 266 ser: 19 audsid: 6991521 user: 115/AAA_SHAREDSVCS
flags: (0x45) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
flags2: (0x40009) -/-/INC
pid: 38 O/S info: user: risknavdba, term: SPPL01557, ospid: 6808
image: ORACLE.EXE (SHAD)
client details:
O/S info: user: SYSTEM, term: unknown, ospid: 1234
machine: SPPL01556 program: JDBC Thin Client
application name: JDBC Thin Client, hash value=2546894660
current SQL:
delete from AAA_WF_OPERAND
where WORKFLOW_OBJECT_ID = :1

----- End of information for the OTHER waiting sessions -----

Information for THIS session:

----- Current SQL Statement for this session (sql_id=2vmxn82bt84pf) -----
delete from AAA_WF_OPERAND
where WORKFLOW_OBJECT_ID = :1
===================================================