DB2 FOR LUW / DB2FORLUW / A10 - DB2

In an environment with multiple instances, 
db2iupgrade/db2icrt/db2iupdt of an instance may alter the file 
ownership of another instance's profile.env. This is because the 
 wrong instance (and wrong instance path) is temporarily set 
during db2iupgrade/db2icrt/db2iupdt. The incorrect ownership of 
profile.env will cause db2set commands to fail with permission 
error. 
 
For example, suppose a server has instances db2inst1 and 
db2inst2. After db2inst1 is upgraded, a db2iupgrade of db2inst2 
results in an update to db2inst1's profile.env; db2inst1's 
profile.env will be owned by db2inst2, while db2inst2's 
profile.env remains unaltered. If another instance is created 
(e.g. db2icrt -u xxxxxxxx db2inst3), then db2inst2's profile.env 
will be owned by db2inst3. 
 
This problem is introduced in and specific to v10.1 FP4. The 
profile.env ownerships will need to be corrected manually by 
root.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to v10.1 Fix Pack 6.                                  * 
****************************************************************

N/A

Fixed in v10.1 Fix Pack 6.

not known / see Local fix

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

25.08.2014
13.08.2015
13.08.2015