Db Job Taking Long Runtime After Purge

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
ds2000
Premium Member
Premium Member
Posts: 109
Joined: Sun Apr 22, 2007 7:25 pm
Location: ny

Db Job Taking Long Runtime After Purge

Post by ds2000 »

Job is taking very long time while doing a select from db2 tables/views. Its a simple job selects from db2 api stage and loads to flat file. There are two tables and two views used in this job. This job was taking only few minutes before and now its taking hours to complete.

Only change on db is that a large volume of data is purged from these tables and after that runtime is increased.

Following actions have been taken already on db but no impact on runtime:
- runstats
- reorg
- one view was re-built
chowdhury99
Participant
Posts: 43
Joined: Thu May 29, 2008 8:41 pm

Re: Db Job Taking Long Runtime After Purge

Post by chowdhury99 »

If the table is indexed, you may use hint to specify the index. Thanks.
ds2000 wrote:Job is taking very long time while doing a select from db2 tables/views. Its a simple job selects from db2 api stage and loads to flat file. There are two tables and two views used in this job. This job was taking only few minutes before and now its taking hours to complete.

Only change on db is that a large volume of data is purged from these tables and after that runtime is increased.

Following actions have been taken already on db but no impact on runtime:
- runstats
- reorg
- one view was re-built
chowdhury99
Participant
Posts: 43
Joined: Thu May 29, 2008 8:41 pm

Re: Db Job Taking Long Runtime After Purge

Post by chowdhury99 »

If the table is indexed, you may use hint to specify the index. Thanks.
ds2000 wrote:Job is taking very long time while doing a select from db2 tables/views. Its a simple job selects from db2 api stage and loads to flat file. There are two tables and two views used in this job. This job was taking only few minutes before and now its taking hours to complete.

Only change on db is that a large volume of data is purged from these tables and after that runtime is increased.

Following actions have been taken already on db but no impact on runtime:
- runstats
- reorg
- one view was re-built
Post Reply