15.00 - Chapter 4 AWT Monitor (awtmon) - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
15.00
Content Type
Configuration
Publication ID
B035-1102-015K
Language
English (United States)
Last Update
2018-09-25

The AWT Monitor utility, awtmon, collects and displays a user-friendly summary of the AMP Worker Task (AWT) in-use count snapshots for the local node or all nodes in the Teradata Database system. This information is useful for debugging purposes, including hot-AMP conditions.

Scenarios Runs From

  • Database Window or comparable interface to the Teradata Database console subsystem, such as cnsterm
  • Linux command line
  • For general information on starting the utilities from different interfaces, see Appendix B: “Starting the Utilities”

    Scenarios Syntax

     

    Syntax element …

    Specifies …

    -h

    the awtmon online help.

    -d

    debug mode.

    -s

    to display system-wide AWT in-use count snapshots.

    -S amp_cnt

    to display AWT in-use count snapshots in summary format if the total number of AMP count (to be printed) is greater than or equal to amp_cnt. By default, the -S option is enabled with 24. For a system-wide AWT in-use count snapshots display (the -s option), amp_cnt is a total AMP count from all TPA nodes.

    - t threshold

    to display the AMP # and AWT in-use count snapshots if the AWT in-use count is greater than or equal to threshold. The default is 1.

    t n

    to display AWT in-use count snapshots in a loop. awtmon samples the AWT in-use counters for n iterations in t-second intervals. The default value for n is 2.

    Scenarios Usage Notes

    By default, awtmon displays the AWT in-use count snapshots on the local node. When you use the -s option, awtmon gathers and displays system-wide AWT in-use count snapshots in summary output mode on a large system to reduce overall output size. Teradata recommends to use the -s and -t options together on a large system to filter out the output size. This allows you to locate any hot AMPs or nodes in the system. Once the hot AMPs or nodes are identified, you can then run awtmon on them.

    The AMP Load utility (ampload) and the AWT Monitor utility (awtmon) provide some similar information. The following table describes the differences between these utilities.

     

    ampload

    awtmon

    Prints AWT INUSE count only.

    Prints the AWT INUSE count by work type, that is, WORKNEW, WORKONE, and so on.

    Knowing the work type for active AWTs helps to troubleshoot performance problems, specifically finding hot AMPs per node.

  • Displays only local node information when invoked from a command prompt window.
  • Prints only system-wide information when invoked from the CNS/DBW supervisor window.
  • Prints local node AWT INUSE count information by default and prints system-wide information with the [-s] option for pcl.

    Returns the data once. It does not provide a loop mode. You must manually submit the ampload command repeatedly if you wish to collect several reports for comparison.

    Provides [t [n]] options for a loop mode.

    Reports the vproc number, node ID number, message count, and AWT availability count for each vproc across the entire system.

    Provides the [-t count] option to filter the output to report only vprocs where the AWT in-use count is less than a number you specify.

    Prints a line for each vproc, even when the AWT in-use count is zero.

    Does not print a line if the AWT in-use count is zero.

    Shows how many messages are waiting on the AMP.

    Does not report the number of messages waiting on the AMP. Displays only a summary of the AWT in-use count snapshots for the local node or all nodes in the Teradata Database system.

    Scenarios Examples

    Example  

    To display all AWT in-use count snapshots on a local node, type the following:

    awtmon

    The following displays:

    Amp 1   : Inuse: 62:  NEW: 50 ONE: 12
    Amp 4   : Inuse: 62:  NEW: 50 ONE: 12
    Amp 7   : Inuse: 62:  NEW: 50 ONE: 12
    Amp 10  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 13  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 16  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 19  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 22  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 25  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 28  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 31  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 34  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 37  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 40  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 43  : Inuse: 62:  NEW: 50 ONE: 12
    Amp 46  : Inuse: 62:  NEW: 50 ONE: 12

    Example  

    To display all AWT in-use count snapshots on a local node with a three-loop count in a two-second sleep interval, type the following:

    awtmon 2 3

    The following displays:

    ====> Mon Jan 24 11:36:45 2005 <=====
    LOOP_0: Amp 2000: Inuse: 31:  NEW: 17 ONE: 14
    LOOP_0: Amp 2007: Inuse: 32:  NEW: 17 ONE: 15
    LOOP_0: Amp 2008: Inuse: 31:  NEW: 17 ONE: 14
    LOOP_0: Amp 2015: Inuse: 34:  NEW: 19 ONE: 15
    LOOP_0: Amp 2016: Inuse: 32:  NEW: 18 ONE: 14
    LOOP_0: Amp 2023: Inuse: 33:  NEW: 19 ONE: 14
    LOOP_0: Amp 2024: Inuse: 31:  NEW: 17 ONE: 14
    LOOP_0: Amp 2031: Inuse: 31:  NEW: 17 ONE: 14
    LOOP_0: Amp 2032: Inuse: 31:  NEW: 17 ONE: 14
    LOOP_0: Amp 2039: Inuse: 32:  NEW: 17 ONE: 15
    ====> Mon Jan 24 11:36:47 2005 <=====
    LOOP_1: Amp 2000: Inuse: 36:  NEW: 17 ONE: 19
    LOOP_1: Amp 2007: Inuse: 36:  NEW: 16 ONE: 20
    LOOP_1: Amp 2008: Inuse: 36:  NEW: 17 ONE: 19
    LOOP_1: Amp 2015: Inuse: 36:  NEW: 16 ONE: 20
    LOOP_1: Amp 2016: Inuse: 35:  NEW: 16 ONE: 19
    LOOP_1: Amp 2023: Inuse: 36:  NEW: 17 ONE: 19
    LOOP_1: Amp 2024: Inuse: 35:  NEW: 16 ONE: 19
    LOOP_1: Amp 2031: Inuse: 35:  NEW: 16 ONE: 19
    LOOP_1: Amp 2032: Inuse: 35:  NEW: 16 ONE: 19
    LOOP_1: Amp 2039: Inuse: 36:  NEW: 16 ONE: 20
    ====> Mon Jan 24 11:36:49 2005 <====
    LOOP_2: Amp 2000: Inuse: 35:  NEW: 16 ONE: 19
    LOOP_2: Amp 2007: Inuse: 37:  NEW: 17 ONE: 20
    LOOP_2: Amp 2008: Inuse: 36:  NEW: 17 ONE: 19
    LOOP_2: Amp 2015: Inuse: 38:  NEW: 17 ONE: 21
    LOOP_2: Amp 2016: Inuse: 37:  NEW: 17 ONE: 20
    LOOP_2: Amp 2023: Inuse: 37:  NEW: 17 ONE: 20
    LOOP_2: Amp 2024: Inuse: 37:  NEW: 17 ONE: 20
    LOOP_2: Amp 2031: Inuse: 38:  NEW: 18 ONE: 20
    LOOP_2: Amp 2032: Inuse: 37:  NEW: 17 ONE: 20
    LOOP_2: Amp 2039: Inuse: 38:  NEW: 17 ONE: 21

    Example  

    To display AWT in-use count snapshots greater than or equal to 60 on a local node with a three-loop count in a two-second interval, type the following:

    awtmon -t 60 2 3

    The following displays:

    ====> Tue Dec 16 08:55:49 2003 <====
    LOOP_0: Amp 17  : Inuse: 62:  NEW: 49 ONE: 13
    LOOP_0: Amp 24  : Inuse: 62:  NEW: 47 ONE: 15
    LOOP_0: Amp 29  : Inuse: 60:  NEW: 50 ONE: 10
    LOOP_0: Amp 30  : Inuse: 60:  NEW: 50 ONE: 10
    LOOP_0: Amp 42  : Inuse: 62:  NEW: 48 ONE: 14
    ====> Tue Dec 16 08:55:52 2003 <====
    LOOP_1: Amp 0   : Inuse: 60:  FOUR:  1 NEW: 50 ONE:  9
    LOOP_1: Amp 6   : Inuse: 60:  NEW: 50 ONE: 10
    LOOP_1: Amp 17  : Inuse: 62:  NEW: 48 ONE: 14
    LOOP_1: Amp 24  : Inuse: 62:  NEW: 46 ONE: 16
    LOOP_1: Amp 29  : Inuse: 62:  NEW: 50 ONE: 12
    LOOP_1: Amp 30  : Inuse: 62:  NEW: 50 ONE: 12
    LOOP_1: Amp 35  : Inuse: 60:  NEW: 50 ONE: 10
    LOOP_1: Amp 36  : Inuse: 60:  NEW: 50 ONE: 10
    LOOP_1: Amp 42  : Inuse: 62:  NEW: 48 ONE: 14
    ====> Tue Dec 16 08:55:54 2003 <====
    LOOP_2: Amp 0   : Inuse: 60:  FOUR:  1 NEW: 50 ONE:  9
    LOOP_2: Amp 6   : Inuse: 60:  NEW: 50 ONE: 10
    LOOP_2: Amp 17  : Inuse: 62:  NEW: 48 ONE: 14
    LOOP_2: Amp 24  : Inuse: 62:  NEW: 46 ONE: 16
    LOOP_2: Amp 29  : Inuse: 62:  NEW: 50 ONE: 12
    LOOP_2: Amp 30  : Inuse: 62:  NEW: 50 ONE: 12
    LOOP_2: Amp 35  : Inuse: 60:  NEW: 50 ONE: 10
    LOOP_2: Amp 36  : Inuse: 60:  NEW: 50 ONE: 10
    LOOP_2: Amp 42  : Inuse: 62:  NEW: 47 ONE: 15

    Note: In-use count snapshots less than 60 are skipped.

    Example  

    To display AWT in-use count snapshots greater than or equal to 50 in a summary format with a three-loop count in a two-second sleep interval, type the following:

    awtmon -S 8 -t 50 2 3

    The following displays:

    ====> Tue Dec 16 08:53:44 2003 <====
    LOOP_0: Inuse: 55 : Amps: 5,6,11,12,17,18,23,29,30,35,36,41,42
    LOOP_0: Inuse: 56 : Amps: 0,47
    LOOP_0: Inuse: 57 : Amps: 24
    ====> Tue Dec 16 08:53:47 2003 <====
    LOOP_1: Inuse: 54 : Amps: 5,6,11,12,17,18,23,29,30,35,36,41,42
    LOOP_1: Inuse: 55 : Amps: 0,47
    LOOP_1: Inuse: 56 : Amps: 24
    ====> Tue Dec 16 08:53:49 2003 <====
    LOOP_2: Inuse: 54 : Amps: 5,11,12,17,18,23,29,30,35,36,41,42
    LOOP_2: Inuse: 55 : Amps: 0,6,47
    LOOP_2: Inuse: 56 : Amps: 24

    Example  

    To display system-wide AWT in-use count snapshots greater than or equal to 50 in a summary format, type the following:

    awtmon -s -t 50

    The following displays:

    ====> Tue Dec 16 08:58:07 2003 <====
    byn001-4: LOOP_0: Inuse: 57 : Amps: 17,42
    byn001-4: LOOP_0: Inuse: 58 : Amps: 5,11,12,35,41
    byn001-4: LOOP_0: Inuse: 59 : Amps: 30
    byn001-4: LOOP_0: Inuse: 60 : Amps: 23,36
    byn001-4: LOOP_0: Inuse: 62 : Amps: 0
    byn001-4: LOOP_0: Inuse: 63 : Amps: 6,18,24,29,47
    byn001-5: LOOP_0: Inuse: 52 : Amps: 16,22
    byn001-5: LOOP_0: Inuse: 53 : Amps: 28
    byn001-5: LOOP_0: Inuse: 55 : Amps: 7,34,46
    byn001-5: LOOP_0: Inuse: 56 : Amps: 10,13,19,43
    byn001-5: LOOP_0: Inuse: 57 : Amps: 1,25,31,37,40
    byn001-5: LOOP_0: Inuse: 62 : Amps: 4
    byn002-5: LOOP_0: Inuse: 52 : Amps: 2,3,14,15,21,27,32,33,38,45
    byn002-5: LOOP_0: Inuse: 53 : Amps: 9,20,39,44