If anyone is running DB2 in a guest operating system on VMWare, be sure
to have only the VMWare Tools update the system clock. Having other
services set the time like Windows Time Server or NTP can cause the
clock to be erratic.

db2dasstm processes seem to have all kinds of weird problems resulting
in excessive CPU. This is especially true when the Health Monitor is
active. I suspect some timeout detection code gets weird when the
clock moves backwards.

See more about VMWare clock at the VMWare Knowledge base.

Hope this helps!

Norm