Using the ResUsageSAWT table to Monitor AMP Worker Tasks - comment by carrie

Dinesh,
 
I am not clear from your comments if you seeing invalid values in the DBC.ResUsageSAWT table itself, or in some other table where you have offloaded the DBC table's data.  It would be a little more clear if you could provide the actual values you are seeing and in what table (DBC or otherwise).   If the problem is only showing up in the PDCR version of the table, but not in the DBC version, than the likely cause is some error in the code that moves the data or in the views being used to access it.  Unfortunately, I am not able to help with PDCR issues as PDCR is out of my area of experience.
 
I'm pretty confident that the AWT in-use count numbers being reported in the base DBC.ResUsageSAWT table are correct in 14.10.  I've looked at quite a bit of that logged output, and I'm not aware of any open incidents or DRs reporting incorrect data in the DBC.ResUsageSAWT table inuse fields. Although it's always possible there is a new problem that no one else has detected, and if that is the case, please open an incident with the support center.
 
There is something else you can check.  What you describe is common if you are looking at the DBC.ResUsageSPS table, which reports inuse counts for workloads.  The SPS table combines all AWT inuse counts on all the node's AMPs.   Because inuse counts include all AMPs on the node, you will typically get inuse counts in the hundreds for worknew and workone when viewing the SPS table.   But because ResUsageSAWT table reports at the AMP level, unless you have a very high number of AWTs per AMP,you will not see worknew + workone inuse counts exceeding 100.   So please check whether the table with the high inuse counts is possibly the ResUsageSPS table.
 
Thanks, -Carrie