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

THE VALUE OF DB2CLIINIPATH GETS AUTOMATICALLY SET TO "C:PROGRAM
FILESSQLLIB"

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
Environment : 
DB2 V95 anyFP on Windows 
 
Problem Description : 
It appears that fixpack upgrade sets the environment variable 
DB2CLIINIPATH, to another location as the default path for the 
db2cli.ini. Thus the file cannot be found anymore. 
 
Steps to reproduce the issue: 
   - Check db2cli.ini path through db2set -all command.It is not 
set by default so you will not find it in the db2set output. 
   - Upgrade to next FP. (Internally in this step the 
DB2CLIINIPATH path gets set to C:\Program Files\SQLLIB )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users using V9.5 and above versions.                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* THE VALUE OF DB2CLIINIPATH GETS AUTOMATICALLY SET TO         * 
* "C:\PROGRAM FILES\SQLLIB"                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Fixed in v10                                                 * 
****************************************************************
Local Fix:
Setting the environment variable to the correct value resolves 
the issue.
Solution
Fixed in v10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.09.2010
07.07.2011
08.07.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)