DB2 Performance
Posted: Thu Nov 07, 2013 7:32 am
I have a job with DB2 connector writing the output to a sequential file.
First when I run the job it took almost 7 hours to complete. I have fine tuned the SQL and then re-run the job and it completed in less than 5 minutes. When the same job is run after two days, it is taking almost an hour to complete.
Can anyone please explain is there any cache where the data is stored so the run time is less when the job is triggered immediately?
First when I run the job it took almost 7 hours to complete. I have fine tuned the SQL and then re-run the job and it completed in less than 5 minutes. When the same job is run after two days, it is taking almost an hour to complete.
Can anyone please explain is there any cache where the data is stored so the run time is less when the job is triggered immediately?