Same here on 5.1.1.1 - looks like the stall (error message is that a
resource waiter has been aborted) happens whenever database
change-intensive processes run at the same time when expiration runs. I
had this happen when move nodedata ran concurrent with expiration and also
when migration ran concurrent with expiration. Good news is that if you
wait one hour, the resource waiter is aborted. In the case of move
nodedata, the process was aborted. In the case of migration, I cancelled
the processes and after an hour expiration picked up and completed
successfully. During my stalls, some backups and restores also stalled,
also a q content of a volume stalled. Backups and restores continued after
the hour wait.

I also have the problem fixed in 5.1.1.2 where delete filespace will not
delete W2K system objects - has anyone installed 5.1.1.2 in a production
environment yet?

Joerg Pohlmann
604-535-0452





"Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2002-08-03 06:36
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Expiration problem with TSM 5.1.1.1 on AIX 4.3.3



I have seen the same problem under V4.2.1.15 but not quite as severe.  The
problem went away with 4.2.2.7.

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


-----Original Message-----
From: Magura, Curtis [mailto:curtis.magura AT LMCO DOT COM]
Sent: Saturday, August 03, 2002 7:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Expiration problem with TSM 5.1.1.1 on AIX 4.3.3


Yep - seeing the same thing. We have three servers. Two are the same
config
you mentioned. The thrid one is hosted on win2k. Also seeing the same
symptoms. Please post back to the list results of the PMR.

Curt Magura
Lockheed Martin EIS
Gaithersburg, Md.
301-240-6305


-----Original Message-----
From: Gerhard Rentschler [mailto:g.rentschler AT RUS.UNI-STUTTGART DOT DE]
Sent: Wednesday, July 31, 2002 4:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Expiration problem with TSM 5.1.1.1 on AIX 4.3.3


Hello,
after one day I got the first more severe problem. I started expiration
and
afterward migration for a storage pool. Later I started migration for
another storage pool. Aftwards I noticed that the expiration and the other
migration processes have stopped advancing their counters. Cancelling the
processes doesn't help. For the expiration I get ANR0819I Cancel in
progress. For the last migration process the cancel was accepted, but
there
was no effect. Everything else (Backup sessions, admin commands) seems to
work.Colleagues from a neighbour university have this problem as well.
They
say after one hour they get an error message and the processes resume
work.

Has anyone else seen this? Is there a circumvention for this?

I created PMR 88563, branch 070, country 724.
Best regards
Gerhard
---
Gerhard Rentschler            email:g.rentschler AT rus.uni-stuttgart DOT de
Regional Computing Center     tel.   ++49/711/685 5806
University of Stuttgart       fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany