Just went from v18.104.22.168 to v22.214.171.1240. The procedure went smoothly,
but so far I'm not impressed with the client backup - slow to start, slow
to run. I'd hate to think that the only solution for the performance is a bit
of sleight of hand to reconstruct the tablespace.
Database is only ~350G with ~360 million objects.
Just not sure if I'm going to stay at v7.
From: ADSM: Dist Stor Manager [ADSM-L AT vm.marist DOT edu] on behalf of Stef
Coene [stef.coene AT DOCUM DOT ORG]
Sent: Monday, August 10, 2015 10:51 AM
To: ADSM-L AT vm.marist DOT edu
Subject: [ADSM-L] expire inventory and delete filespace hangs
We have a V7 TSM server (upgraded from V6).
Expire inventory hangs after running a few hours and we also found a filespace
that we can not delete. The delete filespaces command just hangs.
The only way to cancel the expire inventory and the delete filespace is to halt
The TSM database is 850 GB.
When we contacted IBM support and after tracing the server, they told us it's
a performance problem. I don't understand why they think it's performance
related because all the clients and other server processes are running fine.
The fact that the TSM database, recovery log and archive log is stored on a
SVC with FlashSystem 840 as backend was not impressive enough.
To resolve the performance issues, they want us to convert the DB2 from V6
tablespace format to V7 tablespace format. They can provide scripts for this,
but you need to be a DB2 guru to execute the scripts. This will give as an
extra performance boost, but also a 30% reduction of the database!
Since they consider this a performance issue, the upgrade procedure is not
Has someone else got the same advice and if yes, have you followed the
procedure and what was the result?