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

DB2PROFILE SCRIPT CAN CALL THE USERPFROFILE SCRIPT MORE THAN ONCE.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The ~sqllib/db2profile script to setup the environment for the 
DB2 instance has a call to the ${INSTHOME}/userprofile (for 
custom settings).  However there has been a change to that has 
introduced an additional call to a ${INST_DIR}/userprofile.  If 
${INSTHOME} & ${INST_DIR} point to the same location this can 
result in the script being called twice. 
 
We should look to only call the script once if ${INSTHOME} & 
${INST_DIR} are set to the same location.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 Fixpack 4 or Higher.                * 
****************************************************************
Local Fix:
Can look to modify the userprofile: 
 
if [ "${USERPROFILE_CALLED}" = "TRUE" 
then 
 return 
fi 
USERPROFILE_CALLED=TRUE 
export USERPROFILE_CALLED 
 
So that the userprofile script is only run once.
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 LUW v10.5 Fixpack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.04.2014
15.09.2014
15.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList