15.00 - GET CONFIG - 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

GET CONFIG

Purpose  

Returns the current system configuration.

Syntax  

Usage Notes  

The following table defines the system configuration.

 

Component

Description

Vproc Number

Uniquely identifies the vproc across the entire system.

Rel. Vproc#

Represents the number of the vproc relative to the node upon which the vproc resides.

Node ID

Identifies the node upon which the vproc resides. Node ID is formatted as CCC-MM, where CCC denotes the cabinet number and MM denotes the module number. For example, the node ID 003-07 identifies the node in module number 7 of cabinet 3.

Movable

Indicates whether the vproc can be migrated to another node in its defined clique if its primary node fails.

Crash Count

Represents the number of times the vproc has crashed. The count increments with every attempted system restart. When the system restart succeeds, Crash Count is reset to 0 for all vprocs.

Vproc State

Represents the current PDE system state of a vproc.

  • FATAL: Indicates a serious problem with a vproc and/or its associated storage. For example, if a vproc crashes repeatedly, the number of crashes might have exceeded the allowable crash count, or if there are corrupt tables on the vdisk that require a Table Rebuild of some (or all) of the tables, a vproc is set to the FATAL state.
  • Note: When a TVS vproc is in FATAL state, all AMPs associated with it will be put into FATAL state at the next database restart.

  • FATAL**: Indicates an AMP cannot access its storage.
  • Note: The AMP partition is not started for a vproc in this state.

  • NEWPROC: Applies only to AMP and PE vprocs. It indicates that either a new vproc is added into the Teradata database configuration or an existing vproc is deleted.
  • A vproc with a status of NEWPROC is a member of the PDE message groups but is not a member of the operational Teradata database message group. For more information, contact the Teradata Support Center.

  • NONODE: Indicates that the physical hardware required to run this vproc is not available. This state is not accepted as an argument to the SET command, although this state might appear in the Vproc Status Table produced by the STATUS command.
  • Note: The AMP or PE partitions are not started for a vproc in this state.

  • NULL: Undefined. It is not accepted as an argument to the SET command, although this state might appear in the Vproc Status Table produced by the STATUS command.
  • OFFLINE: Generally, indicates vprocs that are not fully operational and have been forced down by the Teradata database or system administrator.
  • A vproc with status OFFLINE is a member of the PDE message group but is not a member of the operational Teradata Database message group. For more information, contact the Teradata Support Center.

    When a TVS vproc is in OFFLINE state, all AMPs associated with it will be put into FATAL state.

  • ONLINE: Indicates that the vproc is fully operational and actively participating with the Teradata database.
  • A vproc with status ONLINE is a member of both the PDE and Teradata Database message group. For more information, contact the Teradata Support Center.

  • UTILITY: Is transitional and is used by database recovery and the RECONFIG and Table Rebuild utilities to indicate that a previously OFFLINE/FATAL/NEWPROC is interacting with the online Teradata Database.
  • This vproc is a member of the PDE message groups but not a member of the operational Teradata Database message groups. A local crash of a UTILITY vproc causes a database restart.

    Config Status

    Displays the Teradata Database Logical Configuration Map Status of a vproc.

  • Online: The vproc is fully operational.
  • This status usually corresponds to ONLINE Vproc State.

  • Down: The vproc has been forced down.
  • This status usually corresponds to the OFFLINE, UTILITY, FATAL, and NONODE Vproc states.

  • Catchup: The Config Status for the AMP was Down and is being recovered in the background. If System RestartKind is COLDWAIT, the Config Status of the vproc becomes Online when recovery is complete.
  • This status usually corresponds to the UTILITY Vproc State.

  • Hold: The Config Status for the AMP was Catchup or Down and its data is being recovered. The Config Status of this vproc becomes Online when recovery is complete.
  • This status usually corresponds to the ONLINE Vproc State.

  • NewReady: This is either a newly added vproc or one that has been removed from the Teradata Database Logical Configuration.
  • This status usually corresponds to the UTILITY or NEWPROC Vproc State.

  • NewDown: A newly added vproc that is down. It has not yet been added into the DBS configuration with config or reconfig.
  • This status usually corresponds to the OFFLINE Vproc State.

  • Null: This vproc is not yet in the Teradata Database Logical Configuration. The vproc might have been added to the PDE Physical Configuration or deleted from the Teradata Database Logical Configuration, and Teradata Database Startup has not run. Startup notes that this vproc does not appear in the Startup configuration map and changes the Config Status of the vproc to NewReady.
  • This status usually corresponds to the NEWPROC Vproc State.

    Config Type

    Represents the Teradata Database Logical Configuration Map Type of a vproc.

    Cluster/
    Host No.

    Displays the Cluster Number if the Config Type is AMP or displays the Host No. if the Config Type is PE.

    Cluster is the cluster number for the AMP as defined using the Configuration Utility. The valid range of cluster numbers is 0 to 8099.

    Host No. is the host number that was assigned to the PE using the Configuration Utility. The valid range of host numbers is 1 to 1023.

    RcvJrnl/
    Host Type

    Displays the RcvJrnl (that is, Recovery Journaling) flag if the Config Type is AMP or the Host Type if the Config Type is PE.

    The RcvJrnl flag is Off if an AMP is down and the other AMPs in its cluster are not to create a recovery journal for the down AMP.

    Note: If you anticipate that an AMP will be down for a long period of time, Teradata recommends an offline rebuild of all tables on the AMP (after the RcvJrnl flag has been set to Off).

    The Host Type is the host type for the PE as defined using the Configuration Utility and IBM, COP, ATT3B, BULLHN, or OS1100.

    TVS Vproc

    For AMP vprocs, displays the associated TVS vproc.

    The following table defines the node configuration.

     

    Component

    Description

    Node ID

    Defined using PUT. See Parallel Upgrade (PUT) Tool Reference for more information. The node ID is formatted as CCC-MM, where CCC denotes the cabinet number and MM denotes the module number. For example, the node ID 003-07 identifies the node in module number 7 of cabinet 3.

    Node State

    The current state of the node, which is either ONLINE, DOWN, or STANDBY.

    Clique Number

    The clique number for the node as defined using PUT. See Parallel Upgrade (PUT) Tool Reference for more information.

    CPUs

    The number of CPUs on the node.

    Memory (MB)

    The total memory size in megabytes for the node (rounded up to the nearest integer).

    CHANs

    The number of channels attached to the node.

    LANs

    The number of LANs attached to the node.

    AMPs

    The number of AMPs running on the node.

    Node Name

    The network name for the node.

    When applicable, a footnote follows the PDE Status Table, indicating which node is defined as a Non-TPA Node (for nodes in STANDBY).

    Example  

    The following example shows the current system configuration.

    SYSTEM NAME: qpdt23                                         11/06/12 17:09:05
     
                              DBS LOGICAL CONFIGURATION
                              -------------------------
     
                                                                       Rcv
                                                                       Jrnl/
    Vproc  Rel.   Node    Can   Crash Vproc   Config   Config Cluster/ Host  TVS
    Number Vproc# ID      Move  Count State   Status   Type   Host No. Type  Vproc
    ------ ------ ------  ----- ----- ------- -------- ------ -------- ----- -----
        0*    1     1-01  Yes     0   ONLINE  Online    AMP       0    On    10238
        1     2     1-01  Yes     0   ONLINE  Online    AMP       0    On    10237
     8192     5     1-01  No      0   ONLINE  N/A       GTW       1    COP   N/A
    10237     6     1-01  Yes     0   ONLINE  N/A       TVS       0    N/A   N/A
    10238     7     1-01  Yes     0   ONLINE  N/A       TVS       0    N/A   N/A
    16382     3     1-01  Yes     0   ONLINE  Online    PE        1    COP   N/A
    16383     4     1-01  Yes     0   ONLINE  Online    PE        1    COP   N/A
    --------------------------------------------------------------------------------
    *   DBS Control AMP
     
      DBS State: Logons are enabled - The system is quiescent
     
      DBS RestartKind: COLD
     
                              PDE PHYSICAL CONFIGURATION
                              --------------------------
     
    Node    Node    Clique      Memory
    ID      State   Number CPUs  (MB)  CHANs LANs AMPs Node Name
    ------- ------- ------ ---- ------ ----- ---- ---- ---------------------------
      1-01  ONLINE     0     1   1337    0     1    2  localhost
    ------------------------------------------------------------------------------
     
     
      PDE State: RUN/STARTED