APAMA DB Vacuum

Product: APAMA
Verison:10.15

We are using APAMA to process events and make decisions based on events in a mission critical solution which needs to be up 100% of time.

The issue we are facing is the restart of the APAMA is taking too long (sometimes up-to hours). Upon discussions with product team we found that we need to perform Vacuum DB in a certain interval (weekly/ bi-weekly) to reduce the DB size and it can help to restart in lesser time.

The problem is Vacuum itself takes hours and needs downtime and we are unable to get the needed downtime as the application is mission critical.

Can I please check is anyone faced this issue and is there a way to avoid Vacuum DB which is a manual activity.

Any leads would be great and appreciated.

Regards,
Ashok E.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.