Delete Record Versions

This mode is designed for the production environment to remove the older versions of records.

In addition to the retention period, you can also specify the number of versions prior to the cut off date to be retained. For example, versionsToRetain = 3 signifies that 3 versions which are prior to the cut off date are retained. This execution mode can be specified by using FileWatcher or command-line.

To delete versions, there should be at least one confirmed version of the record. No future dated versions are removed. Versions prior to the last confirmed version qualify for removal. However, if versionsToRetain > 0, some versions may be retained.

For example, record R1 has 10 versions. Version 8 is confirmed, 9 and 10 are unconfirmed. Version 5 is also confirmed. Based on the retention period of 1 year, version 6 or below qualify for deletion. If versionsToRetain is specified as 3, version 3, 2, and,1 are deleted.

When record versions are deleted, the following data is removed for such versions:

  • Principal Key and relationships
  • Data stored in MCT, MVT, BCT, and RCT tables
  • Clearing of cache for deleted record versions
    Delete Record Versions

The following are some of the limitations of this purge:

If the previously defined MVT attribute has been deleted at the cutoff date, the MVT data is not deleted. It does not result in any error, however, the table and data is orphaned.