ORA-00060: deadlock detected with only one session in trace

From: Eynat <eynatnir2_at_hotmail.com>
Date: 24 Jan 2005 04:13:47 -0800
Message-ID: <50d17a3f.0501240413.1d44b570@posting.google.com>

I get a "ORA-00060: deadlock detected" error when updating a BLOB (through Weblogic Application Server code of a CMP entity bean).

The DB is Oracle 9.2i, on Linux.

In the server's udump directory, I found the following trace of the deadlock.
The weird thing about it is that it shows only one session participating in the deadlock, and not more.

Does any one have an idea how this can happen? What does this indicate on my code?

Thanks, Eynat

Oracle trace:  

DEADLOCK DETECTED No current SQL statement being executed.

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

TX-00080012-0008fefe        18      88     X             18      88   
       S

session 88: DID 0001-0012-00000002      session 88: DID

0001-0012-00000002

Rows waited on:

Session 88: no row

Information on the OTHER waiting sessions:

End of information on OTHER waiting sessions.

---

Received on Mon Jan 24 2005 - 06:13:47 CST