DB2 FOR LUW / DB2FORLUW / B10 - DB2

On HADR standby, the db2diag.log file is growing very fast with
many messages like the following:

2019-01-25-18.12.54.513886+000 I4134509E612 LEVEL: Info
PID : 17686 TID : 140122481747712 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : TESTDB
HOSTNAME: host1
EDUID : 27 EDUNAME: db2logalloc.0 (TESTDB) 0
FUNCTION: DB2 UDB, data protection services,
sqlpLogAllocCandidatePool::refresh, probe:60
MESSAGE : cpStartExtPos is greater than cpEndExtPos. Forcing
extCount to 0.
DATA #?1 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
798
DATA #?2 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
797

This is a boundary condition, on a new standby database (after
initialization or after takeover command).  The messages will
stop after some work on the primary has generated new log files
for the standby.  Note that in the above example, the value
shown in DATA #1 (which is 798) is the log file number that
would end the boundary condition (ie. the messages will stop
when the primary database is producing log files 798 and
beyond).

****************************************************************
* USERS AFFECTED:                                              *
* HADR standbys                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to the latest fix pack                               *
****************************************************************

Perform work on the primary to generate new log files for the
standby database to process.

Perform work on the primary to generate new log files for the
standby database to process.

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

07.02.2019
31.10.2019
31.10.2019