17.00 - Usage Notes - Parallel Data Pump

Teradata® Parallel Data Pump Reference

prodname
Parallel Data Pump
vrm_release
17.00
created_date
June 2020
category
Programming Reference
featnum
B035-3021-220K

One or more FIELD commands may be intermixed with the TABLE command and the FILLER command.

These commands must follow a LAYOUT command. If an input record field in fieldname is redefined, the data type from “character” to “decimal” with the datadesc parameter cannot be changed. This is illegal in Teradata TPump and will abort the job and return an error message.

If both NULLIF and DROP LEADING/TRAILING BLANKS/NULLS are specified on the same FIELD command, the DROP clause is evaluated after the NULLIF clause. As an example, in the FIELD command:
.FIELD FIELDNAME * CHAR (5) NULLIF FIELDNAME = 'x'
 DROP LEADING BLANKS;
if the input for fieldname is 'x', the NULLIF expression would evaluate to false because the leading blanks are not dropped before the NULLIF evaluation.

If a field-level MACROCHARSSET is present for a field of character type, TPump generates a CHARACTER SET clause in the macro creation DDL for the corresponding field using the specified character set.

If no field-level MACROCHARSET is present for a field of character type, but a layout/schema-level MACROCHARSET is present, TPump generates a CHARACTER SET clause in the macro creation DDL for the corresponding field using the specified layout character set.

Absent user specification, the following clause will be generated for each character macro parameter CHARACTER SET LATIN, when the client session character set is:
  • Is ASCII
  • Is EBCDIC
  • Ends in _0A or _0E
  • Ends in _zx, where “z” is other than 0 (digit zero)
  • Does not end in _zx or _zxx, except for KATAKANAEBCDIC, UTF-8, or UTF-16

TPump generates CHARACTER SET UNICODE in all other cases.