JOB FAILING BECAUSE OF ZERO ROWS IN SOURCE

[arjun_004]

We are inserting data into a Teradata table using the Teradata Enterprise stage.
We observed that whenever there are zero rows in the dataset ( that is the input to this stage), the job fails with the following error:" The runlocally() of the operator failed"
Is this a shortcoming in the Enterprise stage? Is there anyway by which we can ensure that whenever files with zero rows are used, the job is run successfully without errors?

[ray.wurlod]

Search the forum. This is known behaviour. The workaround is to check the number of rows before invoking the job.

[chulett]

Is there anyway by which we can ensure that whenever files with zero rows are used, the job is run successfully without errors?

Use a Server job.