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

Teradata® Data Mover User Guide - 20.01

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
hlv1700545853003.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
don1467241476387
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.