DB2 - Problembeschreibung
Problem IT05071 | Status: Geschlossen |
MEMBER CRASH RECOVERY MAY CONTINUOUSLY FAIL WITH SQLB_EMP_MAP_INFO_NOT_FOUND ERROR | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
In a pureScale environment, if one member has crashed while performing an update on a table, and another member performs a REORG INDEX RECLAIM EXTENTS operation on that same table while the first member is unavailable, the crash recovery of the first member may fail with the following error: 2014-10-01-14.39.06.487160-240 I230947131E5077 LEVEL: Severe PID : 6711 TID : 47190072355136 KTID : 6790 PROC : db2sysc 0 INSTANCE: db2user NODE : 000 DB : SAMPLE APPHDL : 0-53 APPID: *N0.DB2.141001183449 HOSTNAME: db2server EDUID : 34 EDUNAME: db2agnti (SAMPLE ) 0 FUNCTION: DB2 UDB, buffer pool services, sqlbDMScheckObjAlloc, probe:826 MESSAGE : ZRC=0x8402001B=-2080243685=SQLB_EMP_MAP_INFO_NOT_FOUND "EMP MAP INFO NOT FOUND" The crash recovery is attempting to undo a log record that affects an extent that has been reclaimed by the index reorg, and as a result, cannot complete. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All pureScale users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fix pack. * **************************************************************** | |
Local-Fix: | |
To allow the member crash recovery to complete, you will need to issue db2stop, mark the index as invalid with db2dart, and then restart DB2. | |
Lösung | |
Problem was first fixed in DB2 UDB version 10.5 fix pack 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.10.2014 15.12.2014 15.12.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.5 |