On Mon, 25 Sep 1995, BURNS Robert wrote in the thread "Internal Error on
Expiration Proc.":

> The solution from IBM was to perform a standalone audit of the database :
>
>         DSMSERV AUDITDB DISKSTORAGE FIX=YES
>
> ...which lasted for more than 24 hours and locks up the ADSM server during 
> this
> time (great way to spend a weekend !)

More than 24 hours is not much. We have an auditdb running for 19 days
now, and there is nobody who would want to make guesses about the
remaining time.

Hence my question to those who have had this experience with a
sufficiently large database:

Have you seen the effect that after some time there is a saturation from
where onward the process is slower by orders of magnitude? If so, was there
later a speedup again?

What we saw is that the process was fairly quick on the first 13 mio
entries and is now much slower, about 5 or 6 seconds per entry (compute
yourself how long it will take for the remaining 37 mio entries).

If the slowdown effect is normal and there is no subsequent speedup we can
give up right now.

Any help is appreciated.

Best regards,

Helmut Richter

 ============================================================================
Dr. Helmut Richter
Leibniz-Rechenzentrum     X.400:  S=Richter;OU=lrz;P=lrz-muenchen;A=d400;C=de
Barer Str. 21            RFC822:  Helmut.Richter AT lrz-muenchen DOT de
D-80333 Muenchen           Tel.:  ++49-89-2105-8785
Germany                     Fax:  ++49-89-2809460
 ============================================================================