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

On Windows platforms, LOAD with CPU_PARALLELISM more than 1 may leak
message queue memory

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
On Windows, LOAD operations with cpu_parallelism greater than 1 
(implicitly or explicitly) can cause message queue memory 
resource leakage.  Even though each LOAD only leaks a small 
amount of memory (typically less than 1 KB), this Queue Memory 
is not growable.  For heavy LOAD users running thousands of 
LOADs cumulatively, the Queue Memory can eventually be 
exhausted, and after that DB2 can experience errors, panics, and 
hangs. 
 
Indicator in db2diag.log is, messages that show: 
 
MESSAGE : ZRC=0x870F0041=-2029060031=SQLO_QUE_NOT_SENT "Message 
Not Sent"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running large amount of load operations in cumulative  * 
* fashion under windows platform                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In windows platform, users who need to run large amount of   * 
* DB2 load operations concurrently can experience a memory     * 
* leak situation from message queue memory resource.           * 
* This is applicable when cpu_parallelism is greater than 1.   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Users should upgrade to DB2 V9.7 fix pak 4 to avoid          * 
* experiencing this defect.                                    * 
* Also, the guidelines mentioned  under LOCAL FIX  of this     * 
* APAR  could be followed to avoid this issue.                 * 
****************************************************************
Local Fix:
Reduce the load's cpu_parallelism to 1 
 (which will prevent leakage from load); 
 
Increase the queue memory with DB2 registry 
DB2NTMEMSIZE=QUE:<size> 
 (which will delay exhaustion of queue memory)
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
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 pak 4 
 
With this fix in place users will be able to run large number of 
 load operations simultaneously under windows platform.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.09.2010
28.04.2011
28.04.2011
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList