DB2 FOR LUW / DB2FORLUW / 970 - DB2

When two tables have the same Foreign key name to refer to each 
other on different parent - dependent relationships, if a column 
(not related to the foreign key columns) is dropped from one of 
the tables, queries or joins that involve those tables might 
fail with SQL0901N REASON "COLUMN NUMBER OUT OF RANGE". 
 
The following example shows this behaviour: 
 
create table t1 (c1 int not null ,c2 int, c3 int,constraint PKt1 
primary key (c1)); 
create table t2 (c1 int not null,c2 int,c3 int,c4 int,constraint 
PKt2 primary key (c1)); 
 
alter table t2 add constraint FK2 foreign key(c4) references t1; 
alter table t1 add constraint FK2 foreign key(c3) references t2; 
 
Note that both tables refer to each other with the same Foreign 
Key name : FK2. 
 
 
db2 alter table t2 drop column c3; 
 
db2 "select * from t1,t2 where t1.c1=t1.c3" 
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

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 and Fix Pack 9                    * 
****************************************************************

Make sure that there are no duplicate Foreign key names between 
a pair of tables. 
Drop and recreate the foreign keys with different names in 
between the pair of tables: 
 
alter table t2 drop foreign key FK2; 
alter table t1 drop foreign key FK2; 
alter table t2 add constraint FK21 foreign key(c4) references 
t1; 
alter table t1 add constraint FK12 foreign key(c3) references 
t2;

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
 

Problem was first fixed in DB2 Version 9.7 and Fix Pack 9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC96294 IC96330 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

19.06.2013
17.12.2013
17.12.2013

9.0.,
9.7.