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

DB2VAL DOESN'T VERIFY THE PERMISSION FOR INSTANCE OWNER HOME
DIRECTORY, MAY RESULT IN SQL1646N ERRORS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Db2val doesn't check the permission for instance owner home 
directory (chkPermOwn). This check is done by both db2iupdt and 
db2icrt. 
Missing rx for other will cause fenced routines to fail: 
as root: 
$ chmod o-rx /home/<instance_name> 
 
as instance owner: 
$ db2start 
$ db2 connect to <db_name> 
$ db2 -x " select count(*) from sysibmadm.snapbp" 
SQL1646N  A routine failed because the fenced user ID cannot 
access required 
files in the sqllib directory or other instance or database 
directories. 
 
so this is something which should be verified by db2val
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 9 or higher                     * 
****************************************************************
Local Fix:
Manually change permissions while the instance is stopped
Solution
First fixed in DB2 10.5 Fix Pack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.04.2017
29.09.2017
29.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)