DB2 - Problem description
Problem IT39759 | Status: Closed |
ON AIX WHEN A SCRIPT NEEDS TO EXECUTE DB2PROFILE IN A LOOP, LIBPATH HAS MULTIPLE REFERENCES TO GSKIT | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
On AIX customer has a batch that execute in a look db2profile. Doing that, LIBPATH has multiple references to gskit like: LIBPATH=/usr2/db2inst1/sqllib/lib64:/usr2/db2inst1/sqllib/lib64/ gskit:/usr2/db2inst1/sqllib/lib64/gskit:/usr2/db2inst1/sqllib/li b64/gskit:/usr/lib:/lib Customer has detected that increased CPU usage This does not occur on Linux as the code is different in db2profile: On AIX in db2profile: LIBPATH=${LIBPATH:-"/usr/lib:/lib"} LIBPATH="${INST_DIR}/lib64:${INST_DIR}/lib64/gskit:${LIBPATH?}" export LIBPATH On Linux in db2profile: LD_LIBRARY_PATH=${LD_LIBRARY_PATH:-""} AddRemoveString LD_LIBRARY_PATH ${INST_DIR}/lib64 a AddRemoveString LD_LIBRARY_PATH ${INST_DIR}/lib64/gskit a AddRemoveString LD_LIBRARY_PATH ${INST_DIR}/lib32 a export LD_LIBRARY_PATH | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * On AIX only * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to next release in 11.5 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * On AIX only * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to next release in 11.5 * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.01.2022 18.04.2022 18.04.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |