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 IC73754 Status: Geschlossen

CONNECTIONS WITH KERBEROS AUTHENTICATION ARE IMPOSSIBLE FROM A DB2 CLIENT
THAT DOESN'T USE DB2 DATABASE CATALOGS.

Produkt:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problembeschreibung:
If you are trying to connect to a DB2 server, using the Kerberos 
authentication, from a DB2 Client that doesn't use DB2 database 
catalogs, you will receive an error message because CLI doesn't 
have a ini/cfg keyword for passing the principal name. 
 
The following test demonstrates the problem : 
 
With the following db2cli.ini : 
 
[ODBCKB] 
Database=DB2KB 
Trusted_Connection=Yes 
Protocol=TCPIP 
Hostname=LOCALHOST 
Authentication=KERBEROS 
KRBPlugin=IBMkrb5 
;principal=service/host@REALM 
Port=port1 
AutoCommit=0 
 
The following connection fails with this error : SQL30082N 
Security processing failed  with reason "36" ("UNEXPECTED CLIENT 
ERROR"). 
 
 
more test.cli : 
 
opt callerror on 
opt echo on 
sqlallocenv 1 
sqlallocconnect 1 1 
sqldriverconnect 1 0 "DSN=ODBCKB" -3 255 SQL_DRIVER_NOPROMPT 
quit 
 
 
db2cli <  test.cli 
... 
> sqldriverconnect 1 0 "DSN=ODBCKB" -3 255 SQL_DRIVER_NOPROMPT 
SQLDriverConnect: rc = -1 (SQL_ERROR) 
SQLError: rc = 0 (SQL_SUCCESS) 
SQLError: SQLState     : 08001 
          fNativeError : -30082 
          szErrorMsg   : [IBM][CLI Driver] SQL30082N  Security 
processing failed  with reason "36" ("UNEXPECTED CLIENT ERROR"). 
 SQLSTATE=08001 
...
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Clients connecting via Kerberos without using a DB2  * 
* database catalogs.                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP4                                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The problem was first fixed in DB2 9.7 FP4 where a new 
db2cli.ini parameter was introduced : 
TargetPrincipal = name/instance@REALM
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.01.2011
19.05.2011
19.05.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList