home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC64060 Status: Closed

SQL0901N "COLUMN NUMBER OUT OF RANGE" WHEN DROPPING A COLUMN

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Problem recreation : 
 
a. Create table A 
b. Create table B 
C. Run RUNSTATS on the tables 
d. Create view using two tables 
e. Tried to drop some column on table A  and got: 
 
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 "column number out of range".)  SQLSTATE=58004
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Unknown                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL0901N "COLUMN NUMBER OUT OF RANGE" WHEN DROPPING A        * 
* COLUMNProblem recreation :a. Create table Ab. Create table   * 
* BC. Run RUNSTATS on the tablesd. Create view using two       * 
* tablese. Tried to drop some column on table A  and           * 
* got:DB21034E  The command was processed as an SQL            * 
* statementbecauseit was not a valid Command Line Processor    * 
* command.  DuringSQLprocessing it returned:SQL0901N  The SQL  * 
* statement failed because of a non-severesystem               * 
* error.Subsequent SQL statements can be processed.(Reason     * 
* "column number out of range".)  SQLSTATE=58004               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 2.                       * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
29.06.2010
29.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList