DB2 - Problembeschreibung
Problem IC76346 | Status: Geschlossen |
DB2 REDISTRIBUTE RECOVERY MAY FAIL WITH -902 ERROR | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
It is possible for Redistribute Recovery after a failed redistribute to fail with the following error message: SQL6064N SQL error "-902" occurred during data redistribution. During data redistribution, if the user has not specified "INDEXING MODE DEFERRED", Redistribute will recreate the indexes on all nodes but will not mark them invalid while they are being populated. If redistribute were to be interrupted due to a hardware error or other problem it is possible the index on disk ends up in an inconsistent state. The subsequent REDISTRIBUTE CONTINUE or ABORT command will attempt to read the index on disk since they are not marked invalid but will fail since the indexes are inconsistent. The db2diag.log will indicate an error about a bad index page. Redistribute should mark the index invalid prior to populating it, and mark it valid again once it is finished. That way in case of failure REDISTRIBUTE CONTINUE will not attempt to read the index information. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5. * **************************************************************** | |
Local-Fix: | |
Use DB2DART to manually mark the index invalid and re-issue the REDISTRIBUTE CONTINUE or REDISTRIBUTE ABORT command. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 9.7 Fix Pack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 11.05.2011 16.12.2011 16.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |