15.10 - Miscellaneous Housekeeping Columns - Teradata Database

• On SLES 10 or earlier systems, this column 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.
• On SLES 11 or later systems, this column is not valid and returns a zero value.

• On SLES 10 or earlier systems, this column contains the PGId.

  The PGId identifies the PG. There is a one to one mapping between a PG ID and a WD ID at any point in time.

  The mapping between PG ID and WD ID can be determined by looking at the Teradata Viewpoint Workload Designer portlet.

  The PG ID value ranges from 0 to 250, while the value of a WD ID is not in a specific range (that is, the value is incremented and not reused).

• On SLES 11 or later systems, this column contains the pWDid. The pWDid value ranges from 0 to 255.

  When running SLES 11 or later systems in the ResPs macro outputs, the RowIndex1 column displays as PGid, instead of pWDid. For sample outputs of the ResPs macros, see Resource Usage Macros.

The default PGs (System, L, M, H, R) have no associated WD and will have a WDID of zero in the table. Only PGs with a name that has “PGWL” (SLES 10) or “TDWMWD” (SLES 11 or higher) in it have a nonzero WDID.

Resource usages of the workload definition (WD) to which a job instance was assigned can be obtained by joining the DBC.DBQLUtilityTbl table and DBC.ResSPSView on the WDID column for the duration of the job instance.

The example below calculates the sums of IOTA (I/O token allocation) columns.

SELECT SUM(FullPotentialIota), SUM(CodPotentialIota), SUM(UsedIota)
FROM DBC.ResSpsView S,
     DBC.DBQLUtilityTbl U
WHERE S.WDID = U.WDID
  AND U.UtilityName = 'MULTLOAD'
  AND U.UserName = 'USER1'
  AND U.JobEndTime = TIMESTAMP '2013-04-19 16:48:14.98'
  AND S.TheDate >= CAST(Phase1StartTime AS DATE)
  AND S.TheTime >= ((EXTRACT(HOUR FROM Phase1StartTime) * 10000) +
                    (EXTRACT(MINUTE FROM Phase1StartTime) * 100) +
                    (EXTRACT(SECOND FROM Phase1StartTime)))
  AND S.TheDate <= CAST(Phase2EndTime AS DATE)
  AND S.TheTime <= ((EXTRACT(HOUR FROM Phase2EndTime) * 10000) +
                    (EXTRACT(MINUTE FROM Phase2EndTime) * 100) +
                    (EXTRACT(SECOND FROM Phase2EndTime)));

• 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.

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.

If Active is set to a non-zero value, the row contains data columns.

If Active is set to a zero value, none of the data columns in the row have been updated during the logging period.

This column is useful for aligning data with the DBQL log.

The value is set to 1000 if the PM CPU COD is disabled.

The value is set to 1000 if the WM CPU COD is disabled.

The value is set to 100 if the PM I/O COD is disabled.

The value is set to 100 if the WM I/O COD is disabled.