|
Problem IC77742
|
Status: Closed |
SQL_ATTR_GET_LATEST_MEMBER SHOWS INCORRECT MEMBER WHEN CONNECTIO N IS ESTABLISHED TO FIRST MEMBER AFTER LAST MEMBER IS STOPPED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| 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.
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 Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem is first fixed in DB2 Version 9.7 Fix Pack 5 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.07.2011
07.12.2011
07.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
