DEADLOCK PROBLEM

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

a@a.it - 08 Mar 2007 15:11 GMT

I have a db2 V. 8.1 Fix Pack 13 installed, and i have too much problem with
deadlock, maibe depends becouse i have a direct remote connection with a
56k modem.
Someone know if depends to a particular parameter?

Reply to this Message

jefftyzzer - 08 Mar 2007 18:22 GMT

On Mar 8, 7:11 am, <a...@a.it> wrote:

> I have a db2 V. 8.1 Fix Pack 13 installed, and i have too much problem with
> deadlock, maibe depends becouse i have a direct remote connection with a
> 56k modem.
> Someone know if depends to a particular parameter?

Please report the reason code being reported when you receive the
error. Possible reason codes are 2 (deadlock), 68 (lock timeout), and
72 (error concerning a DB2 Data Links Manager). Reason code 68 is by
far the most common.

If you are, in fact, reporting true deadlock errors (again, reason
code 2), then the usual remedy is to turn on a higher level of
montoring that is deadlock-specific, parsing the monitor output, and
then refactoring your transactions accordingly.

--Jeff

Reply to this Message

Knut Stolze - 12 Mar 2007 15:15 GMT

> On Mar 8, 7:11 am, <a...@a.it> wrote:
>> I have a db2 V. 8.1 Fix Pack 13 installed, and i have too much problem
[quoted text clipped - 12 lines]
> montoring that is deadlock-specific, parsing the monitor output, and
> then refactoring your transactions accordingly.

Right. Deadlocks can only be fixed in the applications accessing DB2.
There is no configuration parameter to simply make them disappear. (You
could lower the lock timeout. Then you wouldn't get a deadlock (usually)
but a lock timeout instead. But I wouldn't say that this is really any
better...)

Signature

Knut Stolze
DB2 z/OS Admin Enablement
IBM Germany

Reply to this Message