The following table lists the common mapping for Teradata to Aster, if the target table does not exist. If the target table does exist, ensure the data mapping is correct to avoid an error.
| Source Teradata Type |
Default Aster Type |
| INTEGER, NUMBER |
INTEGER |
| BIGINT |
BIGINT |
| BYTEINT, SMALLINT |
SMALLINT |
| DECIMAL, NUMERIC |
NUMERIC |
| DOUBLE PRECISION, FLOAT, REAL |
DOUBLE PRECISION |
| VARCHAR, LONG VARCHAR |
VARCHAR |
| TIME |
TIME |
| TIMESTAMP |
TIMESTAMP |
| INTERVAL (all interval types) |
CHARACTER |
| VARBYTE, BYTE, BLOB |
BYTEA |
| CHARACTER, CLOB, PERIOD |
CHARACTER |
| JSON |
VARCHAR |
Usage Notes
- Data Mover converts the JSON data type to VARCHAR.
- If the table being moved contains the JSON data type and one of the Teradata system is not Teradata version 15.0 or later, an error occurs with a message indicating that you cannot move a JSON object with a Teradata system prior to 15.0.
- If the table being moved contains JSON data type, and Teradata PT API is used in force_utilities, an error occurs with a message indicating that Teradata PT API cannot be selected as force_utilities when moving a JSON object.
- JSON data type cannot be used in any index or in any of the following clauses: GROUP BY, ORDER BY, PARTITION BY, WHERE, ON, SET, DISTINCT, HASH BY, HAVING, QUALIFY, IN, CUBE, GROUPING SETS or ROLLUP. Methods of the JSON type that return comparable types are substituted for these disallowed clauses.
- Teradata to Aster jobs do not support the following data types:
- UDT (user defined data type)
- XML