home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC76089 Status: Closed

ABEND WHEN ENCOUNTERING A CORRUPTED DICTIONARY WITH DB2_MEMORY_PROTECT
ENABLED ON AIX

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Normally, when DB2 loads a corrupted compression or expansion 
dictionary from disk, it returns an SQL0901N error indicating 
that dictionary validation failed. However, during dictionary 
validation with the DB2_MEMORY_PROTECT registry variable enabled 
on AIX with storage key support, the instance may return an 
SQL1224N error instead and abend with Signal #11. 
 
The stack in the trap file should look similar to the following: 
 
-------Frame------ ------Function + Offset------ 
0x090000002949BB30 ossHexDumpLine + 0x110 
0x090000002949C024 ossHexDumpToBuffer + 0x284 
0x0900000051508F6C pdHexDump + 0x2C 
0x0900000051551F20 pdFormatArg + 0x5C0 
0x0900000051A217D0 pdInvokeFmtFnc + 0x30 
0x0900000051095B74 formatPDType + 0x3B4 
0x0900000051092B5C pdTypeFormatOrDump + 0x1ABC 
0x090000005107106C pdLogInternal + 0x632C 
0x090000005106AB40 pdLog + 0x320 
0x090000005212C9C0 sqldFetchDictionary + 0x820 
0x09000000517DC360 sqldLoadTCB + 0xB40 
0x09000000517E1134 sqldFixTCB + 0x6B4 
0x0900000051D5D034 sqldLockTableFixTCB + 0x374 
0x09000000526E549C sqldGetTableData + 0x5DC 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* AIX users with DB2_MEMORY_PROTECT enabled                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Incorrect diagnostic output triggered by a corrupted         * 
* dictionary caused an abend only when DB2_MEMORY_PROTECT is   * 
* enabled.                                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local Fix:
Disable DB2_MEMORY_PROTECT
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem was first fixed in DB2 Version 9.7 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.04.2011
08.12.2011
08.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList