From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Luke Dahl
>    We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last
>week.  Prior to the upgrade our expiration usually lasted about 24
hours
>(53Gb database).  It would generally post results like this:  examined
>16446439 objects, deleting 59582 backup objects
>Our 3494 library showed est. capacity of 60Tb and approximately 88 pct.
>util.

What is your db's cache hit ratio? 24 hours for a 53GB database is
manifestly too long. It should get through expiration in 2-3 hours. Give
us the output from Q DB F=D.

>Any idea why expiration wasn't running properly prior to the upgrade?
>Data integrity looks good but we've just cleared out loads of space.  I
>don't recall a known bug in expiration processing in 5.1.6.4 but may
>have missed something.  Thanks for your thoughts and input.

How, exactly, did you "clear out loads of space"?

--
Mark Stapleton