Purge Data
To reduce the database size of the ION database you can use the Purge Data page to purge OneView and Confirm BOD history data. You can purge data in two modes.
- Manual Purge: You can purge the data as a one time manual activity. You have the option to simulate the purge before proceeding with actual purge.
- Scheduled Purge: You can set a recurring schedule that triggers the purge process automatically in the background and runs without manual intervention.
Purge manually to optimize performance.
Schedule purges to avoid issues in Production environment such as OneView slowness.
Important! The purge process is now time-based and not id-based. All the documents are purged, including those in-flight, and not yet delivered.
You can purge this data:
- OneView documents
All OneView documents and related events and content where all of the related events happened before the purge date are deleted. Timelines before the selected data become unavailable. In this case messages are selected automatically. This option can only be purged together with the Document contents.
- Document contents
All messages that were registered in ION before the purge date are deleted. Related OneView timelines do no longer show the message content. If you only select messages, the OneView timelines remain available.
- Statistics
Some statistical events and process-related statistics that are used in some Homepages widgets and the Task Viewer contextual application are deleted.
To optimize the purge process, select smaller chunks when purging, for example hours instead of days. Use the same value for all selected data.
- Handled Confirm BODs
All handled Confirm BODs with a time stamp older than the selected purge date are deleted.
Purge Criteria
You can choose the relative age of data to purge in terms of days or hours. All entities older than the specified time are deleted. You can specify separate relative ages for OneView documents, messages, and handled Confirm BODs.