DB2 FOR LUW / DB2FORLUW / 910 - DB2

Customers who experience low memory issues in DB2 v9.1 may run 
into an issue where shared memory segments are not attaching 
properly, which then leads to a trap and abnormal termination of 
DB2. 
 
DB2 9.1 crashes with the following stack Signal #11 (SIGSEGV): 
 
   0x090000000224EBF4 
sqlccipcterm__FP15sqlcc_comhandleP10sqlcc_cond + 0x70 
  0x09000000022CF678 sqlccterm__FP15sqlcc_comhandleP10sqlcc_cond 
+ 0x54 
  0x090000000142B8C4 
@48@sqljsCleanup__FP13sqle_agent_cbP11UCconHandle + 0xC4 
  0x0900000001D620D4 @48@sqljsDrdaAsInnerDriver+ 0x138 
  0x0900000001D61E18 sqljsDrdaAsDriver+ 0x9C 
  0x0900000001DF7144 sqleRunAgent+ 0xE4 
  0x0900000001DD59BC sqloCreateEDU+ 0x274 
  0x0900000001DF63F0 sqloSpawnEDU + 0x230 
  0x0900000001DF5F78 sqleCreateNewAgent+ 0x3D0 
  0x0900000001DF5208 sqleGetAgentFromPool- 0x6B4 
  0x0900000001DF3F64 sqleGetAgent+ 0x444 
  0x0000000100004F04 sqleInitSysCtlr__FPi + 0x1188 
  0x00000001000031D4 sqleSysCtlr__Fv + 0x320 
  0x090000000190A114 @49@sqloSystemControllerMain+ 0x4F4 
  0x0900000001FB3D58 sqloRunInstance + 0xA8 
  0x00000001000029F8 DB2main + 0x930 
  0x0000000100003D48 main + 0x10 
 
 
 
Sample of db2diag.log file entries at time of trap: 
 
2011-02-27-02.01.43.535000-300 I501246475A481     LEVEL: Severe 
PID     : 3784760              TID  : 1           PROC : 
db2agent (idle) 0 
INSTANCE: db2inst1               NODE : 000 
 
APPHDL  : 0-5774               APPID: 
*LOCAL.db2inst1.110227065814 
AUTHID  : AUTH1 
FUNCTION: DB2 UDB, common communication, sqlccrefresh, probe:901 
RETCODE : ZRC=0x850F0005=-2062614523=SQLO_NOSEG 
          "No Storage Available for allocation" 
          DIA8305C Memory allocation failure occurred. 
 
2011-02-27-02.01.43.601934-300 I501246957A705     LEVEL: Severe 
PID     : 3784760              TID  : 1           PROC : 
db2agent (idle) 0 
INSTANCE: db2inst1            NODE : 000 
APPHDL  : 0-5774               APPID: 
*LOCAL.db2inst1.110227065814 
AUTHID  : AUTH1 
FUNCTION: DB2 UDB, DRDA Application Server, sqljsInitAgent, 
probe:20 
DATA #1 : String, 18 bytes 
sqlccrefresh rc = 
DATA #2 : unsigned integer, 4 bytes 
5 
DATA #3 : Communication Failure Condition, PD_TYPE_COMCONDITION, 
284 bytes 
 
2011-02-27-02.01.43.631117-300 E501247663A720     LEVEL: Error 
PID     : 4804694              TID  : 1           PROC : 
db2agent (XXXXXXX) 0 
INSTANCE: db2inst1             NODE : 000         DB   : dbXXX 
APPHDL  : 11111                APPID: XXXX.XXXX.110224065144 
AUTHID  : AUTH1 
FUNCTION: DB2 UDB, oper system services, 
sqloEDUSIGDANGERHandler, probe:40 
MESSAGE : ADM0505E  DB2 received a SIGDANGER signal from the 
operating system. 
 
This signal indicates that the system is running low on paging 
space. 
If the paging space gets too low, the operating system will 
forcibly terminate user processes.  Consider increasing your 
paging space.

**************************************************************** 
* USERS AFFECTED:                                              * 
* v91 customers in a low-memory situation.                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Abnormal termination due to low-memory. SIGDANGER in         * 
* db2diag.log and trap in SQLCCIPCTERM.                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Increase your paging space available. Consider upgrading to  * 
* v95 or highier as this issue is not present.                 * 
****************************************************************

DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows
 

not known / see Local fix

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

01.06.2011
01.02.2012
01.02.2012

9.5.