DB2 FOR LUW / DB2FORLUW / A10 - 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 running on the Linux platform                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3                       * 
****************************************************************

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

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 Version 10.1 Fix Pack 3

See Local Fix

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

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

05.07.2013
04.12.2013
04.12.2013