On this Page

Snap type:

Write


Description:

The Teradata FastLoad Snap uses the "FastLoad" command installed in the Operating System to load data into empty tables. Teradata FastLoad program should be installed on the Snaplex where the Snap is being executed. The Snap generates a script based on the field mapping which is executed using the FastLoad program that is installed on the OS. The Snap also captures the output generated from the FastLoad program (in the OS) and writes to the OUT field in the output views.


You will need the Teradata Tools & Utilities (TTU) to have access to the Teradata FastLoad component. See the Teradata Tool and Utilities documentation for your platform and Teradata version at http://www.info.teradata.com/templates/eSrchResults.cfm?prodline=&txtpid=&txtrelno=&txtttlkywrd=CINSTALL&rdsort=Title&srtord=Asc&nm=Installation for more information.


Queries produced by the Snap have the format:

SELECT TOP [limit] * FROM [table] WHERE [where clause] ORDER BY [ordering] .. and uses QUALIFY() for LIMIT
  • Expected downstream Snaps: A Snap monitoring the exit code to check result status.
  • Expected input: None or documents with values to evaluate expression properties in the Snap. Each input document triggers one execution of the script.
  • Expected output: A single document containing the console output and return status from the external Teradata application for each input document


Prerequisites:

TPT Snaps (TPT Insert, TPT Update, TPT Delete, TPT  Upsert and TPT Load) uses the 'tbuild' utility for the respective operations.

In order to use these Snaps in the pipelines, the respective TPT utilities should be installed/available on the Snapplexes. 

All the required TPT utilities must be installed on the node where JCC is running or the Snap simply executes but may not perform the operation. Any utility/library file missing on the node may cause the Snap to perform a failed operation.


Basic steps for installing the TPT utilities:

Procedure to install the Teradata tools and utilities:

  • Download the Teradata Tools and Utilities base such as TeradataToolsAndUtilitiesBase__Linux_i386-x8664.15.10.06.00.tar.gz for Linux environment.
  • If the OS is 64 bit,  install 32 bit support packages on the environment and also any further dependencies
  • Install the Teradata Tools and Utilities (that includes tbuild, fastload, mload etc)
  • The default installation also configures the PATH in the OS

Flow:  If the tbuild or fastload is already available on the OS path then the corresponding TPT Snap can invoke the required utility, however, if these binaries are not available on the OS path, then we need to provide the absolute path of the respective binary in the Snap.

Support and limitations:

Works in Ultra Task Pipelines.

When the upstream Snap passes empty strings as two consecutive delimiter characters, this Snap inserts null values into the corresponding fields of the table in the Teradata database. Also, if the last character in a record is a delimiter character, and if there is at least one more field to be processed, this Snap inserts null value in the field corresponding to the next one to be processed.

See Null Fields section in the Teradata documentation for more information.

Account: 

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Configuring Teradata Database Accounts for information on setting up this type of account.


Views:


InputThis Snap has at most two document input views. 
Output

This Snap has one output view. The output view produces three output fields, the Script, Status and the Out.

  • SCRIPT: Specifies the script generated by the Snap and will be executed in the OS (the password will be masked)
  • STATUS: Specifies the status after executing the Snap (produced from the FastLoad execution). The status contains the number of records read, duplicated, inserted, dropped(because of error count and unique violation), and the error tables 1&2.
  • OUT: Specifies the output text/data captured from the execution of the FastLoad program.
ErrorThis Snap has at most one document error view and produces zero or more documents in the view.


Settings

Label


Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.


Schema name



The database schema name. In case it is not defined, the suggestion for the table name will retrieve all the table names of all the schemas. The property is suggestible and will retrieve available database schemas during suggest values.

The values can be passed using the pipeline parameters but not the upstream parameter.

Example: SYS

Default value: [None] 

Table name

Required. Name of the table to execute a select query on.

The values can be passed using the pipeline parameters but not the upstream parameter.

Example: people

Default value: [None] 

Create table if not present
 

Whether the table should be automatically created if not already present.

Default value: [None] 

FastLoad absolute path

The absolute path for FastLoad command. If this field is left blank then the Snap tries to load the Fastload command from the Operating System.

Default value: [None] 

Checkpoint size


Required. Value that specifies the number of rows transmitted to the Teradata Database between checkpoints using the CHECKPOINT. If the value is set to 0, then the checkpoint is not enabled during Fastload execution. 

Default value: 0 

Write error table records to error view


Writes all the records from error tables to an error view after a Fastload execution is completed.

Default value: Not Selected 


Example

In this example, we shall load records from an Oracle database using the Oracle Select Snap, to a Teradata table using the Teradata FastLoad Snap. 


Select the table, Book under the schema, TECTONIC,  using the Oracle Select Snap.

The Mapper Snap maps the incoming data from Oracle to the Teradata Table. Note that the source and the target column data types should match for the data to load successfully.

The data is loaded to the table book123 under the schema, Snaplogic.


Successful execution of the pipeline displays the below output preview:Note that the preview displays the insert count as 2 and the duplicate count as 48 out of the 50 records that are read.