Re: how to code for: SQL0913N unsuccessful execution caused bydeadlock or timeout -- WEB400

× 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: Re: how to code for: SQL0913N unsuccessful execution caused bydeadlock or timeout
From: <elehti@xxxxxxxxxxxxxxxxxx>
Date: Thu, 9 Jun 2011 16:06:06 -0500
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Received several recommendations from IBM tech support.
Solution 1. We will edit our SQL statements to use Uncommitted Read
(UR). This works with DB2 Connect which we use.

Alternative solution 2. Use Systemi Access ODBC driver for Linux
instead of DB2 Connect.

Alternative solution 3. Upgrade to V6R1 which allows isolation level
*NONE

As an Amazon Associate we earn from qualifying purchases.

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.