Hello everybody,

since we've upgraded our ADSM server on AIX from 3.1.0.5
to 3.1.2.20 the expiration process has taken from normally
30 minutes that it runs in the old version to about 4-5 hours
now. When running the expiration process takes most of the
server ressources for itself and doing queries in the db or
doing backups/restores is greatly degradated. We've opened
a call at IBM for this but now I've seen in the fixtest directory
that there's an oxford version (???) that relates this problem.
Can anybody tell me more?

Regards,
_________________ Lauer Edouard ____________________
______ Prod. informatique ____ Systèmes Ouverts ________
__ * +352 4590 3889 __ * Edouard.Lauer AT bil-dexia DOT com __


=============================================================
An electronic message is not binding on its sender.
Any message referring to a binding engagement must be confirmed in writing and 
duly signed.

============================================================