DB2 FOR LUW / DB2FORLUW / A50 - DB2

db2 instance tools like db2idrop or db2iupdt might call 
internally "db2iset -d <instance name>". 
In case there are more than one instance (db2inst1, db2inst2, 
...) which belongs to the same 
DB2COPY (UNIX installation path) then  running "db2iset -d 
<second instance>" will remove 
the instance profile of the first instance. 
 
Example: When we have a scenario with two instances created, 
e.g. db2inst1 is created first and 
db2inst2 is created afterwards. If we run "db2idrop db2inst2" to 
drop the second instance, 
we would call internally 
 
"db2iset -d db2inst2" 
 
this will accidentally remove the instance profile 
(sqllib/profile.env) of the first instance (db2inst1).

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************

Unset global DB2INSTDEF value 
ie) db2set -g DB2INSTDEF=

First fixed in DB2 Version 10.5 Fix Pack 7.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

05.03.2015
20.01.2016
20.01.2016