16.10 - MOVE PE - Teradata Database

Teradata Database Support Utilities

prodname
Teradata Database
vrm_release
16.10
created_date
June 2017
category
Configuration
featnum
B035-1180-161K

Purpose

The MOVE PE command specifies that a PE or group of PEs is to be moved to another PE or group of PEs.

Syntax



mmmlist
the range of PE vproc numbers being moved in the configuration.
nnnlist
the range of PE vproc numbers that mmmlist is being moved to in the configuration.
PE vproc numbers start at the high end of their range (30719 or 16383, depending on the system) and decrease consecutively.

Usage Notes

The number of PEs specified in mmmlist and in nnnlist must be the same. The following applies.

PEs in the … Must be …
mmmlist PEs defined in the current configuration.
nnnlist new PEs only.
You also can move PEs that are restricted to specific nodes, such as mainframe-connected PEs, to other nodes.

After the MOVE PE command is accepted, the Configuration utility displays:

The PE range is moved.

If you type the MOVE PE command before the BEGIN CONFIG command, the command is ignored. the system displays:

BEGIN CONFIG is not entered, and MOVE PE is ignored.
Run the Reconfig utility to change the configuration so that the moved PEs are properly associated with the correct nodes and/or disk arrays.

Examples: Moving existing PEs to new PEs

To move PE 16383 in an existing eight-PE system (PEs 16376 - 16383) to a new PE (PE 16375), type:

move pe 16383 to 16375

To move PEs 16380 - 16381 in an existing eight-PE system (PEs 16376 - 16383) to new PEs (PEs 16374 - 16375), type:

move pe 16380-16381 to 16374-16375