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

DB2_FMP_COMM_HEAPSZ VALUES GREATER THAN 1GB NOT HONORED

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
If the DB2_FMP_COMM_HEAPSZ is set to greater than 1GB size ( 
~250,000 pages ), its silently set to a value of ~1GB. 
 
In highly concurrent environments where the FMP infrastructure 
is used extensively ( such as Federation ), this can cause "Out 
of memory" errors and subsequent crash of the FMP threads. This 
happens even when the registry var is set to a higher value than 
1GB.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Even after setting DB2_FMP_COMM_HEAPSZ to a size greater     * 
* than 1GB ( 250,000 pages ) it is silently limited to 1GB.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v111m1fp2                                     * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Fixed in DB2 v111m1fp2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.07.2017
29.01.2018
29.01.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)