DB2 FOR LUW / DB2FORLUW / B10 - DB2

This situation seems to occur on the first two takeovers after
migration from 9.7 to 11.x (failover and back the first time).
After the first two takeovers, the structures in the LFH/GLFH
files seems to be up to date and subsequent takeovers no longer
exhibit this behavior.

Observed behavior in the db2diag.log

2018-02-22-16.45.14.951000-300 I54293F471           LEVEL: Info
PID     : 1932                 TID : 2848           PROC :
db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   :
SAMPLE
HOSTNAME: MYSERVER
EDUID   : 2848                 EDUNAME: db2logalloc.0 (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqlpLogAllocCandidatePool::removeExtraCandidates, probe:10100
DATA #1 : 
log extent 0 is deleted. logStreamId is: 0

2018-02-22-16.45.14.951000-300 I54766F471           LEVEL: Info
PID     : 1932                 TID : 2848           PROC :
db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   :
SAMPLE
HOSTNAME: MYSERVER
EDUID   : 2848                 EDUNAME: db2logalloc.0 (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqlpLogAllocCandidatePool::removeExtraCandidates, probe:10100
DATA #1 : 
log extent 1 is deleted. logStreamId is: 0

(...)

2018-02-22-21.09.44.641000-300 I929973953F477       LEVEL: Info
PID     : 1932                 TID : 2848           PROC :
db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   :
SAMPLE
HOSTNAME: MYSERVER
EDUID   : 2848                 EDUNAME: db2logalloc.0 (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqlpLogAllocCandidatePool::removeExtraCandidates, probe:10100
DATA #1 : 
log extent XXXXXXX is deleted. logStreamId is: 0

Where XXXXXXX is the current first active log.

**********
If the above takes too long, HADR will fail to connect due to
exceeding the timeout.

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 m4fp4 or later                           *
****************************************************************

N/A

not known / see Local fix

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

19.03.2018
29.11.2018
29.11.2018