home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC80743 Status: Geschlossen

ALTER TABLE WITH ALTER FOREIGN KEY DOES NOT RETURN SQL20269N WHEN
SPECIFYING 'ENFORCED' OPTION TO A NICKNAME

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Federation.                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.5 Fix pack 10.                                 * 
****************************************************************
Local-Fix:
Not available.
Lösung
Problem was first fixed in DB2 UDB Version 9.5 Fix Pack 10.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84119 IC84604 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.01.2012
01.11.2012
01.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP10
Problem behoben lt. FixList in der Version
9.5.0.10 FixList