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

A LOAD COMMAND WITH LOW WARNINGCOUNT MIGHT HANG

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version V9.7 Fix Pack 9                       * 
****************************************************************
Local Fix:
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.
available fix packs:
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 Version V9.7 Fix Pack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC96847 IC96848 IC97046 IC97065 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.10.2013
04.02.2014
04.02.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList