Purging the Repository - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
kmo1482331935137.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

Data Mover has an internal repository that stores job execution data from previously executed jobs. The purge service is enabled by default and jobs will be purged 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 purge 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:
    1. repository.purge.enabled – set to TRUE to delete the job history
    2. repository.purge.definition.enabled – set to TRUE to delete job history and job definitions.
    3. repository.purge.history.unit – set to days, weeks, months, or years to delete job history based on age.
    4. 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 will be purged. Set to -1 to disable purge by age.
    5. repository.purge.percent – enter a percentage of the respository's permanent space to keep available. Set to -1 to disable purge by percent.
  3. Run datamove save_configuration -f configuration.xml to save configuration.