DB2 - Problem description
Problem IT19312 | Status: Closed |
REMARKS ON VIEW COLUMNS NOT RETAINED AFTER CHANGES TO BASE TABLE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Remarks on view columns not retained after changes to base table. When we alter underline table, the Remarks on the Columns of our views were lost e.g. $ db2 "create table t1 (col1 varchar(10))" DB20000I The SQL command completed successfully. $ db2 "create view v1 as select col1 from t1" DB20000I The SQL command completed successfully. $ db2 "comment on column jbms.v1.col1 is 'Hello world'" DB20000I The SQL command completed successfully. $ db2 "select char(remarks,30) from syscat.columns where tabname = 'V1'" 1 ------------------------------ Hello world 1 record(s) selected. $ db2 "alter table t1 alter column col1 set data type varchar(20)" DB20000I The SQL command completed successfully. $ db2 "select * from v1" COL1 -------------------- 0 record(s) selected. $ db2 "select char(remarks,30) from syscat.columns where tabname = 'V1'" 1 ------------------------------ - 1 record(s) selected. So Alter statement on Base table deleting the Remark on view.column after "select * from view" (refreshing view) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.02.2017 23.06.2017 23.06.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |