DB2 CONNECT / DB2CONNCT / A10 - DB2

.NET application gives below error message: 
 
Message : [IBM][DB2.NET] SQL0902 An unexpected exception has 
occurred in  Process: 7240 Thread 42 AppDomain: Name:Orcas.exe 
There are no context policies. 
 Function: SQLConnect 
 
CLI Driver throws memory could not read error. This error has 
found on Windows, but may occur on any other platform. On 
windows, CLI Driver may crash with below stack: 
 
  db2app.dll!CLI_csiPostConnect(CLI_CONNECTINFO * 
pDbcInfo=0x03850060)  Line 567 + 0x15 bytes C++ 
  db2app.dll!CLI_sqlConnect(CLI_CONNECTINFO * 
pDbcInfo=0x03850060, sqlca * pSqlca=0x03850ab4, 
CLI_ERRORHEADERINFO * pErrHeader=0x0385010c)  Line 2415 + 0xc 
bytes C++ 
  db2app.dll!SQLConnect2(CLI_CONNECTINFO * pDbcInfo=0x03850060, 
unsigned char * szDSN=0x0385dd70, short cbDSNIn=8, unsigned char 
* szUID=0x0385da2e, short cbUIDIn=8, unsigned char * 
szAuthStr=0x0385da3b, short cbAuthStrIn=8, unsigned char * 
szNewPwd=0x00000000, short cbNewPwdIn=0, unsigned char 
fReadSysOwner='R')  Line 6110 + 0x26 bytes C++ 
 
This error happens because of some fixed number of Keywords in 
the connection string passed to SQLDriverConnect2 from all 
sources.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All CLI Driver user.                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v101fp1 and above fixpack.                    * 
****************************************************************

Add or remove a valid keyword to/from any of connection string, 
db2dsdriver.cfg or db2cli.ini file. The number of keywords 
passed in connection string to SQLDriverConnect2 from all 
sources should get changed from its current count to avoid this 
issue.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

v101fp1 and heigher releases contains this fix. After the fix, 
user fill not face this issue.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

05.06.2012
06.11.2012
06.11.2012