DB2 - Problem description
Problem IC67473 | Status: Closed |
CHANGES MAY NOT BE EFFECTIVE WHEN ALTERING TABLE ATTRIBUTE AND COLUMN INLINE LENGTH IN A SINGLE ALTER TABLE STATEMENT | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When attempting to modify both the table attribute (e.g. row compression) and column inline length within the same ALTER TABLE statement, the system catalog is updated with the new inline length but no actual changes are applied on the physical inline length. However, the change to the table attribute will be taken effect. Example: db2 "create table t1(i int, c clob(2000))" db2 "alter table t1 compress yes alter column c set inline length 1000" db2 insert ... # inserting data db2 "select i, admin_is_inlined(c) is_inlined from t1" I IS_INLINED ----------- ---------- 10 0 1 record(s) selected. db2 "select char(colname,20) column_name, char(tabname,10) table_name, inline_length from syscat.columns where tabname = 'T1'" COLUMN_NAME TABLE_NAME INLINE_LENGTH -------------------- ---------- ------------- C T1 1000 I T1 0 Local Fix: Running the alterations in separate ALTER TABLE statements. db2 alter table t1 compress yes db2 alter table t1 alter column c set inline length 1000 db2 "select i, admin_is_inlined(c) is_inlined from t1" I IS_INLINED ----------- ---------- 10 1 1 record(s) selected. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * When user alter table attribute and column inline length ina * * single alter table statement. * **************************************************************** * PROBLEM DESCRIPTION: * * When attempting to modify both the table attribute (e.g. * * rowcompression) and column inline length within the same * * ALTERTABLE statement, the system catalog is updated with the * * newinline length but no actual changes are applied on * * thephysical inline length. However, the change to the * * tableattribute will be taken effect.Example:db2 "create * * table t1(i int, c clob(2000))"db2 "alter table t1 compress * * yes alter column c set inlinelength 1000"db2 insert ... # * * inserting datadb2 "select i, admin_is_inlined(c) is_inlined * * from t1"I IS_INLINED----------- ----------10 * * 01 record(s) selected.db2 "select char(colname,20) * * column_name, char(tabname,10)table_name, inline_length from * * syscat.columns where tabname= 'T1'"COLUMN_NAME * * TABLE_NAME INLINE_LENGTH-------------------- ---------- * * -------------C T1 1000I * * T1 0Local Fix:Running * * the alterations in separate ALTER TABLE statements.db2 alter * * table t1 compress yesdb2 alter table t1 alter column c set * * inline length 1000db2 "select i, admin_is_inlined(c) * * is_inlined from t1"I IS_INLINED----------- * * ----------10 11 record(s) selected. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 FixPack 3 or later release. * **************************************************************** | |
Local Fix: | |
Separate changes to table attributes and column attributes into different ALTER TABLE statements. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 3. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC69504 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.03.2010 19.10.2010 19.10.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |