Problem when set expiration type to Segment

[teeraw]

I have problem when OnDemand Application Groups were use the expiration type to Segment. When I run arsmaint -cd to expire Database and Cache, it seems only cache files have been deleted. This will cause problem to user cannot retrieve data but index data still shown on OnDemand Client.

Did anyone have suggestion for this problem? How can I workaround for it? (Because I cannot change from Segment to Load expiration type after Application Group was created)

[Alessandro Perucchi]

Hello,

do you have TSM? Or is your Application Groups configured with "Cache Only"?

The problem you describe, is unfortunately not a problem, it works as design. Like it or not...

The idea of expiration type Segment, means that EVERY documents in the segment table must be expired in order to delete the segment. Meaning, if one document has expired today, but the youngest document needs another 10 years for the expiration, then you'll keep your table available for at least 10 years.
And it means also that the documents will have only the link without object behind the scene.

The only method that I can see for you, is to delete the segment links with a "arsdoc delete" for every index that has no object behind anymore.

If you want to change to expiration type "Load", then you'll need (at least from my understanding), to export all documents with indexes, and reload them into a new application group...

The other way, I might have, would be to deactivate the "arsamaint -cd" until you find a way to solve your issue...


I hope somebody else has some idea.

[Justin Derrick]

Put a query restriction on the folder, something like "report_date > (Current_date - days(2557))" -- it'll be much more complex than that, but you get the idea.

Really, the best way forward is to extract & reload the data into a properly configured Application Group.

-JD.