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, <[email protected]>. 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

Appendix A: Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

TPTRD Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 TPTWR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

ii

Table of Contents

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). It is written for database administrators and developers who are responsible for extracting data from and loading data to Teradata. This guide assumes you have knowledge of Teradata PT, Teradata databases, and PowerCenter.

Informatica Resources
Informatica Customer Portal
As an Informatica customer, you can access the Informatica Customer Portal site at http://mysupport.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Product Documentation, and access to the Informatica user community.

Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected]. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from http://mysupport.informatica.com.

Informatica Web Site

You can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.

Informatica How-To Library

As an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com. The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks.

iii

Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through email at [email protected].

Informatica Multimedia Knowledge Base

As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at http://mysupport.informatica.com. 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. If you have questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base team through email at [email protected].

Informatica Global Customer Support

You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at http://mysupport.informatica.com. 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

CHAPTER 1

Understanding PowerExchange for Teradata Parallel Transporter API

This chapter includes the following topic:
Understanding PowerExchange for Teradata Parallel Transporter API Overview, 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. Teradata PT is a load and unload utility that extracts, transforms, and loads data from multiple sources in parallel. You can create a PowerCenter session that uses Teradata PT API to extract from Teradata sources and load to Teradata targets. To use PowerExchange for Teradata Parallel Transporter API, create a mapping with a Teradata source or target. Use a Teradata PT connection to connect to the Teradata tables you want to export or load in a session. The PowerCenter Integration Service uses the Teradata PT API infrastructure to connect to Teradata. It extracts or loads data using one of the following system operators:
Export. Extracts data from Teradata. Load. Bulk loads data into an empty Teradata database table. Update. Performs update, insert, upsert, and delete operations against Teradata database tables. Stream. Performs update, insert, upsert, and delete operations against Teradata database tables in near real-

time mode. You cannot access the following Teradata objects:

Macro Trigger Joined index Stored procedures Hash index Permanent journal

CHAPTER 2

Installation and Configuration

This chapter includes the following topics:
Installation and Configuration Overview, 2 Setting Environment Variables, 3 Installing PowerExchange for Teradata Parallel Transporter API , 4 Registering the Plug-in, 6 Release Information, 7

Installation and Configuration Overview

This chapter provides information about installing and configuring PowerExchange for Teradata Parallel Transporter API.

Prerequisites
Before you install PowerExchange for Teradata Parallel Transporter API, complete the following tasks:
Install or upgrade PowerCenter. Install Teradata. Install Teradata Parallel Transporter. 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

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, you must reinstall PowerExchange for Teradata Parallel Transporter API.
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.
On Windows EMT 64-bit, you must install the Microsoft Visual C++ 2005 Redistributable Package (x64) if the

machine does not have Visual C++ 2005 installed. You can download the Microsoft Visual C++ 2005 Redistributable Package (x64) from the Microsoft download center.

Installing and Configuring PowerExchange for Teradata Parallel Transporter API

To install and configure PowerExchange for Teradata Parallel Transporter API, complete the following steps: 1. 2. 3. Set system environment variables. Install the components. Register the plug-in.

After you install and configure PowerExchange for Teradata Parallel Transporter API, you can create connections to access Teradata PT API. Create connection objects in the Workflow Manager so the PowerCenter Integration Service can connect to Teradata PT API.

Setting Environment Variables

Before you install the PowerExchange for Teradata Parallel Transporter API Service component, 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 must also set the following environment variables:

Environment Variable COPERR TD_ICU_DATA Value Set to the location of the errmsg.cat file, for example, /usr/lib. Set to the location of the Teradata ICU libraries, for example, /opt/tdicu/lib.

Setting Environment Variables

Also, set the shared library environment variable based on the operating system. 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, use the following syntax for Solaris:

Using a Bourne shell: $ LD_LIBRARY_PATH=${JAVA_HOME}/lib: ${JRE_HOME}/lib; 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; 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, you install components that allow PowerCenter to access Teradata PT API. Install the following components:
Client component. Allows you to access online help for PowerExchange for Teradata Parallel Transporter. Service component. Allows the PowerCenter Repository Service access to the Teradata PT API metadata in

the repository. Also allows the PowerCenter Integration Service to run Teradata PT API sessions.

Installing the Client Component

The Client component contains the online help files for PowerExchange for Teradata Parallel Transporter API. Install the Client component on each PowerCenter Client machine where you want to create or access Teradata PT API metadata.

Chapter 2: Installation and Configuration

When you unzip or untar the installation file, the following online help files are extracted:
powercenterhelp.chm. The PowerCenter master help file that contains links to PowerExchange for Teradata

Parallel Transporter API help.

teradata.chm. The online help file for PowerExchange for Teradata Parallel Transporter API.

These files are extracted to the following location:

<Download Location>\help\en

To install the client component: 1. On the PowerCenter Client machine, back up powercenterhelp.chm in the help directory in the following location:
<PowerCenter Installation Directory>\client\bin\help\en

To back up the file, rename it to Original_powercenterhelp.chm. 2. Copy powercenterhelp.chm and teradata.chm to the help directory on the PowerCenter Client machine.

Installing the Service Component

Install the Service component on any node configured to run the PowerCenter Integration Service or PowerCenter Repository Service. If the services are configured to run on primary and backup nodes, install the Service component on each node configured to run the service process. If the PowerCenter Integration Service is configured to run on a grid, install the Service component on each node configured to run on the grid. If you cannot install the Service component on each node in the grid, create a resource in the domain and assign it to each node where you installed the Service component. When you create a session, configure the session to use the resource. For example, create a custom resource called Teradata PT and make it available to one or more nodes. When you configure the session, assign the resource as a required resource. The Load Balancer dispatches the Session task to a node that has the resource.

Installing the Service Component on Windows

Install the Service component on Windows when the PowerCenter Integration Service and PowerCenter Repository Service run on Windows. To install the Service component on Windows: 1. 2. 3. 4. Close all other applications before running the installation. Stop Informatica Services if they are running on the machine. Run the installer from the following location:
<Download Location>\<Operating System Directory>\install.exe

Select the language to use during installation and click OK. The Welcome window introduces the PowerExchange for Teradata Parallel Transporter API installation.

5.

Click Next. The installation program displays a warning about stopping Informatica Services.

6.

Click OK. The Installation Directory window appears.

7.

Enter the absolute path to the PowerCenter installation directory. Click Browse to find the directory or use the default directory. The default directory is C:\Informatica\9.0.1.

Installing PowerExchange for Teradata Parallel Transporter API

8.

Click Next. The Teradata PT Version window asks you to choose the Teradata PT API version.

9.

Choose the correct version of Teradata PT API and click Next. The Pre-Installation Summary window summarizes the installation information.

10.

Review the installation information and click Install to continue. The installer shows the progress of the installation. When the installation is complete, the Installation Summary window displays the status of the installation.

11.

Click Done. You can view the log files generated by the installer to get more information about the installation tasks performed by the installer.

12.

Restart Informatica Services on the machine.

Installing the Service Component on UNIX

Install the Service component on Windows when the PowerCenter Integration Service and PowerCenter Repository Service run on UNIX. To install the Service component on UNIX: 1. 2. 3. Close all other applications. On a shell command line, run install.bin located in the root directory in the location where you downloaded the PowerExchange for Teradata Parallel Transporter API Service component installation files. Select the language to use during installation and press Enter. The Welcome panel introduces the PowerExchange for Teradata Parallel Transporter API Service component installation. 4. 5. Press Enter. Press Enter to use the default directory or enter the absolute path for the PowerCenter installation directory. The name of the installation directory cannot contain spaces. By default, PowerCenter installs in the following directory:
$HOME/Informatica/9.1.0

HOME is the user home directory. 6. 7. Choose the correct version of Teradata PT API on the Teradata PT Version panel and press Enter. Review the information on the Pre-Installation Summary panel and press Enter to continue. Or, enter back to go back and modify the options. 8. After you press Enter, the installer copies the Service component files to the installation directory.
<PowerCenter Installation Directory>/server/bin/

Registering the Plug-in

After you install PowerExchange for Teradata Parallel Transporter API, register the plug-in with the repository. A plug-in is an XML file that defines the functionality of PowerExchange for Teradata Parallel Transporter API. If you are upgrading from a previous version, update the plug-in registration when you reregister the plug-in. To register the plug-in, the repository must be running in exclusive mode. Use the Informatica Administrator or the pmrep RegisterPlugin command to register the plug-in.

Chapter 2: Installation and Configuration

The plug-in file for PowerExchange for Teradata Parallel Transporter API is TeradataPT.xml. When you install the Service component, the installer copies TeradataPT.xml to the following directory:
<PowerCenter Installation Directory>\server\bin\native

After you register the plug-in, two new connection object types, Teradata PT Connection and Teradata Dual Load Connection are available. PowerExchange for Teradata PT API uses Teradata PT Connection. Teradata Dual Load Connection is applicable if you install PowerCenter Dual Load Option for Teradata. Note: If you do not have the correct privileges to register the plug-in, contact the user who manages the PowerCenter Repository Service.

Release Information
PowerExchange for Teradata Parallel Transporter API includes new features and behavior changes.

New Features and Enhancements in Version 9.1.0

New Teradata Parallel Transporter version. PowerExchange for Teradata Parallel Transporter API supports

Teradata Parallel Transporter version 13.10.

SUSE Linux Enterprise Server 11 support. 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.10.
SunOS x64 support. 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.

New Features and Enhancements in Version 9.0.1

Support for query band expression. You can provide the query band expression that you want to pass to

Teradata Parallel Transporter API as a session property. A query band expression is a set of name-value pairs that identify a querys originating source
New Teradata Parallel Transporter version. PowerExchange for Teradata Parallel Transporter API supports

Teradata Parallel Transporter version 13.

Support for multiple instances. You can load data in parallel through multiple instances into a Teradata PT

API target from a source. You can provide the number of instances in the session properties.
Staged Loading. You can pause active loading to a Teradata PT API target in a session. You can acquire data

from several sources with subsequent runs of the session. Run the session without staged loading to load data from all sources at once to the Teradata PT API target.
Windows 2008 R2 support. 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.

Working with Deprecated Connection Objects

Upgrade Impact: Behavior Change, Upgrade Task Version Implemented: 8.6 Versions Affected: 8.1.1

Effective in version 8.6, PowerExchange for Teradata Parallel Transporter API uses the connection object type Teradata PT Connection.

Release Information

In a previous version, PowerExchange for Teradata Parallel Transporter API used Teradata PT API connection objects of type Teradata Parallel Transporter Connection. These connection objects have been replaced with connection objects of type Teradata PT Connection Deprecated. 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, the session properties contain the default values for these properties. The deprecated connection object retains the values you specified. If you run a session that uses a deprecated connection object, the PowerCenter Integration Service uses the values in the session properties. If you do not enter values in the session properties, it uses the connection attributes in the deprecated connection object. Informatica recommends that you replace deprecated connection objects with new connection objects. Deprecated connection objects might not be supported in future versions of PowerExchange for Teradata Parallel Transporter API.

Chapter 2: Installation and Configuration

CHAPTER 3

Teradata PT API Sessions and Workflows

This chapter includes the following topics:
Configuring a Teradata Parallel Transporter API Connection, 9 Working with Teradata PT API Sessions, 11 Configuring a Session for a Teradata PT API Source, 15 Configuring a Session for a Teradata PT API Target, 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 Teradata PT API connection objects to extract from or load to Teradata. Additionally, you can create a Teradata target ODBC connection. The PowerCenter Integration Service uses the target ODBC connection to drop log, error, and work tables, truncate target tables, and create recovery tables in the target database. The PowerCenter Integration Service does not use the ODBC connection to extract from or load to Teradata. If you enable recovery in a session that loads to Teradata, create a Teradata target ODBC connection or create the recovery table manually.

Creating a Teradata PT API Connection Object

You configure Teradata Parallel Transporter API properties when you create a Teradata PT API connection. You can override the system operator in the session properties. For more information about Teradata PT API settings, see the Teradata Parallel Transporter documentation. To create a Teradata Parallel Transporter connection: 1. Click Connections > Relational in the Workflow Manager. The Relational Connection Browser dialog box appears. 2. Click New. The Select Subtype dialog box appears.

3.

Select Teradata PT Connection, and then click OK. The Relational Connection Editor dialog box appears.

4.

Enter the properties for the connection:

Property Name Description Connection name used by the Workflow Manager. Connection name cannot contain spaces or other special characters, except for the underscore. Database user name with the appropriate read and write database permissions to access the database. To define the user name in the parameter file, enter session parameter $Param Name as the user name, and define the value in the session or workflow parameter file. The PowerCenter Integration Service interprets user names that start with $Param as session parameters. Indicates the password for the database user name is a session parameter, $Param Name. If you enable this option, define the password in the workflow or session parameter file, and encrypt it using the pmpasswd CRYPT_DATA option. Default is disabled. Password for the database user name. Code page associated with the database. When you run session that extracts from a Teradata source, the code page of the Teradata PT API connection must be the same as the code page of the Teradata source.

User Name

Use Parameter in Password

Password Code Page

5.

Enter the connection attributes:

Attribute TDPID Database Name Description The name of the Teradata database machine. Teradata database name. If you do not enter a database name, Teradata PT API uses the default login database name. Amount of time, in hours, that Teradata PT API continues trying to log on when the maximum number of operations runs on the Teradata database. Must be a positive, non-zero integer. Default is 4. Maximum number of sessions that Teradata PT API establishes with the Teradata database. Must be a positive, non-zero integer. Default is 4. Minimum number of Teradata PT API sessions required for the Teradata PT API job to continue. Must be a positive integer between 1 and the Max Sessions value. Default is 1. Amount of time, in minutes, that Teradata PT API pauses before it retries to log on when the maximum number of operations runs on the Teradata database. Must be a positive, non-zero integer. Default is 6. Enables full security encryption of SQL requests, responses, and data. Default is disabled. Maximum block size, in bytes, Teradata PT API uses when it returns data to the PowerCenter Integration Service.

Tenacity

Max Sessions

Min Sessions

Sleep

Data Encryption

Block Size

10

Chapter 3: Teradata PT API Sessions and Workflows

Attribute

Description Minimum is 256. Maximum is 64,330. Default is 64,000.

System Operator

Teradata PT API operator type: - Export. Extracts data from Teradata. Select Export if the session uses a Teradata Parallel Transporter Reader. - Load. Bulk loads data into an empty Teradata database table. - Update. Performs update, insert, upsert, and delete operations against Teradata database tables. - Stream. Performs update, insert, upsert, and delete operations against Teradata database tables in near real-time mode. Select Stream if you want to enable recovery for sessions that load data to Teradata. Default is Stream.

6.

Click OK.

Working with Teradata PT API Sessions

When you configure a Teradata PT API session, 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. The session must contain a PowerExchange for CDC source. The session must be configured to use the Stream system operator to load data to Teradata. Set the TPTRecoveryModel custom property to yes for the session or PowerCenter Integration Service. If the PowerCenter Integration Service runs on UNIX, set the THREADONOFF environment variable to 1.

A recovery table must exist in the target database before the PowerCenter Integration Service can recover a session or workflow. You can either create the recovery table manually or configure a target ODBC connection in addition to the Teradata PT API target connection object. Configure a target ODBC connection when you want to drop log, error, and work tables or truncate target tables. Otherwise, you can create the recovery table manually.

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, the PowerCenter Integration Service creates the recovery table in the target database.

Working with Teradata PT API Sessions

11

You can also configure the following session properties:

Drop log, error, and work tables. Log tables can contain inconsistent data when a session fails. If you

configure the session to use a Teradata PT API target connection and a target ODBC connection, the PowerCenter Integration Service can drop existing log, error, and work tables for a session when the session starts.
Truncate the target tables. Teradata PT API can truncate the target tables when the system operator is set to

Update or Stream in the connection object properties. If you configure the session to use a Teradata PT API target connection and a target ODBC connection, Teradata PT API can truncate the target tables when the system operator is Update, Stream, or Load.

Creating the Recovery Table Manually

If you enable recovery for a session that loads to Teradata, and you do not need to drop log, error, and work tables or truncate target tables, you can create the recovery table manually. Create the recovery table in the Teradata target database. To create the recovery table, execute the create_schema_tpt.sql script against the Teradata target database. 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, Counter integer, RecInfo varchar(256), CheckpointNum integer, FrameworkInfo varbyte(2000) );

Working with Log, Error, and Work Tables

When you run a session that extracts data from or loads data to Teradata using Teradata PT API, Teradata PT API creates the following tables:
Log Tables. Store Teradata PT API restart and log information. Teradata PT API creates one log table for

each partition.
Error Tables. Log Teradata errors and rejected data when a session runs. Teradata PT API creates two error

tables for each partition.

Work Tables. Store data when you run a session that uses the Update system operator. 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. You can also choose to create the log table in a log database, a working database, or under the default database. Choose where you want to create the log table when you configure session to load to Teradata.

12

Chapter 3: Teradata PT API Sessions and Workflows

The following session properties allow you to specify log table information:
Property Log Database Description Name of the database that stores the log tables. If you do not enter a log database name in the session properties or a database name in the connection object, Teradata PT API stores the log tables under the user. Name of the log table. If you do not specify a log table name, the PowerCenter Integration Service uses the name <log_database>.INFA_LT_<number>. The exact table name appears in the session log.

Log Table Name

When a session fails, see the log table for more information. Before you run the session again, drop the log table or enter a different table name in the session properties.

Error Tables
Teradata writes rejected data to error tables ErrorTable1 and ErrorTable2. 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. You can also choose to create the error tables in an error database, a working database, or under the default database. Choose where you want to create the error tables when you configure a session to load to Teradata. The following session properties allow you to specify error table names:
Property Error Database Description Name of the database that stores the error tables. If you do not enter an error database name in the session properties or a database name in the connection object, Teradata PT API stores the error tables under the user. Name of the first error table. If you do not specify a name for the first error table, the PowerCenter Integration Service uses the name <error_database>.INFA_ET1_<number>. The exact table name appears in the session log. Name of the second error table. If you do not specify a name for the second error table, the PowerCenter Integration Service uses the name <error_database>.INFA_ET2_<number>. The exact table name appears in the session log.

Error Table Name1

Error Table Name2

When a session fails, see the error tables for more information about the errors. Before you run the session again, drop the error tables or enter different table names in the session properties.

Working with Teradata PT API Sessions

13

Work Tables
The Update system operator uses DML statements for staging data. 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. Enter a work table name when you configure a session to load to Teradata. You can also choose to create the work table in the target database. Choose where you want to create the work table when you configure a session to load to Teradata. 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. If you do not specify a work table database, Teradata PT API stores the work tables in the target database. Name of the work tables when you select the Update system operator. The Teradata database creates one work table for each target table. If you do not specify a work table name, the PowerCenter Integration Service uses the name <work_table_database>.INFA<number>_WT. The exact table name appears in the session log.

Work Table Name

Pipeline Partitioning
You can increase the number of partitions in a pipeline to improve session performance. 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. You can configure partitioning for a session that extracts from or loads to Teradata. If the session loads to Teradata, set the system operator to Stream in the connection object properties. Update partitioning information using the Partitions view on the Mapping tab of the session properties. 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 specify the number of parallel instances to load data into the Teradata PT API target as a session property. If you have multiple targets in a session, you can specify different number of instances for different targets. The session level properties are applicable for all the instances. To achieve optimal session performance you can configure the number of partitions and number of instances based on factors like network latency, type of source, and frequency of data update. Tip: You can use many partitions with less number of instances if the source is slower than the target.

Recovery with Multiple Instances

You cannot recover sessions with multiple instances. Session fails if you enable recovery and run the session.

14

Chapter 3: Teradata PT API Sessions and Workflows

Staged Loading
Staged loading is the ability to pause an active load operation until additional data is available. Enable the session parameter pause acquisition to enable staged loading. When you run a session with pause acquisition enabled, the session extracts data from the source and pauses before it loads to the target. You can run the session multiple times to acquire data from different sources or different data from the same source. Disable pause acquisition and run the session to load the acquired data to the target at once. For example, you want to load data into the same target table from two sources. Run the session with pause acquisition when you load data from the first source. Session pauses the load operation after acquiring data from the source. Disable pause acquisition and run the session with the second source. The session loads data from both the sources into the target table at once. You cannot access the target until the session loads data from all the sources. You can use staged loading with Load and Update operators. If you enable pause acquisition, use the same operator for the subsequent runs of the session. After you successfully run a session with pause acquisition, turn off Drop log, work, and error tables and Truncate target tables for subsequent runs. Use the same log, work, and error tables for the subsequent runs. If you update the same target table through different sessions and use pause acquisition, specify the log, work, and error table names manually. Use the same table names for all sessions for the same target table.

Configuring a Session for a Teradata PT API Source

You can configure a session to extract from Teradata. When you run a Teradata PT API session, you cannot use stored procedures, pushdown optimization, or row error logging. The PowerCenter Integration Service ignores source and source qualifier properties that you override in the session. To configure a session to extract from Teradata: 1. 2. 3. Change the reader type to Teradata Parallel Transporter Reader in the Readers settings on the Mapping tab. From the Connections settings on the Sources node, select a Teradata PT connection. From the Connections settings on the Sources node of the Mapping tab, 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. Teradata PT API disables tracing. TD_OPER. Teradata PT API enables tracing for driver-specific activities for Teradata. TD_OPER_ALL. Teradata PT API enables all driver-level tracing. TD_OPER_CLI. Teradata PT API enables tracing for activites involving CLIv2. TD_OPER_NOTIFY. Teradata PT API enables tracing for activities involving the Notify feature. TD_OPER_OPCOMMON. Teradata PT API enables tracing for activities involving the operator common library. Default is TD_OFF.

Configuring a Session for a Teradata PT API Source

15

Property Infrastructure Tracing Level

Description Determines Teradata PT API tracing at the infrastructure level: TD_OFF. Teradata PT API disables tracing. TD_OPER. Teradata PT API enables tracing for driver-specific activities for Teradata. TD_OPER_ALL. Teradata PT API enables all driver-level tracing. TD_OPER_CLI. Teradata PT API enables tracing for activites involving CLIv2. TD_OPER_NOTIFY. Teradata PT API enables tracing for activities involving the Notify feature. TD_OPER_OPCOMMON. Teradata PT API enables tracing for activities involving the operator common library. Default is TD_OFF. You must enable the driver tracing level before you can enable the infrastructure tracing level.

Trace File Name

File name and path of the Teradata PT API trace file. Default path is $PM_HOME. Default file name is <Name of the TPT Operator>_timestamp. For example, EXPORTER_20091221.

Note: You can view load statistics in the session log. The load summary in the Workflow Monitor does not display load statistics.

Configuring a Session for a Teradata PT API Target

You can configure a session to load to Teradata. A Teradata PT API session cannot use stored procedures, pushdown optimization, or row error logging. The PowerCenter Integration Service ignores target properties that you override in the session. The Workflow Manager allows you to create up to two connections for each target instance. The first connection defines the connection to Teradata PT API. The second connection defines an optional ODBC connection to the target database. Create a target ODBC connection when you enable the session or workflow for recovery, and you do not create the recovery table in the target database manually. 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. Drop log, error, and work tables. Truncate target tables.

Otherwise, leave the second connection empty. Note: If you want to run an update or delete operation on a Teradata target table that does not have a primary key column, you must edit the target definition and specify at least one connected column as a primary key column. To configure a session to load to Teradata: 1. 2. Change the writer type to Teradata Parallel Transporter Writer in the Writers settings on the Mapping tab. From the Connections settings on the Targets node, select a Teradata PT connection.

16

Chapter 3: Teradata PT API Sessions and Workflows

3.

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.

Name of the work table. Name of the database that stores the macros Teradata PT API creates when you select the Stream system operator. The Stream system operator uses macros to modify tables. 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. If you do not specify a macro database, Teradata PT API stores the macros in the log database. Causes load operation to pause before the session loads data to the Teradata PT API target. Disable when you want to load the data to the target. Default is disabled. The number of parallel instances to load data into the Teradata PT API target. Default is 1. The query band expression to be passed to the Teradata PT API. A query band expression is a set of name-value pairs that identify a querys originating source. In the expression, each name-value pair is separated by a semicolon and the expression ends with a semicolon. For example, ApplicationName=Informatica;Version=9.0.1;ClientUser=A;. Teradata PT API updates existing rows and inserts other rows as if marked for update. If disabled, Teradata PT API updates existing rows only. The PowerCenter Integration Service ignores this attribute when you treat source rows as inserts or deletes. Default is disabled. Teradata PT API deletes all rows in the Teradata target before it loads data. This attribute is available for the Update and Stream system operators. It is available for the Load system operator if you select a Teradata target ODBC connection. Default is disabled. Specifies how Teradata PT API handles rows that do not exist in the target table: - None. If Teradata PT API receives a row marked for update or delete but it is missing in the target table, Teradata PT API does not mark the row in the error table. - For Update. If Teradata PT API receives a row marked for update but it is missing in the target table, Teradata PT API marks the row as an error row. - For Delete. If Teradata PT API receives a row marked for delete but it is missing in the target table, Teradata PT API marks the row as an error row. - Both. If Teradata PT API receives a row marked for update or delete but it is missing in the target table, Teradata PT API marks the row as an error row. Default is None.

Pause Acquisition

Instances

Query Band Expression

Update Else Insert

Truncate Table

Mark Missing Rows

Configuring a Session for a Teradata PT API Target

17

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: - None. If Teradata PT API receives a row marked for insert or update that causes a duplicate row in the target table, Teradata PT API does not mark the row in the error table. - For Insert. If Teradata PT API receives a row marked for insert but it exists in the target table, Teradata PT API marks the row as an error row. - For Update. If Teradata PT API receives a row marked for update that causes a duplicate row in the target table, Teradata PT API marks the row as an error row. - Both. If Teradata PT API receives a row marked for insert or update that causes a duplicate row in the target table, Teradata PT API marks the row as an error row. Default is For Insert. Name of the database that stores the log tables. Name of the restart log table. Name of the database that stores the error tables. Name of the first error table. Name of the second error table. Drops existing log, error, and work tables for a session when the session starts. This attribute is available if you select a Teradata target ODBC connection. Default is disabled. Uses the Teradata PT API serialize mechanism to reduce locking overhead when you select the Stream system operator. Default is enabled. Number of statements to pack into a request when you select the Stream system operator. Must be a positive, nonzero integer. Default is 20. Minimum is 1. Maximum is 600. Causes Teradata PT API to determine the maximum number of statements to pack into a request when you select the Stream system operator. Default is disabled. Determines the maximum number of request buffers that may be allocated for the Teradata PT API job when you select the Stream system operator. 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, nonzero integer. Default is 3. Minimum is 2. Error Limit Maximum number of records that can be stored in the error table before Teradata PT API terminates the Stream system operator job. Must be -1 or a positive, nonzero integer. Default is -1, which specifies an unlimited number of records. Specifies how Teradata PT API overrides the normal replication services controls for an active Teradata PT API session: - On. Teradata PT API overrides normal replication services controls for the active session. - Off. Teradata PT API disables override of normal replication services for the active session when change data capture is active. - None. Teradata PT API does not send an override request to the Teradata Database. Default is None.

Replication Override

18

Chapter 3: Teradata PT API Sessions and Workflows

Property Driver Tracing Level

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

Infrastructure Tracing Level

Trace File Name

Configuring a Session for a Teradata PT API Target

19

APPENDIX A

Error Messages
This appendix includes the following topics:
TPTRD Messages, 20 TPTWR Messages, 26

TPTRD Messages
TPTRD_11001
Explanation: User Response:

Plug-in failed to create the TPTLogging class object.

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_11002
Explanation: User Response:

Plug-in failed to convert Code Page to Unicode.

Internal error. Contact Informatica Global Customer Support.

TPTRD_11003
Explanation: User Response:

Plug-in failed to convert Unicode to Code Page.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21101
Explanation: User Response:

Plug-in failed to retrieve Trace level from session.

While initializing logging module, tracing level from session attributes cannot be retrieved. Contact Informatica Global Customer Support.

TPTRD_21201
Explanation: User Response:

Plug-in failed to set ILog logger.

The system does not have enough memory to allocate to the ILog logging object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTRD_21202
Explanation:

Plug-in failed to set TPTLogging logger.

The system does not have enough memory to allocate to the logging object.

20

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTRD_21203
Explanation: User Response:

Plug-in failed to set TDPID.

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.

TPTRD_21204
Explanation: User Response:

Plug-in failed to set User Name.

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_21205
Explanation: User Response:

Plug-in failed to set Password.

The system does not have enough memory to allocate to the password object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTRD_21206
Explanation: User Response:

Plug-in failed to set Working Database.

The system does not have enough memory to allocate to the database name object. 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.

The system does not have enough memory to allocate to the table 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.

The system does not have enough memory to allocate to the DML object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTRD_21209
Explanation: User Response:

Plug-in failed to create Teradata database connection object.

Connection attributes are invalid. Make sure all the connection attributes are correct.

TPTRD_21210
Explanation: User Response:

Plug-in failed to create Schema for Table <table name>.

The schema defined in the mapping is incorrect. Validate or re-create the mapping. Verify that the column names, precision, and scale are the same as the table definition.

TPTRD_21211
Explanation:

Plug-in failed to Initiate Teradata database connection.

Initiate method of Teradata Parallel Transporter connection object failed.

TPTRD Messages

21

User Response:

Check the error message returned by Teradata CLI or DBS. Contact Informatica Global Customer Support.

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. Make sure that there is enough memory on the PowerCenter Integration Service machine.

TPTRD_21213
Explanation: User Response:

Plug-in failed to allocate memory to Schema object.

The system does not have enough memory to allocate to the Teradata Parallel Transporter Schema object. Make sure that there is enough memory on the PowerCenter Integration Service machine.

TPTRD_21214
Explanation: User Response:

No Fields defined to read data from.

No ports mapped in the mapping. Validate or re-create the mapping.

TPTRD_21215
Explanation: User Response:

Plug-in failed to fetch data on row <row number> with status <status code>.
GetRow() call failed on the row <row number>. Contact Informatica Global Customer Support.

TPTRD_21216
Explanation: User Response:

Plug-in failed to retrieve DSQ C-datatype.

The PowerCenter Integration Service cannot get the C-datatype for the Source Qualifier. Check the datatype from the Source Qualifier list of datatypes.

TPTRD_21217
Explanation: User Response:

Plug-in failed to flush all rows.

The PowerCenter Integration Service could not write rows to Source Qualifier buffers. Run the session again. If the session fails again, contact Informatica Global Customer Support

TPTRD_21218
Explanation: User Response:

Error occurred during Export...

EXPORT system operator failed to get data from the Teradata tables. Run the session again.

TPTRD_21219
Explanation: User Response:

Unknown Error in TPTReaderPartition::run()

Internal error. Contact Informatica Global Customer Support.

TPTRD_21220
Explanation: User Response:

Invalid TDPID.
Invalid host name. Make sure that you specify the correct TDPID in the connection object.

22

Appendix A: Error Messages

TPTRD_21301
Explanation: User Response:

Plug-in failed to initialize Teradata PT Reader component.

Reader plug-in initialization failed. Validate the mapping and run the session again.

TPTRD_21302
Explanation: User Response:

Plug-in failed to retrieve Source Qualifier metadata object.

The session failed to initialize because the Source Qualifier instance could not be fetched from the mapping. Re-create the mapping or run the session again.

TPTRD_21501
Explanation: User Response:

Plug-in failed to initialize Teradata PT Reader Partition Driver.

Reader partition driver initialization failed. Run the session again. If the session fails again, contact Informatica Global Customer Support.

TPTRD_21502
Explanation: User Response:

Plug-in failed to retrieve Teradata Parallel Transporter connection information.

Connection object has some invalid parameters. Verify that all attributes in the connection object are appropriate.

TPTRD_21503
Explanation: User Response:

Plug-in failed to retrieve Session-level information.

The PowerCenter Integration Service cannot retrieve the session attributes. Verify that all attributes in the sources session object are valid.

TPTRD_21504
Explanation: User Response:

Plug-in failed to retrieve Metadata Extension information.

The PowerCenter Integration Service cannot retrieve the Source Qualifier attributes. Verify that all attributes in the Source Qualifier are valid.

TPTRD_21505
Explanation: User Response:

Plug-in failed to retrieve Source Qualifier and its field information.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21506
Explanation: User Response:

Plug-in failed to build DML statement.

The PowerCenter Integration Service could not create the DML statement for data extraction. Verify that the custom SQL is correct. Verify that field names and table names are same as in the Teradata table definition.

TPTRD_21507
Explanation: User Response:

Plug-in failed to create TPTAPI class instance.

The system does not have enough memory to allocate to the Teradata PT API object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTRD_21508
Explanation: User Response:

Plug-in failed to create connection to Teradata database.

Internal error. Contact Informatica Global Customer Support.

TPTRD Messages

23

TPTRD_21509
Explanation: User Response:

Plug-in failed to read data from table <table name> of Teradata database.
Internal error. Contact Informatica Global Customer Support.

TPTRD_21510
Explanation: User Response:

Plug-in failed to validate Session level DML statement <DML_statement>.

The custom SQL in the session properties is incorrect. Verify that the custom SQL is correct.

TPTRD_21511
Explanation: User Response:

Plug-in failed to validate Metadata Extension level DML statement <DML statement>.
The custom SQL in the Source Qualifier is incorrect. Verify that the custom SQL is correct.

TPTRD_21512
Explanation: User Response:

Plug-in failed to build Default DML statement.

The PowerCenter Integration Service could not build the DML statement for data extraction. The port business names may not match the table definition. Verify that the ports are defined correctly in the mapping.

TPTRD_21513
Explanation: User Response:

Multiple groups <group_ count> not supported.

The Source Qualifier contains multiple groups. Update the mapping so that the Source Qualifier contains a single group.

TPTRD_21514
Explanation: User Response:

Plug-in failed to retrieve Source Qualifier field list.

The PowerCenter Integration Service cannot get the Source Qualifier or sources field list and field information. Verify that the mapping fields are defined correctly.

TPTRD_21515
Explanation: User Response:

Plug-in failed to retrieve C-datatype of field <field name>.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21516
Explanation: User Response:

Plug-in failed to retrieve datatype of field <field name>.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21517
Explanation: User Response:

Plug-in failed to retrieve source extension attached with particular source qualifier.
Internal error. Contact Informatica Global Customer Support.

TPTRD_21518
Explanation: User Response:

Plug-in failed to retrieve connection reference associated with particular partition.

Internal error. Contact Informatica Global Customer Support.

24

Appendix A: Error Messages

TPTRD_21519
Explanation: User Response:

Plug-in failed to retrieve connection object associated with a connection reference.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21520
Explanation: User Response:

Plug-in failed to retrieve TDPID.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21521
Explanation: User Response:

Plug-in failed to retrieve Database Name.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21522
Explanation: User Response:

Plug-in failed to retrieve Tenacity.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21523
Explanation: User Response:

Plug-in failed to retrieve Max Sessions.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21524
Explanation: User Response:

Plug-in failed to retrieve Sleep.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21525
Explanation: User Response:

Plug-in failed to retrieve Block Size.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21526
Explanation: User Response:

Plug-in failed to retrieve Encrypt Data flag.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21527
Explanation: User Response:

Invalid Sql Query.

The SQL query in the custom SQL field is invalid. Enter a SQL query using Teradata SQL. Make sure that the SQL defined in custom SQL field is valid Teradata SQL.

TPTRD_21528
Explanation: User Response:

Plug-in failed to get the list of sources in the mapping.

Internal error. Contact Informatica Global Customer Support.

TPTRD_21529
Explanation:

Number of Max Sessions must be greater than 0.

The Max Sessions attribute for a Teradata PT connection object is set to an illegal value.

TPTRD Messages

25

User Response:

Update the Max Sessions attribute and then restart the session.

TPTRD_21530
Explanation: User Response:

Sleep must be greater than 0.

The Sleep attribute for a Teradata PT connection object is set to an illegal value. Update the Sleep attribute and then restart the session.

TPTRD_21531
Explanation: User Response:

Tenacity must be greater than or equal to 0.

The Tenacity attribute for a Teradata PT connection object is set to an illegal value. Update the Tenacity attribute and then restart the session.

TPTRD_21532
Explanation: User Response:

The minimum 256 bytes and maximum 64000 bytes Block Size is required.
The Block Size attribute for a Teradata PT connection object is set to an illegal value. Update the Block Size attribute and then restart the session.

TPTRD_21533
Explanation: User Response:

No of sorted Ports more than the No of Output fields.

The Number of Sorted Ports attribute in the Teradata PT source properties exceeds the number of output fields. Update the Number of Sorted Ports for the Teradata source and then restart the session.

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>.
The PowerCenter Integration Service could not get the values of some session-level properties. A system error might have occurred or the repository might have inconsistencies. Fix the operating system error. Contact Informatica Global Customer Support.

TPTWR Messages
TPTWR_11001
Explanation: User Response:

Plug-in failed to create the TPTLogging class object.

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.

TPTWR_11002
Explanation: User Response:

Plug-in failed to convert Code Page to Unicode.

Internal error. Contact Informatica Global Customer Support.

TPTWR_11003
Explanation: User Response:

Plug-in failed to convert Unicode to Code Page.

Internal error. Contact Informatica Global Customer Support.

26

Appendix A: Error Messages

TPTWR_31101
Explanation: User Response:

Plug-in failed to retrieve Trace level from session.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31201
Explanation: User Response:

Plug-in failed to set ILog logger.

The system does not have enough memory to allocate to the ILog logging object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31202
Explanation: User Response:

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.

TPTWR_31203
Explanation: User Response:

Plug-in failed to set System Operator.

The system does not have enough memory to allocate to the System operator. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31204
Explanation: User Response:

Plug-in failed to set TDPID.

The system does not have enough memory to allocate to the host 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.

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_31206
Explanation: User Response:

Plug-in failed to set Password.

The system does not have enough memory to allocate to the password. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31207
Explanation: User Response:

Plug-in failed to set Working Database.

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.

TPTWR_31208
Explanation: User Response:

Plug-in failed to set Table Name.

The system does not have enough memory to allocate to the table name. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR Messages

27

TPTWR_31209
Explanation: User Response:

Plug-in failed to set Error Database Name.

The system does not have enough memory to allocate to error database name. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31210
Explanation: User Response:

Plug-in failed to set Error Table 1 Name.

The system does not have enough memory to allocate to Error Table 1 name. 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.

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_31212
Explanation: User Response:

Plug-in failed to set Log Database Name.

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.

TPTWR_31213
Explanation: User Response:

Plug-in failed to set Log Table Name.

The system does not have enough memory to allocate to the log table 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 INSERT statement. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31215
Explanation: User Response:

Plug-in failed to set Update DML Statement.

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.

TPTWR_31216
Explanation: User Response:

Plug-in failed to set Delete DML Statement.

The system does not have enough memory to allocate to the delete DML statement. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

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 TRUNCATE TABLE statement. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

28

Appendix A: Error Messages

TPTWR_31218
Explanation: User Response:

Plug-in failed to create Teradata database connection object.

The system does not have enough memory to allocate to the Teradata Parallel Transporter connection object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31219
Explanation: User Response:

Plug-in failed to create Schema for Table <table_name>.

Schema defined in the mapping is incorrect. Validate or re-create the mapping. Verify that the column names, precision, and scale match the table definition.

TPTWR_31220
Explanation: User Response:

Plug-in failed to create DML Group <DML group name>.

The system does not have enough memory to allocate to the DML group. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31221
Explanation: User Response:

Plug-in failed to Initiate Teradata database connection.

Initiate method of Teradata Parallel Transporter connection object failed. Check the error message returned by Teradata CLI or DBS. Contact Informatica Global Customer Support.

TPTWR_31222
Explanation: User Response:

Plug-in failed to allocate memory to Connection object.

The system does not have enough memory to allocate to the connection object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31223
Explanation: User Response:

Plug-in failed to allocate memory to Schema object.

The system does not have enough memory to allocate to the schema object. 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>.

The system does not have enough memory to allocate to the DML group. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31225
Explanation: User Response:

Plug-in failed to commit the Connection object.

The PowerCenter Integration Service cannot commit the connection object. Check the DBS/CLI error message for more information.

TPTWR_31226
Explanation: User Response:

Plug-in failed in End Acquisition.

The PowerCenter Integration Service failed in end acquisition. Check the DBS/CLI error message for more information.

TPTWR Messages

29

TPTWR_31227
Explanation: User Response:

Plug-in failed to Apply rows.

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.
DML group built is invalid. Contact Informatica Global Customer Support.

TPTWR_31229
Explanation: User Response:

Plug-in failed to put row in Teradata database.

Sending row data request for insert, update, or delete to the Teradata database failed. Drop the error and log tables if they exist in database, and restart the session.

TPTWR_31230
Explanation: User Response:

Plug-in failed to put buffer in Teradata database.

Sending a buffer data for the insert operation to Teradata database failed. Drop the error and log tables if they exist in database, and restart the session.

TPTWR_31231
Explanation: User Response:

Plug-in failed to retrieve buffer layout for PutBuffer method.

Unable to get information about buffer size, row header, row length, and row trailer in LOAD system operator. Drop the error and log tables if they exist in database, and restart the session.

TPTWR_31232
Explanation: User Response:

Plug-in failed to retrieve affected rows.

Unable to get the number of affected rows and number of rejected rows from Teradata database. Drop the error and log tables if they exist in database, and restart the session.

TPTWR_31233
Explanation: User Response:

Truncate Table: Plug-in failed to create Teradata database connection object.

When there is no sufficient memory to allocate to the Teradata database connection object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31234
Explanation: User Response:

Truncate Table: Plug-in failed to create Schema for Table <table_name>.

Memory is not sufficient to allocate. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31235
Explanation: User Response:

Truncate Table: Plug-in failed to create DML Group <DML_Group_name>.

Memory is not sufficient to allocate. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31236
Explanation:

Truncate Table: Plug-in failed to Initiate Teradata database connection.

Unable to create a connection with Teradata database in Update drive for truncate table.

30

Appendix A: Error Messages

User Response:

Drop the error and log tables if they exist in database, and restart the session.

TPTWR_31237
Explanation: User Response:

Plug-in failed to set Update Recovery_Table DML Statement.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31238
Explanation: User Response:

Plug-in failed to set Insert Recovery_Table DML Statement.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31239
Explanation: User Response:

Plug-in failed to set Delete Recovery_Table DML Statement.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31240
Explanation: User Response:

Unable to support multiple group.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31301
Explanation: User Response:

Plug-in failed to initialize Teradata PT Writer Plug-in.

Writer plug-in initialization failed. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31302
Explanation: User Response:

Plug-in failed to create Target Drivers.

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.

TPTWR_31303
Explanation: User Response:

Plug-in failed to retrieve Target Instance.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31304
Explanation: User Response:

Invalid Target Index <target_index>.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31401
Explanation: User Response:

Plug-in failed to initialize Teradata PT Writer Target Driver.

Writer target driver initialization failed. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31402
Explanation:

Plug-in failed to create Group Drivers.

The system does not have enough memory to allocate to the group drivers.

TPTWR Messages

31

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31403
Explanation: User Response:

Plug-in failed to retrieve Group list.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31404
Explanation: User Response:

Invalid Group Index <group index>.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31501
Explanation: User Response:

Plug-in failed to initialize Teradata PT Writer Group Driver.

Writer Group driver initialization failed. 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.

The system does not have enough memory to allocate to the partition drivers. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31503
Explanation: User Response:

Invalid Partition Index <partition_index>.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31601
Explanation: User Response:

Plug-in failed to initialize Teradata PT Writer Partition Driver.

Writer partition driver initialization failed. Validate the mapping, and then run the session again.

TPTWR_31602
Explanation: User Response:

Plug-in failed to retrieve Row statistics information.

Failure in Teradata PT API call. Contact Informatica Global Customer Support.

TPTWR_31603
Explanation: User Response:

Plug-in failed to retrieve Teradata Parallel Transporter connection and session level attributes.
Connection object has some invalid parameters. Check whether all attributes in the connection object are correct.

TPTWR_31604
Explanation: User Response:

Plug-in failed to retrieve table information.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31605
Explanation:

Plug-in failed to build DML statements on table <table name> for system operator <system operator name>.
The system does not have enough memory to allocate to the DML statement.

32

Appendix A: Error Messages

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31606
Explanation:

Plug-in failed to build Truncate Table DML statement.

The system does not have enough memory to allocate to the Truncate Table DML statement. The PowerCenter Integration Service cannot read target table information from vector.

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31607
Explanation:

Plug-in failed to build INSERT DML statement.

The system does not have enough memory to allocate to the Insert statement. The PowerCenter Integration Service cannot read target table information from vector.

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31608
Explanation:

Plug-in failed to build UPDATE DML statement.

The system does not have enough memory to allocate to the Update DML statement. The PowerCenter Integration Service cannot read target table information from vector.

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.

The system does not have enough memory to allocate to the Delete DML statement. The PowerCenter Integration Service cannot read target table information from vector.

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>. Cannot build DELETE DML Statement.
Row type is deleted and no primary key is defines in the target table. Define a primary key in the target table and restart the session.

TPTWR_31611
Explanation: User Response:

Primary key is defined for all fields of table <table_name>. Cannot build UPDATE DML Statement.
The entire field in target table is primary key and no other column exists for update. Make sure you have at least one column for update.

TPTWR_31612
Explanation: User Response:

Primary Key is not defined for any of the fields of table <table_name>. Cannot build UPDATE DML Statement.
Row type is update and no primary key is defined in the target table. Define a primary key in the target table and restart the session.

TPTWR_31613
Explanation:

Plug-in failed to retrieve Truncate Table attribute.

Internal error.

TPTWR Messages

33

User Response:

Contact Informatica Global Customer Support.

TPTWR_31614
Explanation: User Response:

Plug-in failed to retrieve Update Else Insert attribute.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31615
Explanation: User Response:

Plug-in failed to retrieve connection reference associated with particular partition...

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_31617
Explanation: User Response:

Plug-in failed to retrieve Working Database.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31618
Explanation: User Response:

Plug-in failed to retrieve TDPID.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31619
Explanation: User Response:

Plug-in failed to Retrieve System Operator.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31620
Explanation: User Response:

Plug-in failed to retrieve Log Table Name.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31621
Explanation: User Response:

Plug-in failed to retrieve Log Database Name.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31622
Explanation: User Response:

Plug-in failed to retrieve Error Database Name.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31623
Explanation: User Response:

Plug-in failed to retrieve Error Table 1 Name.

Internal error. Contact Informatica Global Customer Support.

34

Appendix A: Error Messages

TPTWR_31624
Explanation: User Response:

Plug-in failed to retrieve Error Table 2 Name.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31625
Explanation: User Response:

Plug-in failed to retrieve Max Sessions.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31626
Explanation: User Response:

Plug-in failed to retrieve Tenacity.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31627
Explanation: User Response:

Plug-in failed to retrieve Sleep.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31628
Explanation: User Response:

Plug-in failed to retrieve Base Address for each field.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31629
Explanation: User Response:

Plug-in failed to retrieve commit Teradata database connection object.

Teradata internal error. Contact Informatica Global Customer Support.

TPTWR_31630
Explanation: User Response:

Plug-in failed while Data Manipulation.

See the additional error message for more information. Contact Informatica Global Customer Support.

TPTWR_31631
Explanation: User Response:

Plug-in failed to allocate Memory.

The system does not have enough memory to allocate to an object. Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running.

TPTWR_31632
Explanation: User Response:

Plug-in failed to retrieve data indicator.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31633
Explanation: User Response:

Update Operation is not allowed for LOAD system operator.

As system operator is LOAD and row type is Update. Update operation is not allowed in LOAD system operator.

TPTWR_31634
Explanation:

Delete Operation is not allowed for LOAD system operator.

As system operator is LOAD and row type is Update.

TPTWR Messages

35

User Response:

Delete operation is not allowed in LOAD system operator.

TPTWR_31635
Explanation: User Response:

Plug-in failed to truncate table.

The PowerCenter Integration Service cannot delete all rows of the target table. Review the session log and Teradata PT log tables for related messages. Drop the error and log tables, and restart the session.

TPTWR_31636
Explanation: User Response:

Number of Max Sessions must be greater than 0.

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.

TPTWR_31637
Explanation: User Response:

Sleep must be greater than 0.

The Sleep attribute for a Teradata PT connection object is set to an illegal value. Update the Sleep attribute and then restart the session.

TPTWR_31638
Explanation: User Response:

TENACITY must be greater than or equal to 0.

The Tenacity attribute for a Teradata PT connection object is set to an illegal value. Update the Tenacity attribute and then restart the session.

TPTWR_31639
Explanation: User Response:

Block size must be greater than 0.

The Block Size attribute for a Teradata PT connection object is set to an illegal value. Update the Block Size attribute and then restart the session.

TPTWR_31640
Explanation: User Response:

Failed to register TPTRecStorageFactory, recovery will not be supported.

Internal error. Contact Informatica Global Customer Support.

TPTWR_31641
Explanation: User Response:

Failed to initiate TPTRecStorageFactory, recovery will not be supported.

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 initiate the connection with Teradata PT. For example, the Teradata user name or password might be incorrect. Review the session log and Teradata PT log tables for related messages.

TPTWR_34701
Explanation:

Failed to initialize TPTWriterConnection.

An error occurred when the PowerCenter Integration Service tried to initialize the connection with the Teradata PT writer. For example, a network problem might have occurred during initialization. Review the session log and Teradata PT log tables for related messages.

User Response:

36

Appendix A: Error Messages

TPTWR_34702
Explanation:

Failed to deinitialize TPTConnectionManager.

An error occurred when the PowerCenter Integration Service tried to deinitialize the connection with the Teradata PT writer. For example, a network problem might have occurred during deinitialization. Review the session log and Teradata PT log tables for related messages.

User Response:

TPTWR_34703
Explanation:

Failed to commit for target <name> and partition <number>.

An error occurred when Teradata PT tried to issue a commit against the Teradata database. For example, 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 connection errors.

User Response:

TPTWR_34704
Explanation: User Response:

Rollback is not supported for Teradata Parallel Transporter writer.

The Teradata framework requested a rollback for a failed transaction, but Teradata PT does not support rollback for failed transactions. Review the session log and Teradata PT log tables to find the failed transaction. Check the target tables for data discrepancies.

TPTWR_34723
Explanation: User Response:

Initialization of TPT connection for reading recovery information failed.

An error occurred when the PowerCenter Integration Service tried to initialize the connection with Teradata PT for reading recovery information. 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 reading recovery information. Review the session log and Teradata PT log tables for related connection errors.

TPTWR_34727
Explanation: User Response:

Initialization of TPT connection for deleting recovery information failed.

An error occurred when the PowerCenter Integration Service tried to initialize the connection with Teradata PT for deleting recovery information. Review the session log and Teradata PT log tables for related connection errors.

TPTWR_34729
Explanation: User Response:

Termination of TPT connection for deleting recovery information failed.

An error occurred when the PowerCenter Integration Service tried to terminate the connection with Teradata PT for deleting recovery information. Review the session log and Teradata PT log tables for related connection errors.

TPTWR_34730
Explanation: User Response:

Selection of DML statement failed in connection for deleting recovery information.

A connection error occurred when the PowerCenter Integration Service tried to delete recovery information. Review the session log and Teradata PT log tables for related connection errors.

TPTWR Messages

37

TPTWR_34731
Explanation: User Response:

Acquisition failed in connection for deleting recovery information.

A connection error occurred when the PowerCenter Integration Service tried to delete recovery information. 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. Review the session log and Teradata PT log tables for related connection errors.

TPTWR_35001
Explanation: User Response:

ODBC Connection failed to create INFARecoveryTable.

The target ODBC connection could not create the recovery table in the Teradata target database due to a connection error. Review the session log for related connection errors.

TPTWR_35002
Explanation: User Response:

ODBC Connection failed to truncate target table <name> in load mode.

The target ODBC connection could not truncate the target table due to an error. Review the session log for related messages.

TPTWR_35003
Explanation: User Response:

ODBC Connection failed to drop error table.

The target ODBC connection could not drop the error table due to an error. Review the session log for related messages.

TPTWR_35004
Explanation: User Response:

ODBC Connection failed to drop log table.

The target ODBC connection could not drop the log table due to an error. Review the session log for related messages.

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>.
The PowerCenter Integration Service could not get the values of some session-level properties. A system error might have occurred or the repository might have inconsistencies. Fix the operating system error. Contact Informatica Global Customer Support.

TPTWR_36001
Explanation: User Response:

Connectivity license key for Teradata database is not valid.

The license key in the Administrator tool is invalid or does not contain Teradata PT connectivity option. Contact Informatica Global Customer Support to get a valid license key.

TPTWR_36002
Explanation: User Response:

The session uses a deprecated connection object. Replace it with a valid connection object.
The session uses a connection object of type Teradata Parallel Transporter Connection, which is deprecated. Replace the deprecated connection object with a connection object of type Teradata PT Connection.

38

Appendix A: Error Messages

INDEX

C
connections Teradata PT API 9 Teradata PT, 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, dropping 16

R
recovery Teradata PT API sessions 11 recovery tables Teradata PT API, creating automatically 11 Teradata PT, 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, description 12 Teradata PT, dropping 16

T
targets Teradata PT, 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, description 14 Teradata PT, dropping 16

39