DB2 - Problem description
Problem IT36093 | Status: Closed |
DB2_FMP_COMM_HEAPSZ VALUES GREATER THAN 1GB NOT HONORED | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - 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. db2diag.log will show error below originating from db2agent and the heap being around 900 MB. FUNCTION: DB2 UDB, SQO Memory Management, sqloMemLogPoolConditions, probe:30 DATA #1 : Out of memory failure for Undefined Heap on node 0. Requested block size : 4202516 bytes. Physical heap size : 964558848 bytes. Configured heap size : 966393856 bytes. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * db2fmp used to run non-SQL routines * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Apply v11.5.6.0 to DB2 server * **************************************************************** | |
Local Fix: | |
For Federated users only, this restores v11.1 behaviour and allows more concurrent Federeated routines (non-SQL stored procedure / user defined function) to be run. However on busy systems the Out Of Memory may still be encountered and thus recommendation is to apply IT36093. 1) db2set DB2_FED_FMP_COMM_BUF_SIZE=15 2) db2stop 3) db2start | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * db2fmp used to run non-SQL routines * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Apply v11.5.6.0 to DB2 server * **************************************************************** | |
Comment | |
First fixed in v11.5.6.0 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.03.2021 16.06.2021 16.06.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |