Runstats in DB2 V8 z/os

Jorg Lueke

Runstats in DB2 V8 z/os
We've now had several processes where the default setting in V8 resulted in
worse access paths. One recent application example shows the CPU going
from just under two hours to well over 10 hours,. In all cases when we run
the correct statistics the performance goes back to V7 levels or improves.
However, I am beginning to suspect that the default stats gathered during a
load are doing more harm than good at this point. Since the needed runstats
rly heavily on coldist for multiple columns, in some case non-indexed columns,
and the load update doesn't impact these we may need to run corrective
runstats after the loads. What I'm currently looking at is the CA load and
these workloads are Bi/warehousing large parallel queries.

There's also issues with the physical data design in that the notorious part_nbr
is being used to partition and cluster rather than the date field that is used in
almost all the queries.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at