DB2 FOR LUW / DB2FORLUW / A10 - DB2

A script runs in Task Centre can use db2profile to switch 
instance environment. For example, 
. /home2/db2inst23/sqllib/db2profile 
where db2inst23 can be an instance on a different db2 level. 
The problem is an extra slash is added to env variable LIBPATH 
when the script runs. So it has 
value something like the following : 
/home2/db2ins26/sqllib//lib64:/home2/db2ins26/sqllib/function:/h 
ome2/db2ins26/sqllib/function/unfenced::/home2/db2ins26/sqllib/j 
ava/jdk64/jre/bin/classic:/home2/db2ins26/sqllib/java/jdk64/jre/ 
bin:/home2/db2ins26/sqllib/java/jdk64/jre/lib:/home2/db2ins26/sq 
llib/java/jdk64/lib:/home2/db2ins26/sqllib/java/jdk64/jre/lib/pp 
c64:/home2/db2ins26/sqllib/java/jdk64/jre/bin/j9vm::/home2/db2da 
s/das/lib:/home2/db2das/das/function: 
 
db2profile cannot recognize the extra slash and therefore after 
calling db2profile, the path is still included in LIBPATH: 
$ cat libpath.after 
/home2/db2ins26/sqllib//lib64:/home2/db2ins26/sqllib/function:/h 
ome2/db2ins26/sqllib/function/unfenced:/home2/db2ins26/sqllib/ja 
va/jdk64/jre/bin/classic:/home2/db2ins26/sqllib/java/jdk64/jre/b 
in:/home2/db2ins26/sqllib/java/jdk64/jre/lib:/home2/db2ins26/sql 
lib/java/jdk64/lib:/home2/db2ins26/sqllib/java/jdk64/jre/lib/ppc 
64:/home2/db2ins26/sqllib/java/jdk64/jre/bin/j9vm:/home2/db2das/ 
das/lib:/home2/db2das/das/function:/home2/db2ins23/sqllib/lib64 
 
This is causing the wrong libraries being loaded after the 
instance env switch, ie. libraries from the previous instance 
(db2ins26 in this case) are loaded, instead of 
the libraries from the instance to switch to(db2ins23 in this 
case).

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4                       * 
****************************************************************

In the script, manually add the correct library path of the 
instance to switch to. For example: export 
LIBPATH=/home2/db2ins23/sqllib/lib64:$LIBPATH

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in Version 10.1 Fix Pack 4

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

26.09.2013
02.06.2014
02.06.2014