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 IT03516 Status: Geschlossen

DB2 ALTOBJ FAILS TO RECREATE FOREIGN KEY WHICH REFERENCES PRIMARY KEY ON
SAME TABLE AND SCHEMA NAME IS 8 CHARACTERS

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When running ALTOBJ on a table which has a Foreign Key which 
references the Primary Key on the same table, the Foreign Key 
will not be recreated if the schema name is eight characters 
long. If the schema name is less than eight characters then the 
Foreign Key will be recreated successfully. 
 
In both cases the ALTOBJ command will report an SQL0204N error, 
but this related to trying to drop the Foreign Key after it has 
already been dropped when the Primary Key was dropped. This 
message is not related to the Foreign Key not being recreated 
successfully.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW 10.5 FixPack 5                            * 
****************************************************************
Local-Fix:
Manually recreate Foreign Key.
Lösung
Fixed in DB2 LUW 10.5 FixPack 5
Workaround
see LOCAL fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
31.07.2014
18.05.2017
18.05.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList