Does DB2 for iseries support deadlock detection? I can't get it to work. I'm
manually running the following sql commands in different transactions:
T1: set transaction isolation level RS;
T1: select * from aschema.atable where id = 1;
T2: set transaction isolation level RS;
T2: select * from aschema.atable where id = 1;
T1: update aschema.atable set acolumn = acolumn where id = 1; -- this
blocks, which is correct
T2: update aschema.atable set acolumn = acolumn where id = 1; -- this
blocks, which is correct
On DB2 LUW, after 10 seconds I get sql 911 reason 2, indicating that a
deadlock has been detected and one of the transactions has been rolled back.
The other one then proceeds.
On DB2 for iseries, after 30 seconds (the table's record lock wait time) I
get sql 913, indicating that the record lock wait time has been reached. No
deadlock is detected. I'm wondering if there's something I need to configure
to enable deadlock detection.
I'm running the tests on a v6r1 machine through jt400 6.1.
Any help is much appreciated,
Jonathon
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.