home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC68589 Status: Geschlossen

CREATE NICKNAME WITH DBLOB COLUMN FAILS WITH SQL0901N

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
Lösung
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
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.05.2010
16.06.2011
16.06.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version