|
Problem IC65582
|
Status: Closed |
DELETE FROM TABLE MAY RETURN SQL0440N AFTER A COLUMN WAS DROPPED FROM ITS DEPENDENT/PARENT TABLE IN A FOREIGN KEY CONSTRAINT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
This problem may affect either the parent or the dependent table
in a foreign key constraint, depending on the table against
which the DROP COLUMN was issued.
Dropping a column from a table involved in a foreign key
constraint may cause incorrect updates to the referential
constraint descriptor of the "partner" table. As a result, a
DELETE FROM against the "partner" table may return SQL0440N due
to a column type mismatch caused by the corrupted descriptor.
The following error message is returned:
SQL0440N No authorized routine named "=" of type "FUNCTION"
having compatible arguments was found. SQLSTATE=42884
One condition that may lead to this problem is when column(s)
with higher column id value comes before column(s) with lower
column id value in the foreign key definition.
e.g. db2 "alter table t2 add constraint fk foreign key (c3, c1,
c2) references t1 (c3, c1, c2)" where c1 represent column with
column id 1. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Version 9.7 GA through Fix Pack 1 serverson Linux, *
* Unix and Windows where a column isdropped from a table *
* involved in a foreign keyconstraint. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Dropping a column from a table involved in a foreign *
* keyconstraint may cause incorrect updates to the *
* referentialconstraint descriptor of the "partner" table. As *
* a result, aDELETE FROM against the "partner" table may *
* return SQL0440Ndue to a column type mismatch caused by the *
* corrupteddescriptor. *
****************************************************************
* RECOMMENDATION: *
* Update to Version 9.7 Fix Pack 2 *
**************************************************************** |
| Local Fix: |
Contact IBM Support to have the corrupted descriptor patched. |
| 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 |
Problem was first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
See LOCAL FIX |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.01.2010
25.05.2010
25.05.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
|
 |
