DB2 FOR LUW / DB2FORLUW / A10 - DB2

Our documentation says, that DB2_HADR_BUF_SIZE upper limit is 4 
GB. In reality, it can be set to much higher values, up to 64GB. 
 
When DB2_HADR_BUF_SIZE is set to such a high value, standby may 
fail to connect to primary within HADR_TIMEOUT time, as the 
allocation/reallocation of that big buffer can take a long time 
to complete. 
 
Primary reports the following message in the db2diag.log file: 
 
2013-11-07-09.33.03.759520+000 I7833873A555       LEVEL: Error 
PID     : 8257942              TID  : 20048       PROC : db2sysc 
0 
INSTANCE: xxxxx               NODE : 000         DB   : yyy 
EDUID   : 20048                EDUNAME: db2hadrp (yyy) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrEduAcceptEvent, probe:20200 
MESSAGE : Did not receive anything through HADR connection for 
the duration of 
          HADR_TIMEOUT. Closing connection. 
DATA #1 : Hexdump, 4 bytes 
0x0A0000001CBF8ADC : 0000 001F 
.... 
 
Standby will the fail with: 
 
2013-11-07-09.35.20.714698+000 I1245568A399       LEVEL: Error 
PID     : 8978638              TID  : 20048       PROC : db2sysc 
0 
INSTANCE: xxxxxx               NODE : 000         DB   : yyy 
EDUID   : 20048                EDUNAME: db2hadrs (yyy) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrTcpIpRecv, probe:11810 
MESSAGE : Zero bytes received. Remote end may have closed 
connection 
 
This APAR will make sure, that the receive buffer is only 
allocated/reallocted, when really needed, to avoid unnecessary 
long allocation times.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************

Set HADR_TIMEOUT to a higher value.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 4.

not known / see Local fix

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

21.11.2013
23.06.2014
23.06.2014