DB2 - Problembeschreibung
Problem IC71659 | Status: Geschlossen |
DB2 CONNECT IS NOT TRYING TO RECONNECT TO A SYSPLEX SERVER AFTER A FAILURE TO CONNECT TO IT | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / 970 - DB2 | |
Problembeschreibung: | |
When db2 connect have a failure to connect to a sysplex server it will mark it to be in status 1. After a while the db2 connect server should mark it to be in status 2 and try to connect to it again. There is defect that db2 connect is not trying to reconnect. Possible symptoms are: db2pd -sysplex is showing status 1 for a sysplex for hours and days. Other db2 connect servers are connecting to same sysplex server. You can connect direct from the failing db2 connect server. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users that use sysplex. * **************************************************************** * PROBLEM DESCRIPTION: * * When db2 connect have a failure to connect to a sysplex * * server * * it will mark it to be in status 1. After a while the db2 * * connect * * server should mark it to be in status 2 and try to connect * * to it * * again. * * * * * * * * There is defect that db2 connect is not trying to reconnect. * * * * Possible symptoms are: db2pd -sysplex is showing status 1 * * for a * * sysplex for hours and days. Other db2 connect servers are * * * * connecting to same sysplex server. You can connect direct * * from * * the failing db2 connect server. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 fix pack 4 or later versions. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
Fixed in DB2 v9.7 fix pack 4. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.10.2010 19.05.2011 19.05.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP4 | |
Problem behoben lt. FixList in der Version | |
9.7.0.4 |