Teradata Load stage Input page - Load tab

The Load tab contains the following fields:

• Table. The name of the FastLoad target table to receive the data from the client system. This name is used in FastLoad statements, such as the INSERT tablename.* statement. This statement generates a list of field names from the definition of the table. Required.
• Error Table 1. The name of the FastLoad error Table 1 for rows ignored by Teradata because of an error. This table contains records that were rejected because of an error other than unique primary index or duplicate row violation. The stage ensures this is a new table by doing a DROP TABLE first. This name is used by the BEGIN LOADING statement. Required.
• Error Table 2. The name of the FastLoad error Table 2 for rows ignored by Teradata because of an error. This table contains records that violate the unique primary index constraint. The stage ensures this is a new table by doing a DROP TABLE first. This name is used in the BEGIN LOADING statement. Required.

  FastLoad automatically drops error tables that contain no rows when END LOADING finishes executing.

• Pre-load Table Action. The action performed on the table prior to loading it. The stage generates the necessary DROP and CREATE TABLE statements to reestablish the table. The IBM® InfoSphere® DataStage® metadata is used in each of these statements that are created. The options are:
  • Clear the table. Does not drop the table but deletes all rows from the table.
  • Drop and create the table. Drops the table and recreates it before loading.
  • User-defined DDL. Enables the User-defined DDL tab on theScript tab. The User-defined DDL tab allows you to customize the DROP TABLE and CREATE TABLE statements.
• Drop Error Tables Before Load. The disposition of the error tables. If Drop Error Tables Before Load is selected (which is the default), the generated script drops the error tables before loading begins. If Drop Error Tables Before Load is not selected, the stage assumes one of the following:
  • There are no error tables to drop. Therefore, the stage does not put statements to drop the error tables in the generated script. If error tables preexist, FastLoad fails.
  • You are attempting a restart. Therefore the error tables must preexist from a previous run.
• Load Method. The method for loading the data. The options are:
  • Manual. The files to perform a FastLoad are generated, but no loading is performed by the stage.
  • Invoke FastLoad. FastLoad is run after creating the control and data files. Output from the FastLoad sessions is saved in a file.
• Time Data Type. The data type of time columns expected by the stage in the Teradata database. The options are:
  • REAL. The stage expects time columns to be defined as REAL in the Teradata database. The default value.
    Note: Time is encoded for Teradata as (hour*10000 + minute*100 + second) where second might include a fractional value.
  • TIME(n). The stage expects time columns to be defined as TIME(n), where n is the Scale value in the range of 0 - 6. 0 - 6 represents the fractional seconds precision. The Length value for the time column must be 8 if Scale equals 0 or the sum of 9 and Scale if Scale is greater than 0.
• Timestamp Data Type. The data type of timestamp columns expected by the stage in the Teradata database. The options are:
  • CHAR(19). The stage expects timestamp columns to be defined as CHAR(19) in the Teradata database. The default value.
  • TIMESTAMP(n). The stage expects timestamp columns to be defined as TIMESTAMP(n), where n is the Scale value in the range of 0 - 6, which represents the fractional seconds precision. The Length value for the timestamp column must be 19 if Scale equals 0 or the sum of 20 and Scale if Scale is greater than 0.