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

POSSIBLE TRAP (FODC) IN 'HDREDUACCEPTEVENT()' DUE TO INVALID CONNECTION
SEQUENCE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Possible trap (FODC) may occur in 'hdrEduAcceptEvent()' due to
an invalid sequence of connections,
that is for example trying to enable HADR on a database where
both hosts are 'standby' due to some
previous error.

The stack trace in the FODC will look like this (this might vary
based on the platform):

0x09000000122D369C
hdrEduAcceptEvent__6hdrEduFP8HDR_DBCBP14HDR_EVENT_TYPEPP11HDR_HD
R_MSGPP8HDR_RQST + 0x38D8
0x09000000122BF57C hdrEduS__6hdrEduFPUl + 0x191C
0x09000000122A2FB0 RunEDU__6hdrEduFv + 0x2264
0x090000001436B704 EDUDriver__9sqzEDUObjFv + 0x3F0
0x090000001436B704 EDUDriver__9sqzEDUObjFv + 0x3F0
0x0900000013ED94C4 sqloEDUEntry + 0x3A4
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT24063 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.05.2018
27.11.2018
27.11.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)