DB2 - Problem description
Problem IT33712 | Status: Closed |
COMPLETE FIX FOR IT13674 | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
The logic used to fix IT13674 (the underlying DB2 defect) used grep -w, or similar, which is insufficient when /tmp is overmounted with a different filesystem with correct parameters. WHY LOCAL FIX DOES NOT WORK: Due to /etc/mtab being a link to /proc/self/mounts, it is not directly editable. Due to /tmp being in use, it cannot be force unmounted twice in order to work around this. A remount will not work, because the top level mount is valid already, and the db2setup checks for this simply do not notice it. The last entry in mtab is the one that actually is in use. mtab is a link to /proc, so that is not editable APAR FIX: [root@azesp01b01 install]# pwd /sp/software/816srv/repository/native/1/ese/db2/linuxamd64/insta ll [root@azesp01b01 install]# diff db2setup db2setup.old 137c137 < foundit=`mount | grep -w ${TMPDIR?} | tail -1 | grep "noexec" 2> /dev/null` --- > foundit=`mount | grep -w ${TMPDIR?} | grep "noexec" 2> /dev/null` | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.0 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.07.2020 20.11.2020 20.11.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |