External Purge

In addition to the default purge process, which is automated, you can run an external purge process manually from a command line in case of an installation using IBM Installation Manager or a separate Kubernetes job in case of installation using Certified Containers.

Important: IBM recommends that you not run External Purge and the default purge at the same time, because of risks to your data integrity.

External Purge includes the following features:

Uses a configurable number of threads to allow for scaling
Runs in a separate JVM from the engine and adapters
Runs when the ASI nodes or containers or pods are down, if the database is available