PM55074: RC 1027 FAILED TO LOAD SHARED LIBRARY WHEN USING THE DB2 ADAPTER ON 64 BIT LINUX

APAR status

• Closed as program error.

Error description

• A return code of RC 1027 Failed to load shared library error is
  produced when using the DB2 Adapter on 64 bit Linux with 64 bit
  WTX 8.3.0.x.
  The library paths are correct.
  The ldd command indicates that the dependent libraries are
  found successfully in the library path:
  /opt/wtx/libs $ ldd libm4db2.so
          libdb2.so.1 => /cme/db2inst1/sqllib/lib64/libdb2.so.1
  (0x00002b2d51f72000)
          libdstxpi.so => /opt/wtx/libs/libdstxpi.so
  (0x00002b2d53f7a000)
          libc.so.6 => /lib64/libc.so.6 (0x00002b2d54115000)
          libpthread.so.0 => /lib64/libpthread.so.0
  (0x00002b2d5446d000)
          libcrypt.so.1 => /lib64/libcrypt.so.1
  (0x00002b2d54689000)
          libdl.so.2 => /lib64/libdl.so.2 (0x00002b2d548c1000)
          libm.so.6 => /lib64/libm.so.6 (0x00002b2d54ac5000)
          libdb2dascmn.so.1 =>
  /opt/ibm/db2/V9.5/lib64/libdb2dascmn.so.1 (0x00002b2d54d49000)
          libdb2g11n.so.1 =>
  /opt/ibm/db2/V9.5/lib64/libdb2g11n.so.1 (0x00002b2d54f75000)
          libdb2genreg.so.1 =>
  /opt/ibm/db2/V9.5/lib64/libdb2genreg.so.1 (0x00002b2d557f9000)
          libdb2install.so.1 =>
  /opt/ibm/db2/V9.5/lib64/libdb2install.so.1 (0x00002b2d55a3f000)
          libdb2locale.so.1 =>
  /opt/ibm/db2/V9.5/lib64/libdb2locale.so.1 (0x00002b2d55c49000)
          libdb2osse.so.1 =>
  /opt/ibm/db2/V9.5/lib64/libdb2osse.so.1 (0x00002b2d55e6c000)
          libdb2osse_db2.so.1 =>
  /opt/ibm/db2/V9.5/lib64/libdb2osse_db2.so.1 (0x00002b2d56481000)
          libdb2trcapi.so.1 =>
  /opt/ibm/db2/V9.5/lib64/libdb2trcapi.so.1 (0x00002b2d566c6000)
          libstdc++.so.5 => /usr/lib64/libstdc++.so.5
  (0x00002b2d568da000)
          libgcc_s.so.1 => /lib64/libgcc_s.so.1
  (0x00002b2d56bb6000)
          libxml4c.so.57 => /opt/wtx/libs/libxml4c.so.57
  (0x00002b2d56dc4000)
          libcoreapi.so => /opt/wtx/libs/libcoreapi.so
  (0x00002b2d5732d000)
          /lib64/ld-linux-x86-64.so.2 (0x00000034c4c00000)
          librt.so.1 => /lib64/librt.so.1 (0x00002b2d574e4000)
          libicuuc.so.38 => /opt/wtx/libs/libicuuc.so.38
  (0x00002b2d576ee000)
          libicudata.so.38 => /opt/wtx/libs/libicudata.so.38
  (0x00002b2d5792a000)
          libXML4CMessages.so =>
  /opt/wtx/libs/libXML4CMessages.so (0x00002b2d58500000)
          libstdc++.so.6 => /usr/lib64/libstdc++.so.6
  (0x00002b2d5871a000)
          libicui18n.so.38 => /opt/wtx/libs/libicui18n.so.38
  (0x00002b2d58a1a000)
          libmerc_jpn.so => /opt/wtx/libs/libmerc_jpn.so
  (0x00002b2d58c74000)
          libcscr_jpn.so => /opt/wtx/libs/libcscr_jpn.so
  (0x00002b2d58d86000)
  The dlopen utility indicates that the DB2 Adapter library
  opened without an error:
  :/opt/wtx/tmp/LINUX/64 $ ./dlopen_lin64
  ../../../libs/libm4db2.so
  Testing: ../../../libs/libm4db2.so
  NO ERRORS
  NO ERRORS
  clqamc02c:/opt/wtx/tmp/LINUX/64 $
  

Local fix

• WTXCQ - WTX00039215
  PVB/PVB
  Circumvention: Set the following environment variable to
  specify the DB2 client library name:
  export WTX_DB2_LIBRARY_NAME=<...>/libdb2.so.1
  

Problem summary

• Users Affected:
  WebSphere Transformation Extender DB2 Adapter users on 64 bit
  Linux that have a DB2 driver installation that does not contain
  a "libdb2.so" link
  
  Problem Description:
  The DB2 Adapter on 64 bit Linux platforms fails to load.
  
  Platforms Affected:
  Linux 64 bits
  

Problem conclusion

• On 64-bit Linux platforms, the DB2 Adapter attempts to
  dynamically load the DB2 driver module, libdb2.so.  If that
  fails, a second attempt is made to load the module, libdb2.so.1.
   Before this fix, if the libdb2.so module did not exist, the DB2
  Adapter would fail to initialize.  Based on a local DB2
  installation, there should be a link from libdb2.so to
  libdb2.so.1.  If certain configurations do not contain this
  link, then the "libdb2.so.1" module will be loaded instead.  If
  both modules fail to load, an appropriate error will be logged
  to the Adapter trace file and an appropriate return code during
  the DB2 Adapter's connect function.
  
  Delivered in:
  8.3.0.5, 8.4.0.1
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE LAUNC

• Fixed component ID

  5724M4011

Applicable component levels

• R830 PSY

     UP

• R840 PSY

     UP