Job Aborted after 50 errors logged.

venugopal81 · Post by **venugopal81** » Mon Nov 07, 2005 11:06 pm

Hi All,

We have one new issue. Our Job fails everyday if warnings are more than 50. But our run time option is nolimit. Without any changes in the job i ran manually job finished successfuly. Why this situation occurs. The below error message which i got when job ran on schedule. Please suggest me...

DataStage Job 691 Phantom 28092
Job Aborted after 50 errors logged.
Attempting to Cleanup after ABORT raised in stage WFXORDER..TRAN_ORDERS
DataStage Phantom Aborting with @ABORT.CODE = 1

kcbland · Post by **kcbland** » Mon Nov 07, 2005 11:22 pm

Manually run means you used Director? But how does your job run every day? Whatever runs your job, Batch, Sequencer, script, whatever, is responsible for setting that value. It is apparently set to 50.

venugopal81 · Post by **venugopal81** » Tue Nov 08, 2005 4:10 am

Hi kcbland,

Manually means? Using Director we have reset the job and run the job with out any changes. This job scheduled for Mon to Fri in Director. There is no sequence,script or batch process.

rkdatastage · Post by **rkdatastage** » Tue Nov 08, 2005 5:01 am

Hi

check the option while running the job even scheduled

Limits -> warnings

and set the warning limits to unlimited

in your case it is taking the default warning errors limit which is count 50

check it while scheduling

regards
RK

venugopal81 · Post by **venugopal81** » Tue Nov 08, 2005 5:47 am

Hi Rk,

I have checked for scheduled job run options. Here
Limits-->Warnings -->No limit option checked. This problem occurs for last 4 days. Please suggest me.

chulett · Post by **chulett** » Tue Nov 08, 2005 7:52 am

Well, one option would be to fix your job so it doesn't generate any warnings. I'd never consider running any job with unlimited warnings, way too many opportunities for trouble there.

Have you tried unscheduling and rescheduling the job? Not really sure why you would be seeing the behaviour you are seeing, but that might work just like a slap on the side of a TV sometimes 'fixes' it.

manteena · Post by **manteena** » Tue Nov 08, 2005 9:39 am

I think it is better if there are no warnnings,
But as of now...
Unschedule the job.. go director - tools - options- limits-check no limit warnings.
Then rescedule it.
If you done this way ignore this response.

ray.wurlod · Post by **ray.wurlod** » Tue Nov 08, 2005 2:18 pm

Tools > Options only sets the default value.

When you run the job, open the Limits tab in the Job Run Options dialog (in which you are also prompted for parameter values). It's there that the limit for the current run is set.