Abnormal termination of stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 136
- Joined: Wed May 07, 2008 11:26 am
- Location: Sydney, Australia
- Contact:
Abnormal termination of stage
Hi Experts,
We have Scheduled hundreds of Jobs to run every night. Jobs ran fine till last week. But since few days randomly some jobs get aborted with the error : Abnormal termination of stage.
There is no other warning or error message. Both sequencers and the jobs fail. these Jobs if reset and run afain then they run fine. So only scheduled jobs are getting aborted with this error.
Please suggest me how to know the reason for these aborts.
regards,
vinay.
We have Scheduled hundreds of Jobs to run every night. Jobs ran fine till last week. But since few days randomly some jobs get aborted with the error : Abnormal termination of stage.
There is no other warning or error message. Both sequencers and the jobs fail. these Jobs if reset and run afain then they run fine. So only scheduled jobs are getting aborted with this error.
Please suggest me how to know the reason for these aborts.
regards,
vinay.
Vinay
-
- Participant
- Posts: 136
- Joined: Wed May 07, 2008 11:26 am
- Location: Sydney, Australia
- Contact:
hey But one perticular job that reads a table and writes into a hash file gave the following warning while it was reset.
error: TedEmp_LKP_TedEmpPSA..Ted_Emp_PSA_Hash.To_TGT_PSA: DSD.UVOpen Unable to open file '/dsdata/Tedweb/Lookup/Ted_Emp_PSA'.
This is the same job that gave the previous mentined error.
error: TedEmp_LKP_TedEmpPSA..Ted_Emp_PSA_Hash.To_TGT_PSA: DSD.UVOpen Unable to open file '/dsdata/Tedweb/Lookup/Ted_Emp_PSA'.
This is the same job that gave the previous mentined error.
Vinay
That's not what I asked. Find an Aborted job, Reset the job from the Director and tell us if any 'From previous run...' messages get logged.
Find out what changed last week, obviously something did. To me it sounds like a resource issue if you have the problem when "hundreds" of jobs are running but they work fine when rerun on an individual (or small number) basis.
Find out what changed last week, obviously something did. To me it sounds like a resource issue if you have the problem when "hundreds" of jobs are running but they work fine when rerun on an individual (or small number) basis.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers