DB2 FOR LUW / DB2FORLUW / 970 - DB2

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).

**************************************************************** 
* USERS AFFECTED:                                              * 
* systems with a high NUM_INITAGENTS configuration (eg. >      * 
* 1000)                                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 9                        * 
****************************************************************

reduce num_initagents setting to less than 1000 
  OR 
disable address space layout randomization (set 
kernel.randomize_va_space=0)

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
 

Problem first fixed in DB2 Version 9.7 Fix Pack 9

See Local Fix

forerunner  : APAR is sysrouted TO one or more of the following: IC93952 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

05.07.2013
18.12.2013
18.12.2013

9.7.FP9