DB2 - Problem description
Problem IT37965 | Status: Closed |
THE REMOTE CHAR COLUMN LENGTH OVER 86 REPORT SQL0901 AFTER THE COLUMN LENGTH AUTO VARIATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Create nickname if remote table CHAR column length is 10 or 50... up to 85, but it starts failing when it is over 86. I suppose Federation attempted to allocate 3 times bigger column for nickname and it became beyond CHAR max limitation. It leads to "Invalid nickname column length". Since this is no optional, I am afrid that some customer can't create nickname. This is not good. Any workaround can you suggest ?? I know FP6 is coming soon, maybe next week. db2 create nickname t1_nk for udb.db2v115.t1 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0901N The SQL statement or command failed because of a database system error. (Reason "Invalid nickname column length".) SQLSTATE=58004 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * THE REMOTE CHAR COLUMN LENGTH OVER 86 REPORT SQL0901 AFTER * * THE * * COLUMN LENGTH AUTO ARIATION * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 v11.5.7.0 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * THE REMOTE CHAR COLUMN LENGTH OVER 86 REPORT SQL0901 AFTER * * THE * * COLUMN LENGTH AUTO ARIATION * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 v11.5.7.0 * **************************************************************** | |
Comment | |
This is fixed in Db2 v11.5.7.0. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.08.2021 23.11.2021 23.11.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |