Teradata Database
Resource Usage Macros and Tables
Release 13.10
B035-1099-109A
October 2011
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, Active Enterprise Intelligence, Applications Within, Aprimo, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast,
Gridscale, Managing the Business of Marketing, MyCommerce, Raising Intelligence, Smarter. Faster. Wins., SQL-MapReduce, Teradata Decision
Experts, Teradata Labs Logo, Teradata Raising Intelligence Logo, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered
trademarks of Teradata Corporation or its affiliates in the United States and other countries.
Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.
GoldenGate is a trademark of Oracle.
Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.
Intel, Pentium, and XEON are registered trademarks of Intel Corporation.
IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation.
Linux is a registered trademark of Linus Torvalds.
LSI is a registered trademark of LSI Corporation.
Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United
States and other countries.
NetVault is a trademark or registered trademark of Quest Software, Inc. in the United States and/or other countries.
Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.
Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates.
QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation.
SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.
SPARC is a registered trademark of SPARC International, Inc.
Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States
and other countries.
Unicode is a registered trademark of Unicode, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN “AS-IS” BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION
MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL,
OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
The information contained in this document may contain references or cross-references to features, functions, products, or services that are
not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features,
functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions,
products, or services available in your country.
Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated
without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any
time without notice.
To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this
document. Please email: [email protected]
Any comments or materials (collectively referred to as “Feedback”) sent to Teradata Corporation will be deemed non-confidential. Teradata
Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform,
create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata
Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including
developing, manufacturing, or marketing products or services incorporating Feedback.
Copyright © 2000 – 2011 by Teradata Corporation. All Rights Reserved.
Preface
Purpose
This book describes, and provides procedures for, Teradata Database resource usage data and
macros.
Audience
This book is intended for system programmers, system administrators, and other database
specialists responsible for administering or managing Teradata Database.
Supported Software Releases and Operating
Systems
This book supports Teradata® Database 13.10.
Teradata Database 13.10 supports:
•
Microsoft Windows Server 2003 64-bit
•
SUSE Linux Enterprise Server 10
Teradata Database client applications can support other operating systems.
Prerequisites
You should be familiar with basic computer technology, Teradata Database, and the system
console environment.
It will be helpful to review or reference the following books:
•
Introduction to Teradata
•
Workload Management API: PM/API and Open API
•
Performance Management
Resource Usage Macros and Tables
3
Preface
Changes to This Book
Changes to This Book
Release
Description
Teradata Database 13.10
Removed the note and some text from the “Channel Traffic Columns”
section in the “ResUsageSpma Table” chapter.
October 2011
Teradata Database 13.10
August 2010
4
• Replaced instances of:
• "VSS" with "TVS."
• "collect period" and "collection period" with "gather period."
• "32-bit" with "64-bit" to some of the extent driver
I/O columns in "ResUsageSvpr Table."
• "Windows and Linux" with "ALL."
• "Teradata Manager" and "Teradata Dynamic Workload Manager"
or "Teradata DWM" with appropriate references to Teradata
Viewpoint.
• Removed the following:
• References to "MP-RAS," "xctl," "collection rate," and
"Performance Monitor (PMON)."
• The "Using the Active Row Filter Mode" topic from Chapter 2:
“Planning Your Resource Usage Data.”
• Appendix E: System Activity Reporter.
• Combined Node Logging Rate and Vproc Logging Rate into a single
Logging Rate in Chapter 3: “Resource Usage Procedures.”
• Updated the following information:
• The “About the "Invalid Platform" Column” section.
• The SET RESOURCE syntax in Chapter 3: “Resource Usage
Procedures.”
• The description of the CollectIntervals column.
• The descriptions of MailBoxDepth, MSGWORKTHREE and
MSGWORKELEVEN in Chapter 7: “ResUsageSawt Table.”.
• ResSpsView, ResSvprView, and ResGeneralInfoView views in
Chapter 14: “Resource Usage Views.”.
• The sample outputs for ResMemByGroup,
ResMemMgmtOneNode, and ResMemMgmtByNode in
Chapter 15: “Resource Usage Macros.”.
• SpareCount columns 00-05 and 07-08 in Chapter 11:
“ResUsageSps Table.”.
• The NumSets description in Chapter 11: “ResUsageSps Table.”.
• SpareCount columns 00-07 and SpareTmon columns 01-03 in
Chapter 13: “ResUsageSvpr Table.”.
• Changed the number of Performance Group (PGs) to 250.
• Added views: ResSawtView and ResSpsView in Chapter 14:
“Resource Usage Views.”.
Resource Usage Macros and Tables
Preface
Changes to This Book
Release
Description
Teradata Database 13.10
• Marked FilePRowNDel, FileSRowNDel, FilePRowNUpd,
FileSRowNUpd, FileAPtRowNUpd, FileAPtRowNDel,
HostWriteFails, and HostReadFails valid on all platforms.
• Marked ProcWorkType[i]Sum and ProcWorkType[i]Max invalid on
all platforms.
August 2010
(continued)
Teradata Database 13.0
April 2009
Resource Usage Macros and Tables
• The Vproc5 and VprocType5 fields are now valid on all platforms.
• ResUsageSpdsk table is available for use and reports detailed usage of
pdisks.
• Updated descriptions of summary mode to clarify what is being
reported.
• Updated descriptions for file system fields in the ResUsageSpma
table.
• Fields that were once marked as invalid on all platforms that are now
available for use on some or all platforms have been updated.
• QWaitTimeMax, QLengthMax, and ServiceTimeMax have been
changed to gather type "track" (not "count") which means they no
longer need to be divided by the log intervals to obtain the average.
• WorkTypeMax field in both the ResUsageSps and ResUsageAwt table
now have the gather type "track."
• Removed references to xschmon utility. It is no longer supported.
• Added new fields to ResUsageSps and ResUsageSpdsk.
• Added new flow control fields and Worktype fields to ResUsageSawt.
• Added new fields to ResUsageSvpr to support Teradata Dynamic
Workload Management software and DBQL.
• Added new PDE, FSYS, and Teradata Virtual Storage fields to
ResUsageSps.
• Added new MI fields to ResUsageSawt and ResUsageSvpr.
• Updated or added logical device fields such as input and output
traffic columns as well as response time columns to ResUsageSldv.
• Changed NodeType to CHAR(8) to accommodate new node types
with longer names.
• The field PGId has a new data type of SMALLINT. Also, summary
mode of the ResUsageSps table uses the triplet of the PGId, VprType,
and PPId fields.
• Removed instances of gather type "countshft" because the only
difference between countshft and count is how data collection is
implemented.
• Clarified CPU normalization in SPMA table
• Marked all the Extent I/O Driver columns in the SVPR table as
invalid.
5
Preface
Additional Information
Release
Description
Teradata Database 13.0
• The SpareTmon00 field in every table tracks the Capacity on
Demand (COD) value.
• ResUsageSps.WorkTypeInUse values now have a gather type "count."
The value must always be divided by the CollectIntervals value.
• ResUsageSps.WorkTypeMax values reports a maximum of sampled
values and not the actual maximum of all inuse AWTs.
• Updated the definition of the ResGeneralInfo view and added the
new ResSvprView view definition to Chapter 14.
April 2009
(continued)
Additional Information
URL
Description
www.info.teradata.com/
Use the Teradata Information Products Publishing Library site
to:
• View or download a manual:
1 Under Online Publications, select General Search.
2 Enter your search criteria and click Search.
• Download a documentation CD-ROM:
1 Under Online Publications, select General Search.
2 In the Title or Keyword field, enter CD-ROM, and click
Search.
• Order printed manuals:
Under Print & CD Publications, select How to Order.
www.teradata.com
The Teradata home page provides links to numerous sources of
information about Teradata. Links include:
• Executive reports, case studies of customer experiences with
Teradata, and thought leadership
• Technical information, solutions, and expert advice
• Press releases, mentions and media resources
6
www.teradata.com/t/TEN/
Teradata Customer Education designs, develops and delivers
education that builds skills and capabilities for our customers,
enabling them to maximize their Teradata investment.
www.teradataatyourservice.com
Use Teradata @ Your Service to access Orange Books, technical
alerts, and knowledge repositories, view and join forums, and
download software patches.
developer.teradata.com/
Teradata Developer Exchange provides articles on using
Teradata products, technical discussion forums, and code
downloads.
Resource Usage Macros and Tables
Preface
Additional Information
To maintain the quality of our products and services, we would like your comments on the
accuracy, clarity, organization, and value of this document. Please e-mail: [email protected].
Resource Usage Macros and Tables
7
Preface
Additional Information
8
Resource Usage Macros and Tables
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Supported Software Releases and Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Changes to This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Chapter 1: Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Benefits of Using Resource Usage Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Accessing Resource Usage Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Setting Up and Maintaining Resource Usage Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Overview of Resource Usage Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Gathering Resource Usage Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Data Gathering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Data Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Using Resource Usage Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Application Programming Interfaces and Resource Usage Data . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 2: Planning Your Resource Usage Data . . . . . . . . . . . . . . . 19
Enabling Resource Usage Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Tables Based on Needed Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Resource Usage Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Setting the Logging Rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Logging Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Determining the Logging Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Using Summary Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Using Active Row Filter Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Optimizing Resource Usage Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
The Cost of Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Resource Usage Macros and Tables
9
Table of Contents
Logging Cost Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Operational Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Chapter 3: Resource Usage Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Enabling RSS Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Using ctl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Using Database Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
General Macro Input Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Parameter Use for One-Node, Multiple-Node, All-Node, and Group Macros . . . . . . . . .31
Using One-Node Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Using ByGroup Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Saving and Analyzing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Executing Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
EXECUTE MACRO Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Using ENABLE and DISABLE LOGON Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Purging Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Chapter 4: Resource Usage Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Physical Table Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Relational Primary Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Inserting Rows into Resource Usage Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Occasional Event Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Types of Resource Usage Table Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
About the Invalid Platform Column. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
About the Type of Data Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Column Names Ending In Sum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Summary Mode in Resource Usage Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Chapter 5: ResUsageScpu Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Summary Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
10
Resource Usage Macros and Tables
Table of Contents
Chapter 6: ResUsageSpma Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Chapter 7: ResUsageSawt Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Summary Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 8: ResUsageShst Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Summary Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Chapter 9: ResUsageSldv Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Summary Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Chapter 10: ResUsageSpdsk Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Summary Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Chapter 11: ResUsageSps Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Chapter 12: ResUsageSvdsk Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Summary Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Resource Usage Macros and Tables
11
Table of Contents
Chapter 13: ResUsageSvpr Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
Summary Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Chapter 14: Resource Usage Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
ResGeneralInfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
ResCPUUsageByAMPView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
ResCPUUsageByPEView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
ResSawtView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
ResShstGroupView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
ResSldvGroupView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
ResSpsView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
ResSvprView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Chapter 15: Resource Usage Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Macro Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
ResAWT Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
ResAWT Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
ResAWTByAMP Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
ResAWTByNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
ResCPUByAMP Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
ResCPUByAMP Sample Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
ResCPUByAMPOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
ResAmpCpuByGroup Sample Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
Normalized Viewing of CPU Usage by AMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
ResCPUByPE Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
ResCPUByPE Sample Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
ResCPUByPEOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
ResPeCpuByGroup Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
Normalized Viewing of CPU Usage by PE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
ResCPUByNode Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
ResCPUByNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190
ResCPUOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190
ResCPUByGroup Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
ResHostByLink Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
12
Resource Usage Macros and Tables
Table of Contents
ResHostByLink Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
ResHostOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
ResHostByGroup Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
ResLdvByNode Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResLdvByNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResLdvOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResLdvByGroup Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
196
197
197
198
ResPdskByNode Macros: Pdisk Device Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResPdskByNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResPdskOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResPdskByGroup Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
200
201
201
ResMemMgmtByNode Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResMemMgmtByNode Sample Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResMemMgmtOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResMemByGroup Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
202
204
204
204
ResNetByNode Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResNetByNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResNetOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResNetByGroup Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
205
206
206
207
ResNode Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResNodeByNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResNodeByGroup Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
208
211
211
212
212
ResPs Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResPsByNode Macro Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResPsByGroup Macro Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResPsByNodeWDJoin Macro Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213
215
216
216
ResVdskByNode Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResVdskByNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResVdskOneNode Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ResVdskByGroup Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
218
219
219
219
Appendix A: How to Read Syntax Diagrams . . . . . . . . . . . . . . . . . . . 221
Syntax Diagram Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Resource Usage Macros and Tables
13
Table of Contents
Appendix B: ResUsageIpma Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
Appendix C: ResUsageIvpr Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
Summary Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248
Spare Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249
Appendix D: Partition Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
Table Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252
Partition Assignment Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
14
Resource Usage Macros and Tables
CHAPTER 1
Introduction
Resource usage, or ResUsage, is the collection and reporting of statistical information about
the operation of your operating system and Teradata Database.
Benefits of Using Resource Usage Data
Resource usage data is useful for the following purposes:
•
Measuring system performance
•
Measuring component performance
•
Assisting with on-site job scheduling
•
Identifying potential performance impacts
•
Planning installation, upgrade, and migration
•
Analyzing performance degradation and improvement
•
Identifying problems such as bottlenecks, parallel inefficiencies, down components, and
congestion
Accessing Resource Usage Data
Resource usage data is stored in system tables and views in the DBC database. Macros installed
with Teradata Database generate reports that display the data.
As with other database data, you can access resource usage data using SQL if you have the
proper privileges. You can also write your own queries or macros on resource usage data.
Setting Up and Maintaining Resource Usage
Data
You need to decide what resource usage data you want to collect and the level of detail you
want it to cover.
This manual documents the resource usage data and settings for a variety of installation
configurations and environments in Chapter 2: “Planning Your Resource Usage Data.” To
implement the settings you decide on, see Chapter 3: “Resource Usage Procedures.”
The only maintenance required is to purge old data regularly. See “Purging Data” on page 36.
Resource Usage Macros and Tables
15
Chapter 1: Introduction
Overview of Resource Usage Data
Related Topics
For additional information on performance analysis and system tuning, see the following
books:
•
Workload Management API: PM/API and Open API
•
Performance Management
Overview of Resource Usage Data
The following table lists topics covered by resource usage data.
Resource usage data covers …
Which includes …
BYNET traffic on a node
point-to-point messaging, broadcast messaging, and merge
activities.
client-to-server traffic
data for each communication link.
CPU utilization
overhead, user service, and time of session execution.
data tracking
positions of sessions in locking queues.
storage device traffic
the number of reads/writes and amount of data transferred
as seen from the storage driver.
pdisk device traffic
pdisk I/O, cylinder allocation, and migration statistics.
vdisk device traffic
all the cylinders allocated by an AMP (which can come from
any pdisks in the clique).
Priority Scheduler information
data by Performance Group (PG) from the Priority
Scheduler and the ability to report resource usage data by
Teradata Active System Management (ASM) workload
definitions (WDs).
AMP Worker Task (AWT)
information
AWT statistics.
memory management activity
memory allocation.
summary information
all data collected for a node or vproc.
Gathering Resource Usage Data
Resource usage data gathering is a two-phase process as follows:
16
•
Data gathering
•
Data reporting
Resource Usage Macros and Tables
Chapter 1: Introduction
Gathering Resource Usage Data
Data Gathering
During the data gathering phase the RSS gathers information from the operating system,
Parallel Database Extensions (PDE), and Teradata Database.
Data gathering periods may not be uniformly spaced and are based on the Teradata Dynamic
Workload Management, Collect and Logging rates. The number of gather periods that
occurred in any specific reporting period is indicated by the CollectInterval data field.
Data Reporting
The reporting periods occur at the end of one or more gather intervals. Each of the Teradata
Dynamic Workload Management, Collect and Logging rates are independent. For the
reporting period the respective reporting buffer is updated at the end of the respective
reporting period and made accessible via the rssretrieve interface. The resource usage data is
written to the database using the data from the Log buffer.
Data Collection Macros
and
Routines
Collect Buffer
Gather Buffer
Log Buffer
Summary Log
Teradata Dynamic
Workload
Management
Buffer
ResUsage Write Queue
ResUsage
Tables
ResUsage Reports
1099A001
Resource Usage Macros and Tables
17
Chapter 1: Introduction
Using Resource Usage Macros
Using Resource Usage Macros
Resource usage macros produce reports from data collected in the resource usage tables. You
can use the reports to analyze key operational statistics and evaluate the performance of your
system.
Like other macros, resource usage macros consist of one or more Teradata SQL statements
stored in Teradata Database and executed by a single EXECUTE statement.
In addition to the name of the macro, the EXECUTE statement for resource usage macros can
include parameters to specify the following:
•
A specific single-node
•
A group of nodes
•
Starting and ending dates and times
•
Starting and ending nodes of a range of nodes
Refer to Chapter 3: “Resource Usage Procedures” for more information on the resource usage
macros, and SQL Quick Reference for details about how to use the EXECUTE statement.
Application Programming Interfaces and
Resource Usage Data
The resource usage data are not used by just the resource usage macros. Resource usage data
can also be used by the System Performance Monitor and Production Control Application
Programming Interfaces (PMPC APIs). For more information on these APIs, see Workload
Management API: PM/API and Open API.
18
Resource Usage Macros and Tables
CHAPTER 2
Planning Your Resource Usage
Data
This chapter describes how to:
•
Enable resource usage tables
•
Set the logging rate
•
Use Summary Mode and Active Row Filter Mode
•
Optimize resource usage logging
Enabling Resource Usage Tables
The default resource usage settings provide a good starting point for system monitoring.The
default results in the ResUsageSpma (SPMA) table being logged every 10 minutes
(600 seconds).
The ResUsageSpma table provides a high level summary of how the system is operating and
contains summarized or key elements from most of the other tables. If you want to record
detailed statistics covered by any of the resource usage tables, then you should enable them for
logging, along with specifying the largest logging period that will meet your needs. You should
not log data that you do not have a planned need for since this does incur additional database
system overhead and uses up additional database space.
Naturally, the more tables you enable for logging and the shorter the logging period used, the
more overhead the system will use.
Tables Based on Needed Reports
If you plan on using the report macros provided in Chapter 15: “Resource Usage Macros,”
then you need to enable the associated table.
The following table lists more information.
Resource Usage Macros and Tables
19
Chapter 2: Planning Your Resource Usage Data
Enabling Resource Usage Tables
For...
See...
instructions on setting resource usage
tables
“Enabling RSS Logging” on page 27.
instructions on using macros
“General Macro Input Format” on page 29 and
“Executing Macros” on page 32.
descriptions and examples of the macros
Chapter 15: “Resource Usage Macros.”
Resource Usage Tables
The following table describes the tables and provides guidance about which ones to enable.
Table Name
Covers
When You Should Enable
ResUsageScpu
Statistics on the CPUs within the nodes.
When the performance analysis suggests that the
overall performance is limited or to check if a
program is spinning in an infinite loop on an
individual processor.
For example, saturation of a particular CPU on each
node or on a particular node while others are idle
could indicate a task always uses that CPU.
Also, you should enable when the system is first
brought online to verify the following:
• That all CPUs are functioning on all nodes
• There is a good load balance among the CPUs
ResUsageSpma
System-wide node information provides a
summary of overall system utilization
incorporating the essential information
from most of the other tables.
To provide an overall history of the system operation.
Use the columns in ResUsageSpma to view
BYNET utilization.
Note: The BYNET can transmit and receive
at the same time, resulting in 100%
transmitting and 100% receiving values
simultaneously.
Another method of determining BYNET
utilization and traffic is to use the blmstat
tool.
ResUsageIpma
System-wide node information, intended
primarily for Teradata engineers.
Generally, this table is not used at customer sites.
ResUsageSawt
Data specific to the AWTs.
When you want to monitor the utilization of the
AWT and determine if work is backing up because the
AWTs are all being used.
ResUsageShst
Statistics on the host channels and LANs
that communicate with Teradata Database.
To determine details about the traffic over the IBM
Host channels to determine if there is a bottleneck.
20
Resource Usage Macros and Tables
Chapter 2: Planning Your Resource Usage Data
Setting the Logging Rate
Table Name
Covers
When You Should Enable
ResUsageSldv
System-wide, logical device statistics
collected from the storage driver.
To observe the balance of disk usage. The storage
device statistics are often difficult to interpret with
disk arrays attached due to multi-path access to disks.
Note: Use the ResUsageSvdsk table first to observe
general system disk utilization unless specifically
debugging at a low level.
ResUsageSpdsk
Statistics collected from the pdisk device.
To obtain detailed usage information about pdisks.
ResUsageSps
Data by PG ID from the Priority Scheduler.
When you need to track utilization by the query WD
level.
ResUsageSvpr
Data specific to each virtual processor and
its file system.
To view details about the resources being used by each
vproc on the system. This table is useful for looking
for hot AMPS or PEs that may be CPU bound or
throttled on other resources.
ResUsageIvpr
System-wide virtual processor information,
intended primarily for Teradata engineers.
Generally, this table is not used at customer sites.
Setting the Logging Rate
The default for the Node Logging Rate is 600.
When you have decided what rate to set, see Chapter 3: “Resource Usage Procedures” for
details on how to set the logging rate.
Logging Rate
Logging rate controls the frequency (number of seconds) at which resource usage data is
logged to the resource usage tables.
Resource usage logging means the writing of resource data as rows to one or more of the
resource usage database tables. The tables are named DBC.ResUsagexxxx, where xxxx is the
name of the resource usage table (for example, Spma, Ipma, and so forth) as listed in
“Resource Usage Tables” on page 20.
The shorter the logging period, the more frequently data is logged, and the more disk space is
used.
When the system is so busy that the resource usage table logging gets backed up, RSS will
automatically double the logging period which effectively summarizes the data by providing
values for a time period twice that provided by the previous logging period.
If you see the resource usage logging rates change without user intervention, this means that
the database is busy. When no longer busy, the system resumes logging as before.
Note: Events in the event logs related to this doubling of the logging period do not represent
fatal errors but are informational to indicate that the automatic operations of the RSS are
attempting to maintain data logging.
Resource Usage Macros and Tables
21
Chapter 2: Planning Your Resource Usage Data
Using Summary Mode
Determining the Logging Value
The system imposes the following rule on the logging rate:
Intervals must evenly divide into 3600 (the number of seconds in an hour). The following
table shows the valid logging rate.
•
The white area of the table shows rates recommended only for short-term use for
debugging a specific issue.
•
The highlighted area of the table shows rates recommended for production processing.
1
2
3
4
5
6
8
9
10
12
15
16
18
20
24
25
30
36
40
45
48
50
60
72
75
80
90
100
120
144
150
180
200
225
240
300
360
400
450
600
720
900
1200
1800
3600
A practical log interval minimum during production processing is 60 seconds. Intermediate
log intervals, such as 120 seconds or 300 seconds can also be used. The default rate is 600
seconds.
If the system becomes very busy, it will automatically double the logging period. This
effectively summarizes the data by providing values for a time period twice that of the
previous logging period. The system automatically returns to logging back to the rate you set
when it is no longer busy.
Rates and enabled tables may be changed at any time and the changes take effect immediately.
Using Summary Mode
You can use Summary Mode to reduce the system overhead from logging tables that produce
multiple rows per logging period. Summary Mode helps reduce overhead by combining data
from multiple rows into one or more summary rows based on specific criteria for each table.
For example, if you want to log information provided in the ResUsageSvpr table but do not
need data for each individual vproc, then use summary mode to produce one row per vproc
type instead of one row per vproc.
The ResUsageSpma table, in comparison, provides node level summary of key fields from
most of the other ResUsage tables. When more details are required than the ResUsageSpma
table provides then the next level of information is provided by using summary mode logging
for the table of interest. This helps minimize the cost of the data logging.
You can select summary mode for each table individually. See the description for each table
for details on how summary mode affects that particular table.
22
Resource Usage Macros and Tables
Chapter 2: Planning Your Resource Usage Data
Using Active Row Filter Mode
For example, for the ResUsageSvpr table in summary mode, all the individual vproc rows of
the same vproc type are combined into a single row. Since the data values are added together,
you need to divide the summary row data value by the number of rows that made up the
summary mode row to get the average per vproc. For example, divide the AMP summary row
data value by the number of AMPs on that node to determine the average value per AMP. A
similar computation needs to be done to derive the average value per PE from the summary
row data value. (To determine the number of AMP, PEs, and all other vproc types on your
system, you can use the ResUsageSpma table or use the Vproc Manager utility.)
Fields that represent a maximum statistic are not summed together. Instead the maximum
value from the rows is used. For example, the ResUsageSvpr table MsgWorkQLenMax field in
the summary mode row for the AMPs will contain the maximum value from all the AMP rows
that would have been logged in non-summary mode. The fields that represent a minimum
statistic are summarized by storing the minimum value from all the constituent rows.
Summary mode has either no effect on the values of the Housekeeping Columns or it is
specifically detailed in the description of each affected field.
To enable Summary Mode, see “Enabling RSS Logging” on page 27.
For more information on Summary Mode, see “Summary Mode in Resource Usage Tables” on
page 42.
Using Active Row Filter Mode
Active Row Filter Mode reduces the overhead of logging for some of the resource usage table
by limiting the data rows that are logged to the database.
When active row filter is enabled, it may appear that rows are missing when looking at the
query results. This is because the index values of the inactive rows varies over time so that a
row with one index may be logged one period but not in another. To determine if rows are not
being logged to the database, you should look in the event logs for messages indicating that
rows have been lost.
Note: Active Row Filtering should not be disabled for the ResUsageSps table.
Optimizing Resource Usage Logging
The Cost of Logging
Logging resource usage data to database tables incurs costs:
•
Writing to the database adds to the system I/O load. On a heavily loaded system, this could
affect the production workload throughput.
•
The rows written to the database take up space. If this space is never reclaimed, it will
eventually grow to consume all available space in user DBC.
Resource Usage Macros and Tables
23
Chapter 2: Planning Your Resource Usage Data
Optimizing Resource Usage Logging
•
In an extremely loaded system, it is possible that the RSS can fall behind in writing data to
the database. Although it caches such data and will eventually catch up if given a chance,
the RSS will be forced to start discarding rows if the system load persists and its cache
capacity has been exceeded.
Logging Cost Contributors
Logging costs are difficult to quantify. They depend on a number of interrelated factors:
•
How busy is the system
•
Which resource usage tables are enabled
•
What resource usage logging rates are in effect
•
The system configuration (vproc, CPU, host driver, logical devices or device controllers)
Operational Methods
Use the following methods to optimize performance and reduce the cost of resource usage
logging on your system:
1
Use Summary Mode to reduce the number of rows inserted into the resource usage tables
if Summary Mode data provides sufficient information for your needs.
Note: If resource usage logging terminates due to a lack of table space:
a
Delete rows from the appropriate table or make more space for it in USER DBC.
b
Restart resource usage logging by entering the appropriate SET RESOURCE
command.
2
For tables with a large number of rows (for example, ResUsageSps), use Active Row Filter
Mode to limit the number of rows written to the database each logging period and to
minimize the amount of system resources used.
3
Avoid unnecessarily using or exhausting available disk space by doing the following:
•
Never enable logging on tables that you do not intend to use.
For example, logging only to the ResUsageSpma table provides a lot of useful
information with a minimal operational load on the system.
•
Use the largest rates that provide enough detail information for your purposes.
Generally, you should use a logging rate no smaller than 60. The default rate is 600.
These values can be adjusted any time, regardless of whether the database system is
busy. New values take effect as soon as the adjustment command is issued. (For
example, with ctl, when you issue the WRITE command.)
4
24
Purge old data from the ResUsage tables periodically.
Resource Usage Macros and Tables
Chapter 2: Planning Your Resource Usage Data
Optimizing Resource Usage Logging
Related Topics
For instructions on...
See...
enabling resource usage tables, setting the
logging rates, and summarizing or filtering
rows
“Enabling RSS Logging” on page 27.
purging old data from resource usage tables
“Purging Data” on page 36.
Resource Usage Macros and Tables
25
Chapter 2: Planning Your Resource Usage Data
Optimizing Resource Usage Logging
26
Resource Usage Macros and Tables
CHAPTER 3
Resource Usage Procedures
This chapter describes how to:
•
Enable RSS logging
•
Execute different types of macros
•
Enable logons
•
Purge old data
Enabling RSS Logging
By using one of the following interfaces you can enable tables, set the logging rate, and
optionally summarize or filter rows.
If you are running...
You can enable logging by running...
For instructions, see...
Windows or Linux
the ctl utility from the Teradata
Command Prompt.
“Using ctl” on page 27.
Windows or Linux
Database Window (DBW).
“Using Database Window” on page 28.
Before you set the ResUsage tables, determine which tables and controlling rates apply to the
resource usage macros you want to run. For more information, see the following topics:
•
“Enabling Resource Usage Tables” on page 19.
•
“Setting the Logging Rate” on page 21.
Using ctl
The Control GDO Editor utility (ctl) is used to set various Teradata Database configuration
settings. The RSS-related settings are presented on the RSS screen. For detailed information
on starting ctl and modifying the settings, see ctl in Utilities.
Resource Usage Macros and Tables
27
Chapter 3: Resource Usage Procedures
Enabling RSS Logging
Using Database Window
Use the database commands below to enable resource usage tables and set the logging rate
from DBW on Windows or Linux. For instructions on starting DBW, see "Database Window
(xdbw)" in Utilities.
To enable RSS logging from DBW
1
Open the Supvr window.
2
Set the Node Logging Rate using the database command below.
number
LOGGING
SET RESOURCE
NODE
LOG
1099C002
where number is the number of seconds.
Note: A rate of zero disables the logging function.
3
Specify the table you want to enable logging to using the database command below.
SET LOGTABLE
tablename
ON
ALL
OFF
FE0CA030
After the table is enabled for logging, you can log rows in Summary Mode. For more
information, see “Using Summary Mode” on page 22.
Note: To log rows in Summary Mode, you must enable the table specified in both the RSS
Table Logging Enable group and in the RSS Summary Mode Enable group.
4
(Optional) Enable Summary Mode on the table specified using the command below.
SET SUMLOGTABLE
tablename
ON
OFF
1095A010
Example
The following example shows you how to enable table logging and set the Logging rate using
the database commands in DBW. Suppose you want to enable the ResUsageShst table and set
the logging rate for 10 minutes (600 seconds). You would enter the following:
set logtable shst on
set resource node log 600
28
Resource Usage Macros and Tables
Chapter 3: Resource Usage Procedures
General Macro Input Format
Related Topics
For more information on...
See...
ctl
Utilities.
DBW
"Database Window (xdbw)" in Utilities.
General Macro Input Format
As shown in the table below, there are four kinds of macros:
•
Multiple-node
•
One-node
•
All-node
•
ByGroup
For any given line in the following table, the macros on that line report the same statistics for
either multiple nodes, one node, all nodes, or group nodes as indicated.
Resource Usage Macros and Tables
29
30
Description
Multinode Macro
AWTs in use by node
ResAWTByAMP
ResAWTByNode
CPU usage by AMP Vprocs
ResCPUByAMP
ResCPUByAMPOneNode
ResAmpCpuByGroup
CPU usage by
PE Vprocs
ResCPUByPE
ResCPUByPEOneNode
ResPeCpuByGroup
CPU usage by nodes
ResCPUByNode
ResCPUOneNode
ResCpuByGroup
Host statistics
One-Node Macro
All-Node Macro
ByGroup Macro
ResAWT
ResHostOneNode
ResHostByLink
ResHostByGroup
Ldv disk statistics
ResLdvByNode
ResLdvOneNode
ResLdvByGroup
Memory management
ResMemMgmtByNode
ResMemMgmtOneNode
ResMemByGroup
General network statistics
ResNetByNode
ResNetOneNode
ResNetByGroup
General node-level statistics
ResNodeByNode
ResOneNode
Priority Scheduler and
Teradata ASM Workload
statistics
ResPsByNode
pdisk level I/O statistics
ResPdskByNode
ResPdskOneNode
ResPdskByGroup
AMP level I/O statistics
ResVdskByNode
ResVdskOneNode
ResVdskByGroup
ResNode
ResNodeByGroup
ResPsByGroup
Resource Usage Macros and Tables
Chapter 3: Resource Usage Procedures
General Macro Input Format
Parameter Use for One-Node, Multiple-Node, All-Node, and Group Macros
The following table explains parameter use for one-node, multiple-node, all-node, and group
macros.
Macro Type
Number of Parameters
Node Parameters Used
Multiple node
Six (except ResHostByLink)
FromNode, ToNode
One node
Five
Node
All node
Four
None; this macro reports system-wide
statistics.
Group
Four
None; this macro reports statistics for
all nodes in the group.
For instructions on using these macros, see “Executing Macros” on page 32.
Using One-Node Macros
One-node macro versions are primarily used on single-node systems. Alternatively, you can
use the corresponding multiple-node macro to report on just one node by supplying equal
FromNode and ToNode parameters. One-node versions are recommended, however, because
they eliminate redundant report columns on a single-node system. Examples of redundant
columns are the NodeId column and columns that focus on cross-node load balancing.
OneNode macros have the same general input format as the other macros. The only
differences are that the single-node version of each macro has both of the following:
•
OneNode qualifier in the macro name.
•
A single node specification, instead of the FromNode and ToNode parameters to specify a
range of nodes. The default is ‘001-01’.
Using ByGroup Macros
ByGroup macro versions are used on systems with co-existing nodes. In Teradata Database,
co-existing nodes are nodes of different model types in the same configurations. Because of
the differences, the nodes may become bottlenecks in the throughput of the system as a whole.
Therefore, ByGroup macros were developed to provide the system user with a summary of the
performance data based on node groupings.
Note: The Database Administrator must identify the groupings of nodes when the system is
first configured.
ByGroup macros are similar to the other macros. The only difference is that they use the
GroupId column of the views to report system usage for a specific set of nodes grouped by a
GroupId. The input format of the ByGroup macros is the same as the other macros except
ByGroup appears as the qualifier in the macro name.
Resource Usage Macros and Tables
31
Chapter 3: Resource Usage Procedures
Executing Macros
Saving and Analyzing Data
If you expect an ongoing need to retain and analyze data from different Teradata Database
releases, ask your System Administrator to retain two sets of view and macro Data Definition
Language (DDL) files in separate places. Rename the views and macros so that you can use
either.
You could, for example, use ResNodeRxx, where xx represents the Teradata Database release
number, as the name of the resource usage macro and use it when you want to analyze the data
from that release.
Executing Macros
Function
Macro execution is illustrated in the following diagram. For details about each macro and its
resulting report, see Chapter 15: “Resource Usage Macros.”
EXECUTE MACRO Syntax
The execution of each resource usage macro has the following form. For information on
interpreting the syntax diagrams, see Appendix A: “How to Read Syntax Diagrams.”
MacroNameMultiNode
EXECUTE
,
(
FromDate
EXEC
MacroNameAllNode
,
(
FromDate
MacroNameOneNode
,
(
FromDate
FromTime
ToTime
B
,
C
,
D
ToDate
,
,
,
A
,
ToDate
,
(
A
ToDate
FromDate
MacroNameByGroup
,
ToDate
FromNode
);
ToNode
,
B
FromTime
ToTime
,
C
FromTime
,
,
D
FromTime
Node
ToTime
,
ToTime
GX02B001
where:
32
Resource Usage Macros and Tables
Chapter 3: Resource Usage Procedures
Executing Macros
Syntax element
Description
MacroNameMultiNode
Name of a multinode resource usage macro:
•
•
•
•
•
•
MacroNameAllNode
ResAwtByNode
ResCPUByAMP
ResCPUByPE
ResCPUByNode
ResLdvByNode
ResMemMgmtByNode
•
•
•
•
•
ResNetByNode
ResNodeByNode
ResPdskByNode
ResPsByNode
ResVdskByNode
Name of an all-node resource usage macro:
• ResNode
• ResHostByLink
The ResHostByLink and ResNode macros do not use the FromNode and
ToNode parameters.
MacroNameByGroup
Name of a ByGroup resource usage macro:
•
•
•
•
•
•
FromDate
ResAmpCpuByGroup
ResCPUByGroup
ResHostByGroup
ResLdvByGroup
ResMemByGroup
ResNetByGroup
•
•
•
•
•
ResNodeByGroup
ResPeCpuByGroup
ResPdskByGroup
ResPsByGroup
ResVdskByGroup
Start date to report resource usage data.
The date may be entered either as a character string (for example,
character format for May 31, 2007 would appear as '2007-05-31') or as a
numeric value (for the same date in numeric format, 1070531). The
character string is the recommended format. The default is the current
system date.
See "String Date Validations" in SQL Data Manipulation Language for
more detailed information on using numeric dates with macros.
Note: The character string date format has been changed from yymmdd
to 'yyyy-mm-dd' to accommodate dates in the 21st century.
ToDate
End date to report resource usage data.
See the FromDate syntax element column for a further explanation of
date formats.
The character string is the recommended format.
FromTime
Start time to report resource usage data. The format is hhmmss. The
default is 000000.
ToTime
End time to report resource usage data. The format is hhmmss. The
default is 999999.
Resource Usage Macros and Tables
33
Chapter 3: Resource Usage Procedures
Executing Macros
Syntax element
Description
FromNode
Starting range of nodes to report resource usage data. The format is
'nnn-nn'. A hyphen must be included in the fourth character position.
The default is '000-00'.
Note: To identify the node ID numbers for your system, type
get config in the DBW Supervisor Window (Supvr).
ToNode
Ending range of nodes to report resource usage data. The format is 'nnnnn'. A hyphen must be included in the fourth character position. The
default is '999-99'.
Note: To identify the node ID numbers for your system, type
get config in the DBW Supvr window.
Node
Single-node ID to report resource usage data. The format is 'nnn-nn',
and hyphen must be included in the forth character position. For
example, 1-01 should be typed out as '001-01'. The default is '001-01'.
Example 1: Executing the ResCPUByAMP Macro
The following statement executes the ResCPUByAMP macro, producing a report for the
period beginning 8:00 a.m. on December 25, 2006 and ending 12:00 midnight, on December
31, 2006. It includes data for nodes 123-02 through 125-04.
EXECUTE ResCPUByAmp('2006-12-25','2006-12-31', 080000, 240000,
'123-02','125-04');
where:
Statement Element
Description
ResCPUByAMP
Name of the resource usage macro
'2006-12-25'
Starting date of December 25, 2006
'2006-12-31'
Ending date of December 31, 2006
080000
Starting time of 8:00 a.m.
240000
Ending time of 12:00 midnight
'123-02'
Starting node of a range of nodes
'125-04'
Ending node of a range of nodes
See SQL Data Types and Literals for information on using numeric values for dates.
34
Resource Usage Macros and Tables
Chapter 3: Resource Usage Procedures
Executing Macros
Example 2: Executing the ResCPUByAMPOneNode Macro
The following statement executes the OneNode version of the ResCPUByAMP macro shown
in Example 1. It uses the same starting and ending dates and times (using character string
format), except the report is for a single-node, node 123-02.
EXECUTE ResCpuByAmpOneNode ('2006-12-25','2006-12-31',080000,
240000,'123-02');
where:
Statement Element
Description
ResCPUByAMPOneNode
Name of the resource usage macro
'2006-12-25'
Starting date of December 25, 2006
'2006-12-31'
Ending date of December 31, 2006
080000
Starting time of 8:00 a.m.
240000
Ending time of 12:00 midnight
'123-02'
Node
See SQL Data Types and Literals for information on using numeric values for dates.
Example 3: Executing the ResAMPCpuByGroup Macro
The following statement executes the ByGroup version of the ResCPUByAmp macro shown in
Example 1. It uses the same starting and ending dates and times (using character string
format), except the report is for a node grouping.
EXECUTE ResAMPCpuByGroup ('2006-12-25','2006-12-31',080000,
240000);
where:
Statement Element
Description
ResCPUByAMPByGroup
Name of the resource usage macro
'2006-12-25'
Starting date of December 25, 2006
'2006-12-31'
Ending date of December 31, 2006
080000
Starting time of 8:00 a.m.
240000
Ending time of 12:00 midnight
See SQL Data Types and Literals for information on using numeric values for dates.
Resource Usage Macros and Tables
35
Chapter 3: Resource Usage Procedures
Using ENABLE and DISABLE LOGON Commands
Using ENABLE and DISABLE LOGON Commands
The DISABLE LOGONS command prevents new sessions from logging on. When logons are
disabled, resource usage data stops logging to the tables even if there are still active sessions
logged on. (DISABLE ALL LOGONS prevents all users, including user DBC, from logging on
and also stops logging to the tables.)
To enable logons from:
•
Database Window, run ENABLE LOGONS or ENABLE ALL LOGONS.
•
Teradata command prompt, use the Start With Logons field of the Screen Debug menu of
ctl. See "Control GDO Editor (ctl)" in Utilities.
For more information on enabling and disabling logons, see "Changing Logon States and
Restarting the System" in Database Administration.
Purging Data
The RSS does not automatically delete data from the resource usage tables. You need to purge
data you no longer need on a regular basis.
You can directly remove old resource usage data by submitting SQL statements. For example,
use the following SQL statement to remove data more than five days old from the
ResUsageSpma table:
DELETE FROM ResUsageSpma WHERE TheDate < CURRENT_DATE - 7;
For more information about the DELETE syntax, see "SQL Data Manipulation Language
Statement Syntax" in SQL Data Manipulation Language.
36
Resource Usage Macros and Tables
CHAPTER 4
Resource Usage Tables
This chapter describes:
•
How to name the physical table and insert rows into resource usage tables
•
Types of resource usage table columns and data
•
Summary Mode in resource usage tables
Physical Table Naming Conventions
Each physical table name follows this general naming convention:
ResUsage Information_type Table_name
where:
Element
Is one of the following...
Information_type
Code
Description
S
System-wide information
I
Internal Teradata Database information
Code
Description
pma
Node information
vpr
vproc information
cpu
CPU-specific information
ldv
Logical device statistics
pdsk
pdisk device statistics
vdsk
vdisk device statistics
awt
AWT statistics
sps
WD resolution statistics
hst
Channel and LAN host information
Table_name
Resource Usage Macros and Tables
37
Chapter 4: Resource Usage Tables
Relational Primary Index
Relational Primary Index
All resource usage tables have the same nonunique primary index:
•
The nonunique primary index consists of TheDate, TheTime, and NodeID columns.
•
The primary index is nonunique because of duplicate rows that will appear with the same
timestamp during daylight savings time. Rows that have duplicate timestamps can be
distinguished by the GmtTime column.
•
Because the primary index is nonunique, all resource usage tables are created as
MULTISET tables. This prevents the system from checking for duplicate rows.
For more information on MULTISET tables, see "CREATE TABLE (Table Kind Clause)" in
SQL Data Definition Language or "Duplicate Rows in Tables" in SQL Fundamentals.
Inserting Rows into Resource Usage Tables
For information on how rows will be inserted into these tables based on the current resource
usage control settings, see Chapter 2: “Planning Your Resource Usage Data.” For information
on the number of rows inserted in a resource usage table for each applicable log period, refer
to “Using Summary Mode” on page 22.
Occasional Event Data
Occasional event data is considered outside the scope of resource usage and is, therefore,
logged in the ERRORLOG and the DBCINFO tables rather than in the resource usage tables.
Types of Resource Usage Table Columns
This manual describes what each of the resource usage table columns report (that is, what
each DBC.ResUsageXxxx.ColumnName reports) in a table format.
Note: The actual table definitions are obtainable by executing the SHOW TABLE statement.
See SQL Data Definition Language for more information about SHOW TABLE.
All columns described in the following chapters and appendixes are type FLOAT unless
otherwise specified in the description of that column. All nonexistent values are stored as
NULL.
For each resource usage table column, this manual describes the:
38
•
Column Name
•
Type of Data
Resource Usage Macros and Tables
Chapter 4: Resource Usage Tables
Types of Resource Usage Table Columns
•
Description
•
Data Type
•
Invalid Platform
The columns are grouped into either housekeeping columns or statistics columns. Statistic
columns are further grouped by category and subcategory as shown below.
Column Name
Type of Data
Description
Data Type
Invalid Platform
HOUSEKEEPING OR STATISTICS COLUMNS
CATEGORYS
Subcategory
Each table has:
•
Housekeeping columns which contain statistics on timestamp, current logging
characteristics, gather elements and its general characteristics.
•
Statistics columns which can be further categorized into subcategories. Categories and
subcategories may vary from table to table.
The following table shows the types of statistics subdivided into their respective subcategories.
Category
Subcategories
Description
File System
• Cylinder Management
• Cylinder Management Overhead
Events
• Data Block Prefetches
• Data Segment Lock Requests
• Segments Acquired
• Segments Released
• Synchronized Full File Scans
• Write Ahead Logging (WAL)
Some of the file system columns can be viewed as a
subset of memory columns by expanding on the
operations performed on disk memory segments.
Operations counted are logical memory and
physical disk reads and writes (including aging) and
locking control activities. Other columns identify
the purpose of operations being performed on disk
segments such as cylinder migration or data
updates; or identify the requests being made by
database software on the file system. The WAL
columns identify the log-based file system recovery
scheme in which modifications to permanent data
are written to a log file, the WAL log.
General Concurrency
Control
Database Locks
Identification of concurrency control activities is
provided and subdivided into control done for user
level processing, system overhead processing, and
database locks. It does not include control specific
to disk, memory or net concurrency control, which
are included in the disk, memory or net columns.
Resource Usage Macros and Tables
39
Chapter 4: Resource Usage Tables
Types of Resource Usage Table Columns
Category
Subcategories
Description
Host Controller (SHST)
•
•
•
•
•
Channel Traffic
Channel Management
Controller Overhead
User Commands
User Command Arrival and
Departure
These columns identify traffic on the host-to-node
channels and LANs. Some also give overhead and
management information on the host channel and
LAN.
Memory
•
•
•
•
•
•
•
Memory Allocations
Memory Availability Management
Memory Pages Resident
Memory Resident
Paging
Swapping
Task Context Segment Usage
Memory related events, subdivided into memory
types, are collected for memory allocation and
deallocation, logical memory and physical disk
reads and writes (including paging and swapping),
access, deaccess and memory control. Memory
management columns are also provided to identify
events leading up to paging, swapping and aging
activities. Finally, a detailed snapshot of the memory
is provided by tracking the current states per
memory types.
Logical Device
•
•
•
•
•
Concurrent Operations
Input and Output Traffic
Outstanding Requests
Response Time
Seek Statistics
These columns identify individual logical device
activities for external storage components
connected through the buses.
•
•
•
•
•
•
•
•
•
Broadcast Net Traffic
Group Coordination
Merge Services
Net Controller Status and
Miscellaneous Management
Net Circuit Management
Network Transport
Per-Bynet Network Transport Data
Point-to-point Net Traffic
Work Mailbox Queue
Traffic over the BYNET is identified through the
number and direction of messages, subdivided into
the type of transmission, as well as physical
utilization of the BYNET. Logical messages and
direction are identified through subdivisions of the
message class. Controller overhead, channel
utilization, and Teradata net contention are
identified as well.
•
•
•
•
•
•
•
•
ChnSignal Status Tracking
CPU Utilization
Cylinder Read
Process Allocation
Process Block Counts
Process Pending Snapshot
Process Pending Wait Time
Scheduled CPU Switching
These columns provide a CPU-level snapshot of
work started, with current characteristics and states.
Expanded detail is provided for work started but
waiting on resources. This helps identify the ability
or inability of the system to effectively utilize
resources. Time allotments are tracked by
monitoring the time spent waiting for resources or
processing code. These columns also track the
number of times processing was switched to another
process for multitasking purposes or to perform
interrupt services.
Net
Process Scheduling
40
The storage device statistics are calculated only on
what can be derived from statistics collected by the
operating system, since the disk array controllers do
not provide us with any useful data for resource
usage.
Resource Usage Macros and Tables
Chapter 4: Resource Usage Tables
About the Invalid Platform Column
Category
Subcategories
Description
User Commands
• User command
• User command Arrival and
Departure
These columns describe the types of commands
given to Teradata Database by the user and the
progress of those commands.
Secondary Cache Misses
None.
These columns identify the secondary cache miss
rate.
Spare
None.
These columns are for future release or internal
manipulation by Teradata developers.
Teradata ASM
•
•
•
•
AMP Worker Task
In use and Max Array Data
Priority Scheduler
Worktype Descriptions
These columns collect and report statistics about the
AWTs and Priority Scheduler. The columns specific
to the ResUsageSawt table also report the number of
AWTs currently in use and the maximum number of
AWTs for the current vproc on the node.
Teradata Virtual Storage
(VS)
•
•
•
•
Allocation
I/O
Migration
Node Agent
These columns identify individual pdisk and vdisk
device activities.
Note: Teradata VS is available for purchase
separately from Teradata Database.
For information about these columns, see Teradata
Virtual Storage.
About the Invalid Platform Column
The tables in this book that describe the resource usage tables contain an Invalid Platform
column. If your platform appears in that column for a field, then resource usage data for that
particular field is either not collected by the system or is not valid and should not be used.
The following table explains the contents of the Invalid Platform column.
In the Invalid Platform column …
Means …
ALL
do not use on any platform. The column is either obsolete
or not valid on any of the platforms.
Linux
column is only valid on Windows. It is not valid on Linux.
Windows
column is only valid on Linux. It is not valid on Microsoft
Windows.
column is valid on all platforms.
When the Invalid Platform column is blank, the column being described is valid on all
platforms.
Resource Usage Macros and Tables
41
Chapter 4: Resource Usage Tables
About the Type of Data Column
About the Type of Data Column
There are four possible types of data reported in the Type of Data column:
•
Count - Count fields tallies the number of times an event occurred, such as the number of
disk reads or writes during a period of time.
•
Max - Max fields have a Max suffix in the field name. An example of a Max field in the
ResUsageSvdsk table is the ReadRespMax field. This field reports the maximum value for
the logging period.
•
Min - Min fields have a Min suffix in the field name. An example of a Min field in the
ResUsageSvpr table is the ReadResponseHotMin field. This field reports the minimum
value during each logging period.
•
Track - Track fields gauge the current value of a countable item such as a queue length
during a period of time. The track field reports the value at the end of the logging period.
Column Names Ending In Sum
Column values ending in Sum, which are the Count Type of Data, are useful for calculating
the average value for a gather period. Each sum column accumulates the values measured by
the column at the end of every gather period. Divide the resulting logged value by the value
CollectIntervals to get the average value. The CollectIntervals value is the number of gather
periods per reporting period.
Summary Mode in Resource Usage Tables
Summary mode combines data from the multiple data rows normally generated into one or
more rows. When multiple rows are condensed into a single row, the data is combined using
the rules in the following table.
42
Resource Usage Macros and Tables
Chapter 4: Resource Usage Tables
Summary Mode in Resource Usage Tables
For the following Type
of Data…
Summary fields are combined by…
Count
summing the values from all the contributing rows.
Count fields are also added together when there are multiple gather periods in the reporting
period. Depending upon the usage of the field, the value may or may not need to be adjusted by
the number of rows that were combined by summary mode or the number of data sampling
periods as indicated by the CollectIntervals column.
For example, the ResUsageSvpr.FlowCtlCnt field provides the total number of times that the
system entered flow control state from a non-flow control state.
• In normal mode, the values are reported per AMP and no division by CollectIntervals is
necessary since the total over the entire reporting period is desired.
• In summary mode, the value needs to be divided by the number of AMPs if the user wishes to
determine the average number per AMP rather than the total.
On the other hand, for the WorkTypeInuse00 field of the SAWT or SPS table, the value reported is
the sum of the current number of AWTs in use from each CollectInterval. In this case, the field
should always be divided by the number of CollectIntervals, which will provide the sampled
average number of AWTs in use over the reporting period.
Note: To obtain the average number of AWTs in use during the reporting period per AMP, divide
the summary mode reported value by the CollectIntervals value as well as the number of AMPs.
Max
taking the maximum value from all the contributing rows.
In summary mode, the reported value for a Max field such as
ResUsageSpdsk.ConcurrentWriteMax is the maximum value from all the rows that are combined
into a single summary row.
Min
taking the minimum value from all the contributing rows.
In summary mode, the reported value for a Min field such as
ResUsageSvpr.ReadResponseHotMin is the minimum value from all the rows that are combined
into a single summary row.
Track
summing the values from all the contributing rows.
In Summary mode, the Track values from each row to be combined are summed together. For
example, ResUsageSvpr.FlowControlled is a track field so that in summary mode, all the AMP
vproc rows are combined into a single row and the FlowControlled field will report the summed
value from each of the AMP vproc rows.
Note: The Track values are not combined across multiple gathering intervals (as represented by
the CollectIntervals column). For the ResUsageSvpr.FlowControlled field, this means that if there
were 10 gather periods (the CollectIntervals column equals 10) in the reporting period, then the
value reported will be the FlowControlled state at the end of the last gather period. This is the
same as the value at the end of the reporting period. If summary mode is enabled, the values from
each of the non-summary mode rows are added together to produce the summary mode row
value.
The following table describes Summary Mode for the resource usage tables. Summary Mode is
applicable to all tables except ResUsageSpma and ResUsageIpma. If the information for a row
of a table is in Summary Mode, the SummaryFlag value is set to ‘S’. If the row is being logged
normally, the SummaryFlag value is set to ‘N’.
Resource Usage Macros and Tables
43
Chapter 4: Resource Usage Tables
Summary Mode in Resource Usage Tables
The Table…
contains ResUsage data…
and the following information when Summary Mode is active…
ResUsageIpma
for available system-wide, node
information
Summary Mode not applicable to this table.
ResUsageSpma
for available system-wide, node
information
Summary Mode not applicable to this table.
ResUsageScpu
specific to the CPUs within the
nodes.
one row is written to the database for each node in the system,
summarizing the CPUs on that node, for each log interval.
For details, see Chapter 5: “ResUsageScpu Table.”
ResUsageSawt
specific to the AWTs.
one row is written to the database for each node in the system,
summarizing all AWTs per node, for each log interval.
For details, see Chapter 7: “ResUsageSawt Table.”
ResUsageShst
specific to the host channels and
LANs communicating with
Teradata Database.
one row is written to the database for each type of host
(network or channel-connected) on each node in the system,
summarizing the hosts of that type on that node, for each log
interval.
For details, see Chapter 8: “ResUsageShst Table.”
ResUsageSldv
specific to each logical storage
device.
two rows written to the database: one summarizing the system
logical devices and one summarizing the Teradata Database
logical devices.
For details, see Chapter 9: “ResUsageSldv Table.”
ResUsageSpdsk
specific to the pdisk device.
one row for each pdisk type per node inserted each logging
period.
For example, for large configurations, the ResUsageSpdsk table
may contain thousands of rows logged during each logging
period, enabling Summary Mode minimizes the amount of
system resources used.
For details, see Chapter 10: “ResUsageSpdsk Table.”
ResUsageSps
one row written to the database
for each triplet of PGid,
VprType, and PPid fields for
each log interval.
Summary Mode not applicable to this table.
For details, see Chapter 11:
“ResUsageSps Table.”
ResUsageSvdsk
specific to the vdisk device.
one row written to the database for each node in the system,
summarizing all AMP vdisk data in each node, for each log
interval.
For details, see Chapter 12: “ResUsageSvdsk Table.”
ResUsageSvpr
specific to each virtual processor
and its file system.
one row written to the database for each type of vproc on each
node in the system, summarizing the vprocs of that type on
that node, for each log interval.
For details, see Chapter 13: “ResUsageSvpr Table.”
44
Resource Usage Macros and Tables
CHAPTER 5
ResUsageScpu Table
This resource usage table contains resource usage information specific to the CPUs within the
nodes. Table ResUsageScpu includes resource usage data for available system-wide,
CPU information.
Note: This table is created as a MULTISET table. For more information see “Relational
Primary Index” on page 38.
The Invalid Platform column is a little counterintuitive. If your platform appears in that
column, then resource usage data for that particular column is either not collected or not valid
and should not be used. (For more information, see “About the Invalid Platform Column” on
page 41.)
The following table describes the ResUsageScpu table columns.
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system load,
entries may be logged late (typically, by no more
than one or two seconds), but this field will still
contain the time value when the entry should have
been logged. See the Secs and NominalSecs
columns.
NodeId
n/a
Identifies the Node. The Node ID is formatted as
CCC-MM, where CCC denotes the three-digit
cabinet number and MM denotes the two-digit
chassis number of the node. For example, a node in
chassis 9 of cabinet 3 has a node ID of ‘003-09’.
INTEGER
Note: Symmetric Multi-Processing (SMP) nodes
have a chassis and cabinet number of 1. For
example, the node ID of an SMP node is ‘001-01’.
Resource Usage Macros and Tables
45
Chapter 5: ResUsageScpu Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
MISCELLANEOUS HOUSEKEEPING COLUMNS
GmtTime
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that occur twice
a year.
FLOAT
NodeType
n/a
Type of node, representing the per node system
family type. For example, 5600C or 5555H.
CHAR(8)
CPUId
n/a
Identifies the CPU within this node. The values are
0 through NCPUs-1.
SMALLINT
In Summary Mode, the value is zero.
Secs
n/a
Actual number of seconds in the log period
represented by this row. Normally the same as
NominalSecs, but can be different in three cases:
SMALLINT
• The first interval after a log rate change
• A sample logged late because of load on the
system
• System clock adjustments affect reported Secs
Useful for normalizing the count statistics contained
in this row, for example, to a per-second
measurement.
CentiSecs
n/a
Number of centiseconds in the logging period. This
field is useful when performing data calculations
with small elapsed times where the difference
between centisecond-based data and whole seconds
results in a percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds in the
logging period.
SMALLINT
SummaryFlag
n/a
Identifies the summarization status of this row.
Possible values are ‘N’ if the row is a non-summary
row, and ‘S if the row is a summary row.
CHAR
Active
count
Controls whether or not the rows will be logged to
the ResUsage tables if Active Row Filter Mode is
enabled.
FLOAT
If Active is set to:
• a non-zero value, then the row contains
modified data columns.
• a zero value, then none of the data columns in
the row have been updated during the logging
period.
For example, if Active Row Filter Mode is enabled,
then the rows that have a zero Active field value will
not be logged to the ResUsage tables.
46
Resource Usage Macros and Tables
Chapter 5: ResUsageScpu Table
Column Name
Type of
Data
Description
Data Type
CollectIntervals
n/a
The number of gather periods per reporting period.
SMALLINT
Invalid
Platform
In the Collect Buffer and Log Buffer, the value is the
number of Gather operations that have been
performed during the period. This number can vary
from one period to the next.
STATISTICS COLUMNS
PROCESS SCHEDULING COLUMNS
CPU Utilization Columns
Count all CPU activities, including activities performed for virtual processors, subdivided into the following columns:
1 CPUIdle - Idle time
2 CPUIoWait - Idle and waiting for I/O completion
3 CPUUServ - User service
4 CPUUExec - User execution
These statistics are aggregates representing all CPUs on the node. CPU utilization by user code is further subdivided by the
vproc tables.
Note:
•
CPU idle time = CPUIdle + CPUIoWait
•
CPU busy time = CPUUServ + CPUUExec
Theoretically, the values of these four columns, for any given interval, account for total CPU time on the node. That is, they
should total to 100 * Secs * number of CPUs on the node, since each CPU is always in exactly one of these four states. In
practice, there is occasionally a very small plus or minus difference from this theoretical total.
CPUIdle
count
Time in centiseconds the CPU is idle and not
waiting for I/O.
FLOAT
CPUIoWait
count
Time in centiseconds CPU is waiting for I/O
completion.
FLOAT
Windows
Note: This represents another variety of Idle, since
the CPU is only recorded as being in this state if
there are no processes eligible for execution. This is
because if there were any such process, the CPU
would be immediately dispatched for that process.
CPUUServ
count
Time in centiseconds CPU is busy executing user
service code, that is, privileged work performing
system services on behalf of user execution
processes which do not have root access.
FLOAT
CPUUExec
count
Time in centiseconds CPU is busy executing user
execution code, that is, time spent in a user state on
behalf of a process.
FLOAT
Resource Usage Macros and Tables
47
Chapter 5: ResUsageScpu Table
Summary Mode
Type of
Data
Column Name
Description
Data Type
Invalid
Platform
Scheduled CPU Switching Columns
Identify the number of times the CPU was switched by the scheduler from doing one type of work to another type of work.
CPUProcSwitches
count
Number of times the scheduler switched the CPUs
currently active process to a new process.
FLOAT
ALL
CPUProcSameSwitches
count
Number of CPUProcSwitches where a process
replaced itself, that is, the new process was the same
as the old process.
FLOAT
ALL
Summary Mode
When Summary Mode is active for tables in this group, one row is written to the database for
each node, summarizing all CPUs per node, for each log interval.
You can determine if a row is in Summary Mode by checking the SummaryFlag column for
that row.
IF the SummaryFlag column value is…
THEN the data for that row is being logged…
‘S’
in Summary Mode.
‘N’
normally.
Spare Columns
The ResUsageScpu table has six spare columns (one of which is being used) as shown in the
table below.
Column Name
Type of Data
Description
SpareCount[00-01]
count
Spare counted statistic.
SpareTrack[00-01]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 field contains the Capacity on
Demand (COD) value. The value represents the
COD value in one tenths of a percent, so a
displayed value of 500 represents a COD value of
50.0%.
Note: This value is valid only on SUSE Linux
Enterprise Server 10 systems and is a single value
for the entire system.
48
Resource Usage Macros and Tables
Chapter 5: ResUsageScpu Table
Spare Columns
Column Name
Type of Data
Description
SpareTmon01
count
Spare tmonitored statistic.
The spare column fields expand to values 00 - 01, so that column names would be
SpareCount00 or SpareTrack01, and so on.
Resource Usage Macros and Tables
49
Chapter 5: ResUsageScpu Table
Spare Columns
50
Resource Usage Macros and Tables
CHAPTER 6
ResUsageSpma Table
The ResUsageSpma table includes resource usage data for available system-wide, node
information. The ResUsageSpma table is similar to the ResUsageIpma table. For information
on this table, see Appendix B: “ResUsageIpma Table.”
Note: Summary Mode is not applicable to this table.
This table is created as a MULTISET table. For more information see “Relational Primary
Index” on page 38.
The Invalid Platform column is somewhat counterintuitive. If your platform appears in that
column, then resource usage data for that particular column is either not collected or not valid
and should not be used.
The following table describes the ResUsageSpma table columns. However, always use the
views provided in Chapter 14: “Resource Usage Views” to access the data rather than accessing
the ResUsage table directly.
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system load,
entries may be logged late (typically, by no more
than one or two seconds), but this field will still
contain the time when the entry should have been
logged. See the Secs and NominalSecs columns.
NodeId
n/a
Identifies the Node. The Node ID is formatted as
CCC-MM, where CCC denotes the three-digit
cabinet number and MM denotes the two-digit
chassis number of the node. For example, a node
in chassis 9 of cabinet 3 has a node ID of ‘003-09’.
INTEGER
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an
SMP node is ‘001-01’.
Resource Usage Macros and Tables
51
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
MISCELLANEOUS HOUSEKEEPING COLUMNS
These columns provide a generalized picture of the vprocs running on this node, shown as Type n virtual processors where
n = 1 to 7. Under the current implementation, only Type 1 (AMP), Type 2 (PE), Type 3 (GTW), Type 4 (RSG), and Type 5
(VSS) vprocs exist; vproc types 6 through 7 are not currently used.
GmtTime
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that occur
twice a year.
FLOAT
NodeType
n/a
Type of node, representing the per node system
family type. For example, 5600C or 5555H.
CHAR(8)
NCPUs
n/a
Number of CPUs on this node.
SMALLINT
This field is useful for normalizing the CPU
utilization field values for the number of CPUs
on the node. This is especially important in
coexistence systems where the number of CPUs
can vary across system nodes.
Vproc1
n/a
Current count of type 1 (AMP) virtual
processors running on the node.
SMALLINT
VprocType1
n/a
Type of virtual processor for Vproc1. When the
vproc is present on the node, the value is AMP.
CHAR(4)
Vproc2
n/a
Current count of type 2 (PE) virtual processors
running under the node.
SMALLINT
VprocType2
n/a
Type of virtual processor for Vproc2. When the
vproc is present on the node, the value is PE.
CHAR(4)
Vproc3
n/a
Current count of type 3 (GTW) virtual
processors running under the node.
SMALLINT
VprocType3
n/a
Type of virtual processor for Vproc3. When the
vproc is present on the node, the value is GTW.
CHAR(4)
Vproc4
n/a
Current count of type 4 (RSG) virtual processors
running under the node.
SMALLINT
VprocType4
n/a
Type of virtual processor for Vproc4. When the
vproc is present on the node, the value is RSG.
CHAR(4)
Vproc5
n/a
Current count of type 5 (VSS) virtual processors
running under the node.
SMALLINT
VprocType5
n/a
Type of virtual processor for Vproc5. When the
vproc is present on the node, the value is VSS.
CHAR(4)
Vproc6
n/a
Current count of type 6 virtual processors
running under the node.
SMALLINT
This column reports zeros and " " (blanks).
VprocType6
52
n/a
Type of virtual processor for Vproc6.
CHAR(4)
ALL
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
Vproc7
n/a
Description
Data Type
Current count of type 7 virtual processors
running under the node.
SMALLINT
Invalid
Platform
This column reports zeros and " " (blanks).
VprocType7
n/a
Type of virtual processor for Vproc7.
CHAR(4)
MemSize
n/a
Amount of memory on this node in megabytes.
Useful for performing memory usage
calculations.
INTEGER
NodeNormFactor
n/a
A per node normalization factor that is used to
normalize the reported CPU values of the
ResUsageSpma table.
INTEGER
ALL
This value is scaled by a factor of 100. For
example, if the actual factor is 5.25, then the
value of the NodeNormFactor will be 525.
Note: This value is constant for the node and
scaled up by a factor of 100 to preserve the two
digit decimal resolution while using an integer
field.
Secs
n/a
Actual number of seconds in the log period
represented by this row. Normally the same as
NominalSecs, but can be different in three cases:
SMALLINT
• The first interval after a log rate change
• A sample logged late because of load on the
system
• System clock adjustments affect reported Secs
Useful for normalizing the count statistics
contained in this row, for example, to a persecond measurement.
CentiSecs
n/a
Actual number of centiseconds in the logging
period.
INTEGER
This field is useful when performing data
calculations with small elapsed times where the
difference between centisecond-based data and
whole seconds results in a percentage error.
NominalSecs
n/a
A specified or nominal number of seconds in the
logging period.
SMALLINT
CollectIntervals
n/a
The number of gather periods per reporting
period.
SMALLINT
In the Collect Buffer and Log Buffer, the value is
the number of Gather operations that have been
performed during the period. This number can
vary from one period to the next.
Resource Usage Macros and Tables
53
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
Active
NetSamples
Description
Data Type
n/a
Gets set to a non-zero value whenever one of the
other data columns in the row is set.
FLOAT
count
Sample count for sampled statistics for a Bynet.
FLOAT
Invalid
Platform
Note: NetSamples is used to normalize all net
time monitored statistics to a percent-of-time
basis. For example, dividing (NetTxIdle/
NetSamples) yields the transmitter-idle time
ratio for the net statistics.
STATISTICS COLUMNS
Teradata VS Columns
These columns identify pdisk I/O statistics that are reported by Teradata VS.
Note: Teradata VS is available for purchase separately from Teradata Database.
For details about these columns, see Teradata Virtual Storage.
Process Allocation Columns
These columns represent all currently allocated processes, subdivided into the possible process states of running, ready,
blocked or suspended.
ProcReadySum
count
Number of runnable or ready tasks able to
execute on CPUs when a CPU becomes available.
FLOAT
Note: A task is a thread.
Also, to calculate the average number of
runnable or ready tasks, divide this value by the
CollectIntervals value. The CollectIntervals value
is the number of gather periods per reporting
period. For more information, see the
CollectIntervals column.
ProcBlockedSum
count
The total number of threads blocked waiting for
I/O.
FLOAT
Windows
FLOAT
ALL
Note: To calculate the average number of
processes blocked, divide this value by the
CollectIntervals value. The CollectIntervals value
is the number of gather periods per reporting
period. For more information, see the
CollectIntervals column.
ProcSuspendedSum
count
Total number of process suspended from
execution, awaiting another process to resume
them (during a log interval).
Note: To calculate the average number of
processes suspended, divide this value by the
CollectIntervals value. The CollectIntervals value
is the number of gather periods per reporting
period. For more information, see the
CollectIntervals column.
54
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
ProcRunningSum
count
Description
Data Type
Invalid
Platform
Total number of processes running (executing)
on CPUs during each log interval.
FLOAT
ALL
Note: To calculate the average number of
processes running, divide this value by the
CollectIntervals value. The CollectIntervals value
is the number of gather periods per reporting
period. For more information, see the
CollectIntervals column.
ProcReadyMax
max
Maximum number of runnable or ready tasks
able to execute on CPUs when a CPU becomes
available.
FLOAT
Note: A task is a thread.
Process Pending Snapshot Columns
Identify how many processes are blocked for each possible reason. These columns total (minus ProcPendDBLock)
approximately ProcBlockedSum, since we can only be blocked on one blocking type at a time.
Note: In analyzing resource usage, a distinction should be made between the following two kinds of process blocks:
• Block involves a process that is logically idle, waiting to receive work on its primary mailbox, or for a timer to elapse. This
block does not affect throughput.
• Block involves a process that has work to do but is being prevented from proceeding by some circumstance like a segment
lock or flow control. This kind of block does affect throughput.
The first kind of block is represented by column ProcPendNetRead; the second kind is represented by the remaining
columns described here.
Note on Averages: To calculate the average number of processes pending, divide the value by the CollectIntervals value. The
CollectIntervals value is the number of gather periods per reporting period.
In the Collect Buffer and Log Buffer, the value is the number of Gather operations that have been performed during the
period. This number can vary from one period to the next.
ProcPendMemAlloc
count
Number of processes blocked pending memory
allocations.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
ProcPendFsgRead
count
Number of processes blocked pending a File
Segment (FSG) read from disk.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
ProcPendFsgWrite
count
Number of processes blocked pending an FSG
write to disk.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
ProcPendNetThrottle
count
Number of processes blocked pending delivery of
outstanding outgoing messages.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
Resource Usage Macros and Tables
55
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
ProcPendNetRead
count
Description
Data Type
Number of processes blocked pending non-step
work, that is, the number of processes blocked
on any mailbox other than the work mailbox.
FLOAT
Invalid
Platform
Always divide this value by CollectIntervals. See
"Note on Averages" above.
Note: Non-step work is anticipated work the
process spawned off and is now waiting for some
type of response from the spawned process or
processes. Non-step work is not unanticipated
work such as a new work request sent when a
user initiates a request from the host.
ProcPendMonitor
count
Number of processes blocked pending a user
monitor.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
ProcPendMonResume
count
Number of processes blocked pending a user
monitor resume from a yield.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
ProcPendDBLock
count
Number of processes blocked pending database
locks.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
ProcPendSegLock
count
Number of processes blocked pending a segment
lock.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
ProcPendFsgLock
count
Number of processes blocked pending an FSG
lock.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
ProcPendMisc
count
Number of processes blocked pending
miscellaneous events.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
ProcPendQnl
count
Number of processes blocked pending a
TSKQNL lock.
FLOAT
Note: Always divide this value by
CollectIntervals. See "Note on Averages" above.
56
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Process Block Counts Columns
Identify how many times a process became blocked on which blocking type. Average time blocked can be approximated by
dividing corresponding ProcWaitXxx by ProcBlksXxx.
ProcBlksMemAlloc
count
Number of process blocks for memory
allocations.
FLOAT
ProcBlksQnl
count
Number of process blocks for a TSKQNL lock.
FLOAT
ProcBlksFsgRead
count
Number of process blocks for an FSG read from
disk.
FLOAT
ProcBlksFsgWrite
count
Number of process blocks for an FSG write to
disk.
FLOAT
ProcBlksNetThrottle
count
Number of process blocks for delivery of
outstanding outgoing messages.
FLOAT
ProcBlksMsgRead
count
Number of process blocks for non-step work.
FLOAT
ProcBlksMonitor
count
Number of process blocks for a user monitor.
FLOAT
ProcBlksMonResume
count
Number of process blocks for a user monitor
resume from a yield.
FLOAT
ProcBlksDBLock
count
Number of process blocks for database locks.
The AWT can do other work while the lock is
blocked.
FLOAT
ProcBlksSegLock
count
Number of process blocks for a disk or task
context (scratch, stack, and so on) segment lock.
FLOAT
ProcBlksFsgLock
count
Number of process blocks for an FSG lock.
FLOAT
ProcBlksTime
count
Number of process blocks waiting only for timer
expiration.
FLOAT
ProcBlksMisc
count
Number of process blocks for miscellaneous
events.
FLOAT
Process Pending Wait Time Columns
Identify how much time in centiseconds processes were in the blocked state for each possible reason.
Note: Since this time is only accounted for when a blocked process leaves the blocked state, it is possible for this statistic to
be much larger than the amount of time available to all processes in a single log period.
ProcWaitMemAlloc
count
Total time processes were blocked pending
memory allocations.
FLOAT
ProcWaitPageRead
count
Total time processes were blocked pending a page
read from disk.
FLOAT
ProcWaitFsgRead
count
Total time processes were blocked pending an
FSG read from disk.
FLOAT
Resource Usage Macros and Tables
57
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
ProcWaitFsgWrite
Description
Data Type
count
Total time processes were blocked pending an
FSG write to disk.
FLOAT
ProcWaitNetThrottle
count
Total time processes were blocked pending
delivery of outstanding outgoing messages.
FLOAT
ProcWaitMsgRead
count
Total time processes were blocked pending nonstep work.
FLOAT
ProcWaitMonitor
count
Total time processes were blocked pending a user
monitor.
FLOAT
ProcWaitMonResume
count
Total time processes were blocked pending a user
monitor resume from a yield.
FLOAT
ProcWaitDBLock
count
Total time processes were blocked pending
database locks.
FLOAT
ProcWaitSegLock
count
Total time processes were blocked pending a disk
or task context (scratch, stack, and so on)
segment lock.
FLOAT
ProcWaitFsgLock
count
Total time processes were blocked pending an
FSG lock.
FLOAT
ProcWaitTime
count
Total time processes were blocked pending some
amount of elapsed time only.
FLOAT
ProcWaitQnl
count
Total time processes were blocked pending a
TSKQNL lock.
FLOAT
ProcWaitMisc
count
Total time processes were blocked pending
miscellaneous events.
FLOAT
Invalid
Platform
CPU Utilization Columns
Count all CPU activities, including activities performed for virtual processors, subdivided into the following columns:
1 CPUIdle - Idle time
2 CPUIoWait - Idle and waiting for I/O completion
3 CPUUServ - User service
4 CPUUExec - User execution
5 CPUIdleNorm - Normalized idle time
6 CPUIOWaitNorm - Normalized idle and waiting for I/O completion
7 CPUUServNorm - Normalized user service
8 CPUUExecNorm - Normalized user execution
These columns represent the sum of all CPUs on the node. To obtain the average node CPU value for each column,
CPU(Idle, IOWait, Userv, Uexec), divide the column data by the number of CPUs per node (the value in the NCPUs
column) and the number of centiseconds (CentiSecs column) in the logging interval.
58
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Note:
•
•
•
•
•
•
CPU idle time = CPUIdle + CPUIoWait
CPU busy time = CPUUServ + CPUUExec
CPUIdleNorm = (CPUIdle * NodeNormFactor)/100
CPUIOWaitNorm = (CPUIoWait * NodeNormFactor)/100
CPUUServNorm = (CPUUServ * NodeNormFactor)/ 100
CPUUExecNorm = (CPUUExec * NodeNormFactor)/100
where the NodeNormFactor is the per node normalization factor. This is related to the NodeType value reported in this
resource usage table. The normalization factor modifies the reported CPU times to the equivalent time of a specified
virtual processor. This does not add up to the reported CPU time. You can calculate the CPU time by using the formula
below.
CPUIdleNorm + CPUIOWaitNorm + CPUUServNorm + CPUUExecNorm = CentiSecs * NCPUs * NodeNormFactor
To calculate the non-normalized total CPU time, use the following formula:
100 x Secs x NCPUs ≈ CentiSecs x NCPUs = CPU(Idle, IoWait, UServ, UExec)
The CPU time returned in centiseconds is more accurate than those returned in seconds.
CPUIdle
count
Time in centiseconds CPUs are idle and not
waiting for I/O.
FLOAT
CPUIoWait
count
Time in centiseconds CPUs are idle and waiting
for I/O completion.
FLOAT
Windows
On Windows, the value is always 0.
Note: This time represents another variety of
Idle, since a CPU is only in this state if there are
no processes eligible for execution. If there was a
process available, the CPU would be immediately
dispatched for that process.
CPUUServ
count
Time in centiseconds CPUs are busy executing
user service code, that is, privileged work
performing system services on behalf of user
execution processes which do not have root
access.
FLOAT
CPUUExec
count
Time in centiseconds CPUs are busy executing
user execution code, that is, time spent in a user
state on behalf of a process.
FLOAT
CPUIdleNorm
count
Time in centiseconds CPUs are idle and not
waiting on I/O.
FLOAT
CPUIOWaitNorm
count
Time in centiseconds CPUs are idle and waiting
for I/O completion.
FLOAT
Windows
On Windows, the value is always 0.
Resource Usage Macros and Tables
59
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
CPUUServNorm
CPUUExecNorm
Description
Data Type
count
Time in centiseconds CPUs are busy executing
user service code, that is, privileged work
performing system services on behalf of user
execution processes which do not have root
access.
FLOAT
count
Time in centiseconds CPUs are busy executing
user execution code; that is, time spent in a user
state on behalf of a process.
FLOAT
Invalid
Platform
MEMORY COLUMNS
Memory Allocation Columns
Identify the number and amount of memory allocations, subdivided into (the only applicable) generic node memory type
and a summarization of vproc memory types.
MemTextAllocs
count
Number of successful memory allocations and
size-increasing memory alters for non-system
overhead text (code). Amount allocated can be
derived by multiplying the number of allocations
by the fixed page size.
FLOAT
ALL
MemVprAllocs
count
Number of successful memory allocations and
size-increasing memory alters for all vproc
memory types, that is, disk segments and task
context types.
FLOAT
ALL
MemVprAllocKB
count
The value represents the change in memory. It
represents a delta from the previous reporting
period. Thus, it will report negative values as less
memory is used.
FLOAT
Windows
Note: The original meaning of this column was
the total KBs attributed to allocations and sizeincreasing alters for vproc memory types.
Memory Pages Resident Columns
Identify the amount, in number of pages or KBs, of memory resident subdivided into memory types. Disk segment memory
types are described by the single entries below. Each of these expands into six columns, where [seg] is as follows:
•
•
•
•
•
•
PDb = Permanent data block disk segments
PCi =Permanent cylinder index disk segments
SDb =Regular or restartable spool data block disk segments
SCi = Regular or restartable spool cylinder index disk segments
TJt = Transient journal table or WAL data block or WAL cylinder index
APt = Append table or permanent journal table data block or cylinder index disk segments
MemTSysOhRes
60
track
Number of pages resident in memory for system
overhead text. System Overhead Text is wired
into memory upon startup and will not change.
FLOAT
ALL
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
MemDSysOhRes
track
Number of pages resident in memory for system
overhead data. System Overhead Data is wired
into memory upon startup.
FLOAT
ALL
MemTextRes
track
Number of pages resident in memory for text.
FLOAT
ALL
MemCtxtRes
track
Number of pages resident in memory for task
context segments.
FLOAT
ALL
Mem[seg]KBRes
track
Current KBs resident in memory for (nonbackup) disk segments.
FLOAT
ALL
MemFreeKB
track
KBs of free memory. This value should be equal
to the size of memory minus the total amount
resident derived from adding all of the above
memory resident columns and frozen disk
segment resident column from ResUsageSvpr.
FLOAT
On Linux, the value reported is the approximate
amount of memory that is available for use. The
Linux operating system uses most free memory
for buffers and caching to improve performance,
but the operating system can reclaim that
memory if it is needed by programs.
The following formula is used by the RSS to
calculate the MemFreeKB value.
MemFreeKB = MemFree + Buffers + Cached +
SwapCached - fsgavailpgs*kbperpage (active_slabs*pgsperslab*kbperpage)
where the values:
• MemFree, Buffers, Cached, and SwapCached
come from /proc/meminfo.
• fsgavailpgs come from the PDE FSG code.
• active_slabs and pgsperslab come from /proc/
slabinfo.
Memory Availability Management Columns
Identify overhead to managing memory when memory availability is a problem.
MemFails
count
Number of failures performing memory
allocations and size-increasing memory alters for
vproc memory types as well as node memory
types.
FLOAT
ALL
MemAgings
count
Number of times memory was aged.
FLOAT
ALL
MemTextPageDrops
count
Number of non-system overhead text pages
dropped from memory to make more physical
memory available.
FLOAT
ALL
Resource Usage Macros and Tables
61
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
MemTextPageReads
count
Description
Data Type
Number of non-system overhead text pages
required to be read from disk when it was
previously paged out.
FLOAT
Invalid
Platform
On Linux, the number of 4KB pages paged
minus the pages swapped in.
MemProcSwapped
track
Current count of processes whose stack has been
written to disk to make available more physical
memory. This value is less than, or equal to, total
processes allocated.
FLOAT
MemCtxtPageWrites
count
Number of task context (scratch, stack, and so
on) pages that were paged out.
FLOAT
ALL
On Linux, the number of 4KB pages swapped
out.
MemCtxtPageReads
count
Number of task context (scratch, stack, and so
on) pages that were paged in.
FLOAT
On Linux, the number of 4KB pages swapped in.
MemSwapDrops
count
Number of disk segments that were dropped
from memory because all its ancestor processes
were swapped out.
FLOAT
ALL
MemSwapDropKB
count
KBs dropped from memory by MemSwapDrops.
FLOAT
ALL
MemSwapReads
count
Number of disk segments that were re-read when
they were previously dropped from memory
because all its ancestor processes were swapped
out.
FLOAT
ALL
MemSwapReadKB
count
KBs re-read from memory by MemSwapReads.
FLOAT
ALL
NET COLUMNS
Point-to-Point Net Traffic Columns
Identify the number (Reads, Writes) and amount (ReadKB, WriteKB) of input and output messages passing through the
Teradata Database nets through point-to-point (1:1) methods (PtP). It excludes TCP/IP traffic.
MsgPtPReads
count
Number of net point-to-point messages input to
processes on the node via the message
subsystem.
FLOAT
MsgPtPWrites
count
Number of net point-to-point messages output
from processes on the node via the message
subsystem.
FLOAT
MsgPtPReadKB
count
Total KBs of net point-to-point messages input
to processes on the node via the message
subsystem.
FLOAT
62
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
MsgPtPWriteKB
count
Description
Data Type
Total KBs of net point-to-point messages output
from processes on the node via the message
subsystem.
FLOAT
Invalid
Platform
Broadcast Net Traffic Columns
Identify the number (Reads, Writes) and amount (ReadKB, WriteKB) of input and output messages passing through the
Teradata Database nets through broadcast (1:many) methods (Brd).
Note: If a single broadcast message is delivered to multiple processes in this node, the NetBrdReads and NetBrdReadKB are
only incremented once.
MsgBrdReads
count
Number of net broadcast messages input to
processes on the node via the message
subsystem.
FLOAT
MsgBrdWrites
count
Number of net broadcast messages output from
processes on the node via the message
subsystem.
FLOAT
MsgBrdReadKB
count
Total KBs of net broadcast messages input to
processes on the node via the message
subsystem.
FLOAT
MsgBrdWriteKB
count
Total KBs of net broadcast messages output from
processes on the node via the message
subsystem.
FLOAT
Network Transport Data Columns
Identify the number (Reads, Writes) and amount of input and output (PDE messages routed by the message subsystem)
passing through the Teradata Database nets. These statistics are nonspecific, that is, they do not take into consideration
which Bynet performed the transport.
NetMsgPtpWriteKB
count
Amount of point-to-point message data in KBs
transmitted by both Bynets.
FLOAT
NetMsgBrdWriteKB
count
Amount of broadcast message data in KBs
transmitted by both Bynets.
FLOAT
NetMsgPtpReadKB
count
Amount of point-to-point message data in KBs
received by both Bynets.
FLOAT
NetMsgBrdReadKB
count
Amount of broadcast message data in KBs
received by both Bynets.
FLOAT
NetMsgPtpWrites
count
The number of point-to-point messages
transmitted by both Bynets.
FLOAT
NetMsgBrdWrites
count
The number of broadcast messages transmitted
by both Bynets
FLOAT
NetMsgPtpReads
count
The number of point-to-point messages received
by both Bynets.
FLOAT
NetMsgBrdReads
count
The number of broadcast messages received by
both Bynets.
FLOAT
Resource Usage Macros and Tables
63
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Per-Bynet Network Transport Data Columns
Identify the amount of input and output passing through the Teradata Database nets.
These statistics are net-specific, that is, they relate to each specific Bynet. On a single-node (virtual network [vnet]) system,
net-specific statistics are not meaningful and are always zero.
NetTxKBPtP
count
Total point-to-point KBs transmitted over all
Bynets.
FLOAT
NetRxKBPtP
count
Total point-to-point KBs received over all
Bynets.
FLOAT
NetTxKBBrd
count
Total broadcast KBs transmitted over all Bynets.
FLOAT
NetRxKBBrd
count
Total broadcast KBs received over all Bynets.
FLOAT
Net Controller Status and Miscellaneous Management
Provide utilization and other status information about the Teradata Database net controllers.
These statistics are not net-specific since all the Bynet statistics are reported in the net columns. On a single-node (vnet)
system, net-specific statistics are not meaningful and are always zero.
NetTxRouting
count
Number of samples showing the transmitter
routing on a Bynet.
FLOAT
NetTxConnected
count
Number of samples showing the transmitter
connected on a Bynet.
FLOAT
NetRxConnected
count
Number of samples showing the receiver
connected on a Bynet.
FLOAT
NetTxIdle
count
Number of samples showing the transmitter idle
on a Bynet.
FLOAT
NetRxIdle
count
Number of samples showing the receiver idle on
a Bynet.
FLOAT
Net Circuit Management Columns
Identify the management of Teradata Database net circuits (Circ). Additional detail is found in Appendix B: “ResUsageIpma
Table.”
Note: Circuit attempts for one or both Bynets can be computed as the sum of the applicable NetTxCircPtp and
NetTxCircBrd columns. All of these columns except for NetCircBackoffs are net-specific. On a single-node system, netspecific statistics are not meaningful and are always zero.
NetTxCircHPBrd
count
Number of high priority broadcast circuits
transmitted on all Bynets.
FLOAT
NetRxCircPtp
count
Total number (both normal and high priority) of
point-to-point circuits received on all Bynets.
FLOAT
NetTxCircHPPtP
count
Number of high priority point-to-point circuits
transmitted on all Bynets.
FLOAT
64
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
NetRxCircBrd
Description
Data Type
count
Total number (both normal and high priority) of
broadcast circuits received on all Bynets.
FLOAT
NetTxCircBrd
count
Total number (both normal and high priority) of
broadcast circuits transmitted on all Bynets.
FLOAT
NetCircBackoffs
count
Software backoffs, defined as BNS service
blocked occurrences, without regard for which
net was involved.
FLOAT
NetHWBackoffs
count
Hardware backoffs reported by the BLM for all
Bynets.
FLOAT
NetTxCircPtp
count
Total number (both normal and high priority) of
point-to-point circuits transmitted on all Bynets.
FLOAT
Invalid
Platform
Group Coordination Messages Columns
Identify messages that are communicated through the Teradata Database net for coordination of a process among a group of
vprocs. Coordination is handled either through semaphores, groups, or channels.
MsgChnLastDone
count
Number of last done events that occurred on this
node.
FLOAT
Note: The last AMP to finish an operation may
send a last done broadcast message indicating
the work is done for this step. This is used in
tracking down the slowest node or AMP in the
system. A node or AMP that has more last done
messages than the others could be a bottleneck in
the system performance.
NetSemInUseSum
count
Total number of semaphores in use during each
log interval.
FLOAT
NetSemInUseMax
max
Maximum number of semaphores in use during
each log interval.
FLOAT
NetChanInUseSum
count
Total number of channels in use during each log
interval.
FLOAT
NetChanInUseMax
max
Maximum number of channels in use.
FLOAT
NetGroupInUseSum
count
Total number of groups in use during each log
interval. This number should be same across all
nodes.
FLOAT
NetGroupInUseMax
max
Maximum number of groups in use during each
log interval.
FLOAT
Merge Services Columns
Identify activity occurring through merge (many:1) methods (Mrg) on Teradata Database net.
NetMrgTxKB
count
Resource Usage Macros and Tables
Number of KBs transmitted, without regard to
which net, by merge transmission services for
currently active merge operations.
FLOAT
65
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
NetMrgRxKB
Description
Data Type
count
Number of KBs received, without regard to
which net, by merge receive services for currently
active merge operations.
FLOAT
NetMrgTxRows
count
Number of data rows transmitted, without
regard to which net, by merge transmission
services for currently active merge operations.
FLOAT
NetMrgRxRows
count
Number of data rows received, without regard to
which net, by merge receive services for currently
active merge operations.
FLOAT
Invalid
Platform
HOST CONTROLLER COLUMNS
Channel Traffic Columns
Identify the traffic between the host and the node in three levels of granularity: blocks, messages, and KBs. Blocks are made
up of some amount of variable sized messages. ReadKB and WriteKB identify the KBs involved in the traffic.
HostBlockReads
count
Number of blocks read in from the host.
FLOAT
HostBlockWrites
count
Number of blocks written out to the host.
FLOAT
HostMessageReads
count
Number of messages read in from the host.
FLOAT
HostMessageWrites
count
Number of messages written out to the host.
FLOAT
HostReadKB
count
KBs transferred in from the host.
FLOAT
HostWriteKB
count
KBs transferred out to the host.
FLOAT
GENERAL CONCURRENCY CONTROL COLUMNS
Database Locks Columns
Identify database locking occurrences.
DBLockBlocks
count
Number of times a database lock was blocked.
FLOAT
DBLockDeadlocks
count
Number of times a database lock was
deadlocked.
FLOAT
FILE SYSTEM COLUMNS
Segments Acquired Columns
Summarize logical and physical segments acquired by the file system. These columns identify the total disk memory
segments acquired by the file system during the log period. Logical acquires (Acqs) and the logical amount acquired
(AcqKB) are identified. Acquires causing physical reads (AcqReads) and the amount read (AcqReadKB) are identified as a
subset of logical acquires.
For more detail, see “Segment Acquires Columns” on page 136 in the ResUsageSvpr Table chapter.
FileAcqs
66
count
Total number of logical disk segments acquired.
FLOAT
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
Description
Data Type
FileAcqKB
count
Total KBs logically acquired by FileAcqs.
FLOAT
Invalid
Platform
Note: Use the views provided in Chapter 14
instead of accessing the data for this field directly
from this table.
FileAcqReads
count
Total number of disk segment acquires that
caused a physical read.
FLOAT
FileAcqReadKB
count
Total KBs physically read by FileAcqReads.
FLOAT
Segments Released Columns
Summarize logical and physical segments released by the file system. For more detail, see “Segments Released Columns” on
page 138 in the ResUsageSvpr Table chapter.
FileRels
count
Total number of logical disk segments released
by tasks.
FLOAT
FileRelKB
count
Total KBs logically released by FileRels.
FLOAT
Note: Use the views provided in Chapter 14
instead of accessing the data for this field directly
from this table.
FileWrites
count
Total number of disk segment immediate or
delayed physical writes.
FLOAT
FileWriteKB
count
Total KBs physically written by FileWrites.
FLOAT
Data Block Prefetches Columns
Summarize the effects of prefetching data blocks on the file system. For more detail, see “Data Block Prefetches Columns”
on page 137 in the ResUsageSvpr Table chapter.
Note: A prefetch is either a cylinder read operation or individual block reads operation. Either of these operations are
generically called a prefetch.
When all cylinder slots are in use, the cylinder reads revert back to the original algorithm of a block-at-a-time read ahead. So
the column FilePreKB is the sum of the size of data blocks logically read by either cylinder reads or data block pre-reads.
This also applies to the physical pre-reads. FilePreReadKB includes both physical cylinder reads and single block pre-reads.
The number of data blocks that are pre-read at a time is controlled by the DBS Control performance parameter ReadAhead
Count. The default is 1 block at a time pre-read.
If you enable cylinder reads, there will be extra sectors read in on cylinder reads. An accurate calculation of the wasted
kilobytes read by cylinder read is not possible since there are legitimate logical pre-reads that do not incur physical prereads.
For more information on cylinder read, see Performance Management.
FilePres
count
Resource Usage Macros and Tables
Total number of times a logical data prefetch was
performed (either as a cylinder read or
individual block reads).
FLOAT
67
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
FilePreKB
count
Description
Data Type
Sum of the sizes of data blocks logically loaded
with data prefetches (either cylinder reads or
individual block reads).
FLOAT
Invalid
Platform
For cylinder reads, this field does not include the
disk sectors in between the loaded data blocks.
Note: Use the views provided in Chapter 14
instead of accessing the data for this field directly
from this table.
FilePreReads
count
Number of times a data prefetch was physically
performed either as a cylinder read or individual
blocks read.
FLOAT
FilePreReadKB
count
The size of the data prefetch (cylinder section or
individual blocks being read) that is physically
loaded from disk.
FLOAT
For cylinder reads, this field includes the disk
sectors in between the loaded data blocks.
Data Segment Lock Requests Columns
Summarize the number of lock requests, blocks, and deadlocks on a disk segment. For more detail, see “Data Segment Lock
Requests Columns” on page 139 in the ResUsageSvpr Table chapter.
FileLockBlocks
count
Number of lock requests that were blocked.
FLOAT
FileLockDeadlocks
count
Number of deadlocks detected on lock requests.
FLOAT
FileLockEnters
count
Number of times a lock was requested.
FLOAT
Depot Columns
Summarize the physical writes to the Depot used to protect in-place modifications.
FileSmallDepotWrites
68
count
Number of small writes to the depot performed
to protect in-place modifications. Each small
Depot write protects a single in-place write of
either a WAL data block or a database data block.
The small Depot is typically used when the inplace writes are initiated by a foreground task.
Small Depot writes are also counted against
FileWrites; therefore, FileWrites still indicates the
total writes regardless of whether it was a Depot
write or a database write.
FLOAT
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
FileLargeDepotWrites
FileLargeDepotBlocks
Description
Data Type
count
Number of large writes to the depot performed
to protect in-place modifications. Each large
Depot write protects multiple in-place writes of
either WAL data blocks or database data blocks.
The large Depot is typically used when blocks
age out of memory in the background. Large
Depot writes are also counted against FileWrites;
therefore, FileWrites still indicates the total
writes regardless of whether it was a Depot write
or a database write.
FLOAT
count
Total number of blocks (either WAL or database)
that have been protected by large Depot writes.
FLOAT
Invalid
Platform
Since a large Depot write protects multiple
blocks, the following calculation results in the
average number of blocks protected by each large
Depot write:
FileLargeDepotBlocks / FileLargeDepotWrites
USER COMMANDS COLUMNS
User Command Columns
Summarize the type of statements given to Teradata Database by the user. For more detail, see Chapter 8: “ResUsageShst
Table.”
CmdDDLStmts
count
Number of alter, modify, drop, create, replace,
grant or revoke commands.
FLOAT
CmdDeleteStmts
count
Number of delete commands.
FLOAT
CmdInsertStmts
count
Number of insert commands.
FLOAT
CmdSelectStmts
count
Number of select commands.
FLOAT
CmdUpdateStmts
count
Number of update commands.
FLOAT
CmdUtilityStmts
count
Number of utility commands.
FLOAT
CmdOtherStmts
count
Number of other commands.
FLOAT
User Command Arrival and Departure Columns
Summarize the arrival and departure of user statements. For more detail, see Chapter 8: “ResUsageShst Table.”
CmdStmtsInProgCur
count
Current count of statements in progress.
FLOAT
CmdStmtSuccesses
count
Number of statements that departed normally.
FLOAT
CmdStmtFailures
count
Number of statements that departed in failure or
were aborted.
FLOAT
CmdStmtErrors
count
Number of statements that departed in error.
FLOAT
Resource Usage Macros and Tables
ALL
69
Chapter 6: ResUsageSpma Table
Column Name
Type of
Data
CmdStmtTime
count
Description
Data Type
Invalid
Platform
The sums of the resident time of each statement
in progress during the log period, including the
successes and failures.
FLOAT
ALL
TERADATA ASM COLUMNS
AMP Worker Task Columns
Collect and report statistics about the AWTs. For more information about the ResUsageSawt table and columns, see
Chapter 7: “ResUsageSawt Table.”
AwtFlowControlled
count
Number of AMPs currently in flow control on
the work input mailbox.
FLOAT
AwtFlowCtlCnt
count
Number of times this log period that the node
entered the flow control state from a non-flow
controlled state.
FLOAT
AwtInuse
max
Number of AWTs currently in use for this node.
Divide the value for AwtInUse by the
CollectIntervals value to obtain an average.
FLOAT
The AwtInuse value of a log period can be larger
than the AwtInuseMax value of the log period if
a log period consists of multiple gather periods.
The AwtInuse value in a log period is the
summation of the values of the gather periods
comprising the log period. This is why the
AwtInuse value needs to be divided by the
CollectIntervals value. The CollectIntervals value
is the number of gather periods per reporting
period. For more information, see the
CollectIntervals column.
AwtInuseMax
max
Peak number of AWTs (Max) on this node. This
is not the Peak or the Max value stored in the
Priority Scheduler (sch) data structure and
reported by the puma utility. The sch peak value
is the Max value since startup is never set and
Max is the maximum allowed value.
FLOAT
Note: This reported Max value is the maximum
reached during each log period.
For example, if there are 4 gather periods in one
log period, and the max value of each period is
10, 32, 7, and 15, the max of the log period
would be the max of the individual gather
periods, which would be 32.
70
Resource Usage Macros and Tables
Chapter 6: ResUsageSpma Table
Spare Columns
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Priority Scheduler Columns
Provides data specific to the Priority Scheduler. For more information about the ResUsageSps table and columns, see
Chapter 11: “ResUsageSps Table.”
PSNumRequests
count
Number of work requests received for all
Performance Groups on this node.
FLOAT
PSQWaitTime
count
Time in centiseconds that work requests waited
on an input queue before being serviced.
FLOAT
To get an approximate average QWaitTime per
request during this period, divide QWaitTime by
NumRequests.
PSServiceTime
count
Time in centiseconds that work requests
required for service.
FLOAT
To get an approximate average ServiceTime per
request during this period, divide ServiceTime
by NumRequests.
Spare Columns
The ResUsageSpma table has 12 spare columns (one of which is being used) as shown in the
table below.
Column Name
Type of Data
Description
SpareCount[00-03]
count
Spare counted statistic.
SpareTrack[00-03]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 field contains the COD
value. The value represents the COD value in
one tenths of a percent, so a displayed value of
500 represents a COD value of 50.0%.
Note: This value is valid only on SUSE Linux
Enterprise Server 10 systems and is a single
value for the entire system.
SpareTmon[01-03]
count
Spare time monitored statistic.
The spare column fields expand to values 00 - 03, so that column names would be
SpareCount01 or SpareTrack02, and so on.
Resource Usage Macros and Tables
71
Chapter 6: ResUsageSpma Table
Spare Columns
72
Resource Usage Macros and Tables
CHAPTER 7
ResUsageSawt Table
The ResUsageSawt table collects and reports statistics about the AWTs. If table logging is
enabled, then data is written to the database once for each log period.
To consolidate and summarize the total number of rows written to the database, you can
enable Summary Mode. For details, see “Summary Mode” on page 77.
Note: This table is created as a MULTISET table.
The following table describes the ResUsageSawt table columns.
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system load,
entries may be logged late (typically, by no more
than one or two seconds), but this field will still
contain the time value when the entry should have
been logged. See the Secs and NominalSecs
columns.
NodeId
n/a
Identifies the Node upon which the vproc resides.
The Node ID is formatted as CCC-MM, where CCC
denotes the three-digit cabinet number and MM
denotes the two-digit chassis number of the node.
For example, a node in chassis 9 of cabinet 3 has a
node ID of ‘003-09’.
INTEGER
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an SMP
node is ‘001-01’.
MISCELLANEOUS HOUSEKEEPING COLUMNS
GmtTime
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that occur
twice a year.
FLOAT
NodeType
n/a
Type of node, representing the per node system
family type. For example, 5600C or 5555H.
CHAR(8)
Resource Usage Macros and Tables
73
Chapter 7: ResUsageSawt Table
Column Name
Type of
Data
VprId
Secs
Description
Data Type
n/a
Identifies the vproc number. All Vprocs in this table
are AMPS so there is no VprType field provided. In
Summary Mode, this field is zero.
INTEGER
n/a
Actual number of seconds in the log period
represented by this row. Normally the same as
NominalSecs, but can be different in three cases:
SMALLINT
Invalid
Platform
• The first interval after a log rate change
• A sample logged late because of load on the
system
• System clock adjustments affect reported Secs
Useful for normalizing the count statistics
contained in this row, for example, to a per-second
measurement.
CentiSecs
n/a
Number of centiseconds in the logging period. This
field is useful when performing data calculations
with small elapsed times where the difference
between centisecond-based data and whole seconds
results in a percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds in the
logging period.
SMALLINT
SummaryFlag
n/a
Identifies the summarization status of this row. If
the value is ‘N,’ the row is a non-summary row. If
the value is ‘S,’ the row is a summary row. For
details, see “Summary Mode” on page 77.
CHAR
Active
n/a
Controls whether or not the rows will be logged to
the ResUsage tables if Active Row Filter Mode is
enabled.
FLOAT
If Active is set to:
• a non-zero value, then the row contains
modified data columns.
• a zero value, then none of the data columns in
the row have been updated during the logging
period.
For example, if Active Row Filter Mode is enabled,
then the rows that have a zero Active field value will
not be logged to the ResUsage tables.
CollectIntervals
n/a
SMALLINT
The number of gather periods per reporting
period.
In the Collect Buffer and Log Buffer, the value is the
number of Gather operations that have been
performed during the period. This number can
vary from one period to the next.
74
Resource Usage Macros and Tables
Chapter 7: ResUsageSawt Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
STATISTICS COLUMNS
TERADATA ASM COLUMNS
AMP Worker Task Columns
Collect and report statistics about the AWTs.
MailBoxDepth
count
The average depth of the AMP work mailbox.
FLOAT
Note: This value reports the SUM of the values
reported in each gather period when there are
multiple gather intervals in each log period. It
should be divided by the CollectIntervals column
to get the average value.
FlowControlled
track
Specifies if an AMP is in flow control. If the value is
non-zero, then the AMP is in flow control.
FLOAT
FlowCtlCnt
count
Number of times during the log period that the
system entered the flow control state from a nonflow controlled state.
FLOAT
FlowCtlTime
count
The total time in milliseconds that an AMP is in
flow control.
FLOAT
InuseMax
max
Maximum number of AWTs in use at any one time
during the log period.
FLOAT
WorkTypeInuse00 WorkTypeInuse15
count
Current number of AWTs in use during the log
period for each work type for the VprId vproc.
FLOAT
Note: This value reports the SUM of the values
reported in each gather period when there are
multiple gather intervals in each log period. It
should be divided by the CollectIntervals column
to get the average value.
WorkTypeMax00 WorkTypeMax15
max
Maximum number of AWTs in use at one time
during the log period for each work type for the
VprId vproc.
FLOAT
In Summary Mode, the WorkTypeMax field values
are the Max of the values for all the AMPS.
WORK TYPE DESCRIPTIONS
The WorkTypeInuse and WorkTypeMax array data columns above each contain 16 Work Type entries that are described here.
For example, WorktypeInuse00 contains the number of in use AWTs that are of Work Type MSGWORKNEW, and
WorktypeInuse01 contains the values for MSGWORKONE.
These columns allow the user to monitor the usage of the AWTs of each work type. This can be used to determine if the usage is
close to the maximum values defined and what type of work they are doing. Also, this can be used to determine characteristics
of the system during skew conditions or when there are AWT shortages.
Use the tdntune utility to determine the settings for Flow Control. For information on Expedited Allocation Groups, see
"Priority Scheduler (schmon)" chapter of Utilities.
Resource Usage Macros and Tables
75
Chapter 7: ResUsageSawt Table
Column Name
Type of
Data
MSGWORKNEW
n/a
Description
Data Type
Used for new work requests. This work type has the
lowest number, which means it is queued last. It
also has the effect of honoring secondary requests
needed to complete existing work items before any
new ones are started.
n/a
Invalid
Platform
A zero value is used for new work items.
MSGWORKONE
n/a
First level secondary work items. Numbered work
types are used for secondary work items. For
example, work type one (MSGWORKONE) is used
for secondary work requests spawned by new work
items; work type two (MSGWORKTWO) requests
are spawned from work type one requests and
queued for delivery before work type one requests;
and so on. Each numbered work type is queued for
delivery just before the one from which it is
spawned.
n/a
MSGWORKTWO
n/a
Second level secondary work items.
n/a
MSGWORKTHREE
n/a
Special types of database work.
n/a
MSGWORKFOUR
n/a
Start System Recover.
n/a
MSGWORKFIVE
n/a
This field is not normally used and
MSGWORKNEW, MSGWORKONE, and
MSGWORKTWO report work requests for utilities.
However, if utilities are configured to use a separate
pool of work types, this field reports new work for
utilities such as FastLoad, MultiLoad, and
FastExport.
n/a
MSGWORKSIX
n/a
First level secondary work spawned work for
utilities such as FastLoad, MultiLoad, and
FastExport. If the utilities are not configured to use
a separate pool of work types, they use
MSGWORKNEW, MSGWORKONE, and
MSGWORKTWO.
n/a
MSGWORKSEVEN
n/a
Second level secondary work for utilities such as
FastLoad, MultiLoad, and FastExport. If the
utilities are not configured to use a separate pool of
work types, they use MSGWORKNEW,
MSGWORKONE, and MSGWORKTWO.
n/a
MSGWORKEIGHT
n/a
New work for Expedited Allocation Groups.
n/a
MSGWORKNINE
n/a
First level spawned work for Expedited Allocation
Groups.
n/a
MSGWORKTEN
n/a
Second level spawned work for Expedited
Allocation Groups.
n/a
MSGWORKELEVEN
n/a
Not used.
n/a
76
Resource Usage Macros and Tables
Chapter 7: ResUsageSawt Table
Summary Mode
Column Name
Type of
Data
MSGWORKABORT
n/a
Description
Data Type
Used for transaction abort requests. This work type
has a higher value than the numbered work types
so that abort requests are honored before beginning
any additional work item for the transactions being
aborted.
n/a
Invalid
Platform
The array number for MSGWORKABORT is 12.
MSGWORKSPAWN
n/a
Used for spawned abort requests and is delivered
before normal aborts.
n/a
The array number for MSGWORKSPAWN is 13.
MSGWORKNORMAL
n/a
Used for messages that do not fall within the
standard work type hierarchy. This work type is
delivered before any of the work items described
above.
n/a
The array number for MSGWORKNORMAL is 14.
MSGWORKCONTROL
n/a
Used for system control messages. These are
delivered before any other kind of message.
n/a
The array number for MSGWORKCONTROL is
15.
Summary Mode
When Summary Mode is active for the ResUsageSawt table, one row is written to the database
for each node in the system for each log interval. The AWT data will be combined for all the
AMP vprocs on the node.
You can determine if a row is in Summary Mode by checking the SummaryFlag column for
that row.
IF the SummaryFlag column value is…
THEN the data for that row is being logged…
‘S’
in Summary Mode.
‘N’
normally.
Resource Usage Macros and Tables
77
Chapter 7: ResUsageSawt Table
Spare Columns
Spare Columns
The ResUsageSawt table has 30 spare columns (one of which is being used) as shown in the
table below.
Column Name
Type of Data
Description
SpareCount[00-01, 04-09]
count
Spare counted statistic.
SpareCount[02-03]
count
The following SpareCount columns will be
converted to the specified column names in
Teradata Database 14.0.
• SpareCount02=Available. Available is the
number of unreserved AWTs from the pool
that are not being used at the end of the
interval.
For example, if 12 of the normally 62
unreserved AWTs are removed from the
pool by reserving them for expedited work,
there could at most be 50 unreserved AWTs
available. If in this log period, 10 unreserved
AWTs are taken from the pool to service 10
queries that are still executing, than there
would be only 40 available at the end of the
log period.
• SpareCount03=AvailableMin. AvailableMin
is the minimum number of unreserved
AWTs available in the pool for each AMP
for the logged period.
For example, a value of 0 for SpareCount03
means there were no unreserved AWTs
available in the pool at some point during
the reporting period.
SpareTrack[00-09]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 field contains the COD
value. The value represents the COD value in
one tenths of a percent, so a displayed value of
500 represents a COD value of 50.0%.
Note: This value is valid only on SUSE Linux
Enterprise Server 10 systems and is a single
value for the entire system.
SpareTmon[01-09]
count
Spare time monitored statistic.
The spare column fields expand to values 00–09, so that column names would be
SpareCount00, SpareTrack03, SpareTmon08, and so on.
78
Resource Usage Macros and Tables
CHAPTER 8
ResUsageShst Table
The ResUsageShst table:
•
Contains resource usage information specific to the host channels and LANs
communicating with Teradata Database.
•
Includes resource usage data for system-wide, host information.
Note: This table is created as a MULTISET table.
The following table describes the ResUsageShst table columns.
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system load,
entries may be logged late (typically, by no more
than one or two seconds), but this field will still
contain the time value when the entry should have
been logged. See the Secs and NominalSecs
columns.
NodeId
n/a
Identifies the Node upon which the vproc resides.
The Node ID is formatted as CCC-MM, where CCC
denotes the three-digit cabinet number and MM
denotes the two-digit chassis number of the node.
For example, a node in chassis 9 of cabinet 3 has a
node ID of ‘003-09’.
INTEGER
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an SMP
node is ‘001-01’.
MISCELLANEOUS HOUSEKEEPING COLUMNS
GmtTime
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that occur
twice a year.
FLOAT
NodeType
n/a
Type of node, representing the per node system
family type. For example, 5600C or 5555H.
CHAR(8)
Resource Usage Macros and Tables
79
Chapter 8: ResUsageShst Table
Column Name
Type of
Data
VprId
n/a
Description
Data Type
Identifies the vproc number. In Summary Mode,
VprId is -1.
INTEGER
Invalid
Platform
For LAN-connected hosts, VprId is the Gateway
vproc ID.
For channel-connected hosts, VprId should be the
vproc id of the owning PE. If there are multiple PEs
on this node connecting to this channel, then VprId
will be 65534. If, for some reason, no PE on this
node connects to this channel, VprId will be 65535.
HstId
n/a
Identifies the host. Value is BBMMPPHHH (BB =
Bus, MM = Module Number (or chassis number),
PP = Port, HHH = three digit Host Group ID) with
each field getting two or three decimal digits of the
resulting 9 digit value. The chassis number is always
0 for network-connected hosts. In Summary Mode,
HstId is always 0.
INTEGER
HstType
n/a
Type of host. Possible values are “NETWORK”
(LAN-connected host) and “IBMMUX” (channelconnected host).
CHAR(8)
Secs
n/a
Actual number of seconds in the log period
represented by this row. This value is useful for
normalizing the statistics contained in this row, for
example, to a per-second measurement.
SMALLINT
CentiSecs
n/a
Number of centiseconds in the logging period. This
field is useful when performing data calculations
with small elapsed times where the difference
between centisecond-based data and whole seconds
results in a percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds in the
logging period.
SummaryFlag
n/a
Identifies the summarization status of this row. If
the value is ‘N,’ the row is a non-summary row. If
the value is ‘S,’ the row is a summary row.
SMALLINT
CHAR
In Summary Mode, the rows are summarized into a
single row. For details, see “Summary Mode” on
page 83.
80
Resource Usage Macros and Tables
Chapter 8: ResUsageShst Table
Column Name
Type of
Data
Active
count
Description
Data Type
Controls whether or not the rows will be logged to
the ResUsage tables if Active Row Filter Mode is
enabled.
FLOAT
Invalid
Platform
If Active is set to:
• a non-zero value, then the row contains
modified data columns.
• a zero value, then none of the data columns in
the row have been updated during the logging
period.
For example, if Active Row Filter Mode is enabled,
then the rows that have a zero Active field value will
not be logged to the ResUsage tables.
CollectIntervals
n/a
The number of gather periods per reporting
period.
SMALLINT
In the Collect Buffer and Log Buffer, the value is the
number of Gather operations that have been
performed during the period. This number can
vary from one period to the next.
STATISTICS COLUMNS
HOST CONTROLLER COLUMNS
Channel Traffic Columns
Identify the traffic between the host and the node in three levels of granularity: blocks, messages and KBs. Blocks are made
up of some amount of variable sized messages. ReadKB and WriteKB identify the KBs involved in the traffic.
HostBlockReads
count
Number of blocks read in from the host.
FLOAT
HostBlockWrites
count
Number of blocks written out to the host.
FLOAT
HostMessageReads
count
Number of messages read in from the host.
FLOAT
HostMessageWrites
count
Number of messages written out to the host.
FLOAT
HostReadKB
count
KBs transferred in from the host.
FLOAT
HostWriteKB
count
KBs transferred out to the host.
FLOAT
Resource Usage Macros and Tables
81
Chapter 8: ResUsageShst Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
FLOAT
ALL
ALL
Channel Management Columns
Identify overhead of channel management.
HostQLenSum
count
Total number of messages queued for output to the
host during each log interval.
Note: To calculate the average HostQLen divide the
HostQLenSum by the CollectIntervals value to get
the HostQLen average value during the logging
period. This average is an average of the values
recorded at each of the gather periods that occur
during the logging period.
HostQLenMax
max
Maximum number of messages queued in each log
interval.
FLOAT
HostReadFails
count
Number of failures transmitting from the host.
FLOAT
Note: This is for Teradata Channel software
(TCHN) only.
HostWriteFails
count
Number of failures transmitting to the host.
FLOAT
Note: This is for TCHN only.
User Commands Columns
Identify the type of commands given to Teradata Database by the user. Three levels of granularity are given: transaction,
request, and statement. Transactions consist of one or more requests. Requests consist of one or more statements.
Statements are subdivided into the various statement types.
CmdTransactions
count
Number of transaction commands.
FLOAT
CmdRequests
count
Number of request commands.
FLOAT
CmdAlterStmts
count
Number of alter, modify, or drop statement
commands.
FLOAT
CmdCreateStmts
count
Number of create or replace statement commands.
FLOAT
CmdDeleteStmts
count
Number of delete commands.
FLOAT
CmdGrantStmts
count
Number of grant or revoke commands.
FLOAT
CmdInsertStmts
count
Number of insert commands.
FLOAT
CmdSelectStmts
count
Number of select commands.
FLOAT
CmdUpdateStmts
count
Number of update commands.
FLOAT
CmdArchUtilityStmts
count
Number of archival utility commands (for
example, dump, restore, archive and recovery).
FLOAT
CmdLoadUtilityStmts
count
Number of FastLoad and MultiLoad utility
commands. (Tpump commands cannot be
distinguished, and are therefore counted by the
INSERT, UPDATE and DELETE statements).
FLOAT
82
Resource Usage Macros and Tables
Chapter 8: ResUsageShst Table
Summary Mode
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
CmdMiscUtilityStmts
count
Number of miscellaneous utility commands.
FLOAT
ALL
CmdOtherStmts
count
Number of other commands.
FLOAT
User Command Arrival and Departure Columns
Identify the arrival and departure times and status of user commands.
CmdStmtsInProgMax
max
Maximum number of statements in progress
during each log interval.
FLOAT
ALL
CmdStmtsInProgSum
count
Total count of statements in progress during each
log interval.
FLOAT
ALL
Note: To calculate the average number of
statements in progress, divide this value by the
CollectIntervals value. The CollectIntervals value is
the number of gather periods per reporting period.
For more information, see the CollectIntervals
column.
CmdStmtSuccesses
count
Number of statements that departed normally.
FLOAT
CmdStmtFailures
count
Number of statements that departed in failure or
abortion.
FLOAT
CmdStmtErrors
count
Number of statements that departed in error.
FLOAT
CmdStmtTime
count
The sums of the resident time of each statement in
progress during the log period, including the
successes and failures.
FLOAT
ALL
Summary Mode
When Summary Mode is active for the ResUsageShst table, one row is written to the database
for each type of host (network or channel-connected) on each node in the system,
summarizing the hosts of that type on that node, for each log interval as follows:
You can determine if a row is in Summary Mode by checking the SummaryFlag column for
that row.
IF the SummaryFlag column value is…
THEN the data for that row is being logged…
‘S’
in Summary Mode.
‘N’
normally.
Resource Usage Macros and Tables
83
Chapter 8: ResUsageShst Table
Spare Columns
Spare Columns
The ResUsageShst table has 30 spare columns (one of which is being used) as shown in the
table below.
Column Name
Type of Data
Description
SpareCount[00-09]
count
Spare counted statistic.
SpareTrack[00-09]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 field contains the Capacity
on Demand (COD) value. The value represents
the COD value in one tenths of a percent, so a
displayed value of 500 represents a COD value
of 50.0%.
Note: This value is valid only on SUSE Linux
Enterprise Server 10 systems and is a single
value for the entire system.
SpareTmon[01-09]
count
Spare time monitored statistic.
The spare column fields expand to values 00-09, so that column names would be
SpareCount00, SpareTrack04, SpareTmon01, and so on.
84
Resource Usage Macros and Tables
CHAPTER 9
ResUsageSldv Table
The ResUsageSldv table contains resource usage information for system-wide, logical device
information. Statistics from this table are collected from the storage devices.
Note: This table is created as a MULTISET table. For more information see “Relational
Primary Index” on page 38.
The following table describes the ResUsageSldv table columns.
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system load,
entries may be logged late (typically, by no more
than one or two seconds), but this field will still
contain the time value when the entry should have
been logged. See the Secs and NominalSecs
columns.
NodeId
n/a
Identifies the Node upon which the vproc resides.
The Node ID is formatted as CCC-MM, where CCC
denotes the three-digit cabinet number and MM
denotes the two-digit chassis number of the node.
For example, a node in chassis 9 of cabinet 3 has a
node ID of ‘003-09’.
INTEGER
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an SMP
node is ‘001-01’.
MISCELLANEOUS HOUSEKEEPING COLUMNS
GmtTime
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that occur
twice a year.
FLOAT
NodeType
n/a
Type of node, representing the per node system
family type. For example, 5600C or 5555H.
CHAR(8)
Resource Usage Macros and Tables
85
Chapter 9: ResUsageSldv Table
Column Name
Type of
Data
VprId
CtlId
Description
Data Type
n/a
Note: This column is obsolete in normal mode
and the value is set to 65535.
INTEGER
n/a
Represents the controller number.
INTEGER
Invalid
Platform
The value is the decimal equivalent of the three
digit controller ID in the LdvId. The maximum
controller ID is 255 decimal. This allows the storage
devices to be grouped by CtlId for controller based
summarization.
If the controller information is not available, its
value is set to 255.
In summary mode, the CtlId is set to 255.
LdvId
n/a
Represents the storage device in the Bus System
where it resides. The value in LdvId is -1.
BYTE(4)
Note: For Linux, the LdvId is derived from the
Host, Channel, Id, and Lun information of the
device.
For Windows, the LdvId is derived from the Port
number, path Id, target Id, and Lun information of
the device.
If the device address information is not available,
this field contains the device major and minor
number.
LdvType
n/a
Type of logical device. The value is either DISK for
database disk or SDSK for system disk.
CHAR(4)
Secs
n/a
Actual number of seconds in the log period
represented by this row. Normally the same as
NominalSecs, but can be different in three cases:
SMALLINT
• The first interval after a log rate change
• A sample logged late because of load on the
system
• System clock adjustments affect reported Secs
Useful for normalizing the count statistics
contained in this row, for example, to a per-second
measurement.
CentiSecs
n/a
Number of centiseconds in the logging period. This
field is useful when performing data calculations
with small elapsed times where the difference
between centisecond-based data and whole seconds
results in a percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds in the
logging period.
SMALLINT
86
Resource Usage Macros and Tables
Chapter 9: ResUsageSldv Table
Column Name
Type of
Data
SummaryFlag
n/a
Description
Data Type
Identifies the summarization status of this row. If
the value is ‘N,’ the row is a non-summary row. If
the value is ‘S,’ the row is a summary row.
CHAR
Invalid
Platform
In Summary Mode, the rows are summarized into a
single row. For details, see “Summary Mode” on
page 88.
Active
count
Controls whether or not the rows will be logged to
the ResUsage tables if Active Row Filter Mode is
enabled.
FLOAT
If Active is set to:
• A non-zero value, then the row contains
modified data columns.
• A zero value, then none of the data columns in
the row have been updated during the logging
period.
For example, if Active Row Filter Mode is enabled,
then the rows that have a zero Active field value will
not be logged to the ResUsage tables.
CollectIntervals
n/a
Number of gather periods per reporting period.
SMALLINT
In the Collect Buffer and Log Buffer, the value is the
number of Gather operations that have been
performed during the period. This number can
vary from one period to the next.
STATISTICS COLUMNS
LOGICAL DEVICE COLUMNS
Input and Output Traffic Columns
The following columns represent the number and amount, in KBs, of data read and written to the logical device.
LdvReads
count
Number of reads issued.
FLOAT
LdvWrites
count
Number of writes issued.
FLOAT
LdvReadKB
count
The number of KBs (1024) read from the logical
device.
FLOAT
LdvWriteKB
count
The number of KBs (1024) written to the logical
device.
FLOAT
LdvReadRespMax
max
Contains the maximum of the total read response
time in centiseconds. (Note that this is not the
maximum of individual read I/O response times.)
FLOAT
ALL
LdvWriteRespMax
max
Contains the maximum of the total write response
times in centiseconds (Note that this is not the
maximum of individual write I/O response times.)
FLOAT
ALL
Resource Usage Macros and Tables
87
Chapter 9: ResUsageSldv Table
Summary Mode
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
FLOAT
Windows
FLOAT
Windows
Response Time Columns
The following columns represent the response time to requests given to the logical device.
LdvReadRespTot
count
Linux: Total of individual read response times in
centiseconds.
Windows: 0.
LdvWriteRespTot
count
Linux: Total of individual write response times in
centiseconds.
Windows: 0.
ReadActiveTotal
count
Total of read I/O active time in centiseconds.
FLOAT
ALL
WriteActiveTotal
count
Total of write I/O active time in centiseconds.
FLOAT
ALL
Concurrent Operations Columns
The following columns represent the number of concurrent operations performed on the logical device at a time.
LdvConcurrentMax
max
Maximum number of concurrent requests during
the log period. Default value is always 0.
FLOAT
ALL
Note: Do not use this field for any platform.
Outstanding Requests Columns
The following columns represent the number of outstanding operation requests and the amount of time with outstanding
requests for the logical device.
QReadLength
count
Number of read operations in queue.
FLOAT
ALL
QWriteLength
count
Number of write operations in queue.
FLOAT
ALL
LdvOutReqSum
count
Sum of the average of queued requests at each
gather period.
FLOAT
To estimate an average value over the report period,
divide LdvOutReqSum by the CollectIntervals
column. LdvOutReqAvg = LdvOutReqSum /
CollectIntervals.
LdvOutReqMax
max
Maximum value of the LdvOutReqSum field.
FLOAT
LdvOutReqTime
count
Total time in centiseconds with (any) outstanding
requests. The values in this field should be less than
or equal to the reported logging period.
FLOAT
ALL
Summary Mode
When Summary Mode is active for the ResUsageSldv table, the following rows are written to
the database for each node in the system for each log interval:
88
Resource Usage Macros and Tables
Chapter 9: ResUsageSldv Table
Spare Columns
•
One row summarizes the system logical devices
•
One row summarizes Teradata Database logical devices
Also, you can determine if a row is in Summary Mode by checking the SummaryFlag column
for that row.
IF the SummaryFlag column value is…
THEN the data for that row is being logged…
‘S’
in Summary Mode.
‘N’
normally.
Spare Columns
The ResUsageSldv table has nine spare columns (one of which is being used) as shown in the
table below.
Column Name
Type of Data
Description
SpareCount[00-02]
count
Spare counted statistic.
SpareTrack[00-02]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 field contains the COD
value. The value represents the COD value in
one tenths of a percent, so a displayed value of
500 represents a COD value of 50.0%.
Note: This value is valid only on SUSE Linux
Enterprise Server 10 systems and is a single
value for the entire system.
SpareTmon[01-02]
count
Spare time monitored statistic.
The spare column fields expand to values 00-02, so that column names would be
SpareCount00, SpareCount01, SpareCount02, SpareTrack00, and so on.
Resource Usage Macros and Tables
89
Chapter 9: ResUsageSldv Table
Spare Columns
90
Resource Usage Macros and Tables
CHAPTER 10
ResUsageSpdsk Table
The ResUsageSpdsk table:
•
Provides pdisk level statistics.
•
Includes resource usage logs on cylinder I/O, allocation, and migration.
Note: This table is created as a MULTISET table. For more information see “Relational
Primary Index” on page 38.
The following table describes the ResUsageSpdsk table columns.
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system
load, entries may be logged late (typically, by
no more than one or two seconds), but this
field will still contain the time value when the
entry should have been logged. See the Secs
and NominalSecs columns.
NodeId
n/a
Identifies the Node upon which the pdisk is
connected. The Node ID is formatted as
CCC-MM, where CCC denotes the threedigit cabinet number and MM denotes the
two-digit chassis number of the node. For
example, a node in chassis 9 of cabinet 3 has
a node ID of ‘003-09’.
INTEGER
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an
SMP node is ‘001-01’.
MISCELLANEOUS HOUSEKEEPING COLUMNS
GmtTime
Resource Usage Macros and Tables
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that
occur twice a year.
FLOAT
91
Chapter 10: ResUsageSpdsk Table
Column Name
Type of
Data
PdiskGlobalId
n/a
Description
Data Type
Identifies the pdisk in the system. Each pdisk
in the system has a global ID which uniquely
identifies the pdisk in the system. If a pdisk is
connected to the nodes in a clique, all the
nodes in that clique see the same pdisk
global ID associated with that pdisk.
INTEGER
Invalid
Platform
In Summary Mode, the pdisk global ID is -1.
PdiskType
n/a
Type of pdisk. The pdisk can be one of the
following:
CHAR(4)
• DISK: This type of pdisk is a storage
device.
• FILE: This type of pdisk is a file.
PdiskDeviceId
n/a
Identifies the local pdisk device.
BYTE(4)
For DISK pdisk, the pdisk device ID can be
one of the following:
• Linux: This is the pdisk major/minor
number. The major number bit positions
are 20-31 and the minor number is in bits
0-19. The format is similar to the one
shown below.
(MMMM MMMM MMMM mmmm mmmm
mmmm mmmm mmmm)
• Windows: This is the pdisk physical disk/
partition number. The physical disk
number is in the lower 16 bits and the
partition number is in the upper 16 bits.
The format is similar to the one shown
below.
(0000 0000 0000 PPPP DDDD
DDDD DDDD DDDD)
For FILE pdisk, the pdisk device ID is -1.
In Summary Mode, the pdisk device ID is -1.
NodeType
92
n/a
Type of node, representing the per node
system family type. For example, 5600C or
5555H.
CHAR(8)
Resource Usage Macros and Tables
Chapter 10: ResUsageSpdsk Table
Column Name
Type of
Data
Secs
n/a
Description
Data Type
Actual number of seconds in the log period
represented by this row. Normally the same
as NominalSecs, but can be different in three
cases:
SMALLINT
Invalid
Platform
• The first interval after a log rate change
• A sample logged late because of load on
the system
• System clock adjustments affect reported
Secs
Useful for normalizing the count statistics
contained in this row, for example, to a persecond measurement.
CentiSecs
n/a
Number of centiseconds in the logging
period. This field is useful when performing
data calculations with small elapsed times
where the difference between centisecondbased data and whole seconds results in a
percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds in
the logging period.
SMALLINT
SummaryFlag
n/a
Identifies the summarization status of this
row. If the value is ‘N,’ the row is a nonsummary row. If the value is ‘S,’ the row is a
summary row.
CHAR
In Summary Mode, the rows are summarized
into a single row per pdisk type per node. For
details, see “Summary Mode” on page 97.
Active
count
Controls whether or not the rows will be
logged to the ResUsage tables if Active Row
Filter Mode is enabled.
FLOAT
If Active is set to:
• a non-zero value, then the row contains
modified data columns.
• a zero value, then none of the data
columns in the row have been updated
during the logging period.
For example, if Active Row Filter Mode is
enabled, then the rows that have a zero Active
field value will not be logged to the ResUsage
tables.
Resource Usage Macros and Tables
93
Chapter 10: ResUsageSpdsk Table
Column Name
Type of
Data
CollectIntervals
n/a
Description
Data Type
The number of gather periods per reporting
period.
SMALLINT
Invalid
Platform
In the Collect Buffer and Log Buffer, the
value is the number of Gather operations
that have been performed during the period.
This number can vary from one period to the
next.
STATISTICS COLUMNS
I/O Statistics Columns
These columns identify the I/O statistics reported by the Extent Driver.
ReadCnt
count
Number of logical device reads.
FLOAT
WriteCnt
count
Number of logical device writes.
FLOAT
ReadKB
count
Number of KBs (1024 bytes) read from the
logical device.
FLOAT
WriteKB
count
Number of KBs (1024 bytes) written to the
logical device.
FLOAT
ReadRespTot
count
Total of individual read response time in
centiseconds.
FLOAT
WriteRespTot
count
Total of individual write response time in
centiseconds.
FLOAT
ReadRespMax
max
Maximum number of individual read
response time in centiseconds.
FLOAT
WriteRespMax
max
Maximum number of individual write
response time in centiseconds.
FLOAT
ReadRespSq
count
Total of squares of the individual read
response time in centiseconds.
FLOAT
WriteRespSq
count
Total of squares of the individual write
response time in centiseconds.
FLOAT
ConcurrentReadMax
max
Maximum number of concurrent read I/O
requests.
FLOAT
ConcurrentWriteMax
max
Maximum number of concurrent write I/O
requests.
FLOAT
ConcurrentMax
count
Maximum number of concurrent I/O
requests.
FLOAT
OutReqTime
count
Time with outstanding requests (busy time),
in centiseconds.
FLOAT
94
ALL
Resource Usage Macros and Tables
Chapter 10: ResUsageSpdsk Table
Column Name
Type of
Data
MigrationBlockedIos
count
Description
Data Type
Number of inputs and outputs that are
blocked due to migration request.
FLOAT
Invalid
Platform
Allocation Columns
These columns identify the allocation statistics reported by the Allocator process of the VSS vproc.
Note: These columns are populated and used by Teradata VS, an option sold separately from Teradata Database.
For detail s about these columns, see Teradata Virtual Storage.
Migration Columns
The following columns identify the number of cylinders that migrated to a different location on a device as well as the time,
in centiseconds, of all migration I/Os used, incurred, or saved during the log period.
Note: Each allocation is for a cylinder size worth of data, also known internally in the allocator as an extent. Thus the
column names begin with Ext for extent.
ExtMigrateFaster
count
Number of cylinders migrated to a faster
location on a device. This count is for
cylinders that were allocated on this device
and migrated to a different location within
the same device or migrated to a completely
different device.
FLOAT
The following formula calculates a
ExtMigrateSlower value, which is the
number of cylinders migrated to slower
locations: Migrate Slower = ExMigrateTotal ExMigrateFaster.
ExtMigrateTotal
count
Total number of cylinders migrated to a
different physical location. For more
information, see the ExtMigrateFaster field.
FLOAT
ExtMigrateReadRespTot
count
Migration read I/O response time.
FLOAT
ExtMigrateWriteRespTot
count
Migration write I/O response time.
FLOAT
ExtMigrateIOTimeCost
count
Estimates the total cost (in centiseconds)
incurred by migration I/Os completing
during the log period, where cost is the extra
time waited by all non-migration I/Os as a
result of the migration I/O. The Migrator
estimates migration costs.
FLOAT
Note: This field is for internal use only. Do
not use this field unless directed by Teradata
Support Center.
Resource Usage Macros and Tables
95
Chapter 10: ResUsageSpdsk Table
Column Name
Type of
Data
ExtMigrateIOTimeBenefit
count
Description
Data Type
Estimates the total I/O time savings achieved
by migrations completing in the log period.
The I/O time savings include the
improvement in response time caused by the
new data arrangement up to the time
horizon. ExtMigrateIOTimeBenefit does not
include the cost of the migration I/Os and is
a gross benefit, not a net benefit. The
Migrator estimates the migration benefit.
FLOAT
Invalid
Platform
Note: This field is for internal use only. Do
not use this field unless directed by Teradata
Support Center.
ExtMigrateIOTimeImprove
count
Estimates the percent improvement in
average I/O response time due to migrations
completing in the log interval. In theory, this
percentage improvement is permanent. For
example, if, right before a particular log
interval, the average I/O response time was
10 milliseconds (ms), then the Migration
logs an ExtMigrateIOTimeImprove value of
10% in this interval. The average IO response
time after the log interval should be (100%10%)*10ms = 9ms. Migration then logs an
ExtMigrateIOTimeImprove of 1% in the next
interval. The average I/O response time in
the new log interval is (100%-1%)*9ms =
8.91ms.
FLOAT
ExtMigrateIOTimeImprove is only an
estimate. Its permanent improvement
remains in effect as long as the workload
does not change and newer migrations do
not significantly alter the data arrangement.
When the workload changes or new
migrations affect data arrangement, response
time changes in an un-quantified way.
Despite this, ExtMigrateIOTimeImprove is
useful because it predicts actual system
performance at least for short periods of time
and can be used to understand why the
migration algorithm is doing what it is
doing.
Note: This field is for internal use only. Do
not use this field unless directed by Teradata
Support Center.
96
Resource Usage Macros and Tables
Chapter 10: ResUsageSpdsk Table
Summary Mode
Summary Mode
When Summary Mode is active for the ResUsageSpdsk table, rows are summarized into a
single row for each pdisk type (for example, DISK or FILE) for each node in the system per log
interval.
You can determine if a row is in Summary Mode by checking the SummaryFlag column for
that row.
IF the SummaryFlag column value is…
THEN the data for that row is being logged…
‘S’
in Summary Mode.
‘N’
normally.
Spare Columns
The ResUsageSpdsk table has 30 spare columns (one of which is being used) as shown in the
table below.
Column Name
Type of Data
Description
SpareCount[00-09]
count
Spare counted statistic.
SpareTrack[00-09]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 field contains the COD
value. The value represents the COD value in
one tenths of a percent, so a displayed value of
500 represents a COD value of 50.0%.
Note: This value is valid only on SUSE Linux
Enterprise Server 10 systems and is a single
value for the entire system.
SpareTmon[01-09]
count
Spare time monitored statistic.
The spare column fields expand to values 00–09, so that column names would be
SpareCount00, SpareTrack02, SpareTmon05 and so on.
Resource Usage Macros and Tables
97
Chapter 10: ResUsageSpdsk Table
Spare Columns
98
Resource Usage Macros and Tables
CHAPTER 11
ResUsageSps Table
The ResUsageSps table contains data by Performance Group from the Priority Scheduler. It
allows you to see accumulated CPU, number of active processes, and other detail by Priority
Scheduler Allocation Group. The ResUsageSps table carries information that is similar to what
is displayed in Priority Scheduler monitor output.
Information carried in the table is organized by:
•
Collection date/time
•
Node
•
Vproc Type
•
Performance Group
•
Performance Period/Allocation Group
For those using Teradata ASM, each Workload Definition is the equivalent of one
Performance Group in ResUsageSps.
For a complete description of the Priority Scheduler and its components, see "Priority
Scheduler (schmon)" chapter in Utilities.
If table logging is enabled on ResUsageSps, a row is written to the database once for every
triplet of Vproc Type, Performance Group ID, and Performance Period ID (VprType, PGId,
PPId) in the system for each log interval.
Note: This table is created as a MULTISET table.
The following table describes the ResUsageSps table columns.
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system
load, entries may be logged late (typically, by
no more than one or two seconds), but this
column will still contain the time value
when the entry should have been logged. See
the Secs and NominalSecs columns.
Resource Usage Macros and Tables
99
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
NodeId
n/a
Description
Data Type
Identifies the Node upon which the vproc
resides. The Node ID is formatted as CCCMM, where CCC denotes the three-digit
cabinet number and MM denotes the twodigit chassis number of the node. For
example, a node in chassis 9 of cabinet 3 has
a node ID of ‘003-09’.
INTEGER
Invalid
Platform
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an
SMP node is ‘001-01’.
MISCELLANEOUS HOUSEKEEPING COLUMNS
GmtTime
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that
occur twice a year.
FLOAT
NodeType
n/a
Type of node, representing the per node
system family type. For example, 5600C or
5555H.
CHAR(8)
VprId
n/a
Note: This column is obsolete.
INTEGER
Identifies the vproc number. Multiple
Vprocs contribute to each Performance
Group task.
The VprId value is -1.
PPId
n/a
Identifies the performance period. The PPId
is a mapping of the internal performance
period value (ranges 0 to 7) to a RSS value
(ranges 0 to 1). A PPId of 0 maps to the
value 0, and the PPId of 1 maps to the values
1 through 7.
BYTEINT
The PPId column allows RSS to log two
rows for each node, VprType, and PGId set
when a PGId uses more than one AGId
during a logging period. See the AGId
column for more information.
VprType
100
n/a
Type of vproc (for example, AMP, PE, and
MISC).
CHAR(4)
Resource Usage Macros and Tables
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
PGId
n/a
Description
Data Type
Identifies the Performance Group. There is a
one to one mapping between a Performance
Group ID and a Workload Definition ID at
any point in time. The Performance Group
ID value ranges from 0 to 250, while the
value of a Workload Definition ID is not in a
specific range (that is, the value is
incremented and not reused).
SMALLINT
Invalid
Platform
The mapping between Performance Group
ID and Workload Definition ID can be
determined by looking at the Teradata
Viewpoint Workload Designer portlet or the
TDWM.WlcPerfGroupMappings table.
WDId
track
Workload Definition ID number.
FLOAT
0 indicates there is no WDId associated with
the PG.
Use this column to obtain the WD name
from the WLcdefs table of the Teradata
Dynamic Workload Management database
by joining ResUsageSps.WDId with
WLcdefs.WlcId. The resulting join table
outputs the WD name from
WLcdefs.WlcName field.
Secs
n/a
Actual number of seconds in the log period
represented by this row. Normally the same
as NominalSecs, but can be different in three
cases:
SMALLINT
• The first interval after a log rate change
• A sample logged late because of load on
the system
• System clock adjustments affect reported
Secs
Useful for normalizing the count statistics
contained in this row, for example, to a persecond measurement.
CentiSecs
n/a
Number of centiseconds in the logging
period. This column is useful when
performing data calculations with small
elapsed times where the difference between
centisecond-based data and whole seconds
results in a percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds
in the logging period.
SMALLINT
Resource Usage Macros and Tables
101
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
Description
Data Type
NCPUs
n/a
Number of CPUs on this node.
SMALLINT
Invalid
Platform
This column is useful for normalizing the
CPU utilization column values for the
number of CPUs on the node. This is
especially important in coexistence systems
where the number of CPUs can vary across
system nodes.
SummaryFlag
n/a
Identifies the summarization status of this
row. If the value is ‘N,’ the row is a nonsummary row. If the value is ‘S,’ the row is a
summary row.
CHAR
Active
count
Controls whether or not the Performance
Group ID rows will be logged to the
ResUsage tables when Active Row Filter
Mode is enabled.
FLOAT
If Active is set to:
• A non-zero value, then the Performance
Group ID row contains modified data
columns.
• A zero value, then none of the data
columns in the Performance Group ID
row have been updated during the
logging period.
CollectIntervals
n/a
The number of gather periods per reporting
period.
SMALLINT
In the Collect Buffer and Log Buffer, the
value is the number of Gather operations
that have been performed during the period.
This number can vary from one period to
the next.
102
Resource Usage Macros and Tables
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
STATISTICS COLUMNS
TERADATA ASM COLUMNS
Priority Scheduler Columns
The following columns provide a summary of the Priority Scheduler resource usage statistics.
AGId
track
Identifies the current Allocation Group for
the Performance Group ID that is being
reported. This value can be any number
from 0 to 200.
FLOAT
Note: A value of 200 is the system
Allocation Group. This value cannot be
assigned for user work.
For more information on the Allocation
Group (AG), see "Priority Scheduler
(schmon)" chapter in Utilities.
RelWgt
track
Weight of the Allocation Group relative to
the active Allocation Groups of the Resource
Partition and the active Resource Partitions.
FLOAT
Note: Allocation Groups with higher
relative weights will have quicker access to
system resources. For more information on
allocation group weights, see the "Priority
Scheduler (schmon)" chapter in Utilities.
CPUTime
count
Milliseconds of CPU time consumed by all
tasks that have the same VprType, PGId, and
PPId values for a reporting period.
FLOAT
IOBlks
count
Number of logical data blocks read or
written by Performance Group, or both.
FLOAT
NumProcs
track
Number of tasks assigned to the
Performance Group at the end of the gather
period.
FLOAT
NumSets
track
Number of Scheduling Sets per PG/PPid
combination. There is one Scheduling Set
per session.
FLOAT
NumRequests
count
Number of AWT messages/requests that got
assigned AWTs to them on the node.
FLOAT
Resource Usage Macros and Tables
103
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
QWaitTime
count
Description
Data Type
Total time for all messages delivered in the
period (if not delivered then not counted).
FLOAT
Invalid
Platform
Divide by NumRequests to obtain the
average QwaitTime per Request.
This column is reported in
DBC.ResSpsView as
QWaitTimeRequestAvg.
QWaitTimeMax
max
Maximum time in milliseconds that work
requests waited on an input queue before
being serviced.
FLOAT
QLength
count
Sum of the average number of work requests
waiting on the input queue for service.
FLOAT
This value is derived each gather period
from QWaitTime by dividing by the sample
period and rounding the value. The values
from each gather period are then summed
together.
To use this column, always divide QLength
by the AMPcount to get the desired average
Qlength per AMP.
The Average number of work requests
waiting on the input queue for service =
QLength /(CollectIntervals * SpareTrack00).
QLengthMax
max
Maximum number of work requests waiting
on the input queue for service.
FLOAT
This value is derived by dividing the number
of AMPs to display the maximum per AMP
average number of work requests waiting on
the input queue for service = QLengthMax /
SpareTrack00.
ServiceTime
count
FLOAT
Time in milliseconds that work requests
required for service.
To calculate an approximate average
ServiceTime for each request during this
period, divide ServiceTime by
NumRequests.
The service time is the elapsed time from the
time the message was received to the time
the AWT was released. This is the amount of
time the AWT was held through sleeps,
CPU, I/O, and so on until it is released.
ServiceTimeMax
104
max
Maximum time in milliseconds that work
requests required for service.
FLOAT
Resource Usage Macros and Tables
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
PROCESS SCHEDULING COLUMNS
CPU Utilization Columns
The following columns represent CPU activities on the node associated with the AWT, Dispatcher, Parser, or miscellaneous
things.
CPUUServAWT
count
Time in milliseconds CPUs are busy in the
AWT executing user service code. This is the
system level time spent on a process.
FLOAT
CPUUServDisp
count
Time in milliseconds CPUs are busy in the
Dispatcher or Parser executing user service
code. This is the system level time spent on a
process.
FLOAT
CPUUServPars
count
Time in milliseconds CPUs are busy in the
Parser executing user service code. This is
the system level time spent on a process.
FLOAT
CPUUServMisc
count
Time in milliseconds CPUs are busy
executing miscellaneous activities for user
service code. This is the system level time
spent on a process.
FLOAT
CPUUExecAWT
count
Time in milliseconds CPUs are busy in the
AWT executing user execution code. This is
the user level time spent on a process.
FLOAT
CPUUExecDisp
count
Time in milliseconds CPUs are busy in the
Dispatcher or Parser executing user
execution code. This is the user level time
spent on a process.
FLOAT
CPUUExecPars
count
Time in milliseconds CPUs are busy in the
Parser executing user execution code. This is
the user level time spent on a process.
FLOAT
CPUUExecMisc
count
Time in milliseconds CPUs are busy
executing miscellaneous activities for user
execution code. This is the user level time
spent on a process.
FLOAT
ALL
ALL
FILE SYSTEM COLUMNS
Cylinder Read Columns
The following columns represent file system resource usage statistics. The Cylinder Read feature uses these statistics for
tracking performance and utilization.
Resource Usage Macros and Tables
105
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
FileFcrRequests
count
Description
Data Type
Invalid
Platform
Total number of requests for the File System
to use Cylinder Read.
FLOAT
ALL
FLOAT
ALL
FLOAT
ALL
This column is tracked and recorded by the
File System. It records the number of
attempts to use Cylinder Read independent
of whether the request will be issued to FSG
or not. A request can be denied due to
insufficient data blocks or because there is
insufficient space in the FSG cache. Requests
can also be denied at both the user and
kernel level. Each of these items is counted
in other FileFcr ResUsage columns.
A number of calculations can be performed
using this column:
• Requests issued to FSG =
FileFcrRequests - FileFcrDeniedUser
• Successful Cylinder Reads =
FileFcrRequests - FileFcrDeniedUser FileFcrDeniedKern
FileFcrRequestsAdaptive
count
Number of adaptive requests from File
System.
This column is tracked and recorded by the
File System. It records the number of
requests for adaptive-style Cylinder Reads.
FileFcrBlocksRead
count
Number of data blocks read in using
Cylinder Read.
This column is tracked and recorded by the
FSG subsystem. It records the total number
of data blocks read in by successful Cylinder
Read operations.
The average number of data blocks in a
successful Cylinder read can be calculated
as:
Average data blocks/ Cylinder Read =
FileFcrBlocksRead / (FileFcrRequests FileFcrDeniedUser - FileFcrDeniedKern)
106
Resource Usage Macros and Tables
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
FileFcrBlocksDeniedUser
count
Description
Data Type
Invalid
Platform
Number of data blocks in the Cylinder Read
requests denied by the File System.
FLOAT
ALL
FLOAT
ALL
FLOAT
ALL
This column is tracked and recorded by the
File System. It records the number of
Cylinder Read attempts that have been
denied by the File System. A request can be
denied by the File System due to insufficient
number of data blocks being requested (for
example, the FileFcrDeniedThreshUser
column). For information, see the
FileFcrDeniedThreshUser column.
FileFcrBlocksDeniedKern
count
Number of data blocks in the Cylinder Read
requests denied by the FSG subsystem.
This column is tracked and recorded by the
FSG subsystem. It records the number of
Cylinder Read requests issued to the FSG
subsystem which, for any reason, have been
denied. A request can be denied due to
insufficient data blocks (for example, the
FileFcrDeniedThreshKern column) or
because there is insufficient space in the FSG
cache (for example, the FileFcrDeniedCache
column). The FSG subsystem can reject a
request containing insufficient data blocks
that the File System thought had enough
blocks because the FSG subsystem reduces
the count by the number of data blocks that
are already resident in the cache.
FileFcrBlocksDeniedCache
count
Number of data blocks in the Cylinder Read
requests rejected by the FSG subsystem due
to insufficient cache.
This column is tracked and recorded by the
FSG subsystem. It records the number of
data blocks that were part of attempts to use
Cylinder read that were denied by the FSG
subsystem due to insufficient cache space;
therefore, also incremented the
FileFcrDeniedCache column.
Resource Usage Macros and Tables
107
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
FileFcrBlocksDeniedThreshUser
count
Description
Data Type
Invalid
Platform
Number of data blocks in the Cylinder Read
requests denied by the File System due to
insufficient data blocks.
FLOAT
ALL
FLOAT
ALL
FLOAT
ALL
This column is tracked and recorded by the
File System. It records the number of
Cylinder Read requests which have been
denied due to the data block threshold
criteria. There is a minimum threshold of
data blocks for an individual Cylinder Read
request. If the number of data blocks is
below this threshold, the overhead of the
Cylinder Read operation is considered too
large and issuing individual data block reads
is considered more efficient. Therefore, the
Cylinder Read request is denied.
FileFcrDeniedUser
count
Number of Cylinder Read requests denied
by the File System.
This column is tracked and recorded by the
File System. It records the number of
Cylinder Read attempts that have been
denied by the File System. A request can be
denied by the File System due to insufficient
number of data blocks being requested (for
example, the FileFcrDeniedThreshUser
column). For information, see the
FileFcrDeniedThreshUser column
description.
FileFcrDeniedKern
count
Number of Cylinder Read requests denied
by the FSG subsystem.
This column is tracked and recorded by the
FSG subsystem. It records the number of
Cylinder Read requests issued to the FSG
subsystem which, for any reason, have been
denied. A request can be denied due to
insufficient data blocks (for example, the
FileFcrDeniedThreshKern column) or
because there is insufficient space in the FSG
cache (for example, the FileFcrDeniedCache
column). The FSG subsystem can reject a
request containing insufficient data blocks
that the File System thought had enough
blocks because the FSG subsystem reduces
the count by the number of data blocks that
are already resident in the cache.
108
Resource Usage Macros and Tables
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
FileFcrDeniedCache
count
Description
Data Type
Invalid
Platform
Number of Cylinder Read requests denied
by FSG due to insufficient cache.
FLOAT
ALL
FLOAT
ALL
This column is tracked and recorded by
FSG. It records the number of Cylinder Read
requests which have been denied due to
insufficient FSG cache space for a cylinders
worth of data.
FileFcrDeniedThreshUser
count
Number of Cylinder Read requests denied
by the File System due to insufficient data
blocks.
This column is tracked and recorded by the
File System. It records the number of
Cylinder Read requests which have been
denied due to the data block threshold
criteria. There is a minimum threshold of
data blocks for an individual Cylinder Read
request. If the number of data blocks is
below this threshold, the overhead of the
Cylinder Read operation is considered too
large and issuing individual data block reads
is considered more efficient. Therefore, the
Cylinder Read request is denied.
Segment Acquires Columns
The following columns identify the total disk memory segments acquired by the file system during the log period. Logical
acquires (Acqs) and the logical amount acquired (AcqKB) are described by single entries below, each of which expands into
six actual columns, where [seg] is replaced as follows:
PDb = Permanent data block disk segments
PCi = Permanent cylinder index disk segments
SDb = Regular or restartable spool data block disk segments
SCi = Regular or restartable spool index disk segments
Tjt = Transient journal table
APt = Append table or permanent journal table data block or cylinder index disk segments
File[seg]Acqs
count
Total number of disk segments acquired.
FLOAT
File[seg]AcqKB
count
Total KBs acquired by File[seg]Acqs.
FLOAT
File[seg]AcqReads
count
Number of disk segment acquires that
caused a physical read.
FLOAT
File[seg]AcqReadKB
count
KBs physically read by File[seg]AcqReads.
FLOAT
Resource Usage Macros and Tables
109
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Data Block Prefetches Columns
The following columns identify File Segment Prefetch activities. File segments prefetches are described by single entries
below, each of which expands into six actual columns, where [seg] is replaced as follows:
PDb = Permanent data block disk segments
PCi = Permanent cylinder index disk segments
SDb = Regular or restartable spool data block disk segments
SCi = Regular or restartable spool index disk segments
Tjt = Transient journal table
APt = Append table or permanent journal table data block or cylinder index disk segments
File[seg]Pres
count
Total number of disk segments prefetched.
FLOAT
File[seg]PresKB
count
Total number of KBs prefetched by
File[seg]Pres.
FLOAT
File[seg]PreReads
count
Total number of disk segment prefetches
that caused a physical read.
FLOAT
File[seg]PreReadKB
count
Total number of KBs physically read by
File[seg]PreReads.
FLOAT
Segments Released Columns
The following columns identify the total disk memory segments released by the file system, as well as those segments that are
dropped from memory during the log period. When a segment is release, the segment is either:
Force out of memory (F)
Remains resident in memory (R)
Aged out of memory (A), from segments that remain resident
Both the number of segments (Rels, Writes, Drps) and the size of the segments (RelKB, WriteKB, DrpKB) are counted.
When a segment leaves memory, it must be written to disk only if the segment is dirty, that is, modified (Dy). Otherwise, the
clean or unmodified (Cn) segment is simply dropped.
(Most spool blocks are simply dropped from a task and put on the age queue. This may happen multiple times. Each of these
will be counted as a resident release. If the system is low on memory and the age queue must be processed, this may also
result in an age write or age drop. Forced writes are always also counted as either clean resident releases or forced drops,
depending on whether age normal or age out now was specified.)
Disk segment memory types are described by single entries below, each of which expands into six actual columns, where
[seg] is replaced as follows:
•
•
•
•
•
•
PDb = Permanent data block disk segments
PCi = Permanent cylinder index disk segments
SDb = Regular or restartable spool data block disk segments
SCi = Regular or restartable spool cylinder index disk segments
TJt = Transient journal table or WAL data block or WAL cylinder index
APt = Append table or permanent journal table data block or cylinder index disk segments
File[seg]DyRRels
110
count
Number of dirty disk segment resident
releases.
FLOAT
Resource Usage Macros and Tables
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
Description
Data Type
File[seg]DyRRelKB
count
KBs released by File[seg]DyRRels.
FLOAT
File[seg]FWrites
count
Number of disk segment forced releases or
specific I/O requests causing an immediate
physical write. Includes spool data that is
aged out immediately and permanent data
that is written immediately.
FLOAT
File[seg]FWriteKB
count
KBs written by File[seg]FWrites.
FLOAT
Invalid
Platform
Cylinder Management Overhead Events Columns
The following columns identify the number of times the file system software performed a cylinder management event. The
table ResUsageIvpr further breaks down the I/Os associated with these events. See Appendix C: “ResUsageIvpr Table.”
FileCylMigrs
count
Number of cylinder migrations.
FLOAT
ALL
FileCylAllocs
count
Number of new cylinders allocated.
FLOAT
ALL
Note: A new cylinder allocation event
implies one logical cylinder index read and
one logical cylinder index write.
Synchronized Full File Scans Columns
The following columns contain statistics relating to synchronized full-file scans.
FileSyncScans
count
Number of attempts to synchronize a full
file scan.
FLOAT
ALL
FileSyncSubtables
track
Number of subtables scanned by one or
more full file scanners who are willing to
synchronize scans.
FLOAT
ALL
FileSyncScanners
track
Number of tasks involved in full file scans
who are willing to synchronize with other
scanners.
FLOAT
ALL
FileSyncGroups
track
Number of groups of scanners involved in
full file scans. A group consists of scanners
who are able to use the same read I/O to
obtain data from disk.
FLOAT
ALL
ChnSignal Status Tracking columns
The following columns track the chnsignal last done status (or track slowest vproc on the system for processing AMP steps).
MsgChnLastDone
count
The number of last done events that
occurred for this vproc.
FLOAT
ALL
Note: The last AMP to finish an operation
may send a last done broadcast message
indicating the work is done for this step.
This is used in tracking down the slowest
AMP in the system. An AMP that has more
last done messages than the others could be
a bottleneck in the system performance.
Resource Usage Macros and Tables
111
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Memory Allocation Columns
The following columns represent the number and amount of memory allocations, subdivided into (the only applicable)
generic node memory type.
MemAllocs
count
Number of successful SEG memory
allocations.
FLOAT
MemAllocKB
count
Total KBs attributed to SEG memory
allocations.
FLOAT
MemCtxtAllocs
count
Number of successful SWAP memory
allocations.
FLOAT
ALL
FLOAT
ALL
Note: Only scratch pages are allocated.
MemKBRes
count
The amount of memory resident that is
specific to virtual processor activities.
Amp Worker Task Columns
The following columns collect and report statistics about the AWTs. For more information about the ResUsageSawt table
and columns, see Chapter 7: “ResUsageSawt Table.”
Note: The system writes the data to the database once for every triplet of Vproc Type, Performance Group ID, and
Performance Period ID (VprType, PGId, PPId).
The data is reporting the contribution of the respective WD to the column and the values are not the same as the values
reported in the ResUsageSawt table. The ResUsageSps table values should add up to the ResUsageSawt table for columns like
WorkTypeInuse. The Max columns will not be able to be correlated to the ResUsageSawt table Max values in such a direct
way since the ResUsageSps Max columns report the Max value of the ResUsageSps table InUse column for the WD and not
the Max value of the ResUsageSawt table for all the WDs combined.
FlowControlled
count
Number of times this log period that system
entered the flow control state from a
nonflow controlled state.
FLOAT
ALL
FlowCtlCnt
count
Number of AWTs currently in flow control
on the work input mailbox.
FLOAT
ALL
WorkTypeInuse00 WorkTypeInuse15
count
Current number of AWTs in use during the
log period for each work type for the WD
(PGid/VprType/PPid triplet).
FLOAT
112
Resource Usage Macros and Tables
Chapter 11: ResUsageSps Table
Column Name
WorkTypeMax00 WorkTypeMax15
Type of
Data
max
Description
Data Type
The value reported is the maximum of the
WorkTypeInuse values seen at the end of
each gather period during the reporting
period. If only a single gather period occurs
during the reporting period, the
WorkTypeMax and WorkTypeInUse
columns would report the same value.
When multiple gather periods occur during
the reporting period the value is the
maximum of the sampled values.
FLOAT
Invalid
Platform
This is therefore a maximum sampled value.
The true maximum number of inuse AWTs
of a WorkType may occur at a different time
during the reporting period and not be seen
at the end of the gather period and therefore
not be reported.
Maximum number of AWTs in use at one
time during the log period for each work
type for the WD (PGid/VprType/PPid
triplet).
NET COLUMNS
Point-to-Point Net Traffic Columns
The following columns identify the number (Reads, Writes) and amount (ReadKB, WriteKB) of input and output messages
passing through either Teradata Database net through point-to-point (1:1) methods (PtP).
Note: The system writes the data to the database once for every triplet of Vproc Type, Performance Group ID, and
Performance Period ID (VprType, PGId, PPId).
NetPtPReads
count
Number of point-to-point messages input
to the vproc on behalf of the WD.
FLOAT
NetPtPWrites
count
Number of point-to-point messages output
from the vproc on behalf of the WD.
FLOAT
NetPtPReadKB
count
Total KBs of point-to-point messages input
to the vproc on behalf of the WD.
FLOAT
NetPtPWriteKB
count
Total KBs of point-to-point messages output
to the vproc on behalf of the WD.
FLOAT
Broadcast Net Traffic Columns
The following columns identify the number (Reads, Writes) and amount (ReadKB, WriteKB) of input and output messages
passing through the Teradata Database nets through broadcast (1:many) methods (Brd) per net.
NetBrdReads
count
Number of broadcast messages input to the
vproc.
FLOAT
NetBrdWrites
count
Number of broadcast messages output from
the vproc.
FLOAT
Resource Usage Macros and Tables
113
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Allocator Columns
The following columns identify the number of requests or I/Os from the Allocator.
AllocatorExtentAllocReqs
count
Number of cylinder allocation requests
received by the allocator.
FLOAT
ALL
AllocatorExtentFreeReqs
count
Number of cylinder free requests received by
the allocator.
FLOAT
ALL
AllocatorMapIOsStarted
count
Number of map I/Os initiated by the
allocator.
FLOAT
ALL
AllocatorMapIOsDone
count
Number of map I/Os completed by the
allocator.
FLOAT
ALL
Node Agent Columns
The following columns identify the migration and buffer processing statistics reported by the Node Agent.
NodeAgentMigrationsStarted
count
Number of migration requests started by the
Node Agent.
FLOAT
ALL
NodeAgentMigrationsDone
count
Number of migration requests completed by
the Node Agent.
FLOAT
ALL
NodeAgentStatProcessed
count
Number of statistics buffers processed by the
Node Agent.
FLOAT
ALL
I/O Columns
These columns identify the I/O statistics reported from the extent driver.
Note: These columns are populated and used by Teradata VS, an option sold separately from Teradata Database. Associated
configuration settings appear in the ctl utility if you purchased Teradata Virtual Storage.
For details about these columns, see Teradata Virtual Storage.
Write Ahead Logging Columns
The following columns identify the log-based file system recovery scheme in which modifications to permanent data are
written to a log file, the WAL log.
FileWCylAllocs
count
Number of new WAL cylinders allocated.
FLOAT
ALL
FileWCylFrees
count
Number of times the file system logically
frees a cylinder.
FLOAT
ALL
114
Resource Usage Macros and Tables
Chapter 11: ResUsageSps Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Process Blocking and Waiting Columns
The following columns count of blocks and wait time in milliseconds where [reason] is replaced with one of the following:
•
•
•
•
•
•
•
•
•
•
•
SegNoVirtual
FsgNIOs
SegMDL
MonResume
NetThrottle
Qnl
FsgRead
FsgWrite
DBLock
Monitor
SegLock
• FsgLock
• Time
• FlowControla
• CpuLimitb
• Misc
For example, columns can appear as ProcBlksSegNoVirtual, ProcBlksMisc, ProcWaitSegNoVirtual, and so on.
The following column definition descriptions can be found in the ResUsageSpma table descriptions of the same names
except where noted.
ProcBlks[reason]
count
Number of times processes were blocked.
FLOAT
Note: ProcBlksDBLock is invalid on all
platforms.
ProcWait[reason]
count
Total time processes were blocked pending.
FLOAT
Note: ProcWaitDBLock is invalid on all
platforms.
a. FlowControl refers to the delays caused by the flow control conditions.
b. CpuLimit refers to delays due to the Priority Scheduler CPU Limits (System Limit, AG Limit, or RP Limit).
Resource Usage Macros and Tables
115
Chapter 11: ResUsageSps Table
Spare Columns
Spare Columns
The ResUsageSps table has 30 spare columns (several of which are being used) as shown in the
table below.
Column Name
Type of Data
Description
SpareCount[00-05]
count
The following SpareCount columns will be converted to
the specified column names in Teradata Database 14.0:
• SpareCount00 = WorkMsgSendDelay. This column
reports the total time in milliseconds for all messages
delivered in a period (if the messages are not sent yet,
then they are not counted).
• SpareCount01 = WorkMsgSendDelayMax. This
column reports the longest time in milliseconds seen
or still waiting at sample time (if the messages are not
sent yet, then they are not counted).
• SpareCount02 = WorkMsgReceiveDelay. This
column reports the time for all messages not yet
delivered at the end of each gather period. This
column is related to the QWaitTime column and
represents a running total of delays attributed to the
tasks that still have not been assigned an AWT within
this interval. When the task does receive an AWT in a
later interval, the time attributed here will be
counted again within QWaitTime of the interval
where it was assigned an AWT.
• SpareCount03 = WorkMsgReceiveDelayMax. This
column reports the maximum delay time in
milliseconds for messages that are still in the work
box.
• SpareCount04 = WorkTimeInuse. This column
reports service time consumed by a WD during the
current reporting interval. It can be used to calculate
the average usage of AWTs during the reporting
period, for example:
Average AWTs used = WorkTimeInuse/
(Centisecs*10)
This value is available in the ResSpsView as
AwtUsedAvg.
Note: WorkTimeInUse is not the running sum of a
WD that exists over multiple intervals.
• SpareCount05 = WorkTimeInuseMax. This column
reports the maximum service time of a single task in
a WD that is still running or has finished in the
current reporting interval. This includes time used
during previous intervals for that task.
If you use the spare columns above, see “ResSpsView”
on page 159.
116
Resource Usage Macros and Tables
Chapter 11: ResUsageSps Table
Spare Columns
Column Name
Type of Data
Description
SpareCount[06 and 09]
count
Spare counted statistic.
SpareCount[07-08]
count
The following SpareCount columns will be converted to
the specified column names in Teradata Database 14.0:
• SpareCount07 = WorkMsgSendDelayCnt. This
column reports the number of messages that are
delivered to the work box.
• SpareCount08 = WorkMsgReceiveDelayCnt. This
column reports the number of messages that are still
waiting for AWTs at the end of each gather period.
SpareTrack00
track
SpareCount00 will be converted to the column name
AMPcount in Teradata Database 14.0. AMPcount is the
number of AMPs on the Node. AMPcount is used to
divide columns that are reporting data from all the
AMPs. This allows the ResSpsView view to report the
data columns on a per AMP basis. See “ResSpsView” on
page 159 for an example of the view.
SpareTrack[01-09]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 column contains the COD value. The
value represents the COD value in one tenths of a
percent, so a displayed value of 500 represents a COD
value of 50.0%.
Note: This value is valid only on SUSE Linux Enterprise
Server 10 systems and is a single value for the entire
system.
SpareTmon[01-09]
count
Spare time monitored statistic.
The spare column fields expand to values 00–09, so that column names would be
SpareCount00, SpareTrack09, SpareTmon03, and so on.
Resource Usage Macros and Tables
117
Chapter 11: ResUsageSps Table
Spare Columns
118
Resource Usage Macros and Tables
CHAPTER 12
ResUsageSvdsk Table
The ResUsageSvdsk table:
•
Provides AMP-level storage statistics.
•
Includes resource usage logs on cylinder allocation, migration, and I/O statistics.
If table logging is enabled on ResUsageSvdsk, a row is written to the database once for every
AMP vproc in the system for each log interval. To consolidate and summarize the total
number of rows written to the database, you can enable Summary Mode. For details, see
“Summary Mode” on page 124.
Note: This table is created as a MULTISET table.
The following table describes the ResUsageSvdsk table columns.
Column Name
Type of Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system load,
entries may be logged late (typically, by no
more than one or two seconds), but this
column will still contain the time value when
the entry should have been logged. See the Secs
and NominalSecs columns.
NodeId
n/a
Identifies the Node upon which the vproc
resides. The Node ID is formatted as CCCMM, where CCC denotes the three-digit
cabinet number and MM denotes the two-digit
chassis number of the node. For example, a
node in chassis 9 of cabinet 3 has a node ID of
‘003-09’.
INTEGER
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an
SMP node is ‘001-01’.
Resource Usage Macros and Tables
119
Chapter 12: ResUsageSvdsk Table
Column Name
Type of Data
Description
Data Type
Invalid
Platform
MISCELLANEOUS HOUSEKEEPING COLUMNS
GmtTime
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that occur
twice a year.
FLOAT
VprId
n/a
Identifies the AMP vproc. The AMP vproc ID
is numbered upward from 0. The maximum
value is 8191.
INTEGER
In Summary Mode, the value of the AMP
vproc ID is -1.
NodeType
n/a
Type of node, representing the per node system
family type. For example, 5600C or 5555H.
CHAR(8)
Secs
n/a
Actual number of seconds in the log period
represented by this row. Normally the same as
NominalSecs, but can be different in three
cases:
SMALLINT
• The first interval after a log rate change
• A sample logged late because of load on the
system
• System clock adjustments affect reported
Secs
Useful for normalizing the count statistics
contained in this row, for example, to a persecond measurement.
CentiSecs
n/a
Number of centiseconds in the logging period.
This column is useful when performing data
calculations with small elapsed times where the
difference between centisecond-based data and
whole seconds results in a percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds in
the logging period.
SMALLINT
SummaryFlag
n/a
Identifies the summarization status of this row.
If the value is ‘N,’ the row is a non-summary
row. If the value is ‘S,’ the row is a summary
row.
CHAR
In Summary Mode, the rows are summarized
into a single row. For details, see “Summary
Mode” on page 124.
120
Resource Usage Macros and Tables
Chapter 12: ResUsageSvdsk Table
Column Name
Type of Data
Description
Data Type
Active
count
Controls whether or not the rows will be
logged to the ResUsage tables if Active Row
Filter Mode is enabled.
FLOAT
Invalid
Platform
If Active is set to:
• a non-zero value, then the row contains
modified data columns.
• a zero value, then none of the data columns
in the row have been updated during the
logging period.
For example, if Active Row Filter Mode is
enabled, then the rows that have a zero Active
column value will not be logged to the
ResUsage tables.
CollectIntervals
n/a
The number of gather periods per reporting
period.
SMALLINT
In the Collect Buffer and Log Buffer, the value
is the number of Gather operations that have
been performed during the period. This
number can vary from one period to the next.
STATISTICS COLUMNS
I/O Statistics Columns
The following columns identify the I/O statistics reported by FSG for each AMP.
ReadCnt
count
Number of logical device reads.
FLOAT
WriteCnt
count
Number of logical device writes.
FLOAT
ReadKB
count
Number of KBs (1024 bytes) read from the
logical device.
FLOAT
WriteKB
count
Number of KBs (1024 bytes) written to the
logical device.
FLOAT
ReadRespTot
count
Total of individual read response time in
centiseconds.
FLOAT
WriteRespTot
count
Total of individual write response time in
centiseconds.
FLOAT
ReadRespMax
max
Maximum number of individual read response
time in centiseconds.
FLOAT
WriteRespMax
max
Maximum number of individual write
response time in centiseconds.
FLOAT
ReadRespSq
count
Total of squares of the individual read response
time in centiseconds.
FLOAT
WriteRespSq
count
Total of squares of the individual write
response time in centiseconds.
FLOAT
Resource Usage Macros and Tables
121
Chapter 12: ResUsageSvdsk Table
Column Name
Type of Data
Description
Data Type
ConcurrentReadMax
max
Maximum number of concurrent read I/O
requests.
FLOAT
ConcurrentWriteMax
max
Maximum number of concurrent write I/O
requests.
FLOAT
ConcurrentMax
max
Maximum number of concurrent I/O requests.
FLOAT
OutReqTime
count
Time with outstanding requests (busy time), in
centiseconds.
FLOAT
Invalid
Platform
Allocation Columns
These columns identify the allocation statistics reported by the Allocator process of the VSS vproc.
Note: These columns are populated and used by Teradata VS, an option sold separately from Teradata Database.
For details about these columns, see Teradata Virtual Storage.
Migration Columns
The following columns identify the number of cylinders that migrated to a different location on a device as well as the time,
in centiseconds, of all migration I/Os used, incurred, or saved during the log period.
Note: Each allocation is for a cylinder size worth of data, also known internally in the allocator as an extent. Thus the
column names begin with Ext for extent.
ExtMigrateFaster
count
FLOAT
Number of cylinders migrated to faster
locations (that is, migrations whose gross
benefits are positive) for the associated AMP.
The following formula calculates a Slower
Migration value, which is the number of
cylinders migrated to slower locations: Slower
Migration = ExtMigrateTotal ExtMigrateFaster
Cylinders are migrated to slower locations to
make room for hotter cylinders to replace
them.
ExtMigrateTotal
count
Total number of cylinders migrated to a
different physical location. For more
information, see the ExtMigrateFaster column.
FLOAT
ExtMigrateReadRespTot
count
Migration read I/O response time.
FLOAT
ExtMigrateWriteRespTot
count
Migration write I/O response time.
FLOAT
ExtMigrateIOTimeCost
count
Estimates the total cost (in centiseconds)
incurred by migration I/Os completing during
the log period, where cost is the extra time
waited by all non-migration I/Os as a result of
the migration I/O. The Migrator estimates
migration costs.
FLOAT
Note: This column is for internal use only. Do
not use this column unless directed by Teradata
Support.
122
Resource Usage Macros and Tables
Chapter 12: ResUsageSvdsk Table
Column Name
Type of Data
Description
Data Type
ExtMigrateIOTimeBenefit
count
Estimates the total I/O time savings achieved
by migrations completing in the log period.
The I/O time savings include the improvement
in response time caused by the new data
arrangement up to the time horizon.
FLOAT
Invalid
Platform
This value does not include the cost of the
migration I/Os and is a gross benefit, not a net
benefit. The Migrator estimates the migration
benefit.
Note: This column is for internal use only. Do
not use this column unless directed by Teradata
Support.
ExtMigrateIOTimeImprove
count
Estimates the percent improvement in average
I/O response time due to migrations
completing in the log interval. In theory, this
percentage improvement is permanent. For
example, if, right before a particular log
interval, the average I/O response time was 10
milliseconds (ms), then the Migration logs an
ExtMigrateIOTimeImprove value of 10% in
this interval. The average I/O response time
after the log interval should be (100%10%)*10ms = 9ms. Migration then logs an
ExtMigrateIOTimeImprove of 1% in the next
interval. The average I/O response time in the
new log interval is (100%-1%)*9ms = 8.91ms.
FLOAT
ExtMigrateIOTimeImprove is only an
estimate. Its permanent improvement remains
in effect as long as the workload does not
change and newer migrations do not
significantly alter the data arrangement.
When the workload changes or new migrations
affect data arrangement, response time changes
in an unquantifiable way.
Despite this, ExtMigrateIOTimeImprove is
useful because it predicts actual system
performance at least for short periods of time
and can be used to understand why the
migration algorithm is doing what it is doing.
Note: This column is for internal use only. Do
not use this column unless directed by Teradata
Support.
Resource Usage Macros and Tables
123
Chapter 12: ResUsageSvdsk Table
Summary Mode
Summary Mode
When Summary Mode is active for the ResUsageSvdsk table, one row is written to the database
for each node in the system. This row summarizes all AMP data in each node per log interval.
You can determine if a row is in Summary Mode by checking the SummaryFlag column for
that row.
IF the SummaryFlag column value is…
THEN the data for that row is being logged…
‘S’
in Summary Mode.
‘N’
normally.
Spare Columns
The ResUsageSvdsk table has 30 spare columns (one of which is being used) as shown in the
table below.
Column Name
Type of Data
Description
SpareCount[00-09]
count
Spare counted statistic.
SpareTrack[00-09]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 column contains the COD
value. The value represents the COD value in
one tenths of a percent, so a displayed value of
500 represents a COD value of 50.0%.
Note: This value is valid only on SUSE Linux
Enterprise Server 10 systems and is a single
value for the entire system.
SpareTmon[01-09]
count
Spare time monitored statistic.
The spare column fields expand to values 00–09, so that column names would be
SpareCount00, SpareTrack02, or SpareTmon06, and so on.
124
Resource Usage Macros and Tables
CHAPTER 13
ResUsageSvpr Table
ResUsageSvpr logical table includes resource usage data for available system-wide, virtual
processor information.
Note: This table is created as a MULTISET table. For more information see “Relational
Primary Index” on page 38.
The following table describes the ResUsageSvpr table columns. However, always use the view
“ResSvprView” on page 166 to access the data rather than accessing the ResUsageSvpr table
directly.
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system load,
entries might be logged late (typically, by no
more than one or two seconds), but this
column will still contain the time value when
the entry should have been logged. See the Secs
and NominalSecs columns.
NodeId
n/a
Identifies the Node upon which the vproc
resides. The Node ID is formatted as CCCMM, where CCC denotes the three-digit
cabinet number and MM denotes the two-digit
chassis number of the node. For example, a
node in chassis 9 of cabinet 3 has a node ID of
‘003-09’.
INTEGER
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an
SMP node is ‘001-01’.
MISCELLANEOUS HOUSEKEEPING COLUMNS
GmtTime
Resource Usage Macros and Tables
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that occur
twice a year.
FLOAT
125
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
NodeType
VprId
Description
Data Type
n/a
Type of node, representing the per node system
family type. For example, 5600C or 5555H.
CHAR(8)
n/a
Identifies the vproc number (non-Summary
Mode) or the vproc type (Summary Mode; 0 =
NODE, 1 = AMP, 2 = PE, 3=GTW, 4=RSG,
5=VSS).
INTEGER
Invalid
Platform
The VprId can be any of the following
depending on the type:
• AMP vprocs: numbered upward from 0.
• PE vprocs: numbered downward from
16383.
• NODE vprocs: numbered upward from
16384.
• GTW vprocs: numbered upward from 8192.
• RSG vprocs: numbered downward from
9215.
• VSS vprocs: numbered downward from
10238.
The vproc numbers within each type range are
contiguous. Each existing vproc type range
should not overlap into the range of another
existing vproc type on the system.
VprType
n/a
Type of vproc. The values can be NODE, AMP,
PE, GTW, RSG, or TVS (see Teradata Virtual
Storage).
CHAR(4)
Secs
n/a
Actual number of seconds in the log period
represented by this row. Normally the same as
NominalSecs, but can be different in three
cases:
SMALLINT
• The first interval after a log rate change
• A sample logged late because of load on the
system
• System clock adjustments affect reported
Secs
Useful for normalizing the count statistics
contained in this row, for example, to a persecond measurement.
CentiSecs
n/a
Number of centiseconds in the logging period.
This column is useful when performing data
calculations with small elapsed times where the
difference between centisecond-based data and
whole seconds results in a percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds in
the logging period.
SMALLINT
126
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
Description
Data Type
NCPUs
n/a
Number of CPUs on this node.
SMALLINT
Invalid
Platform
This column is useful for normalizing the CPU
utilization column values for the number of
CPUs on the node. This is especially important
in coexistence systems where the number of
CPUs can vary across system nodes.
SummaryFlag
n/a
Identifies the summarization status of this row.
Possible values are ‘N’ if the row is a nonsummary row and ‘S’ if it is a summary row.
CHAR
Active
count
Controls whether or not the rows will be
logged to the ResUsage tables if Active Row
Filter Mode is enabled.
FLOAT
If Active is set to:
• a non-zero value, then the row contains
modified data columns.
• a zero value, then none of the data columns
in the row have been updated during the
logging period.
For example, if Active Row Filter Mode is
enabled, then the rows that have a zero Active
column value will not be logged to the
ResUsage tables.
CollectIntervals
n/a
The number of gather periods per reporting
period.
SMALLINT
In the Collect Buffer and Log Buffer, the value
is the number of Gather operations that have
been performed during the period. This
number can vary from one period to the next.
STATISTICS COLUMNS
PROCESS SCHEDULING COLUMNS
CPU Utilization Columns
These columns represent CPU activities associated with this virtual processor, subdivided into 48 partitions. Partition 0 is
reserved for use by PDE processes. See Appendix D: “Partition Assignments” for more information on the other partitions.
Each entry below represents 48 columns, where [i] expands to the values 00 - 47, for example, CPUUservPart31.
For definitions of user service and user execution, see "Process Scheduling Columns" in the Chapter 5: “ResUsageScpu
Table.”
CPUUServPart[i]
Resource Usage Macros and Tables
count
Time in centiseconds CPUs are busy in
partition i doing user service. This is the system
level time spent on a process.
FLOAT
127
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
CPUUExecPart[i]
count
Description
Data Type
Time in centiseconds CPUs are busy in
partition i doing user execution. This is the
user level time spent on a process.
FLOAT
Invalid
Platform
Cylinder Read Columns
These columns represent file system resource usage statistics. The Cylinder Read feature uses these statistics for tracking
performance and utilization.
FileFcrRequests
count
Total number of requests for the File System to
use Cylinder Read.
FLOAT
This column is tracked and recorded by the File
System. It records the number of attempts to
use Cylinder Read independent of whether the
request will be issued to FSG or not. A request
can be denied due to insufficient data blocks or
because there is insufficient space in the FSG
cache. Requests can also be denied at both the
user and kernel level. Each of these items is
counted in other FileFcr ResUsage columns.
A number of calculations can be performed
using this column:
• Requests issued to FSG =
FileFcrRequests - FileFcrDeniedUser
• Successful Cylinder Reads =
FileFcrRequests - FileFcrDeniedUser FileFcrDeniedKern
FileFcrRequestsAdaptive
count
Number of adaptive requests from File System.
FLOAT
ALL
This column is tracked and recorded by the File
System. It records the number of requests for
adaptive-style Cylinder Reads.
Note: This column is not currently used.
FileFcrBlocksRead
count
Number of data blocks read in using Cylinder
Read.
FLOAT
This column is tracked and recorded by the
FSG subsystem. It records the total number of
data blocks read in by successful Cylinder Read
operations.
The average number of data blocks in a
successful Cylinder read can be calculated as:
Average data blocks/ Cylinder Read =
FileFcrBlocksRead / (FileFcrRequests FileFcrDeniedUser - FileFcrDeniedKern)
128
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
FileFcrDeniedUser
count
Description
Data Type
Number of Cylinder Read requests denied by
the File System.
FLOAT
Invalid
Platform
This column is tracked and recorded by the File
System. It records the number of Cylinder Read
attempts that have been denied by the File
System. A request can be denied by the File
System due to insufficient number of data
blocks being requested (for example, the
FileFcrDeniedThreshUser column). For
information, see the FileFcrDeniedThreshUser
column.
FileFcrBlocksDeniedUser
count
Number of data blocks contained in the
rejected requests for Cylinder Read.
FLOAT
This column is tracked and recorded by the File
System. It records the number of data blocks
that were part of attempts to use Cylinder Read
that were denied by the File System; therefore,
also incremented the FileFcrDeniedUser
column.
FileFcrDeniedKern
count
Number of Cylinder Read requests denied by
the FSG subsystem.
FLOAT
This column is tracked and recorded by the
FSG subsystem. It records the number of
Cylinder Read requests issued to the FSG
subsystem which, for any reason, have been
denied. A request can be denied due to
insufficient data blocks (for example, the
FileFcrDeniedThreshKern column) or because
there is insufficient space in the FSG cache (for
example, the FileFcrDeniedCache column).
The FSG subsystem can reject a request
containing insufficient data blocks that the File
System thought had enough blocks because the
FSG subsystem reduces the count by the
number of data blocks that are already resident
in the cache.
FileFcrBlocksDeniedKern
count
Number of data blocks contained in the
rejected requests for Cylinder Read.
FLOAT
This column is tracked and recorded by the
FSG subsystem. It records the number of data
blocks that were part of attempts to use
Cylinder Read that were denied by the FSG
subsystem; therefore, also incremented the
FileFcrDeniedKern column.
Resource Usage Macros and Tables
129
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
FileFcrDeniedCache
count
Description
Data Type
Number of Cylinder Read requests denied by
FSG due to insufficient cache.
FLOAT
Invalid
Platform
This column is tracked and recorded by FSG. It
records the number of Cylinder Read requests
which have been denied due to insufficient FSG
cache space for a cylinders worth of data.
FileFcrBlocksDeniedCache
count
Number of data blocks contained in Cylinder
Read requests rejected by the FSG subsystem
due to insufficient cache.
FLOAT
This column is tracked and recorded by the
FSG subsystem. It records the number of data
blocks that were part of attempts to use
Cylinder read that were denied by the FSG
subsystem due to insufficient cache space;
therefore, also incremented the
FileFcrDeniedCache column.
FileFcrDeniedThreshUser
count
Number of Cylinder Read requests denied by
the File System due to insufficient data blocks.
FLOAT
This column is tracked and recorded by the File
System. It records the number of Cylinder Read
requests which have been denied due to the
data block threshold criteria. There is a
minimum threshold of data blocks for an
individual Cylinder Read request. If the
number of data blocks is below this threshold,
the overhead of the Cylinder Read operation is
considered too large and issuing individual
data block reads is considered more efficient.
Therefore, the Cylinder Read request is denied.
FileFcrBlocksDeniedThreshUser
count
Number of data blocks contained in Cylinder
Read requests rejected for threshold by the File
System.
FLOAT
This column is tracked and recorded by the File
System. It records the number of data blocks
that were part of attempts to use Cylinder Read
that were denied by the File System due to the
number of blocks being below the threshold;
therefore, also incremented the
FileFcrDeniedThreshUser column.
130
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
FileFcrDeniedThreshKern
count
Description
Data Type
Number of Cylinder Read requests denied by
the FSG subsystem due to insufficient data
blocks.
FLOAT
Invalid
Platform
This column is tracked and recorded by the
FSG subsystem. It records the number of
Cylinder Read requests which have been denied
due to the data block threshold criteria. There
is a minimum threshold of data blocks for an
individual Cylinder Read request. If the
number of data blocks is below this threshold,
the overhead of the Cylinder Read operation is
considered too large and issuing individual
data block reads is considered more efficient.
Therefore, the Cylinder Read request is denied.
FSG must reevaluate the threshold for a request
that the File System considered valid since FSG
eliminates any data blocks from the request list
that are already resident in the cache. This
could reduce the count that the File System
thought was above the threshold to one that is
now below.
FileFcrBlocksDeniedThreshKern
count
Number of data blocks contained in Cylinder
Read requests rejected for threshold by the FSG
subsystem.
FLOAT
This column is tracked and recorded by the
FSG subsystem. It records the number of data
blocks that were part of attempts to use
Cylinder read that were denied by the FSG
subsystem due to the number of blocks being
below the threshold; therefore, also
incremented the FileFcrDeniedThreshKern
column.
ChnSignal Status Tracking Columns
These columns track the chnsignal last done status (or track slowest vproc on the system for processing AMP steps).
MsgChnLastDone
count
The number of last done events that occurred
for this vproc.
FLOAT
Note: The last AMP to finish an operation may
send a last done broadcast message indicating
the work is done for this step. This is used in
tracking down the slowest AMP in the system.
An AMP that has more last done messages than
the others could be a bottleneck in the system
performance.
Resource Usage Macros and Tables
131
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Process Pending Counts and Wait Time Columns
These columns identify the number of processes blocked on database locks, and how long they were blocked.
ProcPendDBLock
count
Number of processes blocked pending database
locks.
FLOAT
ProcBlksDBLock
count
Number of times processes blocked for
database locks.
FLOAT
ProcWaitDBLock
count
Total time processes were blocked pending
database locks.
FLOAT
ALL
MEMORY COLUMNS
Memory Allocations Columns
These columns represent the number and amount of memory allocations specific to virtual processor activities, subdivided
into segment types. The columns do not include any memory allocations specific to the node the vproc is running under.
Teradata Database context amounts are not included since they can be calculated by multiplying the fixed page size by the
number of page allocations. Disk segment memory types are described by single entries below, each of which expands into
six actual columns, where [seg] is replaced as follows:
• PDb = Permanent data block disk segments
• PCi = Permanent cylinder index disk segments
• SDb = Regular or restartable spool data block disk segments
• SCi = Regular or restartable spool cylinder index disk segments
• TJt = Transient journal table or WAL data block or WAL cylinder index
• APt = Append table or permanent journal table data block or cylinder index disk segments
For example MemPDbAlloc, MemPCiAlloc, MemSDb, and so on.
Mem[seg]Allocs
count
Number of successful memory allocations and
size-increasing memory alters on disk
segments.
FLOAT
ALL
Mem[seg]AllocKB
count
Total KBs attributed to allocations and sizeincreasing memory alters for disk segments.
FLOAT
ALL
MemCtxtAllocs
count
Number of successful memory allocations and
size-increasing memory alters on task context
pages.
FLOAT
Note: Only scratch pages will get allocated. All
other task context pages will appear resident at
some point soon after component restart.
132
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Memory Resident Columns
These columns represent the amount of memory resident specific to virtual processor activities, subdivided into memory
types. The columns do not include any memory allocations specific to the node the vproc is running under.
Disk memory segments can be in one of four states:
• Clean (unmodified) and Unaccessed by any process (CU)
• Dirty (modified) and Unaccessed (DU)
• Clean and Accessed (CA)
• Dirty and Accessed (DA).
Permanent segments for an entire table can be user-locked-in to memory. These are called frozen segments (Frz), and no
state subdivision is necessary because they cannot be aged or forced out of memory.
‘Regular’ disk segment memory types are described by single entries below, each of which expands into six actual columns,
where [seg] is replaced as follows:
•
•
•
•
•
•
PDb = Permanent data block disk segments
PCi = Permanent cylinder index disk segments
SDb = Regular or restartable spool data block disk segments
SCi = Regular or restartable spool cylinder index disk segments
TJt =Transient journal table or WAL data block or WAL cylinder index
APt = Append table or permanent journal table data block or cylinder index disk segments
MemCtxtRes
track
Current pages resident in memory for task
context segments.
FLOAT
ALL
MemPKBResFrz
track
Current KBs resident in memory for frozen
segments.
FLOAT
ALL
Mem[seg]KBResCU
track
Current KBs resident in memory for regular
disk segments that are currently clean and not
accessed.
FLOAT
ALL
Note: MemBaseKBResCU tracks of the sum of
the data block sizes in the FSG cache (for both
general purpose preloads and cylinder read
preloads).
Mem[seg]KBResDU
track
Current KBs resident in memory for regular
disk segments that are currently dirty and
unaccessed.
FLOAT
ALL
Mem[seg]KBResCA
track
Current KBs resident in memory for regular
disk segments that are currently clean and
accessed.
FLOAT
ALL
Mem[seg]KBResDA
track
Current KBs resident in memory for regular
disk segments that are currently dirty and
accessed.
FLOAT
ALL
Resource Usage Macros and Tables
133
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Paging Columns
These columns identify paging activities on pages containing Teradata Database context pages only.
MemCtxtPageReads
count
Number of task context pages that were paged
in.
FLOAT
ALL
MemCtxtPageWrites
count
Number of task context pages that were paged
out.
FLOAT
ALL
Swapping Columns
These columns identify the effects on disk segments when all processes accessing them get swapped out.
MemSwapDrops
count
Number of disk segments that were dropped
from memory because all accessor processes
were swapped out.
FLOAT
ALL
MemSwapDropKB
count
KBs dropped from memory by
MemSwapDrops.
FLOAT
ALL
MemSwapReads
count
Number of disk segments that were re-read
when they were previously dropped from
memory because all accessor processes were
swapped out.
FLOAT
ALL
MemSwapReadKB
count
KBs re-read from memory by MemSwapReads.
FLOAT
ALL
Task Context Segment Usage Columns
These columns identify the usage of task context segments and how they leave memory.
MemCtxtAccesses
count
Number of segments accessed.
FLOAT
MemCtxtAccessKB
count
KBs of segments accessed.
FLOAT
MemCtxtDeaccesses
count
Number of segments deaccessed. (Deaccessed
segments remain in memory until paged out
through aging.)
FLOAT
MemCtxtDeaccessKB
count
KBs of segments deaccessed.
FLOAT
MemCtxtDestroys
count
Number of segments destroyed. (Destroyed
segments are immediately dropped from
memory.)
FLOAT
MemCtxtDestroyKB
count
KBs of segments destroyed.
FLOAT
NET COLUMNS
Point-to-Point Net Traffic Columns
These columns identify the number (Reads, Writes) and amount (ReadKB, WriteKB) of input and output messages passing
through either Teradata Database net through point-to-point (1:1) methods (PtP)
NetPtPReads
134
count
Number of point-to-point messages input to
the vproc.
FLOAT
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
NetPtPWrites
Description
Data Type
count
Number of point-to-point messages output
from the vproc.
FLOAT
NetPtPReadKB
count
Total KBs of point-to-point messages input to
the vproc.
FLOAT
NetPtPWriteKB
count
Total KBs of point-to-point messages output to
the vproc.
FLOAT
Invalid
Platform
Broadcast Net Traffic Columns
These columns identify the number (Reads, Writes) and amount (ReadKB, WriteKB) of input and output messages passing
through the Teradata Database nets through broadcast (1:many) methods (Brd) per net.
NetBrdReads
count
Number of broadcast messages input to the
vproc.
FLOAT
NetBrdWrites
count
Number of broadcast messages output from
the vproc.
FLOAT
NetBrdReadKB
count
Total KBs of broadcast messages input to the
vproc.
FLOAT
NetBrdWriteKB
count
Total KBs of broadcast messages output from
the vproc.
FLOAT
Work Mailbox Queue Columns
These columns identify the virtual processor work mailbox queue length where requested work awaits the allocation of a
process to perform the work.
MsgWorkQLenSum
count
Total number of work requests waiting during
each log interval.
FLOAT
The Sum count tracks the current count at the
end of each gather period and sums the counts
over the log period.
Note: To calculate the average work requests
waiting, divide this value by the
CollectIntervals value. The CollectIntervals
value is the number of gather periods per
reporting period. For more information, see
the CollectIntervals column.
MsgWorkQLenMax
max
Maximum number of work requests waiting
during each log interval.
FLOAT
The Max count, unlike the Sum count, tracks
the maximum count over the log period.
Therefore the Sum count can be 0 even though
the Max count can be non-zero over the log
period.
Resource Usage Macros and Tables
135
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
GENERAL CONCURRENCY CONTROL COLUMNS
Database Locks Columns
These columns identify database locking activities.
DBLockEnters
count
Number of times a database lock was entered
for holding.
FLOAT
DBLockBlocks
count
Number of times a database lock was blocked.
FLOAT
DBLockDeadlocks
count
Number of times a database lock was
deadlocked.
FLOAT
DBLockBlocksSum
count
Total number of requests blocked on database
locks during each log interval.
FLOAT
ALL
To calculate the average number of requests
blocked, divide this value by the
CollectIntervals value. The CollectIntervals
value is the number of gather periods per
reporting period. For more information, see
the CollectIntervals column.
DBLockBlocksMax
max
Maximum number of requests blocked on
database locks during each log interval.
FLOAT
ALL
DBLocksHeldSum
count
Total number of database locks held during
each log interval.
FLOAT
ALL
FLOAT
ALL
To calculate the average number of database
locks held, divide this value by the
CollectIntervals value. The CollectIntervals
value is the number of gather periods per
reporting period. For more information, see
the CollectIntervals column.
DBLocksHeldMax
max
Maximum number of database locks held
during each log interval.
FILE SYSTEM COLUMNS
Segment Acquires Columns
These columns identify the total disk memory segments acquired by the file system during the log period. Logical acquires
(Acqs) and the logical amount acquired (AcqKB) are identified. Acquires causing physical reads (AcqReads) and the amount
read (AcqReadKB) are identified as a subset of logical acquires. Disk segment memory types are described by single entries
below, each of which expands into six actual columns, where [seg] is replaced as follows:
•
•
•
•
•
•
136
PDb = Permanent data block disk segments
PCi = Permanent cylinder index disk segments
SDb = Regular or restartable spool data block disk segments
SCi = Regular or restartable spool cylinder index disk segments
TJt = Transient journal table or WAL data block or WAL cylinder index
APt = Append table or permanent journal table data block or cylinder index disk segments
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
Description
Data Type
File[seg]Acqs
count
Total number of disk segments acquired.
FLOAT
File[seg]AcqKB
count
Total KBs acquired by File[seg]Acqs.
FLOAT
File[seg]AcqReads
count
Number of disk segment acquires that caused a
physical read.
FLOAT
File[seg]AcqReadKB
count
KBs physically read by File[seg]AcqReads.
FLOAT
Invalid
Platform
Data Block Prefetches Columns
These columns identify File Segment Prefetch activities. File segment prefetches are described by single entries below, each of
which expands into six actual columns, where [seg] is replaced as follows:
• PDb = Permanent data block disk segments
• PCi = Permanent cylinder index disk segments
• SDb = Regular or restartable spool data block disk segments
• SCi = Regular or restartable spool cylinder index disk segments
• TJt = Transient journal table or WAL data block or WAL cylinder index
• APt = Append table or permanent journal table data block or cylinder index disk segments
Note: A prefetch is either a cylinder read operation or an individual block read operation. Either of these operations are
generically called a prefetch.
File[seg]Pres
count
Total number of times a logical data prefetch
was performed (either a cylinder read or an
individual block read).
FLOAT
File[seg]PresKB
count
Total number of KBs logically prefetched
(either a cylinder read or an individual block
read) by File[seg]Pres.
FLOAT
For cylinder reads, this column does not
include the disk sectors in between the loaded
data blocks.
File[seg]PreReads
count
Total number of disk segment prefetches
(either a cylinder read or an individual block
read) that caused a logical read.
FLOAT
File[seg]PreReadKB
count
Total number of KBs physically read by
File[seg]PreReads.
FLOAT
For cylinder reads, this column includes the
disk sectors in between the loaded data blocks.
Resource Usage Macros and Tables
137
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Segments Released Columns
These columns identify the total disk memory segments released by the file system, as well as those segments that are
dropped from memory during the log period. When a segment is released, the segment is either:
• Forced (F)
• Remains resident in memory (R)
• Aged out of memory (A), from segments that are currently resident
Both the number of segments (Rels, Writes, Drps) and the size of the segments (RelKB,WriteKB, DrpKB) are counted. When
a segment leaves memory, it must be written to disk only if the segment is dirty (Dy), that is, modified. Otherwise, the clean
(Cn), that is, unmodified segment is simply dropped.
Most spool blocks for a small table remain resident when they are created and age there. Each of these will be counted as a
dirty resident release (DyRRel fields). If a block survives in the cache, it would be reacquired (whenever the system creates
spool data, a subsequent step will read it) and released again. The release will still be counted as a dirty resident release, since
the block survived in a modified state. On the other hand, if there is contention for room in the FSG cache, the segment
might be removed from memory. Because it is a modified segment, it must be written out first. This is counted as a dirty age
write (DyAWrite fields). When it is reacquired it will no longer be modified, so the subsequent release will be counted as a
clean resident release (CnRRel fields).
Full table modification operations make one pass on the table and modify each block only once. Since these operations do
not access a block multiple times, there is no point keeping them in the cache. If a block that was examined did not contain
any rows that qualify for the modification, when the block is released it will be dropped from memory immediately (FDrp
fields). However if the block was modified, when it is released the system issues the write as part of the release so it is counted
as a forced write (FWrite fields). Since the system also drops the block from memory as soon as the write is complete, this
release is also counted as a forced drop (FDrp fields).
Disk segment memory types are described by single entries below, each of which expands into six actual columns, where
[seg] is replaced as follows:
•
•
•
•
•
•
PDb = Permanent data block disk segments
PCi = Permanent cylinder index disk segments
SDb = Regular or restartable spool data block disk segments
SCi = Regular or restartable spool cylinder index disk segments
TJt = Transient journal table or WAL data block or WAL cylinder index
APt = Append table or permanent journal table data block or cylinder index disk segments
File[seg]DyRRels
count
Number of dirty disk segment resident releases.
FLOAT
File[seg]DyRRelKB
count
KBs released by File[seg]DyRRels.
FLOAT
File[seg]FWrites
count
Number of disk segment forced releases or
specific I/O requests causing an immediate
physical write. Includes spool data that is aged
out immediately and permanent data that is
written immediately.
FLOAT
File[seg]FWriteKB
count
KBs written by File[seg]FWrites.
FLOAT
File[seg]DyAWrites
count
Number of dirty disk segments aged out of
memory causing a delayed physical write.
FLOAT
If the segment is unmodified, only CnADrps is
incremented. If the segment is modified, both
DyAWrites and CnADrps are incremented.
138
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
Description
Data Type
File[seg]DyAWriteKB
count
KBs written by File[seg]DyAWrites.
FLOAT
Invalid
Platform
If the segment is unmodified, only CnADrpKB
is incremented. If the segment is modified,
both DyAWriteKB and CnADrpKB are
incremented.
File[seg]CnRRels
count
Number of clean disk segment resident
releases.
FLOAT
File[seg]CnRRelKB
count
KBs released by File[seg]CnRRels.
FLOAT
File[seg]FDrps
count
Number of disk segment forced releases
causing an immediate memory drop. Segments
that are never to be part of the memory cache
(the age queue) are counted as forced drops.
FLOAT
File[seg]FDrpKB
count
KBs dropped by File[seg]FDrps.
FLOAT
File[seg]CnADrps
count
Number of clean disk segments aged out of
memory. If the segment is unmodified, only
CnADrps is incremented. If the segment is
modified, both DyAWrites and CnADrps are
incremented.
FLOAT
Note: CnADrps counts includes the DyAWrites
counts. To calculate the clean segments that
aged out of memory, subtract the DyAWrites
value from the CnADrps value.
File[seg]CnADrpKB
count
KBs dropped by File[seg]CnADrps.
FLOAT
If the segment is unmodified, only CnADrpKB
is incremented. If the segment is modified,
both DyAWriteKB and CnADrpKB are
incremented.
Note: CnADrpKB counts includes the
DyAWriteKB counts. To calculate the KBs of
clean segments that aged out of memory,
subtract the DyAWriteKB value from the
CnADrpKB value.
Data Segment Lock Requests Columns
These columns identify the number of lock requests, blocks, and deadlocks on a disk segment, including those implied for
segment acquires.
FileLockEnters
count
Number of lock requests on disk segments.
FLOAT
FileLockBlocks
count
Number of lock requests that were blocked.
(Total locks - locks blocked = locks with
immediate grants.)
FLOAT
FileLockDeadlocks
count
Number of deadlocks detected on lock
requests.
FLOAT
Resource Usage Macros and Tables
139
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
Cylinder Management Overhead Events Columns
These columns identify the number of times the file system software performed a cylinder management event. The table
ResUsageIvpr further breaks down the I/Os associated with these events. See Appendix C: “ResUsageIvpr Table.”
FileCylAllocs
count
Number of new cylinders allocated.
FLOAT
FileCylFrees
count
Number of logical or physical cylinders freed.
FLOAT
FileCylMigrs
count
Number of cylinder migrations.
FLOAT
FileMCylPacks
count
Number of MiniCylPacks performed.
FLOAT
FileCylDefrags
count
Number of cylinder defragments performed.
FLOAT
Synchronized Full Table Scans Columns
These columns contain statistics relating to synchronized full table scans.
Note: The following columns have been moved from ResUsageIvpr to ResUsageSvpr to avoid costly joins.
FileSyncScans
count
Number of attempts to synchronize a full table
scan.
FLOAT
FileSyncSubtables
track
Number of subtables scanned by one or more
full table scanners who are willing to
synchronize scans.
FLOAT
FileSyncScanners
track
Number of tasks involved in full table scans
who are willing to synchronize with other
scanners.
FLOAT
FileSyncGroups
track
Number of groups of scanners involved in full
table scans. A group consists of scanners who
are able to use the same read I/O to obtain data
from disk.
FLOAT
Write Ahead Logging Columns
These columns identify the number of times the file system software performed a cylinder management event associated
with the WAL log.
FileWCylAllocs
count
Number of new WAL cylinders allocated.
FLOAT
FileWCylFrees
count
Number of times the file system logically frees a
cylinder.
FLOAT
Allocation Columns
These columns identify the allocation statistics reported by the Allocator.
AllocatorExtentAllocReqs
count
Number of cylinder allocation requests
received by the allocator.
FLOAT
AllocatorExtentFreeReqs
count
Number of cylinder free requests received by
the allocator.
FLOAT
AllocatorMapIOsStarted
count
Number of map I/Os initiated by the allocator.
FLOAT
140
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Column Name
Type of
Data
AllocatorMapIOsDone
count
Description
Data Type
Number of map I/Os completed by the
allocator.
FLOAT
Invalid
Platform
Node Agent Columns
These columns identify the migration and buffer processing statistics reported by the Node Agent.
NodeAgentMigrationsStarted
count
Number of migration requests started by the
Node Agent.
FLOAT
NodeAgentMigrationsDone
count
Number of migration requests completed by
the Node Agent.
FLOAT
NodeAgentStatProcessed
count
Number of statistics buffers processed by the
Node Agent.
FLOAT
Extent Driver I/O Columns
These columns identify the I/O statistics reported from the extent driver.
Note: These columns are populated and used by Teradata VS, an option sold separately from Teradata Database. Associated
configuration settings appear in the ctl utility if you have purchased Teradata VS.
For details about these columns, see Teradata Virtual Storage.
FSG I/O Columns
These columns identify the I/O statistics reported from the FSG.
IoRespMax
max
Maximum I/O response time in milliseconds
on an AMP.
FLOAT
IoGapMax
max
Maximum time gap between I/O completions
in milliseconds on an AMP.
FLOAT
ALL
Master Index Columns
MIWriteLocks
count
Number of write locks acquired on a MI.
FLOAT
MIWriteLockTime
count
MI write lock hold time in milliseconds.
FLOAT
MIWriteLockTimeMax
max
Maximum MI write lock hold time in
milliseconds.
FLOAT
MIWrites
count
Number of writes while holding a MI no
modification (nomod) write lock.
FLOAT
MIWriteTime
count
Total write time while holding MI no
modification (nomod) write lock in
milliseconds.
FLOAT
MIWriteTimeMax
max
Maximum write time while holding a MI no
modification (nomod) write lock in
milliseconds.
FLOAT
MISleeps
count
Number of times spent waiting to get a MI
lock.
FLOAT
Resource Usage Macros and Tables
141
Chapter 13: ResUsageSvpr Table
Summary Mode
Column Name
Type of
Data
MISleepTime
MISleepTimeMax
Description
Data Type
count
Total amount of time spent waiting to get a MI
lock in milliseconds.
FLOAT
max
Maximum amount of time spent waiting to get
a MI lock.
FLOAT
Invalid
Platform
Summary Mode
When Summary Mode is active for the ResUsageSvpr table, one row is written to the database
for each type of vproc on each node in the system, summarizing the vprocs of that type on
that node, for each log interval.
You can determine if a row is in Summary Mode by checking the SummaryFlag column for
that row.
142
IF the SummaryFlag column value is…
THEN the data for that row is being logged…
‘S’
in Summary Mode.
‘N’
normally.
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Spare Columns
Spare Columns
The ResUsageSvpr table has 30 spare columns as shown in the table below.
Column Name
Type of Data
Description
SpareCount[00-07]
count
The following SpareCount columns will be
converted to the specified column names in
Teradata Database 14.0:
• SpareCount00 = DBMergeTried. The
number of times the data block being
modified was attempted to be merged with
some number of adjacent data blocks as part
of the modification.
• SpareCount01 = DBMergeDone. The
number of times the data block being
modified has successfully merged with some
number of adjacent data blocks as part of the
modification. Subtracting DBMergeDone
from DBMergeTried will result in the
number of data block merge operations that
were tried and failed.
• SpareCount02 = DBMergeElim. The
number of data blocks eliminated due to
data block merges. If n data blocks are
merged into 1 large block (where n is the
number of data blocks), this number is
incremented by n-1.
• SpareCount03 = DBMergeExtrIO. The
number of additional physical I/Os
performed in the data block merge process
over and above those that would have been
done if no data block merges were
attempted. This includes any extra physical
I/Os that were performed regardless of
whether a particular merge attempt
succeeded or not.
• SpareCount04 = FileACPCylsSkipped. The
number of cylinders AutoCylPack scanned at
the MI level and decided nothing needed to
be done.
• SpareCount05 = FileACPCylsMigr. The
number of successful migrations performed
by AutoCylPack.
Resource Usage Macros and Tables
143
Chapter 13: ResUsageSvpr Table
Spare Columns
Column Name
Type of Data
Description
SpareCount[00-07]
count
• SpareCount06 = FileACPCylsUnFSEOnly.
The number of cylinders the background
task, Automatic Cylinder Packing (ACP),
selected for performing a migration, but
could not because of a CI that is marked
down, a locking conflict, or a recently
modified CI. Instead (except for the down CI
case), ACP cleaned-upa the unfree sector
entries (UNFSEs) on these cylinders. For
more information on ACP, see Utilities or
Performance Management.
• SpareCount07 = FileACPCylsPostponed.
The number of cylinders AutoCylPack
selected for performing a migration, but
could not be performed at the current time.
This can happen due to conflicts with
foreground tasks modifying the cylinder at
around the same time as AutoCylPack.
AutoCylPack, therefore, postpones the work
until the next time it scans the MI from the
beginning. When AutoCylPack sees this
cylinder again, if the cylinder still qualifies, it
is selected again for processing.
SpareCount[08-09]
count
Spare counted statistic.
SpareTrack[00-09]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 column contains the COD
value. The value represents the COD value in
one tenths of a percent, so a displayed value of
500 represents a COD value of 50.0%.
(continued)
Note: This value is valid only on SUSE Linux
Enterprise Server 10 systems and is a single
value for the entire system.
144
Resource Usage Macros and Tables
Chapter 13: ResUsageSvpr Table
Spare Columns
Column Name
Type of Data
Description
SpareTmon[01-03]
count
The following SpareCount columns will be
converted to the specified column names in
Teradata Database 14.0:
• SpareTmon01= FSGCacheWaits. The
number of times the file system waits for
memory to become available in the file
segment cache when trying to read data
from disk.
• SpareTmon02 = FSGCacheWaitTime. The
total amount of time the file system waits for
memory to become available in the file
segment cache when trying to read data
from disk.
• SpareTmon03 = MAX. The maximum
amount of time the file system waits for
memory to become available in the file
system cache when trying to read data from
disk.
SpareTmon[04-09]
count
Spare time monitored statistic.
a. Unfree sectors are those that have no current data block, but cannot yet be used for a new data block.
The file system cleans up the unfree sectors, which entails deleting the entries in the CI that say the
sectors are unfree and creating new entries that say these sectors are free.
The spare column fields expand to values 00-09, so that column names would be
SpareCount08, SpareTrack04, SpareTmon01, and so on.
Resource Usage Macros and Tables
145
Chapter 13: ResUsageSvpr Table
Spare Columns
146
Resource Usage Macros and Tables
CHAPTER 14
Resource Usage Views
This chapter provides the definitions of the resource usage views.
Note: Always use the views to access the data when it is available through the views rather
than accessing the ResUsage table directly.
To see the view definitions, execute SHOW VIEW viewname, where viewname is the name of
the view whose most recent SQL create text is to be reported. For details on using the SHOW
VIEW statement, see SQL Data Definition Language.
The following views report the table column, GroupId. A homogenous system requires no
changes to use this macro because all the nodes will be assigned to group A. For a coexisting
system, however, the values need to be set up when the system is installed or reconfigured so
that each type of node is assigned to a specific group ID. For the easiest setup, let the group
with the fewest nodes be assigned under the WHEN clause and the group with most nodes be
assigned via the ELSE clause in the case statement.
Caution:
Do not change or delete columns in these views. If the columns are modified, the resource
usage macros that use these views may not work properly. You can, however, safely add
columns.
Resource Usage Macros and Tables
147
148
ResGeneralInfoView
ResGeneralInfoView provides an overview of system operation.
Note: The data columns in this view will change as the columns in the ResUsageSpma table change.
REPLACE VIEW DBC.ResGeneralInfoView
AS SELECT
/* housekeeping fields */
TheDate, TheTime,
NodeId (FORMAT '999-99') AS NodeId,
CASE
WHEN NodeId IN ('001-01', '001-03', '001-05') THEN 'A'
WHEN NodeId IN ('001-02', '001-04', '001-06') THEN 'A'
ELSE 'A'
END AS GroupId,
GmtTime,
NodeType,
NodeNormFactor,
NCPUs,
Vproc1,
VprocType1,
Vproc2,
VprocType2,
Vproc3,
VprocType3,
Vproc4,
VprocType4,
Vproc5,
VprocType5,
Vproc6,
VprocType6,
Vproc7,
VprocType7,
MemSize,
Secs,
CentiSecs,
NominalSecs,
CollectIntervals,
Reserved,
Resource Usage Macros and Tables
/* transformed fields */
( (CPUUServ + CPUUExec) / NULLIFZERO(NCPUs) ) AS CPUBusy,
( CPUUServ / NULLIFZERO(NCPUs) )
AS CPUOpSys,
( CPUUExec / NULLIFZERO(NCPUs) )
AS CPUUser,
( CPUIoWait / NULLIFZERO(NCPUs) )
AS CPUWaitIO,
( (CPUUServ + CPUUExec) * (NodeNormFactor / 100)/ NULLIFZERO(NCPUs) ) AS CPUBusyNorm,
( CPUUServ * (NodeNormFactor / 100) / NULLIFZERO(NCPUs) )
AS CPUOpSysNorm,
( CPUUExec * (NodeNormFactor / 100) / NULLIFZERO(NCPUs) )
AS CPUUserNorm,
( CPUIoWait* (NodeNormFactor / 100) / NULLIFZERO(NCPUs) )
AS CPUWaitIONorm,
( FileAcqReads + FilePreReads + FileWrites ) AS DiskSegmentIO,
( FileAcqReads
+ FilePreReads
+ FileWrites
+
MemTextPageReads + MemCtxtPageReads + MemCtxtPageWrites +
MemSwapReads ) AS LogicalDeviceIO,
( FileAcqReads + FilePreReads +
MemTextPageReads + MemCtxtPageReads + MemSwapReads ) AS LogicalDeviceReads,
( FileWrites + MemCtxtPageWrites ) AS LogicalDeviceWrites,
( FileAcqReadKB + FilePreReadKB +
Resource Usage Macros and Tables
/* paging or swapping count times pagesize (= 4K) */
(MemTextPageReads + MemCtxtPageReads + MemSwapReads) * 4 ) AS LogicalDeviceReadKB,
( FileWriteKB +
/* paging or swapping count times pagesize (= 4K) */
MemCtxtPageWrites * 4 ) AS LogicalDeviceWriteKB,
( NetTxCircPtP
+ NetTxCircBrd ) (FORMAT '------9') AS NetAttempts,
( NetCircBackoffs ) (FORMAT '------9')
AS NetBackoffs,
0 AS NetChannelSR,
( NetMsgBrdReads
+ NetMsgBrdWrites )
AS NetMultiIO,
( NetMsgPtPReads
+ NetMsgPtPWrites )
AS NetPtoPIO,
( NetMsgBrdReadKB + NetMsgPtPReadKB )
AS NetReadKB,
( NetMsgBrdReads
+ NetMsgPtPReads )
AS NetReads,
( NetMsgBrdWriteKB + NetMsgPtPWriteKB )
AS NetWriteKB,
( NetMsgBrdWrites + NetMsgPtPWrites )
AS NetWrites,
( MemTextPageReads + MemCtxtPageReads + MemCtxtPageWrites + MemSwapReads ) AS PageOrSwapIO,
( ProcBlockedSum + ProcReadySum + ProcRunningSum )/NULLIFZERO(CollectIntervals) AS ProcActiveAvg,
ProcBlockedSum/NULLIFZERO(CollectIntervals) (FORMAT '------9') AS ProcBlockedAvg,
( ProcBlksDBLock + ProcBlksMemAlloc
+ ProcBlksMisc
+
ProcBlksMonitor + ProcBlksMonResume
+
ProcBlksNetThrottle
+
ProcBlksSegLock + ProcBlksFsgLock
+
ProcBlksFsgRead + ProcBlksFsgWrite ) (FORMAT '------9')
AS ProcBlocks,
( ProcWaitDBLock + ProcWaitMemAlloc
+ ProcWaitMisc
+
ProcWaitMonitor + ProcWaitMonResume
+
ProcWaitNetThrottle + ProcWaitPageRead +
ProcWaitSegLock + ProcWaitFsgLock
+
ProcWaitFsgRead + ProcWaitFsgWrite ) (FORMAT '------9')
AS ProcWaits,
( CmdDDLStmts
+ CmdDeleteStmts + CmdInsertStmts + CmdSelectStmts +
CmdUpdateStmts + CmdUtilityStmts + CmdOtherStmts )
AS UserStmtsArriving,
CmdStmtsInProgCur AS UserStmtsInProgress,
/* TVS Teradata Virtual Storage fields will be renamed in the table in the 14.0 release */
VssReadCnt
AS TvsReadCnt,
VssWriteCnt
AS TvsWriteCnt,
VssReadRespTot
AS TvsReadRespTot,
VssWriteRespTot
AS TvsWriteRespTot,
/* Spare Field Usage */
SpareCount00
AS TvsReadMax,
SpareCount01
AS TvsWriteMax,
SpareTmon00
AS COD, /* 14.0 hdr field Capacity On Demand factor */
149
/* SPMA table fields */
Active,
ProcReadySum,
ProcBlockedSum,
ProcSuspendedSum,
ProcRunningSum,
NetSemInUseSum,
NetChanInUseSum,
NetGroupInUseSum,
ProcReadyMax,
ProcPendMemAlloc,
ProcPendFsgRead,
ProcPendFsgWrite,
ProcPendNetThrottle,
ProcPendNetRead,
ProcPendMonitor,
ProcPendMonResume,
ProcPendDBLock,
150
Resource Usage Macros and Tables
ProcPendSegLock,
ProcPendMisc,
ProcPendFsgLock,
ProcPendQnl,
ProcBlksMemAlloc,
ProcBlksFsgRead,
ProcBlksFsgWrite,
ProcBlksNetThrottle,
ProcBlksMsgRead,
ProcBlksMonitor,
ProcBlksMonResume,
ProcBlksDBLock,
ProcBlksSegLock,
ProcBlksTime,
ProcBlksMisc,
ProcBlksFsgLock,
ProcBlksQnl,
ProcWaitMemAlloc,
ProcWaitPageRead,
ProcWaitFsgRead,
ProcWaitFsgWrite,
ProcWaitNetThrottle,
ProcWaitMsgRead,
ProcWaitMonitor,
ProcWaitMonResume,
ProcWaitDBLock,
ProcWaitSegLock,
ProcWaitTime,
ProcWaitMisc,
ProcWaitFsgLock,
ProcWaitQnl,
CPUIdle,
CPUIoWait,
CPUUServ,
CPUUExec,
CPUIdleNorm,
CPUIoWaitNorm,
CPUUServNorm,
CPUUExecNorm,
MemTextAllocs,
MemVprAllocs,
MemVprAllocKB,
MemTSysOhRes,
MemDSysOhRes,
MemTextRes,
MemCtxtRes,
MemPDbKBRes,
MemPCiKBRes,
MemSDbKBRes,
MemSCiKBRes,
MemTJtKBRes,
MemAPtKBRes,
MemFreeKB,
MemFails,
MemAgings,
MemTextPageDrops,
MemTextPageReads,
MemProcSwapped,
MemCtxtPageWrites,
MemCtxtPageReads,
MemSwapDrops,
MemSwapDropKB,
MemSwapReads,
Resource Usage Macros and Tables
151
MemSwapReadKB,
MsgPtPReads,
MsgPtPWrites,
MsgPtPReadKB,
MsgPtPWriteKB,
MsgBrdReads,
MsgBrdWrites,
MsgBrdReadKB,
MsgBrdWriteKB,
NetTxRouting,
NetTxConnected,
NetRxConnected,
NetTxIdle,
NetRxIdle,
NetSamples,
NetMsgPtPWriteKB,
NetMsgBrdWriteKB,
NetMsgPtPReadKB,
NetMsgBrdReadKB,
NetMsgPtPWrites,
NetMsgBrdWrites,
NetMsgPtPReads,
NetMsgBrdReads,
NetTxCircHPBrd,
NetRxCircPtP,
NetTxCircHPPtP,
NetRxKBPtP,
NetTxKBPtP,
NetRxCircBrd,
NetTxCircBrd,
NetRxKBBrd,
NetTxKBBrd,
NetCircAttempts,
NetCircBackoffs,
NetSemInUseMax,
NetChanInUseMax,
NetGroupInUseMax,
NetHWBackoffs,
NetMrgTxKB,
NetMrgRxKB,
NetMrgTxRows,
NetTxCircPtP,
NetMrgRxRows,
HostBlockReads,
HostBlockWrites,
HostMessageReads,
HostMessageWrites,
HostReadKB,
HostWriteKB,
DBLockBlocks,
DBLockDeadlocks,
FileAcqs,
FileAcqKB,
FileAcqReads,
FileAcqReadKB,
FileRels,
FileRelKB,
FileWrites,
FileWriteKB,
FilePres,
FilePreKB,
FilePreReads,
FilePreReadKB,
152
FileLockBlocks,
FileLockDeadlocks,
FileLockEnters,
FileSmallDepotWrites,
FileLargeDepotWrites,
FileLargeDepotBlocks,
MsgChnLastDone,
CmdDDLStmts,
CmdDeleteStmts,
CmdInsertStmts,
CmdSelectStmts,
CmdUpdateStmts,
CmdUtilityStmts,
CmdOtherStmts,
CmdStmtsInProgCur,
CmdStmtSuccesses,
CmdStmtFailures,
CmdStmtErrors,
CmdStmtTime,
AwtFlowControlled,
AwtFlowCtlCnt,
AwtInuse,
AwtInuseMax,
PSNumRequests,
PSQWaitTime,
PSServiceTime,
SpareCount00,
SpareCount01,
SpareCount02,
SpareCount03,
SpareTrack00,
SpareTrack01,
SpareTrack02,
SpareTrack03,
SpareTmon00,
SpareTmon01,
SpareTmon02,
SpareTmon03
FROM ResUsageSpma WITH CHECK OPTION;
COMMENT ON VIEW DBC.ResGeneralInfoView AS
'View of general system information';
Resource Usage Macros and Tables
ResCPUUsageByAMPView
ResCPUUsageByAMPView describes CPU usage per AMP.
REPLACE VIEW DBC.ResCPUUsageByAMPView
( TheDate, TheTime, Vproc, NodeId, Secs, NCPUs, GroupId,
AMPWorkTaskExec, AMPWorkTaskServ,
AMPMiscUserExec, AMPMiscUserServ,
AMPTotalUserExec, AMPTotalUserServ )
AS SELECT TheDate, TheTime, VprId, NodeID, Secs, NCPUs,
/* GroupId */
Resource Usage Macros and Tables
CASE
WHEN NodeId IN ('001-01', '001-03', '001-05') THEN 'A '
WHEN NodeId IN ('001-02', '001-04', '001-06') THEN 'A'
ELSE 'A'
END,
/* AMPWorkTaskExec */
CPUUExecPart11,
/* AMPWorkTaskServ */
CPUUServPart11,
/* AMPMiscUserExec*/
(
CPUUExecPart01+CPUUExecPart02+CPUUExecPart03 +
CPUUExecPart04+CPUUExecPart05+CPUUExecPart06+CPUUExecPart07 +
CPUUExecPart08+CPUUExecPart09+CPUUExecPart10
+
CPUUExecPart12+CPUUExecPart13+CPUUExecPart14+CPUUExecPart15 +
CPUUExecPart16+CPUUExecPart17+CPUUExecPart18+CPUUExecPart19 +
CPUUExecPart20+CPUUExecPart21+CPUUExecPart22+CPUUExecPart23 +
CPUUExecPart24+CPUUExecPart25+CPUUExecPart26+CPUUExecPart27 +
CPUUExecPart28+CPUUExecPart29+CPUUExecPart30+CPUUExecPart31 +
CPUUExecPart32+CPUUExecPart33+CPUUExecPart34+CPUUExecPart35 +
CPUUExecPart36+CPUUExecPart37+CPUUExecPart38+CPUUExecPart39 +
CPUUExecPart40+CPUUExecPart41+CPUUExecPart42+CPUUExecPart43 +
CPUUExecPart44+CPUUExecPart45+CPUUExecPart46+CPUUExecPart47),
/* AMPMiscUserServ */
(
CPUUServPart01+CPUUServPart02+CPUUServPart03 +
CPUUServPart04+CPUUServPart05+CPUUServPart06+CPUUServPart07 +
CPUUServPart08+CPUUServPart09+CPUUServPart10
+
CPUUServPart12+CPUUServPart13+CPUUServPart14+CPUUServPart15 +
CPUUServPart16+CPUUServPart17+CPUUServPart18+CPUUServPart19 +
CPUUServPart20+CPUUServPart21+CPUUServPart22+CPUUServPart23 +
CPUUServPart24+CPUUServPart25+CPUUServPart26+CPUUServPart27 +
CPUUServPart28+CPUUServPart29+CPUUServPart30+CPUUServPart31 +
CPUUServPart32+CPUUServPart33+CPUUServPart34+CPUUServPart35 +
CPUUServPart36+CPUUServPart37+CPUUServPart38+CPUUServPart39 +
CPUUServPart40+CPUUServPart41+CPUUServPart42+CPUUServPart43 +
CPUUServPart44+CPUUServPart45+CPUUServPart46+CPUUServPart47),
/* AMPTotalUserExec */
(CPUUExecPart00+CPUUExecPart01+CPUUExecPart02+CPUUExecPart03 +
CPUUExecPart04+CPUUExecPart05+CPUUExecPart06+CPUUExecPart07 +
CPUUExecPart08+CPUUExecPart09+CPUUExecPart10+CPUUExecPart11 +
CPUUExecPart12+CPUUExecPart13+CPUUExecPart14+CPUUExecPart15 +
CPUUExecPart16+CPUUExecPart17+CPUUExecPart18+CPUUExecPart19 +
CPUUExecPart20+CPUUExecPart21+CPUUExecPart22+CPUUExecPart23 +
CPUUExecPart24+CPUUExecPart25+CPUUExecPart26+CPUUExecPart27 +
CPUUExecPart28+CPUUExecPart29+CPUUExecPart30+CPUUExecPart31 +
CPUUExecPart32+CPUUExecPart33+CPUUExecPart34+CPUUExecPart35 +
CPUUExecPart36+CPUUExecPart37+CPUUExecPart38+CPUUExecPart39 +
CPUUExecPart40+CPUUExecPart41+CPUUExecPart42+CPUUExecPart43 +
CPUUExecPart44+CPUUExecPart45+CPUUExecPart46+CPUUExecPart47),
/* AMPTotalUserServ */
(CPUUServPart00+CPUUServPart01+CPUUServPart02+CPUUServPart03 +
CPUUServPart04+CPUUServPart05+CPUUServPart06+CPUUServPart07 +
CPUUServPart08+CPUUServPart09+CPUUServPart10+CPUUServPart11 +
CPUUServPart12+CPUUServPart13+CPUUServPart14+CPUUServPart15 +
CPUUServPart16+CPUUServPart17+CPUUServPart18+CPUUServPart19 +
CPUUServPart20+CPUUServPart21+CPUUServPart22+CPUUServPart23 +
CPUUServPart24+CPUUServPart25+CPUUServPart26+CPUUServPart27 +
CPUUServPart28+CPUUServPart29+CPUUServPart30+CPUUServPart31 +
CPUUServPart32+CPUUServPart33+CPUUServPart34+CPUUServPart35 +
CPUUServPart36+CPUUServPart37+CPUUServPart38+CPUUServPart39 +
CPUUServPart40+CPUUServPart41+CPUUServPart42+CPUUServPart43 +
CPUUServPart44+CPUUServPart45+CPUUServPart46+CPUUServPart47)
153
FROM ResUsageSvpr WHERE VprType like 'AMP%' WITH CHECK OPTION;
154
ResCPUUsageByPEView
ResCPUUsageByPEView describes CPU usage by each PE.
REPLACE VIEW DBC.ResCPUUsageByPEView
( TheDate, TheTime, Vproc, NodeId, Secs, NCPUs, GroupId,
PEDispExec, PEDispServ, PEParsExec, PEParsServ, PESessExec, PESessServ,
PEMiscUserExec, PEMiscUserServ, PETotalUserExec, PETotalUserServ )
Resource Usage Macros and Tables
AS SELECT TheDate, TheTime, VprId, NodeID(FORMAT'999-99'), Secs, NCPUs,
/* GroupId */
CASE
WHEN NodeId IN ('001-01', '001-03', '001-05') THEN 'A '
WHEN NodeId IN ('001-02', '001-04', '001-06') THEN 'A'
ELSE 'A'
END,
/* PEDispExec */
CPUUExecPart13,
/* PEDispServ */
CPUUServPart13,
/* PEParsExec */
CPUUExecPart14,
/* PEParsServ */
CPUUServPart14,
/* PESessExec */
CPUUExecPart12,
/* PESessServ */
CPUUServPart12,
/* PEMiscUserExec */
(
CPUUExecPart01+CPUUExecPart02+CPUUExecPart03 +
CPUUExecPart04+CPUUExecPart05+CPUUExecPart06+CPUUExecPart07 +
CPUUExecPart08+CPUUExecPart09+CPUUExecPart10+CPUUExecPart11 +
CPUUExecPart15 +
CPUUExecPart16+CPUUExecPart17+CPUUExecPart18+CPUUExecPart19 +
CPUUExecPart20+CPUUExecPart21+CPUUExecPart22+CPUUExecPart23 +
CPUUExecPart24+CPUUExecPart25+CPUUExecPart26+CPUUExecPart27 +
CPUUExecPart28+CPUUExecPart29+CPUUExecPart30+CPUUExecPart31 +
CPUUExecPart32+CPUUExecPart33+CPUUExecPart34+CPUUExecPart35 +
CPUUExecPart36+CPUUExecPart37+CPUUExecPart38+CPUUExecPart39 +
CPUUExecPart40+CPUUExecPart41+CPUUExecPart42+CPUUExecPart43 +
CPUUExecPart44+CPUUExecPart45+CPUUExecPart46+CPUUExecPart47),
/* PEMiscUserServ */
(
CPUUServPart01+CPUUServPart02+CPUUServPart03 +
CPUUServPart04+CPUUServPart05+CPUUServPart06+CPUUServPart07 +
CPUUServPart08+CPUUServPart09+CPUUServPart10+CPUUServPart11 +
CPUUServPart15 +
CPUUServPart16+CPUUServPart17+CPUUServPart18+CPUUServPart19 +
CPUUServPart20+CPUUServPart21+CPUUServPart22+CPUUServPart23 +
CPUUServPart24+CPUUServPart25+CPUUServPart26+CPUUServPart27 +
CPUUServPart28+CPUUServPart29+CPUUServPart30+CPUUServPart31 +
CPUUServPart32+CPUUServPart33+CPUUServPart34+CPUUServPart35 +
CPUUServPart36+CPUUServPart37+CPUUServPart38+CPUUServPart39 +
CPUUServPart40+CPUUServPart41+CPUUServPart42+CPUUServPart43 +
CPUUServPart44+CPUUServPart45+CPUUServPart46+CPUUServPart47),
/* PETotalUserExec */
(CPUUExecPart00+CPUUExecPart01+CPUUExecPart02+CPUUExecPart03 +
CPUUExecPart04+CPUUExecPart05+CPUUExecPart06+CPUUExecPart07 +
CPUUExecPart08+CPUUExecPart09+CPUUExecPart10+CPUUExecPart11 +
CPUUExecPart12+CPUUExecPart13+CPUUExecPart14+CPUUExecPart15 +
Resource Usage Macros and Tables
CPUUExecPart16+CPUUExecPart17+CPUUExecPart18+CPUUExecPart19 +
CPUUExecPart20+CPUUExecPart21+CPUUExecPart22+CPUUExecPart23 +
CPUUExecPart24+CPUUExecPart25+CPUUExecPart26+CPUUExecPart27 +
CPUUExecPart28+CPUUExecPart29+CPUUExecPart30+CPUUExecPart31 +
CPUUExecPart32+CPUUExecPart33+CPUUExecPart34+CPUUExecPart35 +
CPUUExecPart36+CPUUExecPart37+CPUUExecPart38+CPUUExecPart39 +
CPUUExecPart40+CPUUExecPart41+CPUUExecPart42+CPUUExecPart43 +
CPUUExecPart44+CPUUExecPart45+CPUUExecPart46+CPUUExecPart47),
/* PETotalUserServ */
(CPUUServPart00+CPUUServPart01+CPUUServPart02+CPUUServPart03 +
CPUUServPart04+CPUUServPart05+CPUUServPart06+CPUUServPart07 +
CPUUServPart08+CPUUServPart09+CPUUServPart10+CPUUServPart11 +
CPUUServPart12+CPUUServPart13+CPUUServPart14+CPUUServPart15 +
CPUUServPart16+CPUUServPart17+CPUUServPart18+CPUUServPart19 +
CPUUServPart20+CPUUServPart21+CPUUServPart22+CPUUServPart23 +
CPUUServPart24+CPUUServPart25+CPUUServPart26+CPUUServPart27 +
CPUUServPart28+CPUUServPart29+CPUUServPart30+CPUUServPart31 +
CPUUServPart32+CPUUServPart33+CPUUServPart34+CPUUServPart35 +
CPUUServPart36+CPUUServPart37+CPUUServPart38+CPUUServPart39 +
CPUUServPart40+CPUUServPart41+CPUUServPart42+CPUUServPart43 +
CPUUServPart44+CPUUServPart45+CPUUServPart46+CPUUServPart47)
FROM ResUsageSvpr WHERE VprType like 'PE%' WITH CHECK OPTION;
ResSawtView
ResSawtView is based on the ResUsageSawt table.
REPLACE VIEW DBC.ResSawtView
AS SELECT
/* housekeeping fields */
TheDate, TheTime,
NodeId (FORMAT '999-99') AS NodeId,
CASE
/* Coexistence reporting support */
WHEN NodeId IN ('001-01', '001-03', '001-05') THEN 'A'
WHEN NodeId IN ('001-02', '001-04', '001-06') THEN 'A'
ELSE 'A'
END AS GroupId,
NodeType,
GmtTime,
Secs,
CentiSecs,
NominalSecs,
CollectIntervals,
VprId,
SummaryFlag,
Reserved,
/* Spare Field usage */
SpareCount02
AS
SpareCount03
AS
SpareTmon00
AS
Available,
AvailableMin,
COD, /* Capacity On Demand */
155
/* transformed fields */
MailBoxDepth/CollectIntervals
AS MailBoxDepthAvg,
156
( WorkTypeInuse00
WorkTypeInuse04
WorkTypeInuse08
WorkTypeInuse12
+
+
+
+
WorkTypeInuse01
WorkTypeInuse05
WorkTypeInuse09
WorkTypeInuse13
AS
WorkTypeInuse00/CollectIntervals
WorkTypeInuse01/CollectIntervals
WorkTypeInuse02/CollectIntervals
WorkTypeInuse03/CollectIntervals
WorkTypeInuse04/CollectIntervals
WorkTypeInuse05/CollectIntervals
WorkTypeInuse06/CollectIntervals
WorkTypeInuse07/CollectIntervals
WorkTypeInuse08/CollectIntervals
WorkTypeInuse09/CollectIntervals
WorkTypeInuse10/CollectIntervals
WorkTypeInuse11/CollectIntervals
WorkTypeInuse12/CollectIntervals
WorkTypeInuse13/CollectIntervals
WorkTypeInuse14/CollectIntervals
WorkTypeInuse15/CollectIntervals
Resource Usage Macros and Tables
/* Remaining table fields */
Active,
MailBoxDepth,
FlowControlled,
FlowCtlCnt,
FlowCtlTime,
InuseMax,
WorkTypeInuse00,
WorkTypeInuse01,
WorkTypeInuse02,
WorkTypeInuse03,
WorkTypeInuse04,
WorkTypeInuse05,
WorkTypeInuse06,
WorkTypeInuse07,
WorkTypeInuse08,
WorkTypeInuse09,
WorkTypeInuse10,
WorkTypeInuse11,
WorkTypeInuse12,
WorkTypeInuse13,
WorkTypeInuse14,
WorkTypeInuse15,
WorkTypeMax00,
WorkTypeMax01,
WorkTypeMax02,
WorkTypeMax03,
WorkTypeMax04,
WorkTypeMax05,
WorkTypeMax06,
WorkTypeMax07,
WorkTypeMax08,
WorkTypeMax09,
WorkTypeMax10,
WorkTypeMax11,
WorkTypeMax12,
WorkTypeMax13,
WorkTypeMax14,
WorkTypeMax15,
AS
AS
AS
AS
AS
AS
AS
AS
AS
AS
AS
AS
AS
AS
AS
AS
+ WorkTypeInuse02
+ WorkTypeInuse06
+ WorkTypeInuse10
+ WorkTypeInuse14
WorkTypeInuseAvg,
+
+
+
+
WorkTypeInuse00Avg,
WorkTypeInuse01Avg,
WorkTypeInuse02Avg,
WorkTypeInuse03Avg,
WorkTypeInuse04Avg,
WorkTypeInuse05Avg,
WorkTypeInuse06Avg,
WorkTypeInuse07Avg,
WorkTypeInuse08Avg,
WorkTypeInuse09Avg,
WorkTypeInuse10Avg,
WorkTypeInuse11Avg,
WorkTypeInuse12Avg,
WorkTypeInuse13Avg,
WorkTypeInuse14Avg,
WorkTypeInuse15Avg,
WorkTypeInuse03
WorkTypeInuse07
WorkTypeInuse11
WorkTypeInuse15
+
+
+
) / CollectIntervals
Resource Usage Macros and Tables
SpareCount00,
SpareCount01,
SpareCount02,
SpareCount03,
SpareCount04,
SpareCount05,
SpareCount06,
SpareCount07,
SpareCount08,
SpareCount09,
SpareTrack00,
SpareTrack01,
SpareTrack02,
SpareTrack03,
SpareTrack04,
SpareTrack05,
SpareTrack06,
SpareTrack07,
SpareTrack08,
SpareTrack09,
SpareTmon00,
SpareTmon01,
SpareTmon02,
SpareTmon03,
SpareTmon04,
SpareTmon05,
SpareTmon06,
SpareTmon07,
SpareTmon08,
SpareTmon09
FROM ResUsageSawt WITH CHECK OPTION;
COMMENT ON VIEW DBC.ResSawtView AS
'View of Sawt table data';
ResShstGroupView
ResShstGroupView is based on the ResUsageShst table.
REPLACE VIEW DBC.ResShstGroupView
( TheDate, TheTime, NodeId, VprId, HstId, HstType, Secs, NominalSecs,
GroupId, CollectIntervals,
HostBlockReads, HostBlockWrites,
HostMessageReads, HostMessageWrites,
HostReadKB, HostWriteKB,
HostQLenSum, HostQLenMax,
HostReadFails, HostWriteFails
)
157
AS SELECT TheDate, TheTime, NodeId, VprId, HstId, HstType, Secs,
/* GroupId */
CASE
WHEN NodeId IN ('001-01', '001-03', '001-05') THEN 'A '
WHEN NodeId IN ('001-02', '001-04', '001-06') THEN 'A'
ELSE 'A'
END,
NominalSecs,
158
CollectIntervals,
HostBlockReads, HostBlockWrites,
HostMessageReads, HostMessageWrites,
HostReadKB, HostWriteKB,
HostQLenSum, HostQLenMax,
HostReadFails, HostWriteFails
FROM
ResUsageShst
WITH CHECK OPTION;
ResSldvGroupView
ResSldvGroupView is based on the ResUsageSldv table.
REPLACE VIEW DBC.ResSldvGroupView
( TheDate, TheTime, NodeId, VprId, LdvId, LdvType, Secs, NominalSecs,
GroupId, CollectIntervals,
LdvOutReqSum,
LdvReads, LdvWrites,
LdvReadKB, LdvWriteKB,
LdvReadRespTot, LdvWriteRespTot,
LdvReadRespMax, LdvWriteRespMax,
LdvConcurrentMax, LdvOutReqMax, LdvOutReqTime
)
Resource Usage Macros and Tables
AS SELECT TheDate, TheTime, NodeId, VprId, LdvId, LdvType, Secs, NominalSecs,
/* GroupId */
CASE
WHEN NodeId IN ('001-01', '001-03', '001-05') THEN 'A'
WHEN NodeId IN ('001-02', '001-04', '001-06') THEN 'A'
ELSE 'A'
END,
CollectIntervals,
LdvOutReqSum,
LdvReads,
LdvWrites,
LdvReadKB,
LdvWriteKB,
LdvReadRespTot,
LdvWriteRespTot,
LdvReadRespMax,
LdvWriteRespMax,
LdvConcurrentMax,
LdvOutReqMax,
LdvOutReqTime
FROM ResUsageSldv WITH CHECK OPTION;
Resource Usage Macros and Tables
ResSpsView
ResSpsView is based on the ResUsageSps table.
show view ResSpsView;
REPLACE VIEW DBC.ResSpsView
AS SELECT
/* housekeeping fields */
TheDate, TheTime,
NodeId (FORMAT '999-99') AS NodeId,
CASE
/* Coexistence reporting support */
WHEN NodeId IN ('001-01', '001-03', '001-05') THEN 'A'
WHEN NodeId IN ('001-02', '001-04', '001-06') THEN 'A'
ELSE 'A'
END AS GroupId,
NodeType,
NCPUs,
GmtTime,
Secs,
CentiSecs,
NominalSecs,
CollectIntervals,
PGid,
PPid,
VprId,
VprType,
SummaryFlag,
159
/* Spare Field usage */
/*
* WorkTimeInuse reports the service time consummed by a WD during the current
*
reporting interval. This is not the running sum of a WD that
*
exists over multiple intervals.
*
Average AWTs used = WorkTimeInuse/(Centisecs*10)
* WorkTimeInuseMax reports the maximum service time of a single task in a WD
*
that is still running or has finished in the current reporting
*
interval. This includes time used during previous intervals for
*
that task. This value may be much larger than the reporting period.
* ServiceTime
reports the time it took a WD to be serviced and is
*
reported when the AWT is released (task is done).
* ServiceTimeMax reports the maximum time it took a single task in a WD
*
to be serviced that has completed in this reporting interval.
* AwtReleases
reports the number of AWTs released (completed requests)
*
while NumRequests reports number that arrived.
*/
/* Total delay time of messages successfully sent to the workbox */
SpareCount00
AS WorkMsgSendDelay,
/* Longest delay of messages successfully sent to the workbox */
SpareCount01
AS WorkMsgSendDelayMax,
/* be the total delay time of messages still waiting for AWTs.*/
/* So that would be SpareCount02
*/
SpareCount02
AS WorkMsgReceiveDelay,
SpareCount03
AS WorkMsgReceiveDelayMax,
SpareCount04
AS WorkTimeInuse,
/* Average number of AWTs used based on WorkTimeInuse
*/
SpareCount04/(Centisecs*10)
AS AwtUsedAvg,
SpareCount05
AS WorkTimeInuseMax,
160
/* 13.1 AwtReleases
*/
SpareCount06
AS AwtReleases,
/* number of messages accumulating the send side delay time */
SpareCount07
AS WorkMsgSendDelayCnt,
/* number of messages accumulating the receive side delay time */
SpareCount08
AS WorkMsgReceiveDelayCnt,
SpareTrack00
AS AMPcount, /* housekeeping field in 14.0 */
/* Capacity On Demand factor. housekeeping field in 14.0 */
SpareTmon00
AS COD,
/* transformed fields */
(CpuTime * 10)/(CentiSecs * NCPUs)
AS CpuPct,
/* report average wait time per request for messages */
/* already delivered to AWTs
*/
QWaitTime / NULLIFZERO(NumRequests)
AS QWaitTimeRequestAvg,
QLength / ( SpareTrack00 * CollectIntervals ) AS QLengthAmpAvg,
/* Avg delay for msgs delivered in period per Request
*/
WorkMsgSendDelay / NULLIFZERO(WorkMsgSendDelayCnt)
AS WorkMsgSendDelayRequestAvg,
/* requested by Anita Richards to match WorkMsgSendDelayRequestAvg */
/* avg delay per request on receive side for messages not */
/* yet delivered to AWTs
*/
WorkMsgReceiveDelay / NULLIFZERO(WorkMsgReceiveDelayCnt)
AS WorkMsgReceiveDelayRequestAvg,
/* report average service time per request */
ServiceTime / NULLIFZERO(AwtReleases)
AS ServiceTimeRequestAvg,
(CPUUServAWT + CPUUServDisp + CPUUServMisc)
AS CPUUServ,
(CPUUExecAWT + CPUUExecDisp + CPUUExecMisc)
AS CPUUExec,
/* All WorkTypes in use, averaged per AMP */
(WorkTypeInuse00 + WorkTypeInuse01 + WorkTypeInuse02 + WorkTypeInuse03 +
WorkTypeInuse04 + WorkTypeInuse05 + WorkTypeInuse06 + WorkTypeInuse07 +
WorkTypeInuse08 + WorkTypeInuse09 + WorkTypeInuse10 + WorkTypeInuse11 +
WorkTypeInuse12 + WorkTypeInuse13 + WorkTypeInuse14 + WorkTypeInuse15)
/ ( SpareTrack00 * CollectIntervals )
AS WorkTypeInuseAmp,
/* Max of (WorkTypesInuse for all AMPs (NOT per AMP)
*/
/* Can NOT divide by AMPs. MAX(SUM(AWT[AMP]))
*/
(WorkTypeMax00 + WorkTypeMax01 + WorkTypeMax02 + WorkTypeMax03 +
WorkTypeMax04 + WorkTypeMax05 + WorkTypeMax06 + WorkTypeMax07 +
WorkTypeMax08 + WorkTypeMax09 + WorkTypeMax10 + WorkTypeMax11 +
WorkTypeMax12 + WorkTypeMax13 + WorkTypeMax14 + WorkTypeMax15)
AS WorkTypeInuseMax,
Resource Usage Macros and Tables
(ProcBlksFsgRead + ProcBlksFsgWrite + ProcBlksFsgNIOs) AS IODelay,
(ProcWaitFsgRead + ProcWaitFsgWrite + ProcWaitFsgNIOs) AS IODelayTime,
(FilePDbAcqs + FilePDbPres)
AS LogicalReadPerm,
FilePDbDyRRels
AS LogicalWritePerm,
(FilePDbAcqReads + FilePDbPreReads)
AS PhysicalReadPerm,
FilePDbFWrites
AS PhysicalWritePerm,
FilePDbFWriteKB
AS PhysicalWritePermKB,
(NetPtPReads + NetBrdReads)
AS NetReads,
(NetPtPWrites + NetBrdWrites)
AS NetWrites,
(FilePCiAcqs + FileSDbAcqs + FileSCiAcqs + FileTJtAcqs + FileAPtAcqs +
FilePCiPres + FileSDbPres + FileSCiPres + FileTJtPres + FileAPtPres)
AS LogicalReadOther,
(FilePCiAcqReads + FileSDbAcqReads + FileSCiAcqReads + FileTJtAcqReads + FileAPtAcqReads +
FilePCiPreReads + FileSDbPreReads + FileSCiPreReads + FileTJtPreReads + FileAPtPreReads)
AS PhysicalReadOther,
(FilePCiDyRRels + FileSDbDyRRels + FileSCiDyRRels + FileTJtDyRRels + FileAPtDyRRels)
Resource Usage Macros and Tables
AS LogicalWriteOther,
+ FileSCiFWrites + FileTJtFWrites + FileAPtFWrites)
AS PhysicalWriteOther,
(FilePCiFWriteKB + FileSDbFWriteKB + FileSCiFWriteKB + FileTJtFWriteKB + FileAPtFWriteKB)
AS PhysicalWriteOtherKB,
(FilePCiFWrites
( FilePDbAcqKB
( FileSDbAcqKB
FilePCiAcqKB
FilePCiPresKB
+ FileSDbFWrites
+
+
+
+
FilePDbPresKB
FileSDbPresKB
FileSCiAcqKB
FileSCiPresKB
)
AS LogicalReadPermKB,
+
+ FileTJtAcqKB + FileAPtAcqKB +
+ FileTJtPresKB + FileAPtPresKB)
AS LogicalReadOtherKB,
( FilePDbPreReadKB + FilePDbAcqReadKB )
AS PhysicalReadPermKB,
( FilePCiAcqReadKB + FileSDbAcqReadKB + FileSCiAcqReadKB + FileTJtAcqReadKB + FileAPtAcqReadKB +
FilePCiPreReadKB + FileSDbPreReadKB + FileSCiPreReadKB + FileTJtPreReadKB + FileAPtPreReadKB)
AS PhysicalReadOtherKB,
FilePDbDyRRelKB
AS LogicalWritePermKB,
( FileSDbDyRRelKB +
FilePCiDyRRelKB + FileSCiDyRRelKB + FileTJtDyRRelKB + FileAPtDyRRelKB)
AS LogicalWriteOtherKB,
(ProcBlksSegNoVirtual + ProcBlksSegMDL + ProcBlksSegLock) AS ProcBlksSeg,
(ProcWaitSegNoVirtual + ProcWaitSegMDL + ProcWaitSegLock) AS ProcWaitSeg,
(ProcBlksMisc + ProcBlksNetThrottle + ProcBlksQnl +ProcBlksTime + ProcBlksFlowControl)
AS ProcBlksMisc,
/* ProcBlksMonResume = covered by DBLocks */
(ProcWaitMisc + ProcWaitMonResume + ProcWaitNetThrottle +ProcWaitQnl +
ProcWaitTime + ProcWaitFlowControl)
AS ProcWaitMisc,
161
/*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*/
obsolete Sps table fields removed in 14.0
CPUUServPars,
CPUUExecPars,
FileFcrRequests,
FileFcrRequestsAdaptive,
FileFcrBlocksRead,
FileFcrBlocksDeniedUser,
FileFcrBlocksDeniedKern,
FileFcrBlocksDeniedCache,
FileFcrBlocksDeniedThreshUser,
FileFcrDeniedUser,
FileFcrDeniedKern,
FileFcrDeniedCache,
FileFcrDeniedThreshUser,
FileCylMigrs,
FileCylAllocs,
FileSyncScans,
FileSyncSubtables,
FileSyncScanners,
FileSyncGroups,
FileWCylAllocs,
FileWCylFrees,
MsgChnLastDone,
MemCtxtAllocs,
MemKBRes,
FlowControlled,
FlowCtlCnt,
AllocatorExtentAllocReqs,
AllocatorExtentFreeReqs,
AllocatorMapIOsStarted,
AllocatorMapIOsDone,
NodeAgentMigrationsStarted,
NodeAgentMigrationsDone,
NodeAgentStatProcessed,
162
/* Remaining table fields */
Active,
WDid,
AGid,
RelWgt,
CpuTime,
IOBlks,
NumProcs,
NumSets,
NumRequests,
QWaitTime,
QWaitTimeMax,
QLength,
QLengthMax,
ServiceTime,
ServiceTimeMax,
Resource Usage Macros and Tables
SpareCount00,
SpareCount01,
SpareCount02,
SpareCount03,
SpareCount04,
SpareCount05,
SpareCount06,
SpareCount07,
SpareCount08,
SpareCount09,
SpareTrack00,
SpareTrack01,
SpareTrack02,
SpareTrack03,
SpareTrack04,
SpareTrack05,
SpareTrack06,
SpareTrack07,
SpareTrack08,
SpareTrack09,
SpareTmon00,
SpareTmon01,
SpareTmon02,
SpareTmon03,
SpareTmon04,
SpareTmon05,
SpareTmon06,
SpareTmon07,
SpareTmon08,
SpareTmon09,
CPUUServAWT,
CPUUServDisp,
CPUUServMisc,
CPUUExecAWT,
CPUUExecDisp,
CPUUExecMisc,
MemAllocs,
MemAllocKB,
/* QWaitTime = wait time of messages delivered. */
/* WorkMsgReceiveDelay in SpareCount02 is wait time of
/* messages still waiting for AWTs.
*/
/*
/*
/*
/*
/*
/*
/*
/*
/*
13.1
13.1
13.1
13.1
13.1
13.1
13.1
13.1
13.1
WorkMsgSendDelay
WorkMsgSendDelayMax
WorkMsgReceiveDelay
WorkMsgReceiveDelayMax
WorkTimeInuse
WorkTimeInuseMax
AwtReleases
WorkMsgSendDelayCnt
WorkMsgReceiveDelayCnt
/* 13.1 AMPcount
/* 14.0:hdr COD: CodFactor */
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
Resource Usage Macros and Tables
/* AWT fields */
WorkTypeInuse00,
WorkTypeInuse01,
WorkTypeInuse02,
WorkTypeInuse03,
WorkTypeInuse04,
WorkTypeInuse05,
WorkTypeInuse06,
WorkTypeInuse07,
WorkTypeInuse08,
WorkTypeInuse09,
WorkTypeInuse10,
WorkTypeInuse11,
WorkTypeInuse12,
WorkTypeInuse13,
WorkTypeInuse14,
WorkTypeInuse15,
WorkTypeMax00,
WorkTypeMax01,
WorkTypeMax02,
WorkTypeMax03,
WorkTypeMax04,
WorkTypeMax05,
WorkTypeMax06,
WorkTypeMax07,
WorkTypeMax08,
WorkTypeMax09,
WorkTypeMax10,
WorkTypeMax11,
WorkTypeMax12,
WorkTypeMax13,
WorkTypeMax14,
WorkTypeMax15,
FilePDbAcqs,
FilePCiAcqs,
FileSDbAcqs,
FileSCiAcqs,
FileTJtAcqs,
FileAPtAcqs,
FilePDbAcqKB,
FilePCiAcqKB,
FileSDbAcqKB,
FileSCiAcqKB,
FileTJtAcqKB,
FileAPtAcqKB,
FilePDbAcqReads,
FilePCiAcqReads,
FileSDbAcqReads,
FileSCiAcqReads,
FileTJtAcqReads,
FileAPtAcqReads,
163
FilePDbAcqReadKB,
FilePCiAcqReadKB,
FileSDbAcqReadKB,
FileSCiAcqReadKB,
FileTJtAcqReadKB,
FileAPtAcqReadKB,
164
FilePDbPres,
FilePCiPres,
FileSDbPres,
FileSCiPres,
FileTJtPres,
FileAPtPres,
FilePDbPresKB,
FilePCiPresKB,
FileSDbPresKB,
FileSCiPresKB,
FileTJtPresKB,
FileAPtPresKB,
FilePDbPreReads,
FilePCiPreReads,
FileSDbPreReads,
FileSCiPreReads,
FileTJtPreReads,
FileAPtPreReads,
FilePDbPreReadKB,
FilePCiPreReadKB,
FileSDbPreReadKB,
FileSCiPreReadKB,
FileTJtPreReadKB,
FileAPtPreReadKB,
FilePDbDyRRels,
FilePCiDyRRels,
FileSDbDyRRels,
FileSCiDyRRels,
FileTJtDyRRels,
FileAPtDyRRels,
FilePDbDyRRelKB,
FilePCiDyRRelKB,
FileSDbDyRRelKB,
FileSCiDyRRelKB,
FileTJtDyRRelKB,
FileAPtDyRRelKB,
Resource Usage Macros and Tables
FilePDbFWrites,
FilePCiFWrites,
FileSDbFWrites,
FileSCiFWrites,
FileTJtFWrites,
FileAPtFWrites,
FilePDbFWriteKB,
FilePCiFWriteKB,
FileSDbFWriteKB,
FileSCiFWriteKB,
FileTJtFWriteKB,
FileAPtFWriteKB,
NetPtPReads,
NetPtPWrites,
NetPtPReadKB,
NetPtPWriteKB,
NetBrdReads,
NetBrdWrites,
Resource Usage Macros and Tables
/* TVSA fields */
ReadsHot,
ReadsWarm,
ReadsCold,
WritesHot,
WritesWarm,
WritesCold,
/* Process blocking reasons: ProcBlks count of blocks */
ProcBlksSegNoVirtual,
ProcBlksFsgNIOs,
ProcBlksSegMDL,
ProcBlksMonResume,
ProcBlksNetThrottle,
ProcBlksQnl,
ProcBlksFsgRead,
ProcBlksFsgWrite,
ProcBlksDBLock,
ProcBlksMonitor,
ProcBlksSegLock,
ProcBlksFsgLock,
ProcBlksTime,
ProcBlksFlowControl,
ProcBlksCpuLimit,
/* Process blocking reasons: ProcWait time in milliseconds */
ProcWaitSegNoVirtual,
ProcWaitFsgNIOs,
ProcWaitSegMDL,
ProcWaitMonResume,
ProcWaitNetThrottle,
ProcWaitQnl,
ProcWaitFsgRead,
ProcWaitFsgWrite,
ProcWaitDBLock,
ProcWaitMonitor,
ProcWaitSegLock,
ProcWaitFsgLock,
ProcWaitTime,
ProcWaitFlowControl,
ProcWaitCpuLimit
FROM ResUsageSps WITH CHECK OPTION;
165
166
ResSvprView
Use the ResSvprView to access the ResUsageSvpr table data. This view allows data to be properly presented and reports all the
columns available from the ResUsageSvpr table.
Note: The data columns in this view will change as the columns in the ResUsageSvpr table change.
REPLACE VIEW DBC.ResSvprView
AS SELECT
/* housekeeping fields */
NodeID,
thedate,
thetime,
GmtTime,
vprid,
VprType,
NodeType,
NCPUs,
Secs,
CentiSecs,
NominalSecs,
CollectIntervals,
SummaryFlag,
Reserved,
/* transformed fields */
/* user defined co-existence system node groupings */
CASE
WHEN NodeId IN ('001-01', '001-03', '001-05') THEN 'A'
WHEN NodeId IN ('001-02', '001-04', '001-06') THEN 'A'
ELSE 'A'
END AS GroupId,
Resource Usage Macros and Tables
/* Spare field usage */
SpareCount00 AS DBMergeTried,
SpareCount01 AS DBMergeDone,
SpareCount02 AS DBMergeElim,
SpareCount03 AS DBMergeExtrIO,
SpareCount04 AS FileACPCylsSkipped,
SpareCount05 AS FileACPCylsMigr,
SpareCount06 AS FileACPCylsUnFSEOnly,
SpareCount07 AS FileACPCylsPostponed,
SpareTmon00
SpareTmon01
SpareTmon02
SpareTmon03
AS
AS
AS
AS
COD,
FSGCacheWaits,
FSGCacheWaitTime,
FSGCacheWaitTimeMax,
/* SVpr table fields (remaining) */
Active,
ProcPendDBLock,
ProcBlksDBLock,
ProcWaitDBLock,
MemPDbAllocs,
MemPCiAllocs,
MemSDbAllocs,
MemSCiAllocs,
Resource Usage Macros and Tables
MemTJtAllocs,
MemAPtAllocs,
MemPDbAllocKB,
MemPCiAllocKB,
MemSDbAllocKB,
MemSCiAllocKB,
MemTJtAllocKB,
MemAPtAllocKB,
MemCtxtAllocs,
MemCtxtRes,
MemPKBResFrz,
MemPDbKBResCU,
MemPCiKBResCU,
MemSDbKBResCU,
MemSCiKBResCU,
MemTJtKBResCU,
MemAPtKBResCU,
MemPDbKBResDU,
MemPCiKBResDU,
MemSDbKBResDU,
MemSCiKBResDU,
MemTJtKBResDU,
MemAPtKBResDU,
MemPDbKBResCA,
MemPCiKBResCA,
MemSDbKBResCA,
MemSCiKBResCA,
MemTJtKBResCA,
MemAPtKBResCA,
MemPDbKBResDA,
MemPCiKBResDA,
MemSDbKBResDA,
MemSCiKBResDA,
MemTJtKBResDA,
MemAPtKBResDA,
MemCtxtPageReads,
MemCtxtPageWrites,
MemSwapDrops,
MemSwapDropKB,
MemSwapReads,
MemSwapReadKB,
MemCtxtAccesses,
MemCtxtAccessKB,
MemCtxtDeaccesses,
MemCtxtDeaccessKB,
MemCtxtDestroys,
MemCtxtDestroyKB,
NetPtPReads,
NetPtPWrites,
NetPtPReadKB,
NetPtPWriteKB,
NetBrdReads,
NetBrdWrites,
NetBrdReadKB,
NetBrdWriteKB,
MsgWorkQLenMax,
DBLockEnters,
DBLockBlocks,
DBLockDeadlocks,
DBLockBlocksMax,
DBLocksHeldMax,
167
FilePDbAcqs,
168
Resource Usage Macros and Tables
FilePCiAcqs,
FileSDbAcqs,
FileSCiAcqs,
FileTJtAcqs,
FileAPtAcqs,
FilePDbAcqKB,
FileSDbAcqKB,
FilePCiAcqKB,
FileSCiAcqKB,
FileTJtAcqKB,
FileAPtAcqKB,
FilePDbAcqReads,
FilePCiAcqReads,
FileSDbAcqReads,
FileSCiAcqReads,
FileTJtAcqReads,
FileAPtAcqReads,
FilePDbAcqReadKB,
FilePCiAcqReadKB,
FileSDbAcqReadKB,
FileSCiAcqReadKB,
FileTJtAcqReadKB,
FileAPtAcqReadKB,
FilePDbPres,
FilePCiPres,
FileSDbPres,
FileSCiPres,
FileTJtPres,
FileAPtPres,
FilePDbPresKB,
FileSDbPresKB,
FilePCiPresKB,
FileSCiPresKB,
FileTJtPresKB,
FileAPtPresKB,
FilePDbPreReads,
FilePCiPreReads,
FileSDbPreReads,
FileSCiPreReads,
FileTJtPreReads,
FileAPtPreReads,
FilePDbPreReadKB,
FileSDbPreReadKB,
FilePCiPreReadKB,
FileSCiPreReadKB,
FileTJtPreReadKB,
FileAPtPreReadKB,
FilePDbDyRRels,
FilePCiDyRRels,
FileSDbDyRRels,
FileSCiDyRRels,
FileTJtDyRRels,
FileAPtDyRRels,
FilePDbDyRRelKB,
FileSDbDyRRelKB,
FilePCiDyRRelKB,
FileSCiDyRRelKB,
FileTJtDyRRelKB,
FileAPtDyRRelKB,
FilePDbFWrites,
FilePCiFWrites,
FileSDbFWrites,
FileSCiFWrites,
Resource Usage Macros and Tables
169
FileTJtFWrites,
FileAPtFWrites,
FilePDbFWriteKB,
FilePCiFWriteKB,
FileSDbFWriteKB,
FileSCiFWriteKB,
FileTJtFWriteKB,
FileAPtFWriteKB,
FilePDbDyAWrites,
FilePCiDyAWrites,
FileSDbDyAWrites,
FileSCiDyAWrites,
FileTJtDyAWrites,
FileAPtDyAWrites,
FilePDbDyAWriteKB,
FilePCiDyAWriteKB,
FileSDbDyAWriteKB,
FileSCiDyAWriteKB,
FileTJtDyAWriteKB,
FileAPtDyAWriteKB,
FilePDbCnRRels,
FilePCiCnRRels,
FileSDbCnRRels,
FileSCiCnRRels,
FileTJtCnRRels,
FileAPtCnRRels,
FilePDbCnRRelKB,
FileSDbCnRRelKB,
FilePCiCnRRelKB,
FileSCiCnRRelKB,
FileTJtCnRRelKB,
FileAPtCnRRelKB,
FilePDbFDrps,
FilePCiFDrps,
FileSDbFDrps,
FileSCiFDrps,
FileTJtFDrps,
FileAPtFDrps,
FilePDbFDrpKB,
FileSDbFDrpKB,
FilePCiFDrpKB,
FileSCiFDrpKB,
FileTJtFDrpKB,
FileAPtFDrpKB,
FilePDbCnADrps,
FilePCiCnADrps,
FileSDbCnADrps,
FileSCiCnADrps,
FileTJtCnADrps,
FileAPtCnADrps,
FilePDbCnADrpKB,
FilePCiCnADrpKB,
FileSDbCnADrpKB,
FileSCiCnADrpKB,
FileTJtCnADrpKB,
FileAPtCnADrpKB,
FileLockEnters,
FileLockBlocks,
FileLockDeadlocks,
FileCylMigrs,
FileCylAllocs,
FileCylFrees,
FileMCylPacks,
170
Resource Usage Macros and Tables
FileCylDefrags,
FileWCylAllocs,
FileWCylFrees,
FileFcrRequests,
FileFcrRequestsAdaptive,
FileFcrDeniedUser,
FileFcrDeniedCache,
FileFcrDeniedThreshUser,
FileFcrBlocksRead,
FileFcrBlocksDeniedUser,
FileFcrBlocksDeniedCache,
FileFcrBlocksDeniedThreshUser,
FileFcrDeniedKern,
FileFcrDeniedThreshKern,
FileFcrBlocksDeniedKern,
FileFcrBlocksDeniedThreshKern,
FileSyncScans,
FileSyncSubtables,
FileSyncScanners,
FileSyncGroups,
MsgChnLastDone,
MsgWorkQLenSum,
DBLockBlocksSum,
DBLocksHeldSum,
CPUUServPart00,
CPUUServPart01,
CPUUServPart02,
CPUUServPart03,
CPUUServPart04,
CPUUServPart05,
CPUUServPart06,
CPUUServPart07,
CPUUServPart08,
CPUUServPart09,
CPUUServPart10,
CPUUServPart11,
CPUUServPart12,
CPUUServPart13,
CPUUServPart14,
CPUUServPart15,
CPUUServPart16,
CPUUServPart17,
CPUUServPart18,
CPUUServPart19,
CPUUServPart20,
CPUUServPart21,
CPUUServPart22,
CPUUServPart23,
CPUUServPart24,
CPUUServPart25,
CPUUServPart26,
CPUUServPart27,
CPUUServPart28,
CPUUServPart29,
CPUUServPart30,
CPUUServPart31,
CPUUServPart32,
CPUUServPart33,
CPUUServPart34,
CPUUServPart35,
CPUUServPart36,
CPUUServPart37,
CPUUServPart38,
Resource Usage Macros and Tables
171
CPUUServPart39,
CPUUServPart40,
CPUUServPart41,
CPUUServPart42,
CPUUServPart43,
CPUUServPart44,
CPUUServPart45,
CPUUServPart46,
CPUUServPart47,
CPUUExecPart00,
CPUUExecPart01,
CPUUExecPart02,
CPUUExecPart03,
CPUUExecPart04,
CPUUExecPart05,
CPUUExecPart06,
CPUUExecPart07,
CPUUExecPart08,
CPUUExecPart09,
CPUUExecPart10,
CPUUExecPart11,
CPUUExecPart12,
CPUUExecPart13,
CPUUExecPart14,
CPUUExecPart15,
CPUUExecPart16,
CPUUExecPart17,
CPUUExecPart18,
CPUUExecPart19,
CPUUExecPart20,
CPUUExecPart21,
CPUUExecPart22,
CPUUExecPart23,
CPUUExecPart24,
CPUUExecPart25,
CPUUExecPart26,
CPUUExecPart27,
CPUUExecPart28,
CPUUExecPart29,
CPUUExecPart30,
CPUUExecPart31,
CPUUExecPart32,
CPUUExecPart33,
CPUUExecPart34,
CPUUExecPart35,
CPUUExecPart36,
CPUUExecPart37,
CPUUExecPart38,
CPUUExecPart39,
CPUUExecPart40,
CPUUExecPart41,
CPUUExecPart42,
CPUUExecPart43,
CPUUExecPart44,
CPUUExecPart45,
CPUUExecPart46,
CPUUExecPart47,
AllocatorExtentAllocReqs,
AllocatorExtentFreeReqs,
AllocatorMapIOsStarted,
AllocatorMapIOsDone,
NodeAgentMigrationsStarted,
NodeAgentMigrationsDone,
172
Resource Usage Macros and Tables
NodeAgentStatProcessed,
ReadResponseHotTotal,
ReadResponseWarmTotal,
ReadResponseColdTotal,
WriteResponseHotTotal,
WriteResponseWarmTotal,
WriteResponseColdTotal,
ReadsHot,
ReadsWarm,
ReadsCold,
WritesHot,
WritesWarm,
WritesCold,
ReadResponseHotMax,
ReadResponseWarmMax,
ReadResponseColdMax,
ReadResponseHotMin,
ReadResponseWarmMin,
ReadResponseColdMin,
WriteResponseHotMax,
WriteResponseWarmMax,
WriteResponseColdMax,
WriteResponseHotMin,
WriteResponseWarmMin,
WriteResponseColdMin,
IoRespMax,
IoGapMax,
MIWrites,
MIWriteTime,
MIWriteTimeMax,
MIWriteLocks,
MIWriteLockTime,
MIWriteLockTimeMax,
MISleeps,
MISleepTime,
MISleepTimeMax,
SpareCount00,
SpareCount01,
SpareCount02,
SpareCount03,
SpareCount04,
SpareCount05,
SpareCount06,
SpareCount07,
SpareCount08,
SpareCount09,
SpareTrack00,
SpareTrack01,
SpareTrack02,
SpareTrack03,
SpareTrack04,
SpareTrack05,
SpareTrack06,
SpareTrack07,
SpareTrack08,
SpareTrack09,
SpareTmon00,
SpareTmon01,
SpareTmon02,
SpareTmon03,
SpareTmon04,
SpareTmon05,
SpareTmon06,
Resource Usage Macros and Tables
SpareTmon07,
SpareTmon08,
SpareTmon09
FROM ResUsageSvpr WITH CHECK OPTION;
COMMENT ON VIEW DBC.ResSvprView AS
'View of ResUsageSvpr (per Vproc) table data';
173
Chapter 14: Resource Usage Views
ResSvprView
174
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
Macro Output Format
CHAPTER 15
Resource Usage Macros
This chapter describes the output format of the resource usage macros and each macro.
Macro Output Format
Resource usage macros provide output in the following general format.
<Report Date>
<Title of Report>
--------------1st
2nd
1st
Date
Time
Type
Id
Id
Stat
-------- -------- ---- ------ ------ ------99/99/99 99:99:99 AAAA 999-99 999-99 999.99%
999.99%
...........
AAAA 999-99 999-99 999.99%
999-99 999-99 999.99%
99:99:99 AAAA 999-99 999-99 999.99%
...........
Page <num>
2nd
3rd
Stat
Stat ...
-------- -------99999.99 99999.99
99999.99 99999.99
99999.99 99999.99
99999.99 99999.99
99999.99 99999.99
where:
Column
Description
Date
The date at the end of a log interval.
Time
The time at the end of a log interval. Statistics on each line cover the time
period ending at the indicated time.
Type
A virtual processor type, logical device type, host type, or a special type
for certain reports.
1st ID, 2nd ID, and so
on
The appropriate identifier, which varies, depending on the macro. It is
one or more of the following:
•
•
•
•
1st Stat, 2nd Stat, and
so on
NodeID
VprocID
HostID
GroupID
The appropriate statistics. Details are given with the descriptions of each
macro in this chapter.
Numbers are generally displayed with the appropriate fixed format (for
example, 'zzzz9.99') unless the number represents a percentage or sum of
percentages.
Percentages are displayed with the appropriate format (for example,
'zz9.9%', 'zz9' or 'zz9.99').
Resource Usage Macros and Tables
175
Chapter 15: Resource Usage Macros
Macro Output Format
Unless otherwise specified, all statistical numbers are expressed as either:
•
Percentage
•
Milliseconds (ms)
•
Kilobytes (KBs)
Columns whose values depend on the logging rate are never reported as raw data. Instead,
they are converted to a normalized value, such as per second.
All reports are ordered by date, time, type, 1st ID, 2nd ID, and so on. Repeated date, time,
type, and ID column values are suppressed until a new row presents a different value.
Question Marks
Question marks used as values in the output examples are generated when a division by zero is
made. It represents data that is not available. The numbers in the columns are calculated, for
example, by dividing KBs by number of blocks read. When there are no blocks read, KB is
divided by zero. A question mark does not mean there is an error, but indicates that there is no
information to report for this time period.
Usage Notes
To get current data, logging must be enabled on the ResUsage table used by the view or macro.
176
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResAWT Macros
ResAWT Macros
Function
Macro...
Collects and reports the average AWT...
ResAWT
in use for all AMPs in the system.
ResAWTByAMP
in use for each AMP.
ResAWTByNode
on all AMPs in each node.
Input Format Examples
The input forms of these three macros are described below.
EXEC ResAWT
(FromDate,ToDate,FromTime,ToTime);
EXEC ResAWTByAMP
(FromDate,ToDate,FromTime,ToTime);
EXEC ResAWTByNode
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
See “Executing Macros” on page 32 for a description of the FromDate, ToDate, FromTime,
ToTime, FromNode, ToNode and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSawt.
•
Name the node log rate.
Output Examples
The reports in the following sections are sample output reports from the ResAWT,
ResAWTByAMP, and ResAWTByNode macros.
In the ResAWT output report, the 22 statistics columns, after the Date and Time columns,
provide a summary of the AWTs resource usage.
The following table describes the 24 statistics columns, after the Date and Time columns, in
the ResAWTByAMP output.
Statistics columns
Description
1
Node ID.
2
AMP ID.
3 through 24
Summary of AWTs resource usage.
Resource Usage Macros and Tables
177
Chapter 15: Resource Usage Macros
ResAWT Macros
The following table describes the 23 statistics columns, after the Date and Time columns, in
the ResAWTByNode output report.
Statistics columns
Description
1
Node ID.
2 through 23
Summary of AWTs resource usage.
The following table describes the columns in all output reports (with the exception of
ResAWTByNode, which has the NodeId column, and ResAWTByAMP, which has the Node ID
and AMP ID columns).
178
Column...
Reports the...
Mail box Depth
current depth of the AMP work mailbox.
In Flow Ctl?
AMP that is or is not in flow control.
Flow Ctls Per Sec
number of times during the log period that the system entered the
flow control state from a non-flow controlled state.
Work Type In Use
current number of AWTs in use during the log period for each
new work type for the VprId vproc.
Work New AWTs
current number of AWTs in use during the log period for each
new first-level secondary work type for the VprId vproc.
Work One AWTs
current number of AWTs in use during the log period for each
first-level secondary work type for the VprId vproc.
New + One AWTs
summary of the previous two columns: Work New AWTs and
Work One AWTs.
Work Two AWTs
current number of AWTs in use during the log period for each
second-level secondary work type for the VprId vproc.
Work 3 AWTs
current number of AWTs in use during the log period for each
third-level secondary work type for the VprId vproc.
Work Abrt AWTs
current number of AWTs in use during the log period for each
transaction abort request for the VprId vproc.
Work Spwn AWTs
current number of AWTs in use during the log period for each
spawned abort request for the VprId vproc.
Work Norm AWTs
current number of AWTs in use during the log period for each
message that does not fall within the standard work type hierarchy
for the VprId vproc.
Work Ctl AWTs
Note: This column is not currently used.
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResAWT Macros
Column...
Reports the...
Work Exp AWTs
current number of AWTs in use during the log period for each
expedited Allocation Groups for the VprId vproc. (Expedited
Allocation Groups exist when using the reserved AWT pool. See
the "Priority Scheduler (schmon) chapter in Utilities for details.)
Max Work New AWTs
the maximum number of AWTs in use at one time during the log
period for each new work type for the VprId vproc.
Max Work One AWTs
the maximum number of AWTs in use at one time during the log
period for each first-level secondary work type for the VprId
vproc.
Max Work Two AWTs
the maximum number of AWTs in use at one time during the log
period for each second-level secondary work type for the VprId
vproc.
Max Work 3 AWTs
the maximum number of AWTs in use at one time during the log
period for each third-level secondary work type for the VprId
vproc.
Max Work Abrt AWTs
the maximum number of AWTs in use at one time during the log
period for each transaction abort request for the VprId vproc.
Max Work Spwn AWTs
the maximum number of AWTs in use at one time during the log
period for each spawned abort request for the VprId vproc.
Max Work Norm AWTs
the maximum number of AWTs in use at one time during the log
period for each message that does not fall within the standard
work type hierarchy for the VprId vproc.
Max Work Ctl AWTs
Note: This column is not currently used.
Max Work Exp AWTs
the maximum number of AWTs in use at one time during the log
period for each expedited Allocation Groups for the VprId vproc.
(Expedited Allocation Groups exist when using the reserved
AWT pool. See the "Priority Scheduler (schmon)" chapter in
Utilities for details.)
For a complete description of the columns above, see Chapter 7: “ResUsageSawt Table.”
Resource Usage Macros and Tables
179
180
ResAWT Sample Output
07/08/17
AMP Worker Task Summary Average Usage per AMP Across System
Page
Max Max Max Max
Mail
In
Flow Work Work New+ Work Work Work Work Work Work Work Work Work Work Work
Box Flow
Ctls New One One Two
3 Abrt Spwn Norm Ctl Exp New One Two
3
Date
Time Depth Ctl? PerSec AWTs AWTs AWTs AWTs AWTs AWTs AWTs AWTs AWTs AWTs AWTs AWTs AWTs AWTs
-------- -------- ------ ----- ------ ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---07/08/12 23:00:00
8 1.00
0.01
31
22
54
0
0
0
0
0
0
0
35
25
2
1
23:01:00
9 0.00
0.02
28
25
54
0
0
0
0
0
0
0
33
27
1
1
23:02:00
6 0.00
0.00
31
22
54
0
0
0
0
0
0
0
35
26
1
1
23:03:00
3 0.00
0.00
31
22
53
0
0
0
0
0
0
0
35
26
1
1
23:04:00
2 0.00
0.00
31
22
52
0
0
0
0
0
0
0
36
27
1
1
23:05:00
5 0.00
0.00
31
22
53
0
0
0
0
0
0
0
36
26
1
1
23:06:00
3 0.00
0.00
27
24
51
0
0
0
0
0
0
0
34
27
1
1
23:07:00
1 0.00
0.00
21
19
40
0
0
0
0
0
0
1
35
29
1
1
23:08:00
1 0.00
0.00
26
20
46
0
0
0
0
0
0
0
35
29
1
1
23:09:00
2 0.00
0.00
30
20
50
0
0
0
0
0
0
0
37
26
1
1
23:10:00
1 0.00
0.00
29
16
46
0
0
0
0
0
0
0
38
25
2
1
23:11:00
2 0.00
0.00
30
19
49
0
0
0
0
0
0
0
38
27
1
1
23:12:00
2 0.00
0.00
31
21
52
0
0
0
0
0
0
0
37
26
1
1
23:13:00
1 0.00
0.00
29
19
49
0
0
0
0
0
0
0
36
26
1
1
23:14:00
1 0.00
0.00
29
18
47
0
0
0
0
0
0
0
36
25
1
1
23:15:00
2 0.00
0.00
29
19
48
0
0
0
0
0
0
0
37
25
2
1
23:16:00
3 0.00
0.00
34
18
52
0
0
0
0
0
0
0
37
25
1
1
23:17:00
6 0.00
0.00
35
19
54
0
0
0
0
0
0
0
40
22
1
1
23:18:00
8 0.00
0.00
30
23
53
0
0
0
0
0
0
0
37
24
1
1
23:19:00
1 0.00
0.01
25
24
49
0
0
0
0
0
0
0
36
30
1
1
23:20:00
1 0.00
0.00
28
18
46
0
0
0
0
0
0
0
36
30
2
2
23:21:00
7 0.00
0.01
34
20
54
0
0
0
0
0
0
0
36
26
1
1
23:22:00
2 0.00
0.01
30
22
53
0
0
0
0
0
0
0
36
27
1
1
Max
Work
Abrt
AWTs
---1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Max
Work
Spwn
AWTs
---0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
Max Max Max
Work Work Work
Norm Ctl Exp
AWTs AWTs AWTs
---- ---- --0
0
3
0
0
2
0
0
2
0
0
3
0
0
3
0
0
4
0
0
3
0
0
3
0
0
3
0
0
4
0
0
3
0
0
3
0
0
3
0
0
4
0
0
3
0
0
3
0
0
4
0
0
4
0
0
4
0
0
3
0
0
4
0
0
3
0
0
3
ResAWTByAMP Sample Output
07/08/17
AMP Worker Task Summary Usage per AMP
Resource Usage Macros and Tables
Mail In
Flow
Work
AMP Box
Flow Ctls
New
Date
Time
ID Depth Ctl? PerSec AWTs
-------- -------- ------ ------ ----- -----07/08/12 23:00:00 0
3 0.00
0.00
31
1
1 0.00
0.00
32
2
12 0.00
0.00
31
3
14 0.00
0.00
32
4
4 0.00
0.00
32
5
11 0.00
0.00
32
6
12 0.00
0.00
30
7
17 0.00
0.00
32
8
5 0.00
0.00
31
9
4 0.00
0.00
32
10
1 0.00
0.00
30
15
0.00
0.00
32
12
7 0.00
0.00
32
13
1 0.00
0.00
29
14
1 0.00
0.00
31
15
4 0.00
0.00
32
16
27 1.00
0.22
31
17
5 0.00
0.00
32
18
1 0.00
0.00
29
19
11 0.00
0.02
32
23:01:00
0
1
2
3
14
11
19
12
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
28
29
29
28
Work
One
AWTs
---22
22
23
22
22
22
24
22
23
22
23
22
22
24
23
22
23
22
23
22
New+
One
AWTs
---53
54
54
54
54
54
54
54
54
54
53
54
54
53
54
54
54
54
52
54
25
25
25
26
53
54
54
54
Work Work Work Work Work
Two
3 Abrt Spwn Norm
AWTs AWTs AWTs AWTs AWTs
---- ---- ---- ---- ---0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
Page
Work
Ctl
AWTs
---0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Work
Exp
AWTs
---0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Max
Work
New
AWTs
---33
34
34
34
34
35
35
34
34
33
34
34
34
33
34
34
34
34
33
34
Max
Work
One
AWTs
---24
24
24
24
25
23
24
23
23
25
24
24
24
24
24
24
24
24
25
24
Max
Work
Two
AWTs
---2
1
1
1
1
1
1
1
2
0
1
1
0
0
1
1
1
1
1
0
0
0
0
0
0
0
0
0
32
33
33
33
26
26
25
26
0
0
0
0
Max Max Max Max
Work Work Work Work
3 Abrt Spwn Norm
AWTs AWTs AWTs AWTs
---- ---- ---- ---1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
Max
Work
Ctl
AWTs
---0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Max
Work
Exp
AWTs
---3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
0
0
0
0
2
1
1
1
1
Resource Usage Macros and Tables
23:02:00
4
5
6
7
8
9
10
11
12
13
14
15
16
3
13
19
8
12
3
4
13
3
1
1
11
10
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.13
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.17
29
29
28
29
29
28
29
29
30
26
26
28
29
25
25
26
25
25
26
25
25
24
26
25
26
25
54
54
54
54
54
54
54
54
54
52
51
54
54
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
33
32
32
32
33
33
33
32
32
31
33
32
32
26
25
26
26
26
26
26
25
25
26
26
26
27
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
2
1
2
2
2
1
1
2
0
1
2
9
6
1
0.00
0.00
0.00
0.00
0.00
0.00
31
31
31
22
23
23
53
54
54
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
33
32
34
25
26
25
1
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
2
2
2
Max Max Max Max
Work Work Work Work
3 Abrt Spwn Norm
AWTs AWTs AWTs AWTs
---- ---- ---- ---1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
2
1
0
0
Max
Work
Ctl
AWTs
---0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
ResAWTByNode Sample Output
07/08/17
Mail In
Node
Box Flow
Date
Time
ID Depth Ctl?
-------- -------- ------ ------ ----07/08/12
23:00:00 1-04
8 1.00
23:01:00 1-04
9 0.00
23:02:00 1-04
6 0.00
23:03:00 1-04
3 0.00
23:04:00 1-04
2 0.00
23:05:00 1-04
5 0.00
23:06:00 1-04
3 0.00
23:07:00 1-04
1 0.00
23:08:00 1-04
1 0.00
23:09:00 1-04
2 0.00
23:10:00 1-04
1 0.00
23:11:00 1-04
2 0.00
23:12:00 1-04
2 0.00
23:13:00 1-04
1 0.00
23:14:00 1-04
1 0.00
23:15:00 1-04
2 0.00
23:16:00 1-04
3 0.00
23:17:00 1-04
6 0.00
23:18:00 1-04
8 0.00
23:19:00 1-04
1 0.00
23:20:00 1-04
1 0.00
AMP Worker Task Summary Average Usage per AMP By Node Page
Flow
Ctls
PerSec
-----0.01
0.02
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.01
0.00
Work
New
AWTs
---31
28
31
31
31
31
27
21
26
30
29
30
31
29
29
29
34
35
30
25
28
Work
One
AWTs
---22
25
22
22
22
22
24
19
20
20
16
19
21
19
18
19
18
19
23
24
18
New+
One
AWTs
---54
54
54
53
52
53
51
40
46
50
46
49
52
49
47
48
52
54
53
49
46
Work Work Work Work Work
Two
3 Abrt Spwn Norm
AWTs AWTs AWTs AWTs AWTs
---- ---- ---- ---- ---0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Work
Ctl
AWTs
---0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Work
Exp
AWTs
---0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
Max
Work
New
AWTs
---35
33
35
35
36
36
34
35
35
37
38
38
37
36
36
37
37
40
37
36
36
Max
Work
One
AWTs
---25
27
26
26
27
26
27
29
29
26
25
27
26
26
25
25
25
22
24
30
30
Max
Work
Two
AWTs
---2
1
1
1
1
1
1
1
1
1
2
1
1
1
1
2
1
1
1
1
2
1
Max
Work
Exp
AWTs
---3
2
2
3
3
4
3
3
3
4
3
3
3
4
3
3
4
4
4
3
4
181
Chapter 15: Resource Usage Macros
ResCPUByAMP Macros
ResCPUByAMP Macros
Function
Macro...
Reports the following...
ResCPUByAMP
how each AMP on each node utilizes the CPUs.
ResCPUByAMPOneNode
how each AMP on a specific node utilizes the CPUs.
ResAmpCpuByGroup
the summary of AMP CPU usage by node grouping.
Input Format Examples
The input forms of these three macros are described below.
EXECUTE ResCPUByAMP
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXECUTE ResCPUByAMPOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXECUTE ResAmpCpuByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, ToDate, FromTime,
ToTime, FromNode, ToNode and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must have been enabled on ResUsageSvpr at some time before macro execution.
See Chapter 2: “Planning Your Resource Usage Data” for an explanation of how to enable/
disable logging.
•
Name the node log rate.
Note: It is not necessary that logging for the table and the rate be enabled at the moment
the macro is executed.
For a description of partitions and partition assignments in Teradata Database, see
Appendix D: “Partition Assignments.”
Output Examples
The reports in the following sections are sample output reports from the ResCPUByAMP, the
ResCPUByAMPOneNode, and the ResAmpCpuByGroup macros, respectively, where:
182
Column...
Reports the percent of time AMPs were busy doing user...
Awt User Serv%
service for the AMP Worker Task (Awt) partition.
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResCPUByAMP Macros
Column...
Reports the percent of time AMPs were busy doing user...
Misc User Serv%
service for miscellaneous (all other except Partition 0) AMP partitions.
Awt User Exec%
execution within the AMP Worker Task (Awt) partition.
Misc User Exec%
execution within miscellaneous (all other except Partition 0) AMP
partitions.
Total User Serv%
servicea work. This is the sum of the Awt User Serv%, the Misc User
Serv%, and AMP Partition 0 user service%.a
Total User Exec%
executionb work. This is the sum of the Awt User Exec%, Misc User
Exec%, and AMP Partition 0 user execution.b
Total Busy%
service and execution work. This is the sum of the Total User Serv% and
the Total User Exec% columns.
a. Service is the time that a CPU is busy executing user service code, which is privileged work
performing system-level services on behalf of user execution processes that do not have root
privileges.
b. Execution is the time a CPU is busy executing user execution code, which is the time spent in a
user state on behalf of a process.
Note: The above CPU statistics represent the aggregate of all time spent in the indicated way
by all CPUs on the node. Because there are multiple CPUs, the Total Busy % should be
compared to a theoretical maximum of 100% times the number of CPUs on the node.
The Node CPU column in the following sample outputs reports the number of CPUs
(NCPUs).
For more information on how to monitor busy AMP Worker Tasks (AWTs), see "AWT
Monitor (awtmon)" in Utilities.
ResCPUByAMP Sample Output
01/07/12
CPU USAGE BY AMP
Date
-------01/07/12
Page
1
Vproc
Id
----0
1
Node
Id
-----001-01
001-01
Node
CPUs
-------4
4
Awt
User
Serv%
------0.36%
0.26%
Misc
User
Serv%
------0.00%
0.00%
Awt
User
Exec%
------0.05%
0.12%
Misc
User
Exec%
------0.00%
0.00%
Total
User
Serv%
------0.36%
0.30%
Total
User
Exec%
------0.05%
0.12%
Total
Busy
%
------0.41%
0.42%
09:57:20
0
1
001-01
001-01
4
4
0.41%
0.34%
0.00%
0.00%
0.12%
0.05%
0.00%
0.00%
0.45%
0.38%
0.12%
0.05%
0.58%
0.42%
09:57:40
0
1
001-01
001-01
4
4
0.25%
0.19%
0.00%
0.00%
0.18%
0.06%
0.00%
0.00%
0.28%
0.29%
0.18%
0.06%
0.45%
0.35%
09:58:00
0
1
001-01
001-01
4
4
0.38%
0.31%
0.00%
0.00%
0.08%
0.09%
0.00%
0.00%
0.45%
0.34%
0.08%
0.09%
0.52%
0.42%
09:58:20
0
1
001-01
001-01
4
4
0.31%
0.36%
0.00%
0.00%
0.08%
0.09%
0.00%
0.00%
0.34%
0.40%
0.08%
0.09%
0.41%
0.49%
09:58:40
0
1
001-01
001-01
4
4
0.39%
0.32%
0.00%
0.00%
0.11%
0.12%
0.00%
0.00%
0.41%
0.36%
0.11%
0.12%
0.52%
0.49%
09:59:00
0
1
001-01
001-01
4
4
0.29%
0.21%
0.00%
0.00%
0.11%
0.09%
0.00%
0.00%
0.30%
0.22%
0.11%
0.09%
0.41%
0.31%
09:59:20
0
1
001-01
001-01
4
4
0.30%
0.30%
0.00%
0.00%
0.06%
0.19%
0.00%
0.00%
0.31%
0.32%
0.06%
0.19%
0.38%
0.51%
09:59:40
0
1
001-01
001-01
4
4
0.40%
0.26%
0.00%
0.00%
0.09%
0.08%
0.00%
0.00%
0.46%
0.38%
0.09%
0.08%
0.55%
0.45%
Time
-------09:57:00
Resource Usage Macros and Tables
183
Chapter 15: Resource Usage Macros
ResCPUByAMP Macros
10:00:00
0
1
001-01
001-01
4
4
0.32%
0.28%
0.00%
0.00%
0.08%
0.09%
0.00%
0.00%
0.34%
0.31%
0.08%
0.09%
0.41%
0.40%
Note: The NodeID column only appears in the ResCPUByAMP output report.
ResCPUByAMPOneNode Sample Output
01/07/12
CPU Usage by AMP for Node 001-01 (4 CPUs)
Date
-------01/07/12
Page
68
Vproc
Id
----0
1
NCPUs
----4
4
Awt
User
Serv%
------0.36%
0.26%
09:57:20
0
1
4
4
0.41%
0.34%
0.00%
0.00%
0.12%
0.05%
0.00%
0.00%
0.45%
0.38%
0.12%
0.05%
0.58%
0.42%
09:57:40
0
1
4
4
0.25%
0.19%
0.00%
0.00%
0.18%
0.06%
0.00%
0.00%
0.28%
0.29%
0.18%
0.06%
0.45%
0.35%
09:58:00
0
1
4
4
0.38%
0.31%
0.00%
0.00%
0.08%
0.09%
0.00%
0.00%
0.45%
0.34%
0.08%
0.09%
0.52%
0.42%
09:58:20
0
1
4
4
0.31%
0.36%
0.00%
0.00%
0.08%
0.09%
0.00%
0.00%
0.34%
0.40%
0.08%
0.09%
0.41%
0.49%
09:58:40
0
1
4
4
0.39%
0.32%
0.00%
0.00%
0.11%
0.12%
0.00%
0.00%
0.41%
0.36%
0.11%
0.12%
0.52%
0.49%
09:59:00
0
1
4
4
0.29%
0.21%
0.00%
0.00%
0.11%
0.09%
0.00%
0.00%
0.30%
0.22%
0.11%
0.09%
0.41%
0.31%
Time
-------09:57:00
Misc
User
Serv%
------0.00%
0.00%
Awt
User
Exec%
------0.05%
0.12%
Misc
User
Exec%
------0.00%
0.00%
Total
User
Serv%
------0.36%
0.30%
Total
User
Exec%
------0.05%
0.12%
Total
Busy
%
------0.41%
0.42%
ResAmpCpuByGroup Sample Output
01/07/12
AMP CPU USAGE BY GROUP
Date
-------01/07/12
Page
45
Node
CPUs
-------4
Awt
User
Serv%
------0.32%
Misc
User
Serv%
------0.00%
Awt
User
Exec%
------0.07%
Misc
User
Exec%
------0.00%
Total
User
Serv%
------0.36%
Total
User
Exec%
------0.07%
Total
Busy
%
------0.43%
A
4
0.33%
0.00%
0.08%
0.00%
0.36%
0.08%
0.44%
09:52:20
A
4
0.35%
0.00%
0.07%
0.00%
0.37%
0.07%
0.44%
09:52:40
A
4
0.36%
0.00%
0.09%
0.00%
0.39%
0.09%
0.48%
09:53:00
A
4
0.27%
0.00%
0.09%
0.00%
0.28%
0.09%
0.37%
09:53:20
A
4
0.29%
0.00%
0.06%
0.00%
0.34%
0.06%
0.40%
09:53:40
A
4
0.36%
0.00%
0.06%
0.00%
0.40%
0.06%
0.46%
09:54:00
A
4
0.35%
0.00%
0.11%
0.00%
0.38%
0.11%
0.49%
09:54:20
A
4
0.34%
0.00%
0.07%
0.00%
0.36%
0.07%
0.43%
09:54:40
A
4
0.41%
0.00%
0.04%
0.00%
0.43%
0.04%
0.47%
09:55:00
A
4
0.28%
0.00%
0.09%
0.00%
0.28%
0.09%
0.37%
09:55:20
A
4
0.35%
0.00%
0.09%
0.00%
0.43%
0.09%
0.53%
09:55:40
A
4
0.34%
0.00%
0.06%
0.00%
0.42%
0.06%
0.48%
09:56:00
A
4
0.26%
0.00%
0.08%
0.00%
0.29%
0.08%
0.37%
Time
-------09:51:40
Group
Id
----A
09:52:00
Note: The GroupID column only appears in the ResAmpCpuByGroup output report.
Normalized Viewing of CPU Usage by AMP
Some users may prefer to view CPU usage by AMP in a normalized fashion. Conceptually, this
restates each of the above statistics in terms of percentage of total CPU capacity of the node.
184
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResCPUByAMP Macros
The following SQL example shows how to perform this normalization for the Total Busy %
statistic.
SEL TheDate, TheTime, Vproc, NodeId,
(AmpTotalUserExec+AmpTotalUserServ)
/Secs/NCPUs
(FORMAT ‘zz9%’,TITLE ‘Total// Busy// %’)
FROM ResCpuUsageByAMPView
WHERE TheDate = CURRENT_DATE AND TheTime>080000
ORDER BY 1,2,3;
Resource Usage Macros and Tables
185
Chapter 15: Resource Usage Macros
ResCPUByPE Macros
ResCPUByPE Macros
Function
Macro...
Reports...
ResCPUByPE
how each PE on each node is utilizing the CPUs.
ResCPUByPEOneNode
how each PE on a specific node is utilizing the CPUs.
ResPeCpuByGroup
the PE CPU utilization summarized by a node grouping.
Input Format Examples
The input forms of the these three macros are described below.
EXEC ResCPUByPE
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResCPUByPEOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXEC ResPeCpuByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, ToDate, FromTime,
ToTime, FromNode, ToNode and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSvpr.
•
Name the node log rate.
Output Examples
The reports in the following sections are sample output reports from the ResCPUByPE,
ResCPUByPEOneNode, and ResPeCPUByGroup macros, respectively, where:
186
Column...
Reports the percent of time PEs are busy doing user...
Pars User Serv%
servicea for the Parser partition of the PE.a
Disp User Serv%
service for the Dispatcher partition of the PE.
Ses User Serv%
service for the Session Control partition of the PE.
Misc User Serv%
service for miscellaneous (all other, except Partition 0) PE partitions.
Pars User Exec%
execution bwithin the Parser partition of the PE.b
Disp User Exec%
execution within the Dispatcher partition of the PE.
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResCPUByPE Macros
Column...
Reports the percent of time PEs are busy doing user...
Ses User Exec%
execution within the Session Control partition of the PE.
Misc User Exec%
execution within miscellaneous (all other, except Partition 0) PE partitions.
Total User Serv%
service work. This is the sum of the four user service columns above plus PE
Partition 0 user service.
Total User Exec%
execution work. This is the sum of the four user execution columns above
plus PE Partition 0 user execution.
Total Busy%
service and execution work. This is the sum of the Total User Serv% and the
Total User Exec% columns.
a. Service is the time that a CPU is busy executing user service code, which is privileged work
performing system-level services on behalf of user execution processes that do not have root
privileges.
b. Execution is the time a CPU is busy executing user execution code, which is the time spent in a
user state on behalf of a process.
Note: The above CPU statistics represent the aggregate of all time spent in the indicated way
by all CPUs on the node. Because there are multiple CPUs, the Total Busy % should be
compared to a theoretical maximum of 100% times the number of CPUs on the node.
The Node CPU column in the following sample outputs reports the number of CPUs
(NCPUs).
ResCPUByPE Sample Output
01/07/12
CPU USAGE BY PE
Page 1
Pars
Disp
Ses
Misc
Pars
Disp
Ses
Vproc
Node Node
User
User
User
User
User
User
User
Date
Time
Id
Id CPUs
Serv%
Serv%
Serv%
Serv%
Exec%
Exec%
Exec%
-------- -------- ----- ------ ---- ------- ------- ------- ------- ------- ------- ------01/07/12 09:57:00 16382 001-01
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
16383 001-01
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
Misc
User
Exec%
------0.00%
0.00%
Total
Total
Total
User
User
Busy
Serv%
Exec%
%
------ ------ ------0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
09:57:20 16382 001-01
16383 001-01
4
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
09:57:40 16382 001-01
16383 001-01
4
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
09:58:00 16382 001-01
16383 001-01
4
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
09:58:20 16382 001-01
16383 001-01
4
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
09:58:40 16382 001-01
16383 001-01
4
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
09:59:00 16382 001-01
16383 001-01
4
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
09:59:20 16382 001-01
16383 001-01
4
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
09:59:40 16382 001-01
16383 001-01
4
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
10:00:00 16382 001-01
16383 001-01
4
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
Note: The NodeId column only appears in the ResCPUByPE output report.
Resource Usage Macros and Tables
187
Chapter 15: Resource Usage Macros
ResCPUByPE Macros
ResCPUByPEOneNode Sample Output
01/09/13
Date
-----01/08/21
01/08/27
CPU Usage by PE for Node 001-01 (4 CPUs)
Page 4
Vproc Node
Time
Id CPUs
------- ----- ---15:41:00
2
4
Pars
User
Serv%
-----0.02%
Disp
Ses
Misc
Pars
User
User
User
User
Serv% Serv%
Serv% Exec%
------ ------ ------ ----0.05%
0.00%
0.00% 0.56%
15:42:00
2
4
0.01%
0.01%
15:43:00
2
4
0.02%
0.02%
0.00%
0.00%
0.20%
0.00%
0.00%
0.00%
0.04%
0.20%
0.2%
15:44:00
2
4
0.03%
0.02%
0.00%
0.00%
0.55%
0.00%
0.00%
0.00%
0.05%
0.56%
0.6%
15:45:00
2
4
0.02%
0.01%
0.00%
0.00%
0.18%
0.00%
0.00%
0.00%
0.02%
0.18%
0.2%
15:46:00
2
4
0.03%
0.02%
0.00%
0.00%
0.58%
0.00%
0.00%
0.00%
0.05%
0.58%
0.6%
16:21:00
2
4
0.05%
0.08%
0.00%
0.00%
0.69%
0.00%
0.00%
0.00%
0.13%
0.70%
0.8%
0.00%
0.00%
Disp
User
Exec%
-----0.01%
Ses
User
Exec%
-----0.00%
Misc
User
Exec%
-----0.00%
Total
User
Serv%
-----0.08%
Total
User
Exec%
-----0.58%
Total
Busy
%
-----0.7%
0.00%
0.00%
0.00%
0.02%
0.18%
0.2%
0.18%
ResPeCpuByGroup Sample Output
01/07/12
PE CPU USAGE BY GROUP
Pars
Group Node User
Date
Time
Id CPUs Serv%
----------- ----- ---- ------01/07/12 04:55:40 A
4
0.00%
Disp
User
Serv%
-----0.00%
Ses
User
Serv%
------0.00%
Misc
User
Serv%
-----0.00%
Pars
User
Exec%
-----0.0%
Page 8
Disp
User
Exec%
-----0.00
Ses
User
Exec%
-----0.00%
Misc
User
Exec%
------0.00%
Total
User
Serv%
-----0.00%
Total
User
Exec%
----0.00%
Total
Busy
%
----0.00%
04:56:00
A
4
0.00%
0.00%
0.00%
0.00%
0.0%
0.00
0.00%
0.00%
0.00%
0.00%
0.00%
04:56:20
A
4
0.00%
0.00%
0.00%
0.00%
0.0%
0.00
0.00%
0.00%
0.00%
0.00%
0.00%
04:56:40
A
4
0.00%
0.00%
0.00%
0.00%
0.0%
0.00
0.00%
0.00%
0.00%
0.00%
0.00%
04:57:00
A
4
0.00%
0.00%
0.00%
0.00%
0.0%
0.00
0.00%
0.00%
0.00%
0.00%
0.00%
04:57:20
A
4
0.00%
0.00%
0.00%
0.00%
0.0%
0.00
0.00%
0.00%
0.00%
0.00%
0.00%
04:57:40
A
4
0.00%
0.00%
0.00%
0.00%
0.0%
0.00
0.00%
0.00%
0.00%
0.00%
0.00%
04:58:00
A
4
0.00%
04:58:20
A
4
0.00%
0.00%
0.00%
0.00%
0.00%
0.0%
0.00
0.00%
0.00%
0.0%
0.00
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
Note: The GroupID column only appears in the ResPeCpuByGroup output report.
Normalized Viewing of CPU Usage by PE
Some users may prefer to view CPU usage by PEs in a normalized fashion. Conceptually, this
restates each of the above statistics in terms of percentage of total CPU capacity of the node.
The following SQL example shows how to perform this normalization for the Total Busy %
statistic.
SEL TheDate, TheTime,Vproc,NodeId,
(PETotalUserExec+PETotalUserServ)
/Secs/NCPUs
(FORMAT ‘zz9%’,TITLE ‘Total// Busy// %’)
FROM ResCpuUsageByPEView
WHERE TheDate = CURRENT_DATE AND TheTime>080000
ORDER BY 1,2,3;
188
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResCPUByNode Macros
ResCPUByNode Macros
Function
Macro...
Reports how...
ResCPUByNode
each individual node is utilizing its CPUs.
ResCPUOneNode
a specific node is utilizing its CPUs.
ResCPUByGroup
a specified Node Group is utilizing the system CPUs.
Input Format Examples
The input forms of these three macros are described below.
EXEC ResCPUByNode
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResCPUOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXEC ResCPUByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, ToDate, FromTime,
ToTime, FromNode, ToNode and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSpma.
•
Name the node log rate.
Output Examples
The reports in the following sections are sample output reports from the ResCPUByNode, the
ResCPUOneNode macro, and the ResCPUByGroup.
The following columns are the averages for all CPUs on the node.
Resource Usage Macros and Tables
189
Chapter 15: Resource Usage Macros
ResCPUByNode Macros
This column ...
Lists percentage of time spent ...
I/O Wait %
idle and waiting for I/O completion.
Total User Serv %
busy doing user service work.
Total User Exec %
busy doing user execution work.
Total Busy %
busy doing user service and execution work.
This is the sum of Total User Serv % and the Total User Exec %
columns.
where:
This variable…
Describes the time a CPU is busy executing…
User service
user service code, which is privileged work performing system-level services
on behalf of user execution process that do not have root privileges.
User execution
user execution code, which is the time spent in a user state on behalf of a
process.
ResCPUByNode Sample Output
01/07/12
CPU USAGE BY NODE
Date
-------01/07/12
Time
-------09:51:40
09:52:00
09:52:20
09:52:40
09:53:00
09:53:20
Node
Id
-----001-01
001-01
001-01
001-01
001-01
001-01
Page
I/O
Wait
%
-----16.2%
17.2%
15.5%
16.1%
15.8%
15.5%
Total
User
Serv%
-----1.4%
1.3%
1.6%
1.5%
1.0%
1.5%
Total
User
Exec%
-----0.1%
0.2%
0.2%
0.2%
0.2%
0.2%
45
Total
Busy
%
-----1.5%
1.5%
1.8%
1.7%
1.2%
1.7%
Note: The NodeId column only appears in the ResCPUByNode output report.
ResCPUOneNode Sample Output
01/07/12
CPU Usage for Node 001-01
Date
-------01/07/12
190
Time
-------09:44:20
09:44:40
09:45:00
09:45:20
09:45:40
09:46:00
09:46:20
I/O
Wait
%
-----16.2%
16.9%
16.5%
17.0%
17.4%
16.6%
16.2%
Page
01
Total
Total
Total
User
User
Busy
Serv%
Exec%
%
------ ------ -----1.6%
0.2%
1.9%
1.3%
0.2%
1.5%
1.1%
0.1%
1.2%
1.7%
0.2%
1.9%
1.1%
0.2%
1.3%
1.3%
0.2%
1.5%
1.6%
0.2%
1.8%
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResCPUByNode Macros
ResCPUByGroup Sample Output
00/10/16
CPU USAGE BY Group
Date
-------00/10/16
Time
-------11:25:00
B
Page 2
I/O
Total
Total
Group
Wait
User
User
Id
%
Serv%
Exec%
----- ------ ------ -----A
0.0%
0.0%
0.0%
0.0% 0.0% 0.0% 0.0%
Total
Busy
%
-----0.0%
11:30:00
A
B
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
11:35:00
A
B
0.0%
0.0%
0.6%
0.3%
0.6%
0.4%
1.1%
0.7%
11:40:00
A
B
0.0%
0.0%
1.3%
1.1%
0.9%
0.9%
2.2%
2.0%
11:45:00
A
B
0.0%
0.0%
0.6%
0.3%
0.9%
1.0%
1.5%
1.3%
11:50:00
A
B
0.0%
0.0%
0.6%
0.6%
0.6%
0.8%
1.2%
1.3%
11:55:00
A
B
0.0%
0.0%
1.5%
1.6%
1.1%
1.0%
2.6%
2.6%
12:00:00
A
B
0.0%
0.0%
0.5%
0.7%
0.8%
0.9%
1.3%
1.6%
12:05:00
A
B
0.0%
0.0%
1.2%
0.6%
0.7%
0.5%
1.8%
1.1%
12:10:00
A
B
0.0%
0.0%
0.6%
1.1%
0.9%
1.2%
1.6%
2.2%
12:15:00
A
B
0.0%
0.0%
0.6%
0.5%
0.8%
0.7%
1.4%
1.2%
12:20:00
A
B
0.0%
0.0%
1.4%
1.1%
0.8%
0.8%
2.2%
1.9%
12:25:00
A
B
0.0%
0.0%
0.9%
0.9%
1.0%
0.9%
1.9%
1.8%
12:30:00
A
B
0.0%
0.0%
0.6%
0.6%
0.6%
0.8%
1.2%
1.4%
12:35:00
A
B
0.0%
0.0%
1.6%
1.3%
1.1%
0.9%
2.7%
2.2%
Note: The GroupID column only appears in the ResCpuByGroup output report.
Resource Usage Macros and Tables
191
Chapter 15: Resource Usage Macros
ResHostByLink Macros
ResHostByLink Macros
Function
Macro...
Reports the host traffic for...
ResHostByLink
every communication link in the system.
ResHostOneNode
the communication links of a specific node.
ResHostByGroup
the communication links of a node grouping.
Input Format Examples
The input forms of these three macros are described below.
EXEC ResHostByLink
(FromDate,ToDate,FromTime,ToTime);
Note: The ResHostByLink macro syntax does not include the FromNode and ToNode
parameters to specify a range of nodes.
EXEC ResHostOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXEC ResHostByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, FromTime, ToDate,
ToTime, and Node parameters.
Usage Notes
The ResHostByLink macros help you answer the following questions:
•
Is my set up correct?
•
Am I making good use of the channels? If not, how high are they? If not high, then there
may not be enough host resources.
Study the incoming traffic. Problems with incoming traffic may be simply caused by an
incorrect configuration. Once configured correctly, if there is still a traffic problem, consider
studying the LAN traffic, for example, when doing an export, the ResUsageSpma table may
show 30 million rows/log period.
For any of these macros the following usage notes apply:
192
•
Logging must be enabled on ResUsageShst.
•
Name the node log rate.
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResHostByLink Macros
Output Examples
The reports in the following sections are sample output reports from the ResHostByLink, the
ResHostOneNode macros, and the ResHostByGroup, respectively, where:
Column...
Reports the...
Host Type
type of host connection:
• NETWORK, for LAN-connected hosts
• IBMMUX, for channel-connected hosts
KBs Read/ Sec
number of KBs read per second.
KBs Write/ Sec
number of KBs written per second.
Blks Read/ Sec
number of successful blocks read per second.
Blks Write/ Sec
number of successful blocks written per second.
Blk Read Fail %
percentage of block read attempts that failed.
Blk Write Fail %
percentage of block write attempts that failed.
KBs/Blk Read
average number of KBs per block read.
KBs/Blk Write
average number of KBs per block written.
Msgs/Blk Read
average number of messages per block read.
Msgs/Blk Write
average number of messages per block written.
Avg ReqQ Len
average number of messages queued for output to the host.
Max ReqQ Len
maximum number of messages queued for output to the host.
Resource Usage Macros and Tables
193
194
ResHostByLink Sample Output
00/10/16
HOST COMMUNICATIONS BY COMMUNICATION LINK
KBs
KBs
Node Vproc
Host Host Read
Write
Date
Time
Id
Id
Type
Id /Sec
/Sec
------- ------- ------ ----- ------- ----- ----- -----00/10/16 11:07:00 105-04 65535 NETWORK
0 24.0
13.3
IBMMUX 101
0.0
0.0
105-05 65535 NETWORK
0
IBMMUX 202
IBMMUX 304
106-04 65535 NETWORK
0
0.0
0.0
0.0
22.6
Blks Blks
Read Write
/Sec
/Sec
----- ----0.1
0.1
0.0
0.0
Blk
Read
Fail%
----0.0%
?
Blk
Write
Fail%
----0.0%
?
?
?
?
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
?
?
?
11.3
0.1
0.1
0.0%
106-05 65535 NETWORK
0
7.5
97.0
0.1
0.1
11:22:42 105-04 65535 NETWORK
0 81105.0 250605.8 47.1 47.1
IBMMUX 101
0.0
0.0
0.0
0.0
Page
KBs
KBs Msgs Msgs
/Blk
/Blk /Blk /Blk
Read
Write Read Write
------ ------ ----- ----350.5
186.2
0.8
0.8
?
?
?
?
?
?
?
?
?
?
0.0%
398.4
0.0%
0.0%
?
0.0%
0.0%
?
Avg
ReqQ
Len
----0.0
0.0
Max
ReqQ
Len
---0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
?
?
?
?
?
?
198.8
0.9
0.9
0.0
0.0
86.0
1721.2
?
1097.7
5317.6
?
1.0
1.0
?
1.0
1.0
?
0.0
0.0
0.0
0.0
0.0
0.0
105-05 65535 NETWORK
0
IBMMUX 202
IBMMUX 304
44.1
0.0
0.0
22.6
0.0
0.0
0.1
0.0
0.0
0.1
0.0
0.0
0.0%
?
?
0.0%
?
?
391.8
?
?
206.5
?
?
0.9
?
?
0.9
?
?
0.0
0.0
0.0
0.0
0.0
0.0
106-04 65535 NETWORK
0
31.9
391.0
0.4
0.4
0.0%
0.0%
85.3
1037.5
1.0
1.0
0.0
0.0
106-05 65535 NETWORK
0
8.3
81.8
0.1
0.1
0.0%
0.0%
97.3
917.2
0.9
0.9
0.0
0.0
0.0%
?
0.0%
?
1722.0
?
5276.5
?
1.0
?
1.0
?
0.0
0.0
0.0
0.0
11:32:42 105-04 65535 NETWORK
0
IBMMUX 101
80303.8 246270.046.6 46.7
0.0
0.0
0.0
0.0
105-05 65535 NETWORK
0
IBMMUX 202
IBMMUX 304
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
0.0
0.0
0.0
0.0
0.0
0.0
106-04 65535 NETWORK
0
0.0
0.0
0.0
0.0
?
?
?
?
?
?
0.0
0.0
106-05 65535 NETWORK
0
46.2
23.7
0.1
0.1
0.9
0.0%
0.0%
385.4
200.3
0.9
0.0%
?
0.0%
?
1720.4
?
5148.5
?
1.0
?
0.0
0.0
0.0
0.0%
?
?
0.0%
?
?
86.5
?
?
84.7
?
?
11:42:42 105-04 65535 NETWORK
0 59002.2 176635.3 34.3 34.3
IBMMUX 101
0.0
0.0
0.0
0.0
105-05 65535 NETWORK
0
IBMMUX 202
IBMMUX 304
0.3
0.0
0.0
0.4
0.0
0.0
0.0
0.0
0.0
106-04 65535 NETWORK
0
23.1
11.9
0.1
0.1
0.0%
0.0%
407.6
106-05 65535 NETWORK
0
22.5
11.0
0.1
0.1
0.0%
0.0%
408.8
215.8
205.9
0.5
?
?
0.0
0.0
1.0
?
0.0
0.0
0.0
0.0
0.3
?
?
0.0
0.0
0.0
0.0
0.0
0.0
0.9
0.9
0.0 0.0
0.9
0.9
0.0 0.0
Resource Usage Macros and Tables
Note: The NodeId column only appears in the ResHostByLink output report.
1
Resource Usage Macros and Tables
ResHostOneNode Sample Output
00/10/16
Host Communications for Node 105-05
Vproc Host
Host
Date
Time
Id Type
Id
-------- -------- ----- -------- ----00/10/16 11:07:00 65535 NETWORK
0
IBMMUX
202
IBMMUX
304
KBs
KBs
Read
Write
/Sec
/Sec
-------- -------0.0
0.0
0.0
0.0
0.0
0.0
Page
Blks
Blks
Blk
Blk
KBs
Read
Write Read
Write /Blk
/Sec
/Sec Fail% Fail% Read
------ ------ ----- ----- ----0.0
0.0
?
?
?
0.0
0.0
?
?
?
0.0
0.0
?
?
?
11:22:42 65535 NETWORK
IBMMUX
IBMMUX
0
202
304
44.1
0.0
0.0
22.6
0.0
0.0
0.1
0.0
0.0
0.1
0.0
0.0
0.0%
?
?
11:32:42 65535 NETWORK
IBMMUX
IBMMUX
0
202
304
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
?
?
?
11:42:42 65535 NETWORK
IBMMUX
IBMMUX
0
202
304
0.3
0.0
0.0
0.4
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0%
?
?
0.0%
?
?
?
?
?
0.0%
?
?
391.8
?
?
?
?
?
86.5
?
?
1
KBs
/Blk
Write
------?
?
?
Msgs
/Blk
Read
----?
?
?
Msgs
/Blk
Write
----?
?
?
206.5
?
?
0.9
?
?
0.9
?
?
0.0
0.0
0.0
0.0
0.0
0.0
?
?
?
?
?
?
0.0
0.0
0.0
0.0
0.0
0.0
0.5
?
?
0.3
?
?
0.0
0.0
0.0
0.0
0.0
0.0
?
?
?
84.7
?
?
Avg
ReqQ
Len
---0.0
0.0
0.0
Max
ReqQ
Len
---0.0
0.0
0.0
ResHostByGroup Sample Output
Date
-------00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
00/10/16
Time
-------11:30:00
11:30:00
11:35:00
11:35:00
11:40:00
11:40:00
11:45:00
11:45:00
11:50:00
11:50:00
11:55:00
11:55:00
12:00:00
12:00:00
12:05:00
12:05:00
12:10:00
12:10:00
12:15:00
12:15:00
12:20:00
12:20:00
12:25:00
12:25:00
12:30:00
Group
Id
-----A
B
A
B
A
B
A
B
A
B
A
B
A
B
A
B
A
B
A
B
A
B
A
B
A
Host
Type
-------NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
NETWORK
KBs
Read
/Sec
-------0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
KBs
Write
/Sec
-------0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
Blks
Read
/Sec
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
Blks
Write
/Sec
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
Blk
Read
Fail%
----?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
Blk
Write
Fail%
----?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
KBs
/Blk
Read
------?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
KBs
/Blk
Write
------?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
Msgs
/Blk
Read
----?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
Note: The GroupID column only appears in the ResHostByGroup output report.
Msgs
/Blk
Write
----?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
Avg
ReqQ
Len
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
Max
ReqQ
Len
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
195
Chapter 15: Resource Usage Macros
ResLdvByNode Macros
ResLdvByNode Macros
Function
Macro...
Reports the logical device traffic channeled through...
ResLdvByNode
each node by totaling its controller links into one summarized node
output line.
ResLdvOneNode
a specific node by totaling all its controller links into one summarized
node output line.
ResLdvByGroup
a node grouping.
Input Format Examples
The input forms of these three macros are described below.
EXEC ResLdvByNode
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResLdvOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXEC ResLdvByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, FromTime, ToDate,
ToTime, FromNode, ToNode and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSldv.
•
Name the node log rate.
Output Examples
The reports in the following sections are sample output reports from the ResLdvByNode, the
ResLdvOneNode, and the ResLdvByGroup macros, respectively, where:
196
Column...
Reports the...
Reads / Sec
average number of logical device reads per second.
Writes / Sec
average number of logical device writes per second.
Rd KB / I/O
average number of KBs per logical device read.
Wrt KB / I/O
average number of KBs per logical device write.
Avg I/O Resp
average response time for a logical device read or write in seconds.
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResLdvByNode Macros
Column...
Reports the...
Max Concur Rqsts
maximum number of concurrent requests during the log period.
Avg Out Rqsts
average number of outstanding requests.
Out Rqst Time %
percent of time there are outstanding requests.
ResLdvByNode Sample Output
06/09/26
LOGICAL DEVICE TRAFFIC BY NODE
Avg
Avg
Ldv
Node
Reads
Writes
KB
Date Type
Time
Id
/ Sec
/ Sec
/ I/O
-------- ---- -------- ------ -------- -------- -----06/09/26 DISK 10:09:45 001-01
0.00
2.00
4.20
10:10:00 001-01
0.00
1.27
5.89
10:10:15 001-01
0.00
2.20
5.88
10:10:30 001-01
0.00
1.20
6.22
10:10:45 001-01
0.00
3.53
3.96
10:11:00 001-01
0.00
1.33
5.85
10:11:15 001-01
0.00
2.00
4.30
10:11:30 001-01
0.00
1.33
5.65
10:11:45 001-01
0.00
1.87
8.71
10:12:00 001-01
0.00
40.67
31.27
10:12:15 001-01
0.00
3.40
16.57
10:12:30 001-01
0.00
5.40
7.44
10:12:45 001-01
0.00
1.87
14.29
SDSK 10:09:45 001-01
10:10:00 001-01
10:10:15 001-01
10:10:30 001-01
10:10:45 001-01
10:11:00 001-01
10:11:15 001-01
10:11:30 001-01
10:11:45 001-01
10:12:00 001-01
0.13
0.07
0.00
0.44
0.50
0.48
0.51
0.88
0.97
0.98
1.00
7.98
9.21
8.73
9.01
8.45
8.85
2.72
0.34
0.28
55.42
109.53
111.57
107.32
98.02
100.64
100.83
410.24
******
******
Page
1
Out
I/O
Resp
------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Out
Rqsts
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
4.0
0.0
0.0
0.0
Rqst
Time %
-----1.3%
0.6%
1.3%
0.8%
2.5%
1.0%
1.3%
0.7%
1.0%
100.0%
1.4%
5.2%
0.9%
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.0
1.2
1.3
1.1
1.1
1.0
1.0
0.3
0.1
0.0
3.2%
9.1%
9.1%
9.1%
11.2%
9.1%
9.1%
9.1%
9.2%
8.6%
Note: The NodeId column only appears in the ResLdvByNode output report.
ResLdvOneNode Sample Output
06/09/26
Date
-------06/09/26
LOGICAL DEVICE TRAFFIC FOR NODE 001-01
Ldv
Type
---DISK
SDSK
Resource Usage Macros and Tables
Time
-------10:09:45
10:10:00
10:10:15
10:10:30
10:10:45
10:11:00
10:11:15
10:11:30
10:11:45
10:12:00
10:12:15
10:12:30
10:12:45
Reads
/ Sec
-------0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
Writes
/ Sec
-------2.00
1.27
2.20
1.20
3.53
1.33
2.00
1.33
1.87
40.67
3.40
5.40
1.87
KB
/ I/O
-----4.20
5.89
5.88
6.22
3.96
5.85
4.30
5.65
8.71
31.27
16.57
7.44
14.29
Avg
I/O
Resp
------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Avg
Out
Rqsts
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
4.0
0.0
0.0
0.0
Out
Rqst
Time %
-----1.3%
0.6%
1.3%
0.8%
2.5%
1.0%
1.3%
0.7%
1.0%
100.0%
1.4%
5.2%
0.9%
10:09:45
10:10:00
10:10:15
10:10:30
10:10:45
10:11:00
10:11:15
0.13
0.07
0.00
0.44
0.50
0.48
0.51
1.00
7.98
9.21
8.73
9.01
8.45
8.85
55.42
109.53
111.57
107.32
98.02
100.64
100.83
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.0
1.2
1.3
1.1
1.1
1.0
1.0
3.2%
9.1%
9.1%
9.1%
11.2%
9.1%
9.1%
197
Chapter 15: Resource Usage Macros
ResLdvByNode Macros
10:11:30
10:11:45
10:12:00
10:12:15
10:12:30
10:12:45
0.88
0.97
0.98
0.59
0.08
0.00
2.72
0.34
0.28
3.14
4.15
0.39
410.24
******
******
285.78
16.99
32.94
0.000
0.000
0.000
0.000
0.000
0.000
0.3
0.1
0.0
0.1
0.1
0.0
9.1%
9.2%
8.6%
9.1%
9.2%
1.0%
Max
Concur
Rqsts
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
Out
Rqst
Time %
-----1.3%
0.6%
1.3%
0.8%
2.5%
1.0%
1.3%
0.7%
1.0%
100.0%
1.4%
5.2%
0.9%
ResLdvByGroup Sample Output
06/09/26
LOGICAL DEVICE TRAFFIC BY GROUP Page
Grp Ldv
Date Id
Type
-------- --- ---06/09/26 A
DISK
SDSK
Time
--------10:09:45
10:10:00
10:10:15
10:10:30
10:10:45
10:11:00
10:11:15
10:11:30
10:11:45
10:12:00
10:12:15
10:12:30
10:12:45
Reads
/ Sec
-------0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
10:09:45
10:10:00
10:10:15
10:10:30
10:10:45
10:11:00
10:11:15
10:11:30
10:11:45
10:12:00
10:12:15
10:12:30
10:12:45
0.13
0.07
0.00
0.44
0.50
0.48
0.51
0.88
0.97
0.98
0.59
0.08
0.00
Writes
/ Sec
-------2.00
1.27
2.20
1.20
3.53
1.33
2.00
1.33
1.87
40.67
3.40
5.40
1.87
1.00
7.98
9.21
8.73
9.01
8.45
8.85
2.72
0.34
0.28
3.14
4.15
0.39
Rd KB Wrt KB
/ I/O
/ I/O
------- -----?
4.20
?
5.89
?
5.88
?
6.22
?
3.96
?
5.85
?
4.30
?
5.65
?
8.71
?
31.27
?
16.57
?
7.44
?
14.29
121.27
139.00
?
113.33
12.12
12.01
12.08
******
******
******
******
295.14
?
46.64
109.28
111.57
107.02
102.76
105.72
105.93
94.90
39.43
50.13
9.85
11.29
32.94
1
Avg
I/O
Resp
------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
3.2%
9.1%
9.1%
9.1%
11.2%
9.1%
9.1%
9.1%
9.2%
8.6%
9.1%
9.2%
1.0%
Note: The GroupID column only appears in the ResLdvByGroup output report.
198
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResPdskByNode Macros: Pdisk Device Traffic
ResPdskByNode Macros: Pdisk Device Traffic
Function
Macro...
Reports the device traffic...
ResPdskByNode
by a physical node.
ResPdskOneNode
for a specified node.
ResPdskByGroup
node grouping.
Input Format Examples
The input forms of these three macros are described below.
EXEC ResPdskByNode
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResPdskOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXEC ResPdskByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, FromTime, ToDate,
ToTime, FromNode, ToNode and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSpdsk.
•
Name the node log rate.
Output Examples
The following table describes the statistics columns in all output reports (with the exception
of ResPdiskByNode, which reports by NodeId columns, and ResPdiskByGroup, which reports
by NodeType column).
Column...
Reports the...
ReadCnt/Sec
average number of device reads per second.
WriteCnt/Sec
average number of device writes per second.
Rd KB/ I/O
average number of KBs per device read.
Wrt KB/ I/O
average number of KBs per device write.
Avg I/O Resp
average response time for a device read or write in seconds.
Resource Usage Macros and Tables
199
Chapter 15: Resource Usage Macros
ResPdskByNode Macros: Pdisk Device Traffic
Column...
Reports the...
Max Concur Rqsts
maximum number of concurrent requests during the log period.
Out Rqst Time %
percent of time there are outstanding requests.
ResPdskByNode Sample Output
07/11/28
Date
-------07/11/28
PDISK TRAFFIC BY NODE
Pdisk
Type
-----DISK
Page
Time
-------13:20:00
Node
Id
-----001-01
Reads
/ Sec
-------0.10
Writes
/ Sec
-------0.23
Rd KB
/ I/O
------*******
Wrt KB
/ I/O
------*******
Avg
I/O
Resp
------0.004
Out
Rqst
Time %
-----0.0%
13:21:00
001-01
0.12
0.41
*******
4202.15
0.002
0.0%
13:22:00
001-01
0.13
0.49
*******
3623.05
0.001
0.0%
13:24:00
001-01
0.05
0.20
4717.71
5262.77
0.002
0.0%
13:25:00
001-01
0.07
0.35
2560.00
4637.26
0.001
0.0%
13:26:00
001-01
0.11
0.42
6537.85
4485.12
0.001
0.0%
13:28:00
001-01
0.06
0.19
3396.27
4785.63
0.001
0.0%
13:29:00
001-01
0.14
0.45
3602.29
4943.64
0.003
0.0%
13:30:00
001-01
0.12
0.40
5961.14
5274.67
0.002
0.0%
13:32:00
001-01
0.07
0.18
3990.59
3856.34
0.000
0.0%
13:33:00
001-01
0.17
0.53
4532.71
5745.23
0.001
0.0%
13:34:00
001-01
0.11
0.38
5730.46
4975.30
0.002
0.0%
13:36:00
001-01
0.05
0.17
5218.46
5677.51
0.002
0.0%
13:37:00
001-01
0.18
0.51
3990.59
5125.33
0.001
0.0%
13:38:00
001-01
0.11
0.37
5218.46
4846.55
0.001
0.0%
13:39:00
001-01
0.14
0.42
3990.59
4758.59
0.001
0.0%
13:41:00
001-01
0.05
0.17
5139.69
4660.36
0.002
0.0%
13:42:00
001-01
0.11
0.28
5017.60
5546.67
0.001
0.0%
13:43:00
001-01
0.14
0.41
6731.29
5616.33
0.002
0.0%
13:45:00
001-01
0.06
0.19
4176.00
4874.04
0.001
0.0%
13:46:00
001-01
0.07
0.34
2523.43
6260.36
0.002
0.0%
13:47:00
001-01
0.13
0.38
6192.00
5990.40
0.002
0.0%
1
Note: The NodeId column only appears in the ResPdskByNode output report.
200
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResPdskByNode Macros: Pdisk Device Traffic
ResPdskOneNode Sample Output
07/11/28
PDISK Traffic for Node 001-01
Date
-------07/11/28
Pdisk
Type
-----DISK
Time
-------13:20:00
13:21:00
13:22:00
13:24:00
13:25:00
13:26:00
13:28:00
13:29:00
13:30:00
13:32:00
13:33:00
13:34:00
13:36:00
13:37:00
13:38:00
13:39:00
13:41:00
13:42:00
13:43:00
13:45:00
13:46:00
13:47:00
13:49:00
Reads
/ Sec
-------0.10
0.12
0.13
0.05
0.07
0.11
0.06
0.14
0.12
0.07
0.17
0.11
0.05
0.18
0.11
0.14
0.05
0.11
0.14
0.06
0.07
0.13
0.05
Writes
/ Sec
-------0.23
0.41
0.49
0.20
0.35
0.42
0.19
0.45
0.40
0.18
0.53
0.38
0.17
0.51
0.37
0.42
0.17
0.28
0.41
0.19
0.34
0.38
0.21
Rd KB
/ I/O
------*******
*******
*******
4717.71
2560.00
6537.85
3396.27
3602.29
5961.14
3990.59
4532.71
5730.46
5218.46
3990.59
5218.46
3990.59
5139.69
5017.60
6731.29
4176.00
2523.43
6192.00
3693.71
Page
Wrt KB
/ I/O
------*******
4202.15
3623.05
5262.77
4637.26
4485.12
4785.63
4943.64
5274.67
3856.34
5745.23
4975.30
5677.51
5125.33
4846.55
4758.59
4660.36
5546.67
5616.33
4874.04
6260.36
5990.40
5878.52
Avg
I/O
Resp
------0.004
0.002
0.001
0.002
0.001
0.001
0.001
0.003
0.002
0.000
0.001
0.002
0.002
0.001
0.001
0.001
0.002
0.001
0.002
0.001
0.002
0.002
0.002
1
Out
Rqst
Time %
-----0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
Note: The NodeId column only appears in the ResPdskOneNode output report.
ResPdskByGroup Sample Output
06/09/26
PDISK TRAFFIC BY GROUP
Node Pdisk
Date Type Type
-------- ---- -----06/09/26 4400 DISK
Time
-------10:09:45
10:10:00
10:10:15
10:10:30
10:10:45
10:11:00
10:11:15
10:11:30
10:11:45
10:12:00
10:12:15
10:12:30
10:12:45
ReadCnt WriteCnt
Rd KB
Wrt KB
/ Sec
/ Sec
/ I/O
/ I/O
-------- -------- ------- ------0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
0.00
0.00
?
?
Page
Avg
I/O
Resp
------?
?
?
?
?
?
?
?
?
?
?
?
?
1
Max
Out
Concur
Rqst
Rqsts Time %
------ -----0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
0.0
0.0%
Note: The GroupID column only appears in the ResPdskByGroup output report.
Resource Usage Macros and Tables
201
Chapter 15: Resource Usage Macros
ResMemMgmtByNode Macros
ResMemMgmtByNode Macros
Function
Macro...
Reports memory management activity for...
ResMemMgmtByNode
each individual node.
ResMemMgmtOneNode
a specific node.
ResMemByGroup
a node grouping.
Input Format Examples
The input forms of these three macros are described below.
EXEC ResMemMgmtByNode
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResMemMgmtOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXEC ResMemByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, FromTime, ToDate,
ToTime, FromNode, ToNode and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSpma.
•
Name the node log rate.
Output Examples
The reports in the following sections are sample output reports from the
ResMemMgmtByNode, the ResMemMgmtOneNode macros, and the ResMemByGroup,
respectively, where:
Column...
Reports the...
% Mem Free
current snapshot of the percent of memory that is unused.
Text Alocs/ Sec
average number of text page allocations per second.
text pages are allocations of memory for code that is not associated with
system-level overhead tasks.
VPR Alocs/ Sec
202
average number of vproc-specific page and segment allocations per
second on a node.
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResMemMgmtByNode Macros
Column...
Reports the...
KB/ VPR Aloc
average KBs per vproc-specific page and segment allocation on a node.
Aloc Fail %
percent of memory allocation attempts that failed.
Ages/ Sec
average number of times memory pages were aged out per second.
# Proc Swp
current number of processes that are swapped out.
Page Drops/ Sec
average number of text pages dropped from memory per second.
Page drops are text pages that are dropped from memory to increase the
amount of available memory.
Page Reads/ Sec
average number of memory pages read from disk per second.
Page reads include both memory text pages and task context pages, such
as scratch, stack, and so on.
Page Writes/ Sec
average number of memory pages written to disk per second.
Page writes include only task context pages.
Swap Drops/ Sec
average number of disk segments dropped from memory per second.
Swap drops include all disk segments dropped from memory because
their ancestor processes were swapped out.
Swap Reads/ Sec
average number of disk segments reread back into memory, after being
swapped, out per second.
Swap reads include all reread disk segments that had been previously
dropped from memory because their ancestor processes were swapped
out.
KB/Swp Drp
average size, in KBs, of disk segments dropped from memory because
their ancestor processes were swapped out.
KB/Swp Rd
average size, in KBs, of reread disk segments that had been previously
dropped from memory because their ancestor processes were swapped
out.
P+S Drops/ Sec
average number of paged, swapped page, or segment drops per second.
This statistic includes both the memory text pages (Pg Drps/ Sec), and the
disk segments (Swp Drps/ Sec), that were dropped.
P+S Reads/ Sec
average number of paged, swapped page, or segment reads per second.
Includes both the memory text pages and task context pages (Pg Rds/
Sec), and the disk segments (Swp Rds/ Sec), reread back into memory
after being swapped out.
P+S Writes/ Sec
average total number of paged, swapped page, or segment writes per
second.
P+S IO %
percent of total logical device inputs and outputs that are paging or
swapping inputs and outputs.
Resource Usage Macros and Tables
203
204
ResMemMgmtByNode Sample Output
08/09/29
Date
Time
-------- -------08/09/29 11:35:00
11:36:00
11:37:00
MEMORY MANAGEMENT ACTIVITY BY NODE
Page
1
%
Text
VPR
KB Aloc
# Page
Page Page Swap Swap
KB
KB
P+S
P+S
P+S
Node Mem Alocs Alocs /VPR Fail Ages Proc Drops Reads Wrts Drops Reads /Swp /Swp
Drops Reads Writes P+S
Id Free
/Sec
/Sec Aloc
% /Sec Swap /Sec
/Sec /Sec /Sec /Sec Drp
Rd
/Sec
/Sec
/Sec IO %
------ ---- ------ ------ ---- ---- ---- ---- ----- ------ ----- ----- ----- ---- ---- ------- ------ ------- ---001-01 15%
0.0
0.0
?
? 0.0
0
0.0
53
1.8
0.0
0.0
?
?
0.0
53
1.8 97%
001-01 15%
0.0
0.0
?
? 0.0
0
0.0
2
0.0
0.0
0.0
?
?
0.0
2
0.0 50%
001-01 16%
0.0
0.0
?
? 0.0
0
0.0
90 46.4
0.0
0.0
?
?
0.0
90
46.4 97%
Note: The NodeId column only appears in the ResMemMgmtByNode output report.
ResMemMgmtOneNode Sample Output
08/09/29
Date
Time
-------- -------08/09/29 11:35:00
11:36:00
11:37:00
11:38:00
11:40:00
11:41:00
Memory Management Activity for Node 001-01
Page
1
%
Text
VPR
KB Aloc
# Page
Page Page Swap Swap
KB
KB
P+S
P+S
P+S
Mem Alocs Alocs /VPR Fail Ages Proc Drops Reads Wrts Drops Reads /Swp /Swp Drops Reads Writes P+S
Free
/Sec
/Sec Aloc
% /Sec Swap /Sec
/Sec /Sec /Sec /Sec Drp
Rd
/Sec
/Sec
/Sec IO %
---- ------ ------ ---- ---- ---- ---- ----- ------ ----- ----- ----- ---- ---- ------ ------ ------ ---15%
0.0
0.0
?
? 0.0
0
0.0
53
1.8
0.0
0.0
?
?
0
53
2 97%
15%
0.0
0.0
?
? 0.0
0
0.0
2
0.0
0.0
0.0
?
?
0
2
0 50%
16%
0.0
0.0
?
? 0.0
0
0.0
90 46.4
0.0
0.0
?
?
0
90
46 97%
16%
0.0
0.0
?
? 0.0
0
0.0
10
3.4
0.0
0.0
?
?
0
10
3 92%
16%
0.0
0.0
?
? 0.0
0
0.0
1
0.0
0.0
0.0
?
?
0
1
0 45%
16%
0.0
0.0
?
? 0.0
0
0.0
5
2.0
0.0
0.0
?
?
0
5
2 73%
ResMemByGroup Sample Output
08/09/29
Date
Time
-------- -------08/09/29 11:35:00
11:36:00
11:37:00
11:38:00
MEMORY MGMT ACTIVITY BY GROUP
Page
1
%
Text
VPR
KB Aloc
# Page Page Page Swap Swap
KB
KB
P+S
P+S
P+S
Group Mem Alocs Alocs /VPR Fail Ages Proc Drops Reads Wrts Drops Reads /Swp /Swp
Drops
Reads Writes P+S
Id Free
/Sec
/Sec Aloc
% /Sec Swap /Sec /Sec /Sec /Sec /Sec Drp
Rd
/Sec
/Sec
/Sec IO %
----- ---- ------ ------ ---- ---- ---- ---- ----- ----- ----- ----- ----- ---- ---- ------- ------- ------ ---A
15%
0.0
0.0
?
? 0.0
0
0.0 52.6
1.8
0.0
0.0
?
?
0.0
52.6
1.8 97%
A
15%
0.0
0.0
?
? 0.0
0
0.0
2.1
0.0
0.0
0.0
?
?
0.0
2.1
0.0 50%
A
16%
0.0
0.0
?
? 0.0
0
0.0 89.8 46.4
0.0
0.0
?
?
0.0
89.8
46.4 97%
A
16%
0.0
0.0
?
? 0.0
0
0.0 10.3
3.5
0.0
0.0
?
?
0.0
10.3
3.5 92%
Resource Usage Macros and Tables
Note: The GroupID column only appears in the ResMemByGroup output report.
Chapter 15: Resource Usage Macros
ResNetByNode Macros
ResNetByNode Macros
Function
Macro...
Reports net traffic for...
ResNetByNode
each node.
ResNetOneNode
a specific node.
ResNetByGroup
nodes summarized by node groups.
Input Format Examples
The input forms of these three macros are described below.
EXEC ResNetByNode
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResNetOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXEC ResNetByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, FromTime, ToDate,
ToTime, FromNode, ToNode and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSpma.
•
Name the node log rate.
Output Examples
The reports in the following sections are sample output reports from the ResNetByNode, the
ResNetOneNode, and the ResNetByGroup macros, respectively, where:
Column...
Reports the...
% Retries
percent of total net circuit attempts that caused software backoffs (BNS
service-blocked occurrences).
Note: This value reflects how many times the hardware backed off a
connection because the switch nodes could not route to the end point. That
implies that the end point was busy or, in switch node terms, the routing
path was busy. A value over 100% does not imply a problem, but shows that
there were multiple attempts to send new messages while the Bynet path was
busy. On a busy system, this can be a normal level of activity.
Total Reads/ Sec
Resource Usage Macros and Tables
average number of net reads per second.
205
Chapter 15: Resource Usage Macros
ResNetByNode Macros
Column...
Reports the...
Total Writes/ Sec
average number of net writes per second.
Total IOs/ Sec
average number of net reads and writes per second.
KB/ IO
average KBs per net read or write.
% PtP
percent of total net reads and writes that are point-to-point reads and writes.
% Brd
percent of total net reads and writes that are broadcast reads and writes.
Note: In the following examples, the NodeId column appears only in the ResNetByNode
output report. The GroupID column only appears in the ResNetByGroup output report. For
all the examples, the values in the Total Reads/ Sec and Total Writes/ Sec are expected to be
equal on SMP (single-node, vnet) systems.
ResNetByNode Sample Output
00/10/16
NET ACTIVITY BY NODE
Date
Time
---------- -------2000/10/16 11:20:00
Page 2
Total
Total
Total
Node
% ReReads
Writes
IOs
KB
Id
tries
/Sec
/Sec
/Sec
/IO
------ ------ ------- ------- ------- -----001-03
0.0%
0.46
0.39
0.85
0.4
001-04
0.0%
0.55
0.47
1.02
0.4
%
PtP
--92
93
%
Brd
--8
7
11:25:00
001-03
001-04
0.0%
0.0%
0.39
0.39
0.33
0.32
0.72
0.71
0.4
0.4
90
90
10
10
11:30:00
001-03
001-04
0.0%
0.0%
0.44
0.55
0.37
0.47
0.81
1.02
0.4
0.4
91
92
9
8
11:35:00
001-03
001-04
2.5%
2.5%
20.84
23.07
12.53
15.51
33.37
38.58
1.8
1.8
73
74
27
26
11:40:00
001-03
001-04
24.7%
20.6%
35.44
37.16
35.56
38.87
71.00
76.03
17.4
13.8
93
93
7
7
11:45:00
001-03
001-04
15.9%
28.1%
13.47
11.79
10.71
12.63
24.18
24.42
8.3
12.8
76
83
24
17
11:50:00
001-03
001-04
3.3%
4.1%
18.92
22.77
14.18
20.97
33.11
43.74
1.3
1.9
77
75
23
25
ResNetOneNode Sample Output
00/10/16
Net Activity for Node 001-03
Date
-------00/10/16
206
Time
-------10:19:00
10:20:00
10:21:00
10:22:00
10:23:00
10:30:00
10:35:00
10:40:00
10:45:00
10:50:00
10:55:00
11:00:00
11:05:00
11:10:00
% Retries
-----0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
0.0%
Total
Reads
/Sec
------0.78
2.87
3.08
2.13
2.23
0.25
0.53
0.51
0.48
0.52
0.46
0.58
0.57
0.54
Total
Writes
/Sec
------0.07
2.65
2.07
2.07
2.17
0.18
0.47
0.44
0.42
0.45
0.39
0.51
0.38
0.47
Total
IOs
/Sec
------0.85
5.52
5.15
4.20
4.40
0.43
1.00
0.95
0.90
0.97
0.85
1.09
0.95
1.01
Page 1
KB
/IO
-----1.1
0.5
0.6
0.5
0.5
0.4
0.4
0.5
0.4
0.5
0.4
0.4
0.5
0.4
%
PtP
--8
96
80
98
98
84
93
93
92
93
92
94
79
93
%
Brd
--92
4
20
2
2
16
7
7
8
7
8
6
21
7
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResNetByNode Macros
11:15:00
11:20:00
0.0%
0.0%
0.46
0.46
0.40
0.39
0.86
0.85
0.5
0.4
92
92
8
8
ResNetByGroup Sample Output
00/10/16
NET ACTIVITY BY Group
Date
---------2000/10/16
Resource Usage Macros and Tables
Group
% ReTime
Id
tries
-------- ------ -----11:20:00
B
0.0%
Reads
Writes
/Sec
/Sec
------- ------0.55
0.47
Page 2
IOs
/Sec
------1.02
KB
%
%
/IO PtP Brd
------ --- --0.4
93
7
11:25:00
A
B
0.0%
0.0%
0.39
0.39
0.33
0.32
0.72
0.71
0.4
0.4
90
90
10
10
11:30:00
A
B
0.0%
0.0%
0.44
0.55
0.37
0.47
0.81
1.02
0.4
0.4
91
92
9
8
11:35:00
A
B
2.5%
2.5%
20.84
23.07
12.53
15.51
33.37
38.58
1.8
1.8
73
74
27
26
11:40:00
A
B
24.7%
20.6%
35.44
37.16
35.56
38.87
71.00
76.03
17.4
13.8
93
93
7
7
11:45:00
A
B
15.9%
28.1%
13.47
11.79
10.71
12.63
24.18
24.42
8.3
12.8
76
83
24
17
11:50:00
A
B
3.3%
4.1%
33.11
43.74
1.3
1.9
77
75
23
25
11:55:00
A
B
55.8%
41.1%
73.46
88.72
22.3
17.7
95
96
5
4
12:00:00
A
B
5.1%
5.8%
32.27
33.16
2.0
1.7
73
70
27
30
12:05:00
A
B
24.2%
10.6%
33.09
26.97
28.57
25.97
61.67
52.94
14.6
5.5
90
91
10
9
12:10:00
A
B
73.8%
57.4%
17.33
28.12
14.01
26.65
31.34
54.77
23.2
23.0
91
93
9
7
12:15:00
A
B
3.9%
6.3%
37.12
36.83
2.0
1.8
73
73
27
27
12:20:00
A
B
48.7%
34.9%
70.83
71.86
18.0
13.2
95
93
5
7
18.92
22.77
40.01
44.35
19.11
22.13
21.02
22.13
36.18
38.16
14.18
20.97
33.45
44.37
13.16
11.03
16.10
14.70
34.65
33.70
207
Chapter 15: Resource Usage Macros
ResNode Macros
ResNode Macros
Function
Macro...
Provides a summary of resource usage...
ResNode
averaged across all nodes.
ResOneNode
for a specific node.
ResNodeByNode
node by node.
ResNodeByGroup
for a node grouping.
Input Format Examples
The input forms of these four macros are described below.
EXEC ResNode
(FromDate,ToDate,FromTime,ToTime);
Note: The ResNode macro syntax does not include the FromNode and ToNode parameters to
specify a range of nodes.
EXEC ResOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXEC ResNodeByNode
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResNodeByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, ToDate, FromTime,
ToTime, FromNode, ToNode, and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSpma.
•
Name the node log rate.
Output Examples
The reports in the following sections are sample output reports from the ResNode, the
ResOneNode, the ResNodebyNode, and the ResNodeByGroup macros, respectively.
The following table describes the 19 statistics columns, after the Date and Time columns, in
the ResNode output report.
208
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResNode Macros
Statistics columns
Description
1 through 3
CPU usage.
4 through 8
Logical device interface.
9 through 14
Memory interface.
15 through 17
Net interface.
18 and 19
General node process scheduling.
The following table describes the 16 statistics columns, after the Date and Time columns, in
the ResOneNode output report.
Statistics columns
Description
1 and 2
CPU usage.
3 through 6
Logical device interface.
7 through 11
Memory interface.
12 through 14
Net interface.
15 and 16
General node process scheduling.
The following table describes the 17 statistics columns, after the Date and Time columns, in
the ResNodebyNode output report.
Statistics columns
Description
1 and 2
CPU usage.
3 through 6
Logical device interface.
7 through 12
Memory interface.
13 through 15
Net interface.
16 and 17
General node process scheduling.
The following table describes the 17 statistics columns, after the Date and Time columns, in
the ResNodeByGroup output report.
Statistics columns
Description
1
GroupId as defined in the associated view as a grouping of one or
more nodes.
2 and 3
CPU usage.
Resource Usage Macros and Tables
209
Chapter 15: Resource Usage Macros
ResNode Macros
Statistics columns
Description
4 through 7
Logical device interface.
8 through 12
Memory interface.
13 through 15
Net interface.
16 and 17
General node process scheduling.
The following table describes the statistics columns in all output reports (with the exception
of ResNodeByNode, which has a NodeId column, and ResNodeByGroup, which has a
GroupId column).
Column…
Reports the…
CPU Bsy %
percent of time the CPUs are busy, based on average CPU usage
per node.
CPU Eff % (ResNode report)
parallel efficiency of node CPU usage.
Parallel efficiency is the total percent of time nodes are busy. It is
the average for all nodes of total busy divided by the total busy
time of the busiest node.
WIO %
percent of time the CPUs are idle and waiting for completion of an
I/O operation.
Ldv IOs /Sec
average number of logical device reads and writes per second for
each node.
Ldv Eff %
parallel efficiency of the logical device (disk) I/Os. It is the average
number of I/Os per node divided by the number of I/Os
performed by the node with the most I/Os.
(ResNode report)
210
P+S % of IOs
percent of logical device reads and writes that are for paging or
swapping purposes.
Read % of IOs
percent of logical device reads and writes that are reads.
Ldv KB / IO
average size of a logical device read or write.
Fre Mem %
percent of memory that is unused.
Mem Aloc / Sec
average number of memory allocations per second, per node.
Mem Fai %
percent of memory allocation attempts that failed.
Mem Age /Sc
Average number of times memory pages were aged out per
second, per node.
A+R % of IOs
percent of logical device reads and writes that are disk segment
reads and writes.
TPtP IOs /Sec
total point-to-point net reads and writes per second, per node.
TMlt IOs /Sec
total multicast (broadcast or merge) net reads and writes per
second, per node.
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResNode Macros
Column…
Reports the…
Net Rtry %
percent of transmission attempts that resulted in retries.
Prc Blks / Sec
number of times per second, per node, that processes other than
message and timer waits are blocked.
ms /Blk
average time, in milliseconds, spent waiting for a blocked process
other than message and timer waits.
Net Rx Bsy %
percent of time the network was busy either receiving.
Net Tx Bsy %
percent of time the network was busy transmitting.
ResNode Sample Output
01/07/12
CPU CPU
Bsy Eff
Date
Time
%
%
------- -------- --- --01/07/12 04:45:40 2 100
04:46:00 2 100
04:46:20 1 100
04:46:40 2 100
04:47:00 2 100
04:47:20 1 100
04:47:40 1 100
04:48:00 2 100
04:48:20 1 100
04:48:40 2 100
04:49:00 2 100
04:49:20 2 100
04:49:40 2 100
04:50:00 2 100
04:50:20 1 100
04:50:40 1 100
04:51:00 2 100
04:51:20 1 100
04:51:40 2 100
04:52:00 2 100
04:52:20 1 100
04:52:40 1 100
04:53:00 2 100
04:53:20 1 100
04:53:40 2 100
04:54:00 2 100
04:54:20 1 100
GENERAL RESUSAGE SUMMARY Page 4
Average across all nodes
Ldv Ldv P+S Rd Ldv Fre
Mem Mem Mem A+R TPtP TMlt Net
Prc
WIO IOs Eff %of %of KB Mem Aloc Fai Age %of IOs
IOs Rty Blks
% /Sec
% IOs IOs /IO
% /Sec
% /Sec IOs /Sec /Sec
% /Sec
--- ----- --- --- --- --- --- ---- --- ---- --- ----- ----- --- ----15
16 100
0
0 22
1
1
0
0 100
0
0
0
40
16
16 100
0
0 23
1
1
0
0 100
0
0
0
39
16
16 100
0
0 19
1
1
0
0 100
0
0
0
39
17
16 100
0
0 24
1
1
0
0 100
0
0
0
40
16
16 100
0
0 22
1
1
0
0 100
0
0
0
39
16
16 100
0
0 22
1
1
0
0 100
0
0
0
40
17
17 100
0
0 22
1
1
0
0 100
0
0
0
41
15
16 100
0
0 24
1
1
0
0 100
0
0
0
39
14
16 100
0
0 24
1
1
0
0 100
0
0
0
40
16
17 100
0
0 23
1
1
0
0 100
0
0
0
41
16
16 100
0
0 22
1
1
0
0 100
0
0
0
39
17
17 100
0
0 23
1
1
0
0 100
0
0
0
41
16
17 100
0
0 22
1
1
0
0 100
0
0
0
41
16
16 100
0
0 23
1
3
0
0 100
0
0
0
42
15
16 100
0
0 18
1
1
0
0 100
0
0
0
39
16
16 100
0
0 20
1
1
0
0 100
0
0
0
40
16
16 100
0
0 21
1
1
0
0 100
0
0
0
39
16
16 100
0
0 19
1
1
0
0 100
0
0
0
40
16
17 100
0
0 23
1
1
0
0 100
0
0
0
42
15
16 100
0
0 19
1
1
0
0 100
0
0
0
39
16
16 100
0
0 22
1
1
0
0 100
0
0
0
40
15
16 100
0
0 19
1
1
0
0 100
0
0
0
40
15
16 100
0
0 18
1
1
0
0 100
0
0
0
39
15
16 100
0
0 20
1
1
0
0 100
0
0
0
40
16
16 100
0
0 22
1
1
0
0 100
0
0
0
40
16
16 100
0
0 22
1
1
0
0 100
0
0
0
40
16
17 100
0
0 19
1
1
0
0 100
0
0
0
40
ms Net Net
/
Rx
Tx
Blk Bsy% Bsy%
----- --- ---386
?
?
561
?
?
383
?
?
437
?
?
532
?
?
383
?
?
417
?
?
446
?
?
426
?
?
1173
?
?
456
?
?
416
?
?
395
?
?
2481
?
?
463
?
?
353
?
?
662
?
?
505
?
?
341
?
?
537
?
?
480
?
?
395
?
?
491
?
?
461
?
?
1093
?
?
442
?
?
450
?
?
ResOneNode Sample Output
01/07/12
CPU
Bsy WIO
Date
Time
%
%
------- ------- --- --1/07/12 09:44:20 2
16
09:44:40 1
17
09:45:00 1
16
09:45:20 2
17
09:45:40 1
17
09:46:00 2
17
09:46:20 2
16
09:46:40 1
16
09:47:00 2
16
09:47:20 2
16
09:47:40 2
17
09:48:00 1
15
09:48:20 2
16
09:48:40 2
16
09:49:00 1
16
General Resource Usage Summary for Node 001-01
Ldv
P+S
Rd
IOs
%of %of
/Sec IOs IOs
----- --- --17
0
0
16
0
0
16
0
0
16
0
0
16
0
0
16
0
0
17
0
0
16
0
0
17
0
0
16
0
0
16
0
0
16
0
0
16
0
0
17
0
0
16
0
0
Resource Usage Macros and Tables
Ldv Fre
Mem
KB Mem
Aloc
/IO
%
/Sec
--- --- ----21
1
1
20
1
1
21
1
1
22
1
1
19
1
1
23
1
1
22
1
1
20
1
1
24
1
1
21
1
1
20
1
1
23
1
1
21
1
1
24
1
1
22
1
1
Mem
Fai
%
--0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Mem A+R TPtP
TMlt Net Prc
Age %of
IOs IOs
Rtry Blks
/Sc IOs /Sec
/Sec
% /Sec
--- ------- ----- --- --0 100
0
0
0
41
0 100
0
0
0
41
0 100
0
0
0
39
0 100
0
0
0
40
0 100
0
0
0
40
0 100
0
0
0
40
0 100
0
0
0
40
0 100
0
0
0
40
0 100
0
0
0
40
0 100
0
0
0
40
0 100
0
0
0
40
0 100
0
0
0
40
0 100
0
0
0
40
0 100
0
0
0
41
0 100
0
0
0
39
Page 01
ms
/
Blk
---477
371
2810
540
362
371
555
390
366
520
439
433
499
1142
378
Net
Net
Rx
Tx
Bsy% Bsy%
--- ---?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
211
Chapter 15: Resource Usage Macros
ResNode Macros
09:49:20
09:49:40
09:50:00
09:50:20
2
2
1
2
16
17
16
17
17
16
16
16
0
0
0
0
0
0
0
0
20
20
19
20
1
1
1
1
1
1
3
1
0
0
0
0
0
0
0
0
100
100
100
100
0
0
0
0
0
0
0
0
0
0
0
0
41
41
40
40
543
363
2598
506
?
?
?
?
?
?
?
?
ResNodeByNode Sample Output
01/07/12
Node by Node General Resource Usage Summary Page 8
CPU
Ldv P+S Rd Ldv Fre
Mem Mem
Bsy WIO IOs %of %of KB Mem Aloc Fai
Date
Time
NodeId
%
% /Sec IOs IOs /IO
% /Sec
%
------ -------- ------ --- --- ----- --- --- --- --- ----- --01/07/12 04:55:40 001-01 2 17
17
0
0 26
1
1
0
04:56:00 001-01 2 15
16
0
0 22
1
3
0
04:56:20 001-01 2 14
16
0
0 22
1
7
0
04:56:40 001-01 2 16
17
0
0 23
1
6
0
04:57:00 001-01 2 16
16
0
0 23
1
1
0
04:57:20 001-01 1 16
16
0
0 24
1
1
0
04:57:40 001-01 1 15
16
0
0 22
1
1
0
04:58:00 001-01 1 16
16
0
0 22
1
1
0
04:58:20 001-01 1 15
16
0
0 22
1
1
0
04:58:40 001-01 1 16
16
0
0 22
1
1
0
04:59:00 001-01 2 16
16
0
0 21
1
1
0
Mem A+R TPtP TMlt Net
Prc
ms Net Net
Age %of
IOs
IOs Rty Blks
/
Rx
Tx
/Sc IOs /Sec /Sec
% /Sec
Blk Bsy% Bsy%
---- --- ----- ----- ---- ----- ------ ---- ---0 100
0
0
0
42
442
?
?
0 100
0
0
0
41
4887
?
?
0 100
0
0
0
41
3844
?
?
0 100
0
0
0
43
402
?
?
0 100
0
0
0
40
521
?
?
0 100
0
0
0
40
529
?
?
0 100
0
0
0
40
387
?
?
0 100
0
0
0
39
452
?
?
0 100
0
0
0
40
381
?
?
0 100
0
0
0
40
1281
?
?
0 100
0
0
0
39
452
?
?
ResNodeByGroup Sample Output
01/07/12
GENERAL RESOURCE USAGE SUMMARY BY GROUP
Page 8
CPU
Ldv P+S
Rd Ldv Fre
Mem Mem A+R TPtP TMlt Net
Prc
Group Bsy WIO
IOs %of % of KB Mem Aloc Fai %of
IOs
IOs Rty Blks
Date
Time
Id
%
% /Sec IOs IOs /IO
% /Sec
% IOs /Sec /Sec
% /Sec
-------- -------- ----- --- --- ----- --- ---- --- --- ----- --- --- ----- ----- ---- ----01/07/12 04:55:40
A 2 17
17
0
0 26
1
1
0 100
0
0
0
42
04:56:00
A 2 15
16
0
0 22
1
3
0 100
0
0
0
41
04:56:20
A 2 14
16
0
0 22
1
7
0 100
0
0
0
41
04:56:40
A 2 16
17
0
0 23
1
6
0 100
0
0
0
43
04:57:00
A 2 16
16
0
0 23
1
1
0 100
0
0
0
40
04:57:20
A 1 16
16
0
0 24
1
1
0 100
0
0
0
40
04:57:40
A 1 15
16
0
0 22
1
1
0 100
0
0
0
40
04:58:00
A 1 16
16
0
0 22
1
1
0 100
0
0
0
39
04:58:20
A 1 15
16
0
0 22
1
1
0 100
0
0
0
40
04:58:40
A 1 16
16
0
0 22
1
1
0 100
0
0
0
40
04:59:00
A 2 16
16
0
0 21
1
1
0 100
0
0
0
39
212
ms
Net
Net
/
Rx
Tx
Blk
Bsy
Bsy%
------ ---- ---442
?
?
4887
?
?
3844
?
?
402
?
?
521
?
?
529
?
?
387
?
?
452
?
?
381
?
?
1281
?
?
452
?
?
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResPs Macros
ResPs Macros
Function
Macro...
Provides a summary of the Priority Scheduler resource usage...
ResPsByNode
by node, produces one row of data for each Performance Group
ID, for each logging period.
ResPsByGroup
by coexistence group, produces one row of data for each node type
in the system per logging period.
Input Format Examples
The input forms of the macros are described below.
EXEC ResPsByNode
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResPsByGroup
(FromDate,ToDate,FromTime,ToTime);
EXEC ResPsByNodeWDJoin
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResPsWDJoin
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, ToDate, FromTime,
ToTime, FromNode, ToNode, and Node parameters.
Note: Coexistence support can be accomplished using the NodeType column to do a group by
in SQL directly. Therefore, the GroupId column is not needed and the ResUsageSps table view
is not provided.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSps.
•
Name the node log rate.
In order for the ResPsWDJoin and ResPsByNodeWDJoin macros to function, you must have
Teradata ASM Category 3 rule (Workloads) enabled and the workloads defined. Each defined
workload is internally associated with a priority scheduler Performance Group, which in turn
is associated with Allocation Groups. These macros display the critical workloads in the
context of their Allocation Group relationships. For information on working with Teradata
ASM rules, see the Teradata Viewpoint Workload Designer portlet.
Output Examples
The reports in the following sections are sample output reports from the ResPsByNode and
ResPsByGroup macros.
Resource Usage Macros and Tables
213
Chapter 15: Resource Usage Macros
ResPs Macros
The following table describes the 12 statistics columns, after the Date and Time columns, in
the ResPsByNode output report.
Statistics columns
Description
1
Node ID.
2
Performance Group ID.
3 through 12
Summary of the Priority Scheduler statistics.
The following table describes the 11 statistics columns, after the Date and Time columns, in
the ResPsByGroup output report.
Statistics columns
Description
1
Node type.
2 through 11
Summary of the Priority Scheduler statistics.
The following table describes the 15 statistics columns, after the Date and Time columns, in
the ResPsByNodeWDJoin output report.
Statistics columns
Description
1
Node ID.
2
Allocation Group ID.
3
Relative weight.
4
Workload name.
5
Performance period ID.
6 through 15
Summary of the Priority Scheduler and Teradata ASM workload
statistics.
The following table describes the 14 statistics columns, after the Date and Time columns, in
the ResPsWDJoin output report.
The following table describes the summary statistics columns in all output reports (with the
exception of the ResPsWDJoin and ResPsByNodeWDJoin macros which have the CPU ms
column).
214
Column…
Reports the…
CPU Bsy %
percent of CPU time consumed by a task associated or running under the
Performance Group.
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResPs Macros
Column…
Reports the…
IO Blks / Sec
average number of logical data blocks read and (or) written by
Performance Group per second.
Num Procs
number of processes assigned to the Performance Group at the end of the
gather period.
Num Requests
number of requests of the AWT.
Avg QWait Time
average QWaitTime for each request during a specified period.
Max QWait Time
maximum time in milliseconds that work requests waited on an input
queue before being serviced.
Q Length
number of work requests waiting on the input queue for service.
Q Length Max
maximum number of work requests waiting on the input queue for
service.
Avg Svc Time
average ServiceTime for each request during a specified period.
Max Svc Time
maximum time in milliseconds that work requests required for service.
For a complete description of the above columns, see Chapter 11: “ResUsageSps Table.”
ResPsByNode Macro Sample Output
07/05/07
Date
Time
PS by Node Usage Summary Page
Page
6
NodeID
PGid
CPU
Bsy
%
IO
Blks/
Sec
Num
Num
Avg
Max
Q
Q
Procs Requests QWait QWait Length Len
Time
Time
Max
Avg
Svc
Time
Max
Svc
Time
------1-05
1-05
---1
40
--0
1
----0
0
---0
50
------0
5
----- ---?
0
0
0
----0
0
---0
0
----?
62
----0
100
15:00:00
1-04
1-04
1-05
1-05
0
40
0
40
0
1
0
1
0
0
0
0
0
54
0
50
0
2
0
3
?
0
?
2
0
0
10
0
0
0
0
0
0
0
0
0
?
215
?
162
0
220
0
270
15:20:00
1-04
1-04
1-05
1-05
0
40
0
40
0
1
0
1
0
0
0
0
0
54
0
50
0
3
0
3
?
0
?
0
0
0
0
0
0
0
0
0
0
0
0
0
?
97
?
93
0
180
0
160
15:40:00
1-04
1-04
1-05
1-05
0
40
0
40
0
1
0
1
0
0
0
0
0
54
0
50
0
4
0
3
?
?
0
?
0
0
0
0
0
0
0
0
0
0
0
0
?
50
?
102
0
80
0
150
16:00:00
1-04
1-04
1-04
1-05
1-05
0
3
40
0
40
0
1
0
1
0
0
0
0
0
0
0
0
54
0
50
0
0
3
0
5
?
?
0
?
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
?
?
130
?
71
0
0
160
0
260
17:00:00
1-04
1-04
1-05
1-05
0
40
0
40
0
1
0
1
0
0
0
0
0
54
0
0
0
3
0
50
?
0
?
3
0
0
0
0
0
0
0
0
0
0
0
0
?
112
?
62
0
140
0
90
-------- --------07/05/07 14:40:00
Resource Usage Macros and Tables
215
216
ResPsByGroup Macro Sample Output
07/05/04
PS by Group Usage Summary
Date
Time
------- -------07/05/04 13:00:00
13:10:00
13:20:00
14:00:00
CPU
IO
Avg
Node Bsy Blks Num
Num
QWait
Type
% /Sec Procs Requests
Time
---- ---- ----- ----- -------- -----UNKN
0
0
3
5
1
UNKN
0
0
5
0
0
UNKN
0
0
3
3
0
UNKN
0
0
3
3
0
Max
QWait
Time
------10
0
10
10
Page
1
Q
Avg
Max
Q
Len
Svc
Svc
Length MaxTime
Time
Time
------- ------- ------ ------0
0
30
200
0
0
102
210
0
0
30
160
0
0
52
240
ResPsByNodeWDJoin Macro Sample Output
07/08/09
Workload Usage Summary (Average Usage per AMP By Node)
1
Resource Usage Macros and Tables
PP
ID
--
CPU
ms
------
IO
Blks
/Sec
-----
Num
Procs
------
Num
Requests
--------
Avg
QWait
Time
------
Max
QWait
Time
-------
Q
Length
------
Q
Len
Max
------
Avg
Svc
Time
-------
Max
Svc
Time
-------
?
0
0
0
0
0
?
0
0
0
?
0
2
?
0
0
0
0
0
?
0
0
0
?
0
5
?
0
0
0
0
0
?
0
0
0
?
0
4
10
?
0
36
0
0
48
4
70
0
0
2
100
5
48
All_Tactical
TDWM
0
0
1084
0
7
0
0
0
364
0
3
?
220
0
0
0
0
0
18
?
1160
0
7
11
Continious Load
LobLoader
Teradata Manger
WD-ConsoleH
WD-ConsoleR
0
0
0
0
0
4156
0
19
0
0
36
0
0
0
0
0
0
0
0
0
2679
0
18
0
0
3
?
2
?
?
400
0
30
0
0
0
0
0
0
0
0
0
0
0
0
35
?
14
?
?
4120
0
280
0
0
8
5
ADW_Strategic
DWD_OLAP
Java Stored Procedures
Mixedsql
Multiuser Simulation
PEstress
WD-ConsoleM
WD-Default
0
0
0
0
0
0
0
0
2506
0
0
2848
995
0
0
10
2
0
0
10
9
0
0
0
13
0
0
21
7
0
0
0
110
0
0
124
0
0
0
12
4
?
?
5
?
?
?
13
210
0
0
340
0
0
0
130
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1548
?
?
1303
?
?
?
309
41680
0
0
47370
1063680
0
0
3720
9
2
Penalty_box
WD-ConsoleL
0
0
2613
0
3
0
4
0
43
0
4
?
30
0
0
0
0
0
7072
?
67660
0
10
12
All_Tactical
qmiles
1
0
911
3769
2
4
0
0
1
87
22
9
220
240
0
0
0
0
3875
333
500
4740
200
100
?
0
1048
10
6
270
2
50
0
0
24
1980
1
1
?
0
0
0
0
0
?
0
0
0
?
0
2
2
?
0
0
0
0
0
?
0
0
0
?
0
3
5
?
0
0
0
0
0
?
0
0
0
?
0
4
10
?
0
64
0
0
64
3
160
0
0
12
830
5
48
All_Tactical
0
957
7
0
340
3
290
0
0
45
2730
Date
--------
Time
--------
Node
ID
------
AG
ID
---
Rel
Wgt
---
07/08/06
17:57:00
1-04
1
1
2
3
1-05
Page
Workload (WD)
Name
------------------------------
Resource Usage Macros and Tables
TDWM
0
0
0
0
0
?
0
0
0
?
0
Continious Load
LobLoader
Teradata Manger
WD-ConsoleH
WD-ConsoleR
0
0
0
0
0
8223
0
19
0
0
85
0
0
0
0
1
0
0
0
0
3401
0
17
0
0
2
?
4
?
?
550
0
80
0
0
0
0
0
0
0
0
0
0
0
0
25
?
23
?
?
4220
0
100
0
0
5
ADW_Strategic
DWD_OLAP
Java Stored Procedures
Mixedsql
Multiuser Simulation
PEstress
WD-ConsoleM
WD-Default
0
0
0
0
0
0
0
0
1802
0
0
1573
2724
0
0
9
4
0
0
6
4
0
0
0
3
0
0
5
4
0
0
0
66
0
0
427
0
0
0
12
6
?
?
4
?
?
?
4
50
0
0
170
0
0
0
20
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
5564
?
?
1529
?
?
?
134
82900
0
0
82110
0
0
0
960
9
2
Penalty_box
WD-ConsoleL
0
0
1313
0
2
0
4
0
10
0
5
?
30
0
0
0
0
0
13160
?
98350
0
10
12
All_Tactical
qmiles
1
0
670
2916
2
3
0
0
3
69
84
12
510
530
0
0
0
0
1886
345
1890
4710
200
100
?
0
1062
10
6
226
2
360
0
0
32
3570
7
11
8
Note: Question marks used as values in the Workload (WD) Name column in the output above mean there is no associated
workload to the PG ID/PP ID. However, if the question mark is used as a value in any other column, the it indicates there is no
information to report for this time period (see “Question Marks” on page 176 for details).
217
Chapter 15: Resource Usage Macros
ResVdskByNode Macros
ResVdskByNode Macros
Function
Macro...
Reports the logical device traffic by...
ResVdskByNode
a physical node.
ResVdskOneNode
for a specified node.
ResVdskByGroup
a node grouping.
Input Format Examples
The input forms of these three macros are described below.
EXEC ResVdskByNode
(FromDate,ToDate,FromTime,ToTime,FromNode,ToNode);
EXEC ResVdskOneNode
(FromDate,ToDate,FromTime,ToTime,Node);
EXEC ResVdskByGroup
(FromDate,ToDate,FromTime,ToTime);
See “Executing Macros” on page 32 for a description of the FromDate, FromTime, ToDate,
ToTime, FromNode, ToNode and Node parameters.
Usage Notes
For any of these macros the following usage notes apply:
•
Logging must be enabled on ResUsageSvdsk.
•
Name the node log rate.
Output Examples
The following table describes the statistics columns in all output reports (with the exception
of ResVdiskByNode, which has the NodeId column, and ResVdskByGroup, which has the
NodeType column).
218
Column...
Reports the...
Read Cnt / Sec
average number of logical device reads per second.
Write Cnt / Sec
average number of logical device writes per second.
Rd KB / I/O
average number of KBs per logical device read.
Wrt KB / I/O
average number of KBs per logical device write.
Avg I/O Resp
average response time for a logical device read or write in seconds.
Resource Usage Macros and Tables
Chapter 15: Resource Usage Macros
ResVdskByNode Macros
Column...
Reports the...
Out Rqst Time %
percent of time there are outstanding requests.
Max Concur Rqsts
maximum number of concurrent requests during the log period.
ResVdskByNode Sample Output
06/09/26
VDISK TRAFFIC BY NODE
Date
-------06/09/26
Time
-------10:09:45
10:10:00
10:10:15
10:10:30
10:10:45
10:11:00
10:11:15
10:11:30
10:11:45
10:12:00
10:12:15
10:12:30
10:12:45
Node
Id
-----001-01
001-01
001-01
001-01
001-01
001-01
001-01
001-01
001-01
001-01
001-01
001-01
001-01
Page
Read Cnt Write Cnt Rd KB
/ Sec
/ Sec
I/O /
-------- -------- ------0.73
5.20
121.27
0.40
41.17
127.50
0.00
47.40
?
2.43
45.17
111.79
2.77
45.90
12.00
2.67
43.77
12.00
2.83
46.10
12.00
4.87
14.13 1374.25
5.37
1.77 1785.00
5.43
0.30 1785.00
3.20
9.70 1759.00
0.50
12.60
275.47
0.00
2.17
?
Avg
Wrt KB
I/O
I/O
Resp
------- ------46.69
0.023
116.34
0.152
118.98
0.143
113.54
0.126
109.93
0.118
112.07
0.119
112.32
0.107
100.01
0.081
38.15
0.065
71.56
0.064
16.76
0.039
18.84
0.038
32.94
0.017
1
Out
Rqst
Time %
-----9.7%
85.3%
98.8%
98.4%
97.7%
98.0%
97.3%
54.9%
41.0%
36.2%
45.8%
38.6%
3.1%
Note: The NodeId column only appears in the ResVdskByNode output report.
ResVdskOneNode Sample Output
06/09/26
VDISK Traffic for Node 001-01
Date
-------06/09/26
Time
-------10:09:45
10:10:00
10:10:15
10:10:30
10:10:45
10:11:00
10:11:15
10:11:30
10:11:45
10:12:00
10:12:15
10:12:30
10:12:45
ReadCnt
/ Sec
--------0.73
0.40
0.00
2.43
2.77
2.67
2.83
4.87
5.37
5.43
3.20
0.50
0.00
WriteCnt Rd KB
/ Sec
/ I/O
-------- ------5.20
121.27
41.17
127.50
47.40
?
45.17
111.79
45.90
12.00
43.77
12.00
46.10
12.00
14.13 1374.25
1.77 1785.00
0.30 1785.00
9.70 1759.00
12.60
275.47
2.17
?
Page
Wrt KB
/ I/O
------46.69
116.34
118.98
113.54
109.93
112.07
112.32
100.01
38.15
71.56
16.76
18.84
32.94
Avg
I/O
Resp
------0.023
0.152
0.143
0.126
0.118
0.119
0.107
0.081
0.065
0.064
0.039
0.038
0.017
1
Out
Rqst
Time %
-----9.7%
85.3%
98.8%
98.4%
97.7%
98.0%
97.3%
54.9%
41.0%
36.2%
45.8%
38.6%
3.1%
ResVdskByGroup Sample Output
06/09/26
VDISK TRAFFIC BY GROUP
Node
Date
Type
Time
-------- ---- -------06/09/26 4400 10:09:45
10:10:00
10:10:15
10:10:30
10:10:45
10:11:00
10:11:15
10:11:30
Resource Usage Macros and Tables
ReadCnt
/ Sec
-------0.73
0.40
0.00
2.43
2.77
2.67
2.83
4.87
WriteCnt Rd KB
/ Sec
/ I/O
-------- ------5.20
121.27
41.17
127.50
47.40
?
45.17
111.79
45.90
12.00
43.77
12.00
46.10
12.00
14.13 1374.25
Wrt KB
/ I/O
------46.69
116.34
118.98
113.54
109.93
112.07
112.32
100.01
Page
1
Avg
Max
Out
I/O
Concur
Rqst
Resp
Rqsts Time %
------- ------ -----0.023
4.5
9.7%
0.152
20.5
85.3%
0.143
20.0
98.8%
0.126
17.5
98.4%
0.118
13.5
97.7%
0.119
14.5
98.0%
0.107
14.0
97.3%
0.081
12.5
54.9%
219
Chapter 15: Resource Usage Macros
ResVdskByNode Macros
10:11:45
10:12:00
10:12:15
10:12:30
10:12:45
5.37
5.43
3.20
0.50
0.00
1.77
0.30
9.70
12.60
2.17
1785.00
1785.00
1759.00
275.47
?
38.15
71.56
16.76
18.84
32.94
0.065
0.064
0.039
0.038
0.017
3.0
2.0
2.0
3.5
2.0
41.0%
36.2%
45.8%
38.6%
3.1%
Note: The NodeType column only appears in the ResVdskByGroup output report.
220
Resource Usage Macros and Tables
APPENDIX A
How to Read Syntax Diagrams
This appendix describes the conventions that apply to reading the syntax diagrams used in
this book.
Syntax Diagram Conventions
Notation Conventions
Item
Definition / Comments
Letter
An uppercase or lowercase alphabetic character ranging from A through Z.
Number
A digit ranging from 0 through 9.
Do not use commas when typing a number with more than 3 digits.
Word
Keywords and variables.
• UPPERCASE LETTERS represent a keyword.
Syntax diagrams show all keywords in uppercase, unless operating system
restrictions require them to be in lowercase.
• lowercase letters represent a keyword that you must type in lowercase, such as a
Linux command.
• lowercase italic letters represent a variable such as a column or table name.
Substitute the variable with a proper value.
• lowercase bold letters represent an excerpt from the diagram. The excerpt is
defined immediately following the diagram that contains it.
• UNDERLINED LETTERS represent the default value.
This applies to both uppercase and lowercase words.
Spaces
Use one space between items such as keywords or variables.
Punctuation
Type all punctuation exactly as it appears in the diagram.
Paths
The main path along the syntax diagram begins at the left with a keyword, and proceeds, left
to right, to the vertical bar, which marks the end of the diagram. Paths that do not have an
arrow or a vertical bar only show portions of the syntax.
The only part of a path that reads from right to left is a loop.
Resource Usage Macros and Tables
221
Appendix A: How to Read Syntax Diagrams
Syntax Diagram Conventions
Continuation Links
Paths that are too long for one line use continuation links. Continuation links are circled
letters indicating the beginning and end of a link:
A
A
FE0CA002
When you see a circled letter in a syntax diagram, go to the corresponding circled letter and
continue reading.
Required Entries
Required entries appear on the main path:
SHOW
FE0CA003
If you can choose from more than one entry, the choices appear vertically, in a stack. The first
entry appears on the main path:
SHOW
CONTROLS
VERSIONS
FE0CA005
Optional Entries
You may choose to include or disregard optional entries. Optional entries appear below the
main path:
SHOW
CONTROLS
222
FE0CA004
Resource Usage Macros and Tables
Appendix A: How to Read Syntax Diagrams
Syntax Diagram Conventions
If you can optionally choose from more than one entry, all the choices appear below the main
path:
READ
SHARE
ACCESS
JC01A010
Some commands and statements treat one of the optional choices as a default value. This
value is UNDERLINED. It is presumed to be selected if you type the command or statement
without specifying one of the options.
Strings
String literals appear in apostrophes:
'msgtext '
JC01A004
Abbreviations
If a keyword or a reserved word has a valid abbreviation, the unabbreviated form always
appears on the main path. The shortest valid abbreviation appears beneath.
SHOW
CONTROLS
CONTROL
FE0CA042
In the above syntax, the following formats are valid:
•
SHOW CONTROLS
•
SHOW CONTROL
Loops
A loop is an entry or a group of entries that you can repeat one or more times. Syntax
diagrams show loops as a return path above the main path, over the item or items that you can
repeat:
,
,
(
cname
3
4
)
JC01B012
Resource Usage Macros and Tables
223
Appendix A: How to Read Syntax Diagrams
Syntax Diagram Conventions
Read loops from right to left.
The following conventions apply to loops:
IF...
THEN...
there is a maximum number of
entries allowed
the number appears in a circle on the return path.
there is a minimum number of
entries required
the number appears in a square on the return path.
a separator character is required
between entries
the character appears on the return path.
In the example, you may type cname a maximum of 4 times.
In the example, you must type at least three groups of column
names.
If the diagram does not show a separator character, use one
blank space.
In the example, the separator character is a comma.
a delimiter character is required
around entries
the beginning and end characters appear outside the return
path.
Generally, a space is not needed between delimiter characters
and entries.
In the example, the delimiter characters are the left and right
parentheses.
Excerpts
Sometimes a piece of a syntax phrase is too large to fit into the diagram. Such a phrase is
indicated by a break in the path, marked by (|) terminators on each side of the break. The
name for the excerpted piece appears between the terminators in boldface type.
The boldface excerpt name and the excerpted phrase appears immediately after the main
diagram. The excerpted phrase starts and ends with a plain horizontal line:
LOCKING
excerpt
A
A
HAVING
con
excerpt
where_cond
,
cname
,
col_pos
JC01A014
224
Resource Usage Macros and Tables
Appendix A: How to Read Syntax Diagrams
Syntax Diagram Conventions
Multiple Legitimate Phrases
In a syntax diagram, it is possible for any number of phrases to be legitimate:
dbname
DATABASE
tname
TABLE
vname
VIEW
JC01A016
In this example, any of the following phrases are legitimate:
•
dbname
•
DATABASE dbname
•
tname
•
TABLE tname
•
vname
•
VIEW vname
Sample Syntax Diagram
,
viewname
CREATE VIEW
AS
cname
CV
A
LOCKING
LOCK
ACCESS
dbname
A
DATABASE
tname
FOR
SHARE
IN
READ
TABLE
WRITE
EXCLUSIVE
vname
VIEW
EXCL
,
B
SEL
B
MODE
expr
,
FROM
tname
qual_cond
C
.aname
C
HAVING cond
;
qual_cond
,
WHERE cond
GROUP BY
cname
,
col_pos
JC01A018
Resource Usage Macros and Tables
225
Appendix A: How to Read Syntax Diagrams
Syntax Diagram Conventions
Diagram Identifier
The alphanumeric string that appears in the lower right corner of every diagram is an internal
identifier used to catalog the diagram. The text never refers to this string.
226
Resource Usage Macros and Tables
APPENDIX B
ResUsageIpma Table
The ResUsageIpma table includes resource usage data for system-wide, node information.
Note: Summary Mode is not applicable to this table.
This table is created as a MULTISET table. For more information see “Relational Primary
Index” on page 38.
The following table describes the ResUsageIpma table columns.
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY KEY COLUMNS
These columns taken together form the nonunique primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system load,
entries may be logged late (typically, by no
more than one or two seconds), but this field
will still contain the time value when the entry
should have been logged. See the Secs and
NominalSecs columns.
NodeId
n/a
Identifies the Node. The Node ID is formatted
as CCC-MM, where CCC denotes the threedigit cabinet number and MM denotes the
two-digit chassis number of the node. For
example, a node in chassis 9 of cabinet 3 has a
node ID of ‘003-09’.
INTEGER
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an
SMP node is ‘001-01’.
MISCELLANEOUS HOUSEKEEPING COLUMNS
These columns provide a generalized picture of the vprocs running on this node, shown as Type n virtual processors where
n = 1 to 7. Under the current implementation, only Type 1 (AMP), Type 2 (PE), Type 3 (GTW), Type 4 (RSG), and Type 5
(VSS) vprocs exist; vproc types 6 through 7 are not currently used.
GmtTime
n/a
Resource Usage Macros and Tables
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that occur
twice a year.
FLOAT
227
Appendix B: ResUsageIpma Table
Column Name
Type of
Data
NodeType
NCPUs
Description
Data Type
n/a
Type of node, representing the per node
system family type. For example, 5600C or
5555H.
CHAR(8)
n/a
Number of CPUs on this node.
SMALLINT
Invalid
Platform
This field is useful for normalizing the CPU
utilization field values for the number of
CPUs on the node. This is especially
important in coexistence systems where the
number of CPUs can vary across system
nodes.
Vproc1
n/a
Current count of type 1 (AMP) virtual
processors running under the node.
SMALLINT
VprocType1
n/a
Type of virtual processor for Vproc1. Value is
always AMP.
CHAR(4)
Vproc2
n/a
Current count of type 2 (PE) virtual
processors running under the node.
SMALLINT
VprocType2
n/a
Type of virtual processor for Vproc2. Value is
always PE.
CHAR(4)
Vproc3
n/a
Current count of type 3 (GTW) virtual
processors running under the node.
SMALLINT
VprocType3
n/a
Type of virtual processor for Vproc3. Value is
always GTW.
CHAR(4)
Vproc4
n/a
Current count of type 4 (RSG) virtual
processors running under the node.
SMALLINT
VprocType4
n/a
Type of virtual processor for Vproc4. Value is
always RSG.
CHAR(4)
Vproc5
n/a
Current count of type 5 (VSS) virtual
processors running under the node.
SMALLINT
VprocType5
n/a
Type of virtual processor for Vproc5. The
value is always TVS (see Teradata Virtual
Storage).
CHAR(4)
Vproc6
n/a
Current count of type 6 virtual processors
running under the node.
SMALLINT
This column reports zeros and " " (blanks).
VprocType6
n/a
Type of virtual processor for Vproc6.
CHAR(4)
Vproc7
n/a
Current count of type 7 virtual processors
running under the node.
SMALLINT
ALL
This column reports zeros and " " (blanks).
VprocType7
228
n/a
Type of virtual processor for Vproc7.
CHAR(4)
ALL
Resource Usage Macros and Tables
Appendix B: ResUsageIpma Table
Column Name
Type of
Data
MemSize
NodeNormFactor
Description
Data Type
n/a
Amount of memory on this node in
megabytes. Useful for performing memory
usage calculations.
INTEGER
n/a
A per node normalization factor that is used
to normalize the reported CPU values of the
ResUsageSpma table.
INTEGER
Invalid
Platform
This value is scaled by a factor of 100. For
example, if the actual factor is 5.25, then the
value of the NodeNormFactor will be 525.
Note: The normalization factor is related to
the NodeType value reported in the
ResUsageSpma table.
For information on this value, see Chapter 6:
“ResUsageSpma Table.”
Secs
n/a
Actual number of seconds in the log period
represented by this row. Normally the same as
NominalSecs, but can be different in three
cases:
INTEGER
• The first interval after a log rate change
• A sample logged late because of load on the
system
• System clock adjustments affect reported
Secs
Useful for normalizing the count statistics
contained in this row, for example, to a persecond measurement.
CentiSecs
n/a
Number of centiseconds in the logging
period. This field is useful when performing
data calculations with small elapsed times
where the difference between centisecondbased data and whole seconds results in a
percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds in
the logging period.
SMALLINT
Resource Usage Macros and Tables
229
Appendix B: ResUsageIpma Table
Column Name
Type of
Data
Active
count
Description
Data Type
Controls whether or not the rows will be
logged to the ResUsage tables if Active Row
Filter Mode is enabled.
FLOAT
Invalid
Platform
If Active is set to:
• a non-zero value, then the row contains
modified data columns.
• a zero value, then none of the data
columns in the row have been updated
during the logging period.
For example, if Active Row Filter Mode is
enabled, then the rows that have a zero Active
field value will not be logged to the ResUsage
tables.
CollectIntervals
n/a
The number of gather periods per reporting
period.
SMALLINT
In the Collect Buffer and Log Buffer, the value
is the number of Gather operations that have
been performed during the period. This
number can vary from one period to the next.
STATISTICS COLUMNS
PROCESS SCHEDULING COLUMNS
Scheduled CPU Switching Columns
Identify the number of times CPUs were switched by the scheduler from one type of work to another type of work.
CPUProcSwitches
count
Number of times the scheduler switched a
CPU’s currently active process to a new
process.
FLOAT
Windows
CPUProcSameSwitches
count
Number of CPUProcSwitches where a process
replaced itself, that is, the new process was the
same as the old process. This field is a subset
of CPUProcSwitches.
FLOAT
ALL
Interrupted CPU Switching Columns
Identify the number of times an interrupt was issued for the node and/or its CPUs.
ProcNetInts
count
Number of times the node was interrupted for
Teradata a net request.
FLOAT
ALL
IOPtoCPUInts
count
Number of times a CPU was interrupted by
the IOP.
FLOAT
ALL
ProcDiskInts
count
Number of times the node was interrupted to
handle a disk request.
FLOAT
ALL
ProcHostInts
count
Number of times the node was interrupted to
handle a host request.
FLOAT
ALL
230
Resource Usage Macros and Tables
Appendix B: ResUsageIpma Table
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
ProcLanInts
count
Number of times the node was interrupted to
handle a LAN request.
FLOAT
ALL
ProcGenClockInts
count
The number of timer interrupts.
FLOAT
Windows
ProcCPUClockInts
count
Number of times a CPU was interrupted to
service a CPU specific clock event.
FLOAT
ALL
ProcInterCPUInts
count
Number of times the a CPU was interrupted
to service an inter-CPU request.
FLOAT
ALL
MEMORY COLUMNS
Memory Page Deallocation Columns
Represent the number of memory page deallocations specific to generic node activities, subdivided into memory types.
• The amount deallocated can be derived by multiplying the number of deallocations by the fixed page size.
• These columns do not include any memory deallocated specific to a vproc running under the node.
MemTextDestroys
count
Number of memory deallocations and sizedecreasing memory alters for non-system
overhead text (code).
FLOAT
ALL
NET COLUMNS
Message Type Columns
Subdivide all messages sent and received into the type of message, where:
•
•
•
•
•
Hash messages (Hash) are data sent to a destination through its primary or fallback hash value
Processor messages (Proc) are data sent to a destination through a vproc ID
Group messages (Group) are broadcasted messages to be received by members of a group
Local messages (Local) are messages communicated locally within the node
Channel messages (Chan) are data sent between vprocs through channel IDs for purposes of a private conversation to
perform functions such as row redistribution, and so on
• Mailbox messages (Mbox) are data sent between vprocs through mailbox IDs for similar purposes as channel messages.
A duplicated accounting is done with two different perspectives, since Hash + Proc + Group + Local messages = Chan +
MBox messages.
MsgHashReads
count
Number of hash messages read by this node.
FLOAT
MsgHashWrites
count
Number of hash messages written by this
node.
FLOAT
MsgProcReads
count
Number of processor messages read by this
node.
FLOAT
MsgProcWrites
count
Number of processor messages written by the
node.
FLOAT
MsgGroupReads
count
Number of group messages read by this node.
FLOAT
MsgGroupWrites
count
Number of group messages written by this
node.
FLOAT
Resource Usage Macros and Tables
231
Appendix B: ResUsageIpma Table
Column Name
Type of
Data
Description
Data Type
MsgLocalReads
count
Number of local messages read by this node.
FLOAT
MsgLocalWrites
count
Number of local messages written by this
node.
FLOAT
MsgChanReads
count
Number of channel messages read by this
node.
FLOAT
MsgChanWrites
count
Number of channel messages written by this
node.
FLOAT
MsgMboxReads
count
Number of mailbox messages read by this
node.
FLOAT
MsgMboxWrites
count
Number of mailbox messages written by this
node.
FLOAT
Invalid
Platform
Message Delivery Time Columns
Identify the time it took for hash, processor, group and local messages to reach their destination. Two times are provided:
• Message transmission to mailbox delivery (MDelivery)
• Mailbox delivery to process delivery (PDelivery)
MsgHashMDelivery
count
Total amount of time read hash messages took
for mailbox delivery.
FLOAT
MsgProcMDelivery
count
Total amount of time read processor messages
took for mailbox delivery.
FLOAT
MsgGroupMDelivery
count
Total amount of time read group messages
took for mailbox delivery.
FLOAT
MsgLocalMDelivery
count
Total amount of time read local messages took
for mailbox delivery.
FLOAT
MsgHashPDelivery
count
Total amount of time read hash messages took
for process delivery.
FLOAT
MsgProcPDelivery
count
Total amount of time read processor messages
took for process delivery.
FLOAT
MsgGroupPDelivery
count
Total amount of time read group messages
took for process delivery.
FLOAT
MsgLocalPDelivery
count
Total amount of time read local messages took
for process delivery.
FLOAT
Net Circuit Management Columns
Identify the management of Teradata net circuits (Circ) and raw data traffic on the network (hardware) on all networks.
Note: All of these columns except for NetBackoffs are net-specific. On a single-node system, net-specific statistics are not
meaningful and are always zero.
NetBackoffs
232
count
Software backoffs, defined as BNS service
blocked occurrences without regard for which
net was involved.
FLOAT
Resource Usage Macros and Tables
Appendix B: ResUsageIpma Table
Column Name
Type of
Data
NetTxCircPtp
Description
Data Type
count
Total number (both normal and high
priority) of point-to-point circuits
transmitted on all Bynets.
FLOAT
NetTxCircBrd
count
Total number (both normal and high
priority) of broadcast circuits transmitted on
all Bynets.
FLOAT
NetTxCircHPPtP
count
Number of high priority point-to-point
circuits transmitted on all Bynets.
FLOAT
NetTxCircHPBrd
count
Number of high priority broadcast circuits
transmitted on all Bynets.
FLOAT
NetRxCircPtp
count
Total number (both normal and high
priority) of point-to-point circuits received
on all Bynets.
FLOAT
NetRxCircBrd
count
Total number (both normal and high
priority) of broadcast circuits received on all
Bynets.
FLOAT
Invalid
Platform
Bynet Network Transport Data Columns
NetTxKBPtP
count
Total point-to-point data KBs transmitted
over all Bynets.
FLOAT
NetTxKBBrd
count
Total broadcast data KBs transmitted over all
Bynets
FLOAT
NetRxKBPtP
count
Total point-to-point data KBs received over all
Bynets.
FLOAT
NetRxKBBrd
count
Total broadcast data KBs received over all
Bynets.
FLOAT
Net Miscellaneous Contention Management Columns
Identify some additional contention management not addressed in the other contention management areas.
Note: NetBrdWindowOverrun is net-specific, that is, it relates to each specific Bynet. On a single-node system, net-specific
statistics are not meaningful and are always zero.
NetMsgFCSleep
count
Number of times a transmitter process was
put to sleep because it was flow controlled.
FLOAT
NetMsgFCBlock
count
Number of times the net software was blocked
because the receiver was flow controlled.
FLOAT
NetMsgResourceBlock
count
Number of times the net software was blocked
because the receiver could not get the
necessary resources.
FLOAT
NetMsgChannelBlock
count
Number of times the net software was blocked
because the channel was not in RxReady state
on the receiver.
FLOAT
Resource Usage Macros and Tables
233
Appendix B: ResUsageIpma Table
Column Name
Type of
Data
NetMsgGroupBlock
Invalid
Platform
Description
Data Type
count
Number of times the net software was blocked
because the receiver could not implicitly enter
the group.
FLOAT
NetMsgRxBlock
count
Number of times the net software could not
accept a message and caused a transmitter to
block.
FLOAT
NetMrgBlock
count
Number of times a merge message was
blocked until delivery of outstanding
outgoing messages.
FLOAT
NetBrdWindowOverrun
count
Broadcast window overruns on all Bynets.
FLOAT
NetActiveMrg
count
The number of concurrent active merges on
all Bynets.
FLOAT
NetMrgBufWaits
count
Number of times an IOP task encountered an
empty row-block buffer on all Bynets.
FLOAT
NetBackoffExhausted
count
Number of transmit circuits that were backedoff too many times and had to be converted to
blocking circuits.
FLOAT
ALL
NetBrdWindowError
count
Number of broadcast window errors.
FLOAT
ALL
NetConfigurations
count
Number of network configurations and reconfigurations.
FLOAT
ALL
NetProtocolFilter
count
Number of protocol filters executed.
FLOAT
ALL
NetTxSoftBackoffs
count
Number of soft backoffs transmitted on all
Bynets.
FLOAT
ALL
NetRxSoftBackoffs
count
Number of soft backoffs received on all
Bynets.
FLOAT
ALL
Net Queues Columns
Identify lengths of the various internal queues used by the network controllers.
• NetSamples can be used to normalize all aggregated sampled statistics to an average queue-length basis.
• Example: Dividing (NetPtPQueue/NetSamples) yields the average point-to-point queue length over all samples on all
networks taken during this log interval.
• All of the aggregated sampled statistics columns in the following table are net-specific, that is, they relate to each specific
Bynet. On a single-node system, net-specific statistics are not meaningful and are always zero.
NetPtPQueue
count
Aggregated sample point-to-point normal
priority queue length on all Bynets.
FLOAT
NetPtPQueueMax
max
The maximum value of NetPtPQueue over all
gather intervals in this reporting interval.
FLOAT
NetBrdQueue
count
Aggregated sample broadcast normal priority
queue length on all Bynets.
FLOAT
234
Resource Usage Macros and Tables
Appendix B: ResUsageIpma Table
Column Name
Type of
Data
NetBrdQueueMax
Description
Data Type
max
The maximum value of NetBrdQueue over all
gather intervals in this reporting interval.
FLOAT
NetHPPtPQueue
count
Aggregated sample point-to point high
priority queue length on all Bynets.
FLOAT
NetHPPtPQueueMax
max
The maximum value of NetHPPtPQueue over
all gather intervals in this reporting interval.
FLOAT
NetHPBrdQueue
count
Aggregated sample broadcast high priority
queue length on all networks.
FLOAT
NetHPBrdQueueMax
max
The maximum value of NetHPBrdQueue over
all gather intervals in this reporting interval.
FLOAT
NetBlockQueueSum
count
Total number of services on the
BlockableService queue, regardless of which
net during each log interval. Services can be
blocked for a variety of reasons including
receiver flow control, receiver resource usage,
and daemon services.
FLOAT
NetBlockQueueTotal
count
Total number of services on the
BlockableServices queue.
FLOAT
NetBlockQueueMax
max
Maximum number of services on the
BlockableServices queue in this log interval.
FLOAT
NetPendMrgQueue
count
The current count of pending merges,
regardless of which net. A merge may be
queued for reasons such as:
FLOAT
Invalid
Platform
• the local IOP memory is saturated
• system memory is trashing.
GENERAL CONCURRENCY CONTROL COLUMNS
Operating System Lock Management Columns
Identify database locking activities for internal multiprocessing operating system concurrency control.
LockEnters
count
Number of times entry into a lockable
resource was requested.
FLOAT
ALL
LockBlocks
count
Number of times entry into a lockable
resource was blocked, requiring the requestor
to spin until the resource is unblocked.
(requests - blocks = immediate grants.)
FLOAT
ALL
FLOAT
ALL
Secondary Cache Misses Columns
Identify the percentage of time accesses were not in the cache.
CacheAccess
count
Resource Usage Macros and Tables
Total number of accesses.
235
Appendix B: ResUsageIpma Table
Spare Columns
Column Name
Type of
Data
Description
Data Type
Invalid
Platform
CacheMiss
count
Number of times accesses were not in the
cache.
FLOAT
ALL
CacheWrites
count
Total number of writes to the cache.
FLOAT
ALL
CacheWriteThrus
count
Number of cache write through accesses
(write bypasses the cache and goes straight to
main memory).
FLOAT
ALL
CacheWriteBacks
count
Number of cache write back accesses from
cache to main memory, that is, delayed writes
of data previously written to the cache by the
CPU.
FLOAT
ALL
Spare Columns
The ResUsageIpma table has nine spare columns (one of which is being used) as shown in the
table below.
Column Name
Type of Data
Description
SpareCount[00-02]
count
Spare counted statistic.
SpareTrack[00-02]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 field contains the COD
value. The value represents the COD value in
one tenths of a percent, so a displayed value of
500 represents a COD value of 50.0%.
Note: This value is valid only on SUSE Linux
Enterprise Server 10 systems and is a single
value for the entire system.
SpareTmon[01-02]
count
Spare time monitored statistic.
The spare column fields expand to values 00 - 02, so that column names would be
SpareCount01, SpareCount02, SpareTrack01, and so on.
236
Resource Usage Macros and Tables
APPENDIX C
ResUsageIvpr Table
The ResUsageIvpr table includes resource usage data for system-wide, virtual processor
information. This table is intended for internal use only.
The following table describes the ResUsageIvpr table columns.
Column Name
Type of Data
Description
Data Type
Invalid
Platform
HOUSEKEEPING COLUMNS
RELATIONAL PRIMARY INDEX COLUMNS
These columns taken together form the primary index.
TheDate
n/a
Date of the log entry.
DATE
TheTime
n/a
Nominal time of the log entry.
FLOAT
Note: Under conditions of heavy system load,
entries may be logged late (typically, by no more
than one or two seconds), but this field will still
contain the time value when the entry should
have been logged. See the Secs and NominalSecs
columns.
NodeId
n/a
Identifies the Node upon which the vproc
resides. The Node ID is formatted as CCC-MM,
where CCC denotes the three-digit cabinet
number and MM denotes the two-digit chassis
number of the node. For example, a node in
chassis 9 of cabinet 3 has a node ID of ‘003-09’.
INTEGER
Note: SMP nodes have a chassis and cabinet
number of 1. For example, the node ID of an
SMP node is ‘001-01’.
MISCELLANEOUS HOUSEKEEPING COLUMNS
GmtTime
n/a
Greenwich Mean Time is not affected by the
Daylight Savings Time adjustments that occur
twice a year.
FLOAT
NodeType
n/a
Type of node, representing the per node system
family type. For example, 5600C or 5555H.
CHAR(8)
Resource Usage Macros and Tables
237
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
VprId
n/a
Identifies the vproc number (non-Summary
Mode) or the vproc type (Summary Mode;
0 = NODE, 1 = AMP, 2 = PE, 3=GTW, 4=RSG,
5=VSS).
INTEGER
Invalid
Platform
The VprId can be any of the following
depending on the type:
• AMP vprocs: numbered upward from 0.
• PE vprocs: numbered downward from
16383.
• NODE vprocs: numbered upward from
16384.
• GTW vprocs: numbered upward from 8192.
• RSG vprocs: numbered downward from
9215.
• VSS vprocs: numbered downward from
10238.
The vproc numbers within each type range are
contiguous. Each existing vproc type range
should not overlap into the range of another
existing vproc type on the system.
VprType
n/a
The values can be NODE, AMP, PE, GTW, RSG,
or TVS (see Teradata Virtual Storage).
CHAR(4)
Secs
n/a
Actual number of seconds in the log period
represented by this row. Normally the same as
NominalSecs, but can be different in three cases:
SMALLINT
• The first interval after a log rate change
• A sample logged late because of load on the
system
• System clock adjustments affect reported
Secs
Useful for normalizing the count statistics
contained in this row, for example, to a persecond measurement.
CentiSecs
n/a
Number of centiseconds in the logging period.
This field is useful when performing data
calculations with small elapsed times where the
difference between centisecond-based data and
whole seconds results in a percentage error.
INTEGER
NominalSecs
n/a
A specified or nominal number of seconds in
the logging period.
SMALLINT
SummaryFlag
n/a
Identifies the summarization status of this row.
Possible values are 'N' if the row is a nonsummary row, and 'S' if the row is a summary
row.
CHAR
238
Resource Usage Macros and Tables
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
NCPUs
n/a
Number of CPUs on this node.
SMALLINT
Invalid
Platform
This field is useful for normalizing the CPU
utilization field values for the number of CPUs
on the node. This is especially important in
coexistence systems where the number of CPUs
can vary across system nodes.
Active
count
Controls whether or not the rows will be logged
to the ResUsage tables if Active Row Filter Mode
is enabled.
FLOAT
If Active is set to:
• a non-zero value, then the row contains
modified data fields.
• a zero value, then none of the data fields in
the row have been updated during the
logging period.
For example, if Active Row Filter Mode is
enabled, then the rows that have a zero Active
field value will not be logged to the ResUsage
tables.
CollectIntervals
n/a
The number of gather periods per reporting
period.
SMALLINT
In the Collect Buffer and Log Buffer, the value is
the number of Gather operations that have been
performed during the period. This number can
vary from one period to the next.
STATISTICS COLUMNS
PROCESS SCHEDULING COLUMNS
Work Type Summary Columns
Identify the distribution of work types among allocated processes. The total of the following average columns approximately
equals total Process Allocations in ResUsageSpma table. Each entry below represents 16 columns, where [i] expands to the
values 0-15, for example, ProcWorkType2Sum.
ProcWorkType[i]Sum
count
Total number of processes of work type i during
each log interval.
FLOAT
ALL
FLOAT
ALL
Note: To calculate the average number of
processes, divide this value by the
CollectIntervals value. The CollectIntervals
value is the number of gather periods per
reporting period. For more information, see the
CollectIntervals column.
ProcWorkType[i]Max
max
Resource Usage Macros and Tables
Maximum number of processes of work type i
during each log interval.
239
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
Invalid
Platform
NET COLUMNS
Message Type Columns
Subdivide all messages sent and received into the type of message, where:
•
•
•
•
•
hash messages (Hash) are data sent to a destination through its primary or fallback hash value
processor messages (Proc) are data sent to a destination through a vproc ID
group messages (Group) are broadcasted messages to be received by members of a group
local messages (Local) are messages communicated locally within the node
channel messages (Chan) are data sent between vprocs through channel IDs for purposes of a private conversation to
perform functions such as row redistribution, and so on.
• mailbox messages (Mbox) are data sent between vprocs through mailbox IDs for similar purposes as channel messages.
A duplicated accounting is done with two different perspectives, since Hash + Proc + Group + Local messages = Chan +
MBox messages.
MsgHashReads
count
Number of hash messages read by this vproc.
FLOAT
MsgHashWrites
count
Number of hash messages written by this vproc.
FLOAT
MsgProcReads
count
Number of processor messages read by this
vproc.
FLOAT
MsgProcWrites
count
Number of processor messages written by this
vproc.
FLOAT
MsgGroupReads
count
Number of group messages read by this vproc.
FLOAT
MsgGroupWrites
count
Number of group messages written by this
vproc.
FLOAT
MsgLocalReads
count
Number of local messages read by this vproc.
FLOAT
MsgLocalWrites
count
Number of local messages written by this vproc.
FLOAT
MsgChanReads
count
Number of channel messages read by this vproc.
FLOAT
MsgChanWrites
count
Number of channel messages written by this
vproc.
FLOAT
MsgMboxReads
count
Number of mailbox messages read by this
vproc.
FLOAT
MsgMboxWrites
count
Number of mailbox messages written by this
vproc.
FLOAT
Message Delivery Times Columns
Identify the time it took for hash, processor, group and local messages to reach their destination. Two times are provided:
message transmission to mailbox delivery (MDelivery) and mailbox delivery to process delivery (PDelivery).
MsgHashMDelivery
240
count
Total amount of time read hash messages took
for mailbox delivery.
FLOAT
Resource Usage Macros and Tables
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
MsgProcMDelivery
count
Total amount of time read processor messages
took for mailbox delivery.
FLOAT
MsgGroupMDelivery
count
Total amount of time read group messages took
for mailbox delivery.
FLOAT
MsgLocalMDelivery
count
Total amount of time read local messages took
for mailbox delivery.
FLOAT
MsgHashPDelivery
count
Total amount of time read hash messages took
for process delivery.
FLOAT
MsgProcPDelivery
count
Total amount of time read processor messages
took for process delivery.
FLOAT
MsgGroupPDelivery
count
Total amount of time read group messages took
for process delivery.
FLOAT
MsgLocalPDelivery
count
Total amount of time read local messages took
for process delivery.
FLOAT
Invalid
Platform
GENERAL CONCURRENCY CONTROL COLUMNS
Monitor Management Columns
Identify monitor activities for Teradata Database concurrency control.
MonAllocates
count
Number of monitors allocated.
FLOAT
MonEnters
count
Number of times entry into a monitor was
requested.
FLOAT
MonBlocks
count
Number of times entry into a monitor was
blocked. (requests - blocks = immediate grants.)
FLOAT
MonDeadlocks
count
Number of times entry into a monitor was
deadlocked.
FLOAT
MonYields
count
Number of times a monitor yield was requested.
FLOAT
ALL
FILE SYSTEM COLUMNS
Cylinder Overhead Columns
Further identify file system cylinder split/migrate (CylMigr) overhead performed when cylinders can not accommodate new
data. (Event counts are found in ResUsageSvpr.) Only logical I/Os and the amount moved (KBs) for data blocks are
identified. Each cylinder migration event implies 1 logical read and 3 logical writes of the cylinder index. Only permanent
tables (including append and transient journal tables) are migrated.
FileDbCylMigrIO
count
Number of data block logical I/Os due to
cylinder migration.
FLOAT
FileDbCylMigrKB
count
KBs moved by FileDbCylMigrIOs.
FLOAT
Resource Usage Macros and Tables
241
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
Invalid
Platform
Cylinder MiniCylPack Overhead Columns
Identify file system overhead associated with MiniCylPacks (MCylPack) that get performed to make available a free cylinder
when one is needed but not available.
• Event counts are found in ResUsageSvpr.
• Only logical I/Os and the amount moved (KBs) are identified, except the amount moved for cylinder indexes because
they can be calculated by multiplying the current cylinder index fixed size and the I/Os.
• MiniCylPacks are done on cylinders containing permanent tables (including append and transient journal tables) only.
FilePCiMCylPackIO
count
Number of permanent cylinder index logical
I/Os due to performing MiniCylPack
operations.
FLOAT
FilePDbMCylPackIO
count
Number of permanent data block logical I/Os
due to performing MiniCylPack operations.
FLOAT
FilePDbMCylPackKB
count
KBs moved by FilePDbCylPackIOs.
FLOAT
Cylinder Defragmentation Overhead Columns
Identify background file system overhead associated with fragmented free space to achieve one large free space within that
cylinder (CylDefrag).
• Event counts are found in ResUsageSvpr.
• Each cylinder defragment event implies 1 logical cylinder index read and 1 logical cylinder index write.
• Only logical I/Os and the amount moved (KBs) are identified. Cylinder defragments are done on cylinders containing
permanent tables (including append and transient journal tables) only.
FileDbCylDefragIO
count
Number of permanent data block logical I/Os
due to cylinder defragmentation.
FLOAT
FileDbCylDefragKB
count
KBs moved by the FileDbCylDefragIO.
FLOAT
Data Block Update Operations Columns
Identify the file system operations required when a data block is being updated (BlkUpd). When a block is updated, it can be
‘in place’ and requires no new data blocks, or it could spill over the current data block and require 1, 2, 3 or more new data
blocks in addition to the current data block. Only logical I/Os and the amount moved (KBs) are identified, except for the
amount moved for cylinder indexes because they can be calculated by multiplying the current fixed cylinder index size by
the I/Os. Data block updates should only be performed on permanent tables (including append and transient journal
tables), so no attempt is made to separate permanent and spool data segments.
FileCiUpd0IO
count
Number of cylinder index logical I/Os
performed for a block update operation
requiring no new data blocks.
FLOAT
FileDbUpd0IO
count
Number of data block logical I/Os performed
for a block update operation requiring no new
data blocks.
FLOAT
FileDbUpd0KB
count
KBs moved by FileDbUpd0IO.
FLOAT
FileCiUpd1IO
count
Number of cylinder index logical I/Os
performed for a block update operation
requiring 1 new data blocks.
FLOAT
242
Resource Usage Macros and Tables
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
FileDbUpd1IO
count
Number of data block logical I/Os performed
for a block update operation requiring 1 new
data blocks.
FLOAT
FileDbUpd1KB
count
KBs moved by FileDbUpd1IO.
FLOAT
FileCiUpd2IO
count
Number of cylinder index logical I/Os
performed for a block update operation
requiring 2 new data blocks.
FLOAT
FileDbUpd2IO
count
Number of data block logical I/Os performed
for a block update operation requiring 2 new
data blocks.
FLOAT
FileDbUpd2KB
count
KBs moved by FileDbUpd2IO.
FLOAT
FileCiUpd3IO
count
Number of cylinder index logical I/Os
performed for a block update operation
requiring 3 new data blocks.
FLOAT
FileDbUpd3IO
count
Number of data block logical I/Os performed
for a block update operation requiring 3 new
data blocks.
FLOAT
FileDbUpd3KB
count
KBs moved by FileDbUpd3IO.
FLOAT
FileCiUpdNIO
count
Number of cylinder index logical I/Os
performed for a block update operation
requiring over 3 new data blocks.
FLOAT
FileDbUpdNIO
count
Number of data block logical I/Os performed
for a block update operation requiring over 3
new data blocks.
FLOAT
FileDbUpdNKB
count
KBs moved by FileDbUpdNIO.
FLOAT
Invalid
Platform
Data Block Creations Columns
Identify the file system operations required when a data block is being created (BlkCreate). It does not include data blocks
created due to any of the new data blocks created when a data block was updated as described in the Data Block Update
Operations Columns description.
FilePDbCreates
count
Number of permanent table (including append
and transient journal tables) data blocks
created.
FLOAT
FilePDbCreateKB
count
KBs created by FilePDbCreates.
FLOAT
FileSDbCreates
count
Number of spool data blocks created.
FLOAT
FileSDbCreateKB
count
KBs created by FileSDbCreates.
FLOAT
Transient Journal Overhead Columns
Identify file system overhead associated with maintaining a transient journal (TJ).
FileTJBufUpdates
count
Resource Usage Macros and Tables
Number of transient journal buffer updates.
FLOAT
243
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
Invalid
Platform
File System Single-Row Requests Columns
Identify the significant single-row requests made by application software on the file system. Rows are distinguished as
permanent data (P), spool (S) or user append table / permanent journal table (APt).
FilePRowReadInit
count
Number of requests for an initial permanent
row read.
FLOAT
FilePRowReadCont
count
Number of requests for a continued permanent
row read.
FLOAT
FilePRowReplace
count
Number of requests for a permanent row
replace.
FLOAT
FilePRowInsert
count
Number of requests for a permanent row insert.
FLOAT
FilePRowDelete
count
Number of requests for a permanent row delete.
FLOAT
FilePRowAppend
count
Number of requests for a row append.
FLOAT
FileSRowReadInit
count
Number of requests for an initial spool row
read.
FLOAT
FileSRowReadCont
count
Number of requests for a continued spool row
read.
FLOAT
FileSRowReplace
count
Number of requests for a spool row replace/
update.
FLOAT
FileSRowInsert
count
Number of requests for a spool row insert.
FLOAT
FileSRowDelete
count
Number of requests for a spool row delete.
FLOAT
FileSRowAppend
count
Number of requests for a row append.
FLOAT
FileAPtRowReadInit
count
Number of requests for an initial append row
read.
FLOAT
FileAPtRowReadCont
count
Number of requests for an continued append
row read.
FLOAT
FileAPtRowReplace
count
Number of requests for an append row replace/
update.
FLOAT
FileAPtRowInsert
count
Number of requests for an append row insert.
FLOAT
FileAPtRowDelete
count
Number of requests for an append row delete.
FLOAT
FileAPtRowAppend
count
Number of requests for an append row append.
FLOAT
File System Multi-Row Requests Columns
Identify the significant multi-row requests made by application software on the file system. Rows are distinguished as
permanent data (P), spool (S) or user append table / permanent journal table (APt).
FilePBlkRead
244
count
Number of requests for a permanent data block
read.
FLOAT
Resource Usage Macros and Tables
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
FilePBlkReplace
count
Number of requests for a permanent data block
replace.
FLOAT
FilePRowNDel
count
Number of requests for a permanent data
multi-row delete.
FLOAT
FilePRownins
count
Number of requests for a permanent data
multi-row insert.
FLOAT
FilePRowNUpd
count
Number of requests for a permanent data
multi-row update.
FLOAT
FilePSortable
count
Number of requests for permanent table sort.
FLOAT
FilePTabdelete
count
Number of requests for a permanent table
delete.
FLOAT
FilePTabdelra
count
Number of requests for a multi-row delete.
FLOAT
FilePTabmrows
count
Number of requests for a permanent table
modification.
FLOAT
FilePTabrblocks
count
Number of requests for a permanent table
multi-block read.
FLOAT
FileSBlkRead
count
Number of requests for a spool data block read.
FLOAT
FileSBlkReplace
count
Number of requests for a spool data block
replace.
FLOAT
FileSRowNDel
count
Number of requests for a spool data multi-row
delete.
FLOAT
FileSRownins
count
Number of requests for a spool data multi-row
insert.
FLOAT
FileSRowNUpd
count
Number of requests for a spool data multi-row
update.
FLOAT
FileSSortable
count
Number of requests for spool table sort.
FLOAT
FileSTabdelete
count
Number of requests for a spool table delete.
FLOAT
FileSTabdelra
count
Number of requests for a spool multi-row
delete.
FLOAT
FileSTabmrows
count
Number of requests for a spool table
modification.
FLOAT
FileSTabrblocks
count
Number of requests for a spool table multiblock read.
FLOAT
FileAPtBlkRead
count
Number of requests for an append data block
read.
FLOAT
FileAPtBlkReplace
count
Number of requests for an append data block
replace.
FLOAT
Resource Usage Macros and Tables
Invalid
Platform
245
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
FileAPtRownins
count
Number of requests for an append data multirow insert.
FLOAT
FileAPtRowNDel
count
Number of requests for an append data multirow delete.
FLOAT
FileAPtRowNUpd
count
Number of requests for an append data multirow update.
FLOAT
FileAPtSortable
count
Number of requests for an append table sort.
FLOAT
FileAPtTabdelete
count
Number of requests for an append table delete.
FLOAT
FileAPtTabdelra
count
Number of requests for an append multi-row
delete.
FLOAT
FileAPtTabmrows
count
Number of requests for an append table
modification.
FLOAT
FileAPtTabrblocks
count
Number of requests for an append table multiblock read.
FLOAT
Invalid
Platform
File System Transient Journal Requests Column
Identifies the significant transient journal requests made by application software on the file system.
FileTJCalls
count
Number of transient journal calls.
FLOAT
FileTJDbUpdates
count
Number of WAL data blocks modified. The
modification can either be an update or a delete
of an existing WAL or TJ record.
FLOAT
TRANSIENT JOURNAL MANAGEMENT COLUMNS
Transient Journal Purge Overhead Columns
Identify the background overhead associated with the occasional transient journal purge operation.
TJPurges
count
The number of purge passes in which a blockby-block scan is done.
FLOAT
TJDbPurgeReads
count
The number of blocks actually mapped in
during the purge scan. This is a reasonable
approximate measure of the I/O load. The
system uses full-cylinder read mode, but the
block count would still be roughly
proportionate to the I/O load.
FLOAT
246
Resource Usage Macros and Tables
Appendix C: ResUsageIvpr Table
Column Name
Type of Data
Description
Data Type
TJDbPurgeDeletes
count
The number of blocks mapped in during the
scan that were included in the ranges of blocks
that were deleted.
FLOAT
Invalid
Platform
Before WAL, the ratio of deletes to reads would
have been a useful measure of the effectiveness
of the purge processing. However, with WAL,
the ratio cannot be interpreted quite so simply
because:
1 The range of deleted blocks could include
blocks that were not actually mapped in (and
therefore not counted). Blocks that contain
only WAL records are not mapped in during
the scan, as they are automatically filtered
out. Under typical conditions, there are
probably relatively few such blocks. TJ and
WAL records are typically generated in an
interleaved sequence by regular SQL
transactions. But during periods when the
system workload is dominated by
MultiLoad/FastLoad work, there will be
relatively few TJ records written, so the
proportion of WAL-only blocks would
probably be significant.
TJDbPurgeDeletes
(continued)
count
2 Post-WAL, neither TJDbPurgeReads nor
FLOAT
TJDbPurgeDeletes gets incremented during
a normal purge pass. Instead of scanning the
active data blocks, a pointer to the oldest
active transaction is maintained which is a
quicker method. Therefore, PurgeTJ() can
simply compute the bounds of the range of
records that can be deleted in the part of the
WAL/TJ that precedes the start of the oldest
transaction. This does not require any
scanning and the system cannot definitely
determine how many blocks actually get
deleted.
If the oldest transaction remains open for a
long time, then the quick purge method is
not effective. Therefore, the system reverts
back to the full scan method. The
TJDbPurgeReads and TJDbPurgeDeletes are
only incremented during a full scan.
WRITE AHEAD LOGGING COLUMNS
Identify the log-based file system recovery scheme in which modifications to permanent data are written to a log file, the
WAL log.
Resource Usage Macros and Tables
247
Appendix C: ResUsageIvpr Table
Summary Mode
Column Name
Type of Data
Description
Data Type
FileWAppends
count
Number of times a record was appended to the
WAL log. A single append call can append
multiple rows. Subtracting FileTJAppends from
this counter results in the number of times nontransient journal rows were appended to the
WAL log.
FLOAT
FileTJAppends
count
Number of times transient journal records were
appended to the WAL log. A single append call
can append multiple transient journal rows. A
transient journal append by itself does not
imply a write of a WAL block, nor a WAL
Cylinder Index (WCI) modification.
FLOAT
FileTJFlush
count
Number of times a request to force transient
journal records within the WAL log to be
written to disk has been issued. An increment of
this counter may or may not result in an I/O
depending on whether the request was to flush
records that were already on disk.
FLOAT
FileWDBCreates
count
Number of WAL data blocks created. The block
can contain either TJ records, WAL records or
both
FLOAT
FileWFlush
count
Number of times a request to force any record
in the WAL log to be written to disk has been
issued. An increment of this counter may or
may not result in an I/O depending on whether
the request was to flush records that were
already on disk. Subtracting FileTJFlush from
this counter results in the number of times a
non-transient journal WAL flush was issued.
FLOAT
FileWRowDelete
count
Number of times rows were deleted from the
WAL log.
FLOAT
FileWTabDelRa
count
Number of requests for a WAL multi-row
delete.
FLOAT
Invalid
Platform
Summary Mode
When Summary Mode is active for the ResUsageIvpr table, one row is written to the database
for each type of vproc on each node in the system, summarizing the vprocs of that type on
that node, for each log interval.
You can determine if a row is in Summary Mode by checking the SummaryFlag column for
that row.
248
Resource Usage Macros and Tables
Appendix C: ResUsageIvpr Table
Spare Columns
IF the SummaryFlag column value is…
THEN the data for that row is being logged…
‘S’
in Summary Mode.
‘N’
normally.
Spare Columns
The ResUsageIvpr table has 30 spare columns (one of which is being used) as shown in the
table below.
Column Name
Type of
Data
Description
SpareCount[00-09]
count
Spare counted statistic.
SpareTrack[00-09]
track
Spare tracked statistic.
SpareTmon00
n/a
The SpareTmon00 field contains the COD value. The
value represents the COD value in one tenths of a
percent, so a displayed value of 500 represents a COD
value of 50.0%.
Note: This value is valid only on SUSE Linux Enterprise
Server 10 systems and is a single value for the entire
system.
SpareTmon[01-09]
count
Spare time monitored statistic.
The spare column fields expand to values 00 - 09, so that column names would be
SpareCount01, SpareTrack02, SpareTmon07, and so on.
Resource Usage Macros and Tables
249
Appendix C: ResUsageIvpr Table
Spare Columns
250
Resource Usage Macros and Tables
APPENDIX D
Partition Assignments
With regards to Teradata Database, there is more than one definition of partition. The
partitions here refer to the following Parallel Database Extensions (PDE) and vproc definition:
•
A partition is a collection of tasks and associated resources grouped within a virtual
processor according to the function of the tasks. There are multiple partitions within a
single virtual processor. Partitions are the primary mechanism used by Teradata Database
for managing parallel programs.
•
Partitions are the subdivision of vproc software processes into 32 semi-isolated domains.
For example, in an AMP vproc, Partition 11 is the AWT Partition. In all other vproc types,
Partition 11 is unused.
Another partition description is only meaningful in a dialog between client programs and
Teradata Database. It has nothing to do with PDE vproc partitions, but is a way of enforcing
rules about what a client session is allowed to do and of keeping client sessions isolated from
each other. This concept of partitions is centered in the CLIv2 interface, specifically the
CONNECT parcel.
Partition reservation is as follows:
•
Partitions 0 through 6 are reserved by PDE
•
Partitions 7 through 47 are for use by Teradata Database
The table listed under “Partition Assignment Listing” on page 252 describes the individual
partitions. Teradata Database uses the following vprocs:
Vproc Type
Description
AMP
Access module processors perform database functions, such as executing database
queries. Each AMP owns a portion of the overall database storage.
GTW
Gateway vprocs provide a socket interface to Teradata Database.
Node
The node vproc handles PDE and operating system functions not directly related to
AMP and PE work. Node vprocs cannot be externally manipulated, and do not
appear in the output of the Vproc Manager utility.
PE
Parsing engines perform session control, query parsing, security validation, query
optimization, and query dispatch.
RSG
Relay Services Gateway provides a socket interface for the replication agent, and for
relaying dictionary changes to the Teradata Meta Data Services utility.
VSS
Manages Teradata Database storage. AMPs acquire their portions of database
storage through the TVS vproc.
Resource Usage Macros and Tables
251
252
Partition usage is also discussed under “CPU Utilization Columns” on page 127 in the Chapter 13: “ResUsageSvpr Table”
chapter.
Table Conventions
The following table describes the table symbols used in the partition assignments table below.
The symbol used in the Partition
Assignment Listing…
Indicates…
——
partition is unused.
?
activity has been observed but not identified.
Partition Assignment Listing
The following table lists the Node, AMP, and PE (Parsing Engine), GTW, and RSG, and VSS (allocator/node agent) usage of
PDE vproc partitions by PDE and Teradata Database.
Partition:
Usage in Vprocs of Type:
Resource Usage Macros and Tables
No.
Name
Node
AMP
0
Kernel
PDE daemons
——
1
System Debugger
System Debugger tasks
2
Console
Console
Supervisor
——
3-6
Interactive 1 through
4
——
Console
interactive
partition
programs
7
Service
Console utilities
PE
——
GTW
RSG
VSS
Resource Usage Macros and Tables
Partition:
Usage in Vprocs of Type:
No.
Name
Node
AMP
PE
GTW
8
CnsProc
——
Host Utility
console
procedures
——
9
Filesys
——
File System
processes
——
10
Gateway
gtw processes
——
11
AWT
——
AMP Worker
Tasks
12
Session
——
Session Control tasks
13
Dispatch
——
Dispatcher tasks
14
Unused
——
Unused
15
Startup
——
16
[unused]
——
17
RSS Startup
File system rss
startup
18
DDF Server
DDF services
19
[unused]
——
20 - 22
[unused]
——
23 - 28
[unused]
——
29
[unknown]
——
30
[unused]
——
RSG
——
Startup tasks
MDS program
rsgmain
——
VSS
253
254
Partition:
Usage in Vprocs of Type:
No.
Name
Node
AMP
PE
GTW
RSG
VSS
31
Allocator
——
Allocator services
32
Node Agent
——
Node Agents
services
33
Clique Coordinator
——
Clique
Coordinator
services
34 - 47
[unused]
——
Resource Usage Macros and Tables
Glossary
AG
Allocation Group
AMP
Access Module Processor
API Application Programming Interface
AWT
AMP Worker Task
BYNET
Banyan Network (high-speed connection)
DBW
Database Window
DDL
Data Definition Language
FSG
File Segment
GTW
Teradata Gateway
I/O Input/Output
LAN
Local Area Network
MPP Massively Parallel Processing
NUPI
Nonunique Primary Index
PDE Parallel Database Extensions. PDE is a software interface layer between the operating
system and the Teradata Database software. It provides Teradata Database the ability to run in
a parallel environment, execute vprocs, and more.
PE
Parsing Engine
PG
Performance Group
PMA
Processor Module Assembly. This refers to a node.
PMPC APIs Performance Monitor and Production Control Application Programming
Interfaces
PP
Performance Period
RDBMS
Relational Database Management System
ResUsage Resource Usage. The subsystem that logs Resource Usage data from RSS to the
ResUsage tables.
RSG
Relay Services Group
Resource Usage Macros and Tables
255
Glossary
RSS Resource Sampling Subsystem. The RSS provides a method to gather statistics from
across the Teradata Database system, and provides the ability to access the statistics through
an API. ResUsage uses the RSS data from the RSS API to log data to the selected ResUsage
tables.
SMP
TCHN
Symmetric Multi-Processing
Teradata Channel
Teradata ASM
TPA
Teradata Active System Management
Trusted Parallel Application
VNET
Virtual Network. Virtual BYNET for a single-node.
vproc
Virtual Processor
WD Workload Definition
WCI
256
WAL Cylinder Index
Resource Usage Macros and Tables
Index
Symbols
?, meaning in macro outputs 176
A
AMP information
macros 177, 182
table 125
view 152
Average values
determining for gather period 42
B
ByGroup
macros, description of 31
C
Clearing old resource usage data 36
Co-existing node macros. See ByGroup macros
Collecting resource usage data 17
CollectIntervals
using to determine average 42
CPU use by AMP macro output columns
Awt User Exec% 182
Awt User Serv% 182
Misc User Exec% 182
Misc User Serv% 182
Total Busy% 182
Total User Exec% 182
Total User Serv% 182
CPU use by AMPs macros
function 182
input format examples 182
normalized viewing 184
output column descriptions 182
ResAmpCpuByGroup 182
ResCPUByAMP 182
ResCPUByAMPOneNode 182
usage notes 182
CPU use by each node macros
function 189
input format examples 189
output examples 189
ResCPUByGroup 189
ResCPUByNode 189
ResCPUOneNode 189
Resource Usage Macros and Tables
usage notes 189
CPU use by nodes macro output columns
I/O Wait % 190
Total Busy % 190
Total User Exec % 190
Total User Serv % 190
CPU use by PEs macro output columns
Disp User Exec% 186
Disp User Serv% 186
Misc User Exec% 186
Misc User Serv% 186
Pars User Exec% 186
Pars User Serv% 186
Ses User Exec% 186
Ses User Serv% 186
Total Busy% 187
Total User Exec% 187
Total User Serv% 187
CPU use by PEs macros
function 186
input format examples 186
normalized viewing 188
output column descriptions 186
output examples 186
ResCPUByPE 186
ResCPUByPEOneNode 186
ResPeCpuByGroup 186
usage notes 186
D
Database commands
SET LOGTABLE 28
SET RESOURCE 28
SET SUMLOGTABLE 28
Database Window Supervisor
setting logging rates 28
Database Window. See DBW
Deleting old resource usage data 36
DISABLE LOGONS
effects on logging 36
E
Example
executing ResAmpCpuByGroup macro 35
executing ResCPUByAmp macro 34
executing ResCPUByAmpOneNode macro 35
257
Index
ResAmpCpuByGroup macro report 183
ResAWT macro report 180
ResAWTByAMP macro report 180
ResAWTByNode macro report 181
ResCPUByAMP macro report 183
ResCPUByAMPOneNode macro report 183
ResCPUByGroup macro report 191
ResCPUByNode macro report 190
ResCPUByPE macro report 187
ResCPUByPEOneNode macro report 187
ResCPUOneNode macro report 190
ResHostByGroup macro report 195
ResHostByLink macro report 194
ResHostOneNode macro report 195
ResLdvByGroup macro report 198, 201
ResLdvByNode macro report 197, 200, 201
ResLdvOneNode macro report 197
ResMemByGroup macro report 204
ResMemMgmtByNode macro report 204
ResMemMgmtOneNode macro report 204
ResNetByGroup macro report 207
ResNetByNode macro report 206
ResNetOneNode macro report 206
ResNode macro report 211
ResNodeByGroup macro report 212
ResNodeByNode macro report 212
ResOneNode macro report 211
ResPeCpuByGroup macro report 187
ResPsByGroup macro report 216
ResPsByNode macro report 215
ResPsByNodeWDJoin macro report 216
ResVdskByGroup macro report 219
ResVdskByNode macro report 219
ResVdskOneNode macro report 219
EXECUTE MACRO, syntax elements 32
F
KBs/Blk Read 193
KBs/Blk Write 193
Max ReqQ Len 193
Msgs/Blk Read 193
Msgs/Blk Write 193
Host communications traffic information
macros function 192
macros input format examples 192
macros usage notes 192
table 79
view 157
Host communications traffic macros
output column descriptions 193
ResHostByGroup 192
ResHostByLink 192
ResHostOneNode 192
I
Invalid platform columns, description 41
L
Logging
costs 23
optimizing 23
rates 21
resource usage data 17
which tables to enable 20
Logging rates
definition 21
minimum 22
recommended values 22
using SET RESOURCE 28
Logical device information
macros 196, 218
table 85
view 158
format. See Macro input
M
G
Macro input 29
Macro output format
general format 175
ID 175
statistics 175
Macro statistics, datatypes 176
Macro syntax element
for all nodes 33
for co-existing nodes 33
for multinodes 33
FromDate 33
FromNode 34
FromTime 33
Node 34
GmtTime 38
H
Host communication traffic macro output columns
Avg ReqQ Len 193
Blk Read Fail % 193
Blk Write Fail % 193
Blks Read/Sec 193
Blks Write/Sec 193
Host Type 193
KBs Read/Sec 193
KBs Write/Sec 193
258
Resource Usage Macros and Tables
Index
ToDate 33
ToNode 34
ToTime 33
Macros
logging rates for tables 176
usage notes 176
Macros, types of
all-node 29
ByGroup 29
multiple-node 29
one-node 29
Memory management by node macros
function 202
input format examples 202
output column descriptions 202
ResMemByGroup 202
ResMemMgmtByNode 202
ResMemMgmtOneNode 202
usage notes 202
Memory management macro output columns
# Proc Swp 203
% Mem Free 202
Ages/Sec 203
Aloc Fail % 203
KB/Swp Drp 203
KB/Swp Rd 203
KB/VPR Aloc 203
P+S Drps/Sec 203
P+S I/O % 203
P+S Rds/Sec 203
P+S Wrts/Sec 203
Pg Drps/Sec 203
Pg Rds/Sec 203
Pg Wrts/Sec 203
Swp Drps/Sec 203
Swp Rds/Sec 203
Text Alocs/Sec 202
VPR Alocs/Sec 202
MULTISET table
why resusage tables are created as 38
N
Node information
macros 177, 189
view 148
Node network traffic macro output columns
% Brd 206
% PtP 206
% Retries 205
KB/IO 206
Total IOs/Sec 206
Total Reads/Sec 205
Total Writes/Sec 206
Resource Usage Macros and Tables
Node network traffic macros
function 205
input format examples 205
output column descriptions 205
ResMemMgmtByNode 205
ResNetByGroup 205
ResNetOneNode 205
usage notes 205
Nonunique primary index 38
NUPI. See Nonunique primary index
O
Occasional event data 38
One-Node
macros, description of 31
One-Node macros, description 31
Overall resource usage information. See Summary macros
P
Parameters, macros use of 32
Partition Assignments
listing 252
reserved for 251
table convention 252
Partitions, definition 251
PE information
macros 186
table 125
view 154
Priority Scheduler information
macros function 213
macros input format examples 213
macros usage notes 213
Priority Scheduler macros
ResPsByGroup 213
ResPsByNode 213
ResPsByNodeWDJoin 213
Purging old resource usage data 36
Q
Question marks, meaning in macro outputs 176
R
Rates
logging rate definition 21, 22
recommended values 22
rules for setting 22
Raw disk drive traffic macro output columns
Avg I/O Resp 196, 199, 218
KB/ I/O 196, 199
Out Rqst Time % 197, 200
259
Index
Reads/Sec 196, 199
Writes/Sec 196, 199
Raw disk drive traffic macros
function 196, 199
input format examples 196, 199
output column descriptions 196, 199
ResLdvByGroup 196
ResLdvByNode 196
ResLdvOneNode 196
usage notes 196, 199
Relational Primary Index 38
ResAmpCpuByGroup macro
column descriptions 182
input format example 182
sample output 184
usage notes 182
what it reports 182
ResAWT macro
column description 177
input format example 177
output column descriptions 178
sample output 180
usage notes 177
what it reports 177
ResAWTByAMP macro
column description 177
input format example 177
output column descriptions 178
sample output 180
usage notes 177
what it reports 177
ResAWTByNode macro
column description 177
input format example 177
output column descriptions 178
sample output 181
usage notes 177
what it reports 177
ResCPUByAMP macro
column descriptions 182
input format example 182
sample output 183
usage notes 182
what it reports 182
ResCPUByAMPOneNode macro
column descriptions 182
sample output 184
usage notes 182
what it reports 182
ResCPUByGroup macro
column descriptions 189
sample output 191
usage notes 189
what it reports 189
260
ResCPUByNode macro
column descriptions 189
input format example 189
sample output 190
usage notes 189
what it reports 189
ResCPUByPE macro
column descriptions 186
input format example 186
sample output 187
usage notes 186
what it reports 186
ResCPUByPEOneNode macro
column descriptions 186
sample output 188
usage notes 186
what it reports 186
ResCPUOneNode macro
column descriptions 189
sample output 190
usage notes 189
what it reports 189
ResCPUUsageByAMPView, definition listing 152
ResCPUUsageByPEView, definition listing 154
ResGeneralInfoView, definition listing 148
ResHostByGroup macro
column descriptions 193
sample output 195
usage notes 192
what it reports 192
ResHostByLink macro
column descriptions 193
input format example 192
sample output 194
usage notes 192
what it reports 192
ResHostOneNode macro
column descriptions 193
sample output 195
usage notes 192
what it reports 192
ResLdvByGroup macro
column descriptions 196, 199
sample output 198, 201
usage notes 196, 199
what it reports 196, 199
ResLdvByNode macro
column descriptions 196, 199
input format example 196, 199
sample output 197, 200, 201
usage notes 196, 199
what it reports 196, 199
ResLdvOneNode macro
column descriptions 196, 199
Resource Usage Macros and Tables
Index
usage notes 196, 199
what it reports 196, 199
ResMemByGroup macro
column description 202
sample output 204
usage notes 202
what it reports 202
ResMemMgmtByNode macro
column description 202
input format example 202
sample output 204
usage notes 202
what it reports 202
ResMemMgmtOneNode macro
column description 202
sample output 204
usage notes 202
what it reports 202
ResNetByGroup macro
column description 205
sample output 207
usage notes 205
what it reports 205
ResNetByNode macro
column description 205
input format example 205
sample output 206
usage notes 205
what it reports 205
ResNetOneNode macro
column description 205
sample output 206
usage notes 205
what it reports 205
ResNode macro
column description 208
input format example 208
sample output 211
usage notes 208
what it reports 208
ResNodeByGroup macro
column description 208
sample output 212
usage notes 208
what it reports 208
ResNodeByNode macro
column description 208
sample output 212
usage notes 208
ResOneNode macro
column description 208
sample output 211
usage notes 208
what it reports 208
Resource Usage Macros and Tables
Resource usage data
collecting 17
definition 15
deleting old data 36
functions of 15
logging 17
saving old data 32
Resource usage macros
definition 18
example of executing a ByGroup macro 35
example of executing a Multinode macro 34
example of executing a One-Node macro 35
executing 32
syntax for 32
Resource Usage tables. See ResUsage tables
Resource usage views
ResCPUUsageByAMPView 152
ResCPUUsageByPEView 154
ResGeneralInfoView 148
ResShstGroupView 157
ResSldvGroupView 158
ResSvprView 166
ResPeCpuByGroup macro
column descriptions 186
sample output 188
usage notes 186
what it reports 186
ResPsByGroup macro
column description 213
sample output 216
usage notes 213
what it reports 213
ResPsByGroup macro column description 213
ResPsByNode macro
column description 213
input format example 213
sample output 215
usage notes 213
what it reports 213
ResPsByNode macro column description 213
ResPsByNodeWDJoin macro
sample output 216
ResSawtView, definition listing 155
ResShstGroupView, definition listing 157
ResSldvGroupView, definition listing 158
ResSpsView, definition listing 159
ResSvprView, definition listing 166
ResUsage tables
columns ending in "Avg" 42
enabling Summary Mode 28
invalid platform columns 41
naming convention 37
primary index 38
reporting Summary Mode 42
261
Index
ResUsageIpma 20
ResUsageIvpr 20
ResUsageSawt 20
ResUsageShst 20
ResUsageSldv 20
ResUsageSpdsk 91
ResUsageSpma 20
ResUsageSps 20
ResUsageSvdsk 20
ResUsageSvpr 20
types of statistics reported 39
which to enable 20
ResUsageIpma
column names 227
gathering method 227
ResUsageIvpr
column names 237
gathering method 237
spare columns 249
Summary Mode 248
ResUsageSawt
column names 73
Summary Mode 77
ResUsageScpu
column names 45
spare columns 48
Summary Mode 48
ResUsageShst
spare columns 84
Summary Mode 83
ResUsageSldv
column names 79, 85
gathering method 85
spare columns 89
Summary Mode 88
ResUsageSpdsk
column names 91
gathering method 91
spare columns 97
Summary Mode 97
ResUsageSpma
column names 51
ResUsageSps
column names 99
ResUsageSvdsk
column names 119
gathering method 119
spare columns 78, 116, 124
Summary Mode 124
ResUsageSvpr
column names 125
spare columns 143
Summary Mode 142
ResVdskByGroup macro
262
column descriptions 218
sample output 219
usage notes 218
what it reports 218
ResVdskByNode macro
column descriptions 218
input format example 218
sample output 219
usage notes 218
what it reports 218
ResVdskOneNode macro
column descriptions 218
sample output 219
usage notes 218
what it reports 218
RSS logging
enabling from ctl and xctl 27
enabling from DBW 28
RSS table settings
enabling from Database Window 28
S
Saving old resource usage data 32
SET LOGTABLE command 28
SET RESOURCE command 28
SET SUMLOGTABLE command 28
Single-Node. See One-Node
Stopped logging
how to re-enable logging 36
Summary macro output columns
A+R % of IOs 210
CPU Bsy % 210
CPU Eff % 210
Fre Mem % 210
Ldv Eff % 210
Ldv IOs/Sec 210
Ldv KB/IO 210
Mem Age/Sc 210
Mem Aloc/Sec 210
Mem Fai % 210
ms/Blk 211
Net Rtry % 211
P+S % of IOs 210
Prc Blks/Sec 211
Read % of IOs 210
TMIt IOs/Sec 210
TPtP IOs/Sec 210
WIO % 210
Summary macros
function 208, 213
input format examples 208, 213
output column descriptions 210
ResNode 208
Resource Usage Macros and Tables
Index
ResNodeByGroup 208
ResNodeByNode 208
ResOneNode 208
usage notes 208, 213
Summary Mode
description 42
enabling a table 28
using 22
Syntax for
deleting old resource usage data 36
executing macros 32
reporting dates in macros 33
Syntax, how to read 221
System information
macros 177
T
Table naming conventions 37
Tables
which to enable 19
Teradata ASM and Priority Scheduler macros 213, 216
Teradata Virtual Storage 41
V
Vdisk device traffic information
macros 218
Vdisk drive traffic macro output columns
Avg I/O Resp 218
Out Rqst Time % 219
Rd KB/ I/O 218
Read Cnt/ Sec 218
Write Cnt/ Sec 218
Wrt KB/ I/O 218
Vdisk drive traffic macros
output column descriptions 218
ResVdskByNode 218
ResVdskOneNode 218
Vdisk logical drive traffic macros
ResVdskByGroup 218
Views, resource usage data 147
Resource Usage Macros and Tables
263
Index
264
Resource Usage Macros and Tables