1. Enter the command: instr begin
        2. Let the command run for about 5 minutes.
        3. End the command with: instr end file=server.trace.txt

        Send the file server.trace.txt to my IBM userid in my signature below.

At 09:47 AM 12/16/2004 +0100, you wrote:

Wats about your logpoolsize and logutil at this moment?
regards
joachim

-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]Im Auftrag von
Hart, Charles
Gesendet: Mittwoch, 15. Dezember 2004 21:10
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: 5.2.3.5 Upgrade and Slow Expiration

We have two identical TSM Server (AIX 5.2 / p630 / TSM 5.2.3.5) They were both @ TSM 5.2.3.4 then we upgraded to 5.2.3.5 on the same day. One of the servers has been running just fine (TSM Server1). When the other TSM server (TSM Server2) runs Expiration it grinds to a halt with in an hour regardless of doing a cancel expiration or just trying to cancel the process. This TSMServer2 Backups / Archives our Oracle Env so when Expiration runs it brings the TSM Server instance to its knees to the point it won't take client data.

Server Info:

TSM Server 1 ver 5.2.3.5
DB = 141GB Cache Hit 98.89%
Expiration Runs Fine (thousands obj per min)
        Backup Clients are primarily Windows (4-500 Clients)


TSM Server 2 ver 5.2.3.5
DB = 149GB DB Cache Hit 98.26%
Expiration Runs So Slow (a few obj per min)

Backup Clients are primarily Unix (2-300 Clients) Does dsmc Archives and Incremental

Has anyone run into strange issues when going to 5.2.3.5? I have a PMR open... but not getting much out of them... (Which usually isn't the case) I have searched the list and any APARS... No luck yet.

Appreciate any info!

Dave Canan
TSM Performance
IBM Advanced Technical Support
ddcanan AT us.ibm DOT com