By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,610 Members | 2,310 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,610 IT Pros & Developers. It's quick & easy.

DEADLOCK PROBLEM

P: n/a
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?

Mar 8 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Mar 8, 7:11 am, <a...@a.itwrote:
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

Mar 8 '07 #2

P: n/a
jefftyzzer wrote:
On Mar 8, 7:11 am, <a...@a.itwrote:
>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.
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...)

--
Knut Stolze
DB2 z/OS Admin Enablement
IBM Germany
Mar 12 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.