|
Problem IC99580
|
Status: Closed |
RUNNING ADMIN_MOVE_TABLE TWICE DOES NOT SET GENERATE ALWAYS AS IDENTITY VALUES CORRECTLY |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If ADMIN_MOVE_TABLE is run twice without data being inserted
between the moves then columns set as GENERATE ALWAYS AS
IDENTITY will not have their restart values set to the correct
number.
This is due to ADMIN_MOVE_TABLE retrieving the restart value
from SYSCAT.COLIDENTATTRIBUTES, however
SYSCAT.COLIDENTATTRIBUTES only gets set correctly after data has
been inserted into the table. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 and Fix Pack 4 *
**************************************************************** |
| Local Fix: |
Insert data into the table before running ADMIN_MOVE_TABLE the
second time, or run ALTER TABLE with "GENERATE RESTART WITH" to
reset the column with the correct value after the second move. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.02.2014
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
