DB2 - Problem description
Problem IC64255 | Status: Closed |
DB2 ABEND WHEN RUNNING OLAP QUERIES WITH "WITH HOLD" CURSORS USING SCALAR AGGREGATE FUNCTIONS WHEN CC IS ENABLED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problem description: | |
DB2 may abend with signal 11 when running OLAP queries with "WITH HOLD" cursors using scalar aggregate functions in an environment where Connection Concentrator is enabled. The entries in db2 diag may look as follows: 2009-10-08-17.33.13.930178-420 I16330362A1659 LEVEL: Severe PID : 729544 TID : 1 PROC : db2agent (SAMPLE) 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-000 APPID: FUNCTION: DB2 UDB, SQO Memory Management, sqlofmblkEx, probe:20 MESSAGE : Memory corruption detected. DATA #1 : ZRC, PD_TYPE_PARAM_ZRC, 4 bytes 0x820F0002 DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 bytes 0x00000001118145e0 DATA #3 : Block header, PD_TYPE_BLK_HEADER, 16 bytes 0x00000001118145D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 0x00000001118145E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00000001118145F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0000000111814600 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ CALLSTCK: [0] 0x0900000011086C74 pdLog + 0xA4 [1] 0x090000001124065C sqlofmblkEx + 0x5D0 [2] 0x090000001145EB88 sqlri_scalag_close__FP8sqlrr_cbP15sqlri_scalagobj + 0x36C [3] 0x0900000011410688 sqlri_scalag__FP8sqlrr_cb + 0x32C [4] 0x090000001143DC8C sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x18 [5] 0x090000001143CC98 sqlrr_process_fetch_request__FP7UCintfc + 0xC [6] 0x090000001143B3E0 sqlrr_fetch__FP7UCintfcP15db2UCCursorInfo + 0x19C [7] 0x0900000011115E50 sqljs_ddm_cntqry__FP7UCintfcP14sqljsDDMObject + 0x82C [8] 0x09000000111165BC sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP14sqljsDDMObjectP7UCint fc + 0x2C [9] 0x090000001113DF44 sqljsParse__FP13sqljsDrdaAsCbP7UCintfc + 0xFFFFFFFFFFFFFF20 2009-10-08-17.33.14.067268-420 E16337693A737 LEVEL: Severe PID : 729544 TID : 1 PROC : db2agent (SAMPLE) 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-000 APPID: FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:20 DATA #1 : Signal Number Recieved, 4 bytes 11 DATA #2 : Siginfo, 64 bytes 0x0FFFFFFFFFFF7500 : 0000 000B 0000 0000 0000 0033 0000 0000 ...........3.... 0x0FFFFFFFFFFF7510 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0FFFFFFFFFFF7520 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0FFFFFFFFFFF7530 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 2009-10-08-17.33.19.535857-420 E16458189A881 LEVEL: Severe PID : 2130026 TID : 1 PROC : db2gds 0 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, oper system services, sqloEDUSIGCHLDHandler, probe:50 DATA #1 : <preformatted> Detected the death of an EDU with process id 729544 The signal number that terminated this process was 11 Look for trap files (t729544.*) in the dump directory CALLSTCK: [0] 0x0900000011719AF0 pdLogPrintf + 0xB8 [1] 0x09000000113E8490 @38@sqloEDUSIGCHLDHandler__FiP9siginfo_tPv + 0x35C [2] 0x0000000000000000 ?unknown + 0x0 [3] 0x0000000000000000 ?unknown + 0x0 [4] 0x0000000000000000 ?unknown + 0x0 [5] 0x0000000000000000 ?unknown + 0x0 [6] 0x0000000000000000 ?unknown + 0x0 [7] 0x0000000000000000 ?unknown + 0x0 [8] 0x0000000000000000 ?unknown + 0x0 [9] 0x0000000000000000 ?unknown + 0x0 The fix is to return -901 error instead of db2 abend and output the following message in db2diag.log: 2009-10-30-13.01.41.033538-240 I2554A836 LEVEL: Severe PID : 205518 TID : 1 PROC : db2agent (SAMPLE) INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.elena.091030170039 AUTHID : db2inst1 FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 70 sqlerrmc: sqlricjpInfrequent: do not use Connection Concentrator and OLAP functions sqlerrp : SQLRI462 sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFEC11 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: | |
Problem Summary: | |
DB2 ABEND WHEN RUNNING OLAP QUERIES WITH "WITH HOLD" CURSORS USING SCALAR AGGREGATE FUNCTIONS WHEN CC IS ENABLED. | |
Local Fix: | |
1. Disable Connection Concentrator: db2 update dbm cfg using MAX_CONNECTIONS -1 db2start db2stop 2. Do not use WITH HOLD cursors. | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows | |
Solution | |
FIRST FIXED in DB2 v91fp9 LOCAL FIX: 1. Disable Connection Concentrator: db2 update dbm cfg using MAX_CONNECTIONS -1 db2start db2stop 2. Do not use WITH HOLD cursors. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.10.2009 19.04.2010 19.04.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.9 |