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

Z/OS: EDM CREATION FAILS IF A PRIMARY KEY WITH SAME NAME EXIST IN ANOTHER
TABLE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
This problem happens only on z/OS 
 
If more than one table exist in the database with "same primary 
key name" then 
EDM creation gives error saying "The item with identity 'ID' 
already exists in the metadata collection." 
 
Repro. 
-------- 
Create the following two tables in the database and try to 
create EDM by using one of the table. 
 
CREATE TABLE "NEWTON"."AT1" 
( 
"ID" INTEGER  NOT NULL, 
"NAME"  CHAR(12), 
PRIMARY KEY ("ID") 
) ! 
 
CREATE TABLE "NEWTON"."AT2" 
( 
"ID" INTEGER  NOT NULL, 
"NAME"  CHAR(12), 
PRIMARY KEY ("ID") 
) !
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users on .NET Entity Framework executing against DB2 for     * 
* z/OS.                                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If more than one table exist in the database with Primary    * 
* Key consisting of columns with same names ( see table defs   * 
* below ) then                                                 * 
* EDM creation gives error saying "The item with identity 'ID' * 
* already exists in the metadata collection."                  * 
*                                                              * 
* Table Definition Example:                                    * 
*                                                              * 
* CREATE TABLE "NEWTON"."AT1"                                  * 
* (                                                            * 
* "ID" INTEGER  NOT NULL,                                      * 
* "NAME"  CHAR(12),                                            * 
* PRIMARY KEY ("ID")                                           * 
* ) !                                                          * 
*                                                              * 
* CREATE TABLE "NEWTON"."AT2"                                  * 
* (                                                            * 
* "ID" INTEGER  NOT NULL,                                      * 
* "NAME"  CHAR(12),                                            * 
* PRIMARY KEY ("ID")                                           * 
* ) !                                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the client to version 9.7.4.                         * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 8 for Linux, UNIX, and Windows
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

Lösung
Problem was first fixed in Version 9.7 Fix Pack 4.  This fix 
pack should be applied on the client in order to resolve the 
issue.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.03.2011
29.03.2011
29.03.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.4,
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList