DB2 FOR LUW / DB2FORLUW / A50 - DB2

Under rare timing conditions HADR standby might crash the
instance during the deactivation of the database.

Db2diag.log will contain a message similar to this one:

EDUID   : 216724               EDUNAME: db2shred.3 (SAMPLE) 1
FUNCTION: DB2 UDB, SQO Latch Tracing,
sqlo_xlatch::releaseConflict, probe:10

DATA #1 : String, 27 bytes
unlocking an unlatched lock
DATA #3 : String, 101 bytes
{
   lock          = { 0x00000000 [ unlocked ] }
   identity      = sqeScoordCB::sCoordLatch (135)
}

Stack (included in the db2diag.log) and the trap file will
indicate that error is originating from the following stack:

sqle_panic
sqloSpinLockReleaseConflict
sqleSubCoordTerm
sqeAgent::RunEDU()

****************************************************************
* USERS AFFECTED:                                              *
* PureScale                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Fix in next release,  Db2 11.1 Mod 3 Fix Pack 3              *
****************************************************************

not known / see Local fix

forerunner  : 
follow-up : IT25396 

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

15.06.2018
13.09.2018
13.09.2018