Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Sun, 09 Feb 2015 @ 00:12:36 GMT

  <Prev Next>   <<First <Prev Next> Last>>  

Subj:   Re: TPT Scripts and logs location on Informatica
From:   Ganga, Sandeep Kumar

Hi Mahesh,

To the best of my knowledge, I believe Informatica only support TPT API and not the script based interface called tbuild

In regard to logs for TPT API using ETL tool informatica, enable TPT-API tracing through the Informatica GUI is available in "Power Exchange for TPT Plug-In" and higher .

Under the "Mapping" tab, under the "Properties" section there are 3 attributes.

1. Driver Tracing Level.

2. Infrastructure Tracing Level.

3. Trace File Name.

set the Driver tracing level and Infrastructure tracing to TD_OPER_OPCOMMON....

Here is a list of the various tracing levels available in TPT-API:

TD_OFF Tracing is disabled.

TD_OPER Enables tracing for driver specific activities.

TD_OPER_OPCOMMON Enables tracing for activities involving the Opcommon Library

TD_OPER_ALL Enables tracing for all activities (Driver specific, Cliv2, Opcommon library and the Notify feature)

TPT API tracing:

Set the following two attributes for the connection object in your code..


TD_TRACE_OUTPUT to /tptapitrace.txt

TPT API debug trace:

set the following two environment variables:


export TPTAPILOG=/tmp/apidebug.txt

Job output goes to standard out or if ETL app is used it could be stored elsewhere.

The binary log will most likely be in the dir /opt/teradata/client/1x.x0/tbuild/logs/

not sure if these do have for TPT API

In regard to script, TPTAPI does not use a script, is an interface in which you have direct control over the TPT operators. Using the Teradata PT open APIs allows third-party applications to execute Teradata PT operators directly. ETL tool automatically works with TPT. Once the user has entered the ETL data flow into the ETL tool's GUI, the ETL tool will automatically generate the appropriate calls to Parallel Transporter's API interface (TPT API). The input data is passed in data buffers that reside in memory from the ETL tool to TPT API without having to land the data or deal with problematic named pipes.

If you run TPT with the script interface, a TPT infrastructure component interprets the script and invokes the proper Operators to read and load the data.

If you use and ETL tool, the ETL tool will read and transform the data and pass the data in memory to the TPT API interface which will invoke the proper Operator to load the data.

@Forum: please correct me if I'm wrong in any point or missed any.




  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 24 Jul 2020