Job Aborts abruptly after reaching 1000 records

deepak.shanthamurthy · Thu Jan 25, 2007 12:14 pm

Hi,
I have a job which runs fine with a lesser number of records without any warning messages but the same job fails when i test with 1000 records.
The only message that is logged is

Attempting to Cleanup after ABORT raised in stage Job1..Transformer_1

i have tried running the job after clearng the &PH& directory but of no use ...

Any thoughts why this is happening...

Thanks,
Deepak

us1aslam1us · Post by **us1aslam1us** » Thu Jan 25, 2007 12:22 pm

It warning message doesn't say much.
Try to Reset the job from the Director and let us know if you get a new entry in the log that says "From previous run...". If so, double-click on it and post the contents.

I_Server_Whale · Post by **I_Server_Whale** » Thu Jan 25, 2007 12:24 pm

You need to provide more information.

* What is the objective of your job?
* What is your job design?
* What are the metrics at which the job fails?
* Sample data.
and so on.

The information your provided is insufficient to even make a guess.

Whale.

ray.wurlod · Post by **ray.wurlod** » Thu Jan 25, 2007 3:20 pm

Take a look at the "job starting" message in the log. Has the run limit been set to 1000 rows?

If so, go to the Director client and click the Run tool again. In the Job Run Options dialog (where parameters are prompted for) select the Limits tab. What do you see there? Click Cancel so that the job does not actually run.

Now go to the Tools menu and select Options. In the Options dialog you can reset the run limit. 0 means unlimited.

deepak.shanthamurthy · Thu Jan 25, 2007 4:07 pm

thank you all the job was failing because of the warning limit though there were no warnings that were being generated initially....i cleared the status and log for the job and it starts raining warnings.....

Appreciate your help

Thanks,
Deepak