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 IC74969 Status: Closed

ABEND DURING LOAD 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). When these 
conditions are met, the DB2 instance may abend when running the 
LOAD utility. The eyecatcher to identify this problem is the 
presence of the sqlbPurgeAllPagesCommon routine in the trap 
file, while the sqlbPurgeOrFlushEMPs routine is NOT present: 
 
EDU name     : db2agent (SAMPLE) 
Signal #11 
 
sqlbSlotIsInPageDecreaseArea 
sqlbAddToHateList_IUO 
sqlbAddToAlternateHateList 
sqlbPurgeAllPagesCommon 
sqlbPurgeAllPagesMultipleObjects 
sqlbPurgeMultipleObjects 
zFlushAndPurgeObjects 
sqluRegisterLoadStart 
 
This problem only exists in DB2 UDB 9.7 FixPak 3 or newer.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ABEND DURING LOAD WHEN DB2_MEMORY_PROTECT ENABLED ON AIX     * 
* WITH                                                         * 
* STORAGE KEY SUPPORT                                          * 
**************************************************************** 
* 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). When these     * 
* conditions are met, the DB2 instance may abend when running  * 
* the                                                          * 
* LOAD utility. The eyecatcher to identify this problem is the * 
* presence of the sqlbPurgeAllPagesCommon routine in the trap  * 
* file, while the sqlbPurgeOrFlushEMPs routine is NOT present: * 
*                                                              * 
* EDU name    : db2agent (SAMPLE)                              * 
* Signal #11                                                   * 
*                                                              * 
* sqlbSlotIsInPageDecreaseArea                                 * 
* sqlbAddToHateList_IUO                                        * 
* sqlbAddToAlternateHateList                                   * 
* sqlbPurgeAllPagesCommon                                      * 
* sqlbPurgeAllPagesMultipleObjects                             * 
* sqlbPurgeMultipleObjects                                     * 
* zFlushAndPurgeObjects                                        * 
* sqluRegisterLoadStart                                        * 
*                                                              * 
* This problem only exists in DB2 UDB 9.7 FixPak 3 or newer.   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FixPak 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       :
10.03.2011
23.12.2011
23.12.2011
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.5 FixList