I am working on db2 v9.1 on AIx 5.3.
We have scheduled the RUNSTATS script to be executed on every sunday which generates huge number of logs and thus consumes much of the disk space. My question is:
1. How are these logs generated during RUNSTATS execution helpful?
2. If not usefull at all, how can we force RUNSTATS utility not to create them?
2. I've never noticed runstats to generate a lot of logs AND I've never used the "sampled detailed indexes" option. Try runstats without that option and see if that makes a difference. Are your tables that big that you really need sampling?