DB2 - Problem description
Problem IC69581 | Status: Closed |
ALTER TABLE OPERATION MAY LEAVE THE TABLE IN ALTER PENDING STATE AND RETURN SQL0668N RC=8 EVEN IF DB2 HAS BEEN RESTARTED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See error description for details. * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fix pack. * **************************************************************** | |
Local Fix: | |
Commiting every ALTER operation would work around this issue. | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux | |
Solution | |
Problem was first fixed in DB2 UDB version 9.8 fix pack 4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.06.2010 29.07.2011 29.07.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.8.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.4 |