|
Problem IT04044
|
Status: Closed |
CUR_INSTHOME IS NEVER UNSET WHEN DB2PROFILE IS USED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
CUR_INSTHOME is never unset when db2profile is run and it always
retains the value of the previously run db2profile which was
causing problems while removing the old entries.
The problem can be seen when customer is trying to switch from
on instance profile to another one. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to version V9.7FP11. *
* For prior versions, see Circumvention. *
**************************************************************** |
| Local Fix: |
In the db2profile add CUR_INSTHOME in the unset list:
i.e:
done
unset CUR_INSTNAME CUR_INSTHOME path_list class_list
tmp_entry path_name path_value
fi |
| Solution |
Firs fixed in V9.7 FP11 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2014
14.10.2015
14.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
|
 |
