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

SLOW ETHERNET FAILOVER OF PRIMARY CF ROLE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If an ethernet failure occurs, the primary CF role will take a 
long time to failover. It can take up to 2 minutes from the time 
of failure until the primary CF role is restarted.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 PureScale users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FP1                                     * 
****************************************************************
Local Fix:
Set the tcp_keepinit value on the CF host to 10 seconds (from 
the default 75 seconds)
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The fix will be included in DB2 V10.1 FP1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.08.2012
07.11.2012
07.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList