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

INSTALLFIXPACK WRITES TO FILES IN THE INSTANCE'S SQLLIB FOLDER
REGARDLESS IF THE DIRECTORY EXISTS OR NOT.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In certain cases, the home directory of a user does not have 
write access. This could be because it is a mount point that was 
created by the root user. Thus, installfixpack will fail because 
it calls an internal script, db2prechk, which attempts to create 
files within the sqllib directory. 
 
You can verify if you have this issue by running the following 
command as the instance owner: 
 
<Install Path>/instance/db2prechk -i 
 
==== 
Example: 
 
$ /opt/IBM/db2/V9.7/instance/db2prechk -i 
 
Cannot create /home/db2inst1/sqllib. 
/home/db2inst1/sqllib: Permission denied 
touch: /home/db2inst1/sqllib/ctrl/.dbmchk/.host_not_stopped 
cannot create 
touch: /home/db2inst1/sqllib/ctrl/.dbmchk/.host_not_accessible 
cannot create 
/opt/IBM/db2/V9.7/instance/db2prechk: 
/home/db2inst1/sqllib/ctrl/.dbmchk/.hostlist: cannot create 
cat: cannot open /home/db2inst1/sqllib/ctrl/.dbmchk/.hostlist 
/opt/IBM/db2/V9.7/instance/db2prechk: 
/home/db2inst1/sqllib/ctrl/.dbmchk/.host_not_accessible: cannot 
open 
/opt/IBM/db2/V9.7/instance/db2prechk: test: argument expected
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If the home directory of a user does not have write access   * 
* the db2prechk will fail.  This could be be caused by a mount * 
* point that was created by the root user.                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 3.                       * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 3.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC70199 IC70458 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.07.2010
16.09.2010
16.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList