|
Problem IC68589
|
Status: Closed |
CREATE NICKNAME WITH DBLOB COLUMN FAILS WITH SQL0901N |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| 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 DBCLOB on Federation
2. The DBCLOB 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 defining nicknames on DBCLOB columns *
****************************************************************
* 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 DBCLOB on Federation *
* 2. The DBCLOB 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 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to a fixpak containing the fix for this APAR *
**************************************************************** |
| Local Fix: |
Reduce the remote table column length to less than 536870912 |
| Solution |
Databases at a level that includes this APAR fix should not see
the 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
16.06.2011
16.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
