Incremental Copy Jobs With Data Mover Failover | Teradata Data Mover - Incremental Copy Jobs With Data Mover Failover - 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
For information on Data Mover Failover implementation, see, Fixing Sync Service with High Availability

Previously successful Incremental Copy jobs fails when either secondary Daemon becomes active during a failover or primary Daemon is re-promoted to active after a switch back:

Error code: 1186, error message: Incremental Restore is not being processed in the correct order for table 'db.table'.

DSA does not automatically support failover. Here the Active and Standby DSCs are copying to the same target table with different DELTA job history, resulting in potential conflict when either DSC takes over after a failover or switch back.

To work around the issue, start the failed incremental job with "ir_execution_type" parameter set to "full" to do a FULL table copy: datamove start -job_name my_ir_job -ir_execution_type full