|
Problem IT18129
|
Status: Closed |
TEST FOR -NOEXEC MOUNT INCORRECTLY FAILS IN DB2SETUP SCRIPT |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
In the db2setup script, the test for -noexec mount on the /tmp
or DB2TMPDIR will fail if any subdirectory has the -noexec
mount, even directories of no interest to DB2.
This error will be present in the install.log:
DBI20043E DB2 failed to install because of restrictive
permission settings on the temporary directory /tmp
The mount command involved lists all the filesystems present
(/tmp , /var/tmp, /abcd/bcf/tmp etc)and the grep command
currently used will check for all directories that have /tmp as
subdirectory including /tmp instead of specifically /tmp or
DB2TMPDIR. This can cause a customer's installation to
incorrectly fail. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher *
**************************************************************** |
| Local Fix: |
If possible, the customer can choose to unmount the directory
with the -noexec option, and remount it after install. |
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.11.2016
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
