DB2 - Problembeschreibung
Problem IC69271 | Status: Geschlossen |
ALTER TABLE OPERATION MAY LEAVE THE TABLE IN ALTER PENDING STATE AND RETURN SQL0668N RC=8 EVEN IF DB2 HAS BEEN RESTARTED. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
In some rare cases, where a tables column has been altered to change the column type or length or perhaps changed from NOT NULL to a Nullable column, we may leave table still in alter pending status. Even if the application is no longer around, or you have tried to restart the instance and go through crash recovery. Any access to the table would return SQL0668N RC=8. | |
Problem-Zusammenfassung: | |
In some rare cases, where a tables column has been altered to change the column type or length or perhaps changed from NOT NULL to a Nullable column, we may leave table still in alter pending status. Even if the application is no longer around, or you have tried to restart the instance and go through crash recovery. Any access to the table would return SQL0668N RC=8. | |
Local-Fix: | |
Commiting every ALTER operation would work around this issue. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
apar fixed >= v97 fpk3 | |
Workaround | |
Commiting every ALTER operation would work around this issue. | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC69581 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.06.2010 23.09.2010 23.09.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FPk3 | |
Problem behoben lt. FixList in der Version | |
9.7.0.3 | |
9.7.0.3 |