Job is Stalled in the Waiting State - BAR

Teradata Appliance Backup Utility Installation and User Guide

Product
BAR
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-07-13
dita:mapPath
dhb1488824663275.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-3134
lifecycle
previous
Product Category
Teradata Tools and Utilities

A job can be stalled in the waiting state for different reasons, depending on the job process stage.

At the beginning of the job process, all streams must complete logging on to the Teradata Database. This can be time consuming if there are many sessions and job streams, or if online logging is enabled for a job and there is a problem getting the required locks.

In the middle of a job, one or more streams complete processing of the current object. If a specific stream always finishes last, it could be a result of data skew or there might be a performance issue with the associated destination path.

If a job is stalled in the waiting state at the end of job processing, it normally reflects a performance issue. One stream might still be running when other streams have completed. The usual cause is data skew.