suse 11安装db2时The 32-bit library file libpam.so is not found on the system.

环境：

SUSE Linux Enterprise Server 11 SP1 for AMD64 & Intel64

DB2 9.7 data server trial for Linux® on AMD64 and Intel® EM64T systems (x64)

./db2setup时出现下面错误：

WARNING:
DBT3534W  The db2prereqcheck utility determined that ASLR is set to ON and that this could cause issues with some tools.
WARNING: 
   The 32-bit library file libpam.so is not found on the system. 
DBI1190I  db2setup is preparing the DB2 Setup wizard which will guide
      you through the program setup process. Please wait.

是缺少pam包，但是libpam.so.0已经存在了

emal:/lib # rpm -qa |grep pam
pam-doc-1.0.4-0.5.12
pam-modules-32bit-11-1.6.15
pam_mount-0.47-13.13.65
pam-1.0.4-0.5.12
pam-32bit-1.0.4-0.5.12
pam_mount-32bit-0.47-13.13.65
pam-modules-11-1.6.15
pam-config-0.68-1.22
yast2-pam-2.17.2-0.1.79

解决办法：

ln -s libpam.so.0 libpam.so

参考

http://www-01.ibm.com/support/docview.wss?rs=0&q1=IC87092&uid=swg1IC87092&loc=zh_CN&cs=utf-8&lang

C87092: DB2PREREQCHECK GIVES WARNING "THE 32-BIT LIBRARY FILE LIBPAM.SO IS NOT FOUND ON THE SYSTEM." WHEN THE REQUIRED LIBPAM.SO.0 EXIST

Fixes are available

DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error 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.
  

Local fix

• Create a symbolic link named libpam.so that points to
  libpam.so.0:
  
  ln -s libpam.so.0 libpam.so
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to  DB2 Version 9.7 Fixpack 7                        *
  ****************************************************************
  

Problem conclusion

• First fixed in DB2 Version 9.7 Fixpack 7