Server job running Longtime
Moderators: chulett, rschirm, roy
Server job running Longtime
Hi experts,
I have Server job (7.5 AIX) Prod. extracting data from DB2 then loading into Sequential file. job started still showing runing more than 40 Mins.
expected volume of records 60,000 records only.
when ran the same Db2 Query on Control centre executed in 1 min.
ran the same job in Dev region with 200 records completed in 00:00:05 sec.
let me know what are the possible issues
thanks
Vemi
I have Server job (7.5 AIX) Prod. extracting data from DB2 then loading into Sequential file. job started still showing runing more than 40 Mins.
expected volume of records 60,000 records only.
when ran the same Db2 Query on Control centre executed in 1 min.
ran the same job in Dev region with 200 records completed in 00:00:05 sec.
let me know what are the possible issues
thanks
Vemi
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
200 records in 5 sec. Do the arithmetic. 60,000 records in X sec.
X = ?
What are your expectations, and why?
Is there an ORDER BY clause in the query? What else is the job doing while the clock is running? Do you include the time it takes for DB2CC to connect to the database in your timings? Do you count the time DB2CC takes to return the first row, or to return all rows?
X = ?
What are your expectations, and why?
Is there an ORDER BY clause in the query? What else is the job doing while the clock is running? Do you include the time it takes for DB2CC to connect to the database in your timings? Do you count the time DB2CC takes to return the first row, or to return all rows?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 81
- Joined: Tue Aug 15, 2006 8:31 am
- Location: Zürich
- Contact:
Re: Server job running Longtime
Friend,
Use DS job monitor to see the progress and the speed at which records are being fetched.
Replace your query projection clause (between SELECT and FROM) by count(1) and give it to your DBA.
Rest follows automatically.
Regards,
Abhijit
Use DS job monitor to see the progress and the speed at which records are being fetched.
Replace your query projection clause (between SELECT and FROM) by count(1) and give it to your DBA.
Rest follows automatically.
Regards,
Abhijit
Kind regards
Abhijit Gaikwad
Abhijit Gaikwad
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
How do you intend to do this without changing the job and what if the target is a load into some table which cannot be backed out easily ?Akumar1 wrote: I wud suggest you to run the same job in production with less number of records e.g. 100 records.
Check whether all DB2 jobs are having problem or only this specific one ?
Also check whether there is any join condition which is doing a full scan.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Please strive for a professional standard of written English on DSXchange. The correct spellng of the word is "would", not "wud".Akumar1 wrote:I wud suggest you to run the same job in production with less number of records...
More pedantically, perhaps, a better formulation is "fewer records" rather than "less number of records".
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.