Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC94117 Status: Closed

UPDATE A NICKNAME WITH MORE THAN 1012 COLUMNS MAY RESULT IN SQL0901N

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
You may receive -901 error when trying to update a nickname with 
more than 1012 columns: 
 
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 "Error in column idrange".)  SQLSTATE=58004 
 
Reproduce: 
 
SET PASSTHRU OS400SERV; 
DROP TABLE  TMANYCOLUMNS; 
CREATE TABLE TMANYCOLUMNS(C1 CHAR(1),C2 CHAR(1),...C1500 
CHAR(1)); 
SET PASSTHRU RESET; 
 
CREATE NICKNAME NICK1 FOR OS400SERV.MYSCHEMA.TMANYCOLUMNS; 
 
UPDATE NICK1 SET C1013= 'A' WHERE C1='1'; 
 
NOTE: The error only happens when there is at least one column 
with column id >1012 in the SET STATEMENT.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* The users trying to update a nickname with more than 1012    * 
* columns.                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 fp4.                                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The problem is firstly fixed on v10.1fp4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.07.2013
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList