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

DB2HAICU: ACTIVE/PASSIVE FAILOVER TIME IS UNNACCEPTABLY LONG

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
In the DB2/TSA integrated solution, db2 failover can take over 2 
minutes.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Db2haicu users.                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In the DB2/TSA integrated solution, db2 failover may take    * 
* over 2 minutes.                                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.5.0.5.                              * 
****************************************************************
Local Fix:
The failover time can be reduced by removing the db2gcf -k call 
in db2V95_start.ksh script.
available fix packs:
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 version 9.5.0.5.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC64091 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.08.2009
04.02.2010
04.02.2010
Problem solved at the following versions (IBM BugInfos)
9.5.0.5
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.5 FixList