Abnormal Termination of Stage

rajendharreddy · Post by **rajendharreddy** » Mon Jun 15, 2009 5:09 am

Hi,

I am trying to run a job but this is aborting with error in the log "Abnormal termination of stage ********** detected.

I reset the job and see the same error without much help.

Error: "Abnormal termination of stage LoadsCausalStageSchema..Xfm detected"

Job Design: Iam loading data from a sequential file to DB2 Stage and there are 5 records only. The table has 2 columns. There is a transformer stage in between but not transformation is done.

This job runs fine in dev project but is failing in qa project. Both dev and qa are on the same box with just project name being different.

Any help on this is much apprecited.

Thanks

Rajendhar

ArndW · Post by **ArndW** » Mon Jun 15, 2009 6:19 am

Please post the full and complete error message, that also contains the text describing why the stage aborted. Without that we would just be guessing.

chulett · Post by **chulett** » Mon Jun 15, 2009 6:45 am

And when you Reset the aborted job, is there a "From previous run..." log entry added? If so, post the contents of it as well.

pxraja · Post by **pxraja** » Tue Jun 16, 2009 12:40 am

Hi

whenever I was facing this problem i used to compile the job and rerun it.

It was working fine.

I think this is due to no. of process running at the backend or if the server is busy with the existing processes.
I am not sure about what i think, since
I am also eager to know why this error is occured.

you can have a try for rerun the job.

vivekgadwal · Post by **vivekgadwal** » Wed Jun 17, 2009 8:54 am

pxraja wrote: whenever I was facing this problem i used to compile the job and rerun it.
It was working fine.

Usually, the jobs run as part of, say, a daily schedule and it is always a pain-in-the-neck task to see when it aborts, reset/compile it and re-run it.

pxraja wrote: I think this is due to no. of process running at the backend or if the server is busy with the existing processes.
I am not sure about what i think, since
I am also eager to know why this error is occured.

you can have a try for rerun the job.

As Craig noted, there might be many reasons and most often than not, it will be documented as soon as the job is re-set. Occasionally, there might be just the "Abnormal termination..." error without any log posted and this is what I encountered in my previous shop. In the end, we contacted IBM and after much deliberation on their side, the uvconfig file was edited and the T30FILE size as well as RLTABSZ and GLTABSZ were increased as per IBM's recommendation.
BEWARE: Modifying these settings could extremely dangerous especially if we are unsure of what we are doing.