You are on page 1of 33

Resource Usage Porting Guide

Release 14.0
B035-1183-111A
November 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: teradata-books@lists.teradata.com.
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 2011 by Teradata Corporation. All Rights Reserved.

Resource Usage Porting Guide

Table of Contents
Chapter 1 Introduction ........................................................................ 5
1.1
1.2
1.3
1.4
1.5

Scope ............................................................................................................................... 5
RSS API Changes ........................................................................................................... 5
ResUsage Table Changes ................................................................................................ 5
ResUsage Table Views ................................................................................................... 5
ResUsage Table Report Macros...................................................................................... 6

Chapter 2 ResUsage Changes .............................................................. 7


2.1
Averages ......................................................................................................................... 7
2.2
Spare Fields ..................................................................................................................... 9
2.2.1
Spare Fields Converted to Generic Spare Fields .....................................................9
2.2.2
Used Spare Fields Converted ...................................................................................9
2.3
Ipma Table Fields ......................................................................................................... 10
2.3.1
RSS Reserved Fields Added in the Ipma Table .....................................................10
2.3.2
Ipma Table Fields Cleaned Up ..............................................................................11
2.4
VSS Fields Renamed .................................................................................................... 11
2.5
Normalized CPU Columns Removed ........................................................................... 11
2.6
Sps Table Fields ............................................................................................................ 12
2.6.1
Sps Table Cleaned Up ............................................................................................12
2.6.2
SUSE Linux Enterprise Server 10 versus SUSE Linux Enterprise Server 11 .......12
2.7
ResUsage Table Views ................................................................................................. 13
2.7.1
Views for All ResUsage Tables Created or Updated.............................................13
2.7.2
PE-Only Nodes ......................................................................................................13
2.7.3
Mem Fields Reporting in KB .................................................................................14
2.8
Timestamp Housekeeping Field Added to All Tables .................................................. 16
2.9
Field Changes for All Tables ........................................................................................ 16
2.9.1
Ipma Table .............................................................................................................16
2.9.2
Scpu Table .............................................................................................................18
2.9.3
Sldv Table ..............................................................................................................19
2.9.4
Spma Table ............................................................................................................19
2.9.5
Svpr Table ..............................................................................................................21
2.9.6
Ivpr Table ...............................................................................................................25
2.9.7
Shst Table...............................................................................................................25
2.9.8
Spdsk Table............................................................................................................26
2.9.9
Svdsk Table............................................................................................................27
2.9.10
Sawt Table .............................................................................................................28
2.9.11
Sps Table................................................................................................................29

Appendix A: Glossary ......................................................................... 32

Page 3

Resource Usage Porting Guide

Page 4

Resource Usage Porting Guide

Chapter 1

Introduction

1.1 Scope
This document describes the Teradata Database 14.0 Resource Sampling Subsystem (RSS) changes that
affect users of the Resource Usage (ResUsage) tables.
RSS was rewritten in Teradata Database 14.0 which changed how data was collected. This affected how
some of the fields behave, most significantly the sampled averages.
The ResUsage tables are updated for each major Teradata release to add new fields and delete obsolete
fields. In this release views were added for all ResUsage tables that did not have views yet. The existing
report macros were updated for the field changes and to access that data through the views.
All of these changes will be described more fully in this document.

1.2 RSS API Changes


RSS API changes were made but do not directly affect external users of the ResUsage data. This
document will not describe the internal RSS API changes.

1.3 ResUsage Table Changes


The ResUsage table changes affect every ResUsage table and involve the addition of new fields,
renaming of existing fields, and the removal of obsolete fields. All major releases of Teradata have
ResUsage field changes since changes are not allowed at other times. Teradata Database 14.0 has more
than the usual number of field changes due to several factors. The RSS architecture change caused some
fields to be deleted and others to be renamed. Teradata Database 14.0 no longer supports MP-RAS so
fields that were specific to that operating system were deleted. New fields were added for features from
the Release 13.10 and Teradata Database 14.0 release.

1.4 ResUsage Table Views


ResUsage Views have been created from each of the ResUsage tables. The ResShstGroupView,
ResSldvGroupView, and ResSvdskGroupView views have been renamed by dropping the Group from
the name. The ResGeneralInfoView was not renamed and is the only view for the ResUsageSpma table.

Page 5

Resource Usage Porting Guide

All tables except for the Spma table have views named following the format Res<tbl>View, for
example: ResSldvView.

1.5 ResUsage Table Report Macros


ResUsage report macros have been changed to reflect the changes to the fields. The macros have also
been changed to access the ResUsage data through the views.

Page 6

Resource Usage Porting Guide

Chapter 2

ResUsage Changes

2.1 Averages
The most significant change caused by the new architecture is the removal of the CollectIntervals field
from all the tables. The new architecture provides each user of RSS (ResUsage data logging is one user
of RSS) complete independence from other users, so there is only one sample point for fields that are
gathered at the end of the data reporting period (Log period for the ResUsage logging). This removed
the automatic sampled averages behavior of certain fields. These fields had a Sum suffix and produced
a sampled average by dividing by the CollectIntervals field. With the new data model the
CollectIntervals would always be one and the resulting average value would really just be the value
reported for that period.
Reported averages can still be generated where it makes sense in the code reporting the data. For
example the ResUsageSldv table view, ResSldvView, produces a sampled average:
LdvOutReqAvg = LdvOutReqSum /LdvOutReqDiv
The Sum and Div fields are both provided by the reporting code and are not related to the previous
CollectIntervals field.
Some averages can be calculated based on two related fields, where one is a count of instances and the
other is the total of some value over those instances. For example, the Svdsk table reports the number of
reads and the total read KBs and read response time.
Average Read size in KBs = ReadKB/ReadCnt
Average Read Response time = ReadRespTot/ReadCnt
In all tables the CollectIntervals field has been removed. There is no other impact to the Scpu and Svdsk
tables so they are not included in the following table.
The following table lists the fields affected by the elimination of multiple gather periods per reporting
period.

Page 7

Resource Usage Porting Guide

Averaged Fields in Release 13.10


Table
Spma

Field
ProcReadySum
ProcBlockedSum
ProcSuspendedSum
ProcRunningSum
NetSemInUseSum
NetChanInUseSum
NetGroupInUseSum

Shst
Sldv

HostQLenSum
CmdStmtsInProgSum
LdvOutReqSum

Svpr

MsgWorkQLenSum

Ipma

DBLockBlocksSum
DBLocksHeldSum
NetBlockQueueSum

Ivpr

ProcWorkType[i]Sum

Notes
Renamed ProcReady and now reports end of period value.
Not valid for Windows. Renamed ProcBlocked and now
reports end of period value.
Not valid for Linux. Windows - removed field.
Not valid for Linux. Windows - removed field.
Renamed NetSemInUse and now reports end of period value.
Track field.
Renamed NetChanInUse and now reports end of period
value. Track field.
Renamed NetGroupInUse and now reports end of period
value. Track field.
Not valid for Linux. Windows - removed field.
Not valid for Linux. Windows - removed field.
LdvOutReqSum now reports a time weighted total of
samples. A new count field LdvOutReqDiv is added that
contains the divisor, which is the delta time in seconds for
the sample.
The ResSldvView View performs the calculation to provide
the average value:
LdvOutReqAvg = LdvOutReqSum / LdvOutReqDiv
Renamed MsgWorkQLen and now reports end of period
value. Track field.
Removed. There is an existing DBLockBlocks field.
Not valid removed.
Renamed NetBlockQueue and now reports end of period
value. Track field.
Not valid removed.

Some fields will benefit from this change since count fields that were not intended to be an average
value will no longer need to be divided by the CollectIntervals field.
Non-Average Fields (Benefit)
Table
Spma

Field
AwtFlowControlled

Sawt

AwtInuse
MailBoxDepth
WorkTypeInuse00-15

Notes
Number of AMPs currently in flow control on the work input
mailbox
Number of AWTs currently in use
depth of the AMP work mailbox
Current number of AWTs in use

Page 8

Resource Usage Porting Guide

Table
Sldv
Spdsk

Field
QReadLength
QWriteLength
MigrationBlockedIos

Notes
invalid
invalid
Number of inputs and outputs that are blocked

2.2 Spare Fields


2.2.1 Spare Fields Converted to Generic Spare Fields
The spare fields in prior releases are broken down into count, track and tmon type spare fields. This is
not necessary and can be confusing when the fields are used, such as when all the count spare fields are
used so that a tmon spare field is used as a normal count spare field. The names of the spare fields have
been changed to just sparexx, where xx is the two digit number.
Note: There is an issue with efix usage of the Spare fields rolling forward. When an efix uses a spare
field and we have moved past the Teradata Database 14.0 release where we change the spare field
names, then when the efix rolls forward from Teradata Database 13.10 to Teradata Database 14.0, the
SpareCount00 name will no longer be defined. This will be manually fixed with the appropriate new
spare field name. The number of times the spare fields are used more than one release in the past is rare.
2.2.2 Used Spare Fields Converted
All Spare fields that are used in Teradata Database 13.10 were changed to permanent fields in Teradata
Database 14.0. New fields were added and views were updated where the Spare fields were mapped to
the final names. Refer to Resource Usage Macros and Tables for a description of the fields.
Table
Spma

Ipma
Ivpr
Scpu
Shst
Sldv

Page 9

Release 13.10 name


SpareCount00
SpareCount01
SpareTmon00
SpareTrack00
SpareTrack01
SpareTrack02
SpareTrack03
SpareTmon00
SpareTmon00
SpareTmon00
SpareTmon00
SpareTmon00

Release 14.0 name


TvsReadRespMax
TvsWriteRespMax
CodFactor
FileAcqsOther
FileAcqOtherKB
FileRelsOther
FileRelOtherKB
CodFactor
CodFactor
CodFactor
CodFactor
CodFactor

Resource Usage Porting Guide

Table
Spdsk
Svdsk
Svpr

Sawt

Sps

Release 13.10 name


SpareTmon00
SpareTmon00
SpareTmon00
SpareCount00
SpareCount01
SpareCount02
SpareCount03
SpareCount04
SpareCount05
SpareCount06
SpareCount07
SpareTmon01
SpareTmon02
SpareTmon03
SpareCount02
SpareCount03
SpareTmon00
SpareCount00
SpareCount01
SpareCount02
SpareCount03
SpareCount04
SpareCount05
SpareCount06
SpareCount07
SpareCount08
SpareTmon00
SpareTrack00

Release 14.0 name


CodFactor
CodFactor
CodFactor
DBMergeTried
DBMergeDone
DBMergeElim
DBMergeExtraIO
FileACPCylsSkipped
FileACPCylsMigr
FileACPCylsUnFSEOnly
FileACPCylsPostponed
FSGCacheWaits
FSGCacheWaitTime
FSGCacheWaitTimeMax
Available
AvailableMin
CodFactor
WorkMsgSendDelay
WorkMsgSendDelayMax
WorkMsgReceiveDelay
WorkMsgReceiveDelayMax
WorkTimeInuse
WorkTimeInuseMax
AwtReleases
WorkMsgSendDelayCnt
WorkMsgReceiveDelayCnt
CodFactor
AMPcount

2.3 Ipma Table Fields


2.3.1 RSS Reserved Fields Added in the Ipma Table
Twenty internal fields were added to the Ipma table definition. These fields are reserved for use by the
RSS application. The fields are named RssInternal[00-19].

Page 10

Resource Usage Porting Guide

2.3.2 Ipma Table Fields Cleaned Up


Fields in the Ipma table were removed that were duplicates (identical to) the fields in the Spma table.
The following fields were removed:

NetRxCircBrd
NetRxCircPtP
NetRxKBBrd
NetRxKBPtP
NetTxCircBrd
NetTxCircPtP
NetTxKBBrd
NetTxKBPtP
NetTxCircHPBrd
NetTxCircHPPtP
NetBackOffs

2.4 VSS Fields Renamed


Fields starting with Vss were renamed to start with Tvs to match the Teradata Virtual Storage feature
name. Field names were changed in the ResUsageSpma table (the only impacted table) and the
ResGeneralInfoView view was updated to reflect their final names.
Table
Spma

13.10 name
VssReadCnt
VssWriteCnt
VssReadRespTot
VssWriteRespTot
VssReadMax
VssWriteMax

14.0 name
TvsReadCnt
TvsWriteCnt
TvsReadRespTot
TvsWriteRespTot
TvsReadRespMax
TvsWriteRespMax

2.5 Normalized CPU Columns Removed


CPU*Norm fields were removed from the Spma table to reduce memory and disk usage.

Page 11

CPUIdleNorm
CPUIoWaitNorm
CPUUExecNorm
CPUUServNorm

Resource Usage Porting Guide

There is no need to log them when they can be generated as needed from the existing fields in the table.
NodeNormFactor and normalized CPU values were added to ResGeneralInfoView in the Teradata
Database 13.10 release.
The NodeNormFactor value is scaled by a factor of 100, so if the field shows a value of 850 the actual
normalization factor is 850/100 = 8.50. This means that the node performance is 8.5 times higher than
the reference node.
The ResGeneralInfoView provides the following calculations related to the CPU columns and
normalization:
(
(
(
(
(

(CPUUServ
CPUUServ
CPUUExec
CPUIoWait
(CPUUServ

+
/
/
/
+

CPUUExec) / NULLIFZERO(NCPUs) ) AS CPUBusy,


NULLIFZERO(NCPUs) )
AS CPUOpSys,
NULLIFZERO(NCPUs) )
AS CPUUser,
NULLIFZERO(NCPUs) )
AS CPUWaitIO,
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,

Note that the Normalized CPU values are used for coexistence system CPU usage comparisons, where
faster nodes will have larger reported CPU usage than slower nodes.

2.6 Sps Table Fields


2.6.1 Sps Table Cleaned Up
Spares were reduced to 20 generic spares.
In Release 13.10, the Sps table was changed so that it reported data rows by vproc type rather than an
individual vprid to reduce the amount of memory the SPS table consumed. This was the summary mode
behavior, so in Release 14.0 there is no need for summary mode in the Sps table. Therefore, the
summaryflag and vprid fields were removed.
The Sps_CPUUServPars and Sps_CPUUExecPars fields were removed. The Parser and Dispatcher were
combined into the same partition several releases ago.
2.6.2 SUSE Linux Enterprise Server 10 versus SUSE Linux Enterprise
Server 11
The Priority Scheduler changes for SUSE Linux Enterprise Server 11 in Release 14.0 removed the
usefulness of the PPid and AGid fields in the Sps table. However, in Release 14.0, the SUSE Linux

Page 12

Resource Usage Porting Guide

Enterprise Server 10 Priority Scheduler is still supported, so the PPid and AGid fields are still required.
When SLES10 is no longer supported the PPid and AGid fields will be removed.
A new Virtual Partition ID (VPid) field was added. Only one VPid can be associated with a
{pWDid,VprType} row at any point in time. Multiple pWDid values can be associated with a VPid.
The following table shows the fields used for SUSE Linux Enterprise Server operating system release.
Sps Table Field
RowIndex1
VprType
PPid
AGid
VPid

SLES10
PGid
VprType
PPid
AGid
0 - not used

SLES11
pWDid
VprType
zero - not used
zero - not used
VPid

For ResPs macros, such as ResPsByNode, the column label RowIndex1 will still display as PGid
(instead of pWDid) when running in SUSE Linux Enterprise Server 11.

2.7 ResUsage Table Views


2.7.1 Views for All ResUsage Tables Created or Updated
Views were provided for all ResUsage tables that contain all data fields and include the spare fields. All
views contain all the fields in the table in addition to any combining of fields or other math resulting in
new fields. This allows the view to be the primary interface to the ResUsage data rather than the
ResUsage tables themselves. Any corrections to any fields in the view can be made without affecting the
table, and you will not need to change any reports to pick up the corrected field. Views can be modified
without sysinit/tableinit operations.
2.7.2 PE-Only Nodes
With PE-only nodes included in a system, the ResNode macro (in previous releases) may have reported
a system cpu busy % value that was lower than expected. This is because the ResNode macro included
all nodes in the system in the calculation of the average cpu busy % and the PE-only nodes may have
significantly lower CPU utilization than the AMP nodes.
You can include a condition clause that selects only the AMP nodes in a macro. This provides the
intuitively expected result of how busy the database is, excluding the PE-only nodes.
WHERE VPROCTYPE1=AMP

Page 13

Resource Usage Porting Guide

You can obtain utilization of the PE-only nodes using the ResNodeByNode macro and specifying the
desired PE-only nodes.
The implemented solution is to change the default template of the GroupId field in the
ResGeneralInfoView view to create two groups with the PE-only nodes in one and the AMP nodes in
the other. The GroupId field allows reporting of coexistence systems by splitting nodes with different
characteristics into separate groups for reporting purposes. Consider the PE-only nodes as a separate part
of a coexistence system, with potentially other groupings included. The two defined groups are PEonly
and AMPNodes. This provides the correct cpu busy % visibility for both groups of nodes in the
ResNodeByGroup macro.
Coexistence systems can still group nodes by changing the ViewResGeneralInfo case statement. For
example, to identify 5600H AMP nodes as a separate group, you can use the following case statement:
CASE
WHEN (VPROCTYPE1=AMP AND NodeType IN ('5600H') THEN 'AMPNodes5600H'
WHEN (VPROCTYPE1=AMP AND NodeType NOT IN ('5600H) THEN 'AMPNodesOther'
ELSE 'PEonly'
END,

The first CASE WHEN statement selects a group that contains 5600H nodes that have AMPs. The
second CASE WHEN selects a group that contains nodes that have AMPs but are not 5600H nodes. The
final ELSE statement puts all the unmatched nodes into the group called PEonly.
In this example, changes to the GroupId statement for a customer site with a coexistence system of
5550H, 5555H and 5600H AMP nodes with 5550H PE-only would be:
CASE
WHEN (VPROCTYPE1=AMP AND NodeType IN ('5600H') THEN '5600_Nodes'
WHEN (VPROCTYPE1=AMP AND NodeType IN ('5555H') THEN '5555_Nodes'
WHEN (VPROCTYPE1=AMP AND NodeType NOT IN ('5600H, 5555H) THEN '5550_Nodes'
ELSE 'PEonly'
END,

2.7.3 Mem Fields Reporting in KB


Linux MemTextPageReads, MemCtxtPageReads, and MemCtxtPageWrite fields have 4KB data units
instead of I/O counts as in MP-RAS. This required changes to the following views and macros:

ViewResGeneralInfo
ResNode
ResOneNode
ResNodeByNode
ResNodeByGroup
ResMemMgmtOneNode
ResMemMgmtByNode
ResMemByGroup

Page 14

Resource Usage Porting Guide

The calculated values were modified in the view that used these fields so that all the fields in the
calculation use the same data units. The data units used are now 1KB values, so instead of calculating
the number of I/Os the results report the number of KBs read or written. The calculated values affected
by this change are:
Deleted
LogicalDeviceReads
LogicalDeviceWrites
LogicalDeviceIO
PageOrSwapIO
NetChannelSR (has been obsolete)

New or Changed
LogicalDeviceReadKB
LogicalDeviceWriteKB
LogicalDeviceIOKB
PageOrSwapIOKB

The ResUsage reporting macros that used these fields were also changed to report based on KBs of I/O
traffic instead of the number of reads and writes.
The ResNode* report columns that are affected by this change are:
Ldv Eff %
updated: Parallel efficiency of the logical device I/Os
Ldv IO KBs/Sec
Old: Average number of logical device I/Os per sec
New: Average number of logical device I/O KBs per sec
P+S %of IO KBs
Old: Pct logical device I/Os done for paging
New: Percent logical device I/O KBs done for paging
Read % of IO KBs
Old: Percent of logical device I/Os that were reads
New: Percent of logical device I/O KBs that were reads
LDV KB/IO
Old: Avg. size of a logical device read or write
New: Avg. size of non-swap/page logical device read or write
Deleted: Pct tot ldev I/Os that were dsk segs
Same as 100%-paging% column
The ResMem* report columns that are affected by this change are:
Page Read KBs/Sec
Old: Average number paged out page reads per second
New: Average number paged out page read KBs per second
Page+Swap Read KBs/Sec
Old: Avg tot num of pages/swapped-page/segment reads per sec
New: Avg tot num of pages/swapped-page/segment read KBs per sec

Page 15

Resource Usage Porting Guide

P+S IO KB %
Old: Pct tot logical device I/O that were paging/swapping I/O
New: Pct logical device I/O KBs done for paging/swapping I/O

2.8 Timestamp Housekeeping Field Added to All


Tables
DBQL logs data with the standard UNIX timestamp as the reference time field, but ResUsage tables are
logged with thedate and thetime fields. This makes it hard for applications that combine the data from
both sources to align the data.
This change adds TheTimeStamp housekeeping field to all the tables. TheTimeStamp field contains the
number of seconds since Midnight, Jan 1, 1970.

2.9 Field Changes for All Tables


This section identifies all the RSS field changes between Teradata Database 13.10 and Teradata
Database 14.0.
2.9.1 Ipma Table
-------------------------------------------------------------Housekeeping field changes:
-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact
to end user.
NetBlockQueue removed Sum suffix and changed to track field
Spare field usage section states:
If required, the type of the Spare fields can be changed to one of
{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
Spare05

count
count
count
count
count
count

Replaced existing Spare fields

Page 16

Resource Usage Porting Guide

Spare06
Spare07
Spare08
Spare09
SpareInt

count
count
count
count
count

-------------------------------------------------------------Added fields
-------------------------------------------------------------RssInternal00
track All RssInternal fields are reserved
RssInternal01
track
RssInternal02
track
RssInternal03
track
RssInternal04
track
RssInternal05
track
RssInternal06
track
RssInternal07
count
RssInternal08
count
RssInternal09
max
RssInternal10
count
RssInternal11
count
RssInternal12
max
RssInternal13
count
RssInternal14
count
RssInternal15
max
RssInternal16
count
RssInternal17
count
RssInternal18
count
RssInternal19
count
-------------------------------------------------------------Removed fields
-------------------------------------------------------------CpuProcSameSwitches
ProcNetInts
IOPtoCPUInts
ProcDiskInts
ProcHostInts
ProcLanInts
ProcCPUClockInts
ProcInterCPUInts
MemTextDestroys
NetSemPages
NetGroupPages
NetChanPages
NetMrgPages
NetMrgHeapPages
NetMrgSpoolPages
NetProtocolFilter
NetTxCircHPPtP
NetTxCircHPBrd
NetTxCircPtP
NetTxCircBrd
NetTxKBPtP
NetTxKBBrd
NetRxCircPtP
NetRxCircBrd

Page 17

Resource Usage Porting Guide

NetRxKBPtP
NetRxKBBrd
NetBackoffs
NetBackOffExhausted
NetBrdWindowError
NetConfigurations
NetTxSoftBackoffs
NetRxSoftBackoffs
LockEnters
LockBlocks
CacheAccess
CacheMiss
CacheWrites
CacheWriteThrus
CacheWriteBacks

2.9.2 Scpu Table


-------------------------------------------------------------Housekeeping field changes:
-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
cpuid
short
was ushort (unsigned short)
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact
to end user.
Spare field usage section states:
If required, the type of the Spare fields can be changed to one of
{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
SpareInt

count
count
count
count
count
count

Replaced existing Spare fields

-------------------------------------------------------------Added fields
-------------------------------------------------------------<none>
-------------------------------------------------------------Removed fields
-------------------------------------------------------------CPUProcSwitches
CPUProcSameSwitches

Page 18

Resource Usage Porting Guide

2.9.3 Sldv Table


-------------------------------------------------------------Housekeeping field changes:
-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
vprid
removed
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact
to end user.
Spare field usage section states:
If required, the type of the Spare fields can be changed to one of
{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
SpareInt

count
count
count
count
count
count

Replaced existing Spare fields

-------------------------------------------------------------Added fields
-------------------------------------------------------------LdvOutReqDiv
count
Used to divide LdvOutReqSum to get LdvOutReqAvg
-------------------------------------------------------------Removed fields
-------------------------------------------------------------LdvConcurrentMax
LdvOutReqMax

2.9.4 Spma Table


-------------------------------------------------------------Housekeeping field changes:
-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact

Page 19

Resource Usage Porting Guide

NetSemInUse
NetChanInUse
NetGroupInUse

to end user.
Dropped the Sum suffix and changed to track
Dropped the Sum suffix and changed to track
Dropped the Sum suffix and changed to track

ProcReady
track
ProcBlocked
track
ProcPendMemAlloc
ProcPendFsgRead
ProcPendFsgWrite
ProcPendNetThrottle
ProcPendNetRead
ProcPendMonitor
ProcPendMonResume
ProcPendDBLock
ProcPendSegLock
ProcPendMisc
ProcPendFsgLock
ProcPendQnl
MemVprAllocKB
NetBackoffs
AwtFlowControlled
AwtInuse
TvsReadCnt
TvsWriteCnt
TvsReadRespTot
TvsWriteRespTot

Dropped the Sum suffix


Dropped the Sum suffix
Changed to track
Changed to track
Changed to track
Changed to track
Changed to track
Changed to track
Changed to track
Changed to track
Changed to track
Changed to track
Changed to track
Changed to track
Changed to track
renamed from NetCircBackoffs
Changed to track
Changed to track
Renamed
Renamed
Renamed
Renamed

from
from
from
from

Vss
Vss
Vss
Vss

to
to
to
to

Tvs
Tvs
Tvs
Tvs

Spare field usage section states:


If required, the type of the Spare fields can be changed to one of
{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
Spare05
Spare06
Spare07
Spare08
Spare09
Spare10
Spare11
Spare12
Spare13
Spare14
Spare15
Spare16
Spare17
Spare18
Spare19
SpareInt

count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count

Replaced existing Spare fields

--------------------------------------------------------------

Page 20

Resource Usage Porting Guide

Added fields
-------------------------------------------------------------FileAcqsOther count
FileAcqOtherKB count
FileRelsOther count
FileRelOtherKB count
TvsReadRespMax max
TvsWriteRespMax max
-------------------------------------------------------------Removed fields
-------------------------------------------------------------ProcSuspendedSum
ProcRunningSum
CPUIdleNorm
CPUIoWaitNorm
CPUUServNorm
CPUUExecNorm
MemTextAllocs
MemVprAllocs
MemTSysOhRes
MemDSysOhRes
MemTextRes
MemCtxtRes
MemPDbKBRes
MemPCiKBRes
MemSDbKBRes
MemSCiKBRes
MemTJtKBRes
MemAPtKBRes
MemFails
MemAgings
MemTextPageDrops
MemProcSwapped
MemSwapDrops
MemSwapDropKB
MemSwapReads
MemSwapReadKB
NetCircAttempts
CmdStmtsInProgCur
CmdStmtTime

2.9.5 Svpr Table


-------------------------------------------------------------Housekeeping field changes:
-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact

Page 21

Resource Usage Porting Guide

to end user.
ProcPendDBLock changed to track
MsgWorkQLen
track Dropped the Sum suffix
Spare field usage section states:
If required, the type of the Spare fields can be changed to one of
{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
Spare05
Spare06
Spare07
Spare08
Spare09
Spare10
Spare11
Spare12
Spare13
Spare14
Spare15
Spare16
Spare17
Spare18
Spare19
SpareInt

count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count

Replaced existing Spare fields

-------------------------------------------------------------Added fields
-------------------------------------------------------------UdfAmpServ
count
UdfAmpExec
count
UdfPeServ
count
UdfPeExec
count
FilePDbAcqsOther
count
FilePCiAcqsOther
count
FileSDbAcqsOther
count
FileSCiAcqsOther
count
FileTJtAcqsOther
count
FileAPtAcqsOther
count
FilePDbAcqOtherKB
count
FilePCiAcqOtherKB
count
FileSDbAcqOtherKB
count
FileSCiAcqOtherKB
count
FileTJtAcqOtherKB
count
FileAPtAcqOtherKB
count
FilePDbRelsOther
count
FilePCiRelsOther
count
FileSDbRelsOther
count
FileSCiRelsOther
count
FileTJtRelsOther
count
FileAPtRelsOther
count

Page 22

Resource Usage Porting Guide

FilePDbRelOtherKB
count
FilePCiRelOtherKB
count
FileSDbRelOtherKB
count
FileSCiRelOtherKB
count
FileTJtRelOtherKB
count
FileAPtRelOtherKB
count
DBMergeTried
count
DBMergeDone
count
DBMergeElim
count
DBMergeExtraIO
count
FileACPCylsSkipped count
FileACPCylsMigr
count
FileACPCylsUnFSEOnly count
FileACPCylsPostponed count
/* 14.0 Block Level Compression (BLC) fields */
FileCompDBs
count
FileUnCompDBs
count
FileCompFerretDBs
count
FileUnCompFerretDBs count
FileCompTempDBs
count
FileUncompTempDBs
count
FileCompCylMigrs
count
FileUnCompCylMigrs count
FilePreCompMB
count
FilePostCompMB
count
FilePreUnCompMB
count
FilePostUnCompMB
count
FileCompCPU
count
FileUnCompCPU
count
FileTempCPU
count
FsgCacheWaits
count
FsgCacheWaitTime
count
FsgCacheWaitTimeMax
max
-------------------------------------------------------------Removed fields
-------------------------------------------------------------MemPDbAllocs
MemPCiAllocs
MemSDbAllocs
MemSCiAllocs
MemTJtAllocs
MemAPtAllocs
MemPDbAllocKB
MemPCiAllocKB
MemSDbAllocKB
MemSCiAllocKB
MemTJtAllocKB
MemAPtAllocKB
MemCtxtRes
MemPKBResFrz
MemCtxtPageReads
MemCtxtPageWrites
MemSwapDrops
MemSwapDropKB
MemSwapReads
MemSwapReadKB

Page 23

Resource Usage Porting Guide

DBLockBlocksMax
DBLocksHeldMax
DBLockBlocksSum
DBLocksHeldSum
IoGapMax

Page 24

Resource Usage Porting Guide

2.9.6 Ivpr Table


-------------------------------------------------------------Housekeeping field changes:
-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact
to end user.
Spare field usage section states:
If required, the type of the Spare fields can be changed to one of
{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
Spare05
Spare06
Spare07
Spare08
Spare09
SpareInt

count
count
count
count
count
count
count
count
count
count
count

Replaced existing Spare fields

-------------------------------------------------------------Added fields
-------------------------------------------------------------<none>
-------------------------------------------------------------Removed fields
-------------------------------------------------------------ProcWorkType0Sum ... ProcWorkType15Sum
ProcWorkType0Max ... ProcWorkType15Max
MonDeadlocks

2.9.7 Shst Table


-------------------------------------------------------------Housekeeping field changes:
-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed

Page 25

Resource Usage Porting Guide

-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact
to end user.
Spare field usage section states:
If required, the type of the Spare fields can be changed to one of
{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
Spare05
Spare06
Spare07
Spare08
Spare09
SpareInt

count
count
count
count
count
count
count
count
count
count
count

Replaced existing Spare fields

-------------------------------------------------------------Added fields
-------------------------------------------------------------<none>
-------------------------------------------------------------Removed fields
-------------------------------------------------------------HostQLenSum
HostQLenMax
CmdMiscUtilityStmts
CmdStmtsInProgCur
CmdStmtsInProgMax
CmdStmtsInProgSum
CmdStmtTime

2.9.8 Spdsk Table


-------------------------------------------------------------Housekeeping field changes:
-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact
to end user.
Spare field usage section states:

Page 26

Resource Usage Porting Guide

If required, the type of the Spare fields can be changed to one of


{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
Spare05
Spare06
Spare07
Spare08
Spare09
Spare10
Spare11
Spare12
Spare13
Spare14
Spare15
Spare16
Spare17
Spare18
Spare19
SpareInt

count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count

Replaced existing Spare fields

-------------------------------------------------------------Added fields
-------------------------------------------------------------<none>
-------------------------------------------------------------Removed fields
-------------------------------------------------------------OutReqTime

2.9.9 Svdsk Table


-------------------------------------------------------------Housekeeping field changes:
-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact
to end user.
Spare field usage section states:
If required, the type of the Spare fields can be changed to one of
{count|min|max|track}

Page 27

Resource Usage Porting Guide

Spare00
Spare01
Spare02
Spare03
Spare04
Spare05
Spare06
Spare07
Spare08
Spare09
Spare10
Spare11
Spare12
Spare13
Spare14
Spare15
Spare16
Spare17
Spare18
Spare19
SpareInt

count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count

Replaced existing Spare fields

-------------------------------------------------------------Added fields
-------------------------------------------------------------<none>
-------------------------------------------------------------Removed fields
-------------------------------------------------------------<none>

2.9.10

Sawt Table

-------------------------------------------------------------Housekeeping field changes:


-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
NodeID
renamed from NodeId (cap D to match other tables)
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact
to end user.
Available
AvailableMin
MailBoxDepth
WorkTypeInuse00...15

track
min

/* was sparecount02 */
/* was sparecount03 */

changed to track
changed to track

Spare field usage section states:

Page 28

Resource Usage Porting Guide

If required, the type of the Spare fields can be changed to one of


{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
Spare05
Spare06
Spare07
Spare08
Spare09
Spare10
Spare11
Spare12
Spare13
Spare14
Spare15
Spare16
Spare17
Spare18
Spare19
SpareInt

count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count

Replaced existing Spare fields

-------------------------------------------------------------Added fields
-------------------------------------------------------------AwtLimit
track
-------------------------------------------------------------Removed fields
-------------------------------------------------------------<none>

2.9.11

Sps Table

-------------------------------------------------------------Housekeeping field changes:


-------------------------------------------------------------TheTimestamp
long
added
CodFactor
short
renamed from spare field
CollectIntervals
removed
NodeID
renamed from NodeId (cap D to match other tables)
VprId
removed
SummaryFlag
removed
RowIndex1
renamed from PGid
/* RowIndex1 = SLES10:PGid, SLES11:pWDid (Priority Scheduler WDid) */
AMPcount
short
added
-------------------------------------------------------------Changed fields
-------------------------------------------------------------Active
changed to max field. Internal data management issue with no impact
to end user.

Page 29

Resource Usage Porting Guide

NumTasks
was called NumProcs
ActiveSessions was called NumSets
/* converted spare fields */
WorkMsgSendDelay
count
WorkMsgSendDelayMax
max
WorkMsgReceiveDelay
count
WorkMsgReceiveDelayMax max
WorkTimeInuse
count
WorkTimeInuseMax
max
AwtReleases
count
WorkMsgSendDelayCnt
count
WorkMsgReceiveDelayCnt count
Spare field usage section states:
If required, the type of the Spare fields can be changed to one of
{count|min|max|track}
Spare00
Spare01
Spare02
Spare03
Spare04
Spare05
Spare06
Spare07
Spare08
Spare09
Spare10
Spare11
Spare12
Spare13
Spare14
Spare15
Spare16
Spare17
Spare18
Spare19
SpareInt

count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count
count

Replaced existing Spare fields

-------------------------------------------------------------Added fields
-------------------------------------------------------------VPid
track
WorkMsgReceiveDelayCntMax max
WaitIO
count
WaitOther
count
CPURunDelay
count
IOSubmitted
count
IOCompleted
count
IOCriticalSubmitted
count
IOSubmittedKB
count
IOCompletedKB
count
IOCriticalSubmittedKB
count
DecayLevel1IO
count

Page 30

Resource Usage Porting Guide

DecayLevel2IO
DecayLevel1CPU
DecayLevel2CPU
TacticalExceptionIO
TacticalExceptionCPU

count
count
count
count
count

-------------------------------------------------------------Removed fields
-------------------------------------------------------------CpuTime
QLength
QLengthMax
CPUUServPars
CPUUExecPars
FileFcrRequests
FileFcrRequestsAdaptive
FileFcrBlocksRead
FileFcrBlocksDeniedUser
FileFcrBlocksDeniedKern
FileFcrBlocksDeniedCache
FileFcrBlocksDeniedThreshUser
FileFcrDeniedUser
FileFcrDeniedKern
FileFcrDeniedCache
FileFcrDeniedThreshUser
MsgChnLastDone
MemCtxtAllocs
MemKBRes
FlowControlled
FlowCtlCnt
FileCylMigrs
FileCylAllocs
FileSyncScans
FileSyncSubtables
FileSyncScanners
FileSyncGroups
AllocatorExtentAllocReqs
AllocatorExtentFreeReqs
AllocatorMapIOsStarted
AllocatorMapIOsDone
NodeAgentMigrationsStarted
NodeAgentMigrationsDone
NodeAgentStatProcessed
ReadsHot
ReadsWarm
ReadsCold
WritesHot
WritesWarm
WritesCold
FileWCylAllocs
FileWCylFrees

Page 31

Resource Usage Porting Guide

Appendix A: Glossary
OPNPDE

Open Parallel Database Extension

PMPC

Performance Monitor and Production Control

ResUsage

Database tables that contain RSS data that has been logged during system operation.
Also may refer to the SQL macros that can be used to view the ResUsage data.

RSS

Resource Sampling Subsystem collects performance related data for hardware and
software involved in the operation of the database.

SLES10

SUSE Linux Enterprise Server release 10 is an operating system from Novell

SLES11

SUSE Linux Enterprise Server release 11 is an operating system from Novell

TDWM

Teradata Database Workload Management

WDid

Workload Definition identifier.

Page 32

Resource Usage Porting Guide

Page 33

You might also like