DB2 FOR LUW / DB2FORLUW / A10 - DB2

The Load hang might occur under the following conditions: 
1) Low WARNINGCOUNT is specified (e.g. 1). 
2) High CPU_PARALLELISM and/or DISK_PARALLELISM are specified 
explicitly or implicitly. 
3) Data file contains lots of consecutive invalid rows that can 
cause Load Formatters to hit the WARNINGCOUNT very quickly. 
 
When the Load is hanging, you can see the following stack for 
db2agent (i.e. Load agent), but other Load EDUs have exited 
already: 
msgsnd 
uninterruptableMsgSnd 
sqlowqueInternal 
sqlowqueWrapper 
sqlowque 
sqluWriteQueue 
sqlulSndTermMsg 
sqlulTerminate 
sqlulPrcErr 
sqlulFRMResponse 
sqlulPollMsg 
sqluvload 
call_sqluvload 
sqluLoadPartition 
sqlu_register_table_load 
sqluvtld_route_in 
sqlesrvr 
sqleMappingFnServer 
sqlerKnownProcedure 
 
Please note that you might not be able to interrupt the hanging 
Load.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V10.1FP3 and below                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1FP4                                      * 
****************************************************************

Workaround: 
 1)Use Load without the warningcount 
 2)Reduce CPU_PARALLELISM and/or DISK_PARALLELISM 
 3)Correct the input data to avoid too many warnings generated.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Fixed in 
DB2 V10.1FP4

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

21.10.2013
07.07.2014
07.07.2014