DB2 - Problembeschreibung
Problem IC84395 | Status: Geschlossen |
TABLE COLUMN DEFINITION CHANGES AFTER MOVING TABLE TO DIFFRENT FIXPACK BY ADMIN_MOVE_TABLE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
After creating the table using command below .... DESCRIBE shows Column Length 13 and Scale 12: db2 "create table test ("CHGTSP" TIMESTAMP(12)) in userspace1" db2 "describe table test" Data type Column Column name schema Data type name Length Scale Nulls ----------------- ---------- --------------- ------- ----- ----- CHGTSP SYSIBM TIMESTAMP 13 12 Yes 1 record(s) selected. db2 "insert into test values('2011-09-30 00:00:00.001293952')" DB20000I The SQL command completed successfully. db2 "select * from test" CHGTSP -------------------------------- 2011-09-30-00.00.00.001293952000 1 record(s) selected. DB2 "CALL SYSPROC.ADMIN_MOVE_TABLE ('DBINST97', 'TEST','DMS1','DMS1','DMS1','','','','','','MOVE')" After the table MOVE the TIMESTAMP column has a Columnn Length of 10 and Scale of 6: db2 "describe table test" Data type Column Column name schema Data type name Length Scale Nulls ----------------- ---------- --------------- ------- ----- ----- CHGTSP SYSIBM TIMESTAMP 10 6 Yes db2 "select * from test" CHGTSP -------------------------- 2011-09-30-00.00.00.001293 1 record(s) selected. Here OTM is ignoring the length and scale values while constructing souce table column definition string. Hence we are seeing default length and scale values after table move. Its a product defect | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * db2 luw users * **************************************************************** * PROBLEM DESCRIPTION: * * After creating the table using command below .... DESCRIBE * * shows * * Column Length 13 and Scale 12: * * * * * * * * db2 "create table test ("CHGTSP" TIMESTAMP(12)) in * * userspace1" * * * * * * * * db2 "describe table test" * * * * * * * * Data type Column * * * * Column name schema Data type name Length Scale * * Nulls * * * * * * * * ----------------- ---------- --------------- ------- ----- * * ----- * * * * * * * * CHGTSP SYSIBM TIMESTAMP 13 12 * * Yes * * * * * * * * 1 record(s) selected. * * * * * * * * * * * * db2 "insert into test values('2011-09-30 * * 00:00:00.001293952')" * * * * DB20000I The SQL command completed successfully. * * * * * * * * db2 "select * from test" * * * * * * * * CHGTSP * * * * -------------------------------- * * * * 2011-09-30-00.00.00.001293952000 * * * * * * * * 1 record(s) selected. * * * * * * * * * * * * DB2 "CALL SYSPROC.ADMIN_MOVE_TABLE ('DBINST97', * * * * 'TEST','DMS1','DMS1','DMS1','','','','','','MOVE')" * * * * * * * * After the table MOVE the TIMESTAMP column has a Columnn * * Length * * of 10 and * * Scale of 6: * * * * * * * * * * * * db2 "describe table test" * * * * * * * * Data type Column * * * * Column name schema Data type name Length Scale * * Nulls * * * * * * * * ----------------- ---------- --------------- ------- ----- * * ----- * * * * * * * * CHGTSP SYSIBM TIMESTAMP 10 6 * * Yes * * * * * * * * * * * * db2 "select * from test" * * * * * * * * CHGTSP * * * * -------------------------- * * * * 2011-09-30-00.00.00.001293 * * * * * * * * 1 record(s) selected. * * * * Here OTM is ignoring the length and scale values while * * constructing souce table column definition string. * * Hence we are seeing default length and scale values after * * table * * move. * * * * Its a product defect * **************************************************************** * RECOMMENDATION: * * The problem is first fixed in db2 v10 fp2 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.06.2012 01.04.2013 01.04.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.1 | |
10.5.0.1 |