Datastage job

I have a sequence of job in DataStage which is taking more than 4 hrs which is supposed to complete in less than 1 hr
so what could be the possibilities to take much longer time than expected?

Questions by hema123

Showing Answers 1 - 7 of 7 Answers


  • Aug 6th, 2014

The target table is getting skewed because of space issues in the target DB. Please check with the DBA with your log name mentioned in the logs. This could be one of the reasons.


  • Aug 8th, 2014

It may be because some other query is running on DB and your query is waiting for resources.

  Was this answer useful?  Yes


  • Aug 19th, 2014

may be the same DB user id (TD,Oracle…) getting used by some other queries/jobs @ the same time.

  Was this answer useful?  Yes


  • Aug 19th, 2014

There can be many reasons. no one can tell you exact reason. when you ask a datastage related question, we expect you to have basic debugging skill. checkout underlying datastage jobs to see which job is taking longer time then there are many ways to find the bottleneck

  Was this answer useful?  Yes


  • Aug 24th, 2014

- Check if any of the parallel job got hung in the sequencer which may also be the cause for long running.

- Check if any of the SQL used in the data stage waiting for the resources

  Was this answer useful?  Yes

Raveena Mittal

  • Sep 11th, 2014

When sometimes ,some DML statements are executed in the db and they are not committed,then also it may keep the job running for long hours

  Was this answer useful?  Yes


  • Oct 6th, 2014

Check if any stage is reading/processing data sequentially which could have been done in parallel.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions