home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT07104 Status: Closed

DB2 .NET APPLICATIONS CRASH IN DB2CSCSTMT.STARTTIMER WHEN OPM EI IS
DEPLOYED AND THE APPLICATION'S DATABASE IS NOT MONITORED

product:
DB2 CONNECT / DB2CONNCT / A50 - DB2
Problem description:
DB2  .NET applications may crash when OPM Extended Insight is 
deployed and the database that the application is connecting to 
is not monitored 
 
Event Viewer may show the following managed stack 
 
IBM.Data.DB2.DB2CscStmt.StartTimer 
IBM.Data.DB2.DB2Command.ExecuteNonQueryObject 
IBM.Data.DB2.DB2Command.ExecuteNonQueryObject 
IBM.Data.DB2.DB2Command.ExecuteNonQuery 
 
Microsoft crash dump will show the following top functions: 
db2app64!CLI_cscStartStmtTimer 
db2app64!CSCStartStmtTimerADONET 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 .Net users on Windows using OPM Extended Insight         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fixpack 7                                * 
****************************************************************
Local Fix:
To avoid the crash, one of the following workarounds are 
available: 
- OPM Extended Insight can be uninstalled 
- Turn monitoring on in the OPM console
Solution
First fixed in DB2 10.5 Fixpack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.02.2015
22.01.2016
22.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList