|
Problem IC84599
|
Status: Closed |
ALTER COLUMN SET DATA TYPE NOT BLOCKED FOR ROW CHANGE TIMESTAMP COLUMN |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
A row change timestamp column must have data type
TIMESTAMP(6). This is correctly enforced by CREATE TABLE
and ALTER TABLE ADD COLUMN. However, the data type can be
changed via:
ALTER TABLE <table> ALTER COLUMN <row change column>
SET DATA TYPE <data type>
This should be blocked with SQLCODE SQL0190 if <data type>
is not TIMESTAMP(6) but the alteration succeeds. The result
is possible abnormal termination of the DB2 server and
general unpredictable behaviour with respect to the row
change timestamp column.
Use the following query to identify any tables that have a
row change timestamp column with an invalid type:
SELECT TABSCHEMA, TABNAME, COLNAME FROM SYSCAT.COLUMNS
WHERE ROWCHANGETIMESTAMP = 'Y'
AND ( TYPENAME != 'TIMESTAMP' OR SCALE != 6 ) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 fix pack 1 *
**************************************************************** |
| Local Fix: |
To fix such a table, alter the column back to TIMESTAMP(6)
ALTER TABLE <table> ALTER COLUMN <row change timestamp column>
SET DATA TYPE TIMESTAMP(6) |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 version 10.1 fix pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
19.11.2012
19.11.2012 |
| 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
|
|
