Hi all,
One of our job in the sequencer is keep on running status always ..that is the job didn't finished automatically...
which is running perfectly in some other environment,
the functionality of the job is it uses a dataset as source input and writes into a oracle table after doing a lookup.
where could be the problem?
Thanks in advance
Edi
Job not finished- continously running..
Moderators: chulett, rschirm, roy
Dsedi,
just so we understand the problem:
Is it correct that you have a sequencer which calls a job, this job never returns to the sequencer so the sequencer also never finishes. In the Director both the job and sequence have status of "running". If you start the job diretly from the Director it runs correctly and finishes, and if you start the sequence without calling the "hanging" job it also finishes correctly?
Does the log file of the job show any information? Does the job actually process all the rows of the dataset and do all the rows actually get written to the Oracle table?
This for a start - once the information requested above is posted we will surely find a cause for your issues.
just so we understand the problem:
Is it correct that you have a sequencer which calls a job, this job never returns to the sequencer so the sequencer also never finishes. In the Director both the job and sequence have status of "running". If you start the job diretly from the Director it runs correctly and finishes, and if you start the sequence without calling the "hanging" job it also finishes correctly?
Does the log file of the job show any information? Does the job actually process all the rows of the dataset and do all the rows actually get written to the Oracle table?
This for a start - once the information requested above is posted we will surely find a cause for your issues.
</a>