DB2 - Problem description
Problem IC84119 | Status: Closed |
ALTER TABLE WITH ALTER FOREIGN KEY DOES NOT RETURN SQL20269N WHEN SPECIFYING 'ENFORCED' OPTION TO A NICKNAME | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In a Federated configuration, assume we have a nickname refers to a table REMOTE_TAB on a remote server with column PK as the primary key of the table. DB2 allows users to create a foreign key to the nickname only with the option NOT ENFORCED. If creating with the option ENFORCED is specified, the error code SQL20269N is given. However, if a user first creates the foreign key with the option NOT ENFORCED and then uses the ALTER TABLE to change from NOT ENFORCED to ENFORCED, DB2 does not return any error although the foreign key constraint is not validated. Subsequently any INSERT/DELETE/UPDATE operations to the tables in the foreign key relationship could produce an internal error as follows: SQL0901N The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason "sqlnt_add_select_list [200]:rc( 0) Error pushing d".) SQLSTATE=58004 When the problem is fixed, the ALTER TABLE.. ALTER FOREIGN KEY with the ENFORCED option to a nickname will return the error SQL20269N. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * User using federated database. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V9.7 Fix Pack 7. * **************************************************************** | |
Local Fix: | |
Not available. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 7. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.06.2012 01.11.2012 01.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.7 |