| Author |
Message
|
| mkhadse |
 Posted: Thu Aug 01, 2002 8:29 am Post subject: deadlock in workflow logs |
 |
|
Acolyte
Joined: 31 Dec 1969
Posts: 73
|
I am seing appx. 491 deadlocks every day in the fmcerr.log. We are running runstats and rebind every day. What else might be a problem here? Why so many deadlocks?
Please help. |
|
| Back to top |
|
 |
| jmac |
| Posted: Thu Aug 01, 2002 1:05 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I have seen this before, and posted to the IBM Newsgroup. You can read the developers response there
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| kriersd |
| Posted: Thu Aug 01, 2002 4:11 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Is this the "DB2 Database Deadlock or timeout" error?
If so... I had the same issue when running version 3.2.2. We opened up a PMR with IBM and they gave us a HOT FIX to correct the issue.
Dave 
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Aug 02, 2002 5:07 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I agree that this problem seems to have been fixed, in the IBM Newsgroup the bottom line was install V332 and this problem (database deadlock) should go away.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| clindsey |
| Posted: Wed Aug 07, 2002 12:12 pm Post subject: db2 deadlocks |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
FYI,
you also need to apply the latest CSD to the 3.3 level
code for the deadlocks. There was a change made to
3.3.0 CSD (or servicepack) 4 and 3.3.2 CSD 1 for various
deadlocks.
Charlie Lindsey
IBM Developer Relations Tech Support |
|
| Back to top |
|
|
|
|
