Re: deadlock detection/resolving

Define what you consider to be a
'resolution' of this deadlock.

At present Oracle will say to T1

    'ORA-00060 deadlock detected - sort your code out'. and rollback the update to 127494;

There are then two possible 'resolutions':

    T1 says to T2 and says
    'why are you messing with my data,
    roll back your transaction'.
or

    T1 decides it's messing with someone     else's data and rolls back completely.

Which one is the 'correct' one ?

How is Oracle supposed to decide in the
general case ?

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Author of:
Practical Oracle 8i: Building Efficient Databases

Next Seminar - Australia - July/August
http://www.jlcomp.demon.co.uk/seminar.html

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



Rüdiger J. Schulz wrote in message <3cc03614$1_at_netnews.web.de>...


>- there are only two connections

>  (started with benthic-software "golden")

>t1:

>  update artikel set bezeichnung = 'WURST'

>     where artnr = 127493;

>t2:

>  update artikel set bezeichnung = 'WURST'

>     where artnr = 127494;

>t1:

>  update artikel set bezeichnung = 'KÄSE'

>     where artnr = 127494;

>t2:

>  update artikel set bezeichnung = 'KÄSE'

>     where artnr = 127493;

>

>

>--> look at the artnr !!

>

>

>now there's a deadlock! all that I want is that oracle

>resolves it automatic...

>