Change existing Application Group Expiry type from LOAD to DOCUMENT

[stephen.arnott]

Dear All

Is it possible to change an existing Application group with expiry type set to LOAD to DOCUMENT?

We have encountered a problem with utilising a combination of ODWEK and ONDEMAND. We have an existing Application Group in ONDEMAND that is set up with Expiry Type LOAD, and we now wish to insert documents into that AG using ODWEK, however Ondemand seems not to accept an insertion from ODWEK with Expiry Type = LOAD.

We have tested and find that they are able to insert if the AG had Expiry Type = DOCUMENT.

So, we are looking at whether there is a way to change the existing Expiry Type on an Existing AG from LOAD to DOCUMENT without causing a knock on effect elsewhere.

Please can someone help us to understand if it possible to change the Expiry Type on an existing AG and if so, how do we go about doing this and what are the impacts?


Any thoughts hints suggestions woudl be appreciated

Kind Regards
Stephen

[Justin Derrick]

Hi Stephen.

Changing expiration type of an App Group is not supported. 

However, you can build a new AG with the expiration Type of Document, then group it together with the other AG at the folder level.  You can insert documents from ODWEK into the new AG, and continue to do server-side loads into the old AG.

Remember that Document expiration comes with a price -- incompatibility with certain features (I think Enhanced retention management is one of them) and the fact that running expiration (arsmaint -d) will take considerably longer than the Load or Segment expiration types, as CMOD needs to examine each row, and if that row is eligible for deletion, change the indexes to reflect that.

You might consider loading data into that 'new' AG, extracting the data once a day/week/month with arsdoc, and loading it into the existing AG, and clearing out the new one.

Let us know how you solve your issue!

-JD.