> I have a problem that seems to have effected a bunch of people here.
> Expiration...
>
> I upgraded ADSM and fixed my management classes (I had them set to retain
> omly=1 and retain extra=1 for an SQL management class).  I then started
> expiration.  That was at 10:00am Friday.  It is now Monday and it is still
> running.  It has examined over 2.5 million objects and deleted over 1.5
> million!
>
> Anybody have this happen?

Yes.  The first time from 3.1.1.3 to 3.1.2.1 the system did that.

Now it expiration takes >24 hours, examines about 9 million objects
and deletes a few hundred thousand.  This is on a system with 32
million files in the inventory, plus copy pool references.

Russell