|
Problem IC76623
|
Status: Closed |
ABEND WHEN DUMPING INDEX INFORMATION WHEN DB2_MEMORY_PROTECT ENABLED ON AIX WITH STORAGE KEY SUPPORT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The DB2_MEMORY_PROTECT registry variable is enabled, and DB2 is
running on AIX with storage key support, which is one of the
pre-conditions for DB2_MEMORY_PROTECT to take effect (please
refer to Information Center for more detail). At the same time,
an index corruption problem is detected, and DB2 is going to
dump extended diagnostic information about the damaged index.
When these conditions are met, the DB2 instance may abend while
writing the extended diagnostic information. The trap file will
be similar to:
EDU name : db2lrid
Signal #11
sqltData
memcpy
_gtraceVar
sqltData
sqlt_logerr_dump
sqldDumpDKEY
sqldDumpDKEY
sqliDumpICB |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* See APAR description *
****************************************************************
* PROBLEM DESCRIPTION: *
* See APAR description *
****************************************************************
* RECOMMENDATION: *
* Problem first fixed in DB2 UDB 9.7 FixPack 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 |
See APAR description |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.05.2011
12.12.2011
12.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
|
 |
