DB2 - Problem description
Problem IC95462 | Status: Closed |
THE DB2 INSTANCE MAY HANG OR TRAP ON LINUX WHEN USING A HIGH NUM_INITAGENTS SETTING | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Using a high NUM_INITAGENTS setting (~1000 or higher) may result in a hang or trap on DB2 / Linux. The high setting results in the creation of an additional segment for the DBMS memory set during instance startup processing (db2start). The address space assigned to the new segment for the db2sysc process at this point in time may not be available in the db2wdog (watchdog) process. The watchdog may not then be able to function properly, resulting in unpredictable symptom, including problems related to managing FMP processes. This problem may be more common in environments using address space randomization (ASLR). | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Linux systems with a high num_initagents setting * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix pack 3 * **************************************************************** | |
Local Fix: | |
reduce num_initagents setting to less than 1000 OR disable address space layout randomization (set kernel.randomize_va_space=0) | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 Version 10.5 Fix pack 3 | |
Workaround | |
See Local Fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2013 27.02.2014 27.02.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 |