DB2 - Problem description
Problem IC86631 | Status: Closed |
SQLGETCONNECTATTR() WITH SQL_ATTR_PING_DB RETURNS '0' IMMEDIATELY AFTER A SEAMLESS FAILOVER | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If your are using SQL_ATTR_PING_DB with SQLGetConnectAttr() and a seamless failover takes place after this call, a value of 0 is returned instead of a Warning even if SQL_ATTR_REPORT_SEAMLESSFAILOVER_WARNING is set to YES. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 CLI users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.7 FP8 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
The problem is first fixed in DB2 9.7 FP8 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC87079 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.09.2012 08.04.2013 08.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |