DB2 - Problem description
Problem IC68587 | Status: Closed |
CREATE NICKNAME WITH DBLOB COLUMN FAILS WITH SQL0901N | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
SQL0901N can be seen when creating a nickname if: 1. its remote table with a column type that will be mapped to DBLOB on Federation 2. the DBLOB column length is greater than 536870912 This is due to the wrong length being used for the nickname column size checking. For example: On DB2 LUW Datasource create table t1 ( QUERY_TEXT" DBCLOB(536870912)); On Federation Server: create nickname nick for S.schema.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 failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason "Invalid nickname column length".) SQLSTATE=58004 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Persons creating nicknames to access columns that will * * bemapped to LOBs * **************************************************************** * PROBLEM DESCRIPTION: * * SQL0901N can be seen when creating a nickname if:1. its * * remote table with a column type that will be mappedto DBLOB * * on Federation2. the DBLOB column length is greater than * * 536870912 Thisis due to the wrong length being used for the * * nicknamecolumn size checking. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.5 FP7 or newer * **************************************************************** | |
Local Fix: | |
Reduce the remote table column length to less than 536870912 | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
Upgrade to DB2 v9.5 FP7 or newer | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.05.2010 15.11.2010 15.11.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.7 | |
9.5.0.7 |