DB2 - Problembeschreibung
Problem IC99580 | Status: Geschlossen |
RUNNING ADMIN_MOVE_TABLE TWICE DOES NOT SET GENERATE ALWAYS AS IDENTITY VALUES CORRECTLY | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 4 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 24.02.2014 02.06.2014 02.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |