MVSFORUMS.com

[abc2000]

DB2 RUNSTATS time too long, How to reduce the time?

We are DB2 for Z/OS V8.10,
I have a huge partition tablespace(130GB), I need 500 mins to RUNSTATS on the entire tablespace,
My statement is:
RUNSTATS TABLESPACE DATABS.TPSAPST
TABLE(ALL) INDEX(ALL) SHRLEVEL CHANGE

My Problem is RUNSTATS time too long, How to reduce the time?

[CZerfas]

Using TABLE(ALL) means, that you calculate statistics for all columns (!) of all tables. Do you really need that?

If the tablespaces is really huge as in your example, using only a sample would probably produce results that are valid enough for the optimizer to give good access paths.

Just my two cents
Christian

[videlord]

130GB is one partition all the whole tablespace?
If there are several partitions in 130GB, try RUNSTATS parallelly by partitions