| Author |
Message
|
| mqsidude |
 Posted: Mon Feb 28, 2005 4:57 am Post subject: Deadlocks in WBI 5.0 |
 |
|
Centurion
Joined: 22 Jan 2004
Posts: 148
|
Hi folks,
In one of our projects, i see the following problem happening with WBI 5.0.3 + DB2 8.1.6.
SQL State '40001' SQL Native Error Code '-911' SQL Error Text '[IBM][CLI Driver][DB2/6000] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001 '
The flow is a simple one as following:
MQInput -> ComputeNode1 -> MQOuput -> ComputeNode2
Where
* ComputeNode1 inserts a row into a table
* ComputeNode2 updates the same row
* The whole flow is under global transaction
* Transaction Mode properties are set to Automatic in all applicable nodes
This problem seems to be common with DB2 lower versions (< 7). The reponses in this forum point at tuning few DB2 instance parameters although none of posts gave exact solution.
Can anyone of you who have faced this problem in WBI environment and solved this post your experiences and exact solution?
-Crony |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Feb 28, 2005 5:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So you're trying to Update an uncommitted Insert?
Why wouldn't that deadlocK?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqsidude |
| Posted: Tue Mar 01, 2005 3:35 am Post subject: |
|
|
Centurion
Joined: 22 Jan 2004
Posts: 148
|
Jeff,
The updatation is due to some business requirement. And this is working most of the time. Only a fraction of the total messages are landing up in error queue with the given exception.
Any suggestions are appreciated.
-Crony |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 01, 2005 5:44 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, if it is an intermittent problem, then I misunderstood the transactional boundaries.
In that case, talk to your DBA. They should be able to work with you to identify the volume patterns that cause the deadlock, and work with you to tune the system to meet the requirements.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JT |
| Posted: Tue Mar 01, 2005 6:44 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Do some reasearch on the DB2 command: db2set DB2_RR_TO_RS=YES. It disables 'next key-locking' and supposedly improves deadlocks during heavy workloads. |
|
| Back to top |
|
|
|
|
