DB2 - Problem description
Problem IT08196 | Status: Closed |
RUNNING DB2IDROP OR DB2IUPDT TOOLS ON ONE INSTANCE MIGHT CAUSE DROPPING PROFILE ON ANOTHER INSTANCE FROM THE SAME INSTALLATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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). | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL USERS ON UNIX/LINUX PLATFORM * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 11. * **************************************************************** | |
Local Fix: | |
Unset global DB2INSTDEF value ie) db2set -g DB2INSTDEF= | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 11. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.04.2015 09.10.2015 09.10.2015 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP11 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.11 |