| Author |
Message
|
| alex_do |
 Posted: Thu Oct 14, 2004 10:48 am Post subject: Deadlock issue |
 |
|
Voyager
Joined: 17 Feb 2004
Posts: 85
|
Our system previously works on this configuration DB2 8.1.3,MQ 5.3.6 and MQWF 3.4.4 .As we experiencing the deadlock issues we upgraded the service packs to DB2 8.3.6,MQ 5.3.7 and MQWF 3.4.6.But I still see the deadlock errors in fmcsys log file.Do we need to install any additional fixpacks to resolve these errors?Thanks in advance.
FMC31100W The message InvokeProgramResponse could not be processed because of a database deadlock or timeout. The message will be retried. |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Oct 14, 2004 11:48 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Do you do the DB maintenance regularly? |
|
| Back to top |
|
|
| alex_do |
| Posted: Thu Oct 14, 2004 12:37 pm Post subject: |
|
|
Voyager
Joined: 17 Feb 2004
Posts: 85
|
| We do reorg and rebind everynight.Do we need to do any additional maintaince on the database?Thanks |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Fri Oct 15, 2004 7:14 am Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
|
| Back to top |
|
|
| ucbus1 |
| Posted: Fri Oct 15, 2004 7:55 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Ask your DBA to run runstats and rebinds.
If your DBA has monitoring tools, he can monitor the SQL that is causing the deadlock and create an index. Once an index is created, you have to run RUNSTATs. one of possible tables you may want to try is FMC.PROGRAM_ACT_INST table |
|
| Back to top |
|
|
| kriersd |
| Posted: Fri Oct 15, 2004 12:07 pm Post subject: Cleanup server |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Check to make sure your cleanup server is not running during normal business hours. That can cause database contention. You should run the cleanup server off hours as a rule of thumb.
Do you have a custom client or are you using the IBM Web Client? If you have a custom client I would reccomend you review the code to ensure it isn't calling the database directly. Even if a custom client uses the IBM api, there are several things that could be causing this problem.
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
|
|
