TUPLE_MOVER_OPERATIONS
Monitors the status of Tuple Mover operations on each node.
| Column Name | Data Type | Description | 
|---|---|---|
| OPERATION_START_TIMESTAMP | TIMESTAMP | Start time of a Tuple Mover operation. | 
| NODE_NAME | VARCHAR | Node name for which information is listed. | 
| OPERATION_NAME | VARCHAR | One of the following: 
 | 
| OPERATION_STATUS | VARCHAR | Returns the status of each operation, one of the following: 
 | 
| TABLE_SCHEMA | VARCHAR | Schema name for the specified projection. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example,  | 
| TABLE_NAME | VARCHAR | Table name for the specified projection. | 
| PROJECTION_NAME | VARCHAR | Name of the projection being processed. | 
| PROJECTION_ID | INTEGER | Unique numeric ID assigned by the Vertica catalog, which identifies the projection. | 
| COLUMN_ID | INTEGER | Identifier for the column for the associated projection being processed. | 
| EARLIEST_CONTAINER_START_EPOCH | INTEGER | Populated for mergeout and purge operations only. For an automatically-invoked mergeout, for example, the returned value represents the lowest epoch of containers involved in the mergeout. | 
| LATEST_CONTAINER_END_EPOCH | INTEGER | Populated for mergeout and purge_partitions operations. For an automatically-invoked mergeout, for example, the returned value represents the highest epoch of containers involved in the mergeout. | 
| ROS_COUNT | INTEGER | Number of ROS containers. | 
| TOTAL_ROS_USED_BYTES | INTEGER | Size in bytes of all ROS containers in the mergeout operation. (Not applicable for other operations.) | 
| PLAN_TYPE | VARCHAR | One of the following: 
 | 
| SESSION_ID | VARCHAR | Identifier for this session. This identifier is unique within the cluster at any point in time but can be reused when the session closes. | 
| TRANSACTION_ID | INTEGER | Identifier for the transaction within the session, if any. If a session is active but no transaction has begun, TRANSACTION_IDreturns NULL. | 
| IS_EXECUTING | BOOLEAN | Distinguishes between actively-running (t) and completed (f) tuple mover operations. | 
| RUNTIME_PRIORITY | VARCHAR | Determines how many run-time resources (CPU, I/O bandwidth) the Resource Manager should dedicate to running queries in the resource pool, one of the following: 
 | 
Privileges
Non-superuser: No explicit privileges required. You only see records for tables that you have privileges to view.
Examples
=> SELECT node_name, operation_status, projection_name, plan_type
    FROM TUPLE_MOVER_OPERATIONS;
 node_name         | operation_status | projection_name  | plan_type
-------------------+------------------+------------------+-----------
 v_vmart_node0001  | Running          | p1_b2            | Mergeout
 v_vmart_node0002  | Running          | p1               | Mergeout
 v_vmart_node0001  | Running          | p1_b2            | Replay Delete
 v_vmart_node0001  | Running          | p1_b2            | Mergeout
 v_vmart_node0002  | Running          | p1_b2            | Mergeout
 v_vmart_node0001  | Running          | p1_b2            | Replay Delete
 v_vmart_node0002  | Running          | p1               | Mergeout
 v_vmart_node0003  | Running          | p1_b2            | Replay Delete
 v_vmart_node0001  | Running          | p1               | Mergeout
 v_vmart_node0002  | Running          | p1_b1            | Mergeout