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 IT11287 Status: Closed

DURING ARRAY INSERT, DB2 MAY HANG IF THE CONNECTION GETS TERMINATED

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
If server looses connection while replying back to client on 
array insert (arrayinput) processing,  DB2 server may hang in 
error processing code path.The issue can occur if reply 
generated by the server is huge and client has requested to 
return monitoring information. 
 
The hang is caused by endless loop in DB2's error handling 
function sqljsReportError().Top functions may vary and include 
amongst others sqljsSrvdgn,ossSnprintf,vsnprintf and 
_IO_vfprintf but will not return below sqljsReportError. 
 
sqljsSrvdgnP13sqljsDrdaAsCbP11TraceObjectPc 
sqljsReportError 
sqljsDrdaAsCBCompletionArrayInput 
sqlrr_array_input 
sqljs_ddm_excsqlstt 
sqljsParseRdbAccessed
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 7                               * 
****************************************************************
Local Fix:
N/A
Solution
First Fixed in DB2 10.5 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.09.2015
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList