Re: System Value QDBFSTCCOL

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Get the latest DB group PTF, for sure. Even then stats collection has some 
problems. I hate to say it, but you could be better off setting it to *NONE 
until things get sorted out. Although these jobs run at the lowest run 
priorities (97, 98, 99), once they fill up a queue (I/O or CPU) they still 
hold up other work.

Or set to *USER and look at the Stats item in OpsNav.

If you have indexes over a column, stats are generally not going to be 
collected over that column. And stats are single-column for the time being. 
So if you have enough indexes, you don't need to turn on stats as much.

Since these are a critical part of the new query engine, IBM is working 
diligently, I believe, to make this work. Meanwhile, there's a redpaper or 
redbook on the new engine, as well as an info apar for latest status. Look 
at <www.iseries.ibm.com/db2> and look in the Performance section - I think.

HTH
Vern

At 03:06 PM 1/26/2004 -0700, you wrote:
> We just upgraded one of our develop systems.  We started see the job
> QDBFSTCCOL taking high percent of system  resources.
>
> We didn't see this new system value in the "Memo to users".
>
> This job is starting and collecting stats for SQL runs.
>
> Has anyone been working with this system value???
>
> Values are System, User, All or none.   The default is *all.
>
> I have found PTF's that are suppose to help with the number of threads and
> memory management for this job, that should help.