Re: Force Statistics Collection DB2/400?

If you are talking about something like RUNSTATS on other Databases and DB2's... not really.

The statistics on DB2 for i are live, all the time. The OS and DB2 engine control statistics collection on IBM i. Statistics are usually collected on a when used basis. You can see this it the way that the SQE handles the first few requests against an unindexed table, building temporary (but system-wide) indexes once the optimizer decides that this table might be used more than once or twice.

That being said, you can have some influence over statistics collection at the table level using Client Access for i and through the use of indexes (particularly EVI's).

On 04/19/2010 08:35 AM, Ryan Hunt wrote:

We are working on a new JDE install and the process involves a lot of
copying our main business data libraries from a prod LPAR to a test LPAR,
running conversion scripts, and engaging in CRP testing. One thing I've
noticed is that the QDBFSTCCOL job generates a lot of activity once users
get onto the system and try to use it. I think this probably makes sense,
maybe the stats get abondoned during a RSTLIB on a library from a foreign
system...or maybe it's the conversion scripts. Either way, the system
behaves like there are next to no stats once the queries start coming in.

Anyway, I'm curious if there is a way to force statistics collections on
large business data libraries after the RSTLIB, data conversion activies,
etc.

Thanks. RH