About Blocked Job Detection - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
kmo1482331935137.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

Data Mover jobs may fail to complete successfully if they are blocked because there are locks on source or target database objects.

Data Mover provides four configuration properties that can be set to detect whether object locks exist, and to retry starting blocked jobs at a specified interval. These blocked job configuration properties can be edited in the configuration.xml file.

If blocked job detection is enabled, Data Mover must execute a query for each table being copied. Therefore, there may be a noticeable decrease in performance when this feature is enabled. If you are moving an entire database, the queries are executed one time on a randomly chosen table in the database to check for database locks.