DB2 - Problem description
Problem IT17795 | Status: Closed |
SAP DEV: CLI DRIVER OVERRIDES PRIMARY AFFINITY | |
product: | |
DB2 CONNECT / DB2CONNCT / B10 - DB2 | |
Problem description: | |
SAP has run into an issue related to planned failover with DB2 for z/OS data sharing. When using V111 FP0 SB35734, they see that override affinity does not work anymore. C DB2Trc: 00 000000 cliOverrideAffinity SGA2 C DB2Trc: 00 000000 cliCommit C DB2Trc: 00 000000 cliGetLatestMemberName SGA1 This is from their trace, translated in CLI calls: cliRc = SQLSetConnectAttr ( hDbc, SQL_ATTR_OVERRIDE_PRIMARY_AFFINITY, ( SQLPOINTER ) serverNamePtr, ( SQLINTEGER ) TO_RAW_SZ ( serverNameLength ) ); --> On connection 00 return code 00000 input: serverNamePtr = SGA2 cliRc = SQLEndTran ( SQL_HANDLE_DBC, hDbc, SQL_COMMIT ); --> On connection 00 return code 00000 cliRc = SQLGetConnectAttr ( hDbc, SQL_ATTR_GET_LATEST_MEMBER_NAME, ( SQLPOINTER ) memberNamePtr, TO_RAW_SZ ( memberNameLengthC ), &lnR ); --> On connection 00 return code 00000 output: memberNamePtr = SGA1 No failover happened from SGA1 to SGA2. Therefore it looks like SQL_ATTR_OVERRIDE_PRIMARY_AFFINITY is not working any more. If SAP is using a V105 FP6 driver (this is the only change I do in the system) SQL_ATTR_GET_LATEST_MEMBER_NAME returns SGA2 and they see the failover. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All CLI users connecting using client affinity. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 11.1.1.1 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.11.2016 08.05.2017 08.05.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |