How to Restart Datastage sequence when a job aborts?
Moderators: chulett, rschirm, roy
How to Restart Datastage sequence when a job aborts?
Hi,
I want to know how a sequence can be restarted if a job in the sequence aborts. And if the restart is done, what is the process/sequence in which datastage does it?
I searched the forum regarding this, but not sure about the procedure to do it. Can anyone let me know the way to do it without using UNIX scripts.
Regards,
Divya
I want to know how a sequence can be restarted if a job in the sequence aborts. And if the restart is done, what is the process/sequence in which datastage does it?
I searched the forum regarding this, but not sure about the procedure to do it. Can anyone let me know the way to do it without using UNIX scripts.
Regards,
Divya
-
- Premium Member
- Posts: 730
- Joined: Tue Nov 04, 2008 10:14 am
- Location: Bangalore
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
No such thing. You could code something but there's no automagical option for this. The aborted child job can be easily reset as noted and you can build a loop of some kind for the sequence itself but how will the actual problem fix itself? Sounds to me like all you're going to get is a constant crash-restart-crash-restart endless loop.dxk9 wrote:I want to restart it automatically.
![Confused :?](./images/smilies/icon_confused.gif)
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
I wouldn't write off the retry on abort - sometimes a job aborts and then works the next time due to resource conflicts. Sequence jobs have some restart from checkpoint capabilities built in if you enable it in the sequence job properties so if a job called from that sequence aborts the sequence will stop. If you run that sequence again it will start from the job that failed and skip the jobs that worked. If you set you job activity stages to reset and run instead of just run it should reset and run aborted jobs okay.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Mmmmaybe. Really depends on why it aborted.vmcburney wrote:If you set you job activity stages to reset and run instead of just run it should reset and run aborted jobs okay.
I wasn't suggesting this be written off, just written intelligently. Have some kind of an out, a reasonableness test for 'stuckage' rather than simply spinning in an endless Big Bang. That way leads to increasing entropy, black holes and perhaps even the heat death of the universe.
![Wink :wink:](./images/smilies/icon_wink.gif)
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Yes. The aborts in jobs are mostly cause of the resources, so it runs fine the next time.
So I want to know the entire procedure (step-by-step) to
a. Reset the job which gets aborted.
b. Restart the sequence which got aborted cause of the job abort.
I want the above two things to be done automatically without manual intervention.
Your detailed explaination are highly appreciated.
Thanks in advance.
Regards,
Divya
So I want to know the entire procedure (step-by-step) to
a. Reset the job which gets aborted.
b. Restart the sequence which got aborted cause of the job abort.
I want the above two things to be done automatically without manual intervention.
Your detailed explaination are highly appreciated.
Thanks in advance.
Regards,
Divya
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
(1) Automatic reset of job is achieved by setting its run mode in the job activity to "reset if required, then run".
(2) Automatic reset of job sequence can only be achieved by running that sequence from a parent sequence, which never aborts.
Note, however, that it is not necessary to reset a Restartable sequence, provided that it is configured not to abort if one of its activities fails.
(2) Automatic reset of job sequence can only be achieved by running that sequence from a parent sequence, which never aborts.
Note, however, that it is not necessary to reset a Restartable sequence, provided that it is configured not to abort if one of its activities fails.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can't.
Premium memberships are one of the ways in which the hosting and bandwidth costs of DSXchange are defrayed. By taking premium membership you not only benefit in a number of ways, but can also rejoice in the knowledge that you're helping to keep DSXchange alive. It's not expensive, at less than 30c (Rs 12) per day.
Premium memberships are one of the ways in which the hosting and bandwidth costs of DSXchange are defrayed. By taking premium membership you not only benefit in a number of ways, but can also rejoice in the knowledge that you're helping to keep DSXchange alive. It's not expensive, at less than 30c (Rs 12) per day.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.