|
Problem IC99741
|
Status: Closed |
FORCE APPLICATION OF LOAD FROM CURSOR MIGHT CAUSE LOAD TO HANG |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Load from cursor might hang when the following conditions are
met:
-- Large UTIL_HEAP_SZ (database parameter) and/or DATA BUFFER
(load parameter) are set.
-- Large CPU_PARALLELISM and/or DISK_PARALLELISM are specified
explicitly or implicitly.
-- Load a large amount of data from cursor into target table.
-- Load is forced/interrupted during loading data.
Coordinator agent will have stack below waiting for all LOAD
EDU's to finish clean up:
__nanosleep
ossSleep
sqlorest
sqlulTermEDU
sqluvload
sqluLoadPartition
sqlu_register_table_load
while all the LOAD EDUs are blocked by "msgsnd()" when sending
feedback to the agent:
msgsnd
sqlowqueInternal
sqlowque
sqluWriteQueue
sqluCleanupAndSendFinalMessage
Error in db2diag.log:
================================================================
=======================
2014-01-03-08.06.22.609542-360 I15909E459 LEVEL: Severe
PID : 5428 TID : 47687680387392PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-19705 APPID:
192.95.202.157.53762.1401031024
AUTHID : DB2INST1
EDUID : 62617 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, relation data serv, sqlrrbck, probe:150
MESSAGE : SQLEU_STATE2_LOAD_ROLLBACK_PENDING state is set
2014-01-03-08.06.22.609822-360 I16369E552 LEVEL: Error
PID : 5428 TID : 47687680387392PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-19705 APPID:
192.95.202.157.53762.1401031024
AUTHID : DB2INST1
EDUID : 62617 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 123 bytes
LOADID: 62617.2014-01-03-04.24.33.946350.0 (4;9)
, -1224, 0xffffffff8012006d, Detected in file:sqlulxld_fetch.C,
Line:1122 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.1 Fixpack 4 *
**************************************************************** |
| Local Fix: |
Possible workarounds
-- Increase kernel parameter value msgmnb limit to
262144
-- Reduce UTIL_HEAP_SZ and/or DATA BUFFER.
-- Reduce CPU_PARALLELISM and/or DISK_PARALLELISM. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Version 10.1 Fix pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.02.2014
27.06.2014
27.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
