|
Problem IC77351
|
Status: Closed |
EDM CREATION FAILS IF A CONSTRAINT WITH SAME NAME EXISTS IN ANOTHER TABLE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
During EDM creation, an error saying "constraint with same name
already exists" might be reported. This error happens when two
tables with the same schema uses the same constraint name. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* .NET applications using IBM ADO.NET provider V9.7 FP4 and *
* below *
****************************************************************
* PROBLEM DESCRIPTION: *
* During EDM creation, an error saying "constraint with same *
* name already exists" might be reported. This error happens *
* when two tables with the same schema uses the same *
* constraint name *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 FP5 release *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 5. At a
minimum, this fix should be applied on the client." |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.07.2011
07.12.2011
07.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
