Re: Deadlocks

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Sat, 21 Jul 2001 21:29:17 GMT
Message-ID: <994364993.14140.0.nnrp-08.9e984b29@news.demon.co.uk>

Then there's the primary key insert -

User A inserts pk = 'XXX' in table 1

User B inserts pk 'YYY' into table 2

User A inserts pk='YYY' into table 2 - but waits on B without showing a row wait.

User B inserts pk = 'XXX' into table 1 - deadlock detected.

--
Jonathan Lewis

Host to The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Author of:
Practical Oracle 8i: Building Efficient Databases
See http://www.jlcomp.demon.co.uk/book_rev.html

Seminars on getting the best out of Oracle
See http://www.jlcomp.demon.co.uk/seminar.html

Screensaver or Lifesaver: http://www.ud.com
Use spare CPU to assist in cancer research.




Ricky Sanchez wrote in message <3B425AE6.567836A9_at_more.net>...


>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

>

Received on Sat Jul 21 2001 - 16:29:17 CDT