Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange for Teradata Parallel Transporter API
  3. PowerExchange for Teradata Parallel Transporter API Configuration
  4. PowerExchange for Teradata Parallel Transporter Connections
  5. PowerExchange for Teradata Parallel Transporter API Data Objects
  6. PowerExchange for Teradata Parallel Transporter API Mappings
  7. Teradata Parallel Transporter API Run-time Processing
  8. Data Type Reference

PowerExchange for Teradata Parallel Transporter API User Guide

PowerExchange for Teradata Parallel Transporter API User Guide

Advanced Properties

Advanced Properties

The advanced properties allow you to specify data object read operation properties to import data from Teradata tables.
The following table describes the advanced properties that you configure in the data object read operation:
Property
Description
Pre SQL
SQL command that the Data Integration Service runs against the source database before it reads from the source.
Post SQL
SQL command that the Data Integration Service runs against the source database before it writes to the target.
Select Distinct
Specifies if you want to select only unique rows. The Data Integration Service includes a SELECT DISTINCT statement if you choose this option.
Select SQL Statement
This property is applicable in the following scenarios:
  • You run a Teradata mapping on a Hortonworks cluster and on the Blaze engine.
  • You run a Teradata mapping on a Cloudera cluster and on the Blaze engine.
  • You run a Teradata mapping in the native environment.
Enter an SQL statement to override the default query. You can specify the columns that you want to use from the source database.
You can also parameterize the SQL statement.
Query Band Expression
The query band expression to be passed to the Teradata PT API.
A query band expression is a set of name-value pairs that identify a query’s originating source. In the expression, each name-value pair is separated by a semicolon and the expression ends with a semicolon. For example, ApplicationName=Informatica;Version=9.5.0;ClientUser=A;.
Source Table Name
Table name from which you want to extract rows.
Source Table Schema
Schema name from which you want to extract rows.
Driver Tracing Level
Determines Teradata PT API tracing at the driver level:
  • TD_OFF. Teradata PT API disables tracing.
  • TD_OPER. Teradata PT API enables tracing for driver-specific activities for Teradata.
  • TD_OPER_ALL. Teradata PT API enables all driver-level tracing.
  • TD_OPER_CLI. Teradata PT API enables tracing for activites involving CLIv2.
  • TD_OPER_NOTIFY. Teradata PT API enables tracing for activities involving the Notify feature.
  • TD_OPER_OPCOMMON. Teradata PT API enables tracing for activities involving the operator common library.
Default is TD_OFF.
The input locale for the value of the Driver Tracing Level attribute is in the English language only.
Infrastructure Tracing Level
Determines Teradata PT API tracing at the infrastructure level.
Select one of the following values:
  • TD_OFF. Teradata PT API disables tracing.
  • TD_OPER. Teradata PT API enables tracing for driver-specific activities for Teradata.
  • TD_OPER_ALL. Teradata PT API enables all driver-level tracing.
  • TD_OPER_CLI. Teradata PT API enables tracing for activities involving CLIv2.
  • TD_OPER_NOTIFY. Teradata PT API enables tracing for activities involving the Notify feature.
  • TD_OPER_OPCOMMON. Teradata PT API enables tracing for activities involving the operator common library.
Default is TD_OFF.
You must enable the driver tracing level before you can enable the infrastructure tracing level.
The input locale for the value of the Infrastructure Tracing Level attribute is in the English language only.
Trace File Name
File name and path of the Teradata PT API trace file.
Default path is
$<Informatica installation directory>\tomcat\bin
.
Default file name is
<Name of the TPT Operator>_timestamp
. For example,
LOAD_20091221
.
Spool Mode
Determines the spool mode Teradata PT API uses to extract data from Teradata.
You can choose one of the following spool modes:
  • Spool. Teradata PT API spools data while extracting data from Teradata.
  • NoSpool. Teradata PT API does not spool data while extracting data from Teradata. If the database does not support the NoSpool option, Teradata PT API uses the Spool option.
  • NoSpoolOnly. Teradata PT API does not spool while extracting data from Teradata.
Default is Spool.
The input locale for the value of the Spool Mode attribute is in the English language only.
If you set the custom property EnableTdch to true, the advanced properties in the data object read operation are not applicable.
If you run a mapping on a Hortonworks or Cloudera cluster and on the Blaze engine, the following properties are supported for Teradata data objects and customized data objects:
  • Select SQL Statement
  • Source Table Name
  • Source Filter
If you run a mapping on a Hortonworks cluster and on the Blaze engine, the Source Table Prefix property is supported for Teradata data objects and customized data objects.


Updated October 05, 2018