home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT06613 Status: Geschlossen

CLI CONNECTION RETURN WARNING(CLI0004W) WHEN CFG FILE CONTAIN
AUTHENTICATION=CLIENT

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The problem only happens under these conditions: 
 
1. DSN is defined in db2dsdriver.cfg and parameter 
name=authentication is set with value=client 
 
e.g. 
 
<dsn alias="HA" host="hostname" name="SAMPLE" port="12345"> 
<parameter name="Authentication" value="client" /> 
 
AND 
 
2. Same dbalias name as DSN name is catalog in database 
directory. 
 
e.g. 
 
db2 catalog tcpip node nodename remote hostname server 12345 
db2 catalog db sample as ha at node nodename authentication 
client
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to  DB2 LUW Version 9.7 Fixpack 11 or Later.         * 
****************************************************************
Local-Fix:
Remove this line in db2dsdriver.cfg: <parameter 
name="Authentication" value="client" />
Lösung
First Fixed in DB2 LUW Version 9.7 Fixpack 11.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.01.2015
19.10.2015
19.10.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP11
Problem behoben lt. FixList in der Version
9.7.0.11 FixList