DB2 - Problembeschreibung
Problem IC86198 | Status: Geschlossen |
CLI THROWS SQL5163 ERROR DURING CONNECT FOR HOSTNAME OF "CLIENTA FFINITYDEFINED" SECTION IN DB2DSDRIVER.CFG FILE ON SUN64. | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / 970 - DB2 | |
Problembeschreibung: | |
CLI IS NOT ABLE TO GET NETWORK INTERFACE VALUES AND HENCE IP ADDRESS ON SUN64 AND SUNAMD64, HENCE THROWS SQL5163N ERROR. For hostname used under "clientaffinitydefined" section of db2dsdriver.cfg file, CLI throws SQL5163N error while connecting to the database. The issue found on Sun64 and SunAMD64 platforms only. On other platform it works fine. The "db2cli validate -dsn mydsn -connect" also throws same error while trying to connect to the database. SQLDriverConnect: rc = -1 (SQL_ERROR) SQLError: rc = 0 (SQL_SUCCESS) SQLError: SQLState : fNativeError : -5163 szErrorMsg : [IBM][CLI Driver] SQL5163N A required configuration parameter "a qualifying client in affinity group" is missing from the db2dsdriver.cfg configuration file. cbErrorMsg : 159 SQLError: rc = 100 (SQL_NO_DATA_FOUND) | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users using clientaffinitydefined section in db2dsdriver.cfg * * file on Sun64 platform. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2_v97fp7 or later releases. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Lösung | |
db2_v97fp7 contains fix of this issue. After fix, connect will not throw error. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC86898 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 29.08.2012 20.10.2012 20.10.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
9.7.0.7 |