• 2 replies
  • Latest Post - ‏2011-08-26T19:15:24Z by cogura
1 Post

Pinned topic TSM Library Issue

‏2011-07-26T20:15:44Z |

We are trying to unload data from a backup image that is stored in TSM.
Getting following error when I run the command:

INZU462I HPU control step start: 21:12:45.418.
INZM023E Unable to load the Storage tool library (failing library name /opt/IBM/db2/V9.1/adsm/libtsm.a).
INZU463I HPU control step end : 21:12:46.679.
INZU366I HPU return code 8 (reason code 0x283a001)

HPU Version 4.2


DB21085I Instance "db2inst2" uses "64" bits and DB2 code release "SQL09017"
with level identifier "02080107".
Informational tokens are "DB2 v9.1.0.7", "s090308", "U823509", and Fix Pack
Product is installed at "/opt/IBM/db2/V9.1".

"db2hpu.cfg" 7 lines, 117 characters
  1. HPU default configuration

Do we need 32-bit libtsm.a?

Updated on 2011-08-26T19:15:24Z at 2011-08-26T19:15:24Z by cogura
  • SM.
    1 Post

    Re: TSM Library Issue

    Any resolution or suggestion, I am in same pool facing similar issue.

    if it is library compatability, db2hpu -m32 may be one of the options, but its not working in my case.

  • cogura
    1 Post

    Re: TSM Library Issue

    There is no particular mode at the installation time for installing HPU 32 bit or 64 bit.
    On platforms where both 32 bit and 64 bit binaries are existing, for example AIX or Linux xSeries or Solaris, both binaries are always installed.

    Here is how db2hpu script works when 32 bit and 64 bit binaries are both existing:
    • if -m32 is specified in the command line, the 32 bit binary is launched (-v would show 32 bit)
    • if -m64 is specified in the command line, the 64 bit binary is launched (-v would show 64 bit)
    • if neither -m32 nor -m64 are specified in the command line:
    . either the binary to be launched can be chosen according to the DB2 instance concerned, if such an instance is specified, either through the -i option in the command line, or through the default instance parameter in the HPU configuration file: in such a case, the binary chosen is the one having the same bitwidth as the DB2 instance (this determination can be made only if the instance bitwidth can be determined by the db2hpu script)
    • or by default the 32 bit binary is launched (-v would show 32 bits)

    Have you try to add the -m64 option in the db2hpu command?