Using the Deferred Method - Parallel Transporter

Teradata® Parallel Transporter Reference

Product
Parallel Transporter
Release Number
17.10
Published
February 2022
Language
English (United States)
Last Update
2023-11-29
dita:mapPath
abr1608578396711.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
ogv1478610452101
Product Category
Teradata Tools and Utilities

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.

You should be aware of the following events during the job run:

  • The ODBC 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>_<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 will be deleted immediately after their data has been inserted into the target table.