DB2 - Problembeschreibung
Problem IC66918 | Status: Geschlossen |
AUTOMATIC CLIENT REROUTE IS NOT RETRYING WHEN TIMEOUT VALUE IS SET. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in Version 9.7 Fix Pack 2. The fix should be applied to the client. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC67467 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 05.03.2010 31.05.2010 31.05.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP2 | |
Problem behoben lt. FixList in der Version | |
9.7.0.2 |