On Solaris 2.8

$ db2level
DB21085I Instance "icmlsdb" uses "32" bits and DB2 code release "SQL08013"
with level identifier "02040106".
Informational tokens are "DB2 v8.1.0.24", "s030728", "U488482", and FixPak "3".
Product is installed at "/opt/IBM/db2/V8.1".

In trying to work on cross node recovery using TSM I found a wierd issue. One server thinks it has the wrong version of the TSM client.

$ db2adutl query full db sample


Error. Unsupported TSM client API version 4.1.2 detected.
DB2 supports a minimum version of 4.2.0.

$ dsmc
Tivoli Storage Manager
*** Fixtest, Please see README file for more information ***
Command Line Backup Client Interface - Version 4, Release 2, Level 1.21
(C) Copyright IBM Corporation, 1990, 2001, All Rights Reserved.

So the client is actually at release 4.2.

$ db2 backup db sample online use tsm
SQL2079N An error was reported by the shared library
"/export/home/icmlsdb/sqllib/adsm/libtsm.a". Return code: "3".

$ ls -l /export/home/icmlsdb/sqllib/adsm/libtsm.a
-r-xr-xr-x 1 bin bin 46216 Jul 31 2003 /export/home/icmlsdb/sqllib/adsm/libtsm.a

I have the identical binary on a different system which works fine with
the same DB2 version and TSM client version.

works% db2 backup db sample use tsm

Backup successful. The timestamp for this backup image is : 20040416154745


works% ls -l /export/home/icmlsdb/sqllib/adsm/libtsm.a
-r-xr-xr-x 1 bin bin 46216 Jul 31 2003 /export/home/icmlsdb/sqllib/adsm/libtsm.a

works% dsmc
Tivoli Storage Manager
*** Fixtest, Please see README file for more information ***
Command Line Backup Client Interface - Version 4, Release 2, Level 1.21
(C) Copyright IBM Corporation, 1990, 2001, All Rights Reserved.


Any thoughts?

TIA

Ken

Turns out the TSM client install was schmutzed. One of the libraries was actually 4.1.2. The TSM admin reinstalled the client and all is well.