Page 1 of 1
Db Job Taking Long Runtime After Purge
Posted: Tue Jun 01, 2010 11:13 am
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
Re: Db Job Taking Long Runtime After Purge
Posted: Tue Jun 01, 2010 11:43 am
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
Re: Db Job Taking Long Runtime After Purge
Posted: Tue Jun 01, 2010 11:48 am
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