Hi Techies
What are the basic step to solve a aborted job. like..
1) Need to check the job log and find out the reason and what if no specific error logged ?
What are the basic step to solve a aborted job
Moderators: chulett, rschirm, roy
What are the basic step to solve a aborted job
~Atul Singh
<a href=http://www.datagenx.net>DataGenX</a> | <a href=https://www.linkedin.com/in/atulsinghds>LinkedIn</a>
<a href=http://www.datagenx.net>DataGenX</a> | <a href=https://www.linkedin.com/in/atulsinghds>LinkedIn</a>
-
- Participant
- Posts: 27
- Joined: Mon Jul 09, 2012 6:51 am
- Location: Chennai
Re: What are the basic step to solve a aborted job
The Director will show you atleast one fatal error which initiated the abort. Try it
Regards,
Aravind V A
Aravind V A
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
1. Have a look at the fatal error that triggered the abort.
2. If the fatal error does not give a definite actionable error message/code, I'm sure there will be other warnings unless the job aborted due to a terminate command.
3. If the fatal error produces a database specific error, then use the code to resolve the issue with your query.
4. If it is a datastage specific issue, then need I say more?
5. If the datastage error doesn't give you an exact stage where the error occurred, then disable operator combination and re-run the job.
6. If you still cannot resolve the issue, copy paste the error message/warning and see if the topic has been discussed in this forum.
7. If no, post a new topic in the appropriate forum.
8. If no one else can help, then either Craig or Ray or Arnd will at least have a work-around.
9. If they post a solution and you cannot see the answer, then become a premium member and support the forum. If you can see the solution or can infer a solution from whatever little you can see, then mark the topic as Resolved/Workaround and continue transforming!
And that's the way the cookie crumbles! :D
2. If the fatal error does not give a definite actionable error message/code, I'm sure there will be other warnings unless the job aborted due to a terminate command.
3. If the fatal error produces a database specific error, then use the code to resolve the issue with your query.
4. If it is a datastage specific issue, then need I say more?
5. If the datastage error doesn't give you an exact stage where the error occurred, then disable operator combination and re-run the job.
6. If you still cannot resolve the issue, copy paste the error message/warning and see if the topic has been discussed in this forum.
7. If no, post a new topic in the appropriate forum.
8. If no one else can help, then either Craig or Ray or Arnd will at least have a work-around.
9. If they post a solution and you cannot see the answer, then become a premium member and support the forum. If you can see the solution or can infer a solution from whatever little you can see, then mark the topic as Resolved/Workaround and continue transforming!
And that's the way the cookie crumbles! :D
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Thanks Jerome for interesting answers.
~Atul Singh
<a href=http://www.datagenx.net>DataGenX</a> | <a href=https://www.linkedin.com/in/atulsinghds>LinkedIn</a>
<a href=http://www.datagenx.net>DataGenX</a> | <a href=https://www.linkedin.com/in/atulsinghds>LinkedIn</a>