DB2 - Problem description
Problem IT01870 | Status: Closed |
PERFORMING 'UPDATE' THROUGH ENTITY FRAMEWORK RESULTS IN 'SQL0104N ' ERROR WITH LOGICAL TABLES IN IBM I DATABASE SERVER | |
product: | |
DB2 CONNECT / DB2CONNCT / A50 - DB2 | |
Problem description: | |
a) Physical/Logical files are very unique table types available with IBM i and are different from the normal SQL tables and views. If Physical/ Logical files have UNIQUE key defined, it will not be visible as UNIQUE KEY in Entity Framework. b) The root cause for the problem is in the 'Microsoft Entity Framework' layer that does not support 'Update' for tables that have no Primary Keys. DB2Connect is impacted as it inherits this issue from the Microsoft layer and the this APAR will address this issue. c) As part of the fix, DB2 Connect will now support unique-keyed physical and logical files by logically treating them as tables with PRIMARY KEY or UNIQUE constraints. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.5 Fix Pack 5 or higher. * **************************************************************** | |
Local Fix: | |
Solution | |
First fixed in Version 10.5 Fix Pack 5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.05.2014 17.03.2015 17.03.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.5 |