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

DB2 STORED PROCEDURES ARE UNABLE TO LOAD THE GSKIT SHIPPED WITH DB2

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
DB2 Server uses GSKit for SSL support and there are IBM products 
that have DB2 Stored Procedures that uses GSKit for SSL.  By 
default, the Stored Procedure should be loading the GSKit that 
is 
 
shipped with DB2.  However, a defect in the Stored Procedure 
infrastructure is preventing the Stored Procedure from finding 
the GSKit
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1.4                                       * 
****************************************************************
Local-Fix:
Use the DB2 registry variable DB2LIBPATH to help the Stored 
Procedure find GSKit.  For example: 
db2set DB2LIBPATH= 
$HOME/sqllib/lib64/gskit:$HOME/sqllib/lib32/gskit
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.02.2014
02.06.2014
02.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList