17.10 - Definitions of Terms Used in Vproc Manager - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Database Utilities

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Release Date
July 2021
Content Type
Configuration
Publication ID
B035-1102-171K
Language
English (United States)
The following terms apply to Vproc Manager:
  • VprocID

    A VprocID is a number that identifies the vproc to Vantage. VprocIDs are in the range of 0 through 16383, or 0 through 30719, depending on the system. When specifying VprocIDs, decimal or hexadecimal numbers can be used. Hexadecimal numbers must include a trailing X or x, for example, 3FFx and 77FFx.

    Vproc Number and Rel. Vproc # are two columns in the output of Vproc Manager STATUS command output displays. Where commands allow vproc numbers to be specified, use the absolute Vproc Number rather than the Rel. Vproc # number to identify a vproc.
  • VprocList

    A VprocList is defined as a list of one or more vproc identifiers or a range of vproc identifiers in the following format:

    { vprocid | vprocid TO vprocid } [[,]...]

    Examples:

    0 1 2 3
    0, 1, 16382 to 16383
    0 to 10, 16381, 16382
    0 to 1, 27FEx
  • VprocState

    VprocState defines the PDE system state of a vproc. VprocStates include the following:

    • FATAL

      This VprocState indicates a serious problem with a vproc or its associated storage. For example, if a vproc crashes repeatedly, or if there are corrupt tables that require a Table Rebuild, a vproc will be set to the FATAL state.

      When a TVS vproc is in FATAL state, all AMPs associated with it will be put into FATAL state at the next database restart.

      The AMP or PE partitions are not started for a vproc in this state.
    • FATAL*

      This VprocState indicates a lost I/O write.

    • FATAL**

      This VprocState indicates an I/O read issue.

    • NEWPROC

      This VprocState applies only to AMP and PE vprocs.

      This VprocState indicates that either a new vproc is being added to the database configuration or an existing vproc is being deleted.

      A vproc with status NEWPROC is a member of the PDE message group but is not a member of the operational database message group. For more information, contact the Teradata Support Center.

    • NONODE

      This VprocState 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.

      The AMP or PE partitions are not started for a vproc in this state.
    • NULL

      This VprocState is 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.

    • ONLINE

      This VprocState indicates that the vproc is fully operational and actively participating with the database.

      A vproc with status ONLINE is a member of both the PDE and database message group. For more information, contact the Teradata Support Center.

    • OFFLINE

      Generally, this VprocState indicates vprocs that are not fully operational and have been forced down by the DBA or system administrator.

      For example, if a node fails during system startup, its associated storage clique may be prevented from starting, and the AMPs that use that storage will be set to OFFLINE. This behavior is governed by settings in the Control GDO Editor (ctl) utility.

      A vproc with status OFFLINE is a member of the PDE message group but is not a member of the operational 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 at the next database restart.

    • UTILITY

      This vproc state applies only to AMP vprocs.

      This VprocState is transitional and is used by database recovery, reconfiguration, and the Table Rebuild utilities to indicate that a previously OFFLINE/FATAL/NEWPROC is interacting with the online database.

      This vproc is a member of the PDE message groups but not a member of the operational database message groups.

  • ConfigStatus

    The database component of Vantage maintains its own internal version of the status of AMP and PE vprocs. That status is called the Teradata Logical Configuration Status, and represented in the output of the Vproc Manager STATUS command as a column named ConfigStatus. Vproc Manager cannot modify the ConfigStatus of a vproc.

    ConfigStatus can be any of the following:

    To clearly differentiate between VprocStates and ConfigStatus, VprocStates here are written in all UPPERCASE letters, and ConfigStatus is written in mixed-case letters.
    • Online

      The vproc is fully operational.

      This usually coincides with the ONLINE VprocState.

    • Down

      The vproc has been forced down.

      This ConfigStatus usually coincides the OFFLINE, UTILITY, FATAL, and NONODE VprocStates.

    • Catchup

      This ConfigStatus for this vproc was previously Down, and it is being recovered in the background. If System RestartKind is COLDWAIT, the ConfigStatus of this vproc will become Online after recovery is complete.

      This ConfigStatus usually coincides with the UTILITY VprocState.

    • Hold

      The ConfigStatus for this vproc was previously Catchup or Down, and its data is in the process of being recovered. The ConfigStatus of this vproc will become Online after recovery is complete.

      This ConfigStatus usually coincides with the ONLINE VprocState.

    • NewReady

      This is either a newly added vproc or one that has been removed from the database logical configuration.

      This ConfigStatus usually coincides with the UTILITY or NEWPROC VprocState.

    • NewDown

      This is a newly added vproc and has been forced down.

      This ConfigStatus usually coincides with the NEWPROC VprocState.

    • Null

      This vproc is not yet in the Teradata Logical Configuration. Recently, the vproc might have been added to the PDE Physical Configuration or deleted from the Teradata Logical Configuration, and database startup has not run yet. Startup will note that this vproc does not appear in its configuration map and will change its ConfigStatus to NewReady. Null usually coincides with the NEWPROC VprocState.

    The following table illustrates each ConfigStatus and the VprocState that usually coincides with each ConfigStatus.

    VprocState ConfigStatus
    ONLINE Online, Hold
    OFFLINE

    FATAL

    NONODE

    Down
    UTILITY Catchup, Down, NewReady
    NEWPROC NewReady, NewDown, Null

    For an understanding of how vprocs behave during database startup, see VprocState/ConfigStatus Transitions During System Startup.

  • RestartKind
    RestartKind specifies the type of system restart to perform during the next database restart. Types of valid restarts include:
    • COLD

      A full restart, but transaction recovery will be deferred.

    • COLDWAIT

      A full restart, but database startup will be held up until transaction recovery is complete.

Error VprocStates

Vproc Manager displays specific error states that may indicate an unrecognized vproc or a conflict between the DBS Logical Configuration Status of a vproc and the PDE system state of the same vproc. Depending on subsequent activities targeted to this vproc, such as attempts to change its state or to move it into or out of the configuration, data corruption or other unintended consequences can occur. When Vproc Manager displays one of the following error states in any column of the output of the Vproc Manager STATUS command, contact the Teradata Support Center for information about returning the vproc to a valid VprocState.
  • MOCK
  • InID
  • NoAP
  • NoGT
  • INA
  • INAP
  • ISt
  • NV2P
  • InV

VprocState/ConfigStatus Transitions During System Startup

The following is the Key for the table that follows:
  • “=” is read as “remains.”
  • “->” is read as “becomes.”

For a definition of RcvJrnl, see STATUS.

CONFIG-STATUS (prior to System startup)                             VprocState (prior to System startup)  
ONLINE UTILITY (AMP vprocs only) OFFLINE/FATAL/

NONODE

NEWPROC
Online VprocState = ONLINE

ConfigStatus = Online

VprocState -> ONLINE

ConfigStatus = Online

VprocState = OFFLINE/FATAL/NONODE\

ConfigStatus -> Down

This combination is inconsistent and will be transitioned as follows:

VprocState -> ONLINE

ConfigStatus = Online

Hold (AMP vprocs only) VprocState = ONLINE

ConfigStatus -> Online

This combination is inconsistent and will be transitioned as follows:

VprocState -> ONLINE

ConfigStatus -> Online

VprocState = OFFLINE/FATAL/NONODE

ConfigStatus -> Down

This combination is inconsistent and will be transitioned as follows:

VProcState -> ONLINE

ConfigStatus -> Online

Catchup (AMP vprocs only) This combination is inconsistent and will be transitioned as follows:

IF (NOT RcvJrnl) THEN

VprocState -> OFFLINE

ConfigStatus -> Down

ELSE IF (RestartKind = COLDWAIT)

THEN

VprocState = ONLINE

ConfigStatus -> Online

ELSE

VprocState -> UTILITY

ConfigStatus = Catchup

IF (NOT RcvJrnl) THEN

 VprocState -> OFFLINE

 ConfigStatus -> Down

ELSE

IF (RestartKind = COLDWAIT)

THEN

VprocState -> ONLINE

ConfigStatus -> Online

ELSE

VprocState = UTILITY

ConfigStatus = Catchup

VprocState = OFFLINE/FATAL/NONODE

ConfigStatus -> Down

This combination is inconsistent and will be transitioned as follows:

VprocState -> UTILITY

ConfigStatus = Catchup

Down IF (VprocType = PE)

THEN

VprocState = ONLINE ConfigStatus -> Online

ELSE IF (VprocType = AMP)

THEN IF (NOT RECONFIG) AND RcvJrnl

THEN

VprocState -> UTILITY

ConfigStatus -> Catchup

ELSE IF (NOT RcvJrnl) THEN

VprocState -> OFFLINE

ConfigStatus = Down

This vproc is currently undergoing an ALL TABLES REBUILD using the Table Rebuild utility program, therefore:

VprocState = UTILITY

ConfigStatus = Down

Table Rebuild will set to it ONLINE/Online when it is complete.

VprocState = OFFLINE/FATAL/NONODE

ConfigStatus = Down

This combination is inconsistent and will be transitioned as follows

VprocState -> OFFLINE

ConfigStatus = Down

NewReady This combination is inconsistent and will be transitioned as follows:

VProcState -> NEWPROC

ConfigStatus = NewReady

IF RECONFIG THEN

VprocState = UTILITY

ConfigStatus = NewReady

ELSE

This combination is inconsistent and will be transitioned

as follows:

VprocState -> NEWPROC

ConfigStatus = NewReady

VprocState = OFFLINE/FATAL/NONODE

ConfigStatus -> NewDown

VprocState = NEWPROC

ConfigStatus = NewReady

NewDown This combination is inconsistent and will be transitioned as follows:

VprocState -> OFFLINE

ConfigStatus = NewDown

This combination is inconsistent and will be transitioned as follows:

VprocState --> OFFLINE

ConfigStatus = NewDown

VprocState = OFFLINE/FATAL/NONODE

ConfigStatus = NewDown

VprocState = NEWPROC

ConfigStatus -> NewReady