DB2 - Problembeschreibung
Problem IC91269 | Status: Geschlossen |
CONNECTION TO ISERIES USING KERBEROS FAILING WITH SQL30082 RC=36 OR RC=4 | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / A10 - DB2 | |
Problembeschreibung: | |
Kerberos connection to iSeries fails with SQL30082 rc=4 or rc=36 When SQL30082 rc=4 is returned, the db2diag.log contains 2012-06-26-15.19.25.111000-240 I948H343 LEVEL: Severe PID : 3136 TID : 7024 PROC : db2bp.exe INSTANCE: DB2 NODE : 000 EDUID : 7024 FUNCTION: DB2 UDB, bsu security, sqlexSlcGssPluginSecchkrm, probe:250 RETCODE : ZRC=0x805C0151=-2141453999=SQLEX_INVALID_SECTOKEN "Invalid sectoken" When SQL30082 rc=36 is returned, the db2diag.log contains 2012-06-26-15.22.11.923000-240 I948H342 LEVEL: Error PID : 3136 TID : 7024 PROC : db2bp.exe INSTANCE: DB2 NODE : 000 EDUID : 7024 FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20 DATA #1 : String with size, 45 bytes InitializeSecurityContext returned 0x8009030c 2012-06-26-15.22.11.923000-240 E1292H474 LEVEL: Severe PID : 3136 TID : 7024 PROC : db2bp.exe INSTANCE: DB2 NODE : 000 EDUID : 7024 FUNCTION: DB2 UDB, bsu security, sqlexSlcGssPluginSecchk, probe:200 MESSAGE : ADM13000E Plug-in "IBMkrb5" received error code "983040" from the GSS (Generic Security Service) API "gss_init_sec_context" with the error message "The logon attempt failed ". | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users connecting to DB2 for iSeries when using Kerberos * * Authentication * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Apply DB2 10.1 FP3 * **************************************************************** | |
Local-Fix: | |
Use another form of authentication. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in DB2 10.1 FP3 | |
Workaround | |
Use a different Authentication method | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.04.2013 01.10.2013 01.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |