DB2 - Problem description
Problem IC66584 | Status: Closed |
DB2 INSTANCE CRASHES WHEN FAILS TO ALLOCATE SUB-AGENT DUE TO INSUFFICIENT APPLICATION HEAP. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problem description: | |
If a DB2 agent fails to allocate sub-agent due to insufficient "appl_ctrl_heap_sz", you see following error messages in db2diag.log: ============================================== 2000-01-01-01.01.01.873276+480 I38094A531 LEVEL: Error PID : 12345 TID : 1 PROC : db2agnsc (SAMPLE) 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-11 APPID: 11.222.333.444.5555.12345678901 AUTHID : DB2INST1 FUNCTION: DB2 UDB, data management, sqldApplicationInit, probe:108 RETCODE : ZRC=0x8B0F0003=-1961951229=SQLO_NOMEM_APPCTLH "No memory available in 'Application Control Heap'" DIA8300C A memory heap error has occurred. 2000-01-01-01.01.01.875697+480 I38626A531 LEVEL: Severe PID : 12345 TID : 1 PROC : db2agnsc (SAMPLE) 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-11 APPID: 11.222.333.444.5555.12345678901 AUTHID : DB2INST1 FUNCTION: DB2 UDB, base sys utilities, sqleSubCoordInit, probe:40 RETCODE : ZRC=0x8B0F0003=-1961951229=SQLO_NOMEM_APPCTLH "No memory available in 'Application Control Heap'" DIA8300C A memory heap error has occurred. ============================================== As a result, the DB2 agent receives a SIGSEGV and DB2 instance crashes. In the trap file for the DB2 agent which receives SIGSEGV, you see call stack similar to the following: ============================================== sqlmoFreeHeap sqleSubCoordTerm sqleSubCoordProcessRequest ...... ============================================== | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users of version 9.1 on Linux, Unix and Windows * * platforms. * **************************************************************** * PROBLEM DESCRIPTION: * * If a DB2 agent fails to allocate sub-agent due to * * insufficient "app_ctl_heap_sz", you see following error * * messages in db2diag.log: * * ============================================== * * 2000-01-01-01.01.01.873276+480 I38094A531 LEVEL: * * Error * * PID : 12345 TID : 1 PROC : * * db2agnsc (SAMPLE) 0 * * INSTANCE: db2inst1 NODE : 000 DB : * * SAMPLE * * APPHDL : 0-11 APPID: * * 11.222.333.444.5555.12345678901 * * AUTHID : DB2INST1 * * FUNCTION: DB2 UDB, data management, sqldApplicationInit, * * probe:108 * * RETCODE : ZRC=0x8B0F0003=-1961951229=SQLO_NOMEM_APPCTLH * * "No memory available in 'Application Control * * Heap'" * * DIA8300C A memory heap error has occurred. * * * * 2000-01-01-01.01.01.875697+480 I38626A531 LEVEL: * * Severe * * PID : 12345 TID : 1 PROC : * * db2agnsc (SAMPLE) 0 * * INSTANCE: db2inst1 NODE : 000 DB : * * SAMPLE * * APPHDL : 0-11 APPID: * * 11.222.333.444.5555.12345678901 * * AUTHID : DB2INST1 * * FUNCTION: DB2 UDB, base sys utilities, sqleSubCoordInit, * * probe:40 * * RETCODE : ZRC=0x8B0F0003=-1961951229=SQLO_NOMEM_APPCTLH * * "No memory available in 'Application Control * * Heap'" * * DIA8300C A memory heap error has occurred. * * ============================================== * * As a result, the DB2 agent receives a SIGSEGV and DB2 * * instance crashes. * * * * In the trap file for the DB2 agent which receives SIGSEGV, * * you see call stack similar to the following: * * ============================================== * * sqlmoFreeHeap * * sqleSubCoordTerm * * sqleSubCoordProcessRequest * * ...... * * ============================================== * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB Version 9.1 FixPak 10 or higher levels. * **************************************************************** | |
Local Fix: | |
Set a proper value for parameter APPL_CTRL_HEAP_SZ to avoid the failure of allocating sub-agent. | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows | |
Solution | |
First fixed in DB2 UDB Version 9.1 FixPak 10. | |
Workaround | |
Set a proper value for parameter APP_CTL_HEAP_SZ to avoid the failure of allocating sub-agent. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.02.2010 20.06.2011 20.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.1. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.10 |