Re: Deadlocks

A lack of itl entries in a table can also cause this phenomenon. High row density with a default 1 value of INITRANS can produce this "no rows" deadlock if the itl list cannot grow an additional entry and two transactions are updating blocks from the same table in different orders.

Fix it by recreating the table with a higher INITRANS.

• ricky

Chuck Hamilton wrote:
>
> Anyone ever gotten a deadlock detected error where the trace file doesn't
> show the row locks causing the deadlock? What causes this type of deadlock.
> I had several this morning and here's the deadlock graph from the trace
> file.
>
> Deadlock graph:
> ---------Blocker(s)-------- ---------Waiter(s)------
> ---
> Resource Name process session holds waits process session holds
> waits
> TM-00000afb-00000000 22 24 S 14 43
> SX
> TM-00000b07-00000000 14 43 SX 22 24
> S
> session 24: DID 0001-0016-00000002 session 43: DID 0001-000E-00000002
> session 43: DID 0001-000E-00000002 session 24: DID 0001-0016-00000002
> Rows waited on:
> Session 43: no row
> Session 24: no row
>
> --
> Never share a foxhole with anyone braver than yourself!
>
> Chuck Hamilton
> chuck_hamilton_at_hotmail.com
Received on Sat Jul 21 2001 - 16:25:25 CDT