Hello everyone,

There has been discussion about changes to the Expiration Processing in
later versions of V2 and V3 releases of the server.  I was hoping someone
from Development/Support could give us an overview of exactly how
Expiration works.

For example, our current problem is that we have let expiration run for up
to 5 days and it has never (recently) completed.  Yesterday I stopped it at
the following point: 287,312 examined and 256,474 deleted.  I immediately
restarted it and the examined to deleted ratio as it progressed was about
the same! Today after approximately 16 hours the stats are: 97,778 examined
and 97,075 deleted.

Did it start over from the beginning or does it pick up from where it left
off?

Is there any way for me to query the total number of objects in my database
so I can get an idea of how much is left to be examined?

Is there any reason I should let it fully complete, or can I start and
cancel expiration as required by my daily scheduled activities?

Finally, do these stats seem low or normal?  We have a 20GB database
running on an RS/6000 J40 (4 CPU) with AIX 4.2.1 and ADSM V3.1 (+latest
fix), and by the way I just noticed our Cache Hit Pct is 96.45%

Thanks very much,

Scott.
Scott McCambly
AIX/NetView/ADSM Specialist - Unopsys Inc.  Ottawa, Ontario, Canada
(613)238-5620