Dynamically forced FULL execution | Teradata Data Mover - Dynamically Forced FULL Executions - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.11
Published
October 2021
Language
English (United States)
Last Update
2021-10-14
dita:mapPath
cai1626458602965.ditamap
dita:ditavalPath
cai1626458602965.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

Ideally, a DSA incremental copy job only starts a one-time FULL copy during the first job run, with DELTA executions to follow.

DSA dynamically forces a FULL execution if any of the following happens after a previous job execution:

  • A table is write enabled, for example, if user started the job with "-ir_allow_write true" in the previous job run
  • Source or target incremental restore GDO flags have changed
  • User has run “dsc reset_ir_target_system” command to reset target system GDO flag to IR enabled
  • Job definition has changed affecting job objects or job options including online archive, skip stats, and skip join or hash indexes.