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

RARE TIMING DB2 CRASH IN SMP

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 might abend with the following stack on SMP under very rare 
timing conditions: 
 
0x090000000845F12C sqlofmblkEx + 0xD4 
0x090000000A7798A0 
sqldCloseParScan__FP8sqeAgentPP12SQLD_PARSCANP8SQLD_CCB + 0x94 
0x0900000007E20634 sqlricls_complex__FP8sqlrr_cbilN23 + 0x8594 
0x0900000007E298C0 sqlricls_complex__FP8sqlrr_cbilN23 + 0x11A8 
0x09000000081E694C 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x15738 
0x09000000081D2034 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0xE20 
0x09000000081E6C08 @81@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 
0x234 
0x0900000007341118 RunEDU__8sqeAgentFv + 0x2FBDC 
0x0900000007385460 RunEDU__8sqeAgentFv + 0x124 
0x0900000008335F44 EDUDriver__9sqzEDUObjFv + 0x134 
0x09000000076281D0 sqloEDUEntry + 0x390
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.04.2015
14.07.2015
14.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList