DB2 - Problem description
Problem IC87092 | Status: Closed |
DB2PREREQCHECK GIVES WARNING "THE 32-BIT LIBRARY FILE LIBPAM.SO IS NOT FOUND ON THE SYSTEM." WHEN THE REQUIRED LIBPAM.SO.0 EXIST | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The db2prereqcheck utility was enhanced to check for libpam.so in DB2 version 9.7 FP6 via APAR IC78338 and the validation is done by looking up "libpam.so" (either a file or a symbolic link) on the system. The original approach was to look up the file libpam.so.0 on system, however this would not work on systems with updated PAM module. PAM module could be updated from time to time and if we hard-coded db2prereqcheck to check for libpam.so.0, then the check would fail on newer system where the module might have updated to upper version like libpam.so.1. In most case a symbolic link of libpam.so would be created to point to latest version of libpam.so.x, hence have db2prereqcheck to look for libpam.so (either a file or a symbol link). This approach was to avoid any further issue with PAM module upgrade on affected platform. However this may not work on older system which has libpam.so.0 only. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fixpack 7 * **************************************************************** | |
Local Fix: | |
Create a symbolic link named libpam.so that points to libpam.so.0: ln -s libpam.so.0 libpam.so | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fixpack 7 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.10.2012 20.10.2012 20.10.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.7 |