Hi!

How does DB2 choose the victim when a deadlock is detected?
Can it be configured in any way?
Last night a long-running batch transaction was choosen before a one-
account-update Web-application. I was under the impression that the
application that had done the least work was choosen. See article
at:http://www.idug.org/conferences/EU2008/data/EU08F11.pdf

/dg

On Feb 17, 10:50*am, danfan <danfa... (AT) hotmail (DOT) com> wrote:
Hmm!
In Tuning database performance (SC23-5867-01) I found this:
"If it finds a deadlock, the deadlock detector arbitrarily selects one
deadlocked
process as the victim process to roll back. The victim process is
awakened, and
returns SQLCODE -911 (SQLSTATE 40001), with reason code 2, to the
calling
application. The database manager rolls back uncommitted transactions
from the
selected process automatically. When the rollback is complete, the
locks that
belonged to the victim process are released, and the other processes
involved
in the deadlock can continue".

Still, is there no way to influence the behaviour?
/dg