|
Problem IC97065
|
Status: Closed |
A LOAD COMMAND WITH LOW WARNINGCOUNT MIGHT HANG |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - 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: *
* In environments running a Load with a low warning count. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix *
* Pack 4) or higher *
**************************************************************** |
| 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 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.10.2013
11.09.2014
15.10.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
