ARSMAINT Script

[Sairam]

Hi all,

I am new to On Demand application can anyone please provide the command to me that  how to make the ARSMAINT command run every day/week to purge  the data more than 1.8 months in all folders/application groups.

Note:  all app groups expiry date is set 540 days.


Regards,
Sairam

[Justin Derrick]

I'd start with the documentation:

https://www.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.administeringmp.doc/doddm002.htm

Then, once you understand how expiration in CMOD works, then you can begin automating the process through your operating system's scheduler.  You didn't tell us which OS you're on, so we really can't help with that.

-JD.

[Sairam]

thanks JD for responding to my query,

I am able to purge the data successfully for each and every application group individually. But now I would like to make that automate for each and every application group. How can I provide all application groups in command.

Currently we are working on Linux platform(RHEL 6.x), I want include the automate script in Linux crontab. Please guide me with proper command which includes all the applications groups and requirement is to purge the data that is less than 18 months from todays date.

Regards
Sairam

[Justin Derrick]

Hi.

Have you read any of the documentation or examples on using cron on Linux?  Do you have specific questions about that?

Otherwise, if you have it working properly manually, you just need to put that same command into cron.

-JD.

[Sairam]

Thank you JD,

yes we have Unix team here to help us in cron job. but my quick question is how do I include all the application groups in ARSMAINT command and how to I include my primary requirement of deleting data which is older than 18 months in all the application groups.

Regards,
Sairam

[Justin Derrick]

If you specify no Application Groups, ARSMAINT runs on ALL Application Groups.

Also, the expiration isn't controlled by ARSMAINT itself -- the expiration periods are controlled by the Application Group configuration, under "Life of Data and Indexes".

You're probably confused about the -t option in ARSMAINT.  The short answer is:  Don't use it.  It's a very dangerous option (which is why you need to enter ADMIN credentials when you specify it).

-JD.

[Sairam]

Thank you JD,

already modified the expiration date to 540 days for all the application groups, so now I need to delete the files older than 540 days according to current date, please guide me.


Regards,
sairam

[Justin Derrick]

already modified the expiration date to 540 days for all the application groups, so now I need to delete the files older than 540 days according to current date, please guide me.

But you said earlier:

I am able to purge the data successfully for each and every application group individually.

So, I don't know what you're looking for.

-JD.

[Alessandro Perucchi]

Sairam,

What do you want exactly?

Purge the document from the database OR from the cache?

Could you put an example of the arsmaint with all the options that you are using? (you can omit the -g and the application group name... we need only the options that you are using).

Because if you want to delete the documents in the cache, then it is tricky and CMOD will not delete everything ... it can leave things behind according to the current situation on your server at that day.
If you want to delete documents in your database/tsm, then arsmaint will do it as requested.

So again, tell us exactly what you want to do in details, and please show us the options that you want to use/plan to use.

[Sairam]

Thank you JD,

I have been using the given command  "./arsmaint -cdeimrvs -g  XXXX -I ARCHIVE -t 12546 -n 0 -x 0 -v", to purge the application group wise data, right now I need to purge the all application group data at a time using single command and it should run every day or week. please guide me how can I setup -t value in the command which reflects current date which should be incremental(choose the next corresponding date automatically) and delete the old data which is greater than 540 days on the application group.

Kindly suggest.

Regards,
Sairam

[Sairam]

thanks Alessandro Perucchi for responding to my query,

I need to purge the documents in database and cache,

can you please go through my below comments(last post) you can understand my query. 

Regards,
Sairam

[Justin Derrick]

please guide me how can I setup -t value in the command

Don't use the -t option.  CMOD determines if data is eligible for expiration all by itself, based on the current settings in the Application Group configuration.

Also remove the -g option as Alessandro has mentioned -- if you don't explicitly specify an Application Group, arsmaint will perform the selected expiration (as specified by the options) on all Application Groups.

-JD.

[Alessandro Perucchi]

Well if you put every single option on your arsmaint command... why not.
I prefer to keep things separated.
Only the options for cache, only options for migrations, only command for database expiration.
That way you don't have everything mixed up.

As Justin said. NEVER USE the -t option. This is here for VERY SPECIFIC action, that's why it is required to put the user/pwd with the -t option. Because this is a critical and dangerous option if you don't know how to use it.
And from what I see, you don't know how to use it. So PLEASE do you a favor NEVER use it, as long as you don't know what you are doing.

Now, for your question. If you have define that the data in the database should be kept for 540 days, then the command arsmain -d ... should be enough and CMOD will delete the data that are older than 540days.

BUT there is a catch here, it depends on how the application groups are defined.
If the expiration type is "SEGMENT", then CMOD will delete your data, ONLY if ALL documents in a segment table are > 540 days. If it is not the case, then it will wait until ALL documents in the segments table are older than 540 days, then it will drop the segment tables, and what is in the cache.
If the expiration type is "LOAD", then CMOD will delete your data, ONLY if ALL documents in a single LOAD is >540, otherwise, it will wait until all documents are >540 in this load.
If the expiration type is "DOCUMENT", then CMOD will delete right away each document as soon as it is >540.

If you have the case of an expiration type SEGMENT, and you want to delete everythig >540 before then you need to do things manually.
And you cannot use CMOD arsmaint command. and especially NOT the -t option.