Long running job
Moderators: chulett, rschirm, roy
Long running job
Hi ,
I am facing a strange problem while running a job; the job is showing as 'Running' in Director window.But while monitoring I find it as ready even after several minutes, also not able to abort the job from Director.
I finally aborted by using kill command from unix, but facing the same issue again.What could be the possible reason ? How should I solve it ?
Please suggest !
Thanks,
Ankita
I am facing a strange problem while running a job; the job is showing as 'Running' in Director window.But while monitoring I find it as ready even after several minutes, also not able to abort the job from Director.
I finally aborted by using kill command from unix, but facing the same issue again.What could be the possible reason ? How should I solve it ?
Please suggest !
Thanks,
Ankita
-
- Charter Member
- Posts: 822
- Joined: Sat Sep 17, 2005 5:25 pm
- Location: USA
Yes, I agree with you, but I am doing some performance testing with large volume of data and running the jobs manually.The job reads from a Oracle table, performs lookup with Oracle and loads data into another Oracle table, dataset .
When I check in unix , it's showing that a phantom process is running ,
Say phantom DSD.RUN ecf2000a1_NC 0/0/1/0/0 while job name is
ecf2000a1_NC.
I don't have any other way known to abort a job, if it doesn't respond to Director Stop request !
Please let me know if anyone has any suggestion !
Thanks!
Ankita[/img]
When I check in unix , it's showing that a phantom process is running ,
Say phantom DSD.RUN ecf2000a1_NC 0/0/1/0/0 while job name is
ecf2000a1_NC.
I don't have any other way known to abort a job, if it doesn't respond to Director Stop request !
Please let me know if anyone has any suggestion !
Thanks!
Ankita[/img]
Cleanup Resource
Try to use Cleanup Resource option from the director and try to logout that process or release any lock on that process.
Gaurav.
Re: Long running job
In the defective job, maybe some parameters are not set to the right value(such as credentials to database if used or some other parameters), or
there is not-suit place in the job-design-logic.
Double-Checking the job maybe helpful,FYI.
there is not-suit place in the job-design-logic.
Double-Checking the job maybe helpful,FYI.
ankita wrote:Hi ,
I am facing a strange problem while running a job; the job is showing as 'Running' in Director window.But while monitoring I find it as ready even after several minutes, also not able to abort the job from Director.
I finally aborted by using kill command from unix, but facing the same issue again.What could be the possible reason ? How should I solve it ?
Please suggest !
Thanks,
Ankita
Let's Progress Together....
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom