DB2 - Problem description
Problem IC66918 | Status: Closed |
AUTOMATIC CLIENT REROUTE IS NOT RETRYING WHEN TIMEOUT VALUE IS SET. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Automatic Client Reroute does not retry a connection in cases where the timeout is set and it is necessary to do a reconnect for the transport | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Client Reroute and Connect Time-out Users * **************************************************************** * PROBLEM DESCRIPTION: * * Problem Description:Automatic Client Reroute does not retry * * a connection incaseswhere the timeout is set and it is * * necessary to do areconnectfor the transportProblem * * Summary:Automatic Client Reroute does not retry a connection * * incaseswhere the timeout is set and it is necessary to do * * areconnectfor the transport * **************************************************************** * RECOMMENDATION: * * NONE: The issue can be worked around by not setting * * theConnect Time-out * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in Version 9.7 Fix Pack 2. The fix should be applied to the client. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC67467 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.03.2010 31.05.2010 31.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |