Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC61798 Status: Closed

A SESSION IS ABORTED SOME SECONDS AFTER COMMANDTIMEOUT IS REACHED

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
When CommandTimeout is reached, the client needs an additional 
period of 5-10 seconds before the session is aborted. 
 
Example: 
 
In this example, the UPDATE session waits for infinity for a 
lock. 
 
CommandTimeout = 1 
=> The session is aborted after 9714 milliseconds producing the 
following exception: 
 
 
ERROR [IX000] [IBM][IDS/UNIX32] Statement interrupted by user. 
(-157 ISAM error: Interrupted ISAM call)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When CommandTimeout is reached, the client needs an          * 
* additional                                                   * 
* period of 5-10 seconds before the session is aborted.        * 
*                                                              * 
* Example:                                                     * 
*                                                              * 
* In this example, the UPDATE session waits for infinity for a * 
*                                                              * 
* lock.                                                        * 
*                                                              * 
* CommandTimeout = 1                                           * 
* => The session is aborted after 9714 milliseconds producing  * 
* the                                                          * 
* following exception:                                         * 
*                                                              * 
*                                                              * 
* ERROR [IX000] [IBM][IDS/UNIX32] Statement interrupted by     * 
* user.                                                        * 
* (-157 ISAM error: Interrupted ISAM call)                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to IBM Data Server Provider for .Net 9.7 Fix Pack 1  * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 Fix Pack 1 
This fix should be applied on the client.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.06.2009
04.01.2010
04.01.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList