In article <57CEF431.A42F.000C.firstname.lastname@example.org>, Erich D. Flynn wrote: > Is there a point at which it is better to just rebuild your mobility DB rather then run the dsapp maintenance? > > The last time i ran the database cleanup it took 13 hours, every time I run it, it takes longer and longer to finish.
I imagine there probably is such a point, but lets see if there might be other, less drastic options. What resources does this box have? # Of CPUs and RAM? If they are fully used during the cleanup, you might get it to run a whole lot faster with more of them. From a separate shell session, watch how much swap space is getting eaten up and if all the CPUs currently assigned are busy, as per http://www.konecnyad.ca/andyk/nixadmin.htm Also look to see how much time the CPUs are waiting for disk, perhaps there is an problem on your disk system that is bogging things down.