16.10 - MonSesCPUNormalization - Teradata Database

Teradata Database Utilities
Product
Teradata Database
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
zll1480972831047.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval
dita:id
vkz1472241255652

Purpose

Controls whether normalized or non-normalized statistical CPU data is reported in the responses to workload management API calls. API calls that return CPU data include MONITOR SESSION (PM/API), MonitorSession (open API), and MonitorMySessions (open API).

“Coexistent” Teradata Database systems combine different types of node hardware that might use different types of CPUs running at different speeds. CPU normalization adjusts for these differences when calculating statistics across the system. Although normalized CPU data is used in other areas of the system, such as DBQL and AMPusage, this field affects only the CPU data reported by PM/API and open API calls.

Field Group

General

Valid Settings

Setting Effect
TRUE CPU statistical data is normalized.

If dynamic workload management is enabled, asynchronous and synchronous exception detection on CPU thresholds are performed using normalized CPU values.

Workload management can be enabled from the Viewpoint Workload Designer portlet.

There is no measurable overhead associated with setting this field to TRUE.
FALSE CPU statistical data is not normalized.

If dynamic workload management is enabled, asynchronous and synchronous exception detection on CPU thresholds are performed using normalized CPU values.

Workload management can be enabled from the Viewpoint Workload Designer portlet.

Default

FALSE

Changes Take Effect

After the DBS Control Record has been written.

Changing the Setting

  1. Disable Teradata dynamic workload management software Workload Definition (Category 3) rules, if they are enabled, using the Teradata Viewpoint Workload Designer portlet.

    Teradata dynamic workload management workloads are affected by MonSesCPUNormalization because they use the MONITOR SESSION PM/API call to obtain CPU information.

  2. Adjust any CPU-related exception thresholds associated with the workloads to account for the change in CPU data normalization.
  3. Disable session monitoring from Database Window, using the SET SESSION COLLECTION command.
  4. Change the MonSesCPUNormalization field in DBS Control.
  5. Re-enable session monitoring.
  6. Re-enable workload definition rules in the Teradata Viewpoint Workload Designer portlet.

The AMPCPUSec field in the response to workload management API calls contains accumulated CPU seconds for all requests in the session. If the value of MonSesCPUNormalization changes in the middle of a session, AMPCPUSec will no longer be valid during the current session, and will return -1 in record mode, or NULL in indicator mode. All other CPU fields are valid, even if MonSesCPUNormalization changes in the middle of a session.

Related Topics

For more information about Teradata Database APIs, see:

  • Application Programming Reference.
  • Database Administration.