home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC97816 Status: Closed

STANDBY MAY FAIL TO CONNECT TO PRIMARY WITHIN HADR_TIMEOUT, WHEN
DB2_HADR_BUF_SIZE IS SET TO A VERY LARGE VALUE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4.                      * 
****************************************************************
Local Fix:
Set HADR_TIMEOUT to a higher value.
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.5 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.11.2013
06.11.2014
06.11.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList