Incremental Copy Jobs With Data Mover Failover | Teradata Data Mover - 17.11 - Incremental Copy Jobs With Data Mover Failover - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.11
Release Date
October 2021
Content Type
User Guide
Publication ID
B035-4101-091K
Language
English (United States)
For information on Data Mover Failover implemetation, see, Fixing Sync Service with High Availability

Previously successful Incremental Copy jobs fails when either designated standby Daemon becomes active during a failover or designated active 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