Deadlock Detection and Mitigation -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Deadlock Detection and Mitigation
From: Matt Olson <Matt.Olson@xxxxxxxx>
Date: Wed, 6 Mar 2019 23:29:52 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

What deadlock detection and mitigation tools do you use on IBMi DB2?

We are having a hard time narrowing in the reasons for random "Resource error - SQLSTATE 57014, SQLCODE -1044." Messages which we have recently found appear to be related to locking contention on DB2.

Matt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Deadlock Detection and Mitigation , Dawn May
RE: Deadlock Detection and Mitigation , Rob Berendt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.