16.10 - Definitions of Terms Used in Vproc Manager - Teradata Database

The following terms apply to Vproc Manager:

• VprocID

  A VprocID is a number that identifies the vproc to Teradata Database. 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:

  
  

  

  
  

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

  • OFFLINE

    Generally, this VprocState indicates vprocs that are not fully operational and have been forced down by the Teradata Database 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 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 at the next database restart.

  • UTILITY

    This vproc state applies only to AMP vprocs.

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

• ConfigStatus

  The database component of Teradata Database maintains its own internal version of the status of AMP and PE vprocs. That status is called the Teradata Database 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 Database Logical Configuration. Recently, the vproc might have been added to the PDE Physical Configuration or deleted from the Teradata Database 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 Teradata Database startup, see VprocState/ConfigStatus Transitions During Teradata Database 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.

VprocState/ConfigStatus Transitions During Teradata Database 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.