DB2 CONNECT / DB2CONNCT / 970 - DB2

.NET DRIVER CRASHES WITH FOLLOWING ERROR IN A MULTI-THREADED 
PROGRAM NAMED ORCAS.EXE USING MULTI ROW INSERT FEATURE: 
 
Unhandled Exception: System.AccessViolationException: Attempted 
to read or write 
 protected memory. This is often an indication that other memory 
is corrupt. 
   at 
IBM.Data.DB2.UnsafeNativeMethods.DB232.SQLExecDirectADONET(DB2Ex 
ecDirectPa 
rameters* pParam) 
   at IBM.Data.DB2.DB2Command.ExecuteNonQueryObject(Boolean 
skipInitialValidatio 
n) 
   at IBM.Data.DB2.DB2Command.ExecuteNonQueryObject() 
   at IBM.Data.DB2.DB2Command.ExecuteNonQuery() 
   at Orcas.TestOrcas.MultiRowInsert(DB2Connection conn) in 
c:\svtwkld\OrcasAppl 
\TestOrcas.cs:line 698 
   at Orcas.TestOrcas.startSelect() in 
c:\svtwkld\OrcasAppl\TestOrcas.cs:line 19 
2 
   at 
System.Threading.ExecutionContext.RunInternal(ExecutionContext 
executionCo 
ntext, ContextCallback callback, Object state, Boolean 
preserveSyncCtx) 
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, C 
ontextCallback callback, Object state, Boolean preserveSyncCtx) 
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, C 
ontextCallback callback, Object state) 
   at System.Threading.ThreadHelper.ThreadStart()

**************************************************************** 
* USERS AFFECTED:                                              * 
* .NET driver users using array insert in a multi-threaded     * 
* application.                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v97fp10 or later releases.                    * 
****************************************************************

db2_v97fp10 contains the fix of this issue. After the fix, no 
crash has been observed.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC99205 IC99206 
Nachfolger : 

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

06.02.2014
10.11.2014
10.11.2014