DB2 - Problembeschreibung
Problem IT06493 | Status: Geschlossen |
CLP WILL FAIL WITH SQL30082N RC=17 WHEN USING DB2DSDRIVER.CFG AND CONNECTING TO SERVER WITH AUTHENTICATION=CLIENT SET | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
A CLP (Command Line Processor) connection will fail with an SQL30082N rc=17 (Unsupported Function) when using the db2dsdriver.cfg instead of the database directory to connect to a server that has AUTHENTICATION=CLIENT set in the database manager configuration (dbm cfg) file. A CLI or .NET connection will work with this configuration, and we would like the CLP to be consistent with these two interfaces. Note: DB2 does not support the "CLIENT" value for the "AUTHENTICATION" keyword in the db2dsdriver.cfg or the db2cli.ini file. When using AUTHENTICATION=CLIENT on the server, it would be recommended to catalog the database using the "db2 catalog database" command and to specify "AUTHENTICATION CLIENT" on the "CATALOG DATABASE" command. This will ensure that there is less over head on the connection request. AUTHENTICATION=CLIENT is considered unsecure in a DB2 environment, so use with caution and only in an environment that has tight network security. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1, Fixpack 5 * **************************************************************** | |
Local-Fix: | |
Use the "CATALOG DATABASE" and "CATALOG TCPIP NODE" commands to catalog the remote database at the CLP to allow client authentication. | |
Lösung | |
First fixed in DB2 Version 10.1, Fixpack 5 | |
Workaround | |
see Local Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.01.2015 14.07.2015 14.07.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |