home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC99747 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.02.2014
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList