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

HADR STANDBY MAY HANG WHEN ROS IS ENABLED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When Read On Standby is enabled, the DB2 Standby database may 
hang ( and eventually cause the primary database to hang ). 
The db2redom ( redo master ) edu will show a stack with top 
functions : 
 
HdrKickPooledAgents 
HdrForceAppsInReplayOnlyWindow 
 
and there will be an Asynchronous Background Process (ABP or 
db2taskp ) that show as suspended with a stack trace similar to 
: 
 
 
 
thread_wait 
sqloWaitEDUWaitPost 
IntrptWaitLock 
getTaskProAssignment 
main 
abpAgentEntryPoint 
sqleIndCoordProcessRequest 
 
The problem is timing dependent and will not always occur.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR users                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade the DB2 server to V9.7 Fix Pack 8                    * 
****************************************************************
Local Fix:
On the standby instance set : 
db2set DB2_DISABLE_ABP=ON 
before starting the instance, this will disable the Asynchronous 
background tasks from starting. 
However, this should not be set on the primary as that may cause 
maintenance problems ( e.g. Asynchronous Index Cleanup not 
running . ). 
Hence when a failover happens,  a failback should be done as 
soon as possible, or the registry variable should be unset. 
 
on the standby server.
available fix packs:
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
This problem has first been fixed in V9.7 Fix Pack 8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.11.2012
19.04.2013
19.04.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList