Using the Deferred Method - Parallel Transporter

Teradata® Parallel Transporter Reference - 20.00

Deployment
VantageCloud
VantageCore
Edition
IntelliFlex
Enterprise
VMware
Lake
Product
Parallel Transporter
Release Number
20.00
Published
October 2023
ft:locale
en-US
ft:lastEdition
2025-04-02
dita:mapPath
mjn1691132485167.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
ogv1478610452101
Product Category
Teradata Tools and Utilities

If you want to use the deferred method for the job, you must define the LOB columns as BLOB (lengthBytes) AS DEFERRED BY NAME or CLOB (lengthBytes) AS DEFERRED BY NAME, according to their data content, in the schema.

During the job run, be aware of the following events:
  • The SQL Selector operator retrieves data from deferred LOB columns and writes the data to external data files. These data files reside temporarily under the directory specified in LobDirectoryPath attribute or under the current working directory if the LobDirectoryPath attribute is not used.
  • One data file represents data for one LOB column.
  • These LOB data files have formulaic names as follows:

    <file-basename>_<column-name>_c#<job-id>_p<#>_r<#>.<file-extension>

    where:

    • <file-basename> is the value specified in the LobFileBaseName attribute.
    • <column-name> is the column name defined in a source table.
    • <job-id> is the job name from the tbuild command line.
    • <#> is an integer number generated internally by Teradata PT
    • <file-extension> is the value specified in the LobFileExtension attribute.

      These LOB data files need to be deleted immediately after their data has been inserted into the target table.

For a sample Teradata PT script in the <install-directory>/sample/userguide directory, see PST00021.txt.