Job finishes but the status becomes aborted

[rajeshknl]

Hi,

My parellel job runs successfully. It loads the expected 100 rows to the target. I have verified the target table. But the status of the job becomes 'Aborted' after the run. So i cant re-run the job.

I am using Netezza database as target. I am getting a weird error
"count of bad input rows reached maxerrors limit".

I dont understand what this is. I am sure my target table has the data i am expecting.[/b]

[keshav0307]

its not a weird error.
what is bad record or error limit, you have set.

[ray.wurlod]

What warnings/errors are logged (a) by the DataStage job and (b) in the Netezza environment?

[rajeshknl]

By weird i meant weird in this context. The maxerror count has the default value of 1.


If all the records are loaded in the target where is the scope for bad/error records.

[ray.wurlod]

First line is column names not being properly handled? I recall one job where this was off, even though the first line was column names. The file was sorted as it went through DataStage, and caused the job to abort (from memory with an Invalid number error).

[tkbharani]

I have also faced this problem.
Check if the file count is matching the number of inserted records.

A.May be it, contains some header or footer.
B. Check if your job is no overwriting the error count setting.

Check if any after job soubroutine is being called in the job, which is making it to fail.

[rajeshknl]

I dont have any header/footer. Also i dont have any after/before job subroutines.