Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.
Moderators: chulett , rschirm , roy
DSXRAG
Participant
Posts: 23 Joined: Mon Nov 16, 2009 5:06 am
Post
by DSXRAG » Thu Sep 16, 2010 12:21 am
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
Rag
piyu
Participant
Posts: 52 Joined: Thu Jul 21, 2005 12:22 am
Location: Singapore
Post
by piyu » Thu Sep 16, 2010 3:03 am
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..
priyadarshikunal
Premium Member
Posts: 1735 Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI
Post
by priyadarshikunal » Thu Sep 16, 2010 3:17 am
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.
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Thu Sep 16, 2010 5:33 am
It could also mean it was "not runnable" because that invocation was already (aka still) running from a previous invocation of the job.
-craig
"You can never have too many knives" -- Logan Nine Fingers