Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC63658 Status: Closed

ENGINE CRASH BECAUSE SQLKT_UNPACK_TUPLE() HITS SEGV OR ERROR.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 engine crashes because sqlkt_unpack_tuple() hits SEGV 
(Signal #11) with a stack like the following: 
 
0x09000000059A5C2C 
sqlkt_unpack_tuple__FP9sqlri_taoPiT2P5sqlcaPUiT5 - 
0x38C 
0x09000000059DDEA0 
sqlktftc__FP20sqle_agent_privatecbP9sqlri_taoP5sqlcaPUiT4 + 
0x644 
0x09000000059DD1E8 sqlritqa__FP8sqlrr_cb + 0x180 
0x09000000051A0740 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm - 
0x4A4 
0x0900000005B882B4 sqlrr_dss_router__FP8sqlrr_cb + 0x23C 
0x0900000005559DA0 
sqlrr_subagent_router__FP20sqle_agent_privatecbP10sqle_db2ra + 
0xD50 
0x0900000005B7C438 sqleSubRequestRouter__FP13sqle_agent_cbPUiT2 
+ 0x420 
0x09000000054B6508 sqleProcessSubRequest__FP13sqle_agent_cb + 
0x22C 
0x0900000004D07928 sqleRunAgent__FPcUi - 0x1FC 
.............. 
 
 
or after sqlkt_unpack_tuple() reports the following error: 
 
 
2009-01-16-08.03.03.607982+000 I3786938A582       LEVEL: Error 
PID     : 6828516              TID  : 1           PROC : 
db2agntp (AB8) 35 
INSTANCE: db2ab8               NODE : 035         DB   : AB8 
APPHDL  : 0-1484               APPID: 
165.131.71.120.54792.0901160713 
AUTHID  : SAPR3 
FUNCTION: DB2 UDB, table Q services, sqlkt_unpack_tuple, 
probe:80 
MESSAGE : DIA0001E An internal error occurred. Report the 
following error code 
          : "Line=01784, rc1=0x82170001, rc2=0x00000000, rc3=0, 
msg=col(13) 
          type(2) sect ind(0) and buffer ind(3737) mismatch, 
conn(0)". 
 
DB2 may hit SEGV when generating dump file with stack similar to 
the following: 
 
0x000000000000F448 ?unknown + 0x0 
0x0900000000093FB4 fwrite_unlocked + 0x25C 
0x0900000000094188 fwrite + 0xAC 
0x090000000449BA9C write_dump_data_814_44 + 0xC0 
0x0900000004406DDC write_dump_data + 0x20 
0x090000000441C6B8 
@141@dumpDataToFile__FPcT1R10PD_CONTEXTPCcUlPCvT1T5 + 0x298 
0x0900000005183C80 @141@pdLogInternal__FUlUiT1T2N41PvT1PPc + 
0x1548 
0x09000000053A571C _pdLogDump__FUlUiN31PCcT1PCv + 0x8C 
0x0900000004F54BA8 sqlt_logerr_dump + 0x98 
0x09000000058BD49C 
sqlrr_dump_section__FP8sqlrr_cbP9sqlri_shdP25sqlra_sql_context_s 
ibling + 0x47C 
0x0900000005A2F5BC 
sqlrr_dump_sibling__FP8sqlrr_cbP25sqlra_sql_context_siblingiT3 + 
0x5A0 
0x0900000005A2EF3C 
sqlrr_dump_sibling__FP8sqlrr_cbP25sqlra_sql_context_siblingiT3@g 
lue3A9 + 0x7C 
0x0900000004B8BC78 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x254 
0x0900000004B8B9B4 
sqlzeDumpFFDC__FP20sqle_agent_privatecbUiP5sqlcai + 0xA4 
0x0900000004C6B8B8 
sqlzeMapZrc__FP20sqle_agent_privatecbUiUlT2P5sqlcai + 0x9B0 
0x090000000594A364 sqlritqa__FP8sqlrr_cb + 0x2FC 
0x090000000510D740 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm - 
0x4A4 
0x0900000005AF52B4 sqlrr_dss_router__FP8sqlrr_cb + 0x23C 
........
Problem Summary:
ENGINE CRASH BECAUSE SQLKT_UNPACK_TUPLE() HITS SEGV OR ERROR.
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 UDB Version 9.7, FixPak 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.10.2009
28.12.2009
28.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList