179867590 PWXxcx 910 Teradata PT UserGuide

8/18/2019 179867590 PWXxcx 910 Teradata PT UserGuide

1/46

Informatica PowerExchange for Teradata Parallel Transporter API (Version 9.1.0)

User Guide


2/46

Informatica PowerExchange for Teradata Parallel Transporter API User Guide

Version 9.1.0March 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 anddisclosure 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 forby any means (electronic, photocopying, recording or otherwise) w ithout prior consent of Informatica Corporation. This Software may be protected by U.S. and/or internatioPatents 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 iDFARS 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 applica

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 inwriting.

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 OnDemand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and InformatMaster Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other compaand 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 rightsreserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rightsreserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright 2007 Isomorphic Software. All rights reserved. Copyright © MeIntegration 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. Arights 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 theLicense 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 copyright1999-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 httwww.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 notlimited 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, Irvineand 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 redistributionthis software is subject to terms available at http://www.openssl.org.

This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, . All Rights Reserved. Permissions and limitations regarding thissoftware 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 withoufee 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 availabat 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 termsavailable 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 thsoftware 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 httpwww.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 & WirelessDeutschland. 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 subto 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 termsavailable at http:// www.eclipse.org/org/documents/epl-v10.php.

This product includes software li censed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/d

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.orghttp://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3-licensagreement, 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 DistributionLicense (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 softwareare 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/.


3/46

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 impliedwarranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. Tinformation provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation issubject 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 SoftwareCorporation (“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 NOTLIMITED 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


4/46

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i i i

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 Paral lel Transpor ter API Overview. . . . . . . . . . . . . . . . . 1

Chapter 2: Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installation and Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installing and Configuring PowerExchange for Teradata Paral le l 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 Infor mation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

New Features and Enhancements in Version 9.1.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

New Features and Enhancements in Version 9.0.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Working with Deprecated Connection Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3: Teradata PT API Sessions and Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Configuring a Teradata Parallel Transporter API Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Creating a Teradata PT API Connection Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Working with Teradata PT API Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Configuring Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Working with Log, Error, and Work Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Pipeline Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Support for Multiple Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Staged Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring a Session for a Teradata PT API Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring a Session for a Teradata PT API Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Table of Contents i


5/46

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

TPTRD Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

TPTWR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

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

ii Table of Contents


6/46

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 Informat ica 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 DocumentationThe 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 andeducation, and implementation services.

Informatica How-To Library

As an Informatica customer, you can access the Informat ica 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

http://www.informatica.com/http://mysupport.informatica.com/http://www.informatica.com/http://mysupport.informatica.com/mailto:[email protected]://mysupport.informatica.com/


7/46

Informatica Knowledge Base

As an Informatica customer, you can access the Informat ica 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 Informat ica 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 requiresa 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 Europe / Middle East / Africa Asia / Australia

Toll Free

Brazil: 0800 891 0202Mexico: 001 888 209 8853

North America: +1 877 463 2435

Standard Rate

North America: +1 650 653 6332

Toll Free

France: 00800 4632 4357Germany: 00800 4632 4357

Israel: 00800 4632 4357Italy: 800 915 985

Netherlands: 00800 4632 4357Portugal: 800 208 360Spain: 900 813 166

Switzerland: 00800 4632 4357 or 0800 463200United Kingdom: 00800 4632 4357 or 0800

023 4632

Standard Rate

France: 0805 804632Germany: 01805 702702

Netherlands: 030 6022 797

Toll Free

Austra lia: 1 800 151 830New Zealand: 1 800 151 830

Singapore: 001 800 4632 4357

Standard Rate

India: +91 80 4112 5738

iv Preface

http://mysupport.informatica.com/mailto:[email protected]://mysupport.informatica.com/mailto:[email protected]://mysupport.informatica.com/


8/46

C H A P T E R 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 ParallelTransporter 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

1


9/46

C H A P T E R 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- Te rad ata CLI v2- Teradata ODBC

- Teradata Generic Security Services- Teradata Parallel Transporter Data Connector Operator - Shared ICU Libraries for Teradata

2


10/46

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:

\server\bin

\server\bin\native\server\bin\RecoverySQL\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 ParallelTransporter API

To install and configure PowerExchange for Teradata Parallel Transporter API, complete the following steps:

1. Set system environment variables.

2. Install the components.

3. Register the plug-in.

After you instal l and configure PowerExchange for Teradata Parallel Transpor ter 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 followingenvironment variables:

Environment Variable Value

JAVA_HOME /java

JRE_HOME ${JAVA_HOME}/jre

PATH ${JAVA_HOME}/bin:${JRE_HOME}/bin:${PATH}

On UNIX, you must also set the following environment variables:

Environment Variable Value

COPERR Set to the location of the errmsg.cat file, for example, /usr/lib.

TD_ICU_DATA Set to the locat ion o f the Terada ta ICU l ib ra ries , for example, /opt /tdicu /l ib .

Setting Environment Variables 3


11/46

Also, set the shared l ibrary environment variable based on the operating system. The fo llowing table describes the

shared library variables for each operating system:

Operating System Value

Windows PATH

Solaris LD_LIBRARY_PATH

Linux LD_LIBRARY_PATH

AIX LIBPA TH

HP-UX 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:


$ 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:


$ 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 ParallelTransporter 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 inthe 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.

4 Chapter 2: Installation and Configuration


12/46

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:

\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:

\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. Close all other applications before running the installation.

2. Stop Informatica Services if they are running on the machine.

3. Run the installer from the following location:

\\install.exe

4. 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 5


13/46

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. Cl ick 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. Close all other applications.

2. 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.

3. 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. Press Enter.

5. 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. Choose the correct version of Teradata PT API on the Teradata PT Version panel and press Enter.

7. 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.

/server/bin/

Registering the Plug-in After you instal l PowerExchange for Teradata Paral lel Transporter API, regis ter 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.



14/46


15/46

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. Deprecatedconnection objects might not be supported in future versions of PowerExchange for Teradata Parallel Transporter

API.



16/46

C H A P T E R 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 APIConnection

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.

Addit ional ly, 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.

9


17/46

3. Select Teradata PT Connection, and then click OK.

The Relational Connection Editor dialog box appears.

4. Enter the properties for the connection:

Property Description

Name Co nnectio n name use d by the Workfl ow Man ager. Conne cti on name cannot con tain sp aces or

other special characters, except for the underscore.

User Name Database user name with the appropriate read and wr ite database permiss ions to access the

database.To define the user name in the parameter file, enter session parameter $ParamName 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.

Use Parameter inPassword

Indicates the password for the database user name is a session parameter, $ParamName. 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 Password for the database user name.

Code Page Code page associated with the database.

When you run session that extracts from a Teradata source, the code page of the Teradata PT API connecti on must be the sa me as the code page of the Te radata source .

5. Enter the connection attributes:

Attribute Description

TDPID The name of the Teradata database machine.

Database Name Teradata database name.If you do not enter a database name, Teradata PT API uses the default login database name.

Tenac it y Amount o f t ime, in hours, that Terada ta PT API con tinues tr ying to log on when the maximumnumber of operations runs on the Teradata database.

Must be a positive, non-zero integer. Default is 4.

Max Sessions Maximum number of sessions that Teradata PT API establishes with the Teradata database.Must be a positive, non-zero integer. Default is 4.

Min Sessions 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.

Sl eep Amoun t of time, in minu tes, that Terada ta PT API pa uses bef ore it re tri es to log on when themaximum number of operations runs on the Teradata database.Must be a positive, non-zero integer. Default is 6.

Data Encryption Enables full security encryption of SQL requests, responses, and data.Default is disabled.

Block Size Maximum block s ize, in by tes, Teradata PT API uses when i t returns data to the PowerCenter

Integration Service.

10 Chapter 3: Teradata PT API Sessions and Workflows


18/46

Attribute Description

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

Sys tem Opera to r Terada ta PT API opera to r t ype:

- 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 databasetables.

- 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 sessionsthat load data to Teradata.

Default is Stream.

6. Click OK.

Working with Teradata PT API SessionsWhen 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 ConnectionWhen 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


19/46


20/46

The following session properties allow you to specify log table information:


Log Database 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.

Log Table Name Name of the log table.If you do not specify a log table name, the PowerCenter Integration Service uses the name.INFA_LT_ . The exact table name appears in the session log.

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:


Error Database Name of the database that stores the error tables. If you do not enter an error database name inthe session properties or a database name in the connection object, Teradata PT API stores theerror tables under the user.

Erro r Tabl e Name 1 Name of the first error ta ble .If you do not specify a name for the first error table, the PowerCenter Integration Service uses the

name .INFA_ET1_ . The exact table name appears in the session log.

Erro r Tab le Name2 Name o f the second e rror tab le .If you do not specify a name for the second error table, the PowerCenter Integration Service usesthe name .INFA_ET2_ . The exact table name appears in the session

log.

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


21/46

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:


Work Table Database 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 worktables in the target database.

Work Table Name 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 tablename, the PowerCenter Integration Service uses the name.INFA _WT. The exact tab le name appears i n the session log.

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 Partition Type

Source Qualifier Pass-through

Teradata PT API Target 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.



22/46

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. Change the reader type to Teradata Parallel Transporter Reader in the Readers settings on the Mapping tab.

2. From the Connections settings on the Sources node, select a Teradata PT connection.

3. 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 t racing:


Driver Tracing Level Determines Teradata PT API trac ing at the dr iver 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 Notifyfeature.

¨ 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


23/46


Infrastructure Tracing Level 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 theoperator common library.

Default is TD_OFF.

You must enable the driver tracing level before you can enable the infrastructure tracinglevel.

Trace Fi le Name File name and path of the Teradata PT API trace f ile. Defaul t path is $PM_HOME. Defaul tfile name is _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 thetarget 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. Change the writer type to Teradata Parallel Transporter Writer in the Writers settings on the Mapping tab.

2. From the Connections settings on the Targets node, select a Teradata PT connection.



24/46

3. From the Connections settings on the Targets node of the Mapping tab, configure the following Teradata PT

API target properties:


Work TableDatabase

Name of the database that stores the work tables.

Work Table Name Name of the work table.

Macro Database 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 load ing d ata an d removes them from the database af ter Teradata PT A PI loads al l

rows to the target.If you do not specify a macro database, Teradata PT API stores the macros in the log database.

Pause Acquisition 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.

Ins tances The number of paral le l ins tances to load data into the Teradata PT API target.

Default is 1.

Query Band

Expression

The query band expression to be passed to the Teradata PT API.

A query band expression is a set of name-va lue pairs that identi fy a query’s orig inati ng source. Inthe expression, each name-value pair is separated by a semicolon and the expression ends with asemicolon. For example, ApplicationName=Informatica;Version=9.0.1;ClientUser=A;.

Update Else Insert 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 insertsor deletes.


Truncate Table 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 Loadsystem operator if you select a Teradata target ODBC connection.Default is disabled.

Mark Missing Rows 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 thetarget table, Teradata PT API marks the row as an error row.

Default is None.

Configuring a Session for a Teradata PT API Target 17


25/46


Mark DuplicateRows

Specifies how Teradata PT API handles duplicate rows when it attempts to insert or update rowsin 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 rowin 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 duplicaterow in the target table, Teradata PT API marks the row as an error row.

Default is For Insert.

Log Database Name of the database that s tores the log tables.

Log Table Name Name o f the restart log tab le .

Error Database Name of the database that s tores the er ror tables .

Error Table Name1 Name of the f irst error table.

Error TableName2 Name of the second error table.

Drop Log/Error/Work Tables

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.

Ser ia lize Uses the Teradata PT API ser ia lize mechanism to reduce locking overhead when you selec t theStream system operator.

Default is enabled.

Pack Number o f s ta tements to pack into a request when you select the Stream sys tem opera to r.

Must be a positive, nonzero integer.Default is 20. Minimum is 1. Maximum is 600.

Pack Maximum Causes Teradata PT API to determine the maximum number of statements to pack into a requestwhen you select the Stream system operator.


Buf fe rs Determines the max imum number of reques t buf fe rs that may be a llocated fo r the Terada ta PT

API j ob whe n you select the Stream system operator. Te radata PT API determine s the maximumnumber of request buffers according to the following formula:Max_Request_Buffers = Buffers * Number_Connected_Sessions

Must be a positive, nonzero integer.

Default is 3. Minimum is 2.

Error Limit Max imum 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.

Replication

Override

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.



26/46


Driver Tracing Level Determines Teradata PT API tracing at the driver level:- TD_OFF. Teradata PT API disables tracing.- TD_OPER. Teradata PT API enables tracing for driver-specific activities for Teradata.

- TD_OPER_ALL. Teradata PT API enables all driver-level tracing.

- TD_OPER_CLI. Teradata PT API enables tracing for 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.

InfrastructureTracing Level

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.

Trace File Name File name and path of the Teradata PT API trace file. Default path is $PM_HOME. Default filename is _timestamp. For example, LOAD_20091221.

Configuring a Session for a Teradata PT API Target 19


27/46

A P P E N D I X A

Error Messages

This appendix includes the following topics:

¨ TPTRD Messages, 20

¨ TPTWR Messages, 26

TPTRD Messages

TPTRD_11001 Plug-in failed to create the TPTLogging class object.

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

User Response: Make sure that there is enough memory on the machine where the PowerCenter Integration

Service is running.

TPTRD_11002 Plug-in failed to convert Code Page to Unicode.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

TPTRD_11003 Plug-in failed to convert Unicode to Code Page.



TPTRD_21101 Plug-in failed to retrieve Trace level from session.

Explanation: While initializing logging module, tracing level from session attributes cannot be retrieved.


TPTRD_21201 Plug-in failed to set ILog logger.

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


Service is running.

TPTRD_21202 Plug-in failed to set TPTLogging logger.


20


28/46


Service is running.

TPTRD_21203 Plug-in failed to set TDPID.

Explanation: The system does not have enough memory to allocate to the host name object.


Service is running.

TPTRD_21204 Plug-in failed to set User Name.

Explanation: The system does not have enough memory to allocate to the user name object.


Service is running.

TPTRD_21205 Plug-in failed to set Password.

Explanation: The system does not have enough memory to allocate to the password object.


Service is running.

TPTRD_21206 Plug-in failed to set Working Database.

Explanation: The system does not have enough memory to allocate to the database name object.


Service is running.

TPTRD_21207 Plug-in failed to set Table Name.

Explanation: The system does not have enough memory to allocate to the table name object.


Service is running.

TPTRD_21208 Plug-in failed to set DML Statement.

Explanation: The system does not have enough memory to allocate to the DML object.


Service is running.

TPTRD_21209 Plug-in failed to create Teradata database connection object.

Explanation: Connection attr ibutes are inval id.

User Response: Make sure all the connection attributes are correct.

TPTRD_21210 Plug-in failed to create Schema for Table .

Explanation: The schema defined in the mapping is incorrect .

User Response: Validate or re-create the mapping. Verify that the column names, precision, and scale are the

same as the table definition.

TPTRD_21211 Plug-in failed to Initiate Teradata database connection.

Explanation: Initiate method of Teradata Parallel Transporter connection object failed.

TPTRD Messages 21


29/46

User Response: Check the error message returned by Teradata CLI or DBS.

Contact Informatica Global Customer Support.

TPTRD_21212 Plug-in failed to allocate memory to Connection object.

Explanation: The system does not have enough memory to allocate to the Teradata Parallel Transporter connection object.

User Response: Make sure that there is enough memory on the PowerCenter Integration Service machine.

TPTRD_21213 Plug-in failed to allocate memory to Schema object.

Explanation: The system does not have enough memory to allocate to the Teradata Parallel Transporter

Schema object.

User Response: Make sure that there is enough memory on the PowerCenter Integration Service machine.

TPTRD_21214 No Fields defined to read data from.

Explanation: No ports mapped in the mapping.

User Response: Validate or re-create the mapping.

TPTRD_21215 Plug-in failed to fetch data on row with status .

Explanation: GetRow() cal l fai led on the row .


TPTRD_21216 Plug-in failed to retrieve DSQ C-datatype.

Explanation: The PowerCenter Integration Service cannot get the C-datatype for the Source Qualifier.

User Response: Check the datatype from the Source Qualifier list of datatypes.

TPTRD_21217 Plug-in failed to flush all rows.

Explanation: The PowerCenter Integration Service could not write rows to Source Qualifier buffers.

User Response: Run the session again. If the session fails again, contact Informatica Global Customer

Support

TPTRD_21218 Error occurred during Export...

Explanation: EXPORT system operator failed to get data from the Teradata tables.

User Response: Run the session again.

TPTRD_21219 Unknown Error in TPTReaderPartition::run()



TPTRD_21220 Invalid TDPID.

Explanation: Invalid host name.

User Response: Make sure that you specify the correct TDPID in the connection object.

22 Appendix A: Error Messages


30/46

TPTRD_21301 Plug-in failed to initialize Teradata PT Reader component.

Explanation: Reader p lug- in initial ization fai led.

User Response: Validate the mapping and run the session again.

TPTRD_21302 Plug-in failed to retrieve Source Qualifier metadata object.Explanation: The session failed to initialize because the Source Qualifier instance could not be fetched

from the mapping.

User Response: Re-create the mapping or run the session again.

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

Explanation: Reader parti tion dr iver in it ia lization fa iled.

User Response: Run the session again. If the session fails again, contact Informatica Global Customer

Support.

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

Explanation: Connect ion object has some invalid parameters.

User Response: Verify that all attributes in the connection object are appropriate.

TPTRD_21503 Plug-in failed to retrieve Session-level information.

Explanation: The PowerCenter Integration Service cannot retrieve the session attributes.

User Response: Verify that all attributes in the sources session object are valid.

TPTRD_21504 Plug-in failed to retrieve Metadata Extension information.

Explanation: The PowerCenter Integration Service cannot retrieve the Source Qualifier attributes.

User Response: Verify that all attributes in the Source Qualifier are valid.

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



TPTRD_21506 Plug-in failed to build DML statement.

Explanation: The PowerCenter Integration Service could not create the DML statement for data extraction.

User Response: Verify that the custom SQL is correct.

Verify that field names and table names are same as in the Teradata table definition.

TPTRD_21507 Plug-in failed to create TPTAPI class instance.

Explanation: The system does not have enough memory to allocate to the Teradata PT API object.


Service is running.

TPTRD_21508 Plug-in failed to create connection to Teradata database.



TPTRD Messages 23


31/46

TPTRD_21509 Plug-in failed to read data from table of Teradata database.



TPTRD_21510 Plug-in failed to validate Session level DML statement .Explanation: The custom SQL in the session properties is incorrect.


TPTRD_21511 Plug-in failed to validate Metadata Extension level DML statement .

Explanation: The custom SQL in the Source Quali fier is incorrect.


TPTRD_21512 Plug-in failed to build Default DML statement.

Explanation: The PowerCenter Integration Service could not build the DML statement for data extraction.

The port business names may not match the table definition.

User Response: Verify that the ports are defined correctly in the mapping.

TPTRD_21513 Multiple groups not supported.

Explanation: The Source Qualif ier contains multiple groups.

User Response: Update the mapping so that the Source Qualifier contains a single group.

TPTRD_21514 Plug-in failed to retrieve Source Qualifier field list.

Explanation: The PowerCenter Integration Service cannot get the Source Qualifier or sources field list and

field information.

User Response: Verify that the mapping fields are defined correctly.

TPTRD_21515 Plug-in failed to retrieve C-datatype of field .



TPTRD_21516 Plug-in failed to retrieve datatype of field .



TPTRD_21517 Plug-in failed to retrieve source extension attached with particular source qualifier.



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





32/46

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



TPTRD_21520 Plug-in failed to retrieve TDPID.Explanation: Internal error.


TPTRD_21521 Plug-in failed to retrieve Database Name.



TPTRD_21522 Plug-in failed to retrieve Tenacity.



TPTRD_21523 Plug-in failed to retrieve Max Sessions.



TPTRD_21524 Plug-in failed to retrieve Sleep.



TPTRD_21525 Plug-in failed to retrieve Block Size.



TPTRD_21526 Plug-in failed to retrieve Encrypt Data flag.



TPTRD_21527 Invalid Sql Query.

Explanation: The SQL query in the custom SQL field is invalid. Enter a SQL query using Teradata SQL.

User Response: Make sure that the SQL defined in custom SQL field is valid Teradata SQL.

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



TPTRD_21529 Number of Max Sessions must be greater than 0.

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

TPTRD Messages 25


33/46

User Response: Update the Max Sessions attribute and then restart the session.

TPTRD_21530 Sleep must be greater than 0.

Explanation: The Sleep attribute for a Teradata PT connection object is set to an illegal value.

User Response: Update the Sleep attribute and then restart the session.

TPTRD_21531 Tenacity must be greater than or equal to 0.

Explanation: The Tenacity attribute for a Teradata PT connection object is set to an illegal value.

User Response: Update the Tenacity attribute and then restart the session.

TPTRD_21532 The minimum 256 bytes and maximum 64000 bytes Block Size is required.

Explanation: The Block Size attribute for a Teradata PT connection object is set to an illegal value.

User Response: Update the Block Size attribute and then restart the session.

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

Explanation: The Number of Sorted Ports attribute in the Teradata PT source properties exceeds thenumber of output fields.

User Response: Update the Number of Sorted Ports for the Teradata source and then restart the session.

TPTRD_35061 The following system error occurred when the PowerCenter Integration Service tried to get

the values of some session attributes: .

Explanation: 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.

User Response: Fix the operating system error. Contact Informatica Global Customer Support.

TPTWR Messages

TPTWR_11001 Plug-in failed to create the TPTLogging class object.



Service is running.

TPTWR_11002 Plug-in failed to convert Code Page to Unicode.



TPTWR_11003 Plug-in failed to convert Unicode to Code Page.





34/46

TPTWR_31101 Plug-in failed to retrieve Trace level from session.



TPTWR_31201 Plug-in failed to set ILog logger.Explanation: The system does not have enough memory to allocate to the ILog logging object.


Service is running.

TPTWR_31202 Plug-in failed to set TPTLogging logger.



Service is running.

TPTWR_31203 Plug-in failed to set System Operator.

Explanation: The system does not have enough memory to allocate to the System operator.


Service is running.

TPTWR_31204 Plug-in failed to set TDPID.

Explanation: The system does not have enough memory to allocate to the host name.


Service is running.

TPTWR_31205 Plug-in failed to set User Name.

Explanation: The system does not have enough memory to allocate to the user name.


Service is running.

TPTWR_31206 Plug-in failed to set Password.

Explanation: The system does not have enough memory to allocate to the password.


Service is running.

TPTWR_31207 Plug-in failed to set Working Database.

Explanation: The system does not have enough memory to allocate to the Working database.


Service is running.

TPTWR_31208 Plug-in failed to set Table Name.

Explanation: The system does not have enough memory to allocate to the table name.


Service is running.

TPTWR Messages 27


35/46

TPTWR_31209 Plug-in failed to set Error Database Name.

Explanation: The system does not have enough memory to allocate to error database name.


Service is running.

TPTWR_31210 Plug-in failed to set Error Table 1 Name.

Explanation: The system does not have enough memory to allocate to Error Table 1 name.


Service is running.

TPTWR_31211 Plug-in failed to set Error Table 2 Name.

Explanation: The system does not have enough memory to allocate to Error Table 2 name.


Service is running.

TPTWR_31212 Plug-in failed to set Log Database Name.

Explanation: The system does not have enough memory to allocate to the log database name.


Service is running.

TPTWR_31213 Plug-in failed to set Log Table Name.

Explanation: The system does not have enough memory to allocate to the log table name.


Service is running.

TPTWR_31214 Plug-in failed to set Insert DML Statement.

Explanation: The system does not have enough memory to allocate to the INSERT statement.


Service is running.

TPTWR_31215 Plug-in failed to set Update DML Statement.

Explanation: The system does not have enough memory to allocate to the UPDATE statement.


Service is running.

TPTWR_31216 Plug-in failed to set Delete DML Statement.

Explanation: The system does not have enough memory to allocate to the delete DML statement.


Service is running.

TPTWR_31217 Plug-in failed to set Truncate Table DML Statement.

Explanation: The system does not have enough memory to allocate to the TRUNCATE TABLE statement.


Service is running.



36/46

TPTWR_31218 Plug-in failed to create Teradata database connection object.

Explanation: The system does not have enough memory to allocate to the Teradata Parallel Transporter

connection object.


Service is running.

TPTWR_31219 Plug-in failed to create Schema for Table .

Explanation: Schema def ined in the mapping is incorrect .

User Response: Validate or re-create the mapping. Verify that the column names, precision, and scale match

the table definition.

TPTWR_31220 Plug-in failed to create DML Group .

Explanation: The system does not have enough memory to allocate to the DML group.


Service is running.

TPTWR_31221 Plug-in failed to Initiate Teradata database connection.

Explanation: Initiate method of Teradata Parallel Transporter connection object failed.

User Response: Check the error message returned by Teradata CLI or DBS.

Contact Informatica Global Customer Support.

TPTWR_31222 Plug-in failed to allocate memory to Connection object.

Explanation: The system does not have enough memory to allocate to the connection object.


Service is running.

TPTWR_31223 Plug-in failed to allocate memory to Schema object.

Explanation: The system does not have enough memory to allocate to the schema object.


Service is running.

TPTWR_31224 Plug-in failed to allocate memory to DML Group .

Explanation: The system does not have enough memory to allocate to the DML group.


Service is running.

TPTWR_31225 Plug-in failed to commit the Connection object.

Explanation: The PowerCenter Integration Service cannot commit the connection object.

User Response: Check the DBS/CLI error message for more information.

TPTWR_31226 Plug-in failed in End Acquisition.

Explanation: The PowerCenter Integration Service failed in end acquisit ion.


TPTWR Messages 29


37/46

TPTWR_31227 Plug-in failed to Apply rows.

Explanation: The PowerCenter Integration Service cannot apply rows.


TPTWR_31228 Plug-in failed to set DML Group to connection object.Explanation: DML group built is invalid.


TPTWR_31229 Plug-in failed to put row in Teradata database.

Explanation: Sending row data request for insert, update, or delete to the Teradata database failed.

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

TPTWR_31230 Plug-in failed to put buffer in Teradata database.

Explanation: Sending a buffer data for the insert operation to Teradata database failed.


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

Explanation: Unable to get information about buffer size, row header, row length, and row trailer in LOAD

system operator.


TPTWR_31232 Plug-in failed to retrieve affected rows.

Explanation: Unable to get the number of affected rows and number of rejected rows from Teradata

database.


TPTWR_31233 Truncate Table: Plug-in failed

179867590 PWXxcx 910 Teradata PT UserGuide

Documents

Transcript of 179867590 PWXxcx 910 Teradata PT UserGuide