DB2 - Problem description
| Problem IC84395 | Status: Closed |
TABLE COLUMN DEFINITION CHANGES AFTER MOVING TABLE TO DIFFRENT FIXPACK BY ADMIN_MOVE_TABLE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| 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 | |
| Problem Summary: | |
****************************************************************
* 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: | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 01.04.2013 01.04.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.1 |
|
| 10.5.0.1 |
|