Document Based Expiration Type

[nitin.deshpande]

Hello,

I have created an Application Group with expiration type set as document based.
The AG is setup with a "Cache Only" storage set with Life of Data and indexes set as 2 days.

The way I understand it, is the document purge process, in case of document based expiration type, will be done based upon the "Expire Date" field. So the document would be purged by ARSMAINT when the CURRENT_DATE = Date value specified in the field maked as Expire Date.

However, while testing, I can see that the document object is purged whenever the ARSMAINT is run, irrespective of the Date in the Expire Date. I have tested this by setting a future date as Expire date and still the Document Object gets purged if I run the ARSMAINT process today.

Note : The database entires are not deleted for the documents.
The ARSMAINT command and parameters I am using are as below

Code: [Select]

${ARSBIN}/arsmaint -I "${ODINST}" -g "${AG}" -d -c -s -x 0 -n 0
 Please let me know if this is a known issue annd if somebody in the group has encountered this before and any inputs you can provide me to get a work around for this?

[Alessandro Perucchi]

Hello Rooster,

I haven't played very much with expiration type set as "Document" based.

If you are using "cache only", and then you are using the option "-c" in your arsmaint command, then the documents in the cache will be removed and this might cause a problem, because the index will survive, but not your document in cache.

I would test without using the -c, -x and -n options, to see what happens really.

If I have time, I will test it too :-D

Sincerely yours,
Alessandro