- TASM - If Teradata Active System Management (TASM) session rules are enabled on a particular source or target system, the TASM rules may override the Data Mover sessions.
- DBSControl - If you limit the MaxLoadTask and MaxLoadAWT fields of the DBSControl utility, this could override the Data Mover sessions.
You can easily exceed operator limits for a specific target Teradata Database because each Data Mover job can use several instances of these operators, and multiple Data Mover jobs can run at the same time. Data Mover jobs can subsequently fail or hang as attempts to create new instances of the operators are rejected or put on hold by the Teradata Database.
To avoid such failures, Data Mover limits the number of concurrent job tasks, based on the operator being used by the tasks. The limit is enforced independently for each target Teradata Database system. For example, if a job has 10 tasks that use the restricted operators, and the target system load slot limit is 5, Data Mover allows up to 5 of the 10 tasks from that job to run concurrently against the target Teradata Database system. If 2 jobs that each has 10 tasks using the restricted operators are run against the same target Teradata Database system at the same time, Data Mover allows only 5 of the combined 20 tasks from both jobs to run concurrently. If 2 jobs are run against different target Teradata Database systems, and the target system load slot limit is 5 for both systems, Data Mover allows 5 tasks from each job to run at the same time. Data Mover jobs and tasks that use non-restricted operators are not affected by this feature.
The target load slot feature does not affect the number of Data Mover jobs that can run at a specific time or determine which utility Data Mover chooses when creating new jobs.
- A default load slot limit for all target Teradata Database systems
- Different limits for specific target Teradata Database systems