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 IT26407 Status: Closed

ENGINE CRASH IN SQLDINVCURSORPOS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
db2sysc process abnormally terminates (crash) with panic.
Probability of this crash occurring is rare. This APAR will be
fixed in next release of DB2 and not in v10.5

Stack at failure
pthread_kill
sqloDumpEDU
sqle_panic__Fi
sqldInvCursorPos__FP8sqeAgenti
sqldEndTransaction__FP8sqeAgenti
sqlrr_cleanup_tran_before_DPS__FP8sqlrr_cbiN62PiT9
sqlrrcom__FP8sqlrr_cbiT2
sqlrr_commit__FP14db2UCinterface
sqljs_ddm_rdbcmm__FP14db2UCinterfaceP13sqljDDMObject
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface
sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle
sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb
RunEDU__8sqeAgentFv
RunEDU__8sqeAgentFv
EDUDriver__9sqzEDUObjFv
sqloEDUEntry
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Fixed in v11.1 of DB2 via APAR IT27494                       *
****************************************************************
Local Fix:
Solution
Workaround
See LOCAL FIX
BUG-Tracking
forerunner  : 
follow-up : IT27494 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.09.2018
24.12.2018
24.12.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)