Page 1 of 1

job finishes with status =99

Posted: Thu Sep 16, 2010 12:21 am
by DSXRAG
Hi Gurus-

One of my Job is a multi instance job which runs fine most of the time.Some times in any one of the instance the job finishes with status=99.

What are the other possible reasons for 99 status.I know one of them is compiled.

if 99 is NOT RUNNABLE state ,then why the datastage log shows as finished - status=99 ( not runnable )


Thanks
Raghu

Posted: Thu Sep 16, 2010 3:03 am
by piyu
I am assuming you mean its "-99". Officially its a general server error. It could be that its not getting enough resources that's why it runs fine most other times. Do you have too many jobs/instances running at the same time?

Please correct me if I'm wrong..

Posted: Thu Sep 16, 2010 3:17 am
by priyadarshikunal
There is a problem in 8.0 releases with multi-instance jobs and there is a patch for that, however sometimes even that might not work.

For a workaround, switch off the auto-purge for your multi-instance jobs.

Posted: Thu Sep 16, 2010 5:33 am
by chulett
It could also mean it was "not runnable" because that invocation was already (aka still) running from a previous invocation of the job.