|
Problem IC68588
|
Status: Closed |
CREATE NICKNAME WITH DBLOB COLUMN FAILS WITH SQL0901N |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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 lenght 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: *
* Users of federation *
****************************************************************
* PROBLEM DESCRIPTION: *
* SQL0901N can be seen when creating a nickname if: *
* 1. It is a remote table with a column type that will be *
* mapped to DBLOB on Federation *
* 2. The DBLOB column length tis 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 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.7 FP4 or newer *
**************************************************************** |
| Local Fix: |
Reduce the remote table column length to less than 536870912 |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Upgrade to DB2 v9.7 FP4 or newer to resolve this issue |
| Workaround |
Reduce the remote table column length to less than 536870912 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.05.2010
08.06.2011
08.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
