DB2 - Problembeschreibung
Problem IC74968 | Status: Geschlossen |
ABEND WHEN DROPPING SMALL TABLE OR REORGANIZING LOB OBJECT WHEN DB2_MEMORY_PROTECT ENABLED ON AIX WITH STORAGE KEY SUPPORT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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 during one of the following actions. The common denominator is the presence of the sqlbPurgeOrFlushEMPs routine in the trap file. 1) Small Table Drop =================== This problem can only happen if the table to be dropped has dirty pages in one of the bufferpools defined on the current database, and the size of the table is relatively small compared to the size of the dirty lists for the bufferpool (the exact threshold is IBM Confidential and subject to change). In this case the table will qualify for fast dirty page purging, and the attempt to purge its dirty pages during DROP TABLE will cause an instance abend. The trap file will be similar to: EDU name : db2agent (SAMPLE) Signal #11 sqlpflog or sqlbGetPageLSN sqlpflog or sqlbCheckAndForceLogs sqlbPurgeOrFlushAllPagesInSmallRange sqlbPurgeOrFlushEMPs sqlbDMSDeleteObject 2) LOB Reorg ============ A similar trap may happen during a lob object reorganization. The trap file will be similar to: EDU name : db2agent (SAMPLE) Signal #11 sqlbAddToHateList_IUO sqlbPurgeAllPagesCommon sqlbPurgeOrFlushEMPs sqldReorgReplaceDMS sqldReorgCopyPhase Both problems only exist in DB2 UDB 9.7 FixPak 1 or newer. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ABEND WHEN DROPPING SMALL TABLE OR REORGANIZING LOB OBJECT * * 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 during * * one of the following actions. The common denominator is the * * presence of the sqlbPurgeOrFlushEMPs routine in the trap * * file. * * * * 1) Small Table Drop * * =================== * * This problem can only happen if the table to be dropped has * * dirty pages in one of the bufferpools defined on the current * * database, and the size of the table is relatively small * * compared to the size of the dirty lists for the bufferpool * * (the exact threshold is IBM Confidential and subject to * * change). In this case the table will qualify for fast dirty * * page purging, and the attempt to purge its dirty pages * * during DROP TABLE will cause an instance abend. The trap * * file will be similar to: * * * * EDU name : db2agent (SAMPLE) * * Signal #11 * * * * sqlpflog or sqlbGetPageLSN * * sqlpflog or sqlbCheckAndForceLogs * * sqlbPurgeOrFlushAllPagesInSmallRange * * sqlbPurgeOrFlushEMPs * * sqlbDMSDeleteObject * * * * 2) LOB Reorg * * ============ * * A similar trap may happen during a lob object * * reorganization. * * The trap file will be similar to: * * * * EDU name : db2agent (SAMPLE) * * Signal #11 * * * * sqlbAddToHateList_IUO * * sqlbPurgeAllPagesCommon * * sqlbPurgeOrFlushEMPs * * sqldReorgReplaceDMS * * sqldReorgCopyPhase * * * * Both problems only exist in DB2 UDB 9.7 FixPak 1 or newer. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB 9.7 FixPak 5. * **************************************************************** | |
Local-Fix: | |
Disable DB2_MEMORY_PROTECT. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
This APAR is first fixed in DB2 UDB 9.7 FixPak 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC75711 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.03.2011 23.12.2011 23.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7. | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |