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

Load might change the current working directory of db2sysc when loading
LOB/XML data in a non-DPF environment

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When loading LOB/XML data in a non-DPF environment, if LOB/XML 
data resides in separate files (i.e. LOB/XML data is indicated 
by LLS/XDS in data file) and the LOBS/XML FROM parameter is not 
specified (for LOB data, the lobsinfile file type modifier is 
specified), Load might change the current working directory 
(CWD) of db2sysc to the directory where Load is executed. And 
this only applies if the client and server are on the same 
machine. 
 
In the case, it might have some unexpected effects, e.g. you 
might not be able to unmount the file system where Load is 
executed. 
 
The following is an example: 
 
----- example.sh start from here ---------- 
db2start 
DB2SYSCPID=`ps -ef | grep db2sysc | grep $USER |   grep -v grep 
| awk '{print $2}'` 
echo "Time 1:" 
ls -alR /proc/$DB2SYSCPID/cwd 
 
db2 create db test 
db2 connect to test 
db2 "create table tab1 (col1 int, col2 blob)" 
 
echo "Time 2:" 
ls -alR /proc/$DB2SYSCPID/cwd 
 
db2 "load from tab1.ixf of ixf insert into db2inst1.tab1" 
 
echo "Time 3:" 
ls -alR /proc/$DB2SYSCPID/cwd 
----- example.sh end to here ---------- 
 
When a user runs the above example.sh, at Time 1 and Time 2, the 
CWD of db2sysc is '/'. But at Time 3, it is 
"/home/db2inst1/work" where the load is executed. This prevents 
unmounting the file system where "/home/db2inst1/work" is.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 10.1                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 FixPack 3.                           * 
****************************************************************
Local Fix:
Specify the LOBS/XML FROM parameter explicitly for the load.
available fix packs:
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
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.12.2012
27.09.2013
27.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList