DB2 FOR LUW / DB2FORLUW / A50 - DB2

In an HADR setup if there checksum mismatch due to network 
issues Standby shuts down with the following db2diag.log message 
and needs to be restarted manually 
 
2017-06-12-09.54.21.617362+330 I85675A559           LEVEL: Error 
PID     : 18088052             TID : 3142           PROC : 
db2sysc 0 
INSTANCE: db2iusr              NODE : 000           DB   : 
SBLPRDDB 
HOSTNAME: xxxxxx 
EDUID   : 3142                 EDUNAME: db2lfr.0 (SBLPRDDB) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrGetBlock, probe:40100 
MESSAGE : ZRC=0x87800148=-2021654200=HDR_ZRC_BAD_LOG 
          "HADR standby found bad log" 
DATA #1 : <preformatted> 
Log page checksum mismatch. pageLso xxxxxx, CheckSum xxxxxxx 
 
This APAR will add additional checksum integrity checks between 
the Primary and Standby and enable Standby to restart 
automatically 
 
The checksum integrity check will be enabled by default and will 
be controlled by a registry variable 
DB2_ENABLE_HADR_LOG_PAGE_INTEGRITY_CHECK. It's dynamic. 
Options: 
1. db2set DB2_ENABLE_HADR_LOG_PAGE_INTEGRITY_CHECK=P 
This would only enable page checksum checking on primary side 
before sending the log data. 
 
2. db2set DB2_ENABLE_HADR_LOG_PAGE_INTEGRITY_CHECK=S 
This would only enable page checksum checking on standby side 
upon receiving log pages but before writing them to disk. 
 
3. db2set DB2_ENABLE_HADR_LOG_PAGE_INTEGRITY_CHECK=L 
This would enable LFR page checksum checking. This is where 
customer encountered the checksum error. 
 
4. db2set DB2_ENABLE_HADR_LOG_PAGE_INTEGRITY_CHECK=A 
All options above are enabled. 
 
5. Any other settings would disable the checking. 
 
As this will have some performance overhead the checking can be 
disabled by 
 
db2set DB2_ENABLE_HADR_LOG_PAGE_INTEGRITY_CHECK=N

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************

Manually restart Standby. If this doesnt help copy the log files 
from the Primary and restart Standby

First fixed in Db2 10.5 Fix Pack 9

not known / see Local fix

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

22.06.2017
29.09.2017
29.09.2017

9.0.