Can I do runstat on more than 1 table within a database at the same table, any concurrent problem?

There might be some concurrency issues when DB2 goes to update the stats in the catalog, but I would think it would just result in a short lock wait at worst, and not any kind of deadlock.

Marcus_A,
Thx.

Do you mean there is concurrent issue on SYSSTAT table?

I suppose the question is:
Can I do runstat on more than 1 table within a database at the same TIME, any concurrent problem ?

No problem in the system catalog tables.

But you might consider: with more than one table in a tablespace - this is not a problem of doing but who gets to read the pages first ... Still should not be a problem either, only for very fragmented data.

It does not make sense to run runstats twice and in parallel on the same table ...

Runstats updates many more tables than the SYSSTAT table. My guess is that if any concurrency issue exists against the catalog tables, it would only be a very short lock wait, which you probably would not even notice.