You are on page 1of 46

Informatica PowerExchange for Teradata Parallel Transporter API (Version 9.1.

0)

User Guide

Informatica PowerExchange for Teradata Parallel Transporter API User Guide Version 9.1.0 March 2011 Copyright (c) 2006-2011 Informatica. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange, Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights reserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright 2007 Isomorphic Software. All rights reserved. Copyright © Meta Integration Technology, Inc. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. All rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved. Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright © Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright © Information Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at http://www.openssl.org. This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://www.dom4j.org/ license.html. The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http:// svn.dojotoolkit.org/dojo/trunk/LICENSE. This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html. This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http:// www.gnu.org/software/ kawa/Software-License.html. This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php. This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at http:/ /www.boost.org/LICENSE_1_0.txt. This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http:// www.pcre.org/license.txt. This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http:// www.eclipse.org/org/documents/epl-v10.php. This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/doc/ license.html, http://www.asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/ license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3-licenseagreement, http://antlr.org/license.html, http://aopalliance.sourceforge.net/, http://www.bouncycastle.org/licence.html, http://www.jgraph.com/jgraphdownload.html, http:// www.jgraph.com/jgraphdownload.html, http://www.jcraft.com/jsch/LICENSE.txt and http://jotm.objectweb.org/bsd_license.html. This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php) and the BSD License (http:// www.opensource.org/licenses/bsd-license.php). This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For further information please visit http://www.extreme.indiana.edu/.

This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422; 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress Software Corporation (“DataDirect”) which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: PWX-TPU-91000-0001

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Chapter 1: Understanding PowerExchange for Teradata Parallel Transporter API. . . . 1
Understanding PowerExchange for Teradata Parallel Transporter API Overview. . . . . . . . . . . . . . . . . 1

Chapter 2: Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installation and Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Installing and Configuring PowerExchange for Teradata Parallel Transporter API. . . . . . . . . . . . . . 3 Setting Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Installing PowerExchange for Teradata Parallel Transporter API . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Installing the Client Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Installing the Service Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Registering the Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Release Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 New Features and Enhancements in Version 9.1.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 New Features and Enhancements in Version 9.0.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Working with Deprecated Connection Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3: Teradata PT API Sessions and Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configuring a Teradata Parallel Transporter API Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Creating a Teradata PT API Connection Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Working with Teradata PT API Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Configuring Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Working with Log, Error, and Work Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Pipeline Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Support for Multiple Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Staged Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Configuring a Session for a Teradata PT API Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Configuring a Session for a Teradata PT API Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Table of Contents

i

20 TPTWR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Appendix A: Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 TPTRD Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 ii Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

If you have questions. and implementation services. navigate to Product Documentation from http://mysupport.com. and guide you through performing specific real-world tasks. or ideas about this documentation. The site contains information about Informatica.com. you can access the Informatica How-To Library at http://mysupport. you can access the Informatica Customer Portal site at http://mysupport. The services area of the site includes important information about technical support. It is written for database administrators and developers who are responsible for extracting data from and loading data to Teradata. the Informatica Multimedia Knowledge Base.com. Informatica How-To Library As an Informatica customer. Teradata databases.informatica. This guide assumes you have knowledge of Teradata PT.Preface The PowerExchange for Teradata Parallel Transporter API User Guide provides information about extracting data from and loading data to Teradata using Teradata Parallel Transporter API (Teradata PT API). We will use your feedback to improve our documentation. The How-To Library is a collection of resources to help you learn more about Informatica products and features. Informatica Resources Informatica Customer Portal As an Informatica customer. access to the Informatica customer support case management system (ATLAS). It includes articles and interactive demonstrations that provide solutions to common problems. its background. and sales offices. Let us know if we can contact you regarding your comments.informatica. usable documentation.com. You will also find product and partner information. and access to the Informatica user community.informatica. comments. the Informatica How-To Library. The Documentation team updates documentation as needed. user group information. upcoming events. To get the latest documentation for your product. compare features and behaviors. Informatica Documentation The Informatica Documentation team takes every effort to create accurate. newsletters. Informatica Product Documentation. iii .com. training and education. The site contains product information. the Informatica Knowledge Base.informatica. and PowerCenter. Informatica Web Site You can access the Informatica corporate web site at http://www. contact the Informatica Documentation team through email at infa_documentation@informatica.

informatica. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. contact the Informatica Knowledge Base team through email at KB_Feedback@informatica. contact the Informatica Knowledge Base team through email at KB_Feedback@informatica. You can request a user name and password at http://mysupport.Informatica Knowledge Base As an Informatica customer. The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about common concepts and guide you through performing specific tasks. Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Toll Free Brazil: 0800 891 0202 Mexico: 001 888 209 8853 North America: +1 877 463 2435 Europe / Middle East / Africa Toll Free France: 00800 4632 4357 Germany: 00800 4632 4357 Israel: 00800 4632 4357 Italy: 800 915 985 Netherlands: 00800 4632 4357 Portugal: 800 208 360 Spain: 900 813 166 Switzerland: 00800 4632 4357 or 0800 463 200 United Kingdom: 00800 4632 4357 or 0800 023 4632 Asia / Australia Toll Free Australia: 1 800 151 830 New Zealand: 1 800 151 830 Singapore: 001 800 4632 4357 Standard Rate North America: +1 650 653 6332 Standard Rate India: +91 80 4112 5738 Standard Rate France: 0805 804632 Germany: 01805 702702 Netherlands: 030 6022 797 iv Preface .com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products.com. technical white papers. If you have questions. or ideas about the Multimedia Knowledge Base. comments. Online Support requires a user name and password.com. Informatica Multimedia Knowledge Base As an Informatica customer. and technical tips.com.com. comments. you can access the Informatica Multimedia Knowledge Base at http://mysupport.informatica. or ideas about the Knowledge Base.informatica. If you have questions. you can access the Informatica Knowledge Base at http://mysupport. You can also find answers to frequently asked questions.

and delete operations against Teradata database tables. insert. Teradata PT is a load and unload utility that extracts. ¨ Update. 1 Understanding PowerExchange for Teradata Parallel Transporter API Overview PowerExchange for Teradata Parallel Transporter integrates PowerCenter and Teradata Parallel Transporter API (Teradata PT API) for data extraction and loading. ¨ Stream. transforms. and delete operations against Teradata database tables in near real- time mode. It extracts or loads data using one of the following system operators: ¨ Export. and loads data from multiple sources in parallel. Extracts data from Teradata. The PowerCenter Integration Service uses the Teradata PT API infrastructure to connect to Teradata. Use a Teradata PT connection to connect to the Teradata tables you want to export or load in a session. You cannot access the following Teradata objects: ¨ Macro ¨ Trigger ¨ Joined index ¨ Stored procedures ¨ Hash index ¨ Permanent journal 1 . upsert. ¨ Load. You can create a PowerCenter session that uses Teradata PT API to extract from Teradata sources and load to Teradata targets. create a mapping with a Teradata source or target. upsert. Bulk loads data into an empty Teradata database table. Performs update. insert. Performs update.CHAPTER 1 Understanding PowerExchange for Teradata Parallel Transporter API This chapter includes the following topic: ¨ Understanding PowerExchange for Teradata Parallel Transporter API Overview. To use PowerExchange for Teradata Parallel Transporter API.

6 ¨ Release Information. ¨ Install the following utilities on the machines where the PowerCenter Repository Service and PowerCenter Integration Service run: Teradata Parallel Transporter Utilities Teradata Parallel Transporter API Teradata Parallel Transporter Infrastructure Teradata Parallel Transporter Load Operator Teradata Parallel Transporter Update Operator Teradata Parallel Transporter Stream Operator Teradata Parallel Transporter Export Operator Teradata Parallel Transporter Operator Support Library Teradata CLIv2 Teradata ODBC Teradata Generic Security Services Teradata Parallel Transporter Data Connector Operator Shared ICU Libraries for Teradata 2 . complete the following tasks: ¨ Install or upgrade PowerCenter. Prerequisites Before you install PowerExchange for Teradata Parallel Transporter API. 2 ¨ Setting Environment Variables. 4 ¨ Registering the Plug-in. ¨ Install Teradata Parallel Transporter. 3 ¨ Installing PowerExchange for Teradata Parallel Transporter API .CHAPTER 2 Installation and Configuration This chapter includes the following topics: ¨ Installation and Configuration Overview. 7 Installation and Configuration Overview This chapter provides information about installing and configuring PowerExchange for Teradata Parallel Transporter API. ¨ Install Teradata.

2. ¨ Verify that you have read and write permissions on the following directories: <PowerCenter <PowerCenter <PowerCenter <PowerCenter Installation Installation Installation Installation Directory>\server\bin Directory>\server\bin\native Directory>\server\bin\RecoverySQL Directory>\client\bin The installer must be able to add and overwrite files in these directories. /opt/tdicu/lib. ¨ On Windows EMT 64-bit. Register the plug-in.cat file. After you install and configure PowerExchange for Teradata Parallel Transporter API. set the following environment variables: Environment Variable JAVA_HOME JRE_HOME PATH Value <PowerCenter installation directory>/java ${JAVA_HOME}/jre ${JAVA_HOME}/bin:${JRE_HOME}/bin:${PATH} On UNIX. you can create connections to access Teradata PT API. /usr/lib. Install the components. for example.Note: If you install PowerExchange for Teradata Parallel Transporter API using Teradata Parallel Transporter version 12 and then upgrade to Teradata Parallel Transporter version 13. Set to the location of the Teradata ICU libraries. You can download the Microsoft Visual C++ 2005 Redistributable Package (x64) from the Microsoft download center. you must reinstall PowerExchange for Teradata Parallel Transporter API. Create connection objects in the Workflow Manager so the PowerCenter Integration Service can connect to Teradata PT API. complete the following steps: 1. Installing and Configuring PowerExchange for Teradata Parallel Transporter API To install and configure PowerExchange for Teradata Parallel Transporter API. Setting Environment Variables Before you install the PowerExchange for Teradata Parallel Transporter API Service component. you must also set the following environment variables: Environment Variable COPERR TD_ICU_DATA Value Set to the location of the errmsg. Set system environment variables. 3. for example. you must install the Microsoft Visual C++ 2005 Redistributable Package (x64) if the machine does not have Visual C++ 2005 installed. Setting Environment Variables 3 .

export LIBPATH ¨ Using a C shell: $ setenv LIBPATH ${LIBPATH}:${JAVA_HOME}/lib: ${JRE_HOME}/lib Installing PowerExchange for Teradata Parallel Transporter API When you install PowerExchange for Teradata Parallel Transporter API. Allows the PowerCenter Repository Service access to the Teradata PT API metadata in the repository. you install components that allow PowerCenter to access Teradata PT API. Install the Client component on each PowerCenter Client machine where you want to create or access Teradata PT API metadata. Also allows the PowerCenter Integration Service to run Teradata PT API sessions. The following table describes the shared library variables for each operating system: Operating System Windows Solaris Linux AIX HP-UX Value PATH LD_LIBRARY_PATH LD_LIBRARY_PATH LIBPATH SHLIB_PATH For example. export LD_LIBRARY_PATH ¨ Using a C shell: $ setenv LD_LIBRARY_PATH ${JAVA_HOME}/lib: ${JRE_HOME}/lib For HP-UX: ¨ Using a Bourne shell: $ SHLIB_PATH=${SHLIB_PATH}:${JAVA_HOME}/lib: ${JRE_HOME}/lib. export SHLIB_PATH ¨ Using a C shell: $ setenv SHLIB_PATH ${SHLIB_PATH}:${JAVA_HOME}/lib: ${JRE_HOME}/lib For AIX: ¨ Using a Bourne shell: $ LIBPATH=${LIBPATH}:${JAVA_HOME}/lib: ${JRE_HOME}/lib. Installing the Client Component The Client component contains the online help files for PowerExchange for Teradata Parallel Transporter API. set the shared library environment variable based on the operating system. use the following syntax for Solaris: ¨ Using a Bourne shell: $ LD_LIBRARY_PATH=${JAVA_HOME}/lib: ${JRE_HOME}/lib. Install the following components: ¨ Client component.Also. ¨ Service component. 4 Chapter 2: Installation and Configuration . Allows you to access online help for PowerExchange for Teradata Parallel Transporter.

6. 7.1. create a resource in the domain and assign it to each node where you installed the Service component. On the PowerCenter Client machine. Click Next.chm to the help directory on the PowerCenter Client machine. Copy powercenterhelp.When you unzip or untar the installation file. Installing the Service Component on Windows Install the Service component on Windows when the PowerCenter Integration Service and PowerCenter Repository Service run on Windows. create a custom resource called “Teradata PT” and make it available to one or more nodes. Click Browse to find the directory or use the default directory. The PowerCenter master help file that contains links to PowerExchange for Teradata Parallel Transporter API help.chm. The Load Balancer dispatches the Session task to a node that has the resource. Stop Informatica Services if they are running on the machine. configure the session to use the resource. 2. The Welcome window introduces the PowerExchange for Teradata Parallel Transporter API installation. Close all other applications before running the installation.chm.chm in the help directory in the following location: <PowerCenter Installation Directory>\client\bin\help\en To back up the file. 3. The installation program displays a warning about stopping Informatica Services. install the Service component on each node configured to run on the grid. 4. For example.chm and teradata. install the Service component on each node configured to run the service process. Installing the Service Component Install the Service component on any node configured to run the PowerCenter Integration Service or PowerCenter Repository Service. Installing PowerExchange for Teradata Parallel Transporter API 5 . back up powercenterhelp. assign the resource as a required resource. If you cannot install the Service component on each node in the grid. Enter the absolute path to the PowerCenter installation directory. rename it to Original_powercenterhelp. 2. The Installation Directory window appears.chm. The online help file for PowerExchange for Teradata Parallel Transporter API. When you create a session. Click OK. ¨ teradata. When you configure the session. the following online help files are extracted: ¨ powercenterhelp. If the PowerCenter Integration Service is configured to run on a grid. If the services are configured to run on primary and backup nodes. Run the installer from the following location: <Download Location>\<Operating System Directory>\install. The default directory is C:\Informatica\9.exe Select the language to use during installation and click OK. 5. These files are extracted to the following location: <Download Location>\help\en To install the client component: 1. To install the Service component on Windows: 1.0.

The name of the installation directory cannot contain spaces. enter back to go back and modify the options. 3. You can view the log files generated by the installer to get more information about the installation tasks performed by the installer. Press Enter. the repository must be running in exclusive mode. Choose the correct version of Teradata PT API on the Teradata PT Version panel and press Enter. PowerCenter installs in the following directory: $HOME/Informatica/9. run install. To register the plug-in. 4. If you are upgrading from a previous version. <PowerCenter Installation Directory>/server/bin/ Registering the Plug-in After you install PowerExchange for Teradata Parallel Transporter API. When the installation is complete. By default. Or. The Teradata PT Version window asks you to choose the Teradata PT API version. 8.bin located in the root directory in the location where you downloaded the PowerExchange for Teradata Parallel Transporter API Service component installation files. the installer copies the Service component files to the installation directory. 12. A plug-in is an XML file that defines the functionality of PowerExchange for Teradata Parallel Transporter API.1. 7.0 HOME is the user home directory. 6 Chapter 2: Installation and Configuration . update the plug-in registration when you reregister the plug-in. After you press Enter. Review the information on the Pre-Installation Summary panel and press Enter to continue. 9. Installing the Service Component on UNIX Install the Service component on Windows when the PowerCenter Integration Service and PowerCenter Repository Service run on UNIX. 10. register the plug-in with the repository. Click Done. On a shell command line. Restart Informatica Services on the machine. Press Enter to use the default directory or enter the absolute path for the PowerCenter installation directory. Select the language to use during installation and press Enter. 11. Click Next. Use the Informatica Administrator or the pmrep RegisterPlugin command to register the plug-in. 5. To install the Service component on UNIX: 1. The installer shows the progress of the installation. Choose the correct version of Teradata PT API and click Next. Close all other applications. Review the installation information and click Install to continue.8. The Welcome panel introduces the PowerExchange for Teradata Parallel Transporter API Service component installation. 2. The Pre-Installation Summary window summarizes the installation information. the Installation Summary window displays the status of the installation. 6.

1 Effective in version 8. PowerExchange for Teradata Parallel Transporter API uses the connection object type “Teradata PT Connection. You can provide the query band expression that you want to pass to Teradata Parallel Transporter API as a session property. Teradata PT Connection and Teradata Dual Load Connection are available. When you install the Service component.The plug-in file for PowerExchange for Teradata Parallel Transporter API is TeradataPT.1. Run the session without staged loading to load data from all sources at once to the Teradata PT API target. You can provide the number of instances in the session properties. You can extract data from a Teradata source or load data to a Teradata target when the PowerCenter Integration Service runs on Windows 2008 R2.1. the installer copies TeradataPT. Upgrade Task Version Implemented: 8. You can load data in parallel through multiple instances into a Teradata PT API target from a source. New Features and Enhancements in Version 9. You can acquire data from several sources with subsequent runs of the session. Release Information PowerExchange for Teradata Parallel Transporter API includes new features and behavior changes.6 Versions Affected: 8. ¨ Staged Loading. Note: If you do not have the correct privileges to register the plug-in. contact the user who manages the PowerCenter Repository Service. New Features and Enhancements in Version 9. You can extract data from a Teradata source or load data to a Teradata target when the PowerCenter Integration Service runs on SUSE Linux Enterprise Server 11 if you use Teradata Parallel Transporter 13.0 ¨ New Teradata Parallel Transporter version. Working with Deprecated Connection Objects Upgrade Impact: Behavior Change.” Release Information 7 .0. ¨ SunOS x64 support. PowerExchange for Teradata Parallel Transporter API supports Teradata Parallel Transporter version 13.xml. PowerExchange for Teradata PT API uses Teradata PT Connection. ¨ SUSE Linux Enterprise Server 11 support.10. You can extract data from a Teradata source or load data to a Teradata target when the PowerCenter Integration Service runs on SunOS x64 platform.10. PowerExchange for Teradata Parallel Transporter API supports Teradata Parallel Transporter version 13. ¨ Support for multiple instances. two new connection object types.6. Teradata Dual Load Connection is applicable if you install PowerCenter Dual Load Option for Teradata.xml to the following directory: <PowerCenter Installation Directory>\server\bin\native After you register the plug-in. ¨ Windows 2008 R2 support. A query band expression is a set of name-value pairs that identify a query’s originating source ¨ New Teradata Parallel Transporter version.1 ¨ Support for query band expression. You can pause active loading to a Teradata PT API target in a session.

the PowerCenter Integration Service uses the values in the session properties.In a previous version. 8 Chapter 2: Installation and Configuration . Informatica recommends that you replace deprecated connection objects with new connection objects.” These connection objects have been replaced with connection objects of type “Teradata PT Connection Deprecated. the session properties contain the default values for these properties. The deprecated connection object retains the values you specified. it uses the connection attributes in the deprecated connection object. PowerExchange for Teradata Parallel Transporter API used Teradata PT API connection objects of type “Teradata Parallel Transporter Connection. If you run a session that uses a deprecated connection object.” The following connection attributes are moved from the connection object definition to the session properties: ¨ Log Database ¨ Log Table Name ¨ Error Database ¨ Error Table Name 1 ¨ Error Table Name 2 ¨ Drop Error Table When you upgrade. Deprecated connection objects might not be supported in future versions of PowerExchange for Teradata Parallel Transporter API. If you do not enter values in the session properties.

CHAPTER 3 Teradata PT API Sessions and Workflows This chapter includes the following topics: ¨ Configuring a Teradata Parallel Transporter API Connection. The Relational Connection Browser dialog box appears. The Select Subtype dialog box appears. and work tables. You can override the system operator in the session properties. Creating a Teradata PT API Connection Object You configure Teradata Parallel Transporter API properties when you create a Teradata PT API connection. Click Connections > Relational in the Workflow Manager. If you enable recovery in a session that loads to Teradata. create a Teradata target ODBC connection or create the recovery table manually. 11 ¨ Configuring a Session for a Teradata PT API Source. Click New. To create a Teradata Parallel Transporter connection: 1. error. 9 ¨ Working with Teradata PT API Sessions. truncate target tables. 9 . and create recovery tables in the target database. 16 Configuring a Teradata Parallel Transporter API Connection Create Teradata PT API connection objects to define connections to Teradata PT API in the repository. The PowerCenter Integration Service uses the target ODBC connection to drop log. 2. see the Teradata Parallel Transporter documentation. Additionally. 15 ¨ Configuring a Session for a Teradata PT API Target. you can create a Teradata target ODBC connection. The PowerCenter Integration Service does not use the ODBC connection to extract from or load to Teradata. For more information about Teradata PT API settings. The PowerCenter Integration Service uses Teradata PT API connection objects to extract from or load to Teradata.

and define the value in the session or workflow parameter file. the code page of the Teradata PT API connection must be the same as the code page of the Teradata source. Amount of time. The PowerCenter Integration Service interprets user names that start with $Param as session parameters. except for the underscore. The Relational Connection Editor dialog box appears. and then click OK. User Name Use Parameter in Password Password Code Page 5. Enter the properties for the connection: Property Name Description Connection name used by the Workflow Manager. 4. Default is 4. Database user name with the appropriate read and write database permissions to access the database. responses. Must be a positive. Must be a positive. Minimum number of Teradata PT API sessions required for the Teradata PT API job to continue. Select Teradata PT Connection. Default is disabled. Default is 1. Password for the database user name. Tenacity Max Sessions Min Sessions Sleep Data Encryption Block Size 10 Chapter 3: Teradata PT API Sessions and Workflows . in minutes. Teradata PT API uses when it returns data to the PowerCenter Integration Service. Default is 4. Enables full security encryption of SQL requests. Teradata database name. in hours. and data.3. Maximum block size. $Param Name. Default is disabled. Code page associated with the database. If you do not enter a database name. Must be a positive integer between 1 and the Max Sessions value. non-zero integer. non-zero integer. Must be a positive. Default is 6. Teradata PT API uses the default login database name. To define the user name in the parameter file. in bytes. Enter the connection attributes: Attribute TDPID Database Name Description The name of the Teradata database machine. and encrypt it using the pmpasswd CRYPT_DATA option. Maximum number of sessions that Teradata PT API establishes with the Teradata database. Amount of time. enter session parameter $Param Name as the user name. Indicates the password for the database user name is a session parameter. that Teradata PT API pauses before it retries to log on when the maximum number of operations runs on the Teradata database. that Teradata PT API continues trying to log on when the maximum number of operations runs on the Teradata database. Connection name cannot contain spaces or other special characters. non-zero integer. If you enable this option. define the password in the workflow or session parameter file. When you run session that extracts from a Teradata source.

330. . upsert. You can either create the recovery table manually or configure a target ODBC connection in addition to the Teradata PT API target connection object. insert. Default is Stream. ¨ The session must contain a PowerExchange for CDC source. and work tables or truncate target tables. ¨ If the PowerCenter Integration Service runs on UNIX.Export. 6. insert. . ¨ Set the TPTRecoveryModel custom property to “yes” for the session or PowerCenter Integration Service. ¨ The session must be configured to use the Stream system operator to load data to Teradata. Extracts data from Teradata. Creating the Recovery Table using a Target ODBC Connection When you configure a Teradata PT API target connection and a target ODBC connection in a session.Attribute Description Minimum is 256. upsert. set the THREADONOFF environment variable to 1. Performs update. you can create the recovery table manually.000. the PowerCenter Integration Service creates the recovery table in the target database. Bulk loads data into an empty Teradata database table. Working with Teradata PT API Sessions 11 . Working with Teradata PT API Sessions When you configure a Teradata PT API session. Maximum is 64. and delete operations against Teradata database tables. Default is 64. and delete operations against Teradata database tables in near real-time mode.Update. A recovery table must exist in the target database before the PowerCenter Integration Service can recover a session or workflow. . error.Load. Select Stream if you want to enable recovery for sessions that load data to Teradata. Performs update. Select Export if the session uses a Teradata Parallel Transporter Reader. System Operator Teradata PT API operator type: . Click OK. you define properties that determine how the PowerCenter Integration Service extracts data from or loads data to Teradata sources and targets. You can configure the following Teradata PT API session properties: ¨ Recovery ¨ Error and log tables ¨ Pipeline partitioning Configuring Recovery You can recover Teradata PT API sessions that meet the following requirements: ¨ The session must be enabled for recovery. Otherwise. Configure a target ODBC connection when you want to drop log.Stream.

sql script against the Teradata target database. and work tables for a session when the session starts. ¨ Work Tables. Error. Teradata PT API can truncate the target tables when the system operator is Update. the PowerCenter Integration Service can drop existing log. a working database. and work tables. If you configure the session to use a Teradata PT API target connection and a target ODBC connection. Choose where you want to create the log table when you configure session to load to Teradata. Teradata PT API creates one log table for each partition. and Work Tables When you run a session that extracts data from or loads data to Teradata using Teradata PT API. and you do not need to drop log. Creating the Recovery Table Manually If you enable recovery for a session that loads to Teradata.You can also configure the following session properties: ¨ Drop log. Teradata PT API creates two error tables for each partition. To create the recovery table. or Load. Working with Log. FrameworkInfo varbyte(2000) ). RecInfo varchar(256). error. Teradata PT API creates one work table for each partition. Log Tables Enter a log table name when you configure a session to load to Teradata. or under the default database. Store Teradata PT API restart and log information. error. You can also choose to create the log table in a log database. execute the create_schema_tpt. Stream. Log tables can contain inconsistent data when a session fails. Teradata PT API can truncate the target tables when the system operator is set to Update or Stream in the connection object properties. The script is installed in the following directory: <PowerCenter Installation Directory>\server\bin\RecoverySQL The script contains the following query: CREATE TABLE INFARecoveryTable ( TPTCPData integer. CheckpointNum integer. Log Teradata errors and rejected data when a session runs. Store data when you run a session that uses the Update system operator. ¨ Error Tables. error. you can create the recovery table manually. Counter integer. Create the recovery table in the Teradata target database. and work tables or truncate target tables. 12 Chapter 3: Teradata PT API Sessions and Workflows . Teradata PT API creates the following tables: ¨ Log Tables. If you configure the session to use a Teradata PT API target connection and a target ODBC connection. ¨ Truncate the target tables.

Name of the log table. see the log table for more information.INFA_LT_<number>.INFA_ET2_<number>. a working database. Teradata PT API stores the error tables under the user. If you do not specify a log table name. the PowerCenter Integration Service uses the name <error_database>. see the error tables for more information about the errors. If you do not enter a log database name in the session properties or a database name in the connection object. Error Table Name1 Error Table Name2 When a session fails. Name of the first error table. The exact table name appears in the session log. Error Tables Teradata writes rejected data to error tables ErrorTable1 and ErrorTable2. drop the log table or enter a different table name in the session properties.INFA_ET1_<number>. Choose where you want to create the error tables when you configure a session to load to Teradata. the PowerCenter Integration Service uses the name <log_database>. The exact table name appears in the session log. Teradata PT API stores the log tables under the user. The following session properties allow you to specify error table names: Property Error Database Description Name of the database that stores the error tables. Working with Teradata PT API Sessions 13 .The following session properties allow you to specify log table information: Property Log Database Description Name of the database that stores the log tables. drop the error tables or enter different table names in the session properties. Before you run the session again. Before you run the session again. You can also choose to create the error tables in an error database. If you do not specify a name for the second error table. The exact table name appears in the session log. ErrorTable1 contains data rejected for the following reasons: ¨ Data conversion errors ¨ Constraint violations ¨ Access Module Processor configuration changes ErrorTable2 contains data rejected for the following reasons: ¨ Unique primary index constraint violations ¨ Load driver job acquisition phase errors You can enter a name for each error table when you configure a session to load to Teradata. Log Table Name When a session fails. If you do not specify a name for the first error table. If you do not enter an error database name in the session properties or a database name in the connection object. the PowerCenter Integration Service uses the name <error_database>. Name of the second error table. or under the default database.

Work Tables The Update system operator uses DML statements for staging data. Work Table Name Pipeline Partitioning You can increase the number of partitions in a pipeline to improve session performance. If you have multiple targets in a session. You can configure partitioning for a session that extracts from or loads to Teradata. Recovery with Multiple Instances You cannot recover sessions with multiple instances. set the system operator to Stream in the connection object properties. Teradata PT API stores the work tables in the target database. Update partitioning information using the Partitions view on the Mapping tab of the session properties. You can specify the number of parallel instances to load data into the Teradata PT API target as a session property. type of source. To achieve optimal session performance you can configure the number of partitions and number of instances based on factors like network latency. The following table describes the partition types for partition points in Teradata PT API sessions: Partition Point Source Qualifier Teradata PT API Target Partition Type Pass-through Pass-through Support for Multiple Instances You can load data in parallel through multiple instances into a Teradata PT API target from a source to improve session performance. You can also choose to create the work table in the target database. It creates work tables before Teradata PT API begins loading data and removes them from the database after Teradata PT API loads all rows to the target. Session fails if you enable recovery and run the session. and frequency of data update. Name of the work tables when you select the Update system operator. 14 Chapter 3: Teradata PT API Sessions and Workflows . the PowerCenter Integration Service uses the name <work_table_database>. you can specify different number of instances for different targets. The exact table name appears in the session log. Choose where you want to create the work table when you configure a session to load to Teradata. If you do not specify a work table database. Tip: You can use many partitions with less number of instances if the source is slower than the target. Enter a work table name when you configure a session to load to Teradata. If you do not specify a work table name.INFA<number>_WT. The Teradata database creates one work table for each target table. If the session loads to Teradata. Increasing the number of partitions allows the PowerCenter Integration Service to create multiple connections to sources and targets and process partitions of sources and targets concurrently. The following session properties allow you to specify work table information: Property Work Table Database Description Name of the database that stores the work tables created by Teradata PT API when you select the Update system operator. The session level properties are applicable for all the instances.

and error tables for the subsequent runs. Default is TD_OFF. ¨ TD_OPER_CLI. the session extracts data from the source and pauses before it loads to the target. Teradata PT API enables tracing for activities involving the Notify feature. Teradata PT API disables tracing. You cannot access the target until the session loads data from all the sources.Staged Loading Staged loading is the ability to pause an active load operation until additional data is available. Run the session with pause acquisition when you load data from the first source. Enable the session parameter pause acquisition to enable staged loading. configure the following Teradata PT API source properties to enable Teradata PT API tracing: Property Driver Tracing Level Description Determines Teradata PT API tracing at the driver level: ¨ TD_OFF. Disable pause acquisition and run the session with the second source. pushdown optimization. For example. or row error logging. After you successfully run a session with pause acquisition. ¨ TD_OPER_ALL. If you update the same target table through different sessions and use pause acquisition. Teradata PT API enables tracing for driver-specific activities for Teradata. Use the same log. You can use staged loading with Load and Update operators. When you run a session with pause acquisition enabled. ¨ TD_OPER. You can run the session multiple times to acquire data from different sources or different data from the same source. specify the log. you want to load data into the same target table from two sources. turn off Drop log. Teradata PT API enables all driver-level tracing. work. ¨ TD_OPER_NOTIFY. and error tables and Truncate target tables for subsequent runs. work. 2. Session pauses the load operation after acquiring data from the source. 3. Teradata PT API enables tracing for activites involving CLIv2. select a Teradata PT connection. Use the same table names for all sessions for the same target table. When you run a Teradata PT API session. and error table names manually. Teradata PT API enables tracing for activities involving the operator common library. ¨ TD_OPER_OPCOMMON. you cannot use stored procedures. To configure a session to extract from Teradata: 1. If you enable pause acquisition. Change the reader type to Teradata Parallel Transporter Reader in the Readers settings on the Mapping tab. Disable pause acquisition and run the session to load the acquired data to the target at once. Configuring a Session for a Teradata PT API Source You can configure a session to extract from Teradata. From the Connections settings on the Sources node of the Mapping tab. work. Configuring a Session for a Teradata PT API Source 15 . use the same operator for the subsequent runs of the session. From the Connections settings on the Sources node. The PowerCenter Integration Service ignores source and source qualifier properties that you override in the session. The session loads data from both the sources into the target table at once.

For example. A Teradata PT API session cannot use stored procedures. Trace File Name File name and path of the Teradata PT API trace file. From the Connections settings on the Targets node. ¨ Drop log. Teradata PT API enables tracing for activities involving the Notify feature. Teradata PT API enables tracing for activites involving CLIv2. ¨ TD_OPER. ¨ TD_OPER_ALL. or row error logging. pushdown optimization. ¨ Truncate target tables. Default is TD_OFF. Default path is $PM_HOME.Property Infrastructure Tracing Level Description Determines Teradata PT API tracing at the infrastructure level: ¨ TD_OFF. ¨ TD_OPER_NOTIFY. Teradata PT API disables tracing. 2. Configuring a Session for a Teradata PT API Target You can configure a session to load to Teradata. You must enable the driver tracing level before you can enable the infrastructure tracing level. Change the writer type to Teradata Parallel Transporter Writer in the Writers settings on the Mapping tab. you must edit the target definition and specify at least one connected column as a primary key column. Note: If you want to run an update or delete operation on a Teradata target table that does not have a primary key column. 16 Chapter 3: Teradata PT API Sessions and Workflows . Note: You can view load statistics in the session log. and work tables. select a Teradata PT connection. ¨ TD_OPER_CLI. The load summary in the Workflow Monitor does not display load statistics. Teradata PT API enables tracing for activities involving the operator common library. Teradata PT API enables tracing for driver-specific activities for Teradata. The PowerCenter Integration Service ignores target properties that you override in the session. Create a target ODBC connection when you enable the session or workflow for recovery. To configure a session to load to Teradata: 1. Default file name is <Name of the TPT Operator>_timestamp. The second connection defines an optional ODBC connection to the target database. Select a Teradata target ODBC connection as the second connection for the target instance if you want to perform any of the following actions: ¨ Enable the session or workflow for recovery without creating the recovery table in the target database manually. The first connection defines the connection to Teradata PT API. Teradata PT API enables all driver-level tracing. leave the second connection empty. EXPORTER_20091221. ¨ TD_OPER_OPCOMMON. error. and you do not create the recovery table in the target database manually. The Workflow Manager allows you to create up to two connections for each target instance. Otherwise.

Disable when you want to load the data to the target. Teradata PT API marks the row as an error row.For Update. This attribute is available for the Update and Stream system operators.0. The query band expression to be passed to the Teradata PT API.For Delete. Causes load operation to pause before the session loads data to the Teradata PT API target. If disabled. . From the Connections settings on the Targets node of the Mapping tab. configure the following Teradata PT API target properties: Property Work Table Database Work Table Name Macro Database Description Name of the database that stores the work tables. If Teradata PT API receives a row marked for delete but it is missing in the target table. Default is 1. If Teradata PT API receives a row marked for update or delete but it is missing in the target table. Specifies how Teradata PT API handles rows that do not exist in the target table: . In the expression. . Teradata PT API does not mark the row in the error table. If Teradata PT API receives a row marked for update but it is missing in the target table. Default is disabled. Pause Acquisition Instances Query Band Expression Update Else Insert Truncate Table Mark Missing Rows Configuring a Session for a Teradata PT API Target 17 .. Teradata PT API stores the macros in the log database. Teradata PT API marks the row as an error row.None. If you do not specify a macro database. Default is None.1. Teradata PT API updates existing rows and inserts other rows as if marked for update. Name of the database that stores the macros Teradata PT API creates when you select the Stream system operator. Default is disabled. If Teradata PT API receives a row marked for update or delete but it is missing in the target table. . each name-value pair is separated by a semicolon and the expression ends with a semicolon. For example. The PowerCenter Integration Service ignores this attribute when you treat source rows as inserts or deletes.3. It is available for the Load system operator if you select a Teradata target ODBC connection. Teradata PT API marks the row as an error row. Name of the work table. It creates macros before Teradata PT API begins loading data and removes them from the database after Teradata PT API loads all rows to the target. Default is disabled. A query band expression is a set of name-value pairs that identify a query’s originating source.Both. ApplicationName=Informatica. Teradata PT API updates existing rows only.ClientUser=A. The Stream system operator uses macros to modify tables. Teradata PT API deletes all rows in the Teradata target before it loads data. The number of parallel instances to load data into the Teradata PT API target.Version=9.

Error Limit Maximum number of records that can be stored in the error table before Teradata PT API terminates the Stream system operator job. .Off. Default is 3. Must be a positive. Specifies how Teradata PT API overrides the normal replication services controls for an active Teradata PT API session: . Name of the restart log table. Name of the second error table.Both. If Teradata PT API receives a row marked for insert but it exists in the target table. Maximum is 600. Determines the maximum number of request buffers that may be allocated for the Teradata PT API job when you select the Stream system operator. error. Teradata PT API does not send an override request to the Teradata Database. and work tables for a session when the session starts. Minimum is 2.For Insert. Teradata PT API disables override of normal replication services for the active session when change data capture is active. Default is enabled. . Replication Override 18 Chapter 3: Teradata PT API Sessions and Workflows . Teradata PT API does not mark the row in the error table. Default is disabled. Must be -1 or a positive. Drops existing log. Default is None. If Teradata PT API receives a row marked for insert or update that causes a duplicate row in the target table. nonzero integer. . Default is 20. Teradata PT API determines the maximum number of request buffers according to the following formula: Max_Request_Buffers = Buffers * Number_Connected_Sessions Log Database Log Table Name Error Database Error Table Name1 Error TableName2 Drop Log/Error/ Work Tables Serialize Pack Pack Maximum Buffers Must be a positive. Name of the database that stores the error tables. Name of the database that stores the log tables. Teradata PT API marks the row as an error row.None. Uses the Teradata PT API serialize mechanism to reduce locking overhead when you select the Stream system operator. Causes Teradata PT API to determine the maximum number of statements to pack into a request when you select the Stream system operator. Teradata PT API marks the row as an error row. nonzero integer. Number of statements to pack into a request when you select the Stream system operator.For Update. Minimum is 1. which specifies an unlimited number of records. . Default is disabled.Property Mark Duplicate Rows Description Specifies how Teradata PT API handles duplicate rows when it attempts to insert or update rows in the target table: . Default is -1. If Teradata PT API receives a row marked for insert or update that causes a duplicate row in the target table.On. This attribute is available if you select a Teradata target ODBC connection. . Teradata PT API marks the row as an error row. nonzero integer. Default is For Insert. If Teradata PT API receives a row marked for update that causes a duplicate row in the target table. Name of the first error table. Teradata PT API overrides normal replication services controls for the active session.None.

Default is TD_OFF. Teradata PT API disables tracing. Teradata PT API enables tracing for activities involving CLIv2. . . Default file name is <Name of the TPT Operator>_timestamp.TD_OPER. . LOAD_20091221. Teradata PT API disables tracing.TD_OPER_ALL. Default path is $PM_HOME.Property Driver Tracing Level Description Determines Teradata PT API tracing at the driver level: . . . .TD_OPER_CLI. Teradata PT API enables tracing for activities involving the Notify feature.TD_OPER. Infrastructure Tracing Level Trace File Name Configuring a Session for a Teradata PT API Target 19 . Teradata PT API enables tracing for activities involving the operator common library. Teradata PT API enables all driver-level tracing.TD_OPER_OPCOMMON. Default is TD_OFF.TD_OPER_NOTIFY. .TD_OFF. Teradata PT API enables all driver-level tracing. Teradata PT API enables tracing for activities involving the Notify feature. Teradata PT API enables tracing for activities involving the operator common library. Teradata PT API enables tracing for driver-specific activities for Teradata. File name and path of the Teradata PT API trace file. Teradata PT API enables tracing for activities involving CLIv2.TD_OPER_CLI. For example. Determines Teradata PT API tracing at the infrastructure level: . . . .TD_OFF.TD_OPER_OPCOMMON. You must enable the driver tracing level before you can enable the infrastructure tracing level.TD_OPER_ALL.TD_OPER_NOTIFY. Teradata PT API enables tracing for driver-specific activities for Teradata.

tracing level from session attributes cannot be retrieved. 26 TPTRD Messages TPTRD_11001 Explanation: User Response: Plug-in failed to create the TPTLogging class object. TPTRD_11003 Explanation: User Response: Plug-in failed to convert Unicode to Code Page.APPENDIX A Error Messages This appendix includes the following topics: ¨ TPTRD Messages. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. 20 . Contact Informatica Global Customer Support. The system does not have enough memory to allocate to the logging object. The system does not have enough memory to allocate to the ILog logging object. Internal error. TPTRD_11002 Explanation: User Response: Plug-in failed to convert Code Page to Unicode. Contact Informatica Global Customer Support. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. 20 ¨ TPTWR Messages. TPTRD_21101 Explanation: User Response: Plug-in failed to retrieve Trace level from session. TPTRD_21201 Explanation: User Response: Plug-in failed to set ILog logger. While initializing logging module. Internal error. Contact Informatica Global Customer Support. TPTRD_21202 Explanation: Plug-in failed to set TPTLogging logger. The system does not have enough memory to allocate to the logging object.

Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTRD Messages 21 . Connection attributes are invalid. The system does not have enough memory to allocate to the user name object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTRD_21208 Explanation: User Response: Plug-in failed to set DML Statement. TPTRD_21205 Explanation: User Response: Plug-in failed to set Password. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Make sure all the connection attributes are correct. Initiate method of Teradata Parallel Transporter connection object failed. The schema defined in the mapping is incorrect. TPTRD_21211 Explanation: Plug-in failed to Initiate Teradata database connection. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTRD_21207 Explanation: User Response: Plug-in failed to set Table Name.User Response: Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. The system does not have enough memory to allocate to the host name object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. The system does not have enough memory to allocate to the password object. and scale are the same as the table definition. TPTRD_21204 Explanation: User Response: Plug-in failed to set User Name. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. The system does not have enough memory to allocate to the DML object. Verify that the column names. TPTRD_21203 Explanation: User Response: Plug-in failed to set TDPID. Validate or re-create the mapping. The system does not have enough memory to allocate to the database name object. TPTRD_21206 Explanation: User Response: Plug-in failed to set Working Database. precision. The system does not have enough memory to allocate to the table name object. TPTRD_21209 Explanation: User Response: Plug-in failed to create Teradata database connection object. TPTRD_21210 Explanation: User Response: Plug-in failed to create Schema for Table <table name>.

TPTRD_21213 Explanation: User Response: Plug-in failed to allocate memory to Schema object. Make sure that there is enough memory on the PowerCenter Integration Service machine. TPTRD_21219 Explanation: User Response: Unknown Error in TPTReaderPartition::run() Internal error. EXPORT system operator failed to get data from the Teradata tables. contact Informatica Global Customer Support TPTRD_21218 Explanation: User Response: Error occurred during Export. TPTRD_21220 Explanation: User Response: Invalid TDPID. The PowerCenter Integration Service cannot get the C-datatype for the Source Qualifier.User Response: Check the error message returned by Teradata CLI or DBS. Invalid host name. GetRow() call failed on the row <row number>.. The system does not have enough memory to allocate to the Teradata Parallel Transporter Schema object. No ports mapped in the mapping. If the session fails again. TPTRD_21212 Explanation: User Response: Plug-in failed to allocate memory to Connection object. The system does not have enough memory to allocate to the Teradata Parallel Transporter connection object. 22 Appendix A: Error Messages . Run the session again.. Make sure that you specify the correct TDPID in the connection object. Run the session again. Validate or re-create the mapping. TPTRD_21216 Explanation: User Response: Plug-in failed to retrieve DSQ C-datatype. Make sure that there is enough memory on the PowerCenter Integration Service machine. Contact Informatica Global Customer Support. The PowerCenter Integration Service could not write rows to Source Qualifier buffers. TPTRD_21214 Explanation: User Response: No Fields defined to read data from. Contact Informatica Global Customer Support. Check the datatype from the Source Qualifier list of datatypes. Contact Informatica Global Customer Support. TPTRD_21217 Explanation: User Response: Plug-in failed to flush all rows. TPTRD_21215 Explanation: User Response: Plug-in failed to fetch data on row <row number> with status <status code>.

TPTRD_21504 Explanation: User Response: Plug-in failed to retrieve Metadata Extension information. TPTRD_21501 Explanation: User Response: Plug-in failed to initialize Teradata PT Reader Partition Driver. Verify that field names and table names are same as in the Teradata table definition. The PowerCenter Integration Service cannot retrieve the Source Qualifier attributes. The PowerCenter Integration Service cannot retrieve the session attributes. contact Informatica Global Customer Support. TPTRD Messages 23 . TPTRD_21506 Explanation: User Response: Plug-in failed to build DML statement. Validate the mapping and run the session again. Internal error. Reader plug-in initialization failed. Connection object has some invalid parameters. TPTRD_21508 Explanation: User Response: Plug-in failed to create connection to Teradata database. The PowerCenter Integration Service could not create the DML statement for data extraction. TPTRD_21507 Explanation: User Response: Plug-in failed to create TPTAPI class instance. Verify that the custom SQL is correct. TPTRD_21502 Explanation: User Response: Plug-in failed to retrieve Teradata Parallel Transporter connection information. Verify that all attributes in the Source Qualifier are valid. Re-create the mapping or run the session again. TPTRD_21302 Explanation: User Response: Plug-in failed to retrieve Source Qualifier metadata object.TPTRD_21301 Explanation: User Response: Plug-in failed to initialize Teradata PT Reader component. If the session fails again. Verify that all attributes in the sources session object are valid. Run the session again. The session failed to initialize because the Source Qualifier instance could not be fetched from the mapping. TPTRD_21503 Explanation: User Response: Plug-in failed to retrieve Session-level information. Verify that all attributes in the connection object are appropriate. Reader partition driver initialization failed. TPTRD_21505 Explanation: User Response: Plug-in failed to retrieve Source Qualifier and its field information. Contact Informatica Global Customer Support. The system does not have enough memory to allocate to the Teradata PT API object. Contact Informatica Global Customer Support. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Internal error.

TPTRD_21510 Explanation: User Response: Plug-in failed to validate Session level DML statement <DML_statement>. TPTRD_21514 Explanation: User Response: Plug-in failed to retrieve Source Qualifier field list. TPTRD_21513 Explanation: User Response: Multiple groups <group_ count> not supported. Verify that the ports are defined correctly in the mapping. Contact Informatica Global Customer Support. The PowerCenter Integration Service cannot get the Source Qualifier or sources field list and field information. TPTRD_21518 Explanation: User Response: Plug-in failed to retrieve connection reference associated with particular partition. TPTRD_21512 Explanation: User Response: Plug-in failed to build Default DML statement.TPTRD_21509 Explanation: User Response: Plug-in failed to read data from table <table name> of Teradata database. TPTRD_21511 Explanation: User Response: Plug-in failed to validate Metadata Extension level DML statement <DML statement>. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. TPTRD_21517 Explanation: User Response: Plug-in failed to retrieve source extension attached with particular source qualifier. 24 Appendix A: Error Messages . The Source Qualifier contains multiple groups. Internal error. The custom SQL in the Source Qualifier is incorrect. TPTRD_21515 Explanation: User Response: Plug-in failed to retrieve C-datatype of field <field name>. Update the mapping so that the Source Qualifier contains a single group. Verify that the mapping fields are defined correctly. The port business names may not match the table definition. Verify that the custom SQL is correct. Contact Informatica Global Customer Support. The custom SQL in the session properties is incorrect. Verify that the custom SQL is correct. TPTRD_21516 Explanation: User Response: Plug-in failed to retrieve datatype of field <field name>. Contact Informatica Global Customer Support. Internal error. The PowerCenter Integration Service could not build the DML statement for data extraction. Internal error. Internal error. Internal error.

The SQL query in the custom SQL field is invalid. Internal error. Contact Informatica Global Customer Support. Internal error. Internal error. Enter a SQL query using Teradata SQL. TPTRD_21523 Explanation: User Response: Plug-in failed to retrieve Max Sessions. TPTRD_21525 Explanation: User Response: Plug-in failed to retrieve Block Size. TPTRD Messages 25 . Contact Informatica Global Customer Support. TPTRD_21527 Explanation: User Response: Invalid Sql Query. Contact Informatica Global Customer Support. Make sure that the SQL defined in custom SQL field is valid Teradata SQL. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. Internal error. Contact Informatica Global Customer Support. Internal error. The Max Sessions attribute for a Teradata PT connection object is set to an illegal value. TPTRD_21529 Explanation: Number of Max Sessions must be greater than 0. TPTRD_21528 Explanation: User Response: Plug-in failed to get the list of sources in the mapping. Internal error. Internal error. TPTRD_21526 Explanation: User Response: Plug-in failed to retrieve Encrypt Data flag. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. TPTRD_21522 Explanation: User Response: Plug-in failed to retrieve Tenacity. Internal error. Internal error. TPTRD_21524 Explanation: User Response: Plug-in failed to retrieve Sleep. TPTRD_21521 Explanation: User Response: Plug-in failed to retrieve Database Name.TPTRD_21519 Explanation: User Response: Plug-in failed to retrieve connection object associated with a connection reference. Contact Informatica Global Customer Support. TPTRD_21520 Explanation: User Response: Plug-in failed to retrieve TDPID.

Update the Number of Sorted Ports for the Teradata source and then restart the session. The Sleep attribute for a Teradata PT connection object is set to an illegal value. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Internal error. TPTRD_35061 Explanation: User Response: The following system error occurred when the PowerCenter Integration Service tried to get the values of some session attributes: <error message>. 26 Appendix A: Error Messages . TPTWR Messages TPTWR_11001 Explanation: User Response: Plug-in failed to create the TPTLogging class object. Contact Informatica Global Customer Support. The Number of Sorted Ports attribute in the Teradata PT source properties exceeds the number of output fields. The Tenacity attribute for a Teradata PT connection object is set to an illegal value. Contact Informatica Global Customer Support. TPTRD_21533 Explanation: User Response: No of sorted Ports more than the No of Output fields. A system error might have occurred or the repository might have inconsistencies. Update the Sleep attribute and then restart the session. Update the Block Size attribute and then restart the session. TPTWR_11002 Explanation: User Response: Plug-in failed to convert Code Page to Unicode. TPTWR_11003 Explanation: User Response: Plug-in failed to convert Unicode to Code Page. TPTRD_21530 Explanation: User Response: Sleep must be greater than 0. The system does not have enough memory to allocate to the logging object. Fix the operating system error. TPTRD_21531 Explanation: User Response: Tenacity must be greater than or equal to 0. TPTRD_21532 Explanation: User Response: The minimum 256 bytes and maximum 64000 bytes Block Size is required.User Response: Update the Max Sessions attribute and then restart the session. The Block Size attribute for a Teradata PT connection object is set to an illegal value. Update the Tenacity attribute and then restart the session. Internal error. Contact Informatica Global Customer Support. The PowerCenter Integration Service could not get the values of some session-level properties.

Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31206 Explanation: User Response: Plug-in failed to set Password. The system does not have enough memory to allocate to the logging object. Contact Informatica Global Customer Support. TPTWR_31201 Explanation: User Response: Plug-in failed to set ILog logger. TPTWR_31203 Explanation: User Response: Plug-in failed to set System Operator. The system does not have enough memory to allocate to the host name. TPTWR_31208 Explanation: User Response: Plug-in failed to set Table Name. TPTWR_31207 Explanation: User Response: Plug-in failed to set Working Database. TPTWR Messages 27 . Internal error.TPTWR_31101 Explanation: User Response: Plug-in failed to retrieve Trace level from session. The system does not have enough memory to allocate to the table name. The system does not have enough memory to allocate to the System operator. The system does not have enough memory to allocate to the password. TPTWR_31202 Explanation: User Response: Plug-in failed to set TPTLogging logger. TPTWR_31204 Explanation: User Response: Plug-in failed to set TDPID. The system does not have enough memory to allocate to the ILog logging object. The system does not have enough memory to allocate to the Working database. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. The system does not have enough memory to allocate to the user name. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31205 Explanation: User Response: Plug-in failed to set User Name. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.TPTWR_31209 Explanation: User Response: Plug-in failed to set Error Database Name. TPTWR_31210 Explanation: User Response: Plug-in failed to set Error Table 1 Name. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. The system does not have enough memory to allocate to error database name. The system does not have enough memory to allocate to the TRUNCATE TABLE statement. TPTWR_31213 Explanation: User Response: Plug-in failed to set Log Table Name. TPTWR_31217 Explanation: User Response: Plug-in failed to set Truncate Table DML Statement. The system does not have enough memory to allocate to the INSERT statement. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. 28 Appendix A: Error Messages . The system does not have enough memory to allocate to the delete DML statement. TPTWR_31212 Explanation: User Response: Plug-in failed to set Log Database Name. The system does not have enough memory to allocate to the UPDATE statement. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. The system does not have enough memory to allocate to Error Table 1 name. TPTWR_31215 Explanation: User Response: Plug-in failed to set Update DML Statement. The system does not have enough memory to allocate to Error Table 2 name. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31214 Explanation: User Response: Plug-in failed to set Insert DML Statement. The system does not have enough memory to allocate to the log database name. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31211 Explanation: User Response: Plug-in failed to set Error Table 2 Name. TPTWR_31216 Explanation: User Response: Plug-in failed to set Delete DML Statement. The system does not have enough memory to allocate to the log table name.

TPTWR_31223 Explanation: User Response: Plug-in failed to allocate memory to Schema object. The PowerCenter Integration Service failed in end acquisition. The system does not have enough memory to allocate to the DML group. TPTWR_31219 Explanation: User Response: Plug-in failed to create Schema for Table <table_name>. The system does not have enough memory to allocate to the DML group. Check the error message returned by Teradata CLI or DBS. TPTWR_31226 Explanation: User Response: Plug-in failed in End Acquisition. The system does not have enough memory to allocate to the Teradata Parallel Transporter connection object. TPTWR_31221 Explanation: User Response: Plug-in failed to Initiate Teradata database connection. Contact Informatica Global Customer Support. The PowerCenter Integration Service cannot commit the connection object. TPTWR Messages 29 . The system does not have enough memory to allocate to the schema object. Initiate method of Teradata Parallel Transporter connection object failed.TPTWR_31218 Explanation: User Response: Plug-in failed to create Teradata database connection object. TPTWR_31222 Explanation: User Response: Plug-in failed to allocate memory to Connection object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31224 Explanation: User Response: Plug-in failed to allocate memory to DML Group <DML group name>. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Check the DBS/CLI error message for more information. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Verify that the column names. TPTWR_31225 Explanation: User Response: Plug-in failed to commit the Connection object. precision. The system does not have enough memory to allocate to the connection object. and scale match the table definition. Check the DBS/CLI error message for more information. TPTWR_31220 Explanation: User Response: Plug-in failed to create DML Group <DML group name>. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Validate or re-create the mapping. Schema defined in the mapping is incorrect.

TPTWR_31235 Explanation: User Response: Truncate Table: Plug-in failed to create DML Group <DML_Group_name>. and restart the session. Drop the error and log tables if they exist in database. or delete to the Teradata database failed. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Drop the error and log tables if they exist in database. Unable to get information about buffer size. Contact Informatica Global Customer Support. DML group built is invalid. row length. Sending a buffer data for the insert operation to Teradata database failed. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. row header. TPTWR_31230 Explanation: User Response: Plug-in failed to put buffer in Teradata database. TPTWR_31232 Explanation: User Response: Plug-in failed to retrieve affected rows. and row trailer in LOAD system operator. Unable to get the number of affected rows and number of rejected rows from Teradata database. TPTWR_31233 Explanation: User Response: Truncate Table: Plug-in failed to create Teradata database connection object. and restart the session. Memory is not sufficient to allocate. TPTWR_31234 Explanation: User Response: Truncate Table: Plug-in failed to create Schema for Table <table_name>.TPTWR_31227 Explanation: User Response: Plug-in failed to Apply rows. and restart the session. 30 Appendix A: Error Messages . Sending row data request for insert. TPTWR_31231 Explanation: User Response: Plug-in failed to retrieve buffer layout for PutBuffer method. Unable to create a connection with Teradata database in Update drive for truncate table. Memory is not sufficient to allocate. TPTWR_31229 Explanation: User Response: Plug-in failed to put row in Teradata database. The PowerCenter Integration Service cannot apply rows. Check the DBS/CLI error message for more information. TPTWR_31228 Explanation: User Response: Plug-in failed to set DML Group <DML group name> to connection object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. When there is no sufficient memory to allocate to the Teradata database connection object. Drop the error and log tables if they exist in database. Drop the error and log tables if they exist in database. and restart the session. TPTWR_31236 Explanation: Truncate Table: Plug-in failed to Initiate Teradata database connection. update.

Internal error. TPTWR_31401 Explanation: User Response: Plug-in failed to initialize Teradata PT Writer Target Driver.User Response: Drop the error and log tables if they exist in database. TPTWR_31240 Explanation: User Response: Unable to support multiple group. The system does not have enough memory to allocate to the target drivers. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Writer target driver initialization failed. Internal error. TPTWR_31303 Explanation: User Response: Plug-in failed to retrieve Target Instance. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. TPTWR_31237 Explanation: User Response: Plug-in failed to set Update Recovery_Table DML Statement. Internal error. TPTWR_31301 Explanation: User Response: Plug-in failed to initialize Teradata PT Writer Plug-in. Contact Informatica Global Customer Support. TPTWR_31238 Explanation: User Response: Plug-in failed to set Insert Recovery_Table DML Statement. Contact Informatica Global Customer Support. and restart the session. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Internal error. Contact Informatica Global Customer Support. Internal error. TPTWR_31239 Explanation: User Response: Plug-in failed to set Delete Recovery_Table DML Statement. TPTWR_31302 Explanation: User Response: Plug-in failed to create Target Drivers. Contact Informatica Global Customer Support. The system does not have enough memory to allocate to the group drivers. TPTWR Messages 31 . TPTWR_31402 Explanation: Plug-in failed to create Group Drivers. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Writer plug-in initialization failed. Internal error. TPTWR_31304 Explanation: User Response: Invalid Target Index <target_index>.

Failure in Teradata PT API call. 32 Appendix A: Error Messages . Contact Informatica Global Customer Support. TPTWR_31602 Explanation: User Response: Plug-in failed to retrieve Row statistics information. TPTWR_31601 Explanation: User Response: Plug-in failed to initialize Teradata PT Writer Partition Driver. Internal error. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31502 Explanation: User Response: Plug-in failed to create Partition Drivers. Writer Group driver initialization failed. Contact Informatica Global Customer Support. Connection object has some invalid parameters. Check whether all attributes in the connection object are correct. and then run the session again. Writer partition driver initialization failed. TPTWR_31605 Explanation: Plug-in failed to build DML statements on table <table name> for system operator <system operator name>. TPTWR_31503 Explanation: User Response: Invalid Partition Index <partition_index>. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. TPTWR_31603 Explanation: User Response: Plug-in failed to retrieve Teradata Parallel Transporter connection and session level attributes. TPTWR_31404 Explanation: User Response: Invalid Group Index <group index>. Internal error.User Response: Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31604 Explanation: User Response: Plug-in failed to retrieve table information. TPTWR_31501 Explanation: User Response: Plug-in failed to initialize Teradata PT Writer Group Driver. Internal error. Internal error. TPTWR_31403 Explanation: User Response: Plug-in failed to retrieve Group list. Validate the mapping. Contact Informatica Global Customer Support. The system does not have enough memory to allocate to the partition drivers. The system does not have enough memory to allocate to the DML statement.

TPTWR Messages 33 . The PowerCenter Integration Service cannot read target table information from vector. The system does not have enough memory to allocate to the Delete DML statement. Cannot build UPDATE DML Statement. User Response: Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. The entire field in target table is primary key and no other column exists for update. TPTWR_31611 Explanation: User Response: Primary key is defined for all fields of table <table_name>. Cannot build UPDATE DML Statement. Row type is update and no primary key is defined in the target table. Cannot build DELETE DML Statement. TPTWR_31606 Explanation: Plug-in failed to build Truncate Table DML statement. Define a primary key in the target table and restart the session. The system does not have enough memory to allocate to the Update DML statement. Internal error. Make sure you have at least one column for update. User Response: Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31609 Explanation: Plug-in failed to build DELETE DML statement. User Response: Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. The PowerCenter Integration Service cannot read target table information from vector. TPTWR_31608 Explanation: Plug-in failed to build UPDATE DML statement. Define a primary key in the target table and restart the session. The PowerCenter Integration Service cannot read target table information from vector. The PowerCenter Integration Service cannot read target table information from vector. Row type is deleted and no primary key is defines in the target table. The system does not have enough memory to allocate to the Insert statement.User Response: Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31612 Explanation: User Response: Primary Key is not defined for any of the fields of table <table_name>. User Response: Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. TPTWR_31610 Explanation: User Response: Primary Key is not defined for any of the fields of table <table_name>. TPTWR_31607 Explanation: Plug-in failed to build INSERT DML statement. The system does not have enough memory to allocate to the Truncate Table DML statement. TPTWR_31613 Explanation: Plug-in failed to retrieve Truncate Table attribute.

Internal error. TPTWR_31617 Explanation: User Response: Plug-in failed to retrieve Working Database. TPTWR_31619 Explanation: User Response: Plug-in failed to Retrieve System Operator. Contact Informatica Global Customer Support. TPTWR_31615 Explanation: User Response: Plug-in failed to retrieve connection reference associated with particular partition. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. Internal error. Internal error. Internal error. Contact Informatica Global Customer Support.. TPTWR_31616 Explanation: User Response: Plug-in failed to retrieve connection object associated with a connection reference. Internal error. Contact Informatica Global Customer Support. TPTWR_31618 Explanation: User Response: Plug-in failed to retrieve TDPID. TPTWR_31623 Explanation: User Response: Plug-in failed to retrieve Error Table 1 Name. TPTWR_31622 Explanation: User Response: Plug-in failed to retrieve Error Database Name. TPTWR_31614 Explanation: User Response: Plug-in failed to retrieve Update Else Insert attribute. TPTWR_31621 Explanation: User Response: Plug-in failed to retrieve Log Database Name.. Internal error. Internal error. Contact Informatica Global Customer Support.User Response: Contact Informatica Global Customer Support. Contact Informatica Global Customer Support.. Internal error. Contact Informatica Global Customer Support. 34 Appendix A: Error Messages . TPTWR_31620 Explanation: User Response: Plug-in failed to retrieve Log Table Name. Contact Informatica Global Customer Support.. Internal error. Internal error. Contact Informatica Global Customer Support.

Teradata internal error. Internal error. TPTWR_31633 Explanation: User Response: Update Operation is not allowed for LOAD system operator. TPTWR_31632 Explanation: User Response: Plug-in failed to retrieve data indicator. Internal error. Contact Informatica Global Customer Support. TPTWR Messages 35 . TPTWR_31625 Explanation: User Response: Plug-in failed to retrieve Max Sessions. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. TPTWR_31627 Explanation: User Response: Plug-in failed to retrieve Sleep. TPTWR_31631 Explanation: User Response: Plug-in failed to allocate Memory. The system does not have enough memory to allocate to an object. As system operator is LOAD and row type is Update.TPTWR_31624 Explanation: User Response: Plug-in failed to retrieve Error Table 2 Name. Contact Informatica Global Customer Support. Internal error. Contact Informatica Global Customer Support. TPTWR_31628 Explanation: User Response: Plug-in failed to retrieve Base Address for each field. Internal error. TPTWR_31626 Explanation: User Response: Plug-in failed to retrieve Tenacity. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. TPTWR_31630 Explanation: User Response: Plug-in failed while Data Manipulation. Update operation is not allowed in LOAD system operator. Internal error. See the additional error message for more information. TPTWR_31634 Explanation: Delete Operation is not allowed for LOAD system operator. Contact Informatica Global Customer Support. TPTWR_31629 Explanation: User Response: Plug-in failed to retrieve commit Teradata database connection object. Internal error. As system operator is LOAD and row type is Update.

User Response: 36 Appendix A: Error Messages . TPTWR_31640 Explanation: User Response: Failed to register TPTRecStorageFactory. Drop the error and log tables. Review the session log and Teradata PT log tables for related messages. The Block Size attribute for a Teradata PT connection object is set to an illegal value. and restart the session. An error occurred when the PowerCenter Integration Service tried to initialize the connection with the Teradata PT writer. recovery will not be supported. Internal error. Update the Sleep attribute and then restart the session. An error occurred when the PowerCenter Integration Service tried to initiate the connection with Teradata PT. The Tenacity attribute for a Teradata PT connection object is set to an illegal value. TPTWR_34701 Explanation: Failed to initialize TPTWriterConnection. Review the session log and Teradata PT log tables for related messages. Contact Informatica Global Customer Support. The PowerCenter Integration Service cannot delete all rows of the target table. Review the session log and Teradata PT log tables for related messages. a network problem might have occurred during initialization. TPTWR_31641 Explanation: User Response: Failed to initiate TPTRecStorageFactory. TPTWR_31639 Explanation: User Response: Block size must be greater than 0.User Response: Delete operation is not allowed in LOAD system operator. Update the Tenacity attribute and then restart the session. The Sleep attribute for a Teradata PT connection object is set to an illegal value. the Teradata user name or password might be incorrect. For example. TPTWR_31637 Explanation: User Response: Sleep must be greater than 0. TPTWR_31638 Explanation: User Response: TENACITY must be greater than or equal to 0. TPTWR_31635 Explanation: User Response: Plug-in failed to truncate table. recovery will not be supported. The Max Sessions attribute for a Teradata PT connection object is set to an illegal value. Update the Max Sessions attribute and then restart the session. For example. Update the Block Size attribute and then restart the session. TPTWR_31636 Explanation: User Response: Number of Max Sessions must be greater than 0. Internal error. Contact Informatica Global Customer Support. TPTWR_31642 Explanation: User Response: Failed to initiate TPTConnectionManager.

An error occurred when the PowerCenter Integration Service tried to terminate the connection with Teradata PT for reading recovery information. Review the session log and Teradata PT log tables for related connection errors. Review the session log and Teradata PT log tables for related connection errors. TPTWR_34725 Explanation: User Response: Termination of TPT connection for reading recovery information failed. An error occurred when the PowerCenter Integration Service tried to terminate the connection with Teradata PT for deleting recovery information. An error occurred when the PowerCenter Integration Service tried to initialize the connection with Teradata PT for reading recovery information. An error occurred when Teradata PT tried to issue a commit against the Teradata database. Review the session log and Teradata PT log tables to find the failed transaction. a network problem might have occurred during deinitialization. User Response: TPTWR_34703 Explanation: Failed to commit for target <name> and partition <number>. Check the target tables for data discrepancies. An error occurred when the PowerCenter Integration Service tried to initialize the connection with Teradata PT for deleting recovery information. but Teradata PT does not support rollback for failed transactions. An error occurred when the PowerCenter Integration Service tried to deinitialize the connection with the Teradata PT writer. TPTWR_34727 Explanation: User Response: Initialization of TPT connection for deleting recovery information failed. a connection might have been dropped due to a network problem or fatal database error. Review the session log and Teradata PT log tables for related messages. Review the session log and Teradata PT log tables for related connection errors. A connection error occurred when the PowerCenter Integration Service tried to delete recovery information. User Response: TPTWR_34704 Explanation: User Response: Rollback is not supported for Teradata Parallel Transporter writer. TPTWR_34730 Explanation: User Response: Selection of DML statement failed in connection for deleting recovery information. For example. For example. TPTWR Messages 37 . Review the session log and Teradata PT log tables for related connection errors. The Teradata framework requested a rollback for a failed transaction. TPTWR_34729 Explanation: User Response: Termination of TPT connection for deleting recovery information failed. Review the session log and Teradata PT log tables for related connection errors. Review the session log and Teradata PT log tables for related connection errors.TPTWR_34702 Explanation: Failed to deinitialize TPTConnectionManager. TPTWR_34723 Explanation: User Response: Initialization of TPT connection for reading recovery information failed.

Fix the operating system error. The PowerCenter Integration Service could not get the values of some session-level properties. The target ODBC connection could not truncate the target table due to an error. TPTWR_35002 Explanation: User Response: ODBC Connection failed to truncate target table <name> in load mode. Review the session log for related messages. The session uses a connection object of type “Teradata Parallel Transporter Connection. The target ODBC connection could not drop the error table due to an error. The target ODBC connection could not create the recovery table in the Teradata target database due to a connection error.” which is deprecated.TPTWR_34731 Explanation: User Response: Acquisition failed in connection for deleting recovery information. Review the session log for related connection errors. TPTWR_35001 Explanation: User Response: ODBC Connection failed to create INFARecoveryTable. Contact Informatica Global Customer Support.” 38 Appendix A: Error Messages . Review the session log and Teradata PT log tables for related connection errors. TPTWR_35003 Explanation: User Response: ODBC Connection failed to drop error table. TPTWR_35004 Explanation: User Response: ODBC Connection failed to drop log table. The license key in the Administrator tool is invalid or does not contain Teradata PT connectivity option. The target ODBC connection could not drop the log table due to an error. Review the session log for related messages. TPTWR_36001 Explanation: User Response: Connectivity license key for Teradata database is not valid. Replace the deprecated connection object with a connection object of type “Teradata PT Connection. Review the session log and Teradata PT log tables for related connection errors. TPTWR_34732 Explanation: User Response: PutRow call failed in connection for deleting recovery information. A connection error occurred when the PowerCenter Integration Service tried to delete recovery information. Contact Informatica Global Customer Support to get a valid license key. Replace it with a valid connection object. A system error might have occurred or the repository might have inconsistencies. A connection error occurred when the PowerCenter Integration Service tried to delete recovery information. Review the session log for related messages. TPTWR_36002 Explanation: User Response: The session uses a deprecated connection object. TPTWR_35061 Explanation: User Response: The following system error occurred when the PowerCenter Integration Service tried to get the values of some session attributes: <error message>.

deprecated 7 PowerExchange for Teradata Parallel Transporter API upgrading 2 prerequisites PowerExchange for Teradata Parallel Transporter API 2 E environment variables Teradata PT API. setting 3 error messages TPTRD 20 TPTWR 26 error tables Teradata PT. description 13 Teradata PT. description 12 Teradata PT. description 14 Teradata PT.INDEX C connections Teradata PT API 9 Teradata PT. dropping 16 R recovery Teradata PT API sessions 11 recovery tables Teradata PT API. creating automatically 11 Teradata PT. dropping 16 39 . creating manually 12 S sessions configuring to extract from Teradata PT 15 configuring to load to Teradata PT 16 L log tables Teradata PT API. primary key columns 16 Teradata PT API connections creating 9 Teradata PT connections deprecated connection objects 7 M macro database Teradata PT 16 P partitioning Teradata PT API sessions 14 plug-ins registering PowerExchange for Teradata Parallel Transporter API 6 PowerExchange for Teradata Parallel Transporter behavior changes 7 installing and configuring 3 W work tables Teradata PT API. dropping 16 T targets Teradata PT.