home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC89652 Status: Closed

.NET APPLICATION MAY HANG AFTER RECEIVING COMMUNICATION ERROR

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
.NET application may hang after receiving communication error. 
 
In trace you can see even after connection failure, DB2 calls 
being executed which will result in hang situation like this: 
 
1125836 | | | | | | DB2DataReader.Dispose entry 
1125837 | | | | | | | DB2DataReader.Dispose entry 
1125838 | | | | | | | DB2DataReader.Dispose data [probe 15] 
1125839 | | | | | | | | SQLFreeStmt entry 
1125840 | | | | | | | | | sqloxltc_app entry 
1125841 | | | | | | | | | | sqlo_xlatch::getConflict entry 
 
SQLFreeStmt is being called but never exited.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP8                                      * 
****************************************************************
Local Fix:
available fix packs:
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 V9.7 FP8
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91777 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.01.2013
26.06.2013
26.06.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList