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 IC78528 Status: Closed

HADR IMPLEMENTATION ON HP COULD SEE HIGH CPU UTILIZATION ON THE STANDBY DUE
TO A HP SPECIFIC IMPLEMENTATION OF RECV() BUFFER.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
recv() is used to retrieve data from the network (in this case, 
from the HADR Primary).  A typical recv() call looks like: 
recv(Socket, pcBuffer, iLength, iFlag). 
 
The retrieved data is placed in a buffer called pcBuffer.  The 
amount of data we want to retrieve (or can retrieve) is iLength. 
A recv() call typically returns only a few KB each time. So 
iLength 
could be multiple GB and yet we may get only a few KB. 
 
Currently, the HADR Standby requests as much data as there is 
space for in the HADR receive buffer (which can configured over 
a GB).  This presents a problem on the HP operating system.  At 
the start of every recv() call, HP validates pcBuffer (up 
through iLength) to ensure that the memory location is legal. 
This requires a lot of extra work (scanning a GB of data 
compared with copying a KB of data).  This validation only 
occurs (that we know of) on HP, so hasn't been a problem with 
other platforms like Linux and AIX.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR users on HP platforms                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without the fix, customer could be exposed to the problem    * 
* described in the APAR error description                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to product v97fp5                                    * 
****************************************************************
Local Fix:
No Local Fix available. Please move to v97fp5
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The fix will be delivered db2_v97fp5. Customers on HP will not 
see the high cpu utilization on standby as described in the 
error description.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.09.2011
12.12.2011
12.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList