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

NULLREFERENCEEXCEPTION RETURNED WITH .NET ENTITY PROVIDER WITH V9.7 FP2

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Entity Data Model (EDM) generation from command line tools such 
as EdmGen.exe may fail with a NullReferenceException: "Object 
reference not set to an instance of an object" if the Entity 
provider is from DB2 v9.7 FP2 (IBM.Data.DB2.Entity). 
The EDM generation from EDM wizard will still work fine with 
this provider. 
 
This can be reproduced using the .NET Framework SDK utility 
called EdmGen.exe using a DB2 Connection string. 
 
The problem does not occur with either the DB2 v9.7 GA or DB2 
v9.7 FP1 .NET Entity providers. 
 
 
 
The full exception call stack will look like this: 
 
----- 
IBM.Data.DB2.Entity.dll!IBM.Data.DB2.Entity.DB2ProviderManifest. 
GetTableType(string 
TableTypesFilter = null, 
IBM.Data.DB2.Entity.DB2ProviderManifest.DbServerType dbs = LUW) 
+ 0x87 bytes 
 
IBM.Data.DB2.Entity.dll!IBM.Data.DB2.Entity.DB2ProviderManifest. 
GetXmlResource(string 
resourceName = 
"IBM.Data.DB2.Entity.DB2StoreSchemaDefinitionForLUW.ssdl", 
IBM.Data.DB2.Entity.DB2ProviderManifest.DbServerType dbs = LUW) 
+ 0x199 bytes 
 
IBM.Data.DB2.Entity.dll!IBM.Data.DB2.Entity.DB2ProviderManifest. 
a() 
+ 0x106 bytes 
 
IBM.Data.DB2.Entity.dll!IBM.Data.DB2.Entity.DB2ProviderManifest. 
GetDbInformation(string 
informationType = "StoreSchemaDefinition") + 0x55 bytes 
 
System.Data.Entity.dll!System.Data.Common.DbProviderManifest.Get 
Information(string 
informationType = "StoreSchemaDefinition") Line 142 + 0x8 bytes 
C# 
 
System.Data.Entity.Design.dll!System.Data.Entity.Design.EntitySt 
oreSchemaGenerator.GetProviderSchemaMetadataWorkspace(System.Dat 
a.Common.DbProviderServices 
providerServices, System.Data.Common.DbConnection 
providerConnection = {IBM.Data.DB2.DB2Connection}) Line 299 + 
0x21 bytes          C# 
 
System.Data.Entity.Design.dll!System.Data.Entity.Design.EntitySt 
oreSchemaGenerator.CreateStoreSchemaConnection(string 
providerInvariantName, string connectionString) Line 277 + 0x9 
bytes    C# 
 
System.Data.Entity.Design.dll!System.Data.Entity.Design.EntitySt 
oreSchemaGenerator.EntityStoreSchemaGenerator(string 
providerInvariantName, string connectionString, string 
namespaceName) Line 63 + 0x1e bytes  C# 
 
EdmGen.exe!System.Data.Entity.Design.EdmExe.EdmGen.GenerateSsdl( 
) 
Line 221 + 0x50 bytes             C# 
 
EdmGen.exe!System.Data.Entity.Design.EdmExe.EdmGen.DoFullGenerat 
ion() 
Line 135 + 0x6 bytes       C# 
 
EdmGen.exe!System.Data.Entity.Design.EdmExe.EdmGen.Main(string[] 
args = {string[4]}) Line 347 + 0x6 bytes                C# 
-----
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Entity Data Model (EDM) generation from command line tools   * 
* such as EdmGen.exe may fail with a NullReferenceException:   * 
* "Object reference not set to an instance of an object" if    * 
* the Entity provider is from DB2 v9.7 FP2                     * 
* (IBM.Data.DB2.Entity).                                       * 
*                                                              * 
* The EDM generation from EDM wizard will still work fine with * 
* this provider.                                               * 
*                                                              * 
* This can be reproduced using the .NET Framework SDK utility  * 
* called EdmGen.exe using a DB2 Connection string.             * 
*                                                              * 
* The problem does not occur with either the DB2 v9.7 GA or    * 
* DB2 v9.7 FP1 .NET Entity providers.                          * 
*                                                              * 
*                                                              * 
* The exception call stack will look like this:                * 
* -----                                                        * 
*                                                              * 
* IBM.Data.DB2.Entity.dll!IBM.Data.DB2.Entity.DB2ProviderManifes 
* TableTypesFilter = null,                                     * 
* IBM.Data.DB2.Entity.DB2ProviderManifest.DbServerType dbs =   * 
* LUW) + 0x87 bytes                                            * 
*                                                              * 
*                                                              * 
* IBM.Data.DB2.Entity.dll!IBM.Data.DB2.Entity.DB2ProviderManifes 
* resourceName =                                               * 
* "IBM.Data.DB2.Entity.DB2StoreSchemaDefinitionForLUW.ssdl",   * 
* IBM.Data.DB2.Entity.DB2ProviderManifest.DbServerType dbs =   * 
* UW) + 0x199 bytes                                            * 
*                                                              * 
* IBM.Data.DB2.Entity.dll!IBM.Data.DB2.Entity.DB2ProviderManifes 
* + 0x106 bytes                                                * 
*                                                              * 
* IBM.Data.DB2.Entity.dll!IBM.Data.DB2.Entity.DB2ProviderManifes 
* informationType = "StoreSchemaDefinition") + 0x55 bytes      * 
*                                                              * 
* System.Data.Entity.dll!System.Data.Common.DbProviderManifest.G 
* informationType = "StoreSchemaDefinition") Line 142 + 0x8    * 
* bytes                                                        * 
* -----                                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v9.7 Fixpak 3a                            * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 3a
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.08.2010
08.11.2010
08.11.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.,
9.7.FP3
Problem behoben lt. FixList in der Version