DB2 - Problembeschreibung
Problem IC77742 | Status: Geschlossen |
SQL_ATTR_GET_LATEST_MEMBER SHOWS INCORRECT MEMBER WHEN CONNECTIO N IS ESTABLISHED TO FIRST MEMBER AFTER LAST MEMBER IS STOPPED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
The SQL_ATTR_GET_LATEST_MEMBER returns the last member when connection is established to the first member, after the last member is stopped. Repro using 2-member sysplex: -connect to the sysplex -sql_attr_get_latest_member returns 1st member -stop 1st member -connect to the sysplex again -sql_attr_get_latest_member returns 2nd member -stop 2nd member, start 1st member -connect to the sysplex again -sql_attr_get_latest_member returns 2nd member, but should be 1st member | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All DB2 Version 9.7 Fix Pack 3 and 4 clients using * * SQL_ATTR_CONNECT_NODE CLI attribute. * **************************************************************** * PROBLEM DESCRIPTION: * * The SQL_ATTR_GET_LATEST_MEMBER returns the last member when * * connection is established to the first member, after the * * last member is stopped. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
The problem is first fixed in DB2 Version 9.7 Fix Pack 5 and all subsequent Fix Packs. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 26.07.2011 07.12.2011 07.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |