Hi ALL,
Can anybody/everybody post the TIPS to debug printed detail Job log ?
I know everybody got there ways to catch the bug.
Thanks
Debug a Job log
Moderators: chulett, rschirm, roy
Debug a Job log
Every Thing Is Possible!!
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Which particular bug did you have in mind?
Your question currently is akin to "can anybody post a list of everything that can go wrong with a car?" Or a body - doctors spend six years earning a medical degree, of which a large proportion is developing diagnostic skills. For veterinary surgeons it's an even larger proportion.
Your question currently is akin to "can anybody post a list of everything that can go wrong with a car?" Or a body - doctors spend six years earning a medical degree, of which a large proportion is developing diagnostic skills. For veterinary surgeons it's an even larger proportion.
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.
This can be catergozierd as one of the most broad quetions..
most of the times the job failure reasons are diffrent and you can not use the same method to debug the job using the log.
Most of the times you can check where exactly the error is and what description that error is refering to
By looking that you can get at least you get the what could possibly have gone wrong. Whether it is data related issue or dupliates or enviormental or something like that !
Then depending on the type of error you can decide what kind of debugging you can do in your job..!
this is not sufficient thing to explain in such small scale.
the whole document can be written on this !
however hope this helps in some manner !
-----------------------
MK
---------------------------
most of the times the job failure reasons are diffrent and you can not use the same method to debug the job using the log.
Most of the times you can check where exactly the error is and what description that error is refering to
By looking that you can get at least you get the what could possibly have gone wrong. Whether it is data related issue or dupliates or enviormental or something like that !
Then depending on the type of error you can decide what kind of debugging you can do in your job..!
this is not sufficient thing to explain in such small scale.
the whole document can be written on this !
however hope this helps in some manner !
-----------------------
MK
---------------------------