DB2 FOR LUW / DB2FORLUW / A50 - DB2

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

****************************************************************
* USERS AFFECTED:                                              *
* HADR users                                                   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* A small timing window exists where two Standbys may accept a *
* connection from each other at roughly the same time, as they *
* simultaneously see each other as a potential P to connect    *
* to. This can result in an FODC_Trap.                         *
****************************************************************
* RECOMMENDATION:                                              *
* In the case of having a single Standby system, ensure that   *
* your procedures do not result in having two Standby hosts    *
* simultaneously. Also upgrade to v105fp10 to prevent this     *
* FODC_Trap from occurring.                                    *
****************************************************************

not known / see Local fix

forerunner  : 
follow-up : IT24957 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

13.02.2018
12.07.2018
12.07.2018