Purge the Repository | Teradata Data Mover - Purging the Repository - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.20
Published
November 2021
Language
English (United States)
Last Update
2021-11-04
dita:mapPath
wph1512683331242.ditamap
dita:ditavalPath
4101_UG_dm_1620.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
Data Mover has an internal repository that stores job data from previously run jobs. The purge service is enabled by default and jobs are deleted every 60 days. You can adjust this setting as needed based on your business requirement. You can designate cleanup based on how old the data is, what percentage of the repository is full, or by both age and percent full. A daily cleanup check is performed at the time you specify; and if the age or space threshold is reached, the excess data is deleted from the repository. By default, Data Mover does not delete data that is newer than 5 days.
  1. Run datamove list_configuration to view the current Data Mover configuration settings.
  2. Edit the following settings in the output configuration.xml:
    Setting Description
    repository.purge.enabled Set to TRUE to delete the job history.
    repository.purge.definition.enabled Set to TRUE to delete job history and job definitions.
    repository.purge.history.unit Set to days, weeks, months, or years to delete job history based on age.
    repository.purge.history.unitcount Set to number of days, weeks, months, or years to keep job history based on age. Job history older than this value is deleted. Set to -1 to disable delete by age.
    repository.purge.percent Enter a percentage of permanent space to keep available in the repository. Set to -1 to disable delete by percent.
  3. Run datamove save_configuration -f configuration.xml to save configuration.