|
Problem IT36757
|
Status: Closed |
CLR PROCEDURE ABORTS ABNORMALLY WITH ERROR SQL1024N WHEN IT USESIBM.DATA.DB2 .NET provider
|
| product: |
DB2 CONNECT / DB2CONNCT / B50 - DB2 |
| Problem description: |
CLR procedure aborts abnormally when it use IBM.Data.DB2,
IBM.Data.DB2.dll is a .NET provider/API for connecting to
database, CLR procedure works fine if it doesn't use
IBM.Data.DB2.
The error is database connection failure in DB2ConnPool.Open
IBM.Data.DB2.DB2Exception: ERROR [08003] [IBM] SQL1024N A
database connection does not exist. SQLSTATE=08003
at IBM.Data.DB2.DB2ConnPool.Open(DB2Connection connection,
String& szConnectionString, DB2ConnSettings& ppSettings, Object&
ppConn)
at IBM.Data.DB2.DB2Connection.Open()
at IBM.Data.DB2.DB2Connection.OpenNull(DB2ContextInternal
context)
at IBM.Data.DB2.DB2Context.DB2ContextInternal.GetCommand()
at IBM.Data.DB2.DB2Context.GetCommand()
As long as customer use .NET API in their CLR procedure, they
will be impacted. Customers using C or java interface might also
be impacted.
This will result in procedure execution failure and db2fmp will
be terminated and recreated. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Customers using .NET API in their CLR procedure *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V11.5.6.0 or later. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Customers using .NET API in their CLR procedure *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V11.5.6.0 or later. *
**************************************************************** |
| Comment |
Problem fixed in V11.5.6.0 and later. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.05.2021
21.06.2021
21.06.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
