DB2 - Problembeschreibung
Problem IC61981 | Status: Geschlossen |
AFTER A LOAD INTO XML TABLE AND A CRASHED LOAD, CRASH RECOVERY REPLAYS THE LOG RECORDS OF THE FIRST SUCCESSFUL LOAD. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
In a recoverable database, if some data are loaded into the XML table using the load command, and the following load crashed. The crash recovery can replay the log records of the first successful load. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 V95 on all platforms * **************************************************************** * PROBLEM DESCRIPTION: * * In a recoverable database, if some data are loaded into the * * XML * * table using the load command, and the following load * * crashed. * * The crash recovery can replay the log records of the first * * * * successful load. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V95fp5 or later. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 9.5 Fix Pack 5. This fix should be applied on the server. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC64054 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.07.2009 18.01.2010 18.01.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP5 | |
Problem behoben lt. FixList in der Version | |
9.5.0.5 |