ARSMAINT is not Expiring/Removing Documents Past their Retention Period

[JFHall]

We run CMOD v9.0 on AIX with the Windows and ODWEK clients.  Our ARSMAINT seems to process only a finite number of application groups when expiring reports that have passed the retention period.  Sometimes it processes only 1 or 2 groups, sometimes a dozen or a few dozen.  But we have 352 application groups in total.  And there is one application group in particular with 7-year retention period that should be getting reports expired from the January 2013 – February 2013 time period; those reports are not getting expired/unloaded.  Below is the command that is run as root.  You can see that we are not passing any specific application group(s), which should mean (I think) that all application groups get processed.

/usr/lpp/ars/bin/arsmaint –cdeimrs

Can anyone think of any reason why all application groups would not be getting processed?  How does ARSMAINT determine which application groups get processed?  And in what order (or is it just random)?

[Justin Derrick]

What is the expiration type (IBM CMOD Admin Client -> Application Group -> Storage Management Tab -> Expire Type pane) for the Application Groups that are causing you problems?

-JD.

[JFHall]

Expiration type is Load.

[Ed_Arnold]

/usr/lpp/ars/bin/arsmaint –cdeimrs

You're asking arsmaint to do a lot in one invocation.

Have you tried breaking that up?

Especially the -r, and maybe the migrate (non-expire) parameters?

Ed

[Justin Derrick]

Ed has the right idea, breaking up the maintenance into a few steps.  You could create a short and simple script to run the steps individually...

Code: [Select]

echo "Expiring data from caches..."
arsmaint -c
echo "Expiring data from App Groups..."
arsmaint -d
echo "Running table maintenance..."
arsmaint -r
echo "Migrating data from cache to long term storage..."
arsmaint -m
echo "Complete."
Also, try using the -g option to run maintenance on a specific Application Group, and keep an eye on the System Log to see if there are messages relating to the issues it's experiencing.  If it fails silently, consider using the arsmaint trace options -1 and -2.

Also, you're running on out-of-support software.  Mysterious bugs and bad behavior are to be expected, unfortunately.

[Stephen McNulty]

Are you getting any errors or warning in the system log during the expiration?  we had issues in the past, that the expiration processing would stop after a problem  (  ie process one or 2 app groups one time, 20 the next).

our workaround was to resolve the problem, or manually force an expiration on the particular app group to get past the issue.  once all we got around all problem app groups, the expiration jobs would run completely.

[JFHall]

We are not getting any warnings or errors.  As for running an outdated version, I'm afraid it's what I'm stuck with for now.  But thank you for some very good sounding suggestions as to other things I can try.  I'll let you know what I learn.