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

Eynat wrote:
> 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.
>
> ===================================================

Might be related to "Bug 3166756 - Self deadlock (ORA-60) possible on LOB index update"? See Metalink for details maybe. Received on Mon Jan 24 2005 - 08:57:48 CST