Re: How to identify resources in deadlock graph

We'll, as stated by the deadlock graph the other session is not waiting on a row lock, but probably an index lock since the lock type is TX.

I would guess that either the both sessions are trying to use the same value in an unique index or that you might be using a bitmap index which uses a "row-range" type of lock which could lead to deadlocks when multiple sessions are executing DML.

/Kristian

> Hi all,
> I have to diagnose a deadlock cause but I don't know how to extract all
> information.
> Here is an excerpt of the trace file:
> Deadlock graph:
> ---------Blocker(s)--------
> ---------Waiter(s)---------
> Resource Name process session holds waits process session
> holds waits
> TX-000b001c-0013e61f 207 52 X 215 100
> X
> TX-001c002d-0013eb3b 215 100 X 207 52
> S
> session 52: DID 0001-00CF-00000002 session 100: DID 0001-00D7-00000002
> session 100: DID 0001-00D7-00000002 session 52: DID 0001-00CF-00000002
> Rows waited on:
> Session 100: obj - rowid = 00001700 - AAAFH4AAiAAAQ8xAAV
> Session 52: no row
>
> The problem is on session 52, I have identified the object_id which
> corresponds to 1700 hex, but I'm not able to determine the other
> resource in the deadlock graph.
> Any advice?
> Thank in advance,
> Giovanni
> --
>
> ----------------------------------------
> Giovanni Cuccu
> Sw Engineer_at_dianoema.it
> Dianoema S.p.A.
> Via de' Carracci 93 40131 Bologna
> Tel: 051-7098211 051-4193911
> e-mail:gcuccu_at_dianoema.it
> ----------------------------------------
> No man does it all by himself,
> I said young man,
> put your pride on the shelf
> ----------------------------------------
> --
> http://www.freelists.org/webpage/oracle-l
>

--
http://www.freelists.org/webpage/oracle-l