Configuring Loader Settings - Aster Client

Teradata Aster® Client Guide

Product
Aster Client
Release Number
7.00
Published
May 2017
Language
English (United States)
Last Update
2018-04-13
dita:mapPath
hki1475000360386.ditamap
dita:ditavalPath
Generic_no_ie_no_tempfilter.ditaval
dita:id
B700-2005
lifecycle
previous
Product Category
Software
Loader settings
Name Description
Auto Analyse Whether to analyze data after the loading is completed.
Auto Partition Whether to partition data after the loading is completed.
Begin Script  
File Name Name of the script file to run before loading the data.
Location Type Type of the location setting. Choose Environment Variable if the path to the file is stored in an environment variable. Choose Folder Path if you want to specify the folder where the file is stored.
Environment Variable Environment variable that contains the path to the file.
Folder Path Path to the folder where the file is stored. Either enter the path or click the “...” button and select the folder.
Data Prefix CSV-compliant string to add to the start of each log. This string should be used as a prefix for each row (each line in a data file) being loaded into the Aster Database.
Date Format Specifies the date format of the data being loaded: ISO, SQL, POSTGRES, German, SQL_DMY, SQL_MDY, or Postgres_DMY.
End Script  
File Name Name of the script file to run after loading data.
Location Type Type of the location setting. Choose Environment Variable if the path to the file is stored in an environment variable. Choose Folder Path if you want to specify the folder where the file is stored.
Environment Variable The environment variable that contains the path to the file.
Folder Path The path to the folder where the file is stored. Either enter the path or click the “...” button and select the folder.
Error Logging  
Loader Error Logging Whether to enable error logging on malformed rows.
Discard Errors Whether to discard malformed rows.
Error Log Limit Maximum number of rejected rows before the loader aborts.
Error Log Table Schema Schema of the custom error log table. This is a table that the loader creates in Aster Database. The loader logs loading errors into this table. If you do not specify A schema, the public schema is used.

This is the same as using the --el-schema option of ncluster_loader.

Error Log Table Name of the custom error log table.
Session Label Session label or identifier with which to tag rows in the custom error log table. The date and time are automatically appended to this label.
Error Log File  
File Name Name of the log file in which to log errors.
Location Type Type of the location setting. Choose Environment Variable if the path to the file is stored in an environment variable. Choose Folder Path if you want to specify the folder where the file is stored.
Environment Variable Environment variable that contains the path to the file.
Folder Path Path to the folder where the file is stored. Either enter the path or click the “...” button and select the folder.
ForceLoader Force the use of the preferred loader, which is specified by the LoaderIP property. This is the same as using the -f option with ncluster_loader (ncluster_loader -f).
LoaderIP IP address of the preferred loader.
Timeout Aster Database connection timeout in seconds. Default is 30.
Truncate Table Whether to truncate empty tables before loading.
Vacuum Table Whether to “vacuum” the target table in Aster Database if loading fails. In other words, if loading fails, the target table is returned to its state before loading.


If you set Session Label to testLabel and enable error logging as shown above, error messages are tagged with testLabel <date and time>, as show in this example:

Loading tuples using node '10.65.197.95'.
35 tuples were loaded into table '"astertargetdb"."t_datetime_time"'.
Statistics for table: "astertargetdb"."t_datetime_time" with label  testLabel-2013-12-03-11-51-04-7283_Thrd_0_0 
Total Tuples:    37
Loaded Tuples:   35
Malformed Tuples:2
35 tuples were successfully loaded into 1 tables.

You could then run a query on the error logging table using ACT to ret rive the malformed rows:

ssistestdb=> select * from nc_errortable_repl where label like 'testLabel%';
key     |        tupletimestamp         |                    label                    |          targettable          | dmltype |  errmessage                    | sqlerrcode |     rawdata      | linenumber | columnname
------------+-------------------------------+---------------------------------------------+-------------------------------+---------+-------------------------------------------------+------------+------------------+------------+------------
4294967297 | 2013-11-21 18:41:02.127619-08 | testLabel-2013-12-03-11-51-04-7283_Thrd_0_0 | astertargetdb.t_datetime_time | C       | invalid input syntax for type time: "infinity"  | 22007      | "-1","infinity"  |          1 | val
4294967297 | 2013-11-21 18:41:02.213283-08 | testLabel-2013-12-03-11-51-04-7283_Thrd_0_0 | astertargetdb.t_datetime_time | C       | invalid input syntax for type time: "-infinity" | 22007      | "-2","-infinity" |         26 | val
(2 rows)