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 IC87913 Status: Closed

FEDERATION SERVER INCORRECTLY SET KRB5CCNAME VARIABLE FROM DB2DJ.INI CAUSES
KERBEROS SUPPORT FOR SYBASE WRAPPER NOT WORK

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When setting up kerberos connection to sybase server you may 
encounter following error: 
 
$ db2 'set passthru <sybase_server>' 
DB20000I  The SQL command completed successfully. 
 
$ db2 "select count(1) from dbo.sysobjects" 
SQL1822N  Unexpected error code "7,9,5,1" received from data 
source  "<sybase_server>". Associated text and tokens are 
"ct_connect(): security service layer: i".  SQLSTATE=560BD 
 
The error happens because you set variable KRB5CCNAME both in 
instance server OS environment and db2dj.ini, Federation Server 
exports both same entries into the environment variables of the 
running process, rather than set the one in db2dj.in only. As a 
result, sybase wrapper may use one of them which is an wrong 
environment variable KRB5CCNAME, so error happens.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* The users are setting up kerberos connection to sybase       * 
* server.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to InfoSphere Federation Server v101fp2 or later.    * 
****************************************************************
Local Fix:
Remove the OS environment variable KRB5CCNAME, set correct 
KRB5CCNAME variable in db2dj.ini, then restart DB2.
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The problem is first fixed at v101fp2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
18.12.2012
18.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList