I am running controller job and usually this jobs do not more than 15min to complete the job run. I started running the job one hour back and is still running. Input to this job is regular files, still running for long.
How to identify whethere job is hung or not?
Under what situations, a job would hang?
Please advise.
Thanks,
Latha
When do the jobs abort & How to identify?
Moderators: chulett, rschirm, roy
-
Krazykoolrohit
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
a job can hang due to numerous reasons. If datastage shows job as running, there is a very minimal chance that the job has aborted.
meanwhile to check if the job is running or not see the following:
1. If any any file is being written. check if the file size is still increasing
2. goto director and check the job status.
3. right click and see performance of the job.
4. Try and compile the job to check if the job is still locked or not
meanwhile to check if the job is running or not see the following:
1. If any any file is being written. check if the file size is still increasing
2. goto director and check the job status.
3. right click and see performance of the job.
4. Try and compile the job to check if the job is still locked or not
What is the desigh of the job.
Does it write to a target table (DB). Check for locks.
There are chances where the director or job monitor might show that the job is running, but it would have actually finished. Check for the required output.
Does it write to a target table (DB). Check for locks.
There are chances where the director or job monitor might show that the job is running, but it would have actually finished. Check for the required output.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'