DB2 FOR LUW / DB2FORLUW / 970 - DB2

Enabling memory protection via the DB2_MEMORY_PROTECT registry 
variable may cause the DB2 database engine to incorrectly fail 
with spurious memory protection errors. 
 
This type of failure can manifest in many ways, but a common 
signature is a DB2 trap file that shows a SIGSEGV trap with an 
si_code field of hex 34: 
 
Signal #11 (SIGSEGV): si_addr is <some address>, si_code is 
0x00000034 
 
Memory protection is only functional on AIX systems running on 
hardware with memory key support (Power 6 and later).  Other 
platforms are not affected.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 v9.5 or later on AIX systems with hardware that supports * 
* storage keys (Power 6 and later)                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Enabling memory protection via the DB2_MEMORY_PROTECT        * 
* registry variable may cause the DB2 database engine to       * 
* incorrectly fail with spurious memory protection errors.     * 
*                                                              * 
* This type of failure can manifest in many ways, but a common * 
* signature is a DB2 trap file that shows a SIGSEGV trap with  * 
* an si_code field of hex 34:                                  * 
*                                                              * 
* Signal #11 (SIGSEGV): si_addr is <some address>, si_code is  * 
* 0x00000034                                                   * 
*                                                              * 
* Memory protection is only functional on AIX systems running  * 
* on hardware with memory key support (Power 6 and later).     * 
* Other platforms are not affected.                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Do not set the DB2_MEMORY_PROTECT registry variable, or      * 
* explicitly set it to "NO".                                   * 
****************************************************************

Do not set the DB2_MEMORY_PROTECT registry variable, or 
explicitly set it to "NO".

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
 

The DB2_MEMORY_PROTECT registry variable will be ignored in DB2 
v9.7 fp5 and later fixpacks while a comprehensive review is 
performed.  Once the review is complete the function will either 
be rehabilitated or formally deprecated. 
 
As of DB2 v9.7 fp5, the registry variable can still be set (and 
will remain set if set previous).  Regardless of the setting, 
however, the DB2 engine will not enable memory protection.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC78581 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

08.09.2011
08.12.2011
08.12.2011

9.7.FP5,
9.7.FP5