Archives of the TeradataForum
Message Posted: Mon, 15 Oct 2001 @ 16:00:27 GMT
Teradata Manager takes advantage of the PM/API. There is a manual that describes the information in much more detail (PM/API Reference). If you haven't looked here yet, it should help.
Cornelius already pointed out that the DUC charts from within Teradata Manager can give you better insight into real-time AMP resource consumption on an aggregate basis. This is very helpful in initially identifying a skewing problem. But it can't identify which session/query is the root cause of the problem.
DBC.ACCTG is the place to get to the root of the problem. However, you need to take advantage of Teradata's Account String Expansion (ASE). Set at the User ID level, once configured, ASE can collect information at varying levels of detail. For example, in default mode DBC.ACCTG accumulates usage per VPORC at the User ID level forever, or until you clear out the table. ASE allows you collect the same data by session, by request, by hour, etc. I think this is what you are looking for. Keep in mind that ASE has the potential to greatly increase the size of the DBC.ACCTG table. But, in my opinion, the detailed info it provides is well worth the extract space.
Thomas F. Stanek
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|