DW jobs running long ....
![]()
I'm seeing rather lengthy run of the Star DW job. We have JTS which started with 2 applications (CCM/QM) but several new CCM have been added over the last month.
Run time has gone from < 1h to almost 7h. I'm looking at db2 performance (db2 top) and I'm seeing poor access plans on some queries (which unfortunately is querying what appears to be one of the largest (cardinality-wise) tables in the database.
Any suggestions ? |
2 answers
![]()
Almost 1h increase in last 5 runs...
Status Data Collection Job Start Time End Time Time Taken Failed Star Nov 20, 2011 3:22 AM Nov 20, 2011 10:28 AM 7 hours, 5 minutes Succeeded Star Nov 19, 2011 3:36 AM Nov 19, 2011 10:31 AM 6 hours, 55 minutes Succeeded Star Nov 18, 2011 3:52 AM Nov 18, 2011 10:30 AM 6 hours, 37 minutes Succeeded Star Nov 17, 2011 4:13 AM Nov 17, 2011 10:37 AM 6 hours, 23 minutes Succeeded Star Nov 16, 2011 4:27 AM Nov 16, 2011 10:38 AM 6 hours, 10 minutes Who knows anything about this ? What would I assign as Filed Against on a Work Item to get this some attention ? I'm seeing rather lengthy run of the Star DW job. We have JTS which started with 2 applications (CCM/QM) but several new CCM have been added over the last month. |
![]()
If you are not using RRDI, you could disable the STAR job.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.