PowerExchange for Teradata Parallel Transporter …dbmanagement.info/Books/MIX/PWX_86_TeradataPT_UserGuide_TeraData.pdfInformatica PowerExchange for Teradata Parallel Transporter User

Informatica® PowerExchange for Teradata Parallel Transporter(Version 8.6)

User Guide

Informatica PowerExchange for Teradata Parallel Transporter User GuideVersion 8.6September 2008

Copyright (c) 2006–2008 Informatica Corporation. 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(c)(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, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Exchange and Informatica On Demand 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.

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.

Part Number: PWX-TPT-86000-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vInformatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Global Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

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

Chapter 2: Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing and Configuring PowerExchange for Teradata Parallel Transporter . . . . . . . . . . . 4

Setting Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installing PowerExchange for Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installing the Client Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installing the Service Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Registering the Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Release Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Working with Deprecated Connection Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 3: Teradata PT Sessions and Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Configuring a Teradata Parallel Transporter Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

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

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

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

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

Configuring a Session for a Teradata PT Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Configuring a Session for a Teradata PT Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Appendix A: Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17TPTRD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

TPTWR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table of Contents iii

iv Table of Contents

Preface

The Informatica PowerExchange for Teradata Parallel Transporter User Guide provides information about extracting data from and loading data to Teradata Parallel Transporter (Teradata PT). 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 PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, 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.

Informatica Web SiteYou 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 Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://my.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.

v

Informatica Global Customer SupportThere are many ways to access Informatica Global Customer Support. You can contact a Customer Support Center through telephone, email, or the WebSupport Service.

Use the following email addresses to contact Informatica Global Customer Support:

♦ [email protected] for technical inquiries

♦ [email protected] for general customer service requests

WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com.

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Informatica Corporation Headquarters100 Cardinal WayRedwood City, California 94063United States

Toll Free +1 877 463 2435

Standard RateBrazil: +55 11 3523 7761 Mexico: +52 55 1168 9763 United States: +1 650 385 5800

Informatica Software Ltd.6 Waltham ParkWaltham Road, White WalthamMaidenhead, BerkshireSL6 3TNUnited Kingdom

Toll Free 00 800 4632 4357

Standard RateBelgium: +32 15 281 702France: +33 1 41 38 92 26Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511 445

Informatica Business Solutions Pvt. Ltd.Diamond DistrictTower B, 3rd Floor150 Airport RoadBangalore 560 008India

Toll Free Australia: 1 800 151 830Singapore: 001 800 4632 4357

Standard RateIndia: +91 80 4112 5738

vi Preface

C H A P T E R 1

Understanding PowerExchange for Teradata Parallel Transporter

This chapter includes the following topic:

♦ Overview, 1

OverviewPowerExchange for Teradata Parallel Transporter integrates PowerCenter and Teradata Parallel Transporter (Teradata PT) 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 to read from Teradata sources and load to Teradata targets.

To use PowerExchange for Teradata Parallel Transporter, 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 Integration Service uses the Teradata PT 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

2 Chapter 1: Understanding PowerExchange for Teradata Parallel Transporter

C H A P T E R 2

Installation and Configuration

This chapter includes the following topics:

♦ Overview, 3

♦ Setting Environment Variables, 4

♦ Installing PowerExchange for Teradata Parallel Transporter, 5

♦ Registering the Plug-in, 7

♦ Release Information, 8

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

PrerequisitesBefore you install PowerExchange for Teradata Parallel Transporter, complete the following tasks:

♦ Install or upgrade PowerCenter.

♦ Install Teradata.

♦ Install Teradata Parallel Transporter.

♦ Install the following utilities on the machines where the Repository Service and Integration Service run:

Teradata Parallel Transporter version 8.2:

- Teradata Parallel Transporter API version 08.02.00.04 for Linux 32-bit, or Teradata Parallel Transporter API version 08.02.00.03 for other operating systems

- Teradata Parallel Transporter Load Operator version 08.02.00.02 or later- Teradata Parallel Transporter Update Operator version 08.02.00.02 or later- Teradata Parallel Transporter Stream Operator version 08.02.00.02 or later- Teradata Parallel Transporter Export Operator version 08.02.00.01 or later- Teradata Parallel Transporter Operator Support Library version 08.02.00.00 or later- Teradata CLIv2 version 04.08.02.00 or later- Teradata ODBC version 03.06.00.02- Shared ICU libraries for Teradata version 01.01.00.xx or 01.01.01.xx- Teradata GSS Client nt-i386 version 06.02

3

♦ Verify that you have read and write permissions on the following directories:

<PowerCenter Installation Directory>\server\bin<PowerCenter Installation Directory>\server\bin\native<PowerCenter Installation Directory>\server\bin\RecoverySQL<PowerCenter Installation Directory>\client\bin

The installer must be able to add and overwrite files in these directories.

♦ On UNIX, copy the PowerExchange for Teradata Parallel Transporter binaries, tptinstall and TeradataPT.bin, to the directory where you want to install PowerExchange for Teradata Parallel Transporter.

Installing and Configuring PowerExchange for Teradata Parallel Transporter

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

1. Set system environment variables. For more information, see “Setting Environment Variables” on page 4.

2. Install the components. Install the Client and Service components to access Teradata PT. For more information, see “Installing PowerExchange for Teradata Parallel Transporter” on page 5.

3. Register the plug-in. Register the plug-in with the repository. For more information, see “Registering the Plug-in” on page 7.

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

Setting Environment VariablesBefore you install the PowerExchange for Teradata Parallel Transporter Service component, set the following environment variables:

On UNIX, you must also set the following 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:

Environment Variable Value

JAVA_HOME JAVA_HOME <PowerCenter installation directory>/java

JRE_HOME JRE_HOME ${JAVA_HOME}/jre

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

Environment Variable Value

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

TD_ICU_DATA Set to the location of the Teradata ICU libraries, for example, /opt/tdicu/lib.

Operating System Value

Windows PATH

Solaris LD_LIBRARY_PATH

Linux LD_LIBRARY_PATH

4 Chapter 2: Installation and Configuration

For example, use the following syntax for Solaris:

♦ Using a Bourne shell:

$ LD_LIBRARY_PATH=${JAVA_HOME}/lib: ${JRE_HOME}/lib:${LD_LIBRARY_PATH}; export LD_LIBRARY_PATH

♦ Using a C shell:

$ setenv LD_LIBRARY_PATH ${JAVA_HOME}/lib: ${JRE_HOME}/lib:${LD_LIBRARY_PATH}; export LD_LIBRARY_PATH

For HP-UX:


$ SHLIB_PATH=${SHLIB_PATH}:${JAVA_HOME}/lib: ${JRE_HOME}/lib:${LD_LIBRARY_PATH}; export SHLIB_PATH


$ setenv SHLIB_PATH ${SHLIB_PATH}:${JAVA_HOME}/lib: ${JRE_HOME}/lib:${LD_LIBRARY_PATH}

For AIX:


$ LIBPATH=${LIBPATH}:${JAVA_HOME}/lib: ${JRE_HOME}/lib:${LD_LIBRARY_PATH}


$ setenv LIBPATH ${LIBPATH}:${JAVA_HOME}/lib: ${JRE_HOME}/lib:${LD_LIBRARY_PATH}

Installing PowerExchange for Teradata Parallel Transporter

When you install PowerExchange for Teradata Parallel Transporter, you install components that allow PowerCenter to access Teradata PT. Install the following components:

♦ Client component. Allows you to access online help for PowerExchange for Teradata Parallel Transporter.

♦ Service component. Allows the Repository Service access to the Teradata PT metadata in the repository. Also allows the Integration Service to run Teradata PT sessions.

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

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

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

These files are extracted to the following location:

<Download Location>\help\en

AIX LIBPATH

HP-UX SHLIB_PATH

Operating System Value

Installing PowerExchange for Teradata Parallel Transporter 5

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 ComponentInstall the Service component on any node configured to run the Integration Service or 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 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.

For more information about resources, see the PowerCenter Administrator Guide.

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:

<Download Location>\<Operating System Directory>\install.exe

The Welcome window introduces the PowerExchange for Teradata Parallel Transporter installation.

4. Click Next.

The installation program displays a warning about stopping Informatica Services.

5. Click OK.

The Installation Directory window appears.

6. 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\PowerCenter8.6.

7. Click Next.

The Pre-Installation Summary window summarizes the installation information.

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

9. Click Done.

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

10. Restart Informatica Services on the machine.


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 Service component installation files.

The Welcome panel introduces the PowerExchange for Teradata Parallel Transporter Service component installation.

3. Press Enter.

4. 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/PowerCenter8.6

HOME is the user home directory.

5. Review the information on the Pre-Installation Summary panel and press Enter to continue.

Or, enter back to go back and modify the options.

6. After you press Enter, the installer copies the Service component files to the installation directory.

<PowerCenter Installation Directory>/server/bin/

Registering the Plug-inAfter you install PowerExchange for Teradata Parallel Transporter, register the plug-in with the repository. A plug-in is an XML file that defines the functionality of PowerExchange for Teradata Parallel Transporter.

If you are upgrading from a previous version, update the plug-in registration when you register the plug-in.

To register the plug-in, the repository must be running in exclusive mode. Use the Administration Console or the pmrep RegisterPlugin command to register the plug-in.

The plug-in file for PowerExchange for Teradata Parallel Transporter is TeradataPT.xml. When you install the Service component, the installer copies TeradataPT.xml to the following directory:

<PowerCenter Installation Directory>\server\bin\native

For more information about using the Administration Console to register a plug-in, see the PowerCenter Administrator Guide.

For more information about the pmrep RegisterPlugin command, see the PowerCenter Command Reference.

Note: If you do not have the correct privileges to register the plug-in, contact the user who manages the Repository Service.

Registering the Plug-in 7

Release Information

Working with Deprecated Connection Objects

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

In a previous version, PowerExchange for Teradata Parallel Transporter used Teradata PT 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 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.

Upgrade Impact: Behavior Change, Upgrade TaskVersion Implemented: 8.6Versions Affected: 8.1.1


C H A P T E R 3

Teradata PT Sessions and Workflows

This chapter includes the following topics:

♦ Configuring a Teradata Parallel Transporter Connection, 9

♦ Working with Teradata PT Sessions, 11

♦ Configuring a Session for a Teradata PT Source, 14

♦ Configuring a Session for a Teradata PT Target, 14

Configuring a Teradata Parallel Transporter ConnectionCreate Teradata PT connection objects to define connections to Teradata PT in the repository. The Integration Service uses Teradata PT connection objects to read from or write to Teradata PT.

If you enable recovery in a session that writes to Teradata PT, you might also want to create a Teradata target ODBC connection. Create an ODBC connection when you do not want to create the recovery table manually. For more information about enabling a Teradata PT session for recovery, see “Configuring Recovery” on page 11.

Creating a Teradata PT Connection ObjectYou configure Teradata Parallel Transporter properties when you create a Teradata PT connection. You can override the system operator in the session properties.

For more information about Teradata PT 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.

9

4. Enter the properties for the connection:

5. Enter the connection attributes:

6. Click OK.

Property Description

Name Connection name used by the Workflow Manager. Connection name cannot contain spaces or other special characters, except for the underscore.

User Name 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 $ParamName as the user name, and define the value in the session or workflow parameter file. The Integration Service interprets user names that start with $Param as session parameters.

Use Parameter in Password

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.

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 uses the default login database name.

Tenacity Amount of time, in hours, that Teradata PT 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.

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

Min Sessions Minimum number of Teradata PT sessions required for the Teradata PT job to continue.Must be a positive integer between 1 and the Max Sessions value. Default is 1.

Sleep Amount of time, in minutes, that Teradata PT 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.

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

Block Size Maximum block size, in bytes, Teradata PT uses when it returns data to the Integration Service.Minimum is 256. Maximum is 64,330. Default is 64,000.

System Operator Teradata PT 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 PT.

Default is Stream.

10 Chapter 3: Teradata PT Sessions and Workflows

Working with Teradata PT SessionsWhen you configure a Teradata PT session, you define properties that determine how the Integration Service extracts data from or loads data to Teradata PT. You can configure the following Teradata PT session properties:

♦ Recovery

♦ Error and log tables

♦ Pipeline partitioning

Configuring RecoveryYou can recover Teradata PT 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 PT.

♦ Set the TPTRecoveryModel custom property to “yes” for the session or Integration Service.

♦ If the Integration Service runs on UNIX, set the THREADONOFF environment variable to 1.

A recovery table must exist in the target database before the 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 target connection object. Configure a target ODBC connection when you want to drop log and error 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 target connection and a target ODBC connection in a session, the Integration Service creates the recovery table in the target database.

You can also configure the following session properties:

♦ Drop log and error tables. Log tables can contain inconsistent data when a session fails. If you configure the session to use a Teradata PT target connection and a target ODBC connection, the Integration Service can drop existing error and log tables for a session when the session starts.

♦ Truncate the target tables. Teradata PT 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 target connection and a target ODBC connection, Teradata PT can truncate the target tables when the system operator is Update, Stream, or Load.

Creating the Recovery Table ManuallyIf you enable recovery for a session that writes to Teradata PT, and you do not need to drop log and error 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 Teradata PT Sessions 11

Working with Error and Log TablesThe Integration Service uses error tables to log Teradata errors and rejected data when a session runs. It uses log tables to store Teradata PT restart and log information. Teradata PT creates two error tables and one log table for each partition.

Working with Error TablesThe Integration Service 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 Teradata PT connection. You can also choose to create the error tables in an error database, a working database, or under a Teradata user. Choose where you want to create the error tables when you configure a Teradata PT connection.

The following session properties allow you to specify error table names:

The complete error table name is based on where you choose to create the error tables and whether you enter error table names in the session properties. The Integration Service sets the error table name as follows:


Error Database 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, the Integration Service stores the error tables under the user.

Error Table Name1 Name of the first error table.

Error Table Name2 Name of the second error table.

Error Table Name1 or Name2 Specified

Error Database Name Specified

Complete Error Table Name

Yes Yes If you enter error table names and enter an error database name, the error table names are as follows:- Error Table Name1 = <error_database>.<error_table_name>_one_<N>- Error Table Name2 = <error_database>.<error_table_name>_two_<N>where <N> is the partition number.

Yes No If you enter error table names, and you choose to include the error tables under the working database or the user, the error table names are as follows:- Error Table Name1 = <error_table_name>_one_<N>- Error Table Name2 = <error_table_name>_two_<N>where <N> is the partition number.


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

Working with Log TablesEnter a log table name when you configure a Teradata PT connection. You can also choose to create the log table in a log database, a working database, or under a Teradata user. Choose where you want to create the log table when you configure a Teradata PT connection.

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

The complete log table name is based on where you choose to create the log table and whether you enter a log table name in the session properties. The Integration Service sets the log table name as follows:

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

No Yes If you do not enter error table names, and you enter an error database name, the error table names are as follows:- Error Table Name1 = <error_database>.<target_ table_name>

_ET_1_<N>- Error Table Name2 = <error_database>.<target_ table_name>

_ET_2_<N>where <N> is the partition number.

No No If you do not enter error table names, and you choose to include the error tables under the working database or the user, Teradata PT specifies the error table names in the working database. Teradata PT specifies different error table names for different system operators.


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, the Integration Service stores the log tables under the user.

Log Table Name Name of the log table.

Log Table Name Specified

Log Database Name Specified

Complete Log Table Name

Yes Yes If you enter the log table name and a log database name, the complete log table name is as follows:<log_database>.<log_table_name>_<N>where <N> is the partition number.

Yes No If you enter the log table name and a working database name, the complete log table name is as follows:<working_database>.<log_table_name>_<N>where <N> is the partition number.If you enter the log table name, and you do not enter working database name, the complete log table name is as follows:<user_name>.<log_table_name>_<N>where <N> is the partition number.

Error Table Name1 or Name2 Specified

Error Database Name Specified

Complete Error Table Name

Working with Teradata PT Sessions 13

Pipeline PartitioningYou can increase the number of partitions in a pipeline to improve session performance. Increasing the number of partitions allows the 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 reads from or writes to Teradata PT. If the session writes to Teradata PT, 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 sessions:

Configuring a Session for a Teradata PT SourceYou can configure a session to read from Teradata PT. When you run a Teradata PT session, you cannot use stored procedures, pushdown optimization, or row error logging. The Integration Service ignores source and source qualifier properties that you override in the session.

To configure a session to read from Teradata PT:

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.

Configuring a Session for a Teradata PT TargetYou can configure a session to write to Teradata PT. A Teradata PT session cannot use stored procedures, pushdown optimization, or row error logging. The 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. 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 and error 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.

Partition Point Partition Type

Source Qualifier Pass-through

Teradata PT Target Pass-through


To configure a session to write to Teradata PT:

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.

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


Update Else Insert Teradata PT updates existing rows and inserts other rows as if marked for update. If disabled, Teradata PT updates existing rows only.The Integration Service ignores this attribute when you treat source rows as inserts or deletes.Default is disabled.

Truncate Table Teradata PT 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.

Mark Missing Rows Specifies how Teradata PT handles rows that do not exist in the target table:- None. If Teradata PT receives a row marked for update or delete but it is

missing in the target table, Teradata PT does not mark the row in the error table.

- For Update. If Teradata PT receives a row marked for update but it is missing in the target table, Teradata PT marks the row as an error row.

- For Delete. If Teradata PT receives a row marked for delete but it is missing in the target table, Teradata PT marks the row as an error row.

- Both. If Teradata PT receives a row marked for update or delete but it is missing in the target table, Teradata PT marks the row as an error row.

Default is None.

Mark Duplicate Rows Specifies how Teradata PT handles duplicate rows when it attempts to insert or update rows in the target table:- None. If Teradata PT receives a row marked for insert or update that

causes a duplicate row in the target table, Teradata PT does not mark the row in the error table.

- For Insert. If Teradata PT receives a row marked for insert but it exists in the target table, Teradata PT marks the row as an error row.

- For Update. If Teradata PT receives a row marked for update that causes a duplicate row in the target table, Teradata PT marks the row as an error row.

- Both. If Teradata PT receives a row marked for insert or update that causes a duplicate row in the target table, Teradata PT marks the row as an error row.

Default is For Insert.

Log Database Name of the database that stores the log tables.

Log Table Name Name of the restart log table. For more information about the log table, see “Working with Log Tables” on page 13.

Error Database Name of the database that stores the error tables.

Error Table Name1 Name of the first error table. For more information about error tables, see “Working with Error Tables” on page 12.

Error TableName2 Name of the second error table. For more information about error tables, see “Working with Error Tables” on page 12.

Drop Log/Error Tables Drops existing log and error tables for a session when the session starts.This attribute is available if you select a Teradata target ODBC connection.Default is disabled.

Serialize Uses the Teradata PT serialize mechanism to reduce locking overhead when you select the Stream system operator.Default is enabled.

Configuring a Session for a Teradata PT Target 15

For more information about the Teradata PT properties, see the Teradata Parallel Transporter documentation.

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

Pack Maximum Causes Teradata PT to determine the maximum number of statements to pack into a request when you select the Stream system operator.Default is disabled.

Buffers Determines the maximum number of request buffers that may be allocated for the Teradata PT job when you select the Stream system operator. Teradata PT determines the maximum number of request buffers according to the following formula:Max_Request_Buffers = Buffers * Number_Connected_SessionsMust 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 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 overrides the normal replication services controls for an active Teradata PT session:- On. Teradata PT overrides normal replication services controls for the

active session.- Off. Teradata PT disables override of normal replication services for the

active session when change data capture is active.- None. Teradata PT does not send an override request to the Teradata

Database.Default is None.



A P P E N D I X A

Error Messages

This appendix includes the following topics:

♦ TPTRD Messages, 17

♦ TPTWR Messages, 22

TPTRD MessagesTPTRD_11001 Plug-in failed to create the TPTLogging class object.Cause: The system does not have enough memory to allocate to the logging object.

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

TPTRD_11002 Plug-in failed to convert Code Page to Unicode.Cause: Internal error.

Action: Contact Informatica Global Customer Support.

TPTRD_11003 Plug-in failed to convert Unicode to Code Page.Cause: Internal error.


TPTRD_21101 Plug-in failed to retrieve Trace level from session.Cause: While initializing logging module, tracing level from session attributes cannot be retrieved.


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


TPTRD_21202 Plug-in failed to set TPTLogging logger.Cause: The system does not have enough memory to allocate to the logging object.


17

TPTRD_21203 Plug-in failed to set TDPID.Cause: The system does not have enough memory to allocate to the host name object.


TPTRD_21204 Plug-in failed to set User Name.Cause: The system does not have enough memory to allocate to the user name object.


TPTRD_21205 Plug-in failed to set Password.Cause: The system does not have enough memory to allocate to the password object.


TPTRD_21206 Plug-in failed to set Working Database.Cause: The system does not have enough memory to allocate to the database name object.


TPTRD_21207 Plug-in failed to set Table Name.Cause: The system does not have enough memory to allocate to the table name object.


TPTRD_21208 Plug-in failed to set DML Statement.Cause: The system does not have enough memory to allocate to the DML object.


TPTRD_21209 Plug-in failed to create Teradata database connection object.Cause: Connection attributes are invalid.

Action: Make sure all the connection attributes are correct.

TPTRD_21210 Plug-in failed to create Schema for Table <table name>. Cause: The schema defined in the mapping is incorrect.

Action: 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.Cause: Initiate method of Teradata Parallel Transporter connection object failed.

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

-or-

Contact Informatica Global Customer Support.

TPTRD_21212 Plug-in failed to allocate memory to Connection object.Cause: The system does not have enough memory to allocate to the Teradata Parallel Transporter

connection object.

Action: Make sure that there is enough memory on the Integration Service machine.

18 Appendix A: Error Messages

TPTRD_21213 Plug-in failed to allocate memory to Schema object.Cause: The system does not have enough memory to allocate to the Teradata Parallel Transporter

Schema object.

Action: Make sure that there is enough memory on the Integration Service machine.

TPTRD_21214 No Fields defined to read data from.Cause: No ports mapped in the mapping.

Action: Validate or re-create the mapping.

TPTRD_21215 Plug-in failed to fetch data on row <row number> with status <status code>.Cause: GetRow() call failed on the row <row number>.


TPTRD_21216 Plug-in failed to retrieve DSQ C-datatype.Cause: The Integration Service cannot get the C-datatype for the Source Qualifier.

Action: Check the datatype from the Source Qualifier list of datatypes.

TPTRD_21217 Plug-in failed to flush all rows.Cause: The Integration Service could not write rows to Source Qualifier buffers.

Action: Run the session again. If the session fails again, contact Informatica Global Customer Support

TPTRD_21218 Error occurred during Export...Cause: EXPORT system operator failed to get data from the Teradata tables.

Action: Run the session again.

TPTRD_21219 Unknown Error in TPTReaderPartition::run()Cause: Internal error.


TPTRD_21220 Invalid TDPID.Cause: Invalid host name.

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

TPTRD_21301 Plug-in failed to initialize Teradata PT Reader component.Cause: Reader plug-in initialization failed.

Action: Validate the mapping and run the session again.

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

the mapping.

Action: Re-create the mapping or run the session again.

TPTRD_21501 Plug-in failed to initialize Teradata PT Reader Partition Driver.Cause: Reader partition driver initialization failed.

Action: Run the session again. If the session fails again, contact Informatica Global Customer Support.

TPTRD Messages 19

TPTRD_21502 Plug-in failed to retrieve Teradata Parallel Transporter connection information.Cause: Connection object has some invalid parameters.

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

TPTRD_21503 Plug-in failed to retrieve Session-level information.Cause: The Integration Service cannot retrieve the session attributes.

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

TPTRD_21504 Plug-in failed to retrieve Metadata Extension information.Cause: The Integration Service cannot retrieve the Source Qualifier attributes.

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

TPTRD_21505 Plug-in failed to retrieve Source Qualifier and its field information.Cause: Internal error.


TPTRD_21506 Plug-in failed to build DML statement.Cause: The Integration Service could not create the DML statement for data extraction.

Action: Verify that the custom SQL is correct.

-or-

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.Cause: The system does not have enough memory to allocate to the Teradata PT API object.


TPTRD_21508 Plug-in failed to create connection to Teradata database.Cause: Internal error.


TPTRD_21509 Plug-in failed to read data from table <table name> of Teradata database.Cause: Internal error.


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


TPTRD_21511 Plug-in failed to validate Metadata Extension level DML statement <DML statement>.Cause: The custom SQL in the Source Qualifier is incorrect.


TPTRD_21512 Plug-in failed to build Default DML statement.Cause: The Integration Service could not build the DML statement for data extraction. The port

business names may not match the table definition.

Action: Verify that the ports are defined correctly in the mapping.


TPTRD_21513 Multiple groups <group_ count> not supported.Cause: The Source Qualifier contains multiple groups.

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

TPTRD_21514 Plug-in failed to retrieve Source Qualifier field list.Cause: The Integration Service cannot get the Source Qualifier or sources field list and field

information.

Action: Verify that the mapping fields are defined correctly.

TPTRD_21515 Plug-in failed to retrieve C-datatype of field <field name>.Cause: Internal error.


TPTRD_21516 Plug-in failed to retrieve datatype of field <field name>.Cause: Internal error.


TPTRD_21517 Plug-in failed to retrieve source extension attached with particular source qualifier.Cause: Internal error.


TPTRD_21518 Plug-in failed to retrieve connection reference associated with particular partition.Cause: Internal error.


TPTRD_21519 Plug-in failed to retrieve connection object associated with a connection reference.Cause: Internal error.


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


TPTRD_21521 Plug-in failed to retrieve Database Name.Cause: Internal error.


TPTRD_21522 Plug-in failed to retrieve Tenacity.Cause: Internal error.


TPTRD_21523 Plug-in failed to retrieve Max Sessions.Cause: Internal error.


TPTRD_21524 Plug-in failed to retrieve Sleep.Cause: Internal error.


TPTRD Messages 21

TPTRD_21525 Plug-in failed to retrieve Block Size.Cause: Internal error.


TPTRD_21526 Plug-in failed to retrieve Encrypt Data flag.Cause: Internal error.


TPTRD_21527 Invalid Sql Query.Cause: The SQL query in the custom SQL field is invalid. Enter a SQL query using Teradata SQL.

Action: 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.Cause: Internal error.


TPTRD_21529 Number of Max Sessions must be greater than 0.Cause: The Max Sessions attribute for a Teradata PT connection object is set to an illegal value.

Action: Update the Max Sessions attribute and then restart the session.

TPTRD_21530 Sleep must be greater than 0.Cause: The Sleep attribute for a Teradata PT connection object is set to an illegal value.

Action: Update the Sleep attribute and then restart the session.

TPTRD_21531 Tenacity must be greater than or equal to 0.Cause: The Tenacity attribute for a Teradata PT connection object is set to an illegal value.

Action: Update the Tenacity attribute and then restart the session.

TPTRD_21532 The minimum 256 bytes and maximum 64000 bytes Block Size is required.Cause: The Block Size attribute for a Teradata PT connection object is set to an illegal value.

Action: Update the Block Size attribute and then restart the session.

TPTRD_21533 No of sorted Ports more than the No of Output fields.Cause: The Number of Sorted Ports attribute in the Teradata PT source properties exceeds the number

of output fields.

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

TPTWR MessagesTPTWR_11001 Plug-in failed to create the TPTLogging class object.Cause: The system does not have enough memory to allocate to the logging object.



TPTWR_11002 Plug-in failed to convert Code Page to Unicode.Cause: Internal error.


TPTWR_11003 Plug-in failed to convert Unicode to Code Page.Cause: Internal error.


TPTWR_31101 Plug-in failed to retrieve Trace level from session.Cause: Internal error.


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


TPTWR_31202 Plug-in failed to set TPTLogging logger.Cause: The system does not have enough memory to allocate to the logging object.


TPTWR_31203 Plug-in failed to set System Operator.Cause: The system does not have enough memory to allocate to the System operator.


TPTWR_31204 Plug-in failed to set TDPID.Cause: The system does not have enough memory to allocate to the host name.


TPTWR_31205 Plug-in failed to set User Name.Cause: The system does not have enough memory to allocate to the user name.


TPTWR_31206 Plug-in failed to set Password.Cause: The system does not have enough memory to allocate to the password.


TPTWR_31207 Plug-in failed to set Working Database.Cause: The system does not have enough memory to allocate to the Working database.


TPTWR Messages 23

TPTWR_31208 Plug-in failed to set Table Name.Cause: The system does not have enough memory to allocate to the table name.


TPTWR_31209 Plug-in failed to set Error Database Name.Cause: The system does not have enough memory to allocate to error database name.


TPTWR_31210 Plug-in failed to set Error Table 1 Name.Cause: The system does not have enough memory to allocate to Error Table 1 name.


TPTWR_31211 Plug-in failed to set Error Table 2 Name.Cause: The system does not have enough memory to allocate to Error Table 2 name.


TPTWR_31212 Plug-in failed to set Log Database Name.Cause: The system does not have enough memory to allocate to the log database name.


TPTWR_31213 Plug-in failed to set Log Table Name.Cause: The system does not have enough memory to allocate to the log table name.


TPTWR_31214 Plug-in failed to set Insert DML Statement.Cause: The system does not have enough memory to allocate to the INSERT statement.


TPTWR_31215 Plug-in failed to set Update DML Statement.Cause: The system does not have enough memory to allocate to the UPDATE statement.


TPTWR_31216 Plug-in failed to set Delete DML Statement.Cause: The system does not have enough memory to allocate to the delete DML statement.


TPTWR_31217 Plug-in failed to set Truncate Table DML Statement.Cause: The system does not have enough memory to allocate to the TRUNCATE TABLE statement.



TPTWR_31218 Plug-in failed to create Teradata database connection object.Cause: The system does not have enough memory to allocate to the Teradata Parallel Transporter

connection object.


TPTWR_31219 Plug-in failed to create Schema for Table <table_name>.Cause: Schema defined in the mapping is incorrect.

Action: 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 <DML group name>.Cause: The system does not have enough memory to allocate to the DML group.


TPTWR_31221 Plug-in failed to Initiate Teradata database connection.Cause: Initiate method of Teradata Parallel Transporter connection object failed.

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

-or-

Contact Informatica Global Customer Support.

TPTWR_31222 Plug-in failed to allocate memory to Connection object.Cause: The system does not have enough memory to allocate to the connection object.


TPTWR_31223 Plug-in failed to allocate memory to Schema object.Cause: The system does not have enough memory to allocate to the schema object.


TPTWR_31224 Plug-in failed to allocate memory to DML Group <DML group name>.Cause: The system does not have enough memory to allocate to the DML group.


TPTWR_31225 Plug-in failed to commit the Connection object.Cause: The Integration Service cannot commit the connection object.

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

TPTWR_31226 Plug-in failed in End Acquisition.Cause: The Integration Service failed in end acquisition.


TPTWR_31227 Plug-in failed to Apply rows.Cause: The Integration Service cannot apply rows.


TPTWR Messages 25

TPTWR_31228 Plug-in failed to set DML Group <DML group name> to connection object.Cause: DML group built is invalid.


TPTWR_31229 Plug-in failed to put row in Teradata database.Cause: Sending row data request for insert, update, or delete to the Teradata database failed.

Action: 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.Cause: Sending a buffer data for the insert operation to Teradata database failed.


TPTWR_31231 Plug-in failed to retrieve buffer layout for PutBuffer method.Cause: 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.Cause: Unable to get the number of affected rows and number of rejected rows from Teradata database.


TPTWR_31233 Truncate Table: Plug-in failed to create Teradata database connection object.Cause: When there is no sufficient memory to allocate to the Teradata database connection object.


TPTWR_31234 Truncate Table: Plug-in failed to create Schema for Table <table_name>.Cause: Memory is not sufficient to allocate.


TPTWR_31235 Truncate Table: Plug-in failed to create DML Group <DML_Group_name>.Cause: Memory is not sufficient to allocate.


TPTWR_31236 Truncate Table: Plug-in failed to Initiate Teradata database connection.Cause: Unable to create a connection with Teradata database in Update drive for truncate table.


TPTWR_31237 Plug-in failed to set Update Recovery_Table DML Statement.Cause: Internal error.


TPTWR_31238 Plug-in failed to set Insert Recovery_Table DML Statement.Cause: Internal error.



TPTWR_31239 Plug-in failed to set Delete Recovery_Table DML Statement.Cause: Internal error.


TPTWR_31240 Unable to support multiple group.Cause: Internal error.


TPTWR_31301 Plug-in failed to initialize Teradata PT Writer Plug-in.Cause: Writer plug-in initialization failed.


TPTWR_31302 Plug-in failed to create Target Drivers.Cause: The system does not have enough memory to allocate to the target drivers.


TPTWR_31303 Plug-in failed to retrieve Target Instance.Cause: Internal error.


TPTWR_31304 Invalid Target Index <target_index>.Cause: Internal error.


TPTWR_31401 Plug-in failed to initialize Teradata PT Writer Target Driver.Cause: Writer target driver initialization failed.


TPTWR_31402 Plug-in failed to create Group Drivers.Cause: The system does not have enough memory to allocate to the group drivers.


TPTWR_31403 Plug-in failed to retrieve Group list.Cause: Internal error.


TPTWR_31404 Invalid Group Index <group index>.Cause: Internal error.


TPTWR_31501 Plug-in failed to initialize Teradata PT Writer Group Driver.Cause: Writer Group driver initialization failed.


TPTWR Messages 27

TPTWR_31502 Plug-in failed to create Partition Drivers.Cause: The system does not have enough memory to allocate to the partition drivers.


TPTWR_31503 Invalid Partition Index <partition_index>.Cause: Internal error.


TPTWR_31601 Plug-in failed to initialize Teradata PT Writer Partition Driver.Cause: Writer partition driver initialization failed.

Action: Validate the mapping, and then run the session again.

TPTWR_31602 Plug-in failed to retrieve Row statistics information.Cause: Failure in Teradata PT API call.


TPTWR_31603 Plug-in failed to retrieve Teradata Parallel Transporter connection and session level attributes.Cause: Connection object has some invalid parameters.

Action: Check whether all attributes in the connection object are correct.

TPTWR_31604 Plug-in failed to retrieve table information.Cause: Internal error.


TPTWR_31605 Plug-in failed to build DML statements on table <table name> for system operator <system operator name>.

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


TPTWR_31606 Plug-in failed to build Truncate Table DML statement.Cause: The system does not have enough memory to allocate to the Truncate Table DML statement.

-or-

The Integration Service cannot read target table information from vector.


TPTWR_31607 Plug-in failed to build INSERT DML statement.Cause: The system does not have enough memory to allocate to the Insert statement.

-or-



TPTWR_31608 Plug-in failed to build UPDATE DML statement.Cause: The system does not have enough memory to allocate to the Update DML statement.

-or-




TPTWR_31609 Plug-in failed to build DELETE DML statement.Cause: The system does not have enough memory to allocate to the Delete DML statement.

-or-



TPTWR_31610 Primary Key is not defined for any of the fields of table <table_name>. Cannot build DELETE DML Statement.

Cause: Row type is deleted and no primary key is defines in the target table.

Action: Define a primary key in the target table and restart the session.

TPTWR_31611 Primary key is defined for all fields of table <table_name>. Cannot build UPDATE DML Statement.

Cause: The entire field in target table is primary key and no other column exists for update.

Action: Make sure you have at least one column for update.

TPTWR_31612 Primary Key is not defined for any of the fields of table <table_name>. Cannot build UPDATE DML Statement.

Cause: Row type is update and no primary key is defined in the target table.

Action: Define a primary key in the target table and restart the session.

TPTWR_31613 Plug-in failed to retrieve Truncate Table attribute.Cause: Internal error.


TPTWR_31614 Plug-in failed to retrieve Update Else Insert attribute.Cause: Internal error.


TPTWR_31615 Plug-in failed to retrieve connection reference associated with particular partition...Cause: Internal error.


TPTWR_31616 Plug-in failed to retrieve connection object associated with a connection reference...Cause: Internal error.


TPTWR_31617 Plug-in failed to retrieve Working Database.Cause: Internal error.


TPTWR Messages 29

TPTWR_31618 Plug-in failed to retrieve TDPID.Cause: Internal error.


TPTWR_31619 Plug-in failed to Retrieve System Operator.Cause: Internal error.


TPTWR_31620 Plug-in failed to retrieve Log Table Name.Cause: Internal error.


TPTWR_31621 Plug-in failed to retrieve Log Database Name.Cause: Internal error.


TPTWR_31622 Plug-in failed to retrieve Error Database Name.Cause: Internal error.


TPTWR_31623 Plug-in failed to retrieve Error Table 1 Name.Cause: Internal error.


TPTWR_31624 Plug-in failed to retrieve Error Table 2 Name.Cause: Internal error.


TPTWR_31625 Plug-in failed to retrieve Max Sessions.Cause: Internal error.


TPTWR_31626 Plug-in failed to retrieve Tenacity.Cause: Internal error.


TPTWR_31627 Plug-in failed to retrieve Sleep.Cause: Internal error.


TPTWR_31628 Plug-in failed to retrieve Base Address for each field.Cause: Internal error.


TPTWR_31629 Plug-in failed to retrieve commit Teradata database connection object.Cause: Teradata internal error.



TPTWR_31630 Plug-in failed while Data Manipulation.Cause: See the additional error message for more information.


TPTWR_31631 Plug-in failed to allocate Memory.Cause: The system does not have enough memory to allocate to an object.


TPTWR_31632 Plug-in failed to retrieve data indicator.Cause: Internal error.


TPTWR_31633 Update Operation is not allowed for LOAD system operator.Cause: As system operator is LOAD and row type is Update.

Action: Update operation is not allowed in LOAD system operator.

TPTWR_31634 Delete Operation is not allowed for LOAD system operator.Cause: As system operator is LOAD and row type is Update.

Action: Delete operation is not allowed in LOAD system operator.

TPTWR_31635 Plug-in failed to truncate table.Cause: The Integration Service cannot delete all rows of the target table.

Action: Review the session log and Teradata PT log tables for related messages. Drop the error and log tables, and restart the session.

TPTWR_31636 Number of Max Sessions must be greater than 0.Cause: The Max Sessions attribute for a Teradata PT connection object is set to an illegal value.

Action: Update the Max Sessions attribute and then restart the session.

TPTWR_31637 Sleep must be greater than 0.Cause: The Sleep attribute for a Teradata PT connection object is set to an illegal value.

Action: Update the Sleep attribute and then restart the session.

TPTWR_31638 TENACITY must be greater than or equal to 0.Cause: The Tenacity attribute for a Teradata PT connection object is set to an illegal value.

Action: Update the Tenacity attribute and then restart the session.

TPTWR_31639 Block size must be greater than 0.Cause: The Block Size attribute for a Teradata PT connection object is set to an illegal value.

Action: Update the Block Size attribute and then restart the session.

TPTWR_31640 Failed to register TPTRecStorageFactory, recovery will not be supported.Cause: Internal error.


TPTWR Messages 31

TPTWR_31641 Failed to initiate TPTRecStorageFactory, recovery will not be supported.Cause: Internal error.


TPTWR_31642 Failed to initiate TPTConnectionManager.Cause: An error occurred when the Integration Service tried to initiate the connection with

Teradata PT. For example, the Teradata user name or password might be incorrect.

Action: Review the session log and Teradata PT log tables for related messages.

TPTWR_34701 Failed to initialize TPTWriterConnection.Cause: An error occurred when the Integration Service tried to initialize the connection with the

Teradata PT writer. For example, a network problem might have occurred during initialization.


TPTWR_34702 Failed to deinitialize TPTConnectionManager.Cause: An error occurred when the Integration Service tried to deinitialize the connection with the

Teradata PT writer. For example, a network problem might have occurred during deinitialization.


TPTWR_34703 Failed to commit for target <name> and partition <number>.Cause: 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.

Action: Review the session log and Teradata PT log tables for related connection errors.

TPTWR_34704 Rollback is not supported for Teradata Parallel Transporter writer.Cause: The Teradata framework requested a rollback for a failed transaction, but Teradata PT does not

support rollback for failed transactions.

Action: Review the session log and Teradata PT log tables to find the failed transaction. Check the target tables for data discrepancies.

TPTWR_34723 Initialization of TPT connection for reading recovery information failed.Cause: An error occurred when the Integration Service tried to initialize the connection with

Teradata PT for reading recovery information.


TPTWR_34725 Termination of TPT connection for reading recovery information failed.Cause: An error occurred when the Integration Service tried to terminate the connection with

Teradata PT for reading recovery information.


TPTWR_34727 Initialization of TPT connection for deleting recovery information failed.Cause: An error occurred when the Integration Service tried to initialize the connection with

Teradata PT for deleting recovery information.



TPTWR_34729 Termination of TPT connection for deleting recovery information failed.Cause: An error occurred when the Integration Service tried to terminate the connection with

Teradata PT for deleting recovery information.


TPTWR_34730 Selection of DML statement failed in connection for deleting recovery information.Cause: A connection error occurred when the Integration Service tried to delete recovery information.


TPTWR_34731 Acquisition failed in connection for deleting recovery information.Cause: A connection error occurred when the Integration Service tried to delete recovery information.


TPTWR_34732 PutRow call failed in connection for deleting recovery information.Cause: A connection error occurred when the Integration Service tried to delete recovery information.


TPTWR_35001 ODBC Connection failed to create INFARecoveryTable.Cause: The target ODBC connection could not create the recovery table in the Teradata target database

due to a connection error.

Action: Review the session log for related connection errors.

TPTWR_35002 ODBC Connection failed to truncate target table <name> in load mode.Cause: The target ODBC connection could not truncate the target table due to an error.

Action: Review the session log for related messages.

TPTWR_35003 ODBC Connection failed to drop error table.Cause: The target ODBC connection could not drop the error table due to an error.


TPTWR_35004 ODBC Connection failed to drop log table.Cause: The target ODBC connection could not drop the log table due to an error.


TPTWR_36001 Connectivity license key for Teradata database is not valid.Cause: The license key in the Administration Console is invalid or does not contain Teradata PT

connectivity option.

Action: Contact Informatica Global Customer Support to get a valid license key.

TPTWR Messages 33


I N D E X

Cconnections

Teradata PT 9Teradata PT, deprecated 8

Eenvironment variables

Teradata PT, setting 4error messages

TPTRD 17TPTWR 22

error tablesTeradata PT 12

Llog tables

Teradata PT 13

Ppartitioning

Teradata PT sessions 14plug-ins

registering PowerExchange for Teradata Parallel Transporter 7PowerExchange for Teradata Parallel Transporter

behavior changes 8installing and configuring 4

prerequisitesPowerExchange for Teradata Parallel Transporter 3

Rrecovery

Teradata PT sessions 11recovery tables

Teradata PT, creating automatically 11Teradata PT, creating manually 11

Ssessions

configuring to read from Teradata PT 14configuring to write to Teradata PT 14

Ttargets

Teradata PT, primary key columns 14Teradata PT connections

creating 9deprecated connection objects 8

35

36 Index

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.

Documents

PowerExchange for Teradata Parallel Transporter …dbmanagement.info/Books/MIX/PWX_86_TeradataPT_UserGuide_TeraData.pdfInformatica PowerExchange for Teradata Parallel Transporter User