DB2 - Problem description
Problem IT20324 | Status: Closed |
DB2: SILENT INSTALLATION MIGHT FAIL WITH SEGV IN ENCODEPASSWORD->STRCPY IF CRYPT() RETURNS AN ERROR (E.G. WITH FIPS_ENABLED) | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Silent installation of DB2 (db2setup) or instance setup (db2isetup) using response file might fail with no error returned to the installation log file due to a segmentation fault (SEGV). The SEGV might be logged to the operating system log file (errpt, messages) indicating a failure of db2iure executable, e.g.: db2iure[28993]: segfault at 0 ip 00007f51f7f7b748 sp00007ffc1b897108 error 4 in libdb2ure.so.1[7f51f7c1e000+4b0000] A core file will show that error is triggered with following functions on the top of the stack: __intel_sse2_strcpy UserManager::encodePassword UserManager::setPassword IUser::setPassword UREInstance::initializeSettings TaskBuildInstanceList::execute URE::start() Problem will be observed in the environments where libc crypt() function, used to encode the password in response file, returns an error, which might happen in the environments where FIPS mode is enforced on the system. On Linux, where problem originally reported, this can be checked by verifying value of /proc/sys/crypto/fips_enabled: EPERM /proc/sys/crypto/fips_enabled has a nonzero value, and an attempt was made to use a weak encryption type, such as DES. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher * **************************************************************** | |
Local Fix: | |
Install DB2 and set up instance in the interactive mode or temporarily disable FIPS during installation. | |
available fix packs: | |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Db2 11.1 Mod 3 Fix Pack 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.04.2017 19.03.2018 19.03.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |