Troubleshooting DELTA execution failures | Teradata Data Mover - Troubleshooting DELTA Execution Failures - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.12
Published
January 2022
Language
English (United States)
Last Update
2022-01-18
dita:mapPath
ptl1635805434108.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
During DELTA executions, previously successful incremental copy jobs may fail with following errors:
  • Error code: 1187, error message: Incremental Restore is not allowed because table 'db.table' is not in read-only state
  • Error code: 1186, error message: Incremental Restore is not being processed in the correct order for table 'db.table'
These errors indicate job conflicts due to multiple jobs copying to the same target table, for example:
  • A BAR restore job and a Data Mover incremental job copying to the same target table
  • Two Data Mover incremental jobs copying to the same target table

To recover from above job failures, re-run 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

To prevent future errors, user needs to make sure not to restore or copy to the same target table across BAR and Data Mover DSCs.