We went from 4.2.2.7 to 4.2.2.12, not as large a jump as you and we saw this
problem has well.  Have you checked your db cache hit ratio?  We had to
increase the bufferpool size significantly, we needed to anyway.  It appears
4.2.2.12 is much more sensitive to low db cache hits.  As for database
backups, I think there is a problem there, ours are taking much longer than
before.  I am still trying to isolate the problem.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Halvorsen Geirr Gulbrand [mailto:gehal AT WMDATA DOT COM]
Sent: Wednesday, September 18, 2002 3:59 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: !Urgent - SDLT/TSM slow after upgrade from v. 4.2.1.7 to v. 4.2.2
.12


Hi Everyone!
For one of our customers I have recently upgraded their TSM server (and TSM
device-driver) from v. 4.2.1.7 to 4.2.2.12, because of added support for
multiple modules of library Compaq MSL5026DLX. Configuration is now: TSM
Server (+dev.driver) v. 4.2.2.12 Library Compaq MSL5025DLX (2 modules) with
3 SDLT 220 drives.

After the upgrade, many of the processes takes a very long time to complete.
Expiration used to take 10-15 minutes, takes now 1,5 hours. Database backup
used to take about 20 minutes, takes now 1-2 hours, migration is slow,
space-reclamation is very slow, and when they try to stop spacereclamation,
it takes hours before it stops.

I'm sorry I don't have any numbers (MB/s) for these processes. I might have
more data on this by tomorrow. But I would like to know if anyone else have
seen similar problems after an upgrade.

Any help is highly appreciated!

Rgds.
Geirr G. Halvorsen