DB2 - Problembeschreibung
Problem IC76484 | Status: Geschlossen |
CRASH RECOVERY MAY FAIL WITH INDEX ERROR AT SQLIMARKKEY, PROBE:1327 | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Crash recovery may fail due to the following error: 2011-04-03-04.35.25.985380+000 I7081142A564 LEVEL: Severe PID : 844026 TID : 4113 PROC : db2sysc 0 INSTANCE: xxxxxx NODE : 000 DB : xxx APPHDL : 0-8 APPID: 10.50.16.137.54680.110403023105 AUTHID : SAPMDT EDUID : 4113 EDUNAME: db2agent (xxx) 0 FUNCTION: DB2 UDB, index manager, sqliMarkKey, probe:1327 RETCODE : ZRC=0x82090001=-2113339391=SQLI_NONSEVERE_PRGERR "Non severe index programming error" DIA8532C An internal processing error has occurred. The problem can occur during crash recovery if an REORG TABLE operation was running at the time of the crash and the table being reorganized has compressed indexes defined on it. | |
Problem-Zusammenfassung: | |
APAR fix is available in V9.7 Fixpack 5. | |
Local-Fix: | |
Mark the index bad using db2dart /MI command, and restart crash recovery. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
APAR fix is available in V9.7 Fixpack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 18.05.2011 12.12.2011 12.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |