Hi all,
We run ARSMAINT on friday nights to purge old index data per business request. This process is working fine on our Primary site, but on our contingency site the script runs, but does not throw anything in the system log nor does it purge anything. Below is the script that we use:
sudo -S /usr/lpp/ars/bin/arsmaint -d -f 100 -g APPGROUP -I DB2INSTANCE -p ODPW -u ODUSER
This runs and creates hits in the system log related to the purging of the data, but nothing on our contingency site.
One thing to note and IBM has said that this could be a factor- We are performing a migration of cache to tsm. Nightly, the migration process we are running is only creating sym links in the migr directory so our IBM Point of contact for this project says that he wouldn't expect it to interfere with that arsmaint command.
I already have a PMR open and support says that this could be conflicting. I tried running the ARSMAINT out of the time frame that the migration scripts run, and still nothing.
Bump anyone have suggestions?
Hello Jeff,
I'm not sure to understand your problem... so you have a production server (Primary Site), and there the arsmaint works without problem.
But you have a second site (Contingency Site) where it doesn't work.
How both site are related to each other? They have separate TSM nodes? How the sync is done? Is the contingency your backup site?
Maybe stupid questions :-D but I'm trying to understand your situation before giving any kind of advices.
The only thing I can say without saying something too much wrong :-D is that if both site are "independent", meaning that they are not related one to the other, (except maybe each document archived are archive at both site in parallel), then both arsmaint should work the same.
If you are doing some replication on primary to the contingency site, then depending on how you do it, it might be the reason why arsmaint doesn't work as expected.
But without more information it is really difficult to answer.
Sincerely yours,
Alessandro
It seems as though our ARSMAINt is not returning 127 records in the system log since we upgraded to 8.5.0.6. It is not working in our primary and contingency site.
Update on this.
After working with IBM for the past few weeks, our resolution is to run ARSMAINT on our Library Server compared to our Object servers.
Does anyone know why this worked in 8.4.0.3 and 8.5.0.6?
Hello Jeffs42885,
Nice to know that arsmaint should be run on the library server and not object server. To be honest I've only run it in the library server, never tried on an object server.
Thank you for the tip.
Now, why does it work on 8.4.0.X and not on 8.5.X? I cannot answer, only people in the labs.
My personal though on this is that they have vastly rewritten CMOD to handle code page better, and probably during this rewrite they optimized, changed slightly some behavior and corrected some bugs.
And in the process the "feature" that you were using might have been "removed".
So maybe opening a PMR telling that between 8.4 and 8.5 this "feature" doesn't work anymore, and that you consider it as a bug. So maybe it is really a bug, and they will correct it in the next release/fix pack.
Sincerely yours,
Alessandro
Thanks for the feedback, we had a PMR opened with IBM and they said similar feedback.