Data Cleaning

Data cleaning refers to the process of correcting data in a database or deleting old or inaccurate records.

In DOKA SaaS , we collect many types of data, with  “Dump”, log and Temp files needing most frequent maintenance in order to prevent the disk space filling up.

Transaction SYSCLN
This transaction allows records that have become redundant to be cleaned up either daily or weekly (depending on the size of your installation). All data / files that are date stamped BEFORE the specified selection date will be deleted.

Typical/regular items to clean:
Dump files:  Particularly if you have been testing something new and getting dumps.
Log files: Almost everything is logged in DOKA, so these will build up.
Pick a suitable retention period for troubleshooting and clear down older ones.   

The test mode allows you to see which records / files would be deleted given the current settings to be identified and displayed first, without really deleting them.

The help text for the checkboxes shows the 'typical' and 'maximum' values for each item. 'Typical Value' are values that should be chosen for a typical installation. 'Maximum Values' are values that should not be exceeded without fair reason. Storing data over a longer period produces hard to manage data and does not offer any real advantages.

Save the current settings (the selected options and dates) using the context menu ('Store Values for Transaction') for this transaction. So doing will always save the dates relative to today's date.

If the transaction is run run in the background (e.g. via a script or a crontab) it will process using the selection settings last saved (i.e. options and relative dates).

The location of the transfer directory is read from the INI files of the relevant Managers. Because the location of the archive directory depends on the 'retrieving' system, the location of this directory cannot be freely selected. Therefore all the files in the directory (including sub-directories) defined in the Manager will be deleted based on the date entered. It is the Administrator's responsibility to set a suitable retention period.  

Incoming messages that contain an SMH record should not normally be deleted using SYSCLN.