DB2 - Problem description
Problem IT09082 | Status: Closed |
ALTER TABLE DROP COLUMN MAY RESULT IN COLLATIONNAME FIELD FOR THE DROPPED COLUMN IN SYSCAT.COLUMNS VIEW TO BE SET AS INVALID. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Issuing an alter table drop column may result in COLLATIONNAME field for the dropped column in syscat.columns view to be set as INVALID. ie. upon querying syscat.columns for that table, we might see an output like the following: db2 "select distinct(COLLATIONNAME) from syscat.columns where TABNAME='<tabname>'" COLLATIONNAME ---------------------------------------------------------------- ---------------------------------------------------------------- INVALID .... This APAR will fix the above observed issue. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * See SYSROUTE APARs to see where this APAR is addressed * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.05.2015 09.05.2017 09.05.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.11 |