DSXchange

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

What is your Job design? It is not a best practice to use "Kill" command

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]

Try to use Cleanup Resource option from the director and try to logout that process or release any lock on that process.

Ask your DBA to monitor what is happening within Oracle when you run the job. See if the connections are being made and what resources the queries and inserts / updates are consuming. Check there are no locks blocking the associated sql.

Thanks for the suggestions !

I tried to logout from director->clean up resources but couldn't abort the job.
However there could be problem with Database lock as source, lookup
were pointing to production.I will contact our DBA if the problem happens again.

Thanks ,
Ankita

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.

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

Ankita


while you wait for the job to finish did u try querying your final table to see if it has the data that you were expecting?

does your job hang even when you run it without passing any data through it??

what kind of a lookup is it that you do into the lookup table??

cheers
VM

Maybe they have fixed the issue in the past 2 years !!??