DB2 - Problembeschreibung
Problem IC62793 | Status: Geschlossen |
A SPECIAL CASE OF SELECT INTO STATEMENT ON PARTITIONED DATABASE MAY CAUSE DB2 SERVER TO TERMINATE ABNORMALLY | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
The DB2 server may terminate abnormally while running a SELECT INTO statement on a partitioned database. The db2diag.log contains entries that point to memory corruption, for example: MESSAGE : Memory validation failure, diagnostic file dumped. Also in the db2diag.log you should see that the CALLSTACK contains the function sqlriGlobalVarAssign__FP8sqlrr_cb Typical CALLSTCK CALLSTCK: [0] 0x09000000014CBF78 diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc + 0x250 [1] 0x09000000014CBC4C diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc@glue677 + 0x74 [2] 0x0900000000A04F98 MemTreeGet__13SQLO_MEM_POOLFCUlT1PPvPP17SqloChunkSubgroupPP12SMe mLostNode + 0x4 [3] 0x0900000000A2299C .allocateMemoryBlock__13SQLO_MEM_POOLFCUlUlT1UiT1PPvPP17SqloChun kSubgroupPP12SMemLostNodeCP12SMemLogEvent_fdprpro_clone_0 + 0x98 [4] 0x0900000000A23CC0 sqlogmblkEx + 0xFFFFFFFFFFFFFCDC [5] 0x0900000000A2359C sqlmoAllocBlock + 0x90 [6] 0x0900000000A23A08 sqlogmblkEx + 0xFFFFFFFFFFFFFA24 [7] 0x090000000281BE28 @119@sqlraERTAddMember__FP8sqlrr_cb16sqlraERTCategoryPvPP14sqlra ERTMember + 0x2B4 [8] 0x090000000281B908 sqlraERTSetValue__FP8sqlrr_cb16sqlraERTCategoryPvP10sqlz_value +0x144 [9] 0x090000000281B634 sqlriGlobalVarAssign__FP8sqlrr_cb + 0x340 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * users using global variable on a partitioned database * **************************************************************** * PROBLEM DESCRIPTION: * * The DB2 server may terminate abnormally while running a * * SELECTINTO statement on a partitioned database. The * * db2diag.log contains entries that point to memory * * corruption, forexample:MESSAGE : Memory validation failure, * * diagnostic file dumped.Also in the db2diag.log you should * * see that the CALLSTACKcontains the function * * sqlriGlobalVarAssign__FP8sqlrr_cbTypical * * CALLSTCKCALLSTCK:[0] * * 0x09000000014CBF78diagnoseMemoryCorruptionAndCrash__13SQLO_MEM * +0x250[1] * * 0x09000000014CBC4CdiagnoseMemoryCorruptionAndCrash__13SQLO_MEM * 0x74[2] * * 0x0900000000A04F98MemTreeGet__13SQLO_MEM_POOLFCUlT1PPvPP17Sqlo * 0x4[3] * * 0x0900000000A2299C.allocateMemoryBlock__13SQLO_MEM_POOLFCUlUlT * 0x98[4] 0x0900000000A23CC0 sqlogmblkEx + * * 0xFFFFFFFFFFFFFCDC[5] 0x0900000000A2359C sqlmoAllocBlock + * * 0x90[6] 0x0900000000A23A08 sqlogmblkEx + * * 0xFFFFFFFFFFFFFA24[7] * * 0x090000000281BE28@119@sqlraERTAddMember__FP8sqlrr_cb16sqlraER * 0x2B4[8] * * 0x090000000281B908sqlraERTSetValue__FP8sqlrr_cb16sqlraERTCateg * 0x090000000281B634 sqlriGlobalVarAssign__FP8sqlrr_cb +0x340 * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7 fixpak1 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
DB2 version 9.7 fixpak1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 26.08.2009 04.02.2010 04.02.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7. | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |