|
Problem IC69271
|
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 / 970 - 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: |
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. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
apar fixed >= v97 fpk3 |
| Workaround |
Commiting every ALTER operation would work around this issue. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC69581
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.06.2010
23.09.2010
23.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FPk3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
