Tera data install guide for linux

Teradata Tools and UtilitiesInstallation Guide for UNIX® and Linux

Release 13.10B035-2459-020A

August 2010

The product or products described in this book are licensed products of Teradata Corporation or its affiliates.

Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You’ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates.

Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.

AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.

BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc.

EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.

GoldenGate is a trademark of GoldenGate Software, Inc.

Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.

Intel, Pentium, and XEON are registered trademarks of Intel Corporation.

IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation.

Linux is a registered trademark of Linus Torvalds.

LSI and Engenio are registered trademarks of LSI Corporation.

Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries.

Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.

QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation.

SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.

SPARC is a registered trademark of SPARC International, Inc.

Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries.

Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries.

Unicode is a collective membership mark and a service mark of Unicode, Inc.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other product and company names mentioned herein may be the trademarks of their respective owners.

THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN “AS-IS” BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country.

Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice.

To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please e-mail: [email protected]

Any comments or materials (collectively referred to as “Feedback”) sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback.

Copyright © 1996-2010 by Teradata Corporation. All Rights Reserved.

mailto:[email protected]

Preface

Purpose

This book provides information about installing the Teradata Tools and Utilities Release 13.10 software on a computer that runs on UNIX® and Linux operating systems. Teradata Tools and Utilities is a group of products designed to work with Teradata Database.

Audience

This book is intended for use by:

• System and application programmers

• System administrators

• Database administrators and relational database developers

• System operators and other database specialists

Supported Releases

This book supports the following releases:

• Teradata Database 13.10.00

• Teradata Tools and Utilities 13.10.00

To locate detailed supported-release information:

1 Go to http://www.info.teradata.com.

2 Under Online Publications, click General Search.

3 Type 3119 in the Publication Product ID box.

4 Under Sort By, select Date.

5 Click Search.

6 Open the version of the Teradata Tools and Utilities ##.##.## Supported Platforms and Product Versions spreadsheet associated with this release.

The spreadsheet includes supported Teradata Database versions, platforms, and product release numbers.

Teradata Tools and Utilities Installation Guide for UNIX and Linux 3

http://www.info.teradata.com

PrefacePrerequisites

Prerequisites

The following prerequisite knowledge is required for this product:

• Computer technology and terminology

• Relational database management systems

• Utilities that load and retrieve data

Changes to This Book

The following changes were made to this book in support of the current release. Changes are marked with change bars. For a complete list of changes to the product, see the Teradata Tools and Utilities Release Definition associated with this release.

Date and Release Description

August 2010

13.10

The following changes were made to support Teradata Tools and Utilities 13.10 installation:

• Added ARC 64-bit information Linux native 64-bit.

• Added NLSPATH to the ODBC Configuration.

February 2010

13.10


• Total Manual redesign.

• Ported ODBC Driver for Teradata to 64-bit HP.

• Ported Call-Level Interface version 2 to 32-bit on ia64.

• Ported Teradata MQ Access Module to 32-bit on ia64.

• Ported Named Pipes Access Module to 32-bit on ia64.

• Ported Call-Level Interface version 2 to Linux for OS/390.

• Ported Named Pipes Access Module to Linux for OS/390.

• Ported PP2 to Linux for OS/390.

• Ported Teradata Data Connector to Linux for OS/390.

• Ported Teradata FastExport to Linux for OS/390.

• Ported Teradata FastLoad to Linux for OS/390.

• Ported Teradata MultiLoad to Linux for OS/390.

• Ported Teradata TPump to Linux for OS/390.

• Ported Teradata Parallel Transport to Linux for OS/390.

• Ported Teradata MQ Access Module to Linux for OS/390.

• Updated support for TQS Client.

• Consolidated several installation procedures from individual guides to this document.

• Documented change to Red Hat 3.0 compiler.

4 Teradata Tools and Utilities Installation Guide for UNIX and Linux

PrefaceAdditional Information

Additional Information

Additional information that supports this product and Teradata Tools and Utilities is available at the web sites listed in the table that follows. In the table, mmyx represents the publication date of a manual, where mm is the month, y is the last digit of the year, and x is an internal publication code. Match the mmy of a related publication to the date on the cover of this book. This ensures that the publication selected supports the same release.

February 2010

13.10 (continued)


• Documented tar script for deploying products across a network.

• Discontinued support for z/VM.

• Discontinued support for MP-RAS.

• Discontinued support for AIX 5.1 and 5.2.

• Discontinued Teradata MultiTool.

• Removed ODBC Driver for Teradata from Tape Storage Enablers CD.

• Added ARC installation to documentation.

• Added information about using SPNEGO.

• Removed information on xctl from documentation.

• Changed product release numbering scheme.

• Changed ODBC documentation concerning LIBPATH.

• Included information about downloading compat lib in SUSE 10.

August 2008

13.00


• Reduced the number of Teradata Parallel Transport products from 15 to 6.

• The Tivoli Access Module is no longer included on the Tape Storage Management Enabler CD.

• For those Client products that have both a 32-bit and a 64-bit installation package, both versions can co-exist on an EM64T system.

• When a Client product that has both a 32-bit and a 64-bit installation package and is installed silently on an EM64T system, both the 32-bit and the 64-bit versions will be installed. If the Client product is installed interactively, only the 64-bit version is installed.

• Earlier versions of installed Client products are now automatically uninstalled as part of the installation.

• Changes to support the new Teradata Corporation branding that include a new splash screen, copyright, license text, and logo.

• A new directory structure for the Teradata Tools and Utilities 13.00.00 client products where the default location is now:

%Program Files%\Teradata\Client\13.0\<product>

Date and Release Description



Type of Information Description Access to Information

Release overview

Late information

Use the Release Definition for the following information:

• Overview of all of the products in the release

• Information received too late to be included in the manuals

• Operating systems and Teradata Database versions that are certified to work with each product

• Version numbers of each product and the documentation for each product

• Information about available training and the support center

1 Go to http://www.info.teradata.com/.

2 Under Online Publications, click General Search.

3 Type 2029 in the Publication Product ID box.

4 Click Search.

5 Select the appropriate Release Definition from the search results.


http://www.info.teradata.com/


Additional product information

Use the Teradata Information Products web site to view or download specific manuals that supply related or additional information to this manual.


2 Under the Online Publications subcategory, Browse by Category, click Data Warehousing.

3 Do one of the following:

• For a list of Teradata Tools and Utilities documents, click Teradata Tools and Utilities, and then select an item under Releases or Products.

• Select a link to any of the data warehousing publications categories listed.

Specific books related to Teradata Call-Level Interface Version 2 for Channel-Attached Systems are as follows:

• MessagesB035-1096-mmyA

• Teradata Tools and Utilities Command SummaryB035-2401-mmyA

• Teradata JDBC Driver User GuideB035-2403-mmyA

• Teradata Tools and Utilities Installation Guide for Microsoft WindowsB035-2407-mmyA

• Teradata MultiLoad ReferenceB035-2409-mmyA

• Teradata FastExport ReferenceB035-2410-mmyA

• Teradata FastLoad ReferenceB035-2411-mmyA

• Teradata Archive/Recovery Utility ReferenceB035-2412-mmyA

• Basic Teradata Query ReferenceB035-2414-mmyA

• Teradata Director Program ReferenceB035-2416-mmyA





• (Continued from the bulleted list above) in the Publication Product ID field, enter one of the following book numbers:

• Teradata Call-Level Interface Version 2 Reference for Channel-Attached SystemsB035-2417-mmyA

• Teradata Call-Level Interface Version 2 Reference for Network-Attached SystemsB035-2418-mmyA

• Teradata Transparency Series/ Application Programming Interface User GuideB035-2419-mmyA

• Teradata Tools and Utilities Access Module Programmer Guide B035-2424-mmyA

• Teradata Tools and Utilities Access Module Reference B035-2425-mmyA

• Teradata SQL Assistant for Microsoft Windows User GuideB035-2430-mmyA

• Teradata Parallel Transporter ReferenceB035-2436-mmyA

• Teradata Access Module for Tivoli Installation and User GuideB035-2444-mmyA

• Teradata Parallel Transporter User GuideB035-2445-mmyA

• Teradata Preprocessor2 for Embedded SQL Programmer GuideB035-2446-mmyA

• Interactive Teradata Query ReferenceB035-2451-mmyA

• Interactive Teradata Query User GuideB035-2452-mmyA

• Teradata Tools and Utilities Installation Guide for IBM z/OSB035-2458-mmyA

• Teradata Tools and Utilities Installation Guide for UNIX and LinuxB035-2459-mmyA




• (Continued from the bulleted list above) in the Publication Product ID field, enter one of the following book numbers:

• Teradata System Emulation Tool User GuideB035-2492-mmyA

• OLE DB Provider for Teradata Installation and User GuideB035-2498-mmyA

• Teradata Administrator User GuideB035-2502-mmyA

• Teradata Statistics Wizard User GuideB035-2503-mmyA

• Teradata Visual Explain User GuideB035-2504-mmyA

• Teradata Index Wizard User GuideB035-2506-mmyA

• ODBC Driver for Teradata User GuideB035-2509-mmyA

• Teradata Query Director User GuideB035-2510-mmyA

• Teradata Query Scheduler Administrator GuideB035-2511-mmyA

• Teradata Query Scheduler User GuideB035-2512-mmyA

• Teradata Workload Analyzer User GuideB035-2514-mmyA

• Teradata Parallel Transporter Application Programming Interface Programmer GuideB035-2516-mmyA

• Teradata Parallel Data Pump ReferenceB035-3021-mmyA

• Teradata Meta Data Services Installation and Administration GuideB035-3118-mmyA

• Teradata Meta Data Services Programmer GuideB035-3047-mmyA

CD-ROM images Access a link to a downloadable CD-ROM image of all customer documentation for this release. Customers are authorized to create CD-ROMs for their use from this image.


2 Under the Online Publications subcategory, Browse by Category, click Data Warehousing.

3 Click CD-ROM List and Images.

4 Follow the ordering instructions.

Ordering information for manuals

Use the Teradata Information Products web site to order printed versions of manuals.


2 Under Print & CD Publications, click How to Order.

3 Follow the ordering instructions.






General information about Teradata

The Teradata home page provides links to numerous sources of information about Teradata. Links include:

• Executive reports, case studies of customer experiences with Teradata, and thought leadership

• Technical information, solutions, and expert advice

• Press releases, mentions, and media resources

1 Go to Teradata.com.

2 Select a link.



http://www.teradata.com/t/resources

Table of Contents

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Changes to This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Chapter 1: Linux and UNIX Operating Systems General Install . . . . . . . . . . 25

General Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Instructions for Installing Across a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Instructions for Installing Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 2: Installing to Linux from CD Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Step 1: Inspect the Installation Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Inspect the Installation Kit CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Step 2: Review Platforms, Products, Dependencies and Requirements. . . . . . . . . . . . . . . . . . 27

Determine if Platforms and Products are Compatible . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Read Product Descriptions and Determine Product Dependencies . . . . . . . . . . . . . . . . . 27

Determine if System Requirements have been Met . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Step 3: Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . 28

Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . 28

Step 4: Install Third-Party Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Install Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Step 5: Install Teradata Tools and Utilities from the CD Media . . . . . . . . . . . . . . . . . . . . . . . 30

Install Teradata Tools and Utilities on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Step 6: Install Drivers from the Teradata Download Center . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Step 7: Install Patches from the Teradata Software Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


Table of Contents

Step 8: Add CLI User Exit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Step 9: Install Teradata Meta Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Step 10: Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Step 11: Restart the Client Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Step 12: Verify the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Step 13: Deploying Across the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Teradata Tools and Utilities Directory Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Security and Connecting to a Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Troubleshooting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Chapter 3: Installing to IBM AIX from CD Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Step 1: Inspect the Installation Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Inspect the Installation Kit CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Step 2: Review Platforms, Products, Dependencies and Requirements. . . . . . . . . . . . . . . . . . .37

Determine if Platforms and Products are Compatible . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Read Product Descriptions and Determine Product Dependencies . . . . . . . . . . . . . . . . . .37

Determine if System Requirements have been Met . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Step 3: Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . .38

Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . .38

Step 4: Install Third-Party Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Install Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Step 5: Install Teradata Tools and Utilities from the CD Media . . . . . . . . . . . . . . . . . . . . . . . .39

Install Teradata Tools and Utilities on IBM AIX Clients . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Step 6: Install Drivers from the Teradata Download Center . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Step 7: Patches from the Teradata Software Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41


Step 9: Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42








Session Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43


Table of Contents

Chapter 4: Installing to HP-UX and HP-UX Itanium from CD Media . . . . . 45


Inspect the Installation Kit CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45




Determine if System Requirements have been Met . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Step 3: Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . 46

Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . 46

Step 4: Install Third-Party Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Install Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Step 5: Install Teradata Tools and Utilities from the CD Media . . . . . . . . . . . . . . . . . . . . . . . 47

Install Teradata Tools and Utilities on HP-UX and HP-UX Itanium. . . . . . . . . . . . . . . . 47

Step 6: Install Drivers from the Teradata Download Center . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Step 7: Install Patches from the Teradata Software Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Step 8: Add CLI User Exit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Step 9: Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Step 10: Restart the Client Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Step 11: Verify the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Step 12: Deploying Across the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Teradata Tools and Utilities Directory Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Security and Connecting to a Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Troubleshooting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Session Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 5: Installing to Sun Solaris SPARC and Opteronfrom CD Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53


Inspect the Installation Kit and CD Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53




Determine System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54


Table of Contents

Step 3: Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . .54

Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . .54

Step 4: Install Third-Party Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Install Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Step 5: Install Teradata Tools and Utilities from the CD Media . . . . . . . . . . . . . . . . . . . . . . . .55

Installing Teradata Tools and Utilities on Sun Solaris SPARC and Opteron. . . . . . . . . . .56

Step 6: Install Drivers from the Teradata Download Center . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Step 7: Install Patches from the Teradata Software Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58


Step 9: Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58








Session Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Chapter 6: Installing from the Teradata Download Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Products Available on the Download Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Task 1: Install on Linux or UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Step 1: Identify the Package to Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Step 2: Download Packages from the Teradata Download Center . . . . . . . . . . . . . . . . . . .63

Step 3: Install the Downloaded Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Chapter 7: Installing from the Teradata Software Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Task 1: Install Patches on Red Hat Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Step 1: Identify the Patches Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Step 2: Download the Setup Package from the Teradata Software Server . . . . . . . . . . . . .67

Step 3: Install the Downloaded Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68


Table of Contents

Chapter 8: Adding CLI User Exit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Task 1: Adding CLI User Exit Functions to Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Task 2: Adding CLI User Exit Functions to HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Task 3: Adding CLI User Exit Functions to IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Task 4: Adding CLI User Exit Functions to Sun Solaris SPARC . . . . . . . . . . . . . . . . . . . . . . . 70

Task 5: Adding CLI User Exit Functions to Sun Solaris Opteron . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 9: Installing Teradata Meta Data Serviceson Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Task 1: Review MDS Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Step 1: Review Teradata Meta Data Services Documentation . . . . . . . . . . . . . . . . . . . . . . 73

Step 2: Review Teradata Meta Data Services Product Description . . . . . . . . . . . . . . . . . . 73

Step 3: Review Teradata MDS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Step 4: Review Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Step 5: Review Software Components to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Task 2: Uninstall Teradata MDS on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Step 1: Uninstall MDS Development Kit Files on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Step 2: Uninstall on Linux With Automatic DIM Update Enabled . . . . . . . . . . . . . . . . . 78

Step 3: Deactivate MDS Recovery Table Logging and Uninstall RSG. . . . . . . . . . . . . . . . 78

Task 2: Install Teradata MDS on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Step 1: Install Teradata ODBC Package and the ODBC.INI File. . . . . . . . . . . . . . . . . . . . 79

Step 2: Install MDS Core Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Step 3: Install MDS Development Kit Files (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Task 5: Set the MDS Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Step 1: Configure Linux Workstations or Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Task 6: Create the Meta Data Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Step 1: Create the Repository from a Linux Workstation . . . . . . . . . . . . . . . . . . . . . . . . . 82

Task 7: Migrate the Meta Data Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Step 1: Migrate the MDS Repository on a Linux Workstation . . . . . . . . . . . . . . . . . . . . . 82

Task 8: Create A Virtual Directory or Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83


Table of Contents

Chapter 10: Installing Automatic DIM Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Task 1: Review Automatic DIM Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Step 1: Review the Automatic DIM Update Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Step 2: Review Out of Sync Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Task 2: Configure Automatic DIM Update Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Step 1: Configure Linux Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Task 3: Install DIM Update Server Software (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Step 1: Install the MDS Action Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Step 2: Install the MDS DDL Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Step 3: Configure Linux System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Step 4: Configuring the ODBC.INI File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Step 5: Add Services to the Linux /etc/services File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Task 4: Install and Configure RSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Step 1: Install and Configure RSG on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Step 3: Start/Stop the RSG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Task 5: Configure Automatic DIM Update in MetaManager. . . . . . . . . . . . . . . . . . . . . . . . . . .94

Step 1: Add a Teradata Database System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Step 2: Add Teradata Nodes to a Teradata Database System. . . . . . . . . . . . . . . . . . . . . . . .94

Step 3: Load Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Step 4: Enable Automatic DIM Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Task 6: Check DIM Update Status with MetaManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Task 7: Start/Stop the DDL Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Task 8: Start/Stop the MDS Action Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Chapter 11: Deploying Across the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Task 1: Review Script Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Step 1: Determine Platform Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Step 2: Determine the Contents of the Tar File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Step 3: Determine if Script Dependencies are Installed . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Step 4: Review Script Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Task 2: Download Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Step 1: Download tar.exe and gzip.exe to Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Step 2: Example: Archive Packages on a Windows Platform . . . . . . . . . . . . . . . . . . . . . . .107

Step 3: Example: Archive Packages on a Linux Platform . . . . . . . . . . . . . . . . . . . . . . . . . .109

Step 4: Example: Archive a Single Package for a UNIX Platform . . . . . . . . . . . . . . . . . . .110


Table of Contents

Chapter 12: Configuring Teradata Tools and Utilities. . . . . . . . . . . . . . . . . . . . . . . . 113

Task 1: Configure JDBC Driver for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Task 2: Configure the ODBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Step 1: Copy the Template odbc.ini File for ODBC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Step 2: Setup Environment Variables for the ODBC Cursor Libraries for ODBC . . . . 114

Step 3: Setup NLSPATH for ODBC on Sun Solaris SPARC and Opteron . . . . . . . . . . . 115

Step 4: Setup ODBC Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Task 3: Configure Teradata Parallel Transporter for Red Hat Linux. . . . . . . . . . . . . . . . . . . 116

Step 1: Edit the twbcfg.ini File on Red Hat Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Step 2: Select Configuration File Defaults on Red Hat Linux . . . . . . . . . . . . . . . . . . . . . 117

Step 3: Setup the Shared Memory Parameters on Red Hat Linux. . . . . . . . . . . . . . . . . . 117

Step 4: Setup the Semaphore Parameters on Red Hat Linux . . . . . . . . . . . . . . . . . . . . . . 118

Step 5: Update Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Step 6: Switch the IPC Memory Choice to Shared Memory on Red Hat Linux . . . . . . 120

Step 7: Switch the IPC Memory Choice to Memory Mapped File on Red Hat Linux. . 120

Task 4: Configure Teradata Parallel Transporter on SUSE Linux . . . . . . . . . . . . . . . . . . . . . 121

Step 1: Select the Default Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Step 2: Select the Default Logs Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Step 3: Select the Interprocess Communication (IPC) Memory Choice . . . . . . . . . . . . 122

Step 4: Select the System Kernel Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123


Task 5: Configure Teradata Parallel Transporter for Linux 390x. . . . . . . . . . . . . . . . . . . . . . 124

Step 1: Edit the twbcfg.ini File on Linux 390x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Step 2: Select Configuration File Defaults on Linux 390x . . . . . . . . . . . . . . . . . . . . . . . . 125

Step 3: Setup the Shared Memory Parameters on Linux 390x. . . . . . . . . . . . . . . . . . . . . 125

Step 4: Setup the Semaphore Parameters on Linux 390x . . . . . . . . . . . . . . . . . . . . . . . . . 126


Step 6: Switch the IPC Memory Choice to Shared Memory on Linux 390x . . . . . . . . . 128

Step 7: Switch the IPC Memory Choice to Memory Mapped File on Linux 390x. . . . . 129

Task 6: Configure Teradata Parallel Transporter on IBM AIX. . . . . . . . . . . . . . . . . . . . . . . . 129

Step 1: Select Default and Alternate Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Step 2: Select the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Step 3: Select the Logs Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Step 4: Select the Interprocess Communication (IPC) Memory Choice . . . . . . . . . . . . 131


Task 7: Configure Teradata Parallel Transporter on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . 133

Step 1: Change the twbcfg.ini File on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Step 2: Setup Configuration File Defaults on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Step 3: Setup the Shared Memory Parameters on HP-UX. . . . . . . . . . . . . . . . . . . . . . . . 134

Step 4: Setup the Semaphore Parameters on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136


Table of Contents

Step 5: Setup the Environment Variables on HP-UX. . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

Step 6: Switch the IPC Memory Choice to Shared Memory on HP-UX . . . . . . . . . . . . .138

Step 7: Switch the IPC Memory Choice to Memory Mapped File . . . . . . . . . . . . . . . . . .139

Task 8: Configure Teradata Parallel Transporter on HP-UX Itanium . . . . . . . . . . . . . . . . . .139

Step 1: Change the twbcfg.ini File on HP-UX Itanium . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Step 2: Setup Configuration File Defaults on HP-UX Itanium . . . . . . . . . . . . . . . . . . . . .140

Step 3: Setup the Shared Memory Parameters on HP-UX Itanium . . . . . . . . . . . . . . . . .140

Step 4: Setup the Semaphore Parameters on HP-UX Itanium . . . . . . . . . . . . . . . . . . . . .141

Step 5: Setup the Environment Variables on HP-UX Itanium . . . . . . . . . . . . . . . . . . . . .142

Step 6: Switch the IPC Memory Choice to Shared Memory on HP-UX Itanium . . . . . .144

Step 7: Switch the IPC Memory Choice to Memory Mapped File . . . . . . . . . . . . . . . . . .144

Task 9: Configure Teradata Parallel Transporter on Sun Solaris SPARC . . . . . . . . . . . . . . . .145

Step 1: Select Default and Alternate Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145

Step 2: Select the Default Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

Step 3: Select the Logs Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

Step 4: Select the Interprocess Communication (IPC) Memory Choice . . . . . . . . . . . . .147

Step 5: Select the System Kernel Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Step 6: Update Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Task 10: Configuring Teradata Parallel Transporter on Sun Solaris Opteron . . . . . . . . . . . .150

Step 1: Select Default and Alternate Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Step 2: Select Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

Step 3: Select Logs Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

Step 4: Select Interprocess Communication (IPC) Memory Choice . . . . . . . . . . . . . . . .151

Step 5: Select System Kernel Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Step 6: Update Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Chapter 13: Verifying the Installation Using BTEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Task 1: Verify the Installation Using BTEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Step 1: Log onto the Teradata Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Step 2: Submit a Sample Teradata SQL Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

Step 3: Exit BTEQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

Chapter 14: Verifying Installation Using CLI Sample Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

Task 1: Run CLI Sample to Verify the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157


Table of Contents

Step 1: Run clisamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Chapter 15: Checking Files and Folders on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Task 1: Verifying Installation of Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Basic Teradata Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Named Pipes Access Module (npaxsmod) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

ODBC Driver for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Shared Common Components for Internationalization for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Teradata Archive/Recovery Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Teradata C Preprocessor2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Teradata Call-Level Interface version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Teradata Data Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Teradata FastExport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Teradata FastLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Teradata Generic Security Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Teradata MultiLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Teradata TPump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Teradata Parallel Transporter API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Teradata Parallel Transporter Export Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Teradata Parallel Transporter Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Teradata Parallel Transporter Load Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Teradata Parallel Transporter Stream Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Teradata Parallel Transporter Update Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Teradata WebSphere MQ Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Chapter 16: Checking Files and Folderson UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Task 1: Verifying Installation of Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Basic Teradata Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Named Pipes Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

ODBC Driver for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Shared Common Components for Internationalization for Teradata . . . . . . . . . . . . . . 194

Teradata C Preprocessor2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Teradata Call-Level Interface version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Teradata COBOL Preprocessor2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210


Table of Contents

Teradata Data Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211

Teradata FastExport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211

Teradata FastLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212

Teradata Generic Security Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

Teradata MultiLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

Teradata TPump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214

Teradata Parallel Transporter API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215

Teradata Parallel Transporter Export Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221

Teradata Parallel Transporter Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221

Teradata Parallel Transporter Load Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

Teradata Parallel Transporter Stream Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

Teradata Parallel Transporter Update Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Teradata WebSphere MQ Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Chapter 17: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling Previous Versions on Linux. . . . . . . . . . . . . . . . . . . . . . . . .227

Task 1: Uninstall Previous Versions on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

Teradata Tools and Utilities Release 13.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

Step 1: Uninstall All Teradata Tools and Utilities Products. . . . . . . . . . . . . . . . . . . . . . . .227

Step 2: Uninstall Individual Teradata Tools and Utilities Products . . . . . . . . . . . . . . . . .227

Chapter 18: Uninstalling Previous Versions on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

Task 1: Uninstall Previous Versions on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

Teradata Tools and Utilities Release 13.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

Step 1: Uninstall 64-bit BTEQ on HP-UX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237



Task 2: Uninstall Previous Versions on AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240



Task 3: Uninstall Previous Versions on SPARC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242

Step 1: Uninstall 64-bit Sun Solaris SPARC ODBC Driver for Teradata . . . . . . . . . . . . .242



Task 4: Uninstall Previous Versions on Opteron. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245


Table of Contents

Step 1: Uninstall All Products - Sun Solaris Opteron . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Step 2: Uninstall Individual Products - Sun Solaris Opteron . . . . . . . . . . . . . . . . . . . . . 245

Chapter 19: Installation Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Task 1: Inspect the Installation Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Task 2: Determine the CD Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Chapter 20: Product Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Task 1: Review Product Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Chapter 21: Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Task 1: Review Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Task 2: Installing Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Chapter 22: System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Task 1: Determine System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Step 2: Use the Korn Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Chapter 23: Installation Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Task 1: Determine Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Recommendation 1: Uninstall Previous Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Recommendation 2: Install Upgrade or Maintenance Software . . . . . . . . . . . . . . . . . . . 267

Recommendation 3: Install Dependent Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Recommendation 4: Install Teradata Generic Security Services . . . . . . . . . . . . . . . . . . . 268

Recommendation 5: Upgrade TPump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Recommendation 6: Upgrade C/COBOL Preprocessor2. . . . . . . . . . . . . . . . . . . . . . . . . 268


Table of Contents

Chapter 24: Security and Connecting to a Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269

Task 1: Make the Database Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269

Step 1: Review Logon Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269

Step 2: Connect To a Teradata Database from a GUI Application . . . . . . . . . . . . . . . . . .269

Step 3: Connect to a Teradata Database from Command Line Driven Applications . . .272

Step 4: Review Single Sign-On Legacy Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . .278

Step 5: Connect to a Teradata Database Programmatically . . . . . . . . . . . . . . . . . . . . . . . .279

Step 6: Check Logon Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280

Step 7: Reselect Authentication Mechanism on Connection Error. . . . . . . . . . . . . . . . . .281

Chapter 25: Troubleshooting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283

Task 1: Troubleshoot Client Computer Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283

Problem 1: Cannot Communicate Over the Network with Teradata Database . . . . . . .283

Problem 2: Incorrect Path Name in COPLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283

Problem 3: Incorrect Path Name in COPERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284

Problem 4: errmsg.cat File Not Found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284

Problem 5: Incorrect Path Name in COPANOMLOG. . . . . . . . . . . . . . . . . . . . . . . . . . . .284

Problem 6: Missing Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284

Problem 7: Incorrect Entries in the Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284

Problem 8: Missing Entries in the /etc/services File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285

Problem 9: Improper Linking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285

Problem 10: Incorrect clispb.dat Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285

Problem 11: Cannot Log On from CLI Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285

Problem 12: Cannot Log On to the Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . .285

Task 2: Troubleshoot Network Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285

Task 3: Troubleshoot Teradata Database Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286

Task 4: Troubleshoot Teradata Parallel Transporter Problems . . . . . . . . . . . . . . . . . . . . . . . .288

Problem 1: Unable to Find tbuild. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288

Problem 2: Cannot Run the New Installed Version of Teradata Parallel Transporter . .288

Problem 3: Failed to Load libpxcommon Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289

Problem 4: Unable to Find Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289

Problem 5: Unable to Find Messages on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290


Table of Contents

Chapter 26: Session Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Task 1: Determine BTEQ Session Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Task 2: Determine System-Wide Session Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Chapter 27: Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Task 1: Getting Technical Assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295


Table of Contents


CHAPTER 1

Linux and UNIX Operating SystemsGeneral Install

This document describes the general installation of Teradata Tools and Utilities products from CD-ROM, Teradata Download Center, and Teradata Software Server.

General Installation Instructions

Whenever installing Teradata Tools and Utilities software, always compare the versions available on the CD media, the Teradata Download Center and the Teradata Software Server. In general, the software server will contain the most recent point release of a software product, followed in turn by the download center and finally the CD media.

• Installing from a Web URL - Some Teradata Tools and Utilities have third-party dependencies. Install these dependencies from these respective URLs.

• Installing from CD Media - Describes how to install products on a single user from the CD media in the Teradata Tools and Utilities Installation Kit. The CDs contain installation packages for the current release.

• Installing from the Teradata Download Center - Describes how to install Teradata Tools and Utilities communications packages and other software available on the Teradata Download Center. The download center may contain more current software packages which should be installed instead of lower version software contained on the CD media.

• Installing from the Teradata Software Server - This document describes how to install Teradata Tools and Utilities packages from the Teradata Software Server. The server may contain updated software packages which should be installed in lieu of lower version software contained on the CD media, or on the Teradata Download Center.

• Installing from the ESDM Server - This document describes Teradata's Electronic Software Distribution Management (ESDM) program.

Instructions for Installing Across a Network

• Deploying Using tar - This document describes how to deploy one or more Teradata Tools and Utilities products across your network using a UNIX system ksh script or a DOS batch script and tar.


Chapter 1: Linux and UNIX Operating Systems General InstallInstructions for Installing Individual Products

Instructions for Installing Individual Products

• Installing Teradata Meta Data Services - Teradata Meta Data Services (MDS) is installed from CD media or the Teradata Software Server. Installation is generally limited to administrative users. This section details the installation of Teradata Meta Data Services from the CD media.


CHAPTER 2

Installing to Linux from CD Media

Follow these steps to Install one or more Teradata Tools and Utilities products from the Teradata Tools and Utilities installation Kit CD Media to Red Hat Linux, SUSE Linux and Linux for s390x clients.

Step 1: Inspect the Installation Kit

Inspect the Installation Kit CDs

• Installation Kit - Lists the Installation Kit CDs and indicates the CDs where products and their dependencies are located. Inspect the Teradata Tools and Utilities Installation Kit for completeness, and determine which CDs contain the products and the dependencies being installed. Because of space limitations, products on some installation CDs are segregated by platform

Step 2: Review Platforms, Products, Dependencies and Requirements

Determine if the products being installed are compatible with and supported by the client. Then determine if the minimum system requirements have been met, and which products have dependencies which have to be loaded.

Determine if Platforms and Products are Compatible

Links to a spreadsheet which lists the UNIX, Linux, Windows and mainframe platforms and the products supported by each release of Teradata Tools and Utilities are located at:

• http://www.info.teradata.com

Links to the current and last two major releases are included below:

• Teradata Tools and Utilities 12.00.xx Supported Versions - [12.00.xx]



Read Product Descriptions and Determine Product Dependencies

• Product Descriptions - Lists a synopsis of each of the products available.



http://www.info.teradata.com/eDownload.cfm?itemid=071690001

http://www.info.teradata.com/edownload.cfm?itemid=101880002


Chapter 2: Installing to Linux from CD MediaStep 3: Uninstall Previous Versions of Teradata Tools and Utilities

• Product Dependencies - Lists the Teradata Tools and Utilities dependencies and third-party dependencies. If installing from the main install, all Teradata Tools and Utilities product dependencies are verified, and if not available, are installed automatically.

• Third-Party Dependencies - Third-party products must be installed before installing any Teradata Tools and Utilities Products. This software is not contained on the installation CDs. Most are available from the manufacturer’s website.

Determine if System Requirements have been Met

• System Requirements - Minimum system requirements to install Teradata Tools and Utilities

Step 3: Uninstall Previous Versions of Teradata Tools and Utilities

Prior to installing new Teradata Tools and Utilities software, all existing Teradata Tools and Utilities software must be uninstalled. A menu item has been added to remove Teradata Tools and Utilities software. Always uninstall the previous version of the Teradata Tools and Utilities before starting a new installation.

Uninstall Previous Versions of Teradata Tools and Utilities

• Follow the Uninstall Order - See Uninstalling Previous Versions on Linux for instructions. Uninstall Teradata Tools and Utilities products in the following order:

1 Products other than the following 4 products

2 Teradata Data Connector (piom)

3 Call-Level Interface version 2 (cliv2)

4 Shared Common Components for Internationalization for Teradata (tdicu)

5 Teradata Generic Security Services (teragss)

Step 4: Install Third-Party Software Dependencies

Some Teradata Tools and Utilities products require the installation of third-party software. Most third-party dependency software can be installed from the manufacturer’s website. Links are provided where known.

Install Third-Party Software

Install the third-party software listed for each product. Where available, the download site or product information site is shown.


Chapter 2: Installing to Linux from CD MediaStep 4: Install Third-Party Software Dependencies

Teradata JDBC Driver

• JDK 1.4, JDK 5.0, or JDK 6.0 from Sun

http://java.sun.com/javase/downloads/index_jdk5.jsp

http://java.sun.com/javase/downloads/index.jsp

• JDK 5.0

• JDK 6.0

Teradata Parallel Transporter Infrastructure

• Java 2 Runtime Environment 1.4.2_06 or later

http://java.sun.com/products/archive

Teradata WebSphere MQ Access Module

• IBM® WebSphere® MQ 5.2

http://www-01.ibm.com/software/data/masterdata/product-info/library/

documentation.html

Compiler and Linker for SUSE Linux Enterprise Server 11

The required library, libstdc++-libc6.2-2.so.3, does not come as part of the standard SLES 11 installation. Download and install this library.

• libstdc++-libc6.2-2.so.3

http://rpmfind.net/linux/RPM/redhat/9/i386/compat-libstdc++-7.3-2.96.118.i386.html

Compiler and Linker for RedHat Linux AS 3.0

The required library, libstdc++.so.5 is included in the operating system as part of the standard RedHat AS 3.0 installation.


The required libraries, libstdc++.so.6 and libstdc++.so.5 are included as part of the standard RedHat AS 4.0 installation.


The library, libstdc++.so.5 does not come as part of the standard RedHat AS 5.0 installation. Download and install this library by downloading and installing:

• compat-libstdc++-33-3.2.3-61 to download libstdc++-libc6.2-2.so.3

http://rpm.pbone.net/index.php3?stat=26&dist=0&size=237109&name=compat-libstdc%2B%2B-33-3.2.3-61.i386.rpm

OR

• compat-libstdc++-8-3.3.4.2.i386.rpm to download both libstdc++-libc6.2-2.so.3 and libstdc++-libc6.2-2.so.5

http://rpm.pbone.net/index.php3?stat=26&dist=0&size=666891&name=compat-

libstdc%2B%2B-8-3.3.4.2.i386.rpm


http://rpmfind.net/linux/RPM/redhat/9/i386/compat-libstdc++-7.3-2.96.118.i386.html



http://rpm.pbone.net/index.php3?stat=26&dist=0&size=666891&name=compat-libstdc%2B%2B-8-3.3.4.2.i386.rpm

http://rpm.pbone.net/index.php3?stat=26&dist=0&size=666891&name=compat-libstdc%2B%2B-8-3.3.4.2.i386.rpm




http://www-01.ibm.com/software/data/masterdata/product-info/library/documentation.html


Chapter 2: Installing to Linux from CD MediaStep 5: Install Teradata Tools and Utilities from the CD Media

Step 5: Install Teradata Tools and Utilities from the CD Media

• Follow the Install Order - When installing “all” packages through the Main Install, the installer will install packages in the correct order. When installing individual products, they must be installed in the following order.





5 Any other products

Warning: For ODBC on all platforms, since the installation process now installs both 32-bit and 64-bit versions of the ODBC driver, both the 32-bit and 64-bit versions of TeraGSS must be installed before installing ODBC.

Note: Using the main install will install all products and their dependencies in the correct order. Using an alternative method to do the install requires that the products be installed manually in the correct order.

Install Teradata Tools and Utilities on Linux

This section contains the procedure to install Teradata Tools and Utilities products on Linux operating systems.

Procedure - Installing Teradata Tools and Utilities Products on Linux

Follow these steps to install Teradata Tools and Utilities products on Linux client operating systems.

1 Log on to the Linux client as root.

2 If a /mnt directory does not exist, create one

# mkdir /mnt

where: the CD-ROM mount point is /mnt, although an alternate may be used.

3 Insert the installation CD, Teradata Utility Pack for HP-UX - Linux - Vol 2 of 3, into the CD-ROM drive, then enter the following command at the prompt:

# mount /dev/<cdrom device name> /mnt

For example, if the CD-ROM device name is cdrom, enter:

# mount /dev/cdrom /mnt

In the example, the CD-ROM mount point is /mnt, although an alternate may be entered.

4 To begin the installation process, enter:

# cd /mnt# ./setup.bat


Chapter 2: Installing to Linux from CD MediaStep 5: Install Teradata Tools and Utilities from the CD Media

A screen similar to the following appears:

Copyright 2002-2010. Teradata Corporation. All Rights Reserved.Platform: Linux 32bit (i386)

Media: Load/Unload

Which software do you want to install? 1. teragss - Teradata GSS client package2. tdicu - Teradata Shared Component for Internationalization3. tdodbc - Teradata ODBC Driver4. cliv2 - Teradata CLIv25. piom - Teradata Data Connector API6. npaxsmod - Teradata Named Pipes Access Module7. mqaxsmod - Teradata WebSphere(r) MQ Access Module

8. bteq - Teradata BTEQ Application 9. fastexp - Teradata FastExport Utility10. fastld - Teradata FastLoad Utility11. mload - Teradata MultiLoad Utility12. tpump - Teradata TPump Utility13. qrydir - Teradata Query Director

a. Install all of the above softwareu. Remove previously installed Teradata Tools and Utilities softwareq. Quit the installation

Enter one or more selections (separated by space):

5 Select the packages to install. Software must be installed in the following order:





5 Other Products

6 After reviewing product dependencies, enter the products to install at the prompt:

• One or more numbers for the product(s), separated by spaces, or

Command Action

Install All Packages

Enter a. The number of products selected appears in the bottom right hand corner of the screen. The packages selected for installation have an asterisk beside them.

Uninstall All Enter u. Removes previous versions of Teradata Tools and Utilities products, except for Teradata Generic Security Services (TeraGSS).


Chapter 2: Installing to Linux from CD MediaStep 6: Install Drivers from the Teradata Download Center

7 Change back to the root directory and unmount the CD:

# umount /mnt

8 Remove the installation CD from the CD-ROM drive and repeat the procedure for each Linux CD in the installation kit.

• Preprocessors for HP-UX - Linux - Vol. 2 of 3

• Load/Unload for HP-UX - Linux - Vol. 2 of 3

• Parallel Transporter for HP-UX - Linux - Vol. 2 of 3

• Tape Storage Enablers for Linux - Windows

• Meta Data Services for Linux - MPRAS (RSG) - Windows

9 When done installing products, remove the installation CD from the CD-ROM drive.

Step 6: Install Drivers from the Teradata Download Center

• Installing from the Teradata Download Center - [Optional] Install products from the Teradata Download Center. All products are not available.

Step 7: Install Patches from the Teradata Software Server

• Installing from the Teradata Software Server - [Optional] Install the most recent critical post-production product updates from the Teradata Software Server.

Install Selected Packages

Enter 1, 2, ...n. Products and dependencies associated with the numbers will be installed.

• Dependencies: If individual products are going to be installed, first determine the product dependencies, such as CLIv2 or Data Connector API (PIOM), and enter the numbers for the dependencies at the prompt: one or more numbers for the product(s) to be installed, separated by spaces.

For information on dependent products, see Product Dependencies

• Products: Enter numbers for the dependencies at the prompt: one or more numbers for the product(s) to be installed, separated by spaces.

Quit Enter q to quit the installation.

Command Action


Chapter 2: Installing to Linux from CD MediaStep 8: Add CLI User Exit Functions

Step 8: Add CLI User Exit Functions

• Adding CLI User Exit Functions - [Optional] CLI User Exit functions are general purpose facilities that can be added to the CLI workstation architecture on client systems after the products have been installed. These functions allow user-defined processing to take place.

Step 9: Install Teradata Meta Data Services

To install the latest version of Teradata Meta Data Services and its associated products, go to:

• Installing Teradata Meta Data Services on Linux

• Installing Automatic DIM Update

Step 10: Configure Products

After the installation is complete, before restarting the client system, edit environment variable names, configure products.

• Configuring Teradata Tools and Utilities

Step 11: Restart the Client Computer

In most cases, the client computer does not require a restart. Reboot if the client installation requires it.

Note: Teradata Parallel Transporter adds some kernel modifications which require a computer restart.

Step 12: Verify the Installation

Verify the installation of individual Teradata Tools and Utilities products using one of the following methods:

• Verifying the Installation Using BTEQ - Verify the installation using BTEQ.

• Verifying Installation Using CLI Sample Program - Verify the installation using the CLI Sample program on the installed files.

• Checking Files and Folders on Linux - Verify the installation by comparing a list of folder and file names for each product.


Chapter 2: Installing to Linux from CD MediaStep 13: Deploying Across the Network

Step 13: Deploying Across the Network

If you decide to deploy across the network go to the following chapter:

• Deploying Across the Network

Reference Material

The information in this section is provided as additional reference material useful in logging onto the database, and troubleshooting a Teradata Tools and Utilities installation.

Teradata Tools and Utilities Directory Layout

The Teradata Tools and Utilities directory is the combination of the user-specified base directory, the Teradata Tools and Utilities fixed directory, and the Teradata Tools and Utilities release directory. The installation package allows the selection of a starting location, where the release is installed. The default location is /opt.

Security and Connecting to a Teradata Database

Security and Connecting to a Teradata Database contains information helpful in understanding the security schemes used in Teradata and making a successful connection to a Teradata Database.

Base Directory Fixed Directory Release Directory

/opt teradata/client/13.10/ bin

bin64

include

lib

lib64

odbc

odbc_32

odbe_64

sample

tbuild

tdicu

ODBC_32

ODBC_64


Chapter 2: Installing to Linux from CD MediaReference Material

Troubleshooting the Installation

Troubleshooting the Installation - Contains information helpful in troubleshooting problems that may arise while installing Teradata Tools and Utilities products.


Chapter 2: Installing to Linux from CD MediaReference Material


CHAPTER 3

Installing to IBM AIX from CD Media

Follow these steps to Install one or more Teradata Tools and Utilities products from the Teradata Tools and Utilities installation Kit CD Media to IBM AIX clients.



• Installation Kit - Lists the Installation Kit CDs and indicates the CDs where products and their dependencies are located. Inspect the Teradata Tools and Utilities Installation Kit for completeness, and determine which CDs contain the products and the dependencies being installed. Because of space limitations, products on some installation CDs are segregated by platform.

















Chapter 3: Installing to IBM AIX from CD MediaStep 3: Uninstall Previous Versions of Teradata Tools and Utilities








• Follow the Uninstall Order - See Uninstalling Previous Versions on UNIX Systems for instructions. Uninstall Teradata Tools and Utilities products in the following order:

1 Products other than 2 through 5










Chapter 3: Installing to IBM AIX from CD MediaStep 5: Install Teradata Tools and Utilities from the CD Media

IBM XL C/C++ Compiler

• Although versions of AIX support IBM XL C/C++ Compiler v7.0 (runtime libraries fileset xlC.rte v7.x.x.x) through IBM XL C/C++ Compiler v10.0 (runtime libraries fileset xlC.rte v10.x.x.x), IBM XL C/C++ Compiler v9.0 (runtime libraries fileset xlC.rte v9.x.x.x) or later must be used since TDICU has been compiled with v9.0, otherwise runtime errors such as unresolved symbols from libC.a will occur.

http://www-01.ibm.com/support/docview.wss?rs=2239&uid=swg24015997





• JDK 5.0

• JDK 6.0







documentation.html










http://www-01.ibm.com/support/docview.wss?rs=2239&uid=swg24015997






Chapter 3: Installing to IBM AIX from CD MediaStep 5: Install Teradata Tools and Utilities from the CD Media


Install Teradata Tools and Utilities on IBM AIX Clients

Teradata Tools and Utilities that can be installed on an IBM AIX client.

Procedure - Installing Teradata Tools and Utilities on an IBM AIX Client

Follow these steps to install Teradata Tools and Utilities on an IBM AIX client.

1 Log on to the IBM AIX client system as root user.

2 If a /mnt directory does not exist, create one:

# mkdir /mnt

3 Insert the installation CD, Teradata Utility Pack for AIX-Solaris - Vol 3 of 3, into the CD-ROM drive and enter:

# mount -V cdrfs -o ro /dev/<cd-rom device> /mnt

For device name, cd0, the entry is:

# mount -V cdrfs -o ro /dev/cd0 /mnt

where: the CD-ROM mount point is /mnt.

4 To begin the installation, enter:



Welcome to the Teradata Tools and Utilities 13.10.00.00 installationCopyright 2010. Teradata Corporation. All Rights Reserved.Media: Load/UnloadPlatform: AIX

Which software do you want to install? 1. TeraGSS - Teradata GSS client package 2. tdicu - Teradata Shared Component for Internationalization 3. tdodbc - Teradata ODBC Driver 4. cliv2 - Teradata CLIv2 5. piom - Teradata Data Connector API 6. npaxsmod - Teradata Named Pipes Access Module 7. mqaxsmod - Teradata WebSphere(r) MQ Access Module 8. bteq - Teradata BTEQ Application 9. fastexp - Teradata FastExport Utility

10. fastld - Teradata FastLoad Utility 11. mload - Teradata MultiLoad Utility 12. tpump - Teradata TPump Utility


Enter one or more selection (separated by space):


Chapter 3: Installing to IBM AIX from CD MediaStep 6: Install Drivers from the Teradata Download Center




a Call-Level Interface version 2 (cliv2)


4 Other Products



• a to install all the software,

• u to remove previously installed Teradata Tools and Utilities software

• q to quit the installation

6 After all installations are complete, change back to the root directory and unmount the CD by entering the following at the command prompt:

# umount /mnt

7 Remove the installation CD from the CD-ROM drive and repeat the procedure for each of the IBM AIX CDs in the installation kit.

• Preprocessors for AIX-Solaris - Vol. 3 of 3

• Load/Unload for AIX-Solaris - Vol. 3 of 3

• Parallel Transporter for AIX-Solaris - Vol. 3 of 3




Step 7: Patches from the Teradata Software Server



Chapter 3: Installing to IBM AIX from CD MediaStep 8: Add CLI User Exit Functions







After editing environment variables and configuring products, always restart the client computer to ensure that environment variables are setup correctly, and to allow file upgrades to complete.





• Checking Files and Folders on UNIX Systems - Verify the installation by comparing a list of folder and file names for each product.





Chapter 3: Installing to IBM AIX from CD MediaReference Material

Reference Material

The information in this section is provided as additional reference material useful in logging onto the database, and troubleshooting a Teradata Tools and Utilities installation




Security and Connecting to a Teradata Database - Contains information helpful in understanding the security schemes used in Teradata and making a successful connection to a Teradata Database.



Session Limits

Session Limits - Lists Teradata session limits for Basic Teradata Query (BTEQ) and for the entire system.



include

lib

lib64

odbc

odbc_32

odbe_64

sample

tbuild

tdicu

ODBC_32

ODBC_64


Chapter 3: Installing to IBM AIX from CD MediaReference Material


CHAPTER 4

Installing to HP-UX and HP-UX Itaniumfrom CD Media

Follow these steps to Install one or more Teradata Tools and Utilities products from the Teradata Tools and Utilities installation Kit CD Media to HP-UX and HP-UX Itanium clients.




















Chapter 4: Installing to HP-UX and HP-UX Itanium from CD MediaStep 3: Uninstall Previous Versions of Teradata Tools and Utilities



















Chapter 4: Installing to HP-UX and HP-UX Itanium from CD MediaStep 5: Install Teradata Tools and Utilities from the CD Media





• JDK 5.0

• JDK 6.0







documentation.html










Install Teradata Tools and Utilities on HP-UX and HP-UX Itanium

This section contains the procedure to install Teradata Tools and Utilities products on HP-UX and HP-UX Itanium operating systems.







Chapter 4: Installing to HP-UX and HP-UX Itanium from CD MediaStep 5: Install Teradata Tools and Utilities from the CD Media

Procedure - Installing Teradata Tools and Utilities Products on HP-UX and HP-UX Itanium

Follow these steps to install the Teradata Tools and Utilities products on HP-UX and HP-UX Itanium client operating systems:

1 Log on to the HP-UX or HP-UX Itanium client as the root user.

2 If a /mnt directory does not exist, create one:

# mkdir /mnt


3 Insert the installation CD, Teradata Utility Pack for HP-UX -Linux - Vol 2 of 3, into the CD-ROM drive, then enter the following:

# mount /dev/dsk/<device name> /mnt

For example, if the CD-ROM device name is c0t1d0:

# mount /dev/dsk/c0t1d0 /mnt


Note: To find a CD-ROM device, enter the following:

ioscan -fnC disk

4 To begin the installation process, enter:


A screen similar to the following appears.

Welcome to the Teradata Tools and Utilities 13.10 installationCopyright 2002-2010. Teradata Corporation. All Rights Reserved.Media: Load/UnloadPlatform: HP-UX

Which software do you want to install?1. TeraGSS - Teradata GSS client package 2. tdicu - Teradata Shared Component for Internationalization 3. tdodbc - Teradata ODBC Driver 4. cliv2 - Teradata CLIv2 5. piom - Teradata Data Connector API 6. npaxsmod - Teradata Named Pipes Access Module 7. mqaxsmod - Teradata WebSphere(r) MQ Access Module8. bteq - Teradata BTEQ Application 9. fastexp - Teradata FastExport Utility

10. fastld - Teradata FastLoad Utility 11. mload - Teradata MultiLoad Utility 12. tpump - Teradata TPump Utility a. Install all of the above softwareu. Remove previously installed Teradata Tools and Utilities softwareq. Quit the installation

Enter one or more selection (separated by space):

Note: Teradata Parallel Transporter packages are contained on Load/Unload CD #2.



Chapter 4: Installing to HP-UX and HP-UX Itanium from CD MediaStep 6: Install Drivers from the Teradata Download Center





5 Other Products






7 Change back to the root directory, and unmount the CD:

# umount /mnt

8 Remove the installation CD from the CD-ROM drive and repeat the procedure for each HP-UX CD in the installation kit.

• Preprocessors for HP-UX - Linux - Vol. 2 of 3

• Load/Unload for HP-UX - Linux - Vol. 2 of 3

• Parallel Transporter for HP-UX - Linux - Vol. 2 of 3







• Adding CLI User Exit Functions - CLI User Exit functions are general purpose facilities that can be added to the CLI workstation architecture on client systems after the products have been installed. These functions allow user-defined processing to take place.


Chapter 4: Installing to HP-UX and HP-UX Itanium from CD MediaStep 9: Configure Products













•Deploying Across the Network

Reference Material





Chapter 4: Installing to HP-UX and HP-UX Itanium from CD MediaReference Material


Security and Connecting to a Teradata Database - Contains information helpful in understanding the security schemes used in Teradata and making a successful connection to a Teradata Database.



Session Limits




include

lib

lib64

odbc

odbc_32

odbe_64

sample

tbuild

tdicu

ODBC_32

ODBC_64


Chapter 4: Installing to HP-UX and HP-UX Itanium from CD MediaReference Material


CHAPTER 5

Installing toSun Solaris SPARC and Opteron

from CD Media

Follow these steps to Install one or more Teradata Tools and Utilities products from the Teradata Tools and Utilities installation Kit CD Media to Sun Solaris SPARC and Opteron clients.


Inspect the Installation Kit and CD Contents
















Chapter 5: Installing to Sun Solaris SPARC and Opteron from CD MediaStep 3: Uninstall Previous Versions of Teradata Tools and Utilities





Determine System Requirements














Chapter 5: Installing to Sun Solaris SPARC and Opteron from CD MediaStep 5: Install Teradata Tools and Utilities from the CD Media







• JDK 5.0

• JDK 6.0







documentation.html
















Chapter 5: Installing to Sun Solaris SPARC and Opteron from CD MediaStep 5: Install Teradata Tools and Utilities from the CD Media

Installing Teradata Tools and Utilities on Sun Solaris SPARC and Opteron

This section contains the procedure to install Teradata Tools and Utilities products on Sun Solaris SPARC and Opteron operating systems.

Procedure - Installing on Sun Solaris SPARC and Opteron Systems

Follow these steps to install Teradata Tools and Utilities on Sun Solaris SPARC and Opteron operating systems.

1 Insert the installation CD, Teradata Utility Pack for AIX-Solaris - Vol 3 of 3, in the CD-ROM drive on the server running the Sun Solaris system.

2 From the console, log on as root or change to root and enter your password.

3 Change your directory to CD-ROM mount point with the following command:

# cd /cdrom/cdrom0

Note: If cdrom0 does not exist under the CD-ROM mount point, then, in the cdrom directory, change the directory to: <cd directory>.

The following table lists the CD mount points.

4 Enter:

# ./setup.bat

A Teradata Tools and Utilities CD Installation screen similar to the following appears:

Welcome to the Teradata Tools and Utilities 13 installationCopyright 2002-2010. Teradata Corporation. All Rights Reserved.

Platform: Solaris Sparc 64-bit (or Solaris Opteron 64-bit)Media: Load/Unload - Volume 3

Which software do you want to install?1. teragss - Teradata GSS client package

2. tdicu - Teradata Shared Component for Internationalization 3. cliv2 - Teradata CLIv2 4. piom - Teradata Data Connector API 5. npaxsmod - Teradata Named Pipes Access Module 6. mqaxsmod - Teradata WebSphere(r) MQ Access Module 7. bteq - Teradata BTEQ Application 8. fastexp - Teradata FastExport Utility 9. fastld - Teradata FastLoad Utility10. mload - Teradata MultiLoad Utility11. tpump - Teradata TPump Utility

CD Directory

Teradata Utility Pak cd1a_tera_util_pak

Database Management cd2_database_mgnt

Preprocessors cd3_preprocessors

Load/Unload cd4_load_unload


Chapter 5: Installing to Sun Solaris SPARC and Opteron from CD MediaStep 6: Install Drivers from the Teradata Download Center


Enter one or more selections (separated by space):






5 Other Products






7 From the root directory, enter the following command and remove the installation CD from the CD-ROM drive:

# umount /cdrom

8 Remove the installation CD from the CD-ROM drive and repeat the procedure for each Sun Solaris SPARC or Opteron CD in the installation kit.

• Preprocessors for AIX - Solaris - Vol. 3 of 3

• Load/Unload for AIX - Solaris - Vol. 3 of 3

• Parallel Transporter for AIX - Solaris - Vol. 3 of 3

9 When done installing products, remove the CD-ROM mount point, enter the following command (this step is optional):

# rmdir /cdrom/<mount point>

10 Log off and then login to fully enable the newly installed software packages.




Chapter 5: Installing to Sun Solaris SPARC and Opteron from CD MediaStep 7: Install Patches from the Teradata Software Server


• Installing from the Teradata Software Server -[Optional] Install the most recent critical post-production product updates from the Teradata Software Server.














Chapter 5: Installing to Sun Solaris SPARC and Opteron from CD MediaStep 12: Deploying Across the Network




Reference Material





Security and Connecting to a Teradata Database contains information helpful in understanding the security schemes used in Teradata and making a successful connection to a Teradata Database.





include

lib

lib64

odbc

odbc_32

odbe_64

sample

tbuild

tdicu

ODBC_32

ODBC_64


Chapter 5: Installing to Sun Solaris SPARC and Opteron from CD MediaReference Material

Session Limits



CHAPTER 6

Installing from theTeradata Download Center

This document describes the general procedures for installing Teradata Tools and Utilities from the Teradata Download Center.

Products Available on the Download Center

The following is a list of the Teradata Tools and Utilities products that can be installed from the center.

Drivers and Connectivity Software:

• ODBC Driver for Teradata

• OLE DB Provider for Teradata

• .NET Data Provider for Teradata

• Teradata Call-Level Interface version 2

• Teradata JDBC Driver

Task 1: Install on Linux or UNIX Systems

Perform the steps in this section to download and install products from the Teradata Download Center.

Step 1: Identify the Package to Download

The following procedure illustrates how to identify which package are available to download from the Teradata Download Center.


Chapter 6: Installing from the Teradata Download CenterTask 1: Install on Linux or UNIX Systems

Procedure - Identifying Setup Packages Available on the Download Center

1 Go to http://www.teradata.com/downloadcenter/. The Teradata Download Center screen with a list of selectable products appears.

2 Click on the product name. The list expands to list the operating systems which can be chosen.

3 Click on the operating system A list of the downloads available appears.


http://www.teradata.com/downloadcenter/


Step 2: Download Packages from the Teradata Download Center

The following steps illustrate how to download a typical setup package from the Teradata Download Center.

Procedure - Downloading the Selected Setup Package from the Download Center

1 Click on the software package to download. A description of the package appears along with a list of Download Files. If there are unique download procedures for a product or a specific release, the link to a file containing the procedures also appears with the download .tar.gz file link.

2 If a readme file is included, click on the readme file link and determine any special download or installation instructions before continuing.

3 Return to the Download screen.

4 Click on the Download Files package (typically a .tar.gz file).



5 Read the License Agreement, then click I Accept. A screen with a link to the Download file appears.

6 Click Download..., and select the location where to save the .tar.gz file.

7 Click SAVE to save the .tar.gz file is saved to the location chosen.

Step 3: Install the Downloaded Product

The following steps continue with the installation of the downloaded product.

Procedure - Installing the Downloaded Product

1 Go to the location where the .tar.gz file was saved.

2 Read the .txt readme file to determine further installation instructions.

3 Typically the instructions describe how to uncompress and untar the files and dependent product packages into a folder for the setup packages.

For example, for Linux, uncompress and untar the cliv2 package with:

# gunzip cliv2_LINUX_x8664_12.00.00.07.tar.gz | tar xvf

Remove previous software.

# rpm -e

Install dependencies in order, and then install the product.

# rpm [INSERT Tdicu]# rpm [ISERT TeradGSS]# rpm -ivh --nodeps cliv2_64-12.00.00.07-1.x86_64.rpm


CHAPTER 7

Installing from theTeradata Software Server

To ensure the highest quality and best performance of Teradata Tools and Utilities products, the most recent critical post-production updates can be installed from the Teradata Software Server at:

http://tssprod.teradata.com:8080/TSFS/home.do

Task 1: Install Patches on Red Hat Linux

Step 1: Identify the Patches Available

The following procedure shows how to download patches available on the Teradata Software Server to the Red Hat operating system.

Procedure - Identifying Patches on the Teradata Software Server

The following steps illustrate how to identify patches on the Teradata Software Server.

1 Go to http://tssprod.teradata.com:8080/TSFS/home.do.

2 Click on Teradata Client. The Client Help screen appears.




Chapter 7: Installing from the Teradata Software ServerTask 1: Install Patches on Red Hat Linux

3 Click on the operating system . The Teradata Client Released Software screen appears.

4 Select the Software Base and Platform Base, then click on Submit. The Client Patches available screen appears.



Step 2: Download the Setup Package from the Teradata Software Server

The following procedure continues by downloading the selected product setup packages from the Teradata Software Server.

Procedure - Downloading the Setup Package

1 Click in the check box(es) to select the software patch(es) to download

2 Enter your User Name and E-Mail Address, then click Submit.



3 Click Download. The zipped .gz.tar files and associated readme.txt files are downloaded.

Step 3: Install the Downloaded Product

The following steps continue with the installation of the downloaded product on a Red Hat Linux client.

Procedure - Installing the Downloaded Product

1 Go to the location where the .zip file containing the required .tar.gz files and associated files was saved.

2 Read the .txt readme file(s) to determine further installation instructions.

3 Typically the instructions describe how to uncompress and untar the files and dependent product packages into a folder for the setup packages.

For example, for Linux, uncompress and untar the cliv2 package with:

# gunzip cliv2_LINUX_x8664_13.10.00.00.tar.gz | tar xvf

Remove previous software.

# rpm -e

Install dependencies in order, and then install the product.

# rpm [INSERT Tdicu]# rpm [ISERT TeradGSS]

# rpm -ivh --nodeps cliv2_64-13.10.00.00-1.x86_64.rpm


CHAPTER 8

Adding CLI User Exit Functions

This section contains the procedure to add CLI User Exit Functions to the operating system. CLI User Exit functions are general purpose facilities that can be added to the CLI workstation architecture on the selected operating system. These functions allow user-defined processing to take place.

Task 1: Adding CLI User Exit Functions to Linux

Procedure - Adding CLI User Exit Functions to a Linux Client

Follow these steps to add CLI User Exit functions to a Linux client.

1 Change directories to /opt/teradata/client/13.10/sample, using the following command:

# cd /opt/teradata/client/13.10/sample

2 Modify the CliLgnEx.c or CliPPS.c file in the sample directory.

3 Compile and link using either the 32-bit or 64-bit version of the makefile to create a new shared object, libtdusr.so.

Note: The Native compiler on IA64 is not supported.

On Linux, this command compiles the 32-bit version:

# make -f maketdusr.lx

Note: On 64-bit Linux, the compiler always generates 64-bit binaries. The 32-bit makefile is not supported on 64-bit Linux platforms.

4 Move the libtdusr.so file into the cli installation directory, and verify that libcliv2 exists in the same directory.

For more information on CLI User Exit Functions, see Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems, Appendix D.

Task 2: Adding CLI User Exit Functions to HP-UX

Procedure - Adding CLI User Exit Functions to an HP-UX Client

Follow these steps to add CLI User Exit functions to an HP-UX client.


Chapter 8: Adding CLI User Exit FunctionsTask 3: Adding CLI User Exit Functions to IBM AIX




3 Compile and link using either the 32-bit or 64-bit version of the makefile to create a new shared object, libtdusr.sl.

On HP-UX, this command compiles the 32-bit version:

# make -f maketdusr.hpux

Note: The Native compiler on IA64 is not supported.

4 Move the libtdusr.sl file into the cli installation directory, and verify that libcliv2 exists in the same directory.


Task 3: Adding CLI User Exit Functions to IBM AIX

Procedure - Adding CLI User Exit Functions to an IBM AIX Client

Follow these steps to add CLI User Exit functions to an IBM AIX client.





On IBM AIX, this command compiles the 32-bit version:

# make -f maketdusr.aix



Task 4: Adding CLI User Exit Functions to Sun Solaris SPARC

Procedure - Adding CLI User Exit Functions to a Sun Solaris SPARC Client

Follow these steps to add CLI User Exit functions to a Sun Solaris SPARC client.


Chapter 8: Adding CLI User Exit FunctionsTask 5: Adding CLI User Exit Functions to Sun Solaris Opteron





On Sun Solaris SPARC, this command compiles the 32-bit version:

# make -f maketdusr.sols

Note: On 64-bit Linux, the compiler always generates 64-bit binaries. The 32-bit makefile is not supported on 64-bit Linux platforms.



Task 5: Adding CLI User Exit Functions to Sun Solaris Opteron

Procedure - Adding CLI User Exit Functions to a Sun Solaris Opteron Client

Follow these steps to add CLI User Exit functions to a Sun Solaris Opteron client.





On Sun Solaris Opteron, this command compiles the 32-bit version:

# make -f maketdusr.sols




Chapter 8: Adding CLI User Exit FunctionsTask 5: Adding CLI User Exit Functions to Sun Solaris Opteron


CHAPTER 9

Installing Teradata Meta Data Serviceson Linux

Installation, configuration, dependencies and reference information for Teradata Meta Data Services on Linux operating systems are described in this section.

Distribution Media

Whenever installing Teradata Meta Data Services, always compare the versions available on the CD media and the Teradata Software Server. The software server will contain the most recent point release of a software product.

• “Installing from CD Media” - Teradata Tools and Utilities installs on a single user from the CD media in the Teradata Tools and Utilities Installation Kit. The CDs contain installation packages for the current release.

• “Installing from the Teradata Software Server” - on the Teradata Software Server. The server may contain updated software packages which should be installed in lieu of lower version software contained on the CD media.

Task 1: Review MDS Product Information

Step 1: Review Teradata Meta Data Services Documentation

Click on the following link to display a list of Teradata Meta Data Services documentation:

Teradata Meta Data Services documentation

Step 2: Review Teradata Meta Data Services Product Description

Teradata Meta Data Services (MDS) provides an infrastructure for managing Teradata archive data warehouse metadata and for creating tools to interchange metadata with external operational systems, Extraction Transformation and Load (ETL) tools, Business Intelligence tools, Database Modeling tools, and any other metadata sources.

Step 3: Review Teradata MDS Overview

The following figure illustrates a typical Teradata MDS configuration consisting of:

• A Teradata Database System containing a Teradata MDS repository


http://www.info.teradata.com/templates/eSrchResults.cfm?prodline=&txtpid=&txtrelno=&txtttlkywrd=MetaDataServices&rdsort=Title&srtord=Asc&nm=Teradata+Meta+Data+Services

Chapter 9: Installing Teradata Meta Data Services on LinuxTask 1: Review MDS Product Information

• One or more workstations accessing the Teradata MDS repository with a web browser

• An Active Server Pages (ASP) compliant web server with MetaSurf installed

• A Windows based workstation configured to administer the MDS repository

A system may also contain one or more workstations that will be used to develop or run MDS applications and, if the Teradata MDS Automatic DIM Update feature is to be installed, a designated DIM Update server.

Step 4: Review Installation Prerequisites

The following table lists software and hardware required before installing Teradata Meta Data Services:

MDSRepository

Teradata Server

HTMLPage Intranet

orInternetHTTP

Request

HTMLPage

MDSCom

Interface+

Engine

ASPPage

ActiveServerEngine

Metasurf

Client Web Browser

Workstation/Laptop/Etcwith Supported Browsers

3118

B00

1

WindowsWeb

Server

ODBCODBC

TeradataDatabase

MetaManager/MetaBrowse(Windows PC)

MDSEngine

*

*

*MDS Installed



Text Box Description

Teradata Database System The MDS repository is stored in a Teradata Database System V2R6.1.x or greater.

The minimum size of the database for a production MDS repository is 50MB.

Note: A versioned repository will require more space than a non-versioned repository.

Teradata User Account Because the MDS repository is stored in a Teradata Database, a Teradata user account is required to connect to the Teradata Database system to access these tables.

Note: A Teradata user account is required for each Teradata Database system to be loaded into the MDS repository. Unless the metaviews utility is used, these users must have SELECT privileges to the DBC tables.

Note: If Teradata Meta Data Services is being installed on the MDS administrator’s workstation, grant the user all privileges to the MDS database.

ODBC Driver for Teradata (ODBC) and Data Source Name (DSN)

All of the machines running Teradata MDS software must have the appropriate Teradata ODBC driver installed and configured. ODBC 12.00.00 and above is required. For best results use the ODBC driver for Teradata version that matches the Teradata Meta Data Services version being used.

Create a System DSN for the Teradata Database Systems that will contain the MDS repository.

On Linux machines, the DSN information is specified with the odbc.ini file. The name and location of the odbc.ini file can be specified with the ODBCINI environment variable.

Windows-based Workstation Because the Teradata MDS administrative software is a Windows based application, at least one Windows based workstation is required. This can be either a Windows XP, Windows Server 2008, Windows Server 2003, Windows 2000, or Windows Vista system.

Hardware requirements are:

• Pentium PC or greater with at least 256 MB RAM

• Minimum of 50 MB disk space

An Active Server Pages (ASP) Compliant Web Server

If the Teradata MDS MetaSurf web application will be used a Windows 2008 Server with Microsoft IIS 7.0, Windows 2000/2003 Server with Microsoft IIS 5.0, Microsoft IIS 6.0, or a Web Server that supports ASP and Microsoft COM components is required.



Step 5: Review Software Components to Install

There are four different types of Teradata MDS software packages that perform different tasks and install on different hardware and software environments.

DIM Update Server If setting up and using the Teradata MDS Automatic DIM Update feature, a Linux, Windows XP, Windows Server 2003, Windows 2000, or Windows Vista system is required to run the server processes. This can be an application node on the Teradata Database System or a separate host with a network connection to the Teradata Database System.



MDS Core Files The core files are the MDS executables and DLLs. The core files include the MDS MetaBrowse and MDS MetaManager programs. These files are required on all systems running an MDS application or developing MDS applications.

Installed: The MDS core files can be installed on either Windows or Linux based systems.

MDS Development Kit The MDS development kit contains additional files needed to develop MDS applications. MDS provides a set of application programming interfaces (APIs) for third-party applications to store, administer, and retrieve metadata from the MDS repository. The development kit also includes sample applications.

Installed: The MDS development kit is installed on the workstation of any user who will be working with the MDS APIs. The MDS development kit files can be installed on either Windows or Linux based systems.

MDS MetaSurf Files MetaSurf provides HTML files and ASP scripts that enable users to browse and search the MDS repository using a Web application.

Installed: The MetaSurf files are installed on the ASP compliant web server.

MDS DIM Update Files Installed: If setting up and using the Teradata MDS Automatic DIM Update feature, install executable files for the MDS DDL Gateway and the MDS Action Processor on the designated DIM Update Server.

The MDS DIM Update files can be installed on either Windows, or Linux based systems.


Chapter 9: Installing Teradata Meta Data Services on LinuxTask 2: Uninstall Teradata MDS on Linux

Task 2: Uninstall Teradata MDS on Linux

If a machine running Linux has an older version of the Teradata Meta Data Services software installed, uninstall the older version before installing the new version. The steps required depend upon whether the Automatic DIM Update files were installed.

The metadelete program needs to be run first. The metadelete program drops all MDS repository tables, views and macros; that is, all tables, views and macros that were created by MDS in the Teradata Database.

Procedure - Uninstalling Teradata MDS on Linux

1 Logon as “root”.

2 From the command line, run metadelete. The metadelete program drops all MDS repository tables, views, and macros in the MDS repository.

metadelete superuser password [-F]-h

where:

3 Do the following:

• If the MDS DIM Update files are not currently installed or the MDS development files, uninstall the MDS Core files by removing the MDS base package with the rpm -e mdsbase command.

• If the MDS development files are installed, remove them following the instructions in “Step 1: Uninstall MDS Development Kit Files on Linux” before removing the mdsbase package.

• If the DIM Update files are installed, refer to “Step 2: Uninstall on Linux With Automatic DIM Update Enabled” for instructions.

Step 1: Uninstall MDS Development Kit Files on Linux

If the MDS Automatic DIM Update files or the MDS development files are installed, uninstall the MDS development kit files with the rpm -e mdssdk command.

If the DIM Update files are installed, refer to “Step 2: Uninstall on Linux With Automatic DIM Update Enabled” for instructions.

Parameter Description

Superuser The name of an MDS Administrator

Password The password of an MDS Administrator

-F Deletes the repository even if it is not the current release

-h Displays a message describing the metadelete parameters and then exits. No changes are made to the repository.


Chapter 9: Installing Teradata Meta Data Services on LinuxTask 2: Uninstall Teradata MDS on Linux

Step 2: Uninstall on Linux With Automatic DIM Update Enabled

Use the this procedure to uninstall Teradata Meta Data Services on a Linux system that currently has the Automatic DIM Update files installed to remove the DIM Update files and other MDS software components:

To uninstall MDS with Automatic DIM Update enabled

1 Execute the package remove script for the DDL Gateway with the rpm -e mdsgwy command.

The package remove script will check to see if the DDL Gateway is running.

If the DDL Gateway is running the package remove will fail and the error message will describe how to manually stop the DDL Gateway to remove the package.

2 Remove the MDS Action Processor package by using the rpm -e mdsap command.

The package remove script will check to see if the MDS Action Processor is running.

If the Action Processor is running the package remove will fail and the error message will tell you how to manually stop the Action Processor so you can remove the package.

Follow the instructions shown in the error message to stop the Action Processor and uninstall the package with the rpm -e mdsap command.

If the MDS development kit files are installed, proceed to step 3, if not, proceed to step 4.

3 Uninstall the MDS development kit software with the rpm -e mdssdk command.

4 Uninstall the MDS base software with the rpm -e mdsbase command.

5 If the Automatic DIM Update feature will not be used in the future, refer to “Step 3: Deactivate MDS Recovery Table Logging and Uninstall RSG” for information on deactivating MDS Recovery Table Logging.

Step 3: Deactivate MDS Recovery Table Logging and Uninstall RSG

If the DIM Update packages/files were uninstalled and the Automatic DIM Update feature will not be used in the future, uninstall the RSG and deactivate logging to the MDS Recovery Table.

To uninstall RSG and deactivate logging to the MDS Recovery Table

1 Remove the RSG package. It is strongly suggested that tdpkgrm be used because it allows selected versions of RSG to be removed from all nodes simultaneously. On Linux, rpm -e rsg removes RSG from a single node.

Note: A TPA shutdown must be done prior to removing the RSG package. None of the commands will allow the removal of a running RSG version.

Then the next time Teradata is reset, it will stop logging to the MDS Recovery Table. Also, Teradata will not start the MDS RSG program.


Chapter 9: Installing Teradata Meta Data Services on LinuxTask 2: Install Teradata MDS on Linux

Task 2: Install Teradata MDS on Linux

Before installing MDS software on a Linux machine, uninstall any MDS software currently installed on the machine. For information on removing MDS software, refer to “Task 2: Uninstall Teradata MDS on Linux.”

Step 1: Install Teradata ODBC Package and the ODBC.INI File

If not already installed, install the Teradata ODBC package (tdodbc). The Teradata ODBC package tdodbc installs a sample odbc.ini file.

Sample odbc.ini

Listed below are the contents of a sample odbc.ini file.

[ODBC]InstallDir=/usr/odbcTrace=0TraceFile=/usr/joe/odbcusr/trace.logTraceAutoStop=0[ODBC Data Sources]MDSDSN=tdata.sodefault=tdata.soSYSTEMIDSN=tdata.so[MDSDSN] Driver=/usr/odbc/drivers/tdata.so Description=MDS Repository DBCName=208.199.59.208 LastUser= Username= Password= Database= DefaultDatabase= [SYSTEM1DSN] Driver=/usr/odbc/drivers/tdata.so Description=Teradata V12.0 System DBCName=208.199.59.209 LastUser= Username= Password= Database= DefaultDatabase= [default]Driver=/usr/odbc/drivers/tdata.so Description=NCR 5500 running Teradata V12.0DBCName=208.199.59.209 LastUser= Username= Password= DefaultDatabase=


Chapter 9: Installing Teradata Meta Data Services on LinuxTask 5: Set the MDS Configuration Parameters

Procedure - Configure ODBC

1 Edit the appropriate odbc.ini file and create a DSN to the Teradata system that will contain the MDS repository.

2 Add the DSN names to the ODBC Data Sources section.

Note: For each name added, create an independent section with the additional information.

3 Add the DSN name specified using mdsconfig for the location of the MDS repository to the odbc.ini file on all Linux machines running the MDS base software.

4 If a Linux machine will be loading databases with the metaload utility, the odbc.ini file for that Linux machine must have a DSN for each Teradata system to be loaded.

Step 2: Install MDS Core Files

After installing the Teradata ODBC package and editing the appropriate odbc.ini file, install the core MDS executables and shared object libraries with the appropriate command. Use the PUT utility, mdsbaseinstall, or mdsbasenonstdinstall.

If mdsbaseinstall is used, the mdsbase software will be installed in the /opt/teradata/mds directory. The mdsbase software will be installed in a nonstandard location if specified with the PUT utility or mdsbasenonstdinstall.

After installing the mdsbase package, run the mdsconfig utility to configure the ODBC Data Source Name and Database User Name and Password for the MDS repository.

If you will not be installing the MDS Development Kit Files, proceed to Task 5: Set the MDS Configuration Parameters.

Step 3: Install MDS Development Kit Files (Optional)

After installing mdsbase, install the developer’s kit. The kit includes additional files, libraries, and source file examples on how to build MDS applications with the appropriate command. Use the PUT utility to install the mdssdk package or use the mdssdkinstall command.

The mdssdk software will be installed in the /opt/teradata/mds directory or a nonstandard location.

Proceed to Task 5: Set the MDS Configuration Parameters.

Task 5: Set the MDS Configuration Parameters

After installing the appropriate software on a workstation or server, set the MDS configuration parameters for each workstation or server.


Chapter 9: Installing Teradata Meta Data Services on LinuxTask 6: Create the Meta Data Repository

Step 1: Configure Linux Workstations or Servers

On Linux workstations the local configuration parameters are set using the mdsconfig program. You must be logged on as root to run mdsconfig.

The DSN name specified with mdsconfig for the location of the MDS repository should have been added to the odbc.ini file on the Linux workstation or server.

Command-line Syntax

The parameters for the mdsconfig program are as follows:

mdsconfig -h <metahome> -o <DSNname> -u <dbuser> -p <dbpasswd> -l <loglevel> -t <tracelevel> -s <numISvr>

Use mdsconfig –H to get help for the mdsconfig program.

If installing and using the Automatic DIM Update, refer to “Chapter 10 Installing Automatic DIM Update” on page 85 for additional installation and configuration tasks.

Task 6: Create the Meta Data Repository

The following instructions assume that the system does not have an existing MDS repository created from an earlier version of MDS. If a repository exists refer to “Task 7: Migrate the Meta Data Repository” for information on migrating the existing MDS repository to the current software version.


-h <metahome> The MDS Installation folder.

It is highly recommended that the default location of /opt/teradata/mds not be changed.

-o <DSN name> Default ODBC Data Source Name (DSN) that MDS uses to connect to the Teradata Database System containing the MDS repository.

-u <dbuser> Database User Name that MDS uses to log on to the Teradata DatabaseSystem to access the MDS repository.

-p <dbpasswd> Database User Password that MDS uses to log on to the Teradata Database System to access the MDS repository.

-l <loglevel> Error Log level (0..5). Where 0 is the least amount of logging and 5 is the greatest amount.

-t <tracelevel> Trace level (0..5) to be used for Application debugging. Where 0 is the least amount of tracing and 5 is the greatest amount of tracing.

-s <numIntSvr> Number of Integrity Servers for the MDS Data Definition Language (DDL) Gateway to start. Defaults to 5.

-H Displays option list.


Chapter 9: Installing Teradata Meta Data Services on LinuxTask 7: Migrate the Meta Data Repository

After installing the MDS software, the next step is to create the MDS repository.

Step 1: Create the Repository from a Linux Workstation

Use this procedure to create an MDS Repository from a Linux workstation.

Procedure - Creating the MDS Repository from a Linux Workstation

1 Log onto the workstation as root.

2 Run the /opt/teradata/mds/bin/metacreate program to create an MDS repository without versioning support or

Run the /opt/teradata/mds/bin/metacreate -v on program to create an MDS repository with versioning support.

Task 7: Migrate the Meta Data Repository

The following procedure assumes that the system has an existing MDS repository created from an earlier version of MDS. If the system does not have such a repository refer to “Task 6: Create the Meta Data Repository” for information on creating an MDS repository.

Procedure - Upgrading from an Earlier Version of Teradata

If also upgrading from an earlier version of Teradata, complete the following tasks before upgrading and migrating the MDS repository:

1 Save the database containing the MDS repository.

2 Upgrade the Teradata Database version.

3 Restore the MDS repository.

4 Install MDS 13.10 software components.

After installing the MDS software, migrate the existing MDS repository to the current software version.

Step 1: Migrate the MDS Repository on a Linux Workstation

Use this procedure to migrate the MDS Repository from a Linux workstation.

Procedure - To migrate the MDS Repository

✔ Run the metamigrate utility as directed in “metamigrate.”


Chapter 9: Installing Teradata Meta Data Services on LinuxTask 8: Create A Virtual Directory or Web Application

Task 8: Create A Virtual Directory or Web Application

After installation of MetaSurf, a virtual directory or web application to MetaSurf on the web server should be defined.

Procedure - Creating a Virtual Directory

1 When creating the virtual directory or web application, select an alias name for MetaSurf for example:

http://www.<yourhostname>/<mds>

or

http://<yourhostname>/<mds>

Where yourhostname is the name of the system and mds is the virtual name assigned for MetaSurf.

Note: When changes are made to the Teradata ODBC DSN or MDS configuration, web services may need to be restarted for the change to take effect.

2 For complete information on setting up the web server, starting and stopping web services, and using IIS manager to create a virtual directory or web applications, refer to the web server documentation.

3 Alter the appearance of the MetaSurf Web pages by:

• modifying the style sheets used

• defining new style sheets and incorporating them into MetaSurf

Style sheets, defined by the World Wide Web Consortium (W3C), allow you to describe the appearance of individual HTML tags. The style sheet tags describe the font, color, paragraph alignment, and other attributes for common HTML tags such as headings, paragraphs, lists, and tables. Style sheets separate the style and layout of HTML from the informational content.


Chapter 9: Installing Teradata Meta Data Services on LinuxTask 8: Create A Virtual Directory or Web Application


CHAPTER 10

Installing Automatic DIM Update

This section describes the Automatic DIM Update feature for Teradata Meta Data Services.

Task 1: Review Automatic DIM Update

This section contains general information on the Automatic DIM Update feature, information on software installation, configuration tasks required to implement and administer the feature.

Because the Teradata Database metadata is a central part of the Teradata MDS repository, it is vital to the use of MDS that the information be kept up to date and dynamically reflect any changes in the Teradata active data warehouse. The Automatic DIM Update feature will dynamically keep the MDS repository synchronized with the Teradata Database Systems it describes.

Step 1: Review the Automatic DIM Update Process

The following picture illustrates the processes supporting Automatic DIM updates.


Chapter 10: Installing Automatic DIM UpdateTask 1: Review Automatic DIM Update

Feature Description

Relay Services Gateway (RSG) The RSG is a Teradata VPROC that relays messages between Teradata and the MDS DDL Gateway.

Whenever a Teradata Database System processes a Data Definition Language (DDL) statement, it sends the DDL to the RSG, which sends it on to the MDS DDL Gateway. The DDL Gateway then updates the metadata in the MDS repository. An example of a DDL is:

create table mytable (c1 int);

Every Teradata node of the Teradata Database System must have an RSG VPROC running.

The RSG communicates via TCP/IP with the MDS DDL Gateway.

DDL Gateway The DDL Gateway consists of one client, one server, and one or more integrity server processes that keep the metadata in the MDS repository synchronized with Teradata. MDS can track changes to multiple Teradata systems. The DDL Gateway is also responsible for maintaining the audit trail of the DIM changes for each processed DDL statement. If the Audit Log Flag is set to “On”, an entry is inserted into the audit trail for each update to the DIM.

The DDL Gateway can be installed on an application node of the Teradata system or on a separate Windows or Linux box. Only one instance of the DDL Gateway is allowed.



MDS Action Processor The MDS Action Processor is responsible for polling the Audit Log for expired entries and purging the expired entries. The MDS Action Processor is also responsible for sending messages to the MDS DDL Gateway to initiate scheduled recovery.

The MDS Action Processor runs on Windows or Linux and only one MDS Action Processor can be run.

The Action Poll Rate defined in the MetaManager System-Wide Parameters defines the frequency that the MDS Action Processor will reread the MDS system settings to pick up changes to the Audit Flag, Audit Trail Expiration Days, and DIM Update Recovery Schedule for each Teradata System object. The default setting for the Action Poll Rate is 5 minutes. The Action Poll Rate can be increased to a maximum of 1440 minutes (24 hours).

The MDS Action Processor will poll the MDS Audit Trail every 24 hours at 1:30 a.m. local time to remove expired entries in the Audit Trail.

A Recovery Schedule is configured in MDS for each Teradata Database System. The MDS Action Processor will monitor the schedule times for each Teradata system and send a message to the MDS DDL Gateway server when scheduled recovery is to be performed on each system.

MDS Recovery Tables For the Automatic DIM update feature to be enabled on each Teradata Database System loaded into the MDS repository, an MDS Recovery Table must exist on each of the Teradata Database Systems.

V2R5 (or later) Teradata Database Systems automatically contain an MDS Gateway MDS Recovery Table. The table has a fixed name (mdsrecoverytbl) and location (DBC).

Database Connection Information When creating a System with Automatic DIM Updates enabled, a DSN, user name and password for the DDL Gateway to use to connect to the system are specified in MetaManager.The Gateway Server process uses these settings to resync a database during recovery and to access the MDS Recovery Table. The Gateway Integrity Servers use these settings to connect to the system to get information from the DBC tables.

DDL Gateway User Accounts If the DDL Gateway is running on Linux, the Gateway uses the Teradata user name specified in mdsconfig to connect to the MDS repository. The Gateway uses the Teradata user name specified in MetaManager’s system configuration to connect to other Teradata systems.

Feature Description



Step 2: Review Out of Sync Recovery

The MDS repository can be out of sync with a Teradata Database System for a number of reasons:

• A Teradata Database System, RSG and/or MDS DDL Gateway reset occurs.

• An error occurs and an Integrity Server cannot commit a transaction to the repository.

• The MDS DDL Gateway goes down and does not come back up right away. In this case Teradata is processing DDLs and not forwarding them on to MDS but is writing the database names to the MDS Recovery Table.

• The Integrity Servers have a backlog of transactions that have not yet been processed.

When the Automatic DIM Update feature is enabled, the task of keeping track of the DDL Transactions is divided among the three components: Teradata Database System, RSG, and DDL Gateway Server.

Feature Description

Teradata Database System When the MDS DDL Gateway is down, the Teradata Database System will process DDL statements but will write the names of all “Affected” databases to the MDS Recovery Table. There is one MDS Recovery Table per Teradata Database System.

When the MDS DDL Gateway Server comes up, if the Recovery on Startup flag is checked, it will read the MDS Recovery Table and resynchronize the repository for each database name listed in the table.

RSG The RSG keeps track of the in-progress Teradata DDL transactions. These are DDLs that the Gateway Server has not yet captured in its log and has not responded to Teradata to complete the transaction. When the RSG detects that the MDS DDL Gateway has gone down or receives a reset message from the MDS DDL Gateway Server, the RSG will abort the in-progress transactions with the Teradata Database System.


Chapter 10: Installing Automatic DIM UpdateTask 2: Configure Automatic DIM Update Software

Task 2: Configure Automatic DIM Update Software

If the Automatic DIM Update feature is desired, there are additional configuration tasks that must be performed before using this feature.

DDL Gateway Server DDL Gateway Server

The MDS DDL Gateway Server will keep track of the database names of all DDL transactions that it has received messages for. It will track the transaction in a backlog list and in a log file. The log will be combined with the MDS Recovery Table to resync the repository. Only databases that are out-of-sync will be resynced during recovery.

The DDL Gateway Server performs recovery:

• On startup of the DDL Gateway. On startup, the Gateway Server looks in the MDS Recovery Table and in its own log to determine which databases need recovery. If the Teradata Database System is configured in MDS to have the “Recovery On Startup” flag enabled, the Gateway will begin recovery for that system. If the flag is not set, recovery will be deferred until the scheduled time.

• When the DDL Gateway receives a “Recover now” message from the MDS Action Processor. Scheduled recovery will only occur once per day for each Teradata Database System based on the schedule configured for that system in MDS. The schedule configuration also specifies the days of the week to perform scheduled recovery.

The Gateway Server performs the following steps when performing recovery:

• The Gateway Server sends a message to the Teradata Database to stop sending DDLs to RSG and to log “Affected” databases in the MDS Recovery Table.

• The Gateway Server reads and deletes MDS Recovery Table entries, reads the backlog list and compiles a list of database names to resync.

• Calls the metaload utility to resync each database name.

• Reads and deletes the MDS Recovery Table again to resync databases that may have been affected by DDLs during the resync process.

• Sends a message to the Teradata Database to start sending DDLs to RSG.

Feature Description


Chapter 10: Installing Automatic DIM UpdateTask 3: Install DIM Update Server Software (Linux)

You will need to install and configure software on your designated Automatic DIM Update Server. In addition installing or configuring software on TPA nodes.

Step 1: Configure Linux Servers

If the designated DIM Update Server is a Linux machine, the configuration tasks are as follows:

• Install and configure required packages on the DIM Update Server

• Install RSG on TPA nodes

• Configure the RSG VProcs on TPA nodes

Task 3: Install DIM Update Server Software (Linux)

The designated DIM Update Server must already have the MDS Core software files (mdsbase package) installed before continuing.

Step 1: Install the MDS Action Processor

After installing mdsbase, install the MDS Action Processor package (mdsap) on the DIM Update Server using the:

• mdsapinstall command for Linux

• PUT utility

The mdsap software is required to support the scheduled recovery and Audit logging. It will be installed in the/opt/teradata/mds/bin directory.

The mdsap package will install a default odbc.ini file in/opt/teradata/mds/msg_txt.

• If the ODBCINI environment variable is not set, the package installation will use the /opt/teradata/mds/msg_txt/odbc.ini file.

• The installation will not change the environment variable if the ODBCINI environment variable is set. The MDS Action Processor will use the odbc.ini file specified in the environment variable.

• If the default odbc.ini file installed by the package is used, it will need to be modified to add the data source information.

The MDS Action Processor is started automatically at system startup or can be started using the /etc/init.d/mdsap start script.

Step 2: Install the MDS DDL Gateway

After installing mdsbase and the mdsap package, install the MDS DDL Gateway package mdsgwy on the DIM Update Server using the

• mdsgwy install command for Linux


Chapter 10: Installing Automatic DIM UpdateTask 3: Install DIM Update Server Software (Linux)

• PUT utility

The mdsgwy software will be installed in the /opt/teradata/mds/gateway directory.

The mdsgwy package will install a default odbc.ini file in/opt/teradata/mds/msg_txt.

• If the ODBCINI environment variable is not set, the DDL Gateway software will use the /opt/teradata/mds/msg_txt/odbc.ini file.

• The installation will not change the environment variable if the ODBCINI environment variable is set. The DDL Gateway will use the odbc.ini file specified in the environment variable.


The DDL Gateway processes are started automatically at system startup or can be started using the /etc/init.d/mdsgwy start script. The DDL Gateway processes are not started at installation.

Note: On initial installation of the DDL Gateway, the status of the system is “Down” and a message similar to the following appears in the mds log:

10/18/02 15:31:43|PID-523|5|CGwaySocket::Get HostByAddr(153.64.14.126) returns ‘SMP001-4’

The first name specified for a node in the /etc/hosts file is the primary node name for the node. This is the name that must be used for a node defined for a system in the MetaManager GUI. Correct the etc/hosts file or the MetaManager node names.

Step 3: Configure Linux System Parameters

The mdsgwy package will automatically increase the following Linux system tunable parameters (in /etc/sysctl.conf) to these values:

• kernel.msgmnb=2097152

• kernel.msgmni=1000

• kernel.msgmax=32767

Step 4: Configuring the ODBC.INI File

The mdsgwy or mdsap package will install an odbc.ini example file /opt/teradata/mds/msg_txt.

• The mdsgwy (and mdsap) software will use the /opt/teradata/mds/msg_txt file if the ODBCINI environment variable is not set.

• The installation will not change the environment variable if the ODBCINI environment variable is set. The DDL Gateway and MDS Action Processor will use the odbc.ini file specified in the environment variable.


Add the necessary DSN names to the ODBC Data Sources section and then create independent sections that match each of the names that were added.


Chapter 10: Installing Automatic DIM UpdateTask 4: Install and Configure RSG

For all systems running the MDS Action Processor, or the DDL Gateway, the DSN name specified via mdsconfig for the location of the MDS repository needs to be added to the odbc.ini file.

Add a DSN for each configured Teradata system to the odbc.ini file used by the MDS DDL Gateway.

Step 5: Add Services to the Linux /etc/services File

The following services are added to the /etc/services file on your designated DIM Update Server.

TxServer 56969/tcp # MDS Gateway Server RSiMsg 56970/tcp # RSG Server

The Linux services file changes will be done as a consequence of installing mdsgwy. They may have been previously done as a consequence of installing mdsap or RSG.

Task 4: Install and Configure RSG

Every node of every Teradata Database System that is to be loaded into the MDS repository and tracked with the Automatic DIM Update feature must have RSG installed and RSG vprocs configured and running.

Under Linux, the RSG package must be installed on the appropriate nodes.

Edit the RSG configuration files to:

• indicate where the MDS DDL Gateway is installed and

• which node is the RSG master node

Creating and configuring RSG vprocs is required.

Step 1: Install and Configure RSG on Linux

Procedure - Install RSG on Linux

1 Run the PUT utility before the initial install of RSG and add the RSG vprocs to the appropriate nodes. The RSG vproc on the RSG master node should have id 9215; secondary RSG nodes should use smaller RSG vproc ids.

Note: The vconfig.txt file on Linux created by PUT also contains RSG vproc information, including whether the vproc is movable or not. It should always say the vproc is not movable. The RSG vproc type is defined in the DBS startup.txt file on Linux, and is 4. The RSG partition is partition 19.

2 It is strongly suggested that a TPA shutdown be done prior to installing RSG:

tpareset –x stop

If a TPA shutdown is not done at this time, it must remain up throughout the RSG installation.


Chapter 10: Installing Automatic DIM UpdateTask 4: Install and Configure RSG

If a TPA shutdown occurs during the RSG installation, and if the ctl utility on Linux shows that the “Running RSG” version is a version that is no longer on the system, ctl must be used to set the “Desired RSG” to the last installed RSG version, or blank it out. The next time a TPA start or reset is done, the system automatically switches to the “Desired RSG” version, or if it is blank, the last installed RSG version.

3 Run rsginstall on each Linux node, or use the PUT utility's “Additional Packages” menu to update all nodes simultaneously.

The RSG package is installed in the following directory on each Linux node:

<Teradata installation directory> /rsg/<version>

where <version> is the package version (e.g. 06.01.00.00).

The following services are added to the /etc/services file on the node when the RSG packages are installed.

TxServer 56969/tcp # MDS Gateway Server RSiMsg 56970/tcp # RSG Server

The Linux services file changes may or may not be done as a consequence of installing mdsgwy. The RSG package, if installed first, will make the changes.

4 Edit each node’s RSG configuration file, <tdconfig directory>/rsg/rsg.cfg on Linux to indicate where the MDS DDL Gateway is installed and which node is the RSG master node.

MDSGWYNODE=<MDS Gateway node name>RSGMASTERNODE=<RSG master node name> DEBUGTRACE=<optional; can have value ON, OFF, or REPLACE>

REPLACE indicates that at the next TPA reset, the old RSG log file will be removed and a new log file created.

If the MDSGWYNODE or the RSGMASTERNODE value is NULL, RSG will keep trying to read the RSG configuration file. It will sleep between tries.

5 If the tdinfo utility on Linux indicates that the RSG vproc is not online, run the vprocmanager utility to set it offline and then online as follows:

set xxxx offline

set xxxx online

Where xxxx is the ID of the vproc.

Repeat these steps for each RSG vproc.

Note: The vprocmanager utility cannot be used to set the state for Hot Swap Nodes.

6 Run the dbscontrol utility and turn on the “MDS is Enabled” flag:

modify general 38=TRUE

write

quit

7 Restart the Teradata Database.


Chapter 10: Installing Automatic DIM UpdateTask 5: Configure Automatic DIM Update in MetaManager

Step 3: Start/Stop the RSG

RSG starts automatically with the Teradata Database if the “MDS is Enabled” flag is set in dbscontrol.

To validate that the “MDS is Enabled” flag is set, run the dbscontrol utility. Display the “MDS is Enabled” flag with:

display general

There is an Event Viewer log entry indicating that the RSG has been started.

If DEBUGTRACE is set to ON, full RSG logging will take place. If it is set to OFF, then minimal logging occurs. The REPLACE option will replace the old log file and start a new one when a Teradata TPA reset occurs.

On Windows, the files are located in <tdconfig directory>\RSG.There is one set of files per node.

Procedure - Putting the RSG vproc online in Linux

1 If the tdinfo utility on Linux indicates that the RSG vproc is not online, run the vprocmanager utility to set it online as follows:

set 9215 online

The RSG will be stopped when the Teradata Database is stopped.

Task 5: Configure Automatic DIM Update in MetaManager

Use MetaManager to enable Automatic DIM Update. The steps to be performed are:

1 Add a Teradata Database System.

2 Add all Teradata nodes to the Teradata Database System.

3 Load databases.

4 Enable DIM Update and optionally setting the recovery database and table names, Recovery on Startup flag, and recovery schedule.

Step 1: Add a Teradata Database System

For details on this, see, “Administer MDS with MetaManager” of the Teradata Meta Data Administration Guide.

Step 2: Add Teradata Nodes to a Teradata Database System

Configure Nodes

The Automatic DIM Update feature requires that Teradata nodes on the Teradata Database System be configured.



Add a Node

Procedure - Adding a Node

Nodes may be added to a system, edited or deleted. A node definition consists of a name and the node status (Up or Down).

1 In MetaManager, select a system. In the example shown, the system’s name is “simca.”

2 Click System>Add Node. The Add Node dialog appears.

3 Type in the node name, choose the node status, and click OK.

The node names are not arbitrary. Each name must be the primary name (first name after the IP address in an /etc/hosts file) for its IP address and not an alias. The node names must be unique within the enterprise, not just within the Teradata Database System.

4 A request is made to add another node. When you are finished adding nodes, they will appear in MetaManager.



Edit a Node in Meta Manager

Procedure - Editing a Node in MetaManager

1 In MetaManager, choose the node to edit, then right-click on it to display the shortcut menu.

2 Click Edit, and an Edit node dialog box will appear.

3 The node status can be changed to Up or Down.

The status of the node should be set Down if the node on the Teradata Database System is to be removed for an extended period. This will prevent the MDS DDL Gateway from sending messages to the RSG on the node when it is unavailable.

Step 3: Load Databases

MDS loads data dictionary information for each of the selected databases into the MDS repository. The actual data in the databases’ tables is not loaded.

The option used to load databases into the MDS repository determines what databases the DDL Gateway keeps in sync. The difference is in how the DDL Gateway handles newly created users and databases in the Teradata Database System.



For all other DDLs, the DDL Gateway will update the repository for loaded databases and will ignore DDL for databases that are not loaded into the repository.

If databases are loaded for a Teradata Database System, the MDS DDL Gateway will not track that system even if Automatic DIM Update is enabled for the system.

Before enabling DIM Update, load all databases to be maintained. If there is a lengthy time between the initial load of the databases and when DIM Update is enabled, resync all databases before enabling DIM Update.

For details on this, see “Resynchronize Databases” in “Administer MDS with MetaManager” of the Teradata Meta Data Administration Guide.

Step 4: Enable Automatic DIM Update

Procedure - Enabling the Automatic DIM Updater

1 In MetaManager, choose the system which will have Automatic DIM Update enabled, then right-click it.

2 Click DIM Update, and the DIM Update dialog appears.

3 Select the Enable DIM Update check box.

4 Click OK to exit the dialog. From this dialog select the Recovery on Startup check box or define the recovery schedule by clicking Schedule (both are optional).

The MDS Recovery Table keeps track of the database name for each DDL that occurs while the DDL Gateway is down. If RSG detects that the Gateway is down, RSG notifies Teradata to

Load... Description

All Databases If “All” databases is chosen, the DDL Gateway will automatically add new databases and users that are created in the Teradata Database System to the MDS repository. In other words, “All” indicates that the MDS repository will contain all databases in the Teradata Database System.

Selected Databases If “Selected” databases is chosen, the DDL Gateway will NOT add new databases and users that are created in the Teradata Database System to the MDS repository. The DDL Gateway will maintain only those databases selectively loaded into the MDS repository.

All but Selected If “All but Selected” databases is chosen – the DDL Gateway will automatically add new databases and users that are created in the Teradata Database System to the MDS repository. It, however, maintains the list of those databases that were excluded on the initial load and ignores all DDLs for those databases. Databases that were originally loaded but are later unloaded are considered to be databases that are excluded.


Chapter 10: Installing Automatic DIM UpdateTask 6: Check DIM Update Status with MetaManager

begin writing to the MDS Recovery Table. When the Gateway comes back up, it reads the MDS Recovery Table and marks each of the databases in the MDS Recovery Table as “out of sync.” The Gateway will resync each database if Recovery on Startup is selected or at a scheduled recovery time.

The recovery database is always DBC and the MDS Recovery Table is mdsrecoverytbl.

The Teradata user specified in the System Object must have SELECT and DELETE privileges to the MDS Recovery Table.

Task 6: Check DIM Update Status with MetaManager

Procedure - Checking DIM Update Status with MetaManager

1 From MetaManager, click System>Database Systems.

2 In the Teradata Meta Data Services Administration window, highlight a system name, click Database Administration. The Teradata Meta Data Services Administration dialog appears.

To go directly to the Teradata Meta Data Services Administration dialog, from the MetaManager main window, right click on the system with database(s) to administer, and click Database Administration.

3 Click the Dim Update Status tab to determine if any databases are marked out of sync by the DDL Gateway.

The DIM Update Status tab is disabled if Automatic DIM Update has not been enabled for your system. Refer to “Step 4: Enable Automatic DIM Update” on page 97 for additional information.

The DIM Update Status window shows:

Name Description

System Name Displays the system chosen

DIM Update Status Displays the DIM Update status of the system. The status codes are:

UP DIM Update is up and tracking changes to the system

DOWN DDL Gateway has not yet notified the Teradata Database System to begin sending DDLs

STOPPED DIM Update is disabled and not tracking changes to the system

RESYNC Gateway is currently running recovery (scheduled or on startup)


Chapter 10: Installing Automatic DIM UpdateTask 7: Start/Stop the DDL Gateway

Task 7: Start/Stop the DDL Gateway

The DDL Gateway is automatically started at system boot and stops at system shutdown. The DDL Gateway starts as a service on Windows. The names of the DDL Gateway programs are:

Procedure - To Manually Start the DDL Gateway on Linux

1 To manually start the DDL Gateway on Linux, execute:

/etc/init.d/mdsgwy start

Procedure - To Manually Stop the DDL Gateway on Linux

1 To manually stop the DDL Gateway on Linux, execute:

/etc/init.d/mdsgwy stop

Task 8: Start/Stop the MDS Action Processor

The MDS Action Processor is automatically started at system boot and stops at system shutdown. The MDS Action Processor starts as a service on Windows.

The name of the MDS Action Processor program is metaaction on Linux.

UNKNOWN MetaManager could not contact the DDL Gateway to get the status or the DDL Gateway does not know about the system

Database out of sync Displays the list of database names that the DDL Gateway has marked out of sync including those that were in the MDS Recovery Table.

Refresh List Updates the display

Sync Now Sends a message to the DDL Gateway to immediately begin recovery to synchronize the Out of Sync databases.

Name Description

Gateway Component Linux Program Name

Gateway Server gwserver

Gateway Client gwclient

Integrity Servers iserver


Chapter 10: Installing Automatic DIM UpdateTask 8: Start/Stop the MDS Action Processor

Procedure - Manually Start the MDS Action Processor on Linux

1 To manually start the MDS Action Processor on Linux, execute:

/etc/init.d/mdsap start

Procedure - Manually Stop the MDS Action Processor on Linux

1 To manually stop the MDS Action Processor on Linux, execute:

/etc/init.d/mdsap stop


CHAPTER 11

Deploying Across the Network

This section describes tar_teradata_client_packages script. The script is intended for use by system administrators tasked with deploying Teradata Tools and Utilities products across a network

Task 1: Review Script Information

The tar_teradata_client_packages script downloads Teradata client packages from a Windows or UNIX system disk mount and packages them in a tar file for distribution to other UNIX and Linux systems. If the gzip executable is installed, packages will be compressed accordingly. The tar file can include either all packages, or specific packages depending on the command options selected.

Dependent Teradata Tools and Utilities packages are automatically included in the tar file. The files are copied from the Teradata Client media. Third-party software dependencies must be installed separately.

Step 1: Determine Platform Compatibility

The script runs on all of the major UNIX and Linux platforms that Teradata Client supports:

• AIX

• HP-UX

• SUSE Linux

• Red Hat Linux

• Sun Solaris SPARC

• Solaris Opteron

• Executed within a Windows command window (DOS)

• On UNIX machines with the Korn shell (/bin/ksh).

Step 2: Determine the Contents of the Tar File

The tar_teradata_client_packages script is contained on each of the Teradata Tools and Utilities installation CD ROMs for UNIX systems. It allows the creation of a subset of the Teradata client packages from the CD ROM media by simply copying a single tar file across the network.

The tar file created:


Chapter 11: Deploying Across the NetworkTask 1: Review Script Information

• Contains all of the files for the specified platform, or all the files for a specified package

• Includes all of the dependent packages for the client packages in the file

Step 3: Determine if Script Dependencies are Installed

The tar executable must be located in the PATH on the system running the script.

Note: Windows does not automatically include tar.exe or gzip.exe. They must be installed manually.

If the tar.exe executable isn't located on the system, the script aborts and provides a suggested location for the user to download the GNU version of tar.exe from the following web address:

ftp://ftp.gnu.org/pub/pub/gnu/tar/tar-1.12.msdos.exe

Note: On a UNIX system, the tar program is typically available in /bin.

If the gzip executable (“gzip.exe” on Windows) is available in the PATH, the script will attempt to compress the tar file, in order to make it smaller to transfer across a network.

Note: The Linux tar file only compresses a small amount, compared to the other platform's

packages.

Step 4: Review Script Usage

Two version of the script have been provided. Descriptions of what they do are contained in the following tables.

• tar_teradata_client_packages.bat for Windows

• tar_teradata_client_packages.sh for UNIX and Linux systems

Command Description

tar_teradata_client_packages

or

tar_teradata_client_packages help

Runs displays tar_teradata_client_packages help.

Running tar_teradata_client_packages without any parameters, or with the help parameter specified, displays the available commands.

tar_teradata_client_packages list Lists the platforms and available packages on the CD.

Specifying the single parameter list displays the available platforms and packages for that media.




tar_teradata_client_packages list {platform} Lists the products available for a specific platform on the CD.

[platform] as first parameter - Running the script with [platform] as the first parameter creates a tar file in the default target path. The resulting tar file contains all of the Teradata client packages on that media for that system.

[platform] can be one of the following:

• aix

• hpux or hp-ux

• linux

• mpras

• sparc

• opteron

The path for the output can be changed, but the output filename will be in the format:

teradata-client-{platform}-{media name}.tar (.gz if compressed)

[platform] as second parameter - Running the script with [platform] as the second parameter following the list parameter only lists the packages available for the specified platform.

tar_teradata_client_packages {platform} Runs the script creating a tar file for a specific platform, including all packages.

Optional parameters following <platform> list specific packages, including:

• bteq

• cliv2

• fastexp

• fastld

• mload

If any packages are specified, other than the four dependent packages, the dependent are all included:

• TeraGSS


• TDICU

• Teradata Data Connector

Adding package names (previously displayed by the “list” command) after the [platform] parameter always includes the dependent packages: TeraGSS, CLIv2, TDICU, and Data Connector (piom), if available on the media.

If any of these packages are individually specified, all of these dependencies are included in the archive.

Command Description



Note: The version of the package isn't needed with the package name. For example, Solaris displays the package as bteq1310. The parameter bteq will work as well as bteq1310.

Default Directory

The tar script prompts for a directory to create the tar file, and accepts Enter for the default user directory. The default is:

• C:\Documents and Settings\username is usually HOME for Windows

• UNIX sytem user's home directory for UNIX systems

• /tmp if the script is run as root on UNIX systems

tar_teradata_client_packages attempts to create the directory if it doesn't exist. If the location is read-only or unable to be written, the script ends.

Multiple and Dependent Packages

If a single package or multiple packages are selected, all of the dependent products are included, even if the product selected is one of the single dependent packages.

Typically, the dependent packages depend on each other; cliv2 depends on tdicu and TeraGSS, for example.

tar_teradata_client_packages {platform} [{package1} {package2} …]

Runs the script creating a tar file for a specific platform, and specific packages.

Optional parameters following <platform> list specific packages, including:

• bteq

• cliv2

• fastexp

• fastld

• mload

If any packages are specified, other than the four dependent packages, the dependent are all included:

• TeraGSS


• TDICU


Adding package names (previously displayed by the “list” command) after the [platform] parameter always includes the dependent packages: TeraGSS, CLIv2, TDICU, and Data Connector (piom), if available on the media.

If any of these packages are individually specified, all of these dependencies are included in the archive.

Command Description



Example: Getting Help on the Script

This example displays the help screen for tar_teradata_client_packages, run the tar executable without parameters, or with the help parameter:

D:\tar_teradata_client_packages

or

D:\tar_teradata_client_packages help

Example Help Screen

A screen similar to the following, listing the command usage and optional parameters, appears as a result of the command.

************************************************************************* Tar Teradata Client Packages v.13.10.00.00 *************************************************************************Tar Teradata Client Packages

Usage: tar_teradata_client_packages listtar_teradata_client_packages list {platform}tar_teradata_client_packages {platform} [{package1} {package2} ...]

Parameters:

commands : help, list, {platform} [{package1} {package2} ...] help : Display this help message. list : List the available platforms and packages from the

media. list {platform} : List the packages available for the specified

platform. {platform} : Available platforms: aix, hpux, linux, mpras,opteron,

sparc Create the tar file for the supplied platform and

include all packages or individual packages. {package} : Specify the packages available on this media for the

specific platform. The parameter "all" (or blank) will include all available packages. To specify individual packages, list the packages separated by a space. Example: ttcp.bat linux bteq fastld

The dependencies will automatically be included and do not need to be listed individually. The following packages are included:---TeraGSS cliv2 tdicu piom

Example: Listing the Available Packages and Platforms

This example lists all the platforms and packages contained on the CD, run the tar executable with the list parameter (platforms and packages vary), for example:

/mount/LoadUnloadVol2> tar_teradata_client_packages.sh list

Or, as a variant, to list all the packages for a specific platform available on the CD, run the tar executable with the list parameter followed by the platform parameter. for example:

/mount/LoadUnloadVol2> tar_teradata_client_packages.sh list HP-UX


Chapter 11: Deploying Across the NetworkTask 2: Download Packages

Example List of Platforms and Packages

A screen similar to the following appears as a result of the list command. It lists all the Platforms and packages on the current CD.

************************************************************************* Tar Teradata Client Packages v.13.10.00.00 *************************************************************************Load/Unload - Volume 2

The available platforms are:HP-UXLinux

The available packages are:--- HP-UX Productsbteq fastexp mload npaxsmod tdicu tpumpcliv2 fastld mqaxsmod piom TeraGSS

--- Linux Productsbteq fastexp mload npaxsmod tdicu tpumpcliv2 fastld mqaxsmod piom TeraGSS

Task 2: Download Packages

Step 1: Download tar.exe and gzip.exe to Windows

If installing from a Windows platform, perform this step, otherwise, continue with the next step.

Check if tar.exe is Already Installed

A screen similar to the following appears, directing you to a location where the tar.exe file can be downloaded, if tar.exe is not installed, and the tar_teradata_client_packages executable is run on the Windows system:

D:\tar_teradata_client_packages

************************************************************************* Tar Teradata Client Packages v.13.10.00.00 *************************************************************************Load/Unload - Volume 2

ERROR:

The executable tar.exe doesn't exist on this system or isn't in the PATH.Please download the GNU tar executable from the following address:


Save the file as ‘tar.exe’ in the C:\WINDOWS directory, or to another directory in the PATH, then rerun this script again.

GNU Tar version 1.12 is the recommended tar for DOS to use.For more information see: http://www.gnu.org/software/tar/



Download tar.exe

Unless you have previously installed it, tar.exe does not exist in your C:\Windows directory. To install it, run:


and save tar-1.12.msdos.exe as tar.exe in your windows directory.

Check if gzip.exe is Already Installed

When the tar file is being created, and gzip.exe cannot be found a message similar to the following is displayed. To compress files, download gzip.exe.

Notice: The executable gzip.exe is not found. Download from www.gzip.org for MSDOS to automatically compress the output tar file to a gzip file.

Download gzip.exe

Unless gzip.exe was previously installed, gzip.exe does not exist in your C:\Windows directory. To install it, go to:

www.gzip.org

and download the MSDOS version to the C:\Windows directory

Step 2: Example: Archive Packages on a Windows Platform

This example, copies all SPARC packages on the installation CD to a Windows client. The resulting tar file can be copied to Sun Solaris SPARC machines, and the packages loaded there. The example first lists the packages with:

D:\tar_teradata_client_packages list

Then uses:

D:\tar_teradata_client_packages sparc

To download the SPARC files to:

C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar

In this example, gzip.exe has not been installed and the files are not compressed.

Display the List of Packages

Run the tar executable on the Windows system with the list parameter to list the products available for each product and platform:

D:\tar_teradata_client_packages list


************************************************************************* Tar Teradata Client Packages v.13.10.00.00 *************************************************************************Preprocessors - Volume 3

The available platforms are:AIX


www.gzip.org


Solaris

For Solaris Sparc use "sparc" for the platform parameter.For Solaris Opteron use "opteron" for the platform parameter.

The available packages are:--- AIX Productscliv2cobppsqlpptdicuTeraGSS

--- Solaris Sparc Productscliv21310sqlpp1310tdicu1310TeraGSSTeraGSS32

--- Solaris Opteron Productscliv21310sqlpp1310tdicu1310TeraGSS_solaris-i386TeraGSS_solaris-x8664

Archive Packages for a SPARC Platform

In this example, the Sun Solaris SPARC packages and dependencies on the CD are downloaded to a Windows client PC:

D:\tar_teradata_client_packages sparc

************************************************************************* Tar Teradata Client Packages v.13.10.00.00 *************************************************************************Preprocessors - Volume 3Platform: Solaris\Sparc

Default Path and Output File:C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar

Hit [Enter] to accept the path: "C:\Documents and Settings\<user>",or input a different save directory :Output File "C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar"

Press Enter to download the packages:

---Archiving all packages for sparc.tar cvf "C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar" Solaris\SparcSolaris/Sparc/Solaris/Sparc/TeraGSS/Solaris/Sparc/TeraGSS/install/Solaris/Sparc/TeraGSS/install/depend..(more files)



.Solaris/Sparc/tdicu1310/reloc/$LIBDIR64/libiculxtd.so.36.0Solaris/Sparc/tdicu1310/reloc/$LIBDIR64/libicuuctd.so.36.0tar rvf "C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar" .setup.sh.setup.shtar rvf "C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar" setup.batsetup.battar rvf "C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar" MEDIALABELMEDIALABELtar rvf "C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar" tar_teradata_client_packages.*tar_teradata_client_packages.battar_teradata_client_packages.sh

Notice: The executable gzip.exe is not found. Download from www.gzip.org for MSDOS to automatically compress the output tar file to a gzip file.

The file has been saved at : C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar

Step 3: Example: Archive Packages on a Linux Platform

This example, copies all packages and dependencies on the installation CD for a SUSE Linux or Red Hat Linux client by running:

D:\tar_teradata_client_packages linux

The command creates the tar file:

C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar

gzip is automatically run on the output tar file and the resultant compressed file is:

C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar.gz

Archive and Compress Packages for Linux

Run the tar executable with linux as the platform:

D:\tar_teradata_client_packages linux

************************************************************************* Tar Teradata Client Packages v.13.10.00.00 *************************************************************************Load/Unload - Volume 2Platform: Linux

Default Path and Output File:C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar

Hit [Enter] to accept the path: "C:\Documents and Settings\user",or input a different save directory :



Output File "C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar"---Archiving all packages for linux.tar cvf "C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar" Linuxa Linux/mqaxsmod/mqaxsmod-13.10.00.00-1.i386.rpm 118 blocksa Linux/mload/mload131-13.10.00.00-1.i386.rpm 374 blocksa Linux/piom/piom131-13.10.00.00-1.i386.rpm 79 blocksa Linux/tdicu/tdicu-13.10.00.00-1.noarch.rpm 20564 blocksa Linux/fastld/fastld131-13.10.00.00-1.i386.rpm 189 blocksa Linux/TeraGSS/TeraGSS_redhatlinux-i386-13i.10.00.00-1.i386.rpm 12240 blocksa Linux/fastexp/fastexp131-13.00.00.00-1.i386.rpm 341 blocksa Linux/tpump/tpump131-13.10.00.00-1.i386.rpm 478 blocksa Linux/npaxsmod/npaxsmod-13.10.00.00-1.i386.rpm 272 blocksa Linux/cliv2/cliv2-13.10.00.00-1.x86_64.rpm 766 blocksa Linux/bteq/bteq-13.10.00.00-1.i386.rpm 303 blockstar rvf "C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar" .setup.shtar: blocksize = 20a .setup.sh 282 blockstar rvf "C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar" setup.battar: blocksize = 20a setup.bat 1 blocktar rvf "C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar" MEDIALABELtar: blocksize = 20a MEDIALABEL 1 block

The file has been saved at : C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar.gz

Step 4: Example: Archive a Single Package for a UNIX Platform

This example downloads the bteq packages and dependencies for a HP-UX client and compresses them with gzip.exe:

D:\tar_teradata_client_packages tar hp-ux bteq

HP-UX with BTEQ Example

Run the tar executable with HP-UX as the platform:

D:\tar_teradata_client_packages tar hp-ux bteq

************************************************************************* Tar Teradata Client Packages v.13.10.00.00 *************************************************************************Load/Unload - Volume 2Platform: HP-UXDefault Path and Output File:C:\Documents and Settings\user\teradata-client-hp-ux-load-unload-volume-2.tarHit [Enter] to accept the path: "C:\Documents and Settings\user",or input a different save directory :d:Output File "d:\teradata-client-hp-ux-load-unload-volume-2.tar"---Archiving setup files and dependency packages for hp-ux



tar cvf "d:\teradata-client-hp-ux-load-unload-volume-2.tar" HP-UX\TeraGSS*a HP-UX/TeraGSS/ia64/pkginfo.txt 1 blocka HP-UX/TeraGSS/ia64/TeraGSS_hpux-ia64_13.10.00.00.depot 164540 blocksa HP-UX/TeraGSS/ia64/TeraGSS_hpux-ia64_13.10.00.00.psf 3 blocksa HP-UX/TeraGSS/pa32/pkginfo.txt 1 blocka HP-UX/TeraGSS/pa32/TeraGSS_hpux-pa32_13.10.00.00.depot 114340 blocksa HP-UX/TeraGSS/pa32/TeraGSS_hpux-pa32_13.10.00.00.psf 3 blockstar rvf "d:\teradata-client-hp-ux-load-unload-volume-2.tar" HP-UX\tdicu*tar: blocksize = 20a HP-UX/tdicu/ia64/swagent.log 3 blocksa HP-UX/tdicu/ia64/tdicu1310/tdicu1310/opt/teradata/client/13.10/tdicu/lib/libicudatatd.so.36.0 16206 blocksa HP-UX/tdicu/ia64/tdicu1310/tdicu1310/opt/teradata/client/13.10/tdicu/lib/libicui18ntd.so.36.0 24941 blocksa HP-UX/tdicu/ia64/tdicu1310/tdicu1310/opt/teradata/client/13.10/tdicu/lib/libicuiotd.so.36.0 773 blocks…a HP-UX/bteq/pa32/catalog/swlock 0 blocksa HP-UX/bteq/pa32/catalog/INDEX 9 blocksa HP-UX/bteq/pa32/catalog/bteq1310/bteq1310/INFO 4 blocksa HP-UX/bteq/pa32/catalog/bteq1310/bteq1310/INDEX 1 blocka HP-UX/bteq/pa32/catalog/bteq1310/bteq1310/postinstall 10 blocksa HP-UX/bteq/pa32/catalog/bteq1310/bteq1310/postremove 5 blocksa HP-UX/bteq/pa32/catalog/bteq1310/bteq1310/preinstall 11 blocksa HP-UX/bteq/pa32/catalog/bteq1310/pfiles/INFO 1 blocka HP-UX/bteq/pa32/catalog/bteq1310/pfiles/INDEX 8 blocksa HP-UX/bteq/pa32/catalog/bteq1310/pfiles/README 1 blocka HP-UX/bteq/pa32/catalog/bteq1310/pfiles/_ACL 1 blocka HP-UX/bteq/pa32/catalog/bteq1310/pfiles/_LOCK_FILE 0 blocksa HP-UX/bteq/pa32/catalog/bteq1310/pfiles/_OWNER 1 blocka HP-UX/bteq/pa32/catalog/dfiles/INFO 1 blocka HP-UX/bteq/pa32/catalog/dfiles/INDEX 1 blocka HP-UX/bteq/pa32/catalog/dfiles/_ACL 1 blocka HP-UX/bteq/pa32/catalog/dfiles/_PROD_DFLT_ACL 1 blocka HP-UX/bteq/pa32/catalog/dfiles/_LOCK_FILE 0 blocksa HP-UX/bteq/pa32/catalog/dfiles/_OWNER 1 blockThe file has been saved at : d:\teradata-client-hp-ux-load-unload-volume-2.tar.gz


CHAPTER 12

Configuring Teradata Tools and Utilities

This section contains procedures to configure the following Teradata Tools and Utilities software.

Task 1: Configure JDBC Driver for Teradata

For configuration instructions, see “Importing the SQL Package and Loading the Teradata JDBC Driver” in chapter 2 of the Teradata JDBC Driver User Guide.

Task 2: Configure the ODBC Driver

This section describes how to configure the ODBC Driver for Teradata for all supported operating systems.

After installing the ODBC Driver for Teradata, you must configure:

• Environment Variables

• The odbc.ini Template

• ODBC Data Sources

For complete configuration information on the ODBC Driver for Teradata, see the ODBC Driver for Teradata User Guide.

Follow the procedures in this section to configure the ODBC Driver for Teradata on all supported operating systems.

Step 1: Copy the Template odbc.ini File for ODBC

The odbc.ini template is located in the root directory where the ODBC Driver for Teradata software is installed. Before using an ODBC driver, copy this file to the home directory and rename it .odbc.ini.

The default location of the .odbc.ini file is the home directory, but a different path for the file using the ODBCINI environment variable can be specified. The .odbc.ini file is a hidden file.

To copy the .ini file to the home directory, enter:

cp /opt/teradata/client/ODBC_32/odbc.ini $HOME/.odbc.ini

or


Chapter 12: Configuring Teradata Tools and UtilitiesTask 2: Configure the ODBC Driver

cp /opt/teradata/client/ODBC_64/odbc.ini $HOME/.odbc.ini

Step 2: Setup Environment Variables for the ODBC Cursor Libraries for ODBC

For ODBC applications that request the Driver Manager to use the ODBC cursor library, the Run-time Shared Library Loader requires the following environment variables to contain the path to the ODBC Cursor library:

• SHLIB_PATH for HP-UX

• LIBPATH for IBM AIX

• LD_LIBRARY_PATH Solaris and HP-UX IA64 (all the remaining supported UNIX operating systems)

The Cursor library is:

• odbccurs.so for all UNIX platforms with the exception of the HP-UX

• odbccurs.sl for HP-UX

The ODBC API below is an example of how the ODBC Application triggers the usage of the ODBC Cursor library.

SQLSetConnectAttr(hdbc, SQL_ATTR_ODBC_CURSORS, (SQLUINTEGER *) SQL_CUR_USE_ODBC, SQL_IS_UINTEGER);

If the environment variable for the specific UNIX operating system does not include the path to the ODBC cursor library, then the following error is reported.

01000 "Cursor library not used. Load failed".

Setup SHLIB_PATH for ODBC on HP-UX

The SHLIB_PATH environment variable must reflect the location of the ODBC libraries on HP-UX.

Note: An optional environment variable ODBCINI is available that allows an application to use an alternate odbc.ini file. When specifying an alternate file, the full path name must be used.

Note: Using version independent directories, ODBC_32 and ODBC_64, the existing setup doesn’t have to be modified when upgrading to a newer version of ODBC Driver. Teradata ODBC install creates these version independent folders.

Procedure - Setting SHLIB_PATH for the ODBC on HP-UX

Follow these steps to setup the SHLIB_PATH environment variable to include the path to the ODBC Libraries:

1 Setup SHLIB_PATH for HP-UX.

2 If the ODBC driver was installed in /opt, append the following to SHLIB_PATH:

/opt/teradata/client/ODBC_32/lib


Chapter 12: Configuring Teradata Tools and UtilitiesTask 2: Configure the ODBC Driver

or


Setup LIBPATH for ODBC on IBM AIX

The LIBPATH environment variable must reflect the location of the ODBC libraries on IBM AIX.


Procedure - Setting LIBPATH for the ODBC on IBM AIX

Follow these steps to setup the LIBPATH environment variable to include the path to the ODBC Libraries:

1 Setup LIBPATH for IBM AIX.

2 If the ODBC driver was installed in /opt, append the following to LIBPATH:


or


Setup LD_LIBRARY_PATH for ODBC on Solaris and HP-UX IA64

The LD_LIBRARY_PATH environment variable must reflect the location of the ODBC libraries on Solaris and HP-UX IA64.


Procedure - Setting LD_LIBRARY_PATH for the ODBC on Solaris and HP-UX IA64

Follow these steps to setup the LD_LIBRARY_PATH environment variable to include the path to the ODBC Libraries:

1 Setup LD_LIBRARY_PATH for Solaris.

2 If the ODBC driver was installed in /opt, append the following to LD_LIBRARY_PATH:


or


Step 3: Setup NLSPATH for ODBC on Sun Solaris SPARC and Opteron

On Sun Solaris SPARC and Opteron, the NLSPATH environment variable must be set because the ODBC driver message catalog file (tdodbc.cat) is not guaranteed to be in the /usr/lib/odbc


Chapter 12: Configuring Teradata Tools and UtilitiesTask 3: Configure Teradata Parallel Transporter for Red Hat Linux

directory. The NLSPATH should include the directory containing the ODBC message catalog file.

Procedure - Setting NLSPATH for the ODBC on Solaris

Follow these steps to setup the NLSPATH environment variable to include the path to the ODBC message catalog:

1 Setup NLSPATH for Solaris.

/opt/teradata/client/lib/odbc/%N.cat

Step 4: Setup ODBC Data Sources

For complete configuration information, including information on setting up data sources for the ODBC Driver for Teradata, see the ODBC Driver for Teradata User Guide.

Task 3: Configure Teradata Parallel Transporter for Red Hat Linux

Follow the procedures in this section to configure the Teradata Parallel Transporter on Red Hat Linux.

The Teradata Parallel Transporter configuration normally requires modifications to only one file in the Teradata Parallel Transporter installation directory: twbcfg.ini

Additionally, the system configuration may require modification of the following parameters:

• Shared memory parameters: shmmax and shmmni

• Semaphore parameters: semmni and semmns

The following environment variables may also need to be modified:

• TWB_ROOT

• PATH

• SHLIB_PATH

• NLSPATH

Step 1: Edit the twbcfg.ini File on Red Hat Linux

After the Teradata Parallel Transporter Infrastructure package is installed, the configuration file, $TWB_ROOT/twbcfg.ini can be edited to change the default directory for checkpoint and logs. The $TWB_ROOT environment variable contains the installation directory for Teradata Parallel Transporter.

Logon as the root user and use an text and use a text editor to modify the configuration file.



To make a change in the configuration file, log in as root user to change the checkpoint or logs directory. For example, if the logs directory is full, then you should change the logs directory to another directory with free disk space.

No kernel rebuild or reboot is required after making the changes in the configuration file.

Step 2: Select Configuration File Defaults on Red Hat Linux

The configuration file contains parameters that determine the default behavior for Teradata Parallel Transporter Infrastructure, such as:

• Default checkpoint directory

• Default log directory

The Teradata Parallel Transporter configuration file defaults are:

CheckpointDirectory='/opt/teradata/client/13.10/tbuild/checkpoint'LogDirectory='/opt/teradata/client/13.10/tbuild/logs'

where: CheckpointDirectory refers to the directory that contains the checkpoint files for Teradata Parallel Transporter jobs.

where: LogDirectory refers to the directory that contains the binary logs for Teradata Parallel Transporter jobs. Each Teradata Parallel Transporter job creates a job log in the jobs directory. Refer to the Teradata Parallel Transporter Reference manual on how to read the job log.

Step 3: Setup the Shared Memory Parameters on Red Hat Linux

The Teradata Parallel Transporter Infrastructure installation process checks the values of the shared memory parameters for the required minimum values:

The following table lists the Linux Red Hat shared memory parameters.

Note: The Teradata Parallel Transporter Infrastructure installation does not support a formula value for a kernel parameter. If the value for a kernel parameter is less than the required minimum value, the installation will recommend increasing the value to the minimum value.

If any of the shared memory parameters is less than the minimum value, the Teradata Parallel Transporter Infrastructure installation recommends increasing the shared memory parameter to the minimum value.

The following procedure increases the Shared Memory value to the minimum value.


shmmax (minimum value of 4194304) The shmmax value determines the maximum size of a shared memory segment.

shmmni (minimum value of 200) The shmmni value determines the system wide limit on the number of shared memory segments that can be created.



Procedure - Increasing the Shared Memory Value to the Minimum Value

Follow these steps to increase the Shared Memory Value to the Minimum Value.

1 To check the value of the shmmni parameter:

# /sbin/sysctl kernel.shmmni

2 to increase the shmmni parameter to 200, you must be a root user:

3 On Red Hat Linux, add this line in the /etc/rc.d/rc.local file:

echo 200 > /proc/sys/kernel/shmmni

4 To shutdown the system in 1 minute:

# /sbin/shutdown -r +1

Step 4: Setup the Semaphore Parameters on Red Hat Linux

The Teradata Parallel Transporter Infrastructure installation process checks the values of the semaphore parameters for the required minimum value:

The following table lists the Linux Red Hat Semaphore parameters.


The most significant is the semmns semaphore parameter, which determines the number of semaphores in the entire system. The default configuration allows 1000 semaphores in concurrent use.

Step 5: Update Environment Variables

The Teradata Parallel Transporter Infrastructure installation updates the environment variables in the system /etc/profile and /etc/csh.login files.

The following table lists the Red Hat Linux environment variables updated.


semmni (set to 1000) The semmni value

semmns (set to 1000) The semmns value

Environment Variable Update to Environment Variable

TWB_ROOT Set to the Teradata Parallel Transporter installation directory.

PATH Add $TWB_ROOT/bin to the front of the PATH environment variable.



The updates to the environment variables are effective in the next login only if the Teradata Parallel Transporter Infrastructure package is installed. The updates to the environment variables allow users to run the installed version of Teradata Parallel Transporter.

If the Teradata Parallel Transporter API package is installed, then the LD_LIBRARY_PATH and NLSPATH environment variables must be updated manually.

• The 32-bit files is in $TWB_ROOT/lib and $TWB_ROOT/msg.

• The 64-bit files is in $TWB_ROOT/lib64 and $TWB_ROOT/msg64.

The environment variables must be updated on the command line, in the user's profile, or in the system profile.

• If the environment variables are updated on the command line, then the updates are effective only for the current session.

• If the environment variables are updated in the user's profile, then the updates are only effective every time that particular user logs in.

• If the environment variables are updated in the system profile, then the updates are effective every time any user logs in.

Note: Use the updates to the environment variables to run the installed version of Teradata Parallel Transporter. If the updates to the environment variables are not used, the installed version of Teradata Parallel Transporter will not run correctly.

If users do not use the updates to the environment variables, there are the commands to setup the environment variables:

Bourne and Korn shell users

• To setup the TWB_ROOT environment variable:

# TWB_ROOT=<Teradata Parallel Transporter installation directory># export TWB_ROOT

<Teradata Parallel Transporter installation directory> is the Teradata Parallel Transporter installation directory. You can find out the Teradata Parallel Transporter installation directory by running the /usr/bin/twbpkgrm tool.

• To update the PATH environment variable:

# PATH=$TWB_ROOT/bin:$PATH# export PATH

• To update the LD_LIBRARY_PATH environment variable:

# LD_LIBRARY_PATH=$TWB_ROOT/lib:$LD_LIBRARY_PATH# export LD_LIBRARY_PATH

• To update the NLSPATH environment variable:

LD_LIBRARY_PATH Add $TWB_ROOT/lib to the front of the LD_LIBRARY_PATH environment variable.

NLSPATH Add $TWB_ROOT/msg/%N to the front of the NLSPATH environment variable.




# NLSPATH=$TWB_ROOT/msg/%N:$NLSPATH# export NLSPATH

C-shell users


# setenv TWB_ROOT <Teradata Parallel Transporter installation directory>

where: <Teradata Parallel Transporter installation directory> is the Teradata Parallel Transporter installation directory. Run the /usr/bin/twbpkgrm tool. You can find out the Teradata Parallel Transporter installation directory by running the /usr/bin/twbpkgrm tool.


# setenv PATH $TWB_ROOT"/bin:$PATH"


# setenv LD_LIBRARY_PATH $TWB_ROOT"/lib:$LD_LIBRARY_PATH"


# setenv NLSPATH $TWB_ROOT"/msg/%N:$NLSPATH"

Step 6: Switch the IPC Memory Choice to Shared Memory on Red Hat Linux


Procedure - Switching the IPC Choice to Shared Memory

Follow these steps to switch the IPC Memory Choice to Shared Memory:

1 Log in as root user.

2 Change directories to the Teradata Parallel Transporter install directory.

cd <install dir>

3 Remove the “mmap” directory using this command:

# rm -rf mmap

Teradata Parallel Transporter will use shared memory as the IPC memory choice.

The change does not require a kernel rebuild or a reboot.

Step 7: Switch the IPC Memory Choice to Memory Mapped File on Red Hat Linux

The following procedure switches the IPC Memory Choice to Memory Mapped File:

Procedure - Switching the IPC Choice to Memory Mapped File

Follow these steps to switch the IPC Memory Choice to Memory Mapped File:



cd <install dir>


Chapter 12: Configuring Teradata Tools and UtilitiesTask 4: Configure Teradata Parallel Transporter on SUSE Linux

3 Create the “mmap” directory with “777” permission:

# mkdir mmap# chmod 777 mmap

Teradata Parallel Transporter will use memory mapped file as the IPC memory choice.


Task 4: Configure Teradata Parallel Transporter on SUSE Linux

This section contains instructions for configuring Teradata Parallel Transporter on SUSE Linux.

Step 1: Select the Default Installation Directory

The installation of a new version of Teradata Parallel Transporter prompts for the Teradata Parallel Transporter installation directory.

Here is a sample of the prompt:

Please specify the install directory [default: /opt/teradata/client/13.10/tbuild/]:

Press Enter to use the default installation directory.

Installation Directory Restrictions

The restrictions for the Teradata Parallel Transporter installation directory:

• Do not use “/” or “/usr” as the installation directory.

• The installation directory cannot be a relative directory path

• The pipe character “|” cannot be in the name of the installation directory

• The double quote character cannot be in the name of the installation directory

• The equal character “=” cannot be in the name of the installation directory

• The whitespace character cannot be in the name of the installation directory

Step 2: Select the Default Logs Directory

In addition to the Teradata Parallel Transporter installation directory, the Teradata Parallel Transporter Infrastructure package will prompt for the Teradata Parallel Transporter logs directory.

The following is an example of the prompt:

The logs directory contains Teradata Parallel Transporter job log files. The logs directory should be in a partition with a large free space. Please specify the logs directory [ default: /opt/teradata/client/13.10/tbuild/logs]:

Press Enter to use the default logs directory.



Logs Directory Restrictions

The following are the restrictions for the Teradata Parallel Transporter logs directory:

• The logs directory cannot be a relative directory path

• The whitespace character cannot be in the name of the logs directory

Step 3: Select the Interprocess Communication (IPC) Memory Choice

The Teradata Parallel Transporter package prompts for the interprocess communication (IPC) memory choice.

Teradata Parallel Transporter Infrastructure uses shared memory or memory mapped file for interprocess communication (IPC).Shared memory utilizes system shared memory for IPC.Memory mapped file utilizes temporary disk storage for IPC.Please select the IPC memory mechanism [ default: shared memory ]:

Enter 1 for shared memoryEnter 2 for memory mapped file

Press Enter, or Press 1, the IPC memory choice will be shared memory.

Press 2, the IPC memory choice is a memory mapped file and the Teradata Parallel Transporter package prompts for the memory mapped file directory.


The memory mapped file directory contains temporary Teradata Parallel Transporter job files.

The memory mapped file directory should be in a partition with a large free space.

Please specify the memory mapped file directory [ default: /opt/teradata/client/13.10/tbuild/mmap ]:

Press Enter to use the default memory mapped file directory:

Memory Mapped File Directory Restrictions

The restrictions for the Teradata Parallel Transporter memory mapped file directory include:

• The memory mapped file directory cannot be a relative directory path

• The whitespace character cannot be in the name of the memory mapped file directory

Note: During a reinstallation of the same Teradata Parallel Infrastructure version, the Teradata Parallel Infrastructure reinstallation does not request the IPC memory choice. The reinstallation re-uses the existing IPC memory choice.

Note: The first Teradata Parallel Transporter package requests the installation directory.

Subsequent Teradata Parallel Transporter packages of the same version do not request the installation directory, instead, they use the same installation directory as the first installation package.



Step 4: Select the System Kernel Values

The Teradata Parallel Transporter Infrastructure package checks for the following system kernel values.

The following table lists the kernel values checked.

Note: The Teradata Parallel Transporter Infrastructure installation does not support formula value. If the kernel value is a formula, then the Teradata Parallel Transporter Infrastructure installation displays a warning message.

If the system does not meet the required minimum value, the Teradata Parallel Transporter Infrastructure installation prompts to increase the value to the minimum required value.

Warning: The current value of 1048675 for the kernel parameter (shmmax) is less than the minimum required value of 4194304. shmmax refers to the maximum size of a shared memory segment.

Note: Increase the value to the minimum required value.

Note: A reboot is not required to make the above kernel parameter change(s) effective.

Do you want to increase the value to the minimum required value for the above kernel parameter(s)?

Please enter y for X or n for no [y,n,? (default : y)]

If N is entered, the Teradata Parallel Transporter Infrastructure package does not change the kernel value.

If Y is entered, or if Enter is pressed, the Teradata Parallel Transporter Infrastructure package changes the kernel value. A reboot is not required to make the kernel parameter change(s) effective.


At the end of the Teradata Parallel Transporter Infrastructure installation, the Teradata Parallel Transporter Infrastructure installation updates the environment variables in the system /etc/profile and /etc/csh.login files.

The following table lists the environment variables updated.

Kernel ParameterRequired Minimum Value Description

semmni 1000 Maximum number of semaphore sets in entire system.

semmns 1000 Maximum number of semaphores in entire system.

shmmax 4194304 Maximum size of a shared memory segment in bytes.

shmmni 200 Maximum number of shared memory segments in entire system.


Chapter 12: Configuring Teradata Tools and UtilitiesTask 5: Configure Teradata Parallel Transporter for Linux 390x

Updates to the environment variables are effective at the next login only if the Teradata Parallel Transporter Infrastructure package is installed. Updates to the environment variables allow users to run the installed version of Teradata Parallel Transporter.


• The 32-bit files are located in $TWB_ROOT/lib and $TWB_ROOT/msg.

• The 64-bit files are located in $TWB_ROOT/lib64 and $TWB_ROOT/msg64.





Note: Updates to the environment variables must be made, to run the installed version of Teradata Parallel Transporter properly.

Note: If updates to the environment variables are not made, then the installed version of Teradata Parallel Transporter does not run properly.

Task 5: Configure Teradata Parallel Transporter for Linux 390x

Follow the procedures in this section to configure the Teradata Parallel Transporter on Linux 390x.



• Shared memory parameters: shmmax and shmmni








• Semaphore parameters: semmni and semmns


• TWB_ROOT

• PATH

• SHLIB_PATH

• NLSPATH

Step 1: Edit the twbcfg.ini File on Linux 390x

After the Teradata Parallel Transporter Infrastructure package is installed, the configuration file, $TWB_ROOT/twbcfg.ini can be edited to change the default directory for checkpoint and logs. The $TWB_ROOT environment variable contains the installation directory for Teradata Parallel Transporter.

Logon as the root user and use an text and use a text editor to modify the configuration file.

To make a change in the configuration file, log in as root user to change the checkpoint or logs directory. For example, if the logs directory is full, then you should change the logs directory to another directory with free disk space.

No kernel rebuild or reboot is required after making the changes in the configuration file.

Step 2: Select Configuration File Defaults on Linux 390x




The Teradata Parallel Transporter configuration file defaults are:


where: CheckpointDirectory refers to the directory that contains the checkpoint files for Teradata Parallel Transporter jobs.


Step 3: Setup the Shared Memory Parameters on Linux 390x


The following table lists the Linux 390x shared memory parameters.




If any of the shared memory parameters is less than the minimum value, the Teradata Parallel Transporter Infrastructure installation recommends increasing the shared memory parameter to the minimum value.


Procedure - Increasing the Shared Memory Value to the Minimum Value

Follow these steps to increase the Shared Memory Value to the Minimum Value.

1 To check the value of the shmmni parameter:

# /sbin/sysctl kernel.shmmni

2 to increase the shmmni parameter to 200, you must be a root user:

3 On Red Hat Linux, add this line in the /etc/rc.d/rc.local file:

echo 200 > /proc/sys/kernel/shmmni

4 To shutdown the system in 1 minute:

# /sbin/shutdown -r +1

Step 4: Setup the Semaphore Parameters on Linux 390x

The Teradata Parallel Transporter Infrastructure installation process checks the values of the semaphore parameters for the required minimum value:

The following table lists the Linux 390x Semaphore parameters.






semmni (set to 1000) The semmni value

semmns (set to 1000) The semmns value






The following table lists the Linux 390x environment variables updated.

The updates to the environment variables are effective in the next login only if the Teradata Parallel Transporter Infrastructure package is installed. The updates to the environment variables allow users to run the installed version of Teradata Parallel Transporter.


• The 32-bit files is in $TWB_ROOT/lib and $TWB_ROOT/msg.

• The 64-bit files is in $TWB_ROOT/lib64 and $TWB_ROOT/msg64.





Note: Use the updates to the environment variables to run the installed version of Teradata Parallel Transporter. If the updates to the environment variables are not used, the installed version of Teradata Parallel Transporter will not run correctly.

If users do not use the updates to the environment variables, there are the commands to setup the environment variables:















# LD_LIBRARY_PATH=$TWB_ROOT/lib:$LD_LIBRARY_PATH# export LD_LIBRARY_PATH



C-shell users



where: <Teradata Parallel Transporter installation directory> is the Teradata Parallel Transporter installation directory. Run the /usr/bin/twbpkgrm tool. You can find out the Teradata Parallel Transporter installation directory by running the /usr/bin/twbpkgrm tool.




# setenv LD_LIBRARY_PATH $TWB_ROOT"/lib:$LD_LIBRARY_PATH"



Step 6: Switch the IPC Memory Choice to Shared Memory on Linux 390x






cd <install dir>


# rm -rf mmap


Chapter 12: Configuring Teradata Tools and UtilitiesTask 6: Configure Teradata Parallel Transporter on IBM AIX

Teradata Parallel Transporter will use shared memory as the IPC memory choice.


Step 7: Switch the IPC Memory Choice to Memory Mapped File on Linux 390x

The following procedure switches the IPC Memory Choice to Memory Mapped File:





cd <install dir>

3 Create the “mmap” directory with “777” permission:


Teradata Parallel Transporter will use memory mapped file as the IPC memory choice.


Task 6: Configure Teradata Parallel Transporter on IBM AIX

Follow the procedures in this section to configure the Teradata Parallel Transporter on IBM AIX.



• Shared memory parameters: shmmax, and shmseg

• Semaphore parameters: semmni, semmns, semmnu and semmap


• TWB_ROOT

• PATH

• SHLIB_PATH

• NLSPATH



Step 1: Select Default and Alternate Directories

Teradata Parallel Transporter allows a user-specified installation directory. The default installation directory for Teradata Parallel Transporter is /opt/teradata/client/<version>/tbuild.

where: <version> is the version number for Teradata Parallel Transporter.

For example, the default installation directory for Teradata Parallel Transporter version 13.10.00.00 is:

/opt/teradata/client/13.10/tbuild


The following are the restrictions on the installation directory for Teradata Parallel Transporter:






The first Teradata Parallel Transporter package requests the installation directory. Subsequent Teradata Parallel Transporter packages of the same version do not request the installation directory, but use the same installation directory as the first package installed.

E-fix Package Installation

The installation of a Teradata Parallel Transporter emergency fix (efix) package overwrites the installed Teradata Parallel Transporter package.

For example, the installation of Teradata Parallel Transporter Infrastructure 13.10.00.01 overwrites the Teradata Parallel Transporter Infrastructure 13.10.00.00 package.

This section contains instructions for installing the Teradata Parallel Transporter on IBM AIX.

Step 2: Select the Installation Directory

The installation of a new version of Teradata Parallel Transporter will prompt for the Teradata Parallel Transporter installation directory.

Here is a sample of the prompt:

Please specify the install directory [default:/opt/teradata/client/13.10/tbuild]:

Press the Enter key, to use the default installation directory.

Note: It is not recommended to use “/” or “/usr” as the installation directory.


The following are the installation directory restrictions for Teradata Parallel Transporter:

• The installation directory cannot be a relative directory path.



• The pipe character “|” cannot be in the name of the installation directory.

• The double quote character cannot be in the name of the installation directory.

• The equal character “=” cannot be in the name of the installation directory.

• The whitespace character cannot be in the name of the installation directory.

Step 3: Select the Logs Directory

In addition to the Teradata Parallel Transporter installation directory, the Teradata Parallel Transporter Infrastructure package prompts for the Teradata Parallel Transporter logs directory.


The logs directory contains Teradata Parallel Transporter job log files. The logs directory should be in a partition with a large free space. Please specify the logs directory [ default: /opt/teradata/client/13.10/tbuild/logs ]:

When prompted, press the Enter key, to use the default logs directory.


The following are the logs directory restrictions for Teradata Parallel Transporter:







• Enter 1 for shared memory

• Enter 2 for memory mapped file

Respond by pressing the Enter key or 1, to select shared memory as the IPC memory choice.

Or, respond by pressing 2, to select the memory mapped file as the IPC memory choice. The Teradata Parallel Transporter package prompts for the memory mapped file directory.







Respond by pressing the Enter key, to use the default memory mapped file directory.


The following are the memory mapped file directory restrictions for Teradata Parallel Transporter:



Note: During a reinstallation of the same Teradata Parallel Infrastructure version, the Teradata Parallel Infrastructure does not request the IPC memory choice. The reinstallation uses the existing IPC memory choice.

Note: The first Teradata Parallel Transporter package installed requests the installation directory. Subsequent Teradata Parallel Transporter packages of the same version do not request the installation directory, but use the same installation directory as the first package installed.


At the end of the Teradata Parallel Transporter Infrastructure installation, the Teradata Parallel Transporter Infrastructure installation updates the environment variables in the system /etc/profile and /etc/csh.login files.

The following table lists the Environment variables updated.

The updates to the environment variables are effective in the next logon only if the Teradata Parallel Transporter Infrastructure package has been installed. The updates to the environment variables allow users to run the installed version of Teradata Parallel Transporter.

If the Teradata Parallel Transporter API package has been installed, then the LIBPATH and NLSPATH environment variables must be updated manually.

The 32-bit files are in:

• $TWB_ROOT/lib




LIBPATH Add $TWB_ROOT/lib to the front of the LIBPATH environment variable.



Chapter 12: Configuring Teradata Tools and UtilitiesTask 7: Configure Teradata Parallel Transporter on HP-UX

• $TWB_ROOT/msg

The 64-bit files are in:

• $TWB_ROOT/lib64

• $TWB_ROOT/msg64

The environment variables can be updated on the command line, in the user's profile, or in the system profile.




Note: The updates to the environment variables must be used to run the installed version of Teradata Parallel Transporter.

Note: If the updates to the environment variables are not used, the installed version of Teradata Parallel Transporter will not run correctly.

Note: After installing Teradata Parallel Transporter and before running a Teradata Parallel Transporter job, the LANG environment variable must be set to “en_US”, or make the LC__FASTMSG environment variable must be set to “false”.

Task 7: Configure Teradata Parallel Transporter on HP-UX

Follow the procedures in this section to configure the Teradata Parallel Transporter on HP-UX.






• TWB_ROOT

• PATH

• SHLIB_PATH

• NLSPATH



Step 1: Change the twbcfg.ini File on HP-UX

After the Teradata Parallel Transporter Infrastructure package is installed, the configuration file, $TWB_ROOT/twbcfg.ini, can be edited to change the default directory for checkpoint and logs. The $TWB_ROOT environment variable contains the installation directory for Teradata Parallel Transporter.

To make a change in this configuration file, log on as the root user, and use an editor to modify the file.

A typical reasons for modifying the file is to change the logs directory to another directory with free disk space, if the log is full.

No kernel rebuild or reboot is required after making the change in the configuration file.

Step 2: Setup Configuration File Defaults on HP-UX




The following is an example of the Teradata Parallel Transporter configuration file defaults:


where: CheckpointDirectory refers to the directory that contains the checkpoint files for Teradata Parallel Transporter jobs


Step 3: Setup the Shared Memory Parameters on HP-UX


The following table lists the HP-UX shared memory parameters.




shmseg (minimum value of 10) The shmseg value determines the maximum number of shared memory segments per process.




If any of the above shared memory parameter is less than the minimum value, the Teradata Parallel Transporter Infrastructure installation recommends increasing the shared memory parameter to the minimum value using the kmtune command as the root user.

Use the following procedure to increase the shared memory parameter to the minimum value.

Procedure - Increasing the Shared Memory Parameter

Follow these steps to increase the shared memory parameter to the minimum value.

1 To check the shmseg parameter:

# /usr/sbin/kmtune -q shmseg

2 To increase the shmseg parameter to 10:

# /usr/sbin/kmtune -s shmseg=10

3 After the shared memory parameters are changed, rebuild the kernel using the mk_kernel command as the root user:

# /usr/sbin/mk_kernel

4 After rebuilding the kernel, save the current vmunix file:

# cp /stand/vmunix /stand/vmunix.prev

5 Then, move the new vmunix file into the /stand directory:

# mv /stand/build/vmunix_test /stand/vmunix

6 Lastly, reboot the machine:

# /usr/sbin/reboot

Note: If there is a change to the kernel value, the following kernel parameter requires a kernel rebuild and a reboot:

• shmmni

Note: If there is a change to the kernel value, the following kernel parameters do not require a kernel rebuild or a reboot:

• shmmax

• shmseg

Step 4: Setup the Semaphore Parameters on HP-UX

The Teradata Parallel Transporter Infrastructure installation process checks the values of the semaphore parameters and increases them if they are not setup properly:

The following table lists the HP-UX Semaphore parameters.

semmnu (minimum value of 2500 The semmnu value






If any of the semaphore parameters is less than the minimum value, the Teradata Parallel Transporter Infrastructure installation recommends increasing the semaphore parameter to the minimum value using the kmtune command. This requires a root login.

Use the following procedure to increase the semaphore parameter to the minimum value.

Procedure - Increasing the Semaphore Parameter to the Minimum Value

Follow these steps to increase the semaphore parameter to the minimum value.

1 To increase the semmap parameter to 1000:

# /usr/sbin/kmtune -s semmap=1000

2 After the semaphore parameters are changed, rebuild the kernel using the mk_kernel command as the root user:




4 Move the new vmunix file into the /stand directory:


5 Reboot the machine:

# /usr/sbin/reboot

Note: If there is a change to the kernel value, the following kernel parameters require a kernel rebuild and reboot: semmap, semmni, semmns and semmnu.

Step 5: Setup the Environment Variables on HP-UX




semmni (minimum value of 1000) The semmni value

semmns (minimum value of 1000) The semmns value

semmap (minimum value of 1000) The semmap value

semmnu (minimum value of 2500) The semmnu value




If the Teradata Parallel Transporter API package was installed, then the SHLIB_PATH and NLSPATH environment variables must be updated manually.

• The 32-bit files are in $TWB_ROOT/lib and $TWB_ROOT/msg.

• The 64-bit files are in $TWB_ROOT/lib64 and $TWB_ROOT/msg64.

Environment variables are updated on the command line, in the user's profile, or in the system profile.



• If the environment variables are updated in the system profile then the updates will be effective every time any user logs in.

Note: Use the updates to the environment variables to run the installed version of Teradata Parallel Transporter properly.

Note: If updates to the environment variables are not used, the installed version of Teradata Parallel Transporter will not run correctly.

Use the following commands to setup the environment variables:






# PATH=$TWB_ROOT/bin:$PATH




SHLIB_PATH Add $TWB_ROOT/lib to the front of the SHLIB_PATH environment variable.




# export PATH

• To update the SHLIB_PATH environment variable:

# SHLIB_PATH=$TWB_ROOT/lib:$SHLIB_PATH# export SHLIB_PATH



C-shell users



where: <Teradata Parallel Transporter installation directory> is the Teradata Parallel Transporter installation directory. Run the /usr/bin/twbpkgrm tool to find the Teradata Parallel Transporter installation directory.




# setenv SHLIB_PATH $TWB_ROOT"/lib:$SHLIB_PATH"



Step 6: Switch the IPC Memory Choice to Shared Memory on HP-UX

Use the following procedure to switch the IPC Memory Choice to Shared Memory.





cd <install dir>


# rm -rf mmap

After following the above steps, Teradata Parallel Transporter will use shared memory as the IPC memory choice.


Step 7: Switch the IPC Memory Choice to Memory Mapped File

Use the following procedure to switch the IPC Memory Choice to Memory Mapped File.


Chapter 12: Configuring Teradata Tools and UtilitiesTask 8: Configure Teradata Parallel Transporter on HP-UX Itanium





cd <install dir>

3 Create the “mmap” directory with “777” permission using these commands:


Teradata Parallel Transporter uses memory mapped file as the IPC memory choice. The change does not require a kernel rebuild or a reboot.

Task 8: Configure Teradata Parallel Transporter on HP-UX Itanium

Follow the procedures in this section to configure the Teradata Parallel Transporter on HP-UX Itanium.






• TWB_ROOT

• PATH

• SHLIB_PATH

• NLSPATH

Step 1: Change the twbcfg.ini File on HP-UX Itanium

After the Teradata Parallel Transporter Infrastructure package is installed, the configuration file, $TWB_ROOT/twbcfg.ini, can be edited to change the default directory for checkpoint and logs. The $TWB_ROOT environment variable contains the installation directory for Teradata Parallel Transporter.

To make a change in this configuration file, log on as the root user, and use an editor to modify the file.

A typical reasons for modifying the file is to change the logs directory to another directory with free disk space, if the log is full.



No kernel rebuild or reboot is required after making the change in the configuration file.

Step 2: Setup Configuration File Defaults on HP-UX Itanium




The following is an example of the Teradata Parallel Transporter configuration file defaults:


where: CheckpointDirectory refers to the directory that contains the checkpoint files for Teradata Parallel Transporter jobs


Step 3: Setup the Shared Memory Parameters on HP-UX Itanium


The following table lists the HP-UX Itanium shared memory parameters.


If any of the above shared memory parameter is less than the minimum value, the Teradata Parallel Transporter Infrastructure installation recommends increasing the shared memory parameter to the minimum value using the kmtune command as the root user.

Use the following procedure to increase the shared memory parameter to the minimum value.




shmseg (minimum value of 10) The shmseg value determines the maximum number of shared memory segments per process.

semmnu (minimum value of 2500 The semmnu value



Procedure - Increasing the Shared Memory Parameter

Follow these steps to increase the shared memory parameter to the minimum value.

1 To check the shmseg parameter:

# /usr/sbin/kmtune -q shmseg

2 To increase the shmseg parameter to 10:

# /usr/sbin/kmtune -s shmseg=10

3 After the shared memory parameters are changed, rebuild the kernel using the mk_kernel command as the root user:




5 Then, move the new vmunix file into the /stand directory:


6 Lastly, reboot the machine:

# /usr/sbin/reboot

Note: If there is a change to the kernel value, the following kernel parameter requires a kernel rebuild and a reboot:

• shmmni

Note: If there is a change to the kernel value, the following kernel parameters do not require a kernel rebuild or a reboot:

• shmmax

• shmseg

Step 4: Setup the Semaphore Parameters on HP-UX Itanium

The Teradata Parallel Transporter Infrastructure installation process checks the values of the semaphore parameters and increases them if they are not setup properly:

The following table lists the HP-UX Itanium Semaphore parameters.



semmni (minimum value of 1000) The semmni value

semmns (minimum value of 1000) The semmns value

semmap (minimum value of 1000) The semmap value

semmnu (minimum value of 2500) The semmnu value




If any of the semaphore parameters is less than the minimum value, the Teradata Parallel Transporter Infrastructure installation recommends increasing the semaphore parameter to the minimum value using the kmtune command. This requires a root login.

Use the following procedure to increase the semaphore parameter to the minimum value.

Procedure - Increasing the Semaphore Parameter to the Minimum Value

Follow these steps to increase the semaphore parameter to the minimum value.

1 To increase the semmap parameter to 1000:

# /usr/sbin/kmtune -s semmap=1000

2 After the semaphore parameters are changed, rebuild the kernel using the mk_kernel command as the root user:




4 Move the new vmunix file into the /stand directory:


5 Reboot the machine:

# /usr/sbin/reboot

Note: If there is a change to the kernel value, the following kernel parameters require a kernel rebuild and reboot: semmap, semmni, semmns and semmnu.

Step 5: Setup the Environment Variables on HP-UX Itanium






SHLIB_PATH Add $TWB_ROOT/lib to the front of the SHLIB_PATH environment variable.





If the Teradata Parallel Transporter API package was installed, then the SHLIB_PATH and NLSPATH environment variables must be updated manually.

• The 32-bit files are in $TWB_ROOT/lib and $TWB_ROOT/msg.

• The 64-bit files are in $TWB_ROOT/lib64 and $TWB_ROOT/msg64.




• If the environment variables are updated in the system profile then the updates will be effective every time any user logs in.

Note: Use the updates to the environment variables to run the installed version of Teradata Parallel Transporter properly.

Note: If updates to the environment variables are not used, the installed version of Teradata Parallel Transporter will not run correctly.

Use the following commands to setup the environment variables:








# SHLIB_PATH=$TWB_ROOT/lib:$SHLIB_PATH# export SHLIB_PATH



C-shell users





where: <Teradata Parallel Transporter installation directory> is the Teradata Parallel Transporter installation directory. Run the /usr/bin/twbpkgrm tool to find the Teradata Parallel Transporter installation directory.




# setenv SHLIB_PATH $TWB_ROOT"/lib:$SHLIB_PATH"



Step 6: Switch the IPC Memory Choice to Shared Memory on HP-UX Itanium

Use the following procedure to switch the IPC Memory Choice to Shared Memory.





cd <install dir>


# rm -rf mmap

After following the above steps, Teradata Parallel Transporter will use shared memory as the IPC memory choice.


Step 7: Switch the IPC Memory Choice to Memory Mapped File

Use the following procedure to switch the IPC Memory Choice to Memory Mapped File.





cd <install dir>

3 Create the “mmap” directory with “777” permission using these commands:


Teradata Parallel Transporter uses memory mapped file as the IPC memory choice. The change does not require a kernel rebuild or a reboot.


Chapter 12: Configuring Teradata Tools and UtilitiesTask 9: Configure Teradata Parallel Transporter on Sun Solaris SPARC

Task 9: Configure Teradata Parallel Transporter on Sun Solaris SPARC


The following table lists the default and alternate directories where the software is installed.

To choose an alternate directory, first, log on as root. After selecting the packages to install, the installation program prompts for the default directory. Browse the system and select an alternate directory.

The first Teradata Parallel Transporter package requests the installation directory. Subsequent Teradata Parallel Transporter packages of the same version do not ask for the installation directory, but uses the same installation directory as the first package.

Starting with Teradata Parallel Transporter version 08.01.00.00, installing a Teradata Parallel Transporter emergency fix (efix) package overwrites the installed Teradata Parallel Transporter package.


This section contains instructions for installing the Teradata Parallel Transporter on Sun Solaris SPARC.

Item Default Directory

ODBC driver files /opt/teradata/client/ODBC_32 and/or/opt/teradata/client/ODBC_64

Executable files /opt/teradata/client/<version>/bin

Library files /opt/teradata/client/<version>/lib

Includes files /opt/teradata/client/<version>/include

Sample files /opt/teradata/client/<version>/sample

64-bit Library files /opt/teradata/client/<version>/lib64

64-bit Executable files /opt/teradata/client/<version>/bin64

Teradata Parallel Transporter /opt/teradata/client/<version>/tbuild


For example, the default install directory for Teradata Parallel Transporter version 13.10.00.00 is /opt/teradata/client/13.10/tbuild.



Step 2: Select the Default Installation Directory

The install of a new version of Teradata Parallel Transporter prompts for the Teradata Parallel Transporter installation directory.




The restrictions for the Teradata Parallel Transporter installation directory include:

• Do not use “/” or “/usr” as the installation directory






Step 3: Select the Logs Directory



Press Enter to use the default logs directory.







Enter 1 for shared memoryEnter 2 for memory mapped file

Press Enter or 1, to make the IPC memory choice shared memory.



Press 2, to make the IPC memory choice memory mapped file. The Teradata Parallel Transporter package prompts for the memory mapped file directory.




Press Enter to use the default memory mapped file directory.


The following are the restrictions on the memory mapped file directory for Teradata Parallel Transporter:



Note: During a reinstallation of the same Teradata Parallel Infrastructure version, the Teradata Parallel Infrastructure reinstallation does request for the IPC memory choice. The reinstallation reuses the existing IPC memory choice.

Note: The first Teradata Parallel Transporter package prompts for the installation directory. Subsequent Teradata Parallel Transporter packages of the same version do not request the installation directory, but uses the same installation directory as the first Teradata Tools and Utilities package installed.

Step 5: Select the System Kernel Values

The Teradata Parallel Transporter Infrastructure package checks for the system kernel values.

The following table lists the kernel values.


SEMMNI 1000 Maximum number of semaphore sets in entire system.

SEMMNS 1000 Maximum number of semaphores in entire system.

SEMMNU 2500 Maximum number of processes that can have undo operations pending on semaphores.

SHMMAX 4194304 Maximum size of a shared memory segment.

SHMMNI 200 Maximum number of shared memory segments in entire system.



Note: The Teradata Parallel Transporter Infrastructure installation does not support formula value. If the kernel value is a formula, then the Teradata Parallel Transporter Infrastructure installation displays a warning message.

If the Sun Solaris SPARC system does not meet the required minimum value, the Teradata Parallel Transporter Infrastructure installation prompts to increase the value to the minimum required value.

Warning: The current value of 1048675 for the kernel parameter (SHMMAX) is less than the minimum required value of 4194304. SHMMAX refers to the maximum size of a shared memory segment.

Note: This install recommends increasing the value to the minimum required value.

Note: A kernel rebuild is not required to make the kernel parameter change(s) effective.Note: A reboot is required to make the kernel parameter change(s) effective. The reboot can be done after this installation but before running Teradata Parallel Transporter jobs.

Do you want to increase the value to the minimum required value for the above kernel parameter(s)?

Please enter y for yes or n for no [y,n,? (default : y)]

Enter N to keep the current kernel value.

Enter Y, or press Enter, to change the kernel value. A reboot is required to make the kernel parameter change(s) effective.

Log on as root user to reboot the system.

The reboot can be done after all the installations, but must be done before running a Teradata Parallel Transporter job.

The following reboot command reboots the system in 60 seconds:

# cd; /usr/sbin/shutdown -y -g60 -i6


At the end of the Teradata Parallel Transporter Infrastructure installation, the Teradata Parallel Transporter Infrastructure installation updates the environment variables in the system /etc/profile and /etc/.login files.

The following table lists the environment variables.

SHMSEG 10 Maximum number of shared memory segments per process.

Note: Checked only on Sun Solaris 8.



Chapter 12: Configuring Teradata Tools and UtilitiesTask 10: Configuring Teradata Parallel Transporter on Sun Solaris Opteron

Updates to the environment variables are effective in the next login only if the Teradata Parallel Transporter Infrastructure package is installed. Updates to the environment variables allow users to run the installed version of Teradata Parallel Transporter.

If the Teradata Parallel Transporter API package is installed, then the LD_LIBRARY_PATH and NLSPATH environment variables must be updated. The 32-bit files are in $TWB_ROOT/lib and $TWB_ROOT/msg. The 64-bit files will be in $TWB_ROOT/lib64 and $TWB_ROOT/msg64.





Note: Users must use the updates to the environment variables to run the installed version of Teradata Parallel Transporter properly.

Note: If users do not use the updates to the environment variables, the installed version of

Teradata Parallel Transporter will not run properly.

Task 10: Configuring Teradata Parallel Transporter on Sun Solaris Opteron


The following table lists the default directories where the software is installed.








To choose an alternate directory, first log on as rot user. After selecting the packages to install, the installation program prompts to select the default directory, alternatively browse the system and select an alternate directory.

The first Teradata Parallel Transporter package requests the installation directory. Subsequent Teradata Parallel Transporter packages of the same version do not request the installation directory, but use the same installation directory as the first installed package.

Starting with Teradata Parallel Transporter version 08.01.00.00, an installation of a Teradata Parallel Transporter emergency fix (efix) package overwrites the installed Teradata Parallel Transporter package.


Step 2: Select Installation Directory

The installation of a new version of Teradata Parallel Transporter prompts for the Teradata Parallel Transporter installation directory.



Item Default Directory

ODBC driver files /opt/teradata/client/ODBC_32 and/or /opt/teradata/client/ODBC_64

Executable files /opt/teradata/client/<version>/bin

Library files /opt/teradata/client/<version>/lib

Includes files /opt/teradata/client/<version>/include

Sample files /opt/teradata/client/<version>/sample

Installation /opt/teradata/client/<version>/product

64-bit Library files /opt/teradata/client/<version>/lib64

64-bit Executable files /opt/teradata/client/<version>/bin64

Teradata Parallel Transporter /opt/teradata/client/<version>/tbuild


For example, the default install directory for Teradata Parallel Transporter version 13.10.00.00 is /opt/teradata/client/13.10/tbuild.




The following are the restrictions for the Teradata Parallel Transporter installation directory:

• Do not use “/” or “/usr” as the installation directory.






Step 3: Select Logs Directory








Step 4: Select Interprocess Communication (IPC) Memory Choice


Teradata Parallel Transporter Infrastructure uses shared memory or memory mapped file for interprocess communication (IPC).Shared memory utilizes system shared memory for IPC.Memory mapped file utilizes temporary disk storage for IPC.Please select the IPC memory mechanism [ default: shared memory ]:Enter 1 for shared memoryEnter 2 for memory mapped file

Press Enter or 1, the IPC memory choice will be shared memory.

Press 2, to choose the IPC memory choice. IPC memory is a memory mapped file and the Teradata Parallel Transporter package prompts for the memory mapped file directory.






Press Enter to use the default memory mapped file directory.


The following are the restrictions for the Teradata Parallel Transporter memory mapped file directory:

• The memory mapped file directory cannot be a relative directory path.

• The whitespace character cannot be in the name of the memory mapped file directory.

Note: During reinstallation of the same Teradata Parallel Infrastructure version, the Teradata Parallel Infrastructure does not request the IPC memory choice. The reinstallation uses the existing IPC memory choice.

Note: The first Teradata Parallel Transporter package requests the installation directory. Subsequent Teradata Parallel Transporter packages of the same version not request the installation directory, but instead use the same installation directory as the first installation package.

Step 5: Select System Kernel Values

The Teradata Parallel Transporter Infrastructure package checks for system kernel values. The following table lists the kernel values.

Note: The Teradata Parallel Transporter Infrastructure installation does not support formula value. If the kernel value is a formula, then the Teradata Parallel Transporter Infrastructure installation will display a warning message.

If the system does not meet the required minimum value, the Teradata Parallel Transporter Infrastructure installation prompts to increase the value to the minimum required value.


SEMMNI 1000 Maximum number of semaphore sets in entire system.

SEMMNS 1000 Maximum number of semaphores in entire system.

SEMMNU 2500 Maximum number of processes that can have undo operations pending on semaphores.

SHMMAX 4194304 Maximum size of a shared memory segment.

SHMMNI 200 Maximum number of shared memory segments in entire system.

SHMSEG 10 Maximum number of shared memory segments per process.

Note: Checked only on Sun Solaris 8.



Warning: The current value of 1048675 for the kernel parameter (SHMMAX) is less than the minimum required value of 4194304. SHMMAX refers to the maximum size of a shared memory segment.

Note: This install recommends increasing the value to the minimum required value.

Note: A kernel rebuild is not required to make the kernel parameter change(s) effective.

Note: A reboot is required to make the kernel parameter change(s) effective. The reboot can be done after this installation but before running Teradata Parallel Transporter jobs.Do you want to increase the value to the minimum required value for the above kernel parameter(s)?

Please enter y for yes or n for no [y,n,? (default : y)]

If N is entered, the Teradata Parallel Transporter Infrastructure package does not change the kernel value.

If Y is entered, or if Enter is pressed, the Teradata Parallel Transporter Infrastructure package changes the kernel value. A reboot is required to make the kernel parameter change(s) effective.

To reboot the system log on as the root user.

The reboot should be done after all the installations are complete but before running a Teradata Parallel Transporter job.

The following reboot command reboots the system in 60 seconds:

# cd; /usr/sbin/shutdown -y -g60 -i6


At the end of the Teradata Parallel Transporter Infrastructure installation, the Teradata Parallel Transporter Infrastructure installation updates the environment variables in the system /etc/profile and /etc/.login files. The following table lists the environment variables updated.








Updates to the environment variables are effective at the next login only if the Teradata Parallel Transporter Infrastructure package is installed. Updates to the environment variables allow the installed version of Teradata Parallel Transporter to run properly.

If the Teradata Parallel Transporter API package is installed, then the LD_LIBRARY_PATH and NLSPATH environment variables must be updated. The 32-bit files are in $TWB_ROOT/lib and $TWB_ROOT/msg. The 64-bit files will be in $TWB_ROOT/lib64 and $TWB_ROOT/msg64.


If the environment variables are updated on the command line, then the updates are effective only for the current session. If the environment variables are updated in the user's profile, then the updates are only effective every time that particular user logs in. If the environment variables are updated in the system profile, then the updates are effective every time any user logs in.

Note: Updates to the environment variables are not required run the installed version of Teradata Parallel Transporter properly.

Note: Updates to the environment variables are not done, the installed version of Teradata

Parallel Transporter does not run properly.


CHAPTER 13

Verifying the InstallationUsing BTEQ

This section describes how to verify the installation using BTEQ.

Task 1: Verify the Installation Using BTEQ

Using Basic Teradata Query (BTEQ) is the simplest way to verify that Teradata Tools and Utilities has been installed properly. BTEQ files were installed during the installation of product software on the system. The following sections describe these steps in detail. Refer to Basic Teradata Query Reference for information on how to use BTEQ.

Procedure - Verifying Teradata Tools and Utilities Installation

Follow these steps to verify Teradata Tools and Utilities installation.

1 Add the directory where BTEQ resides to the search path. Then change directories to that directory.

2 Start BTEQ by entering:

bteq


Teradata BTEQ 13.10.00.00 for UNIX5.Copyright 1984-2010, Teradata Corporation. ALL RIGHTS RESERVED.Enter your logon or BTEQ command:

3 Log on to the Teradata Database. See “Step 1: Log onto the Teradata Database”.

4 Submit a sample query. See “Step 2: Submit a Sample Teradata SQL Query”.

Step 1: Log onto the Teradata Database

Complete the steps below to log onto the Teradata Database. Requirements include a user ID and password for the Teradata Database.

Note: See Task 1: Make the Database Connection for complete information about logging onto Teradata.

Procedure - Logging onto the Teradata Database

Follow these steps to log onto the Teradata Database.


Chapter 13: Verifying the Installation Using BTEQTask 1: Verify the Installation Using BTEQ

1 Enter the BTEQ logon command with a logon ID. Include the dbcpath if the Teradata Database dbcpath is not the default i_dbcpath specified in clispb.dat.

The syntax of the .logon command is:

.logon dbcpath/username

2 When prompted, enter the password. For example, if the Teradata Database has a dbcpath of Finance, the username is fml and the password is fml, enter:

.logon Finance/fmlPassword: fml

If the logon is successful, the following appears:

*** Logon successfully completed.*** Transaction Semantics are BTET.*** Character Set Name is 'ASCII'.

*** Total elapsed time was 1 second.

BTEQ -- Enter your DBC/SQL request or BTEQ command:

Step 2: Submit a Sample Teradata SQL Query

After successfully logging onto the Teradata Database, try the following sample query to display the time of day.

Procedure - Submitting a Sample Teradata SQL Query

Follow these steps to submit a sample Teradata SQL query.

1 At the prompt, type:

SELECT time;


BTEQ select time output:*** Query completed. One row found. One column returned. *** Total elapsed time was 1 second.

Time--------

11:09:11

Step 3: Exit BTEQ

After verifying the time returned by the SQL query, log off the Teradata Database.

Procedure - Logging off the Teradata Database

Follow these steps to log off the Teradata Database.

1 To log off the Teradata Database and exit BTEQ, enter:

.quit

The host prompt appears.


CHAPTER 14

Verifying InstallationUsing CLI Sample Program

This section describes how to verify the installation using the CLI Sample Program.

Task 1: Run CLI Sample to Verify the Installation

Another way to verify that Teradata Tools and Utilities software installed properly is to run the sample CLI application called clisamp. The program and its makefile were installed during installation of Teradata Tools and Utilities.

Step 1: Run clisamp

Procedure - Running clisamp

Follow these steps to verify that Teradata Tools and Utilities software was installed correctly.

1 Modify the makefile makesamp.3000 with the correct directory paths to the include files.

2 Execute the makefile to create the executable module clisamp:

# make -f makesamp.3000

3 Change the mode of the executable to run by entering the following command:

# chmod +x clisamp

4 Run the sample program using one of the following commands:

To run the sample program using the default logon information (dbc/systemfe,service) enter:

# clisamp

To show help for the sample program, use the -h option, enter:

# clisamp -h

To run the sample program, using a user provided input string TDPID= slugger, user=dbc, password=dbc, enter:

# clisamp slugger/dbc,dbc

The program logs on to the default dbccop1 (no user input supplied) specified in the /etc/hosts file and run a simple query SELECT * from dbc.sessioninfo;" and writes the output to that file: clisamp.dat. A display similar to the following appears:


Chapter 14: Verifying Installation Using CLI Sample ProgramTask 1: Run CLI Sample to Verify the Installation

CLIv2 version is 13.10.00.24MTDP version is 13.10.00.20MOSIOS version is 13.10.00.05MOSIDEP version is 13.10.00.05OSERR version is 13.10.00.01

Logging on to --->dbc/systemfe,servicewriting out to--> CLISAMP.DATsubmitting -->select* from dbc.sessioninfo;writintg out to --> CLISAMP.DATLogging off.


CHAPTER 15

Checking Files and Folders on Linux

This section contains tables which list the directories and filenames of products to enable verification that Teradata Tools and Utilities software has been installed properly on Linux operating systems.

Task 1: Verifying Installation of Individual Products

Procedure - Verifying Installation of Individual Products

Follow these steps to verify the installation of individual Teradata Tools and Utilities products and their dependencies.

1 Check that the directories specified in the tables below have been installed.

2 Check that the files specified in the tables below have been installed.

• Basic Teradata Query

• Named Pipes Access Module (npaxsmod)


• Shared Common Components for Internationalization for Teradata

• Teradata Archive/Recovery Utility

• Teradata C Preprocessor2



• Teradata FastExport

• Teradata FastLoad

• Teradata Generic Security Services


• Teradata MultiLoad

• Teradata TPump

• Teradata Parallel Transporter API

• Teradata Parallel Transporter Export Operator

• Teradata Parallel Transporter Infrastructure

• Teradata Parallel Transporter Load Operator


Chapter 15: Checking Files and Folders on LinuxTask 1: Verifying Installation of Individual Products

• Teradata Parallel Transporter Stream Operator

• Teradata Parallel Transporter Update Operator

• Teradata WebSphere MQ Access Module

Basic Teradata Query

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for a file that has been installed in the directory (default) /opt/teradata/client/usr/<version>/bin.

The following table lists the files and the directories installed for each operating system supported by Basic Teradata Query.

Named Pipes Access Module (npaxsmod)

An asterisk (*) after a name in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/lib directories.

The following table lists the files and the directories installed for each operating system supported by Named Pipes Access Module.

ODBC Driver for Teradata

The default directory for the ODBC Driver for Teradata for all platforms is:

/opt/teradata/client/ODBC_32

and/or

/opt/teradata/client/ODBC_64


Directory Red Hat Linux SUSE Linux Linux for s390x

/usr/bin bteq* bteq* bteq*

/usr/include btnfyext.h* btnfyext.h* btnfyext.h*

/opt/teradata/client/<version>/bin bteq bteq bteq

/opt/teradata/client/<version>/sample btnfyext.c

mkbtnfyext.linux

btnfyext.c

mkbtnfyext.linux

btnfyext.c

mkbtnfyext.suselinux-390.32

/opt/teradata/client/<version>/include btnfyext.h btnfyext.h btnfyext.h

Directory Red HatLinux SUSE Linux Linux for s390x

/usr/lib np_axsmod.so* np_axsmod.so* np_axsmod.so*

/opt/teradata/client/<version>/lib np_axsmod.so np_axsmod.so np_axsmod.so



The following table lists the files and the directories installed for each operating system supported by the ODBC Driver for Teradata.


/usr/lib libivicu24.so* libivicu24.so* libivicu24.so*

/user/lib libtdsso.so* libtdsso.so* libtdsso.so*

/usr/lib libodbcinst.so* libodbcinst.so* libodbcinst.so*

/usr/lib libtdparse.so* libtdparse.so* libtdparse.so*

installation directory README README README

installation directory odbc.ini odbc.ini odbc.ini

installation directory odbcinst.ini odbcinst.ini odbcinst.ini

/lib tdata.so tdata.so tdata.so

/bin tdxwinapp tdxwinapp tdxwinapp

/include odbcinst.h odbcinst.h odbcinst.h

/include sql.h sql.h sql.h

/include sqlext.h sqlext.h sqlext.h

/include sqltypes.h sqltypes.h sqltypes.h

/include sqlucode.h sqlucode.h sqlucode.h

/include sqlunx.h sqlunx.h sqlunx.h

/include tdsql.h tdsql.h tdsql.h

/lib libodbc.so libodbc.so libodbc.so

/<install dir>/lib libivicu24.so libddicu24.so libddicu24.so

/<install dir>/lib libodbcinst.so libodbcinst.so libodbcinst.so

/<install dir>/lib libtdparse.so libtdparse.so libtdparse.so

/<install dir>/lib odbccurs.so odbccurs.so odbccurs.so

/<install dir>/lib odbctrac.so odbctrac.so odbctrac.so

/<install dir>/lib tdconndlg.so tdconndlg.so tdconndlg.so

/<install dir>/lib vscnctdlg.so vscnctdlg.so vscnctdlg.so

/<install dir>/lib tdata.so tdata.so tdata.so

/opt/teradata/client/<version>/odbc_32/help/man/man5

or

/opt/teradata/client/<version>/odbc_64/msg/man/man5

tdata.man tdata.man tdata.man



Shared Common Components for Internationalization for Teradata

The following table lists the files and the directories installed for each operating system supported by Shared Common Components for Internationalization for Teradata.

/opt/teradata/client/ODBC_32/locale/en_US/LC_MESSAGES

or

/opt/teradata/client/ODBC_64/locale/en_US/LC_MESSAGES

odbc.m odbc.m odbc.m

/<install dir>/samples/C Makefile Makefile Makefile

/<install dir>/samples/C adhoc adhoc adhoc

/<install dir>/samples/C adhoc.c adhoc.c adhoc.c

/<install dir>/samples/C common.includes common.includes common.includes

/<install dir>/samples/C error.c error.c error.c

/<install dir>/samples/C++ Makefile Makefile Makefile

/<install dir>/samples/C++ adhoc adhoc adhoc

/<install dir>/samples/C++ adhoc.cpp adhoc.cpp adhoc.cpp

/<install dir>/samples/C++ common.includes common.includes common.includes

/<install dir>/samples/C++ error.cpp error.cpp error.cpp

/opt/teradata/client/<version>/odbc_32/msg

or


tdodbc.cat tdodbc.cat tdodbc.cat



/usr/lib libicudatatd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

libicudatatd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

libicudatatd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

/usr/lib libicui18ntd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libicui18ntd.so.36.0

libicui18ntd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libicui18ntd.so.36.0




/usr/lib libicuuctd.so.36-> /opt/teradata/client/<version>/tdicu/lib/libicuuctd.so.36.0

libicuuctd.so.36-> /opt/teradata/client/<version>/tdicu/lib/libicuuctd.so.36.0

libicuuctd.so.36-> /opt/teradata/client/<version>/tdicu/lib/libicuuctd.so.36.0

/usr/lib libicuiotd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libicuiotd.so.36.0

libicuiotd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libicuiotd.so.36.0


/usr/lib libiculxtd36.so -> /opt/teradata/client/<version>/tdicu/lib/libiculxtd.so.36.0

libiculxtd36.so -> /opt/teradata/client/<version>/tdicu/lib/libiculxtd.so.36.0

libiculxtd36.so -> /opt/teradata/client/<version>/tdicu/lib/libiculxtd.so.36.0

/usr/lib libiculetd36.so -> /opt/teradata/client/<version>/tdicu/lib/libiculetd.so.36.0

libiculetd36.so -> /opt/teradata/client/<version>/tdicu/lib/libiculetd.so.36.0

libiculetd36.so -> /opt/teradata/client/<version>/tdicu/lib/libiculetd.so.36.0

/usr/lib libicui18ntd.so -> /opt/teradata/client/<version>/tdicu/lib/libicui18ntd.so.36.0

libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

/usr/lib libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib/libicuintd.so.36.0

libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib/libicuintd.so.36.0

libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib/libicuintd.so.36.0

/usr/lib libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib/libicuuctd.so.36.0

libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib/libicuuctd.so.36.0


/usr/lib libicuiotd.so -> /opt/teradata/client/<version>/tdicu/lib/libicuiotd.so.36.0

libicuiotd.so -> /opt/teradata/client/<version>/tdicu/lib/libicuiotd.so.36.0


/usr/lib libiculxtd.so -> /opt/teradata/client/<version>/tdicu/lib/libiculxtd.so.36.0

libiculxtd.so -> /opt/teradata/client/<version>/tdicu/lib/libiculxtd.so.36.0


/usr/lib libiculetd.so -> /opt/teradata/client/<version>/tdicu/lib/libiculetd.so.36.0

libiculetd.so -> /opt/teradata/client/<version>/tdicu/lib/libiculetd.so.36.0


/opt/teradata/client/<version>/tdicu/lib

libicudatatd.so.36 -> libicudatatd.so.36.0




libicui18ntd.so.36-> libicui18ntd.so.36.0







libicuuctd.so.36 -> libicuuctd.so.36.0




libicuiotd.so.36 -> libicuiotd.so.36.0




libicudatatd.so.36.0 libicudatatd.so.36.0 libicudatatd.so.36.0


libicui18ntd.so.36.0 libicui18ntd.so.36.0 libicui18ntd.so.36.0


libicuuctd.so.36.0 libicuuctd.so.36.0 libicuuctd.so.36.0


libicuiotd.so.36.0 libicuiotd.so.36.0 libicuiotd.so.36.0


libiculetd.so.36.0 libiculetd.so.36.0 libiculetd.so.36.0


libiculxtd.so.36.0 libiculxtd.so.36.0 libiculxtd.so.36.0


libiculetd.so.36 -> libiculetd.so.36.0




libiculxtd.so.36 -> libiculxtd.so.36.0




libicudatatd.so -> libicudatatd.so.36.0




libicui18ntd.so -> libicui18ntd.so.36.0




libicuiotd.so -> libicuiotd.so.36.0 libicuiotd.so -> libicuiotd.so.36.0

libicuiotd.so -> libicuiotd.so.36.0


libiculetd.so -> libiculetd.so.36.0




libiculxtd.so -> libiculxtd.so.36.0




libicuuctd.so -> libicuuctd.so.36.0 libicuuctd.so -> libicuuctd.so.36.0

libicuuctd.so -> libicuuctd.so.36.0

/usr/lib64 n/a libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

/usr/lib64 n/a libicui18ntd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0

libicui18ntd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0




/usr/lib64 n/a libicuiotd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

libicuiotd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

/usr/lib64 n/a libiculetd.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0

libiculetd.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0

/usr/lib64 n/a libiculxtd.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

libiculxtd.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

/usr/lib64 n/a libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd.so.36.0

libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd.so.36.0

/usr/lib64 n/a libicudatatd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

libicudatatd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

/usr/lib64 n/a libicui18ntd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0

libicui18ntd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0

/usr/lib64 n/a libicuiotd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

libicuiotd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

/usr/lib64 n/a libiculetd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0

libiculetd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0

/usr/lib64 n/a libiculxtd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

libiculxtd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

/usr/lib64 libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd36.0.so

libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd36.0.so

libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd36.0.so

/usr/lib64 libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd36.0.so

libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd36.0.so

libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd36.0.so

/usr/lib64 libiculxtd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd36.0.so

libiculxtd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd36.0.so

libiculxtd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd36.0.so




/usr/lib64 libiculetd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd36.0.so

libiculetd36.so -> /opt/teradata/client/<version>/tdicu/lib_64/libiculetd36.0.so

libiculetd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd36.0.so

/usr/lib64 libicuiotd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd36.0.so

libicuiotd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd36.0.so

libicuiotd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd36.0.so

/usr/lib64 libicui18ntd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd36.0.so

libicui18ntd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd36.0.so

libicui18ntd36.so -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd36.0.so

/opt/teradata/client/<version>/tdicu/lib64

n/a libicudatatd.so.36 -> libicudatatd.so.36.0



n/a libicui18ntd.so.36-> libicui18ntd.so.36.0



n/a libicuuctd.so.36 -> libicuuctd.so.36.0



n/a libicuiotd.so.36 -> libicuiotd.so.36.0



n/a libiculetd.so.36 -> libiculetd.so.36.0



n/a libiculxtd.so.36 -> libiculxtd.so.36.0



n/a libicudatatd.so -> libicudatatd.so.36.0



n/a libicui18ntd.so -> libicui18ntd.so.36.0



n/a libicuiotd.so -> libicuiotd.so.36.0



n/a libicuuctd.so -> libicuuctd.so.36.0



n/a libiculetd.so->libiculetd.so.36.0

libiculetd.so->libiculetd.so.36.0


n/a libiculxtd.so->libiculxtd.so.36.0

libiculxtd.so->libiculxtd.so.36.0


n/a libicudatatd.so.36.0 libicudatatd.so.36.0


n/a libicui18ntd.so.36.0 libicui18ntd.so.36.0




Teradata Archive/Recovery Utility

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/bin and the /opt/teradata/client/<version>/bin64 directories.

The Teradata Archive/Recovery Utility .rpm install package will now install both 32-bit and 64-bit versions of Teradata Archive/Recovery Utility on a 64-bit SUSE Linux machine at the same time. Even though the 64-bit version of Teradata Archive/Recovery Utility will be installed on a 64-bit Linux machine, the 32-bit version of Teradata Archive/Recovery Utility will still be the default version.

To use the 64-bit version of Teradata Archive/Recovery Utility, you will have to explicitly identify that version of Teradata Archive/Recovery Utility by either accessing it through the softlink at /usr/bin64/arcmain or by specifying the full path to the 64-bit executable, for example: /opt/teradata/client/<version>/bin64/arcmain.

The following table lists Teradata Archive/Recovery Utility (ARC) installed for 32-bit and 64-bit platforms.

Teradata C Preprocessor2

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/bin, /opt/teradata/client/<version>/bin64, /opt/teradata/client/<version>/lib and the /opt/teradata/client/<version>/lib64 directories.

The following table lists the files and the directories installed on Linux operating systems supported by Teradata C Preprocessor.


n/a libicuuctd.so.36.0 libicuuctd.so.36.0


n/a libicuiotd.so.36.0 libicuiotd.so.36.0


n/a libiculetd.so.36.0 libiculetd.so.36.0


n/a libiculxtd.so.36.0 libiculxtd.so.36.0



/usr/bin n/a arcmain.exe* n/a

/usr/bin64 n/a arcmain.exe* n/a

/opt/teradata/client/<version>/bin n/a arcmain.exe n/a

/opt/teradata/client/<version>/bin64 n/a arcmain.exe n/a



Teradata Call-Level Interface version 2

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/include and the /opt/teradata/client/<version>/lib directories.

The following table lists the files and the directories installed for each operating system supported by Teradata Call-Level Interface version 2.


/usr/bin ppcmain* n/a ppcmain*

/usr/lib lippruntim.so* n/a lippruntim.so*

/usr/bin64 n/a ppcmain* ppcmain*

/usr/lib64 n/a lippruntim.so* lippruntim.so*

/opt/teradata/client/<version>/bin ppcmain n/a ppcmain

/opt/teradata/client/<version>/bin64 n/a ppcmain ppcmain

/opt/teradata/client/<version>/lib lippruntim.so n/a lippruntim.so

/opt/teradata/client<version>/lib64 n/a lippruntim.so lippruntim.so

/opt/teradata/client/<version>/sample LABSBTEQ LABSBTEQ LABSBTEQ

/opt/teradata/client/<version>/sample PPCLB1 PPCLB1 PPCLB1









Directory Red Hat LinuxSUSE Linux32-bit

SUSE Linux64-bit Linux for s390x

/usr/lib clispb.dat* clispb.dat* clispb.dat* clispb.dat*

/usr/lib errmsg.cat* errmsg.cat* errmsg.cat* errmsg.cat*

/usr/lib errmsg.txt* errmsg.txt* errmsg.txt* errmsg.txt*

/usr/lib libcliv2.so* libcliv2.so* libcliv2.so* libcliv2.so*



/usr/lib libtdusr.so* libtdusr.so* libtdusr.so* libtdusr.so*

/usr/include cliv2if.h* cliv2if.h* cliv2if.h* cliv2if.h*

/usr/include coptypes.h* coptypes.h* coptypes.h* coptypes.h*

/usr/include coperr.h* coperr.h* coperr.h* coperr.h*

/usr/include dbca2px.h* dbca2px.h* dbca2px.h* dbca2px.h*

/usr/include dbcarea.h* dbcarea.h* dbcarea.h* dbcarea.h*

/usr/include dbcerr.h* dbcerr.h* dbcerr.h* dbcerr.h*

/usr/include dbchqep.h* dbchqep.h* dbchqep.h* dbchqep.h*

/usr/include parcel.h* parcel.h* parcel.h* parcel.h*

/usr/include mosiif.h* mosiif.h* mosiif.h* mosiif.h*

/usr/lib/lib-i386 libcliv2.so* n/a n/a n/a

/usr/lib/lib-i386 libtdusr.so* n/a n/a n/a

/opt/teradata/client/<version>/lib64 libcliv2.so libcliv2.so libcliv2.so libcliv2.so

/opt/teradata/client/<version>/lib64 libtdusr.so libtdusr.so libtdusr.so libtdusr.so

/opt/teradata/client/<version>/lib64 errmsg.cat errmsg.cat errmsg.cat errmsg.cat

/opt/teradata/client/<version>/lib64 errmsg.txt errmsg.txt errmsg.txt errmsg.txt

/opt/teradata/client/<version>/lib64 clispb.dat clispb.dat clispb.dat clispb.dat

/opt/teradata/client/<version>/include

coptypes.h coptypes.h coptypes.h coptypes.h


dbchqep.h dbchqep.h dbchqep.h dbchqep.h


dbca2px.h dbca2px.h dbca2px.h dbca2px.h


cliv2if.h cliv2if.h cliv2if.h cliv2if.h


coperr.h coperr.h coperr.h coperr.h


dbcarea.h dbcarea.h dbcarea.h dbcarea.h


parcel.h parcel.h parcel.h parcel.h


dbcerr.h dbcerr.h dbcerr.h dbcerr.h





Teradata Data Connector


The following table lists the files and the directories installed for each operating system supported by Teradata Data Connector.


mosiff.h mosiff.h mosiff.h mosiff.h

/opt/teradata/client<version>/lib errmsg.cat errmsg.cat errmsg.cat errmsg.cat

/opt/teradata/client<version>/lib errmsg.txt errmsg.txt errmsg.txt errmsg.txt

/opt/teradata/client<version>/lib clispb.dat clispb.dat clispb.dat clispb.dat

/opt/teradata/client/<version>/sample

CliLgn.Ex.c CliLgn.Ex.c CliLgn.Ex.c CliLgn.Ex.c


CliPPS.c CliPPS.c CliPPS.c CliPPS.c

/opt/teradata/client<version>/sample

clisamp.c clisamp.c clisamp.c clisamp.c

/opt/teradata/client<version>/sample

makesamp.lx makesamp.lx makesamp.lx makesamp.lx


makerdusr.lx makerdusr.lx makerdusr.lx makerdusr.lx


n/a n/a makesamp.lx64 n/a


n/a n/a makerdusr.lx64 n/a




/usr/lib libpm.so* libpm.so* libpm.so*

/usr/include pmdcomt.h* pmdcomt.h* pmdcomt.h*

/usr/include pmddamt.h* pmddamt.h* pmddamt.h*

/usr/include pmtypes.h* pmtypes.h* pmtypes.h*

/opt/teradata/client/<version>/lib libpm.so libpm.so libpm.so

/opt/teradata/client/<version>/include pmdcomt.h pmdcomt.h pmdcomt.h

/opt/teradata/client/<version>/include pmddamt.h pmddamt.h pmddamt.h



Teradata FastExport

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/bin, /opt/teradata/client/<version>/include, and the /opt/teradata/client/<version>/sample directories.

The following table lists the files and the directories installed for the Red Hat Linux operating system supported by Teradata FastExport.

Teradata FastLoad

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/bin and the /opt/teradata/client/<version>/sample directories.

The following table lists the files and the directories installed for each operating system supported by Teradata FastLoad.

/opt/teradata/client/<version>/include pmtypes.h pmtypes.h pmtypes.h



/usr/bin fexp* fexp* fexp*

/usr/include expnfyxt.h* expnfyxt.h* expnfyxt.h*

/usr/sample expnfyxt.c* expnfyxt.c* expnfyxt.c*

/usr/sample mkexpext.linux* mkexpext.linux* mkexpext.linux*

/opt/teradata/client/<version>/bin fexp fexp fexp

/opt/teradata/client/<version>/include expnfyxt.h expnfyxt.h expnfyxt.h

/opt/teradata/client/<version>/sample expnfyxt.c expnfyxt.c expnfyxt.c

/opt/teradata/client/<version>/sample mkexpext.linux mkexpext.linux mkexpext.suselinux-390.32


/usr/bin fastload* fastload* fastload*

/usr/sample blkexit.c* blkexit.c* blkexit.c*

/usr/sample blkexitr.c* blkexitr.c* blkexitr.c*

/usr/sample flnfyext.c* flnfyext.c* flnfyext.c*

/opt/teradata/client/<version>/bin fastload fastload fastload

/opt/teradata/client/<version>/sample blkexit.c blkexit.c blkexit.c



Teradata Generic Security Services

The files that are included with the TeraGSS package can change from package to package, so there is not a definitive filename list to verify. To verify the installation of the TeraGSS packages, verify the existence of a file named “version” in the /usr/teragss/<architecture>/<version> directory, where: <version> is the version of software that is being verified.

The following table lists the files and the directories installed for each operating system supported by Teradata Generic Security Services.


The following table lists the files and the directories installed for each operating system supported by Teradata JDBC Driver.

/opt/teradata/client/<version>/sample blkexitr.c blkexitr.c blkexitr.c

/opt/teradata/client/<version>/sample flnfyext.c flnfyext.c flnfyext.c


Platform Package File

Red Hat Linux teragss_redhatlinux-i386 /usr/teragss/redhatlinux-i386/<version>

Red Hat Linux teragss_redhatlinux-i64 /usr/teragss/redhatlinux-i64/<version>

Red Hat Linux teragss_redhatlinux-ia64 /usr/teragss/redhatlinux-ia64/<version>

SUSELinux teragss_suselinux-i386 /usr/teragss/suselinux-i386/<version>

SUSELinux teragss_suselinux-i64 /usr/teragss/suselinux-i64/<version>

SUSELinux teragss_suselinux-ia64 teragss_suselinux-ia64

Linux for s390x teragss_redhatlinux-i386 /usr/teragss/redhatlinux-i386/<version>

Linux for s390x teragss_redhatlinux-i64 /usr/teragss/redhatlinux-i64/<version>

Linux for s390x teragss_redhatlinux-ia64 /usr/teragss/redhatlinux-ia64/<version>


Executable terajdbc4.jar terajdbc4.jar terajdbc4.jar

Sample samples.jar samples.jar samples.jar

Security tdgssconfig.jar tdgssconfig.jar tdgssconfig.jar



Teradata MultiLoad


The following table lists the files and the directories installed for each operating system supported by Teradata MultiLoad.

Teradata TPump

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/bin and /opt/teradata/client/<version>/lib directories.

The following table lists the files and the directories installed for each operating system supported by Teradata TPump.


/usr/bin* mload* mload* mload*

/usr/include* mldnfyxt.h* mldnfyxt.h* mldnfyxt.h*

/usr/sample* mldnfyxt.c* mldnfyxt.c* mldnfyxt.c*

/usr/sample* mkmldext.linux* mkmldext.linux* mkmldext.linux*

/opt/teradata/client/<version>/bin mload mload mload

/opt/teradata/client/<version>/include mldnfyxt.h mldnfyxt.h mldnfyxt.h

/opt/teradata/client/<version>/sample mldnfyxt.c mldnfyxt.c mldnfyxt.c

/opt/teradata/client/<version>/sample mkmldext.linux mkmldext.linux mkmldext.suselinux-390.32


/usr/bin tpumpexe* tpumpexe* tpump

/usr/bin n/a tdatpump.cfg* tpump.exe

/usr/lib tdatpump.cfg* tdatpump.cfg tdatpump.cfg

/opt/teradata/client/<version>/bin tpumpexe* tpumpexe* tpumpexe*

/opt/teradata/client/<version>/lib tdatpump.cfg tldnfyxt.c n/a

/opt/teradata/client/<version>/sample makinmod.3000 makinmod.3000 n/a

/opt/teradata/client/<version>/sample tldnfyxt.c n/a mktldext.suselinux-390.32

/opt/teradata/client/<version>/sample tpumpimd.c tpumpimd.c tpumpimd.c



Teradata Parallel Transporter API

The default value for <INSTALLDIR> is /opt/teradata/client/<version>/tbuild.

The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter API.

/opt/teradata/client/<version>/sample tpumpar.csql tdatpump.csql tpumpar.csql



<INSTALLDIR>/lib libtelapi.so

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

<INSTALLDIR>/lib/gcc_3.x libtelapi.so libtelapi.so

<INSTALLDIR>/lib64 libtelapi.so

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

<INSTALLDIR>/lib64/gcc_3.x libtelapi.so libtelapi.so

<INSTALLDIR>/msg opermsgs.cat opermsgs.cat opermsgs.cat

<INSTALLDIR>/msg64 opermsgs.cat opermsgs.cat opermsgs.cat

<INSTALLDIR>/tptapi/inc connection.h connection.h connection.h

<INSTALLDIR>/tptapi/inc DMLGroup.h DMLGroup.h DMLGroup.h

<INSTALLDIR>/tptapi/inc schema.h schema.h schema.h

<INSTALLDIR>/tptapi/sample/inc connection.h connection.h connection.h

<INSTALLDIR>/tptapi/sample/inc DMLGroup.h DMLGroup.h DMLGroup.h

<INSTALLDIR>/tptapi/sample/inc schema.h schema.h schema.h

<INSTALLDIR>/tptapi/sample/common OptionsManager.cpp OptionsManager.cpp OptionsManager.cpp

<INSTALLDIR>/tptapi/sample/common OptionsManager.h OptionsManager.h OptionsManager.h

<INSTALLDIR>/tptapi/sample/generic GenericDriver.cpp GenericDriver.cpp GenericDriver.cpp

<INSTALLDIR>/tptapi/sample/generic main.cpp main.cpp main.cpp

<INSTALLDIR>/tptapi/sample/generic input.txt input.txt input.txt

<INSTALLDIR>/tptapi/sample/generic infile.littleEndian infile.littleEndian infile.littleEndian



<INSTALLDIR>/tptapi/sample/generic makedriver.linux makedriver.linux makedriver.linux_390

<INSTALLDIR>/tptapi/sample/generic cleanupTables.bteq cleanupTables.bteq cleanupTables.bteq

<INSTALLDIR>/tptapi/sample/generic setupTables.bteq setupTables.bteq setupTables.bteq

<INSTALLDIR>/tptapi/sample/generic/inc

GenericDriver.h GenericDriver.h GenericDriver.h

<INSTALLDIR>/tptapi/sample/blockloading

BlockLoad.cpp BlockLoad.cpp BlockLoad.cpp


main.cpp main.cpp main.cpp


input.txt input.txt input.txt


infile.littleEndian infile.littleEndian infile.littleEndian


makeblock.linux makeblock.linux makeblock.linux_390


cleanupTables.bteq cleanupTables.bteq cleanupTables.bteq


setupTables.bteq setupTables.bteq setupTables.bteq

<INSTALLDIR>/tptapi/sample/blockloading/inc

BlockLoad.h BlockLoad.h BlockLoad.h

<INSTALLDIR>/tptapi/sample/checkpoint

checkpoint.cpp checkpoint.cpp checkpoint.cpp




input.txt input.txt input.txt


infile.littleEndian infile.littleEndian infile.littleEndian


makecheckpoint.linux makecheckpoint.linux makecheckpoint.linux_390





<INSTALLDIR>/tptapi/sample/checkpoint/inc

checkpoint.h checkpoint.h checkpoint.h




<INSTALLDIR>/tptapi/sample/getbuffer GetBuffer.cpp GetBuffer.cpp GetBuffer.cpp

<INSTALLDIR>/tptapi/sample/getbuffer main.cpp main.cpp main.cpp

<INSTALLDIR>/tptapi/sample/getbuffer input.txt input.txt input.txt

<INSTALLDIR>/tptapi/sample/getbuffer makedriver.linux makedriver.linux makedriver.linux_390

<INSTALLDIR>/tptapi/sample/getbuffer cleanupTables.bteq cleanupTables.bteq cleanupTables.bteq

<INSTALLDIR>/tptapi/sample/getbuffer setupTables.bteq setupTables.bteq setupTables.bteq

<INSTALLDIR>/tptapi/sample/getbuffer/inc

GetBuffer.h GetBuffer.h GetBuffer.h

<INSTALLDIR>/tptapi/sample/xsp GenericDriver.cpp GenericDriver.cpp GenericDriver.cpp

<INSTALLDIR>/tptapi/sample/xsp GenericDriver.h GenericDriver.h GenericDriver.h

<INSTALLDIR>/tptapi/sample/xsp OptionsReader.cpp OptionsReader.cpp OptionsReader.cpp

<INSTALLDIR>/tptapi/sample/xsp OptionsReader.h OptionsReader.h OptionsReader.h

<INSTALLDIR>/tptapi/sample/xsp makedriver.linux makedriver.linux makedriver.linux

<INSTALLDIR>/tptapi/sample/xsp xsp.cpp xsp.cpp xsp.cpp

<INSTALLDIR>/tptapi/sample/xsp input.lod input.lod input.lod

<INSTALLDIR>/tptapi/sample/xsp input.exp input.exp input.exp

<INSTALLDIR>/tptapi/sample/xsp input.stm input.stm input.stm

<INSTALLDIR>/tptapi/sample/xsp input.upd input.upd input.upd

<INSTALLDIR>/tptapi/sample/xsp infile.littleEndian infile.littleEndian infile.littleEndian

<INSTALLDIR>/tptapi/sample/multiple MultipleOperators.cpp MultipleOperators.cpp MultipleOperators.cpp

<INSTALLDIR>/tptapi/sample/multiple


<INSTALLDIR>/tptapi/sample/multiple input.txt input.txt input.txt

<INSTALLDIR>/tptapi/sample/multiple makemultiple.linux makemultiple.linux makemultiple.linux_390

<INSTALLDIR>/tptapi/sample/multiple cleanupTables.bteq cleanupTables.bteq cleanupTables.bteq

<INSTALLDIR>/tptapi/sample/multiple setupTables.bteq setupTables.bteq setupTables.bteq

<INSTALLDIR>/tptapi/sample/multiple/inc

MultipleOperators.h MultipleOperators.h MultipleOperators.h

<INSTALLDIR>/tptapi/sample/multi_node

multitest.cpp multitest.cpp multitest.cpp





synchronize.cpp synchronize.cpp synchronize.cpp


fileio.cpp fileio.cpp fileio.cpp


master.cpp master.cpp master.cpp


slave.cpp slave.cpp slave.cpp


master_input.txt master_input.txt master_input.txt


slave_input.txt slave_input.txt slave_input.txt


infilemaster.littleEndian infilemaster.littleEndian infilemaster.littleEndian


infileslave.littleEndian.1 infileslave.littleEndian.1 infileslave.littleEndian.1


makemulti.linux makemulti.linux makemulti.linux_390






fileio.h fileio.h fileio.h


multitest.h multitest.h multitest.h


synchronize.h synchronize.h synchronize.h

<INSTALLDIR>/tptapi/sample/threads PerfTestMessage.cpp PerfTestMessage.cpp PerfTestMessage.cpp

<INSTALLDIR>/tptapi/sample/threads TelapiThreadTest.cpp TelapiThreadTest.cpp TelapiThreadTest.cpp

<INSTALLDIR>/tptapi/sample/threads makeparallel.linux makeparallel.linux makeparallel.linux_390

<INSTALLDIR>/tptapi/sample/threads TestBase.cpp TestBase.cpp TestBase.cpp

<INSTALLDIR>/tptapi/sample/threads TestExport.cpp TestExport.cpp TestExport.cpp

<INSTALLDIR>/tptapi/sample/threads TestLoad.cpp TestLoad.cpp TestLoad.cpp

<INSTALLDIR>/tptapi/sample/threads TestSim.cpp TestSim.cpp TestSim.cpp

<INSTALLDIR>/tptapi/sample/threads TestStream.cpp TestStream.cpp TestStream.cpp




Teradata Parallel Transporter Export Operator


The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Export Operator.

<INSTALLDIR>/tptapi/sample/threads TestUpdate.cpp TestUpdate.cpp TestUpdate.cpp

<INSTALLDIR>/tptapi/sample/threads ThreadTest.cpp ThreadTest.cpp ThreadTest.cpp

<INSTALLDIR>/tptapi/sample/threads ThreadTestParameters.cpp

ThreadTestParameters.cpp


<INSTALLDIR>/tptapi/sample/threads Synchronizer.cpp Synchronizer.cpp Synchronizer.cpp

<INSTALLDIR>/tptapi/sample/threads input.txt input.txt input.txt

<INSTALLDIR>/tptapi/sample/threads loadData.littleEndian loadData.littleEndian loadData.littleEndian

<INSTALLDIR>/tptapi/sample/threads cleanupTables.bteq cleanupTables.bteq cleanupTables.bteq

<INSTALLDIR>/tptapi/sample/threads setupTables.bteq setupTables.bteq setupTables.bteq

<INSTALLDIR>/tptapi/sample/threads/inc

common.h common.h common.h


PerfTestMessage.h PerfTestMessage.h PerfTestMessage.h


TestBase.h TestBase.h TestBase.h


TestExport.h TestExport.h TestExport.h


TestLoad.h TestLoad.h TestLoad.h


TestSim.h TestSim.h TestSim.h


TestStream.h TestStream.h TestStream.h


TestUpdate.h TestUpdate.h TestUpdate.h


ThreadTest.h ThreadTest.h ThreadTest.h


ThreadTestParameters.h ThreadTestParameters.h ThreadTestParameters.h


Synchronizer.h Synchronizer.h Synchronizer.h






The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Infrastructure.


<INSTALLDIR>/lib libexportop.so libexportop.so libexportop.so

<INSTALLDIR>/lib64 libexportop.so libexportop.so libexportop.so

<INSTALLDIR>/sample expnfyxt.c expnfyxt.c expnfyxt.c


<INSTALLDIR> twbcfg.ini twbcfg.ini twbcfg.ini

<INSTALLDIR> twboper.ini twboper.ini twboper.ini

<INSTALLDIR> version version version

<INSTALLDIR>/bin tbuild tbuild tbuild

<INSTALLDIR>/bin tlogview tlogview tlogview

<INSTALLDIR>/bin tdload tdload tdload

<INSTALLDIR>/bin tdlog tdlog tdlog

<INSTALLDIR>/bin twbkill twbkill twbkill

<INSTALLDIR>/bin twbstat twbstat twbstat

<INSTALLDIR>/bin ptmgts ptmgts ptmgts

<INSTALLDIR>/bin ptmtims ptmtims ptmtims

<INSTALLDIR>/bin ptmexec ptmexec ptmexec

<INSTALLDIR>/bin ptmjlgr ptmjlgr ptmjlgr

<INSTALLDIR>/bin ptmlvs ptmlvs ptmlvs

<INSTALLDIR>/bin coordinator coordinator coordinator

<INSTALLDIR>/bin planexecutor planexecutor planexecutor

<INSTALLDIR>/bin executor executor executor

<INSTALLDIR>/bin twbpkgrm twbpkgrm twbpkgrm

<INSTALLDIR>/bin tbuildexe tbuildexe tbuildexe

<INSTALLDIR>/bin tlogviewexe tlogviewexe tlogviewexe

<INSTALLDIR>/bin twbcmdexe twbcmdexe twbcmdexe



<INSTALLDIR>/bin twbkillexe twbkillexe twbkillexe

<INSTALLDIR>/bin twbstatexe twbstatexe twbstatexe

<INSTALLDIR>/bin twbrmcpexe twbrmcpexe twbrmcpexe

<INSTALLDIR>/bin tptlaunch tptlaunch tptlaunch

<INSTALLDIR>/bin twbpathexe twbpathexe twbpathexe

<INSTALLDIR>/bin twbrmcp twbrmcp twbrmcp

<INSTALLDIR>/bin pxlogdef.h pxlogdef.h pxlogdef.h

<INSTALLDIR>/inc pxstc.h pxstc.h pxstc.h

<INSTALLDIR>/inc pxutypes.h pxutypes.h pxutypes.h

<INSTALLDIR>/inc pxdtypes.h pxdtypes.h pxdtypes.h

<INSTALLDIR>/inc pxoper.h pxoper.h pxoper.h

<INSTALLDIR>/inc pxos.h pxos.h pxos.h

<INSTALLDIR>/inc pxtypes.h pxtypes.h pxtypes.h

<INSTALLDIR>/inc pxdef.h pxdef.h pxdef.h

<INSTALLDIR>/inc pxmacros.h pxmacros.h pxmacros.h

<INSTALLDIR>/inc pxversion.h pxversion.h pxversion.h

<INSTALLDIR>/inc libpxicu.so libpxicu.so libpxicu.so

<INSTALLDIR>/lib libdataconop.so libdataconop.so libdataconop.so

<INSTALLDIR>/lib libddlop.so libddlop.so libddlop.so

<INSTALLDIR>/lib libodbcop.so libodbcop.so libodbcop.so

<INSTALLDIR>/lib liboscmdop.so liboscmdop.so liboscmdop.so

<INSTALLDIR>/lib libinsertop.so libinsertop.so libinsertop.so

<INSTALLDIR>/lib ibselectop.so ibselectop.so ibselectop.so

<INSTALLDIR>/lib libopcommon.so libopcommon.so libopcommon.so

<INSTALLDIR>/lib libptmos.so libptmos.so libptmos.so

<INSTALLDIR>/lib libptmpo.so libptmpo.so libptmpo.so

<INSTALLDIR>/lib libptmpi.so libptmpi.so libptmpi.so

<INSTALLDIR>/lib libptmpi.a libptmpi.a libptmpi.a

<INSTALLDIR>/lib libptmin.so libptmin.so libptmin.so

<INSTALLDIR>/lib liblogview.so liblogview.so liblogview.so

<INSTALLDIR>/lib libpxcommon.so libpxcommon.so libpxcommon.so




Teradata Parallel Transporter Load Operator


<INSTALLDIR>/lib libflimop.so libflimop.so libflimop.so

<INSTALLDIR>/lib libfeomop.so libfeomop.so libfeomop.so

<INSTALLDIR>/lib libmlimop.so libmlimop.so libmlimop.so

<INSTALLDIR>/lib libtableqry.so libtableqry.so libtableqry.so

<INSTALLDIR>/msg opermsgs.cat opermsgs.cat opermsgs.cat

<INSTALLDIR>/msg twbmsgs.cat twbmsgs.cat twbmsgs.cat

<INSTALLDIR>/sample/etl GT11.txt GT11.txt GT11.txt








<INSTALLDIR>/sample/etl jobvars.txt jobvars.txt jobvars.txt

<INSTALLDIR>/sample/metadata sql1.txt sql1.txt sql1.txt

<INSTALLDIR>/sample/metadata sql2.txt sql2.txt sql2.txt

<INSTALLDIR>/sample/metadata twb_status.txt twb_status.txt twb_status.txt

<INSTALLDIR>/sample/metadata twb_targets.txt twb_targets.txt twb_targets.txt

<INSTALLDIR>/template $STREAM.txt $STREAM.txt $STREAM.txt

<INSTALLDIR>/template $INSERTER.txt $INSERTER.txt $INSERTER.txt

<INSTALLDIR>/template $UPDATE.txt $UPDATE.txt $UPDATE.txt

<INSTALLDIR>/template $FILE_READER.txt $FILE_READER.txt $FILE_READER.txt

<INSTALLDIR>/template $LOAD.txt $LOAD.txt $LOAD.txt

<INSTALLDIR>/template $DATACONNECTOR_PRODUCER.txt

$DATACONNECTOR_PRODUCER.txt


/usr/bin twbpkgrm twbpkgrm twbpkgrm

/var twbpkg twbpkg twbpkg




The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Load Operator.

Teradata Parallel Transporter Stream Operator


The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Stream Operator.

Teradata Parallel Transporter Update Operator


The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Update Operator.


An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/lib and the /opt/teradata/client/<version>/opt directories.

The following table lists the files and the directories installed for each operating system supported by Teradata WebSphere MQ Access Module.


<INSTALLDIR>/lib libloadop.so libloadop.so libloadop.so

<INSTALLDIR>/lib64 libloadop.so libloadop.so libloadop.so

<INSTALLDIR>/sample ldnfyext.c ldnfyext.c ldnfyext.c


<INSTALLDIR>/lib libstreamop.so libstreamop.so libstreamop.so

<INSTALLDIR>/lib64 libstreamop.so libstreamop.so libstreamop.so

<INSTALLDIR>/sample stmnfyxt.c stmnfyxt.c stmnfyxt.c


<INSTALLDIR>/lib libupdateop.so libupdateop.so libupdateop.so

<INSTALLDIR>/lib64 libupdateop.so libupdateop.so libupdateop.so

<INSTALLDIR>/sample updnfyxt.c updnfyxt.c updnfyxt.c




/usr/lib libmqsc.so* libmqsc.so* libmqsc.so*

/opt/teradata/client/<version>/lib libmqsc.so libmqsc.so libmqsc.so


CHAPTER 16

Checking Files and Folderson UNIX Systems

This section contains tables which list the directories and filenames of products to enable verification that Teradata Tools and Utilities software has been installed properly on UNIX operating systems.

Task 1: Verifying Installation of Individual Products

Procedure - Verifying Installation of Individual Products

Follow these steps to verify the installation of individual Teradata Tools and Utilities products and their dependencies.

1 Check that the directories specified in the tables below have been installed.

2 Check that the files specified in the tables below have been installed.

• Basic Teradata Query

• Named Pipes Access Module



• Teradata C Preprocessor2


• Teradata COBOL Preprocessor2



• Teradata FastExport

• Teradata FastLoad

• Teradata Generic Security Services

• Teradata MultiLoad

• Teradata TPump


• Teradata Parallel Transporter Export Operator


Chapter 16: Checking Files and Folders on UNIX SystemsTask 1: Verifying Installation of Individual Products


• Teradata Parallel Transporter Load Operator

• Teradata Parallel Transporter Stream Operator

• Teradata Parallel Transporter Update Operator

• Teradata WebSphere MQ Access Module

Basic Teradata Query

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for a file that has been installed in the directory (default) /opt/teradata/client/usr/<version>/bin.

The following table lists the files and the directories installed for each operating system supported by Basic Teradata Query.

Named Pipes Access Module


The following table lists the files and the directories installed for each operating system supported by Named Pipes Access Module.

Directory HP-UX IBM AIX Sun Solaris SPARC Sun Solaris Opteron

/usr/bin bteq* bteq* bteq* bteq*

/usr/include btnfyext.h* btnfyext.h* btnfyext.h* btnfyext.h*

/opt/teradata/client/<version>/bin

bteq bteq bteq bteq


btnfyext.c

mkbtnfyext.hpux

mkbtnfyext.hpux-ia64

btnfyext.c

mkbtnfyext.aix

btnfyext.c

mkbtnfyext.unx

btnfyext.c

mkbtnfyext.unx


btnfyext.h btnfyext.h btnfyext.h btnfyext.h

Directory HP-UX IBM AIXSun Solaris SPARC

Sun Solaris Opteron

/usr/lib np_axsmod.sl* np_axsmod.so* np_axsmod.so* np_axsmod.so*

/usr/lib/hpux32 np_axsmod.so* n/a n/a n/a

/usr/lib/hpux64 np_axsmod.so* n/a n/a n/a

/opt/teradata/client/<version>/lib np_axsmod.sl np_axsmod.so np_axsmod.so np_axsmod.so

/opt/teradata/client/<version>/lib np_axsmod.so n/a n/a n/a



ODBC Driver for Teradata

The default directory for the ODBC Driver for Teradata for all platforms is:

/opt/teradata/client/ODBC_32/

and/or

/opt/teradata/client/ODBC_64/

The following table lists the files and the directories installed for each operating system supported by the ODBC Driver for Teradata.

/opt/teradata/client/<version>/lib64

np_axsmod.so n/a n/a n/a


Sun Solaris Opteron

Directory HP-UXHP-UXIitanium IBM AIX

Sun Solaris SPARC

Sun Solaris Opteron

/usr/lib libivicu24.so -> /opt/teradata/client/ODBC_32/lib/libivicu24.so

hpux32/libivicu234.so -> /opt/teradata/client/ODBC_32/lib/libivicu234.so

libivicu24.so -> /opt/teradata/client/ODBC_32/lib/libivicu24.so



/usr/lib libodbc.so.so -> /opt/teradata/client/ODBC_32/lib/libodbc.so

hpux32/libodbc.so.so -> /opt/teradata/client/ODBC_32/lib/libodbc.so

libodbc.so.so -> /opt/teradata/client/ODBC_32/lib/libodbc.so



/usr/lib libodbcinst.so -> /opt/teradata/client/ODBC_32/lib/libodbc.so

hpux32/libodbcinst.so -> /opt/teradata/client/ODBC_32/lib/libodbc.so

libodbcinst.so -> /opt/teradata/client/ODBC_32/lib/libodbc.so



/usr/lib libtdparse.so -> /opt/teradata/client/ODBC_32/lib/libtdparse.so

hpux32/libtdparse.so -> /opt/teradata/client/ODBC_32/lib/libtdparse.so

libtdparse.so -> /opt/teradata/client/ODBC_32/lib/libtdparse.so



/user/lib libtdsso.so-> /opt/teradata/client/ODBC_32/lib/libtdsso.so

hpux32/libtdsso.so-> /opt/teradata/client/ODBC_32/lib/libtdsso.so

libtdsso.so-> /opt/teradata/client/ODBC_32/lib/libtdsso.so



/opt/teradata/client/<version>/odbc_32/

odbc.ini odbc.ini odbc.ini odbc.ini odbc.ini




odbcinst.ini odbcinst.ini odbcinst.ini odbcinst.ini odbcinst.ini


README README README README README

/opt/teradata/client/<version>/odbc_32/bin

tdxodbc tdxodbc tdxodbc tdxodbc tdxodbc


tdxwinapp tdxwinapp tdxwinapp tdxwinapp tdxwinapp


.build_pre130_bridge






tdata.5 tdata.5 tdata.5 tdata.5 tdata.5

/opt/teradata/client/<version>/odbc_32/include

odbcinst.h odbcinst.h odbcinst.h odbcinst.h odbcinst.h


sql.h sql.h sql.h sql.h sql.h

/opt/teradata/<version>/odbc_32/include

sqlext.h sqlext.h sqlext.h sqlext.h sqlext.h


sqltypes.h sqltypes.h sqltypes.h sqltypes.h sqltypes.h


sqlucode.h sqlucode.h sqlucode.h sqlucode.h sqlucode.h


sqlunx.h sqlunx.h sqlunx.h sqlunx.h sqlunx.h


tdsql.h tdsql.h tdsql.h tdsql.h tdsql.h


Sun Solaris SPARC

Sun Solaris Opteron




libtdparse.sl libtdparse.sl libtdparse.so libtdparse.so libtdparse.so


libtdsso.sl libtdsso.sl libtdsso.so libtdsso.so libtdsso.so

/opt/teradata/client/<version>/odbc_32/lib

tdata.sl tdata.sl tdata.so tdata.so tdata.so


dconndlg.sl dconndlg.sl tdconndlg.so tdconndlg.so tdconndlg.so

/opt/teradata/client/<version>/odbc_32/locale/en_US/LC_MESSAGES

odbc.m odbc.m n/a n/a n/a


tdodbc.cat tdodbc.cat tdodbc.cat tdodbc.cat tdodbc.cat

/opt/teradata/client/<version>/odbc_32/samples/C

adhoc adhoc adhoc adhoc adhoc


adhoc.c adhoc.c adhoc.c adhoc.c adhoc.c


common.includes common.includes aix.includes common.includes common.includes


error.c error.c error.c error.c error.c


Makefile Makefile Makefile Makefile Makefile

/opt/teradata/client/<version>/odbc_32/samples/C++



adhoc.cpp adhoc.cpp adhoc.cpp adhoc.cpp adhoc.cpp


Sun Solaris SPARC

Sun Solaris Opteron






error.cpp error.cpp error.cpp error.cpp error.cpp



/usr/lib/ pa20_64/libivicu24.so -> /opt/teradata/client/ODBC_64/lib/libivicu24.so

hpux64/libivicu24.so -> /opt/teradata/client/ODBC_64/lib/libivicu24.so

lib64/libivicu24.so -> /opt/teradata/client/ODBC_64/lib/libivicu24.so

64/libivicu24.so -> /opt/teradata/client/ODBC_64/lib/libivicu24.so

64/libddicu24.so -> /opt/teradata/client/ODBC_64/lib/libddicu24.so

/usr/lib/ pa20_64/libodbc.so.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

hpux64/libodbc.so.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

lib64/libodbc.so.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

64/libodbc.so.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

64/libodbc.so.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

/usr/lib/ pa20_64/libodbcinst.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

hpux64/libodbcinst.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

lib64/libodbcinst.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

64/libodbcinst.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

64/libodbcinst.so -> /opt/teradata/client/ODBC_64/lib/libodbc.so

/usr/lib/ pa20_64/libtdparse.so -> /opt/teradata/client/ODBC_64/lib/libtdparse.so

hpux64/libtdparse.so -> /opt/teradata/client/ODBC_64/lib/libtdparse.so

lib64/libtdparse.so -> /opt/teradata/client/ODBC_64/lib/libtdparse.so

64/libtdparse.so -> /opt/teradata/client/ODBC_64/lib/libtdparse.so

64/libtdparse.so -> /opt/teradata/client/ODBC_64/lib/libtdparse.so

/usr/lib/ pa20_64/libtdsso.so-> /opt/teradata/client/ODBC_64/lib/libtdsso.so

hpux64/libtdsso.so-> /opt/teradata/client/ODBC_64/lib/libtdsso.so

lib64/libtdsso.so-> /opt/teradata/client/ODBC_64/lib/libtdsso.so

64/libtdsso.so-> /opt/teradata/client/ODBC_64/lib/libtdsso.so

64/libtdsso.so-> /opt/teradata/client/ODBC_64/lib/libtdsso.so

/opt/teradata/client/<version>/odbc_64

odbc.ini odbc.ini odbc.ini odbc.ini odbc.ini


odbcinst.ini odbcinst.ini odbcinst.ini odbcinst.ini odbcinst.ini


Sun Solaris SPARC

Sun Solaris Opteron




README README README README README

/opt/teradata/client/<version>/ODBC_64/bin

tdxodbc tdxodbc tdxodbc tdxodbc tdxodbc


tdxwinapp tdxwinapp tdxwinapp tdxwinapp tdxwinapp








tdata.5 tdata.5 tdata.5 tdata.5 tdata.5


odbcinst.h odbcinst.h odbcinst.h odbcinst.h odbcinst.h


sql.h sql.h sql.h sql.h sql.h


sqlext.h sqlext.h sqlext.h sqlext.h sqlext.h


sqltypes.h sqltypes.h sqltypes.h sqltypes.h sqltypes.h


sqlucode.h sqlucode.h sqlucode.h sqlucode.h sqlucode.h


sqlunx.h sqlunx.h sqlunx.h sqlunx.h sqlunx.h


tdsql.h tdsql.h tdsql.h tdsql.h tdsql.h


libtdparse.sl libtdparse.sl libtdparse.so libtdparse.so libtdparse.so


Sun Solaris SPARC

Sun Solaris Opteron




libtdsso.sl libtdsso.sl libtdsso.so libtdsso.so libtdsso.so


tdata.sl tdata.sl tdata.so tdata.so tdata.so


dconndlg.sl dconndlg.sl tdconndlg.so tdconndlg.so tdconndlg.so

/opt/teradata/client/<version>/odbc_64/locale/en_US/LC_MESSAGES

odbc.m odbc.m n/a n/a n/a


tdodbc.cat tdodbc.cat tdodbc.cat tdodbc.cat tdodbc.cat




adhoc.c adhoc.c adhoc.c adhoc.c adhoc.c




error.c error.c error.c error.c error.c






adhoc.cpp adhoc.cpp adhoc.cpp adhoc.cpp adhoc.cpp


Sun Solaris SPARC

Sun Solaris Opteron






error.cpp error.cpp error.cpp error.cpp error.cpp




Sun Solaris SPARC

Sun Solaris Opteron




The following table lists the files and the directories installed for each operating system supported by Shared Common Components for Internationalization for Teradata.

Directory HP-UX HP-UX IA64 IBM AIXSun Solaris SPARC

Sun Solaris Opteron

/usr/lib libicudatatd.sl-> /opt/teradata/client/<version>/tdicu/lib/libicudatatd.sl.36.0

n/a libicudatatd.so-> /opt/teradata/client/<version>/tdicu/lib/libicudatatd36.0.so

libicudatatd.so ->/opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

libicudatatd.so ->/opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

/usr/lib libicui18ntd.sl-> /opt/teradata/client/<version>/tdicu/lib/ libicui18ntd.sl.36.0

n/a libicui18ntd.so-> /opt/teradata/client/<version>/tdicu/lib/libicui18ntd36.0.so

libicui18ntd.so -> /opt/teradata/client/<version>/tdicu/lib/libicui18ntd.so.36.0

libicui18ntd.so -> /opt/teradata/client/<version>/tdicu/lib/libicui18ntd.so.36.0

/usr/lib libicuuctd.sl-> /opt/teradata/client/<version>/tdicu/lib/ libicuuctd.sl.36.0

n/a libicuuctd.so-> /opt/teradata/client/<version>/tdicu/lib/libicuuctd36.0.so



/usr/lib libicuiotd.sl -> /opt/teradata/client/<version>/tdicu/lib/ libicuiotd.sl.36.0

n/a libicuiotd.so-> /opt/teradata/client/<version>/tdicu/lib/libicuiotd36.0.so



/usr/lib libiculxtd.sl ->/opt/teradata/client/<version>/tdicu/lib/libiculxtd.sl.36.0

n/a libiculxtd.so -> /opt/teradata/client/<version>/tdicu/lib/libiculxtd36.0.so



/usr/lib libiculetd.sl -> /opt/teradata/client/<version>/tdicu/lib/libiculetd.sl.36.0

n/a libiculetd.so -> /opt/teradata/client/<version>/tdicu/lib/libiculetd36.0.so



/usr/lib libicudatatd.sl.36-> /opt/teradata/client/<version>/tdicu/lib/libicudatatd.sl.36.0

n/a libicudatatd36.so-> /opt/teradata/client/<version>/tdicu/lib/libicudatatd36.0.so

libicudatatd.so.36 ->/opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

libicudatatd.so.36 ->/opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0



/usr/lib libicui18ntd.sl.36-> /opt/teradata/client/<version>/tdicu/lib/ libicui18ntd.sl.36.0

n/a libicui18ntd36.so-> /opt/teradata/client/<version>/tdicu/lib/libicui18ntd36.0.so



/usr/lib libicuuctd.sl.36-> /opt/teradata/client/<version>/tdicu/lib/ libicuuctd.sl.36.0

n/a libicuuctd36.so-> /opt/teradata/client/<version>/tdicu/lib/libicuuctd36.0.so

libicuuctd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libicuuctd.so.36.0

libicuuctd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libicuuctd.so.36.0

/usr/lib libicuiotd.sl .36-> /opt/teradata/client/<version>/tdicu/lib/ libicuiotd.sl.36.0

n/a libicuiotd36.so-> /opt/teradata/client/<version>/tdicu/lib/libicuiotd36.0.so


libicuiotd.so.36-> /opt/teradata/client/<version>/tdicu/lib/libicuiotd.so.36.0

/usr/lib libiculxtd36.sl .36->/opt/teradata/client/<version>/tdicu/lib/libiculxtd.sl.36.0

n/a libiculxtd36.so -> /opt/teradata/client/<version>/tdicu/lib/libiculxtd36.0.so

libiculxtd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libiculxtd.so.36.0

libiculxtd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libiculxtd.so.36.0

/usr/lib libiculetd36.sl .36->/opt/teradata/client/<version>/tdicu/lib/libiculetd.sl.36.0

n/a libiculetd36.so -> /opt/teradata/client/<version>/tdicu/lib/libiculetd36.0.so

libiculetd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libiculetd.so.36.0

libiculetd.so.36 -> /opt/teradata/client/<version>/tdicu/lib/libiculetd.so.36.0

/usr/lib/hpux32 n/a libicudatatd.so-> /opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

n/a n/a n/a

/usr/lib/hpux32 n/a libicui18ntd.so-> /opt/teradata/client/<version>/tdicu/lib/ libicui18ntd.so.36.0

n/a n/a n/a

/usr/lib/hpux32 n/a libicuuctd.so-> /opt/teradata/client/<version>/tdicu/lib/ libicuuctd.so.36.0

n/a n/a n/a


Sun Solaris Opteron



/usr/lib/hpux32 n/a libicuiotd.so -> /opt/teradata/client/<version>/tdicu/lib/ libicuiotd.s0.36.0

n/a n/a n/a

/usr/lib/hpux32 n/a libiculxtd.so ->/opt/teradata/client/<version>/tdicu/lib/libiculxtd.so.36.0

n/a n/a n/a

/usr/lib/hpux32 n/a libiculetd.so -> /opt/teradata/client/<version>/tdicu/lib/libiculetd.so.36.0

n/a n/a n/a

/usr/lib/hpux32 n/a libicudatatd.so.36-> /opt/teradata/client/<version>/tdicu/lib/libicudatatd.so.36.0

n/a n/a n/a

/usr/lib/hpux32 n/a libicui18ntd.so.36-> /opt/teradata/client/<version>/tdicu/lib/ libicui18ntd.so.36.0

n/a n/a n/a

/usr/lib/hpux32 n/a libicuuctd.so.36-> /opt/teradata/client/<version>/tdicu/lib/ libicuuctd.so.36.0

n/a n/a n/a

/usr/lib/hpux32 n/a libicuiotd.so .36-> /opt/teradata/client/<version>/tdicu/lib/ libicuiotd.so.36.0

n/a n/a n/a

/usr/lib/hpux32 n/a libiculxtd36.so .36->/opt/teradata/client/<version>/tdicu/lib/libiculxtd.so.36.0

n/a n/a n/a


Sun Solaris Opteron



/usr/lib/hpux32 n/a libiculetd36.so .36->/opt/teradata/client/<version>/tdicu/lib/libiculetd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libicui18ntd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libicudatatd.so .36-> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libicuuctd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libiculxtd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libiculetd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libicuiotd.so.36-> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libicui18ntd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0

n/a n/a n/a


Sun Solaris Opteron



/usr/lib/hpux64 n/a libicudatatd.so-> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libicuuctd.so-> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libiculxtd.so-> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libiculetd.so-> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0

n/a n/a n/a

/usr/lib/hpux64 n/a libicuiotd.so-> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

n/a n/a n/a


libicudatatd.sl-> libicudatatd.sl.36.0

libicudatatd.so->libicudatatd.so.36.0

libicudatatd.so->libicudatatd36.0.so




libicui18ntd.sl-> libicui18ntd.sl.36.0

libicui18ntd.so->libicui18ntd.so.36.0

libicui18ntd.so-> libicui18ntd36.0.so




libicuuctd.sl ->libicuuctd.sl.36.0

libicuuctd.so->libicuuctd.so.36.0

libicuuctd.so->libicuuctd36.0.so




libicuiotd.sl -> libicuiotd.sl.36.0

libicuiotd.so ->libicuiotd.s0.36.0

libicuiotd.so->libicuiotd36.0.so




Sun Solaris Opteron




libiculxtd.sl ->libiculxtd.sl.36.0

libiculxtd.so ->libiculxtd.so.36.0

libiculxtd.so -> libiculxtd36.0.so




libiculetd.sl -> libiculetd.sl.36.0

libiculetd.so ->libiculetd.so.36.0

libiculetd.so -> libiculetd36.0.so




libicudatatd.sl.36-> libicudatatd.sl.36.0

libicudatatd.so.36->libicudatatd.so.36.0

libicudatatd36.so->libicudatatd36.0.so




libicui18ntd.sl.36-> libicui18ntd.sl.36.0


libicui18ntd36.so->libicui18ntd36.0.so




libicuuctd.sl.36 ->libicuuctd.sl.36.0

libicuuctd.so.36-> libicuuctd.so.36.0

libicuuctd36.so->libicuuctd36.0.so




libicuiotd.sl .36-> libicuiotd.sl.36.0

libicuiotd.so .36-> libicuiotd.so.36.0

libicuiotd36.so->libicuiotd36.0.so




libiculxtd36.sl .36->libiculxtd.sl.36.0

libiculxtd36.so .36->libiculxtd.so.36.0

libiculxtd36.so -> libiculxtd36.0.so




libiculetd36.sl .36->libiculetd.sl.36.0

libiculetd36.so .36->libiculetd.so.36.0

libiculetd36.so -> /opt/teradata/client/<version>/tdicu/lib/libiculetd36.0.so




libicudatatd.sl.36.0 libicudatatd.so.36.0

libicudatatd36.0.so

libicudatatd.so.36.0



libicui18ntd.sl.36.0 libicui18ntd.so.36.0

libicui18ntd36.0.so

libicui18ntd.so.36.0



libicuuctd.sl.36.0 libicuuctd.so.36.0 libicuuctd36.0.so libicuuctd.so.36.0 libicuuctd.so.36.0


Sun Solaris Opteron




libicuiotd.sl.36.0 libicuiotd.so.36.0 libicuiotd36.0.so libicuiotd.so.36.0 libicuiotd.so.36.0


libiculxtd.sl.36.0 libiculxtd.so.36.0 libiculxtd36.0.so libiculxtd.so.36.0 libiculxtd.so.36.0


libiculetd.sl.36.0 libiculetd.so.36.0 libiculetd36.0.so libiculetd.so.36.0 libiculetd.so.36.0

usr/lib/sparcv9 n/a n/a n/a libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a n/a libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a libiculxtd.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a n/a libiculetd.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a n/a libicuiotd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a n/a libicui18ntd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0

n/a


Sun Solaris Opteron



usr/lib/sparcv9 n/a n/a n/a libicudatatd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a n/a libicuuctd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a libiculxtd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a n/a libiculetd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a n/a libicuiotd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

n/a

usr/lib/sparcv9 n/a n/a n/a libicui18ntd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0

n/a

/usr/lib/amd64 n/a n/a n/a n/a libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

/usr/lib/amd64 n/a n/a n/a n/a libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd.so.36.0


Sun Solaris Opteron



/usr/lib/amd64 n/a n/a n/a n/a libiculxtd.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

/usr/lib/amd64 n/a n/a n/a n/a libiculetd.so -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0

/usr/lib/amd64 n/a n/a n/a n/a libicuiotd.so -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

/usr/lib/amd64 n/a n/a n/a n/a libicui18ntd.so ->/opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0

/usr/lib/amd64 n/a n/a n/a n/a libicudatatd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicudatatd.so.36.0

/usr/lib/amd64 n/a n/a n/a n/a libicuuctd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicuuctd.so.36.0

/usr/lib/amd64 n/a n/a n/a n/a libiculxtd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculxtd.so.36.0

/usr/lib/amd64 n/a n/a n/a n/a libiculetd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libiculetd.so.36.0


Sun Solaris Opteron



/usr/lib/amd64 n/a n/a n/a n/a libicuiotd.so.36 -> /opt/teradata/client/<version>/tdicu/lib64/libicuiotd.so.36.0

/usr/lib/amd64 n/a n/a n/a n/a libicui18ntd.so.36 ->/opt/teradata/client/<version>/tdicu/lib64/libicui18ntd.so.36.0

/usr/lib/lib_64 n/a n/a libicudatatd.so->/opt/teradata/client/<version>/tdicu/lib64/libicudatatd36.0.so

n/a n/a

/usr/lib/lib_64 n/a n/a libicui18ntd.so->/opt/teradata/client/<version>/tdicu/lib64/libicui18ntd36.0.so

n/a n/a

/usr/lib/lib_64 n/a n/a libicuuctd.so->/opt/teradata/client/<version>/tdicu/lib64/libicuuctd36.0.so

n/a n/a

/usr/lib/lib_64 n/a n/a libicuiotd.so->/opt/teradata/client/<version>/tdicu/lib64/libicuiotd36.0.so

n/a n/a

/usr/lib/lib_64 n/a n/a libiculetd.so->/opt/teradata/client/<version>/tdicu/lib64/libiculetd36.0.so

n/a n/a

/usr/lib/lib_64 n/a n/a libiculxtd.so->/opt/teradata/client/<version>/tdicu/lib64/libiculxtd36.0.so

n/a n/a


Sun Solaris Opteron



/usr/lib/lib_64 n/a n/a libicudatatd36.so->/opt/teradata/client/<version>/tdicu/lib64/libicudatatd36.so

n/a n/a

/usr/lib/lib_64 n/a n/a libicui18ntd36.so->/opt/teradata/client/<version>/tdicu/lib64/libicui18ntd36.so

n/a n/a

/usr/lib/lib_64 n/a n/a libicuuctd36.so->/opt/teradata/client/<version>/tdicu/lib64/libicuuctd36.so

n/a n/a

/usr/lib/lib_64 n/a n/a libicuiotd36.so->/opt/teradata/client/<version>/tdicu/lib64/libicuiotd36.so

n/a n/a

/usr/lib/lib_64 n/a n/a libiculetd36.so->/opt/teradata/client/<version>/tdicu/lib64/libiculetd36.so

n/a n/a

/usr/lib/lib/_4 n/a n/a libiculxtd36.so->/opt/teradata/client/<version>/tdicu/lib64/libiculxtd36.so

n/a n/a


libicudatatd.sl -> libicudatatd.sl.36.0


libicudatatd.so -> libicudatatd36.0.so




libicui18ntd.sl -> libicui18ntd.sl.36.0


libicui18ntd.so -> libicui18ntd36.0.so




libicuuctd.sl -> libicuuctd.sl.36.0


libicuuctd.so->libicuuctd36.0.so




Sun Solaris Opteron




libicuiotd.sl -> libicuiotd.sl.36.0

libicuiotd.so ->libicuiotd.so.36.0

libicuiotd.so ->libicuiotd36.0.so




libiculetd.sl->libiculetd.sl.36.0






libiculxtd.sl->libiculxtd.sl.36.0






libicudatatd.sl.36 -> libicudatatd.sl.36.0

libicudatatd.so .36-> libicudatatd.so.36.0

libicudatatd36.so -> libicudatatd36.0.so




libicui18ntd.sl .36-> libicui18ntd.sl.36.0


libicui18ntd36.so -> libicui18ntd36.0.so




libicuuctd.sl.36 -> libicuuctd.sl.36.0


libicuuctd36.so->libicuuctd36.0.so




libicuiotd.sl.36 -> libicuiotd.sl.36.0

libicuiotd.so ->libicuiotd.so.36.0

libicuiotd36.so ->libicuiotd36.0.so




libiculetd.sl.36->libiculetd.sl.36.0


libiculetd36.so->libiculetd36.0.so




libiculxtd.sl.36->libiculxtd.sl.36.0


libiculxtd36.so->libiculxtd36.0.so




libicudatatd.sl.36.0 libicudatatd.so.36.0

libicudatatd36.0.so




libicui18ntd.sl.36.0 libicui18ntd.so.36.0

libicui18ntd36.0.so




Sun Solaris Opteron



Teradata C Preprocessor2


The following table lists the files and the directories installed for each operating system supported by C Preprocessor2.


libicuuctd.sl.36.0 libicuuctd.so.36.0 libicuuctd36.0.so libicuuctd.so.36.0 libicuuctd.so.36.0


libicuiotd.sl.36.0 libicuiotd.so.36.0 libicuiotd36.0.so libicuiotd.so.36.0 libicuiotd.so.36.0


libiculetd.sl.36.0 libiculetd.so.36.0 libiculetd.so.36.0 libiculetd.so.36.0 libiculetd.so.36.0


libiculxtd.sl.36.0 libiculxtd.so.36.0 libiculxtd.so.36.0 libiculxtd.so.36.0 libiculxtd.so.36.0


Sun Solaris Opteron

Directory HP-UX HP-UX Itanium IBM AIXSun Solaris SPARC

Sun Solaris Opteron

/usr/bin ppcmain* ppcmain* ppcmain* ppcmain* ppcmain*

/usr/lib libppruntim.sl*

libppruntim.so* libppruntim.so* libppruntim.so* libppruntim.so*

/usr/lib/hpux64 n/a libppruntim.so* n/a n/a n/a

/usr/bin/hpux64 n/a ppcmain* n/a n/a n/a

/usr/bin/bin_64 n/a ppcmain* ppcmain* n/a n/a

/usr/lib/lib_64 n/a n/a libppruntim.so* n/a n/a

/usr/bin/pa20_64 ppcmain* n/a n/a n/a n/a

/usr/lib/pa20_64 libppruntim.sl*

n/a n/a n/a n/a

/usr/bin/sparc9 n/a n/a n/a ppcmain* n/a



/usr/lib/sparc9 n/a n/a n/a libppruntim.so* n/a

/usr/bin/amd64 n/a n/a n/a n/a ppcmain*

/usr/lib/amd64 n/a n/a n/a n/a libppruntim.so*


ppcmain ppcmain ppcmain ppcmain ppcmain

/opt/teradata/client/<version>/bin64

ppcmain n/a ppcmain ppcmain ppcmain

/opt/teradata/client/<version>/lib

libppruntim.sl libppruntim.so libppruntim.so libppruntim.so libppruntim.so


libppruntim.sl libppruntim.so libppruntim.so libppruntim.so libppruntim.so


LABSBTEQ LABSBTEQ n/a LABSBTEQ LABSBTEQ


PPCLB1 PPCLB1 PPCLB1 PPCLB1 PPCLB1
















Sun Solaris Opteron





The following table lists the files and the directories installed for each operating system supported by Teradata Call-Leval Interface version 2.




Sun Solaris Opteron


/usr/lib clispb.dat* clispb.dat* clispb.dat* clispb.dat*

/usr/lib errmsg.cat* errmsg.cat* errmsg.cat* errmsg.cat*

/usr/lib errmsg.txt* errmsg.txt errmsg.txt errmsg.txt*

/usr/lib libcliv2.sl* libcliv2.so* libcliv2.so* libcliv2.so*

/usr/lib libtdusr.sl* libtdusr.so* libtdusr.so* libtdusr.so*

/usr/include cliv2if.h* cliv2if.h* cliv2if.h* cliv2if.h*

/usr/include coptypes.h* coptypes.h* coptypes.h* coptypes.h*

/usr/include coperr.h* coperr.h* coperr.h* coperr.h*

/usr/include dbca2px.h* dbca2px.h* dbca2px.h* dbca2px.h*

/usr/include dbcarea.h* dbcarea.h* dbcarea.h* dbcarea.h*

/usr/include dbcerr.h* dbcerr.h* dbcerr.h* dbcerr.h*

/usr/include dbchqep.h* dbchqep.h* dbchqep.h* dbchqep.h*

/usr/include parcel.h* parcel.h* parcel.h* parcel.h*

/usr/include mosiif.h* mosiif.h* mosiif.h* mosiif.h*

/usr/lib/lib_64 n/a libcliv2.so n/a n/a

/usr/lib/lib_64 n/a libtdusr.so n/a n/a

/usr/lib/pa20_64 libcliv2.sl* n/a n/a n/a

/usr/lib/pa20_64 libtdusr.sl* n/a n/a n/a

/usr/lib/sparcv9 n/a n/a libcliv2.so* libcliv2.so*

/usr/lib/sparcv9 n/a n/a libtdusr.so* libtdusr.so*



/usr/lib/lib-i386 n/a n/a n/a n/a

/usr/lib/lib-i386 n/a n/a n/a n/a


libcliv2.sl libcliv2.so libcliv2.so libcliv2.so


libtdusr.sl libtdusr.so libtdusr.so libtdusr.so


errmsg.cat errmsg.cat errmsg.cat errmsg.cat


errmsg.txt errmsg.txt errmsg.txt errmsg.txt


clispb.dat clispb.dat clispb.dat clispb.dat


coptypes.h coptypes.h coptypes.h coptypes.h


dbchqep.h dbchqep.h dbchqep.h dbchqep.h


dbca2px.h dbca2px.h dbca2px.h dbca2px.h


cliv2if.h cliv2if.h cliv2if.h cliv2if.h


coperr.h coperr.h coperr.h coperr.h


dbcarea.h dbcarea.h dbcarea.h dbcarea.h


parcel.h parcel.h parcel.h parcel.h


dbcerr.h dbcerr.h dbcerr.h dbcerr.h


mosiff.h mosiff.h mosiff.h mosiff.h

/opt/teradata/client<version>/lib

errmsg.cat errmsg.cat errmsg.cat errmsg.cat


errmsg.txt errmsg.txt errmsg.txt errmsg.txt


clispb.dat clispb.dat clispb.dat clispb.dat




Teradata COBOL Preprocessor2


The following table lists the files and the directories installed for each operating system supported by Teradata COBOL Preprocessor2.

Directory HP-UX HP-UX Itanium IBM AIX

/usr/bin ppbmain* ppbmain* ppbmain*

/usr/bin/bin_64 n/a n/a ppbmain*

/usr/lib libppruntim.sl* libppruntim.sl* libppruntim.so*

/usr/lib/lib_64 n/a n/a libppruntim.so*

/usr/bin/hpux64 n/a n/a n/a

/usr/lib/hpux64 n/a n/a n/a

/usr/bin/pa20_64 ppbmain ppbmain n/a

/usr/lib/pa20_64 libppruntim.sl libppruntim.sl n/a

/opt/teradata/client/<version>/bin ppbmain ppbmain ppbmain

/opt/teradata/client/<version>/bin64

ppbmain ppbmain ppbmain

/opt/teradata/client/<version>/lib libppruntim.sl libppruntim.sl libppruntim.so


libppruntim.sl libppruntim.sl libppruntim.so


LABSBTEQ LABSBTEQ n/a


PPCOBLB1 PPCOBLB1 PPCOBLB1

/opt/teradata/client/<version>/usr/sample












Teradata Data Connector


The following table lists the files and the directories installed for each operating system supported by Teradata Data Connector.

Teradata FastExport


The following table lists the files and the directories installed for each operating system supported by Teradata FastExport.







Directory HP-UX HP-UX Itanium IBM AIX


/usr/lib libpm.sl* libpm.so* libpm.so* libpm.so*

/usr/include pmdcomt.h* pmdcomt.h* pmdcomt.h* pmdcomt.h*

/usr/include pmddamt.h* pmddamt.h* pmddamt.h* pmddamt.h*

/usr/include pmtypes.h* pmtypes.h* pmtypes.h* pmtypes.h*


libpm.sl libpm.so libpm.so libpm.so


pmdcomt.h pmdcomt.h pmdcomt.h pmdcomt.h


pmddamt.h pmddamt.h pmddamt.h pmddamt.h


pmtypes.h pmtypes.h pmtypes.h pmtypes.h



Teradata FastLoad

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/bin and the /opt/teradata/client/<version>/sample directories.

The following table lists the files and the directories installed for each operating system supported by Teradata FastLoad.


/usr/bin fexp* fexp* fexp* fexp*

/usr/include expnfyxt.h* expnfyxt.h* expnfyxt.h* expnfyxt.h*

/usr/sample expnfyxt.c* expnfyxt.c* expnfyxt.c* expnfyxt.c*

/usr/sample mkexpext.hpux* mkexpext.aix* mkexpext.unx* mkexpext.unx*


fexp fexp fexp fexp


expnfyxt.h expnfyxt.h expnfyxt.h expnfyxt.h


expnfyxt.c expnfyxt.c expnfyxt.c expnfyxt.c


mkexpext.hpux mkexpext.aix mkexpext.unx mkexpext.unx


/usr/bin fastload* fastload* fastload* fastload*

/usr/sample blkexit.c* blexit.c* blkexit.c* blkexit.c*

/usr/sample blkexitr.c* blexitr.c* blkexitr.c* blkexitr.c*

/usr/sample flnfyext.c* flnfyext.c* flnfyext.c* flnfyext.c*


fastload fastload fastload fastload


blkexit.c blexit.c blkexit.c blkexit.c


blkexitr.c blexitr.c blkexitr.c blkexitr.c


flnfyext.c flnfyext.c flnfyext.c flnfyext.c



Teradata Generic Security Services

The files that are included with the TeraGSS package can change from package to package, so there is not a definitive filename list to verify. To verify the installation of the TeraGSS packages, verify the existence of a file named “version” in the /usr/teragss/<architecture>/<version> directory, where: <version> is the version of software that is being verified.

The following table lists the files and the directories installed for each operating system supported by Teradata Generic Security Services.


The following table lists the files and the directories installed for each operating system supported by Teradata JDBC Driver.

Teradata MultiLoad


The following table lists the files and the directories installed for each operating system supported by Teradata MultiLoad.

Platform Package File

HP-UX teragss_hpux-pa /usr/teragss/hpux-pa/<version>

HP-UX teragss_hpux-pa32 /usr/teragss/hpux-pa.32/<version>

HP-UX teragss_hpux-ia64 /usr/teragss/hpux-ia64/<version>

IBM AIX teragss_aix-power /usr/teragss/aix-power/<version>

IBM AIX teragss_aix-power-32 /usr/teragss/aix-power.32/<version>

Sun Solaris SPARC teragss_solaris-sparc /usr/teragss/solaris-sparc/<version>

Sun Solaris SPARC teragss_solaris-sparc32 /usr/teragss/solaris-sparc.32/<version>

Sun Solaris Opteron teragss_solaris-sparc /usr/teragss/solaris-sparc/<version>

Sun Solaris Opteron teragss_solaris-sparc32 /usr/teragss/solaris-sparc.32/<version>


Executable terajdbc4.jar terajdbc4.jar terajdbc4.jar terajdbc4.jar

Sample samples.jar samples.jar samples.jar samples.jar

Security tdgssconfig.jar tdgssconfig.jar tdgssconfig.jar tdgssconfig.jar



Teradata TPump

An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/bin and /opt/teradata/client/<version>/lib directories.

The following table lists the files and the directories installed for each operating system supported by Teradata TPump.


/usr/bin* mload* mload* mload* mload*

/usr/include* mldnfyxt.h* mldnfyxt.h* mldnfyxt.h* mldnfyxt.h*

/usr/sample* mldnfyxt.c* mldnfyxt.c* mldnfyxt.c* mldnfyxt.c*

/usr/sample* mkmldext.hpux* mkmldext.aix* mkmldext.unx* mkmldext.unx*


mload mload mload mload


mldnfyxt.h mldnfyxt.h mldnfyxt.h mldnfyxt.h


mldnfyxt.c mldnfyxt.c mldnfyxt.c mldnfyxt.c


mkmldext.hpux mkmldext.aix mkmldext.unx mkmldext.unx


/usr/bin tpumpexe* tpumpexe* tpumpexe* tpumpexe*

/usr/bin tpump* tpump* tpump* tpump*

/usr/lib tdatpump.cfg* tdatpump.cfg* tdatpump.cfg* tdatpump.cfg*


tpumpexe tpumpexe tpumpexe tpumpexe


tpump tpump tpump tpump


tdatpump.cfg tdatpump.cfg tdatpump.cfg tdatpump.cfg


makinmod.3000 makinmod.3000 makinmod.3000 makinmod.3000


tldnfyxt.c tldnfyxt.c n/a n/a


tpumpimd.c tpumpimd.c tpumpimd.c tpumpimd.c



Teradata Parallel Transporter API


The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter API.


tpumpar.csql tpumpar.csql tpumpar.csql tpumpar.csql


DirectoryHP-UXRisc

HP-UXItanium IBM AIX

Sun Solaris SPARC

Sun Solaris Opteron

<INSTALLDIR>/lib libtelapi.s1

libopcommon.sl

libpxicu.sl

n/a

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

<INSTALLDIR>/lib64 libtelapi.s1

libopcommon.sl

libpxicu.sl

libtelapi.so

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

libtelapi.so

libopcommon.so

libpxicu.so

<INSTALLDIR>/msg opermsgs.cat opermsgs.cat opermsgs.cat opermsgs.cat opermsgs.cat

<INSTALLDIR>/nsg64

opermsgs.cat opermsgs.cat opermsgs.cat opermsgs.cat opermsgs.cat

<INSTALLDIR>/tptapi/inc

connection.h connection.h connection.h connection.h connection.h


DMLGroup.h DMLGroup.h libtelapi.so

libopcommon.so

libpxicu.so

DMLGroup.h DMLGroup.h


schema.h schema.h libtelapi.so

libopcommon.so

libpxicu.so

schema.h schema.h

<INSTALLDIR>/tptapi/sample/inc

connection.h connection.h opermsgs.cat connection.h connection.h


DMLGroup.h DMLGroup.h DMLGroup.h DMLGroup.h DMLGroup.h


schema.h schema.h schema.h schema.h schema.h

<INSTALLDIR>/tptapi/sample/common

OptionsManager.cpp

OptionsManager.cpp

OptionsManager.cpp

OptionsManager.cpp

OptionsManager.cpp

<INSTALLDIR>/tptapi/sample/common

OptionsManager.h

OptionsManager.h OptionsManager.h

OptionsManager.h

OptionsManager.h



<INSTALLDIR>/tptapi/sample/generic

GenericDriver.cpp

GenericDriver.cpp GenericDriver.cpp

GenericDriver.cpp

GenericDriver.cpp


main.cpp main.cpp main.cpp main.cpp main.cpp


input.txt input.txt input.txt input.txt input.txt


infile.bigEndian infile.bigEndian infile.bigEndian infile.littleEndian

infile.littleEndian


makedriver.hpux

makedriver.hpux makedriver.aix makedriver.sol_s makedriver.sol_o


cleanupTables.bteq

cleanupTables.bteq cleanupTables.bteq

cleanupTables.bteq

cleanupTables.bteq


setupTables.bteq setupTables.bteq setupTables.bteq setupTables.bteq setupTables.bteq

<INSTALLDIR>/tptapi/sample/generic/inc

GenericDriver.h GenericDriver.h GenericDriver.h GenericDriver.h GenericDriver.h


BlockLoad.cpp BlockLoad.cpp BlockLoad.cpp BlockLoad.cpp BlockLoad.cpp






infile.bigEndian infile.bigEndian infile.bigEndian infile.bigEndian infile.littleEndian


makeblock.hpux makeblock.hpux makedriver.aix makeblock.sol_s makeblock.sol_o


cleanupTables.bteq


cleanupTables.bteq

cleanupTables.bteq



<INSTALLDIR>/tptapi/sample/blockloading/inc

BlockLoad.h BlockLoad.h BlockLoad.cpp BlockLoad.h BlockLoad.h

DirectoryHP-UXRisc


Sun Solaris SPARC

Sun Solaris Opteron




checkpoint.cpp checkpoint.cpp checkpoint.cpp checkpoint.cpp checkpoint.cpp






infile.bigEndian infile.bigEndian infile.bigEndian infile.bigEndian infile.littleEndian


makecheckpoint.hpux

makecheckpoint.hpux

makeblock.aix makeblock.aix makecheckpoint.sol_o


cleanupTables.bteq


cleanupTables.bteq

cleanupTables.bteq



<INSTALLDIR>/tptapi/sample/checkpoint/inc

checkpoint.h checkpoint.h checkpoint.h checkpoint.h checkpoint.h

<INSTALLDIR>/tptapi/sample/getbuffer

GetBuffer.cpp GetBuffer.cpp GetBuffer.cpp GetBuffer.cpp GetBuffer.cpp






makedriver.hpux

makedriver.hpux makedriver.aix makeblock.sol_s makedriver.sol_o


cleanupTables.bteq


cleanupTables.bteq

cleanupTables.bteq


setupTables.bteq

setupTables.bteq setupTables.bteq setupTables.bteq setupTables.bteq

<INSTALLDIR>/tptapi/sample/getbuffer/inc

GetBuffer.h GetBuffer.h GetBuffer.h GetBuffer.h GetBuffer.h


MultipleOperators.cpp





DirectoryHP-UXRisc


Sun Solaris SPARC

Sun Solaris Opteron








makemultiple.hpux

makemultiple.hpux makemultiple.aix

makemultiple.sol_s

makemultiple.sol_o


cleanupTables.bteq


cleanupTables.bteq

cleanupTables.bteq



<INSTALLDIR>/tptapi/sample/multiple/inc

MultipleOperators.h

MultipleOperators.h MultipleOperators.h

MultipleOperators.h

MultipleOperators.h


multitest.cpp multitest.cpp multitest.cpp multitest.cpp multitest.cpp


synchronize.cpp synchronize.cpp synchronize.cpp synchronize.cpp synchronize.cpp


fileio.cpp fileio.cpp fileio.cpp fileio.cpp fileio.cpp


master.cpp master.cpp master.cpp master.cpp master.cpp


slave.cpp slave.cpp slave.cpp slave.cpp slave.cpp


master_input.txt master_input.txt master_input.txt master_input.txt master_input.txt


slave_input.txt slave_input.txt slave_input.txt slave_input.txt slave_input.txt


infilemaster.bigEndian




infilemaster.littleEndian


infileslave.bigEndian.1




infileslave.littleEndian.1

DirectoryHP-UXRisc


Sun Solaris SPARC

Sun Solaris Opteron




makemulti.hpux makemulti.hpux makemulti.aix makemulti.sol_s makemulti.sol_o


cleanupTables.bteq


cleanupTables.bteq

cleanupTables.bteq



<INSTALLDIR>/tptapi/sample/multi_node/inc

fileio.h fileio.h fileio.h fileio.h fileio.h


multitest.h multitest.h multitest.h multitest.h multitest.h


synchronize.h synchronize.h synchronize.h synchronize.h synchronize.h

<INSTALLDIR>/tptapi/sample/threads

PerfTestMessage.cpp

PerfTestMessage.cpp PerfTestMessage.cpp

PerfTestMessage.cpp

PerfTestMessage.cpp


TelapiThreadTest.cpp






makeparallel.hpux

makeparallel.hpux makeparallel.aix makeparallel.sol_s

makeparallel.sol_s


TestBase.cpp TestBase.cpp TestBase.cpp TestBase.cpp TestBase.cpp


TestExport.cpp TestExport.cpp TestExport.cpp TestExport.cpp TestExport.cpp


TestLoad.cpp TestLoad.cpp TestLoad.cpp TestLoad.cpp TestLoad.cpp


TestSim.cpp TestSim.cpp TestSim.cpp TestSim.cpp TestSim.cpp


TestStream.cpp TestStream.cpp TestStream.cpp TestStream.cpp TestStream.cpp


TestUpdate.cpp TestUpdate.cpp TestUpdate.cpp TestUpdate.cpp TestUpdate.cpp


ThreadTest.cpp ThreadTest.cpp ThreadTest.cpp ThreadTest.cpp ThreadTest.cpp







DirectoryHP-UXRisc


Sun Solaris SPARC

Sun Solaris Opteron




Synchronizer.cpp Synchronizer.cpp Synchronizer.cpp Synchronizer.cpp Synchronizer.cpp




loadData.bigEndian

loadData.bigEndian loadData.bigEndian

loadData.bigEndian

loadData.littleEndian


cleanupTables.bteq


cleanupTables.bteq

cleanupTables.bteq




common.h common.h common.h common.h common.h


PerfTestMessage.h

PerfTestMessage.h PerfTestMessage.h

PerfTestMessage.h

PerfTestMessage.h


TestBase.h TestBase.h TestBase.h TestBase.h TestBase.h


TestExport.h TestExport.h TestExport.h TestExport.h TestExport.h


TestLoad.h TestLoad.h TestLoad.h TestLoad.h TestLoad.h


TestSim.h TestSim.h TestSim.h TestSim.h TestSim.h


TestStream.h TestStream.h TestStream.h TestStream.h TestStream.h


TestUpdate.h TestUpdate.h TestUpdate.h TestUpdate.h TestUpdate.h


ThreadTest.h ThreadTest.h ThreadTest.h ThreadTest.h ThreadTest.h


ThreadTestParameters.h





DirectoryHP-UXRisc


Sun Solaris SPARC

Sun Solaris Opteron





The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Export Operator.



The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Infrastructure.


Synchronizer.h Synchronizer.h Synchronizer.h Synchronizer.h Synchronizer.h

DirectoryHP-UXRisc


Sun Solaris SPARC

Sun Solaris Opteron

DirectoryHP-UXPA-RISC

HP-UXItanium IBM AIX Sun Solaris SPARC

Sun Solaris Opteron

<INSTALLDIR>/lib libexportop.sl n/a libexportop.so libexportop.so libexportop.so

<INSTALLDIR>/lib64

libexportop.sl libexportop.so libexportop.so libexportop.so libexportop.so

<INSTALLDIR>/sample

expnfyxt.c expnfyxt.c expnfyxt.c expnfyxt.c expnfyxt.c

Directory HP-UXHP-UX Itanium IBM AIX

Sun Solaris SPARC

Sun Solaris Opteron

<INSTALLDIR> twbcfg.ini twbcfg.ini twbcfg.ini twbcfg.ini twbcfg.ini

<INSTALLDIR> twboper.ini twboper.ini twboper.ini twboper.ini twboper.ini

<INSTALLDIR> version version version version version

<INSTALLDIR>/bin tbuild tbuild tbuild tbuild tbuild

<INSTALLDIR>/bin tlogview tlogview tlogview tlogview tlogview

<INSTALLDIR>/bin twbkill twbkill twbkill twbkill twbkill

<INSTALLDIR>/bin twbstat twbstat twbstat twbstat twbstat

<INSTALLDIR>/bin ptmgts ptmgts ptmgts ptmgts ptmgts

<INSTALLDIR>/bin ptmtims ptmtims ptmtims ptmtims ptmtims

<INSTALLDIR>/bin ptmexec ptmexec ptmexec ptmexec ptmexec



<INSTALLDIR>/bin ptmjlgr ptmjlgr ptmjlgr ptmjlgr ptmjlgr

<INSTALLDIR>/bin ptmlvs ptmlvs ptmlvs ptmlvs ptmlvs

<INSTALLDIR>/bin coordinator coordinator coordinator coordinator coordinator

<INSTALLDIR>/bin planexecutor planexecutor planexecutor planexecutor planexecutor

<INSTALLDIR>/bin executor executor executor executor executor

<INSTALLDIR>/bin twbpkgrm twbpkgrm twbpkgrm twbpkgrm twbpkgrm

<INSTALLDIR>/bin tbuildexe tbuildexe tbuildexe tbuildexe tbuildexe

<INSTALLDIR>/bin tlogviewexe tlogviewexe tlogviewexe tlogviewexe tlogviewexe

<INSTALLDIR>/bin twbcmdexe twbcmdexe twbcmdexe twbcmdexe twbcmdexe

<INSTALLDIR>/bin twbkillexe twbkillexe twbkillexe twbkillexe twbkillexe

<INSTALLDIR>/bin twbstatexe twbstatexe twbstatexe twbstatexe twbstatexe

<INSTALLDIR>/bin twbrmcpexe twbrmcpexe twbrmcpexe twbrmcpexe twbrmcpexe

<INSTALLDIR>/bin twbpathexe twbpathexe twbpathexe twbpathexe twbpathexe

<INSTALLDIR>/bin tptlaunch tptlaunch tptlaunch tptlaunch tptlaunch

<INSTALLDIR>/bin twbpath twbpath twbpath twbpath twbpath

<INSTALLDIR>/bin twbrmcp twbrmcp twbrmcp twbrmcp twbrmcp

<INSTALLDIR>/bin tdload tdload tdload tdload tdload

<INSTALLDIR>/bin tdlog tdlog tdlog tdlog tdlog

<INSTALLDIR>/bin twbmdlgr twbmdlgr twbmdlgr twbmdlgr twbmdlgr

<INSTALLDIR>/inc pxlogdef.h pxlogdef.h pxlogdef.h pxlogdef.h pxlogdef.h

<INSTALLDIR>/inc pxstc.h pxstc.h pxstc.h pxstc.h pxstc.h

<INSTALLDIR>/inc pxutypes.h pxutypes.h pxutypes.h pxutypes.h pxutypes.h

<INSTALLDIR>/inc pxdtypes.h pxdtypes.h pxdtypes.h pxdtypes.h pxdtypes.h

<INSTALLDIR>/inc pxoper.h pxoper.h pxoper.h pxoper.h pxoper.h

<INSTALLDIR>/inc pxos.h pxos.h pxos.h pxos.h pxos.h

<INSTALLDIR>/inc pxtypes.h pxtypes.h pxtypes.h pxtypes.h pxtypes.h

<INSTALLDIR>/inc pxdef.h pxdef.h pxdef.h pxdef.h pxdef.h

<INSTALLDIR>/inc pxmacros.h pxmacros.h pxmacros.h pxmacros.h pxmacros.h

<INSTALLDIR>/inc pxversion.h pxversion.h pxversion.h pxversion.h pxversion.h

<INSTALLDIR>/lib libpxicu.sl libpxicu.so libpxicu.so libpxicu.so libpxicu.so


Sun Solaris SPARC

Sun Solaris Opteron



<INSTALLDIR>/lib libdataconop.sl libdataconop.so libdataconop.so libdataconop.so libdataconop.so

<INSTALLDIR>/lib libddlop.sl libddlop.so libddlop.so libddlop.so libddlop.so

<INSTALLDIR>/lib libodbcop.sl libodbcop.so libodbcop.so libodbcop.so libodbcop.so

<INSTALLDIR>/lib liboscmdop.sl liboscmdop.so liboscmdop.so liboscmdop.so liboscmdop.so

<INSTALLDIR>/lib libinsertop.sl libinsertop.so libinsertop.so libinsertop.so libinsertop.so

<INSTALLDIR>/lib ibselectop.sl ibselectop.so ibselectop.so ibselectop.so ibselectop.so

<INSTALLDIR>/lib libopcommon.sl libopcommon.so libopcommon.so

libopcommon.so libopcommon.so

<INSTALLDIR>/lib libptmos.sl libptmos.so libptmos.so libptmos.so libptmos.so

<INSTALLDIR>/lib libptmpo.sl libptmpo.so libptmpo.so libptmpo.so libptmpo.so

<INSTALLDIR>/lib libptmpi.sl libptmpi.so libptmpi.so libptmpi.so libptmpi.so

<INSTALLDIR>/lib ibptmpi.a ibptmpi.a libptmpi.a libptmpi.a libptmpi.a

<INSTALLDIR>/lib libptmin.sl libptmin.so n/a libptmin.so libptmin.so

<INSTALLDIR>/lib liblogview.sl liblogview.so liblogview.so liblogview.so liblogview.so

<INSTALLDIR>/lib libpxcommon.sl libpxcommon.so libpxcommon.so

libpxcommon.so libpxcommon.so

<INSTALLDIR>/lib libflimop.sl libflimop.so libflimop.so libflimop.so libflimop.so

<INSTALLDIR>/lib libfeomop.sl libfeomop.so libfeomop.so libfeomop.so libfeomop.so

<INSTALLDIR>/lib libmlimop.sl libmlimop.so libmlimop.so libmlimop.so libmlimop.so

<INSTALLDIR>/lib libtableqry.sl libtableqry.so libtableqry.so libtableqry.so libtableqry.so

<INSTALLDIR>/msg opermsgs.cat opermsgs.cat opermsgs.cat opermsgs.cat opermsgs.cat

<INSTALLDIR>/msg twbmsgs.cat twbmsgs.cat twbmsgs.cat twbmsgs.cat twbmsgs.cat

<INSTALLDIR>/sample/etl GT11.txt GT11.txt GT11.txt GT11.txt GT11.txt









Sun Solaris SPARC

Sun Solaris Opteron





The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Load Operator.



<INSTALLDIR>/sample/etl jobvars.txt jobvars.txt jobvars.txt jobvars.txt sql2.txt

<INSTALLDIR>/sample/metadata

sql1.txt sql1.txt sql1.txt sql1.txt twb_status.txt


sql2.txt sql2.txt sql2.txt sql2.txt twb_targets.txt


twb_status.txt twb_status.txt twb_status.txt twb_status.txt twbpkgrm


twb_targets.txt twb_targets.txt twb_targets.txt twb_targets.txt twbpkg

<INSTALLDIR>/template $STREAM.txt $STREAM.txt $STREAM.txt $STREAM.txt $STREAM.txt

<INSTALLDIR>/template $INSERTER.txt $INSERTER.txt $INSERTER.txt

$INSERTER.txt $INSERTER.txt

<INSTALLDIR>/template $UPDATE.txt $UPDATE.txt $UPDATE.txt $UPDATE.txt $UPDATE.txt

<INSTALLDIR>/template $FILE_READER.txt

$FILE_READER.txt

$FILE_READER.txt

$FILE_READER.txt

$FILE_READER.txt

<INSTALLDIR>/template $LOAD.txt $LOAD.txt $LOAD.txt $LOAD.txt $LOAD.txt

<INSTALLDIR>/template $DATACONNECTOR_PRODUCER.txt





/usr/bin twbpkgrm twbpkgrm twbpkgrm twbpkgrm sql2.txt

/var twbpkg twbpkg twbpkg twbpkg twb_status.txt


Sun Solaris SPARC

Sun Solaris Opteron



Sun Solaris SPARC

Sun Solaris Opteron

<INSTALLDIR>/lib libloadop.sl n/a libloadop.so libloadop.so libloadop.so

<INSTALLDIR>/lib64 libloadop.sl libloadop.so libloadop.so libloadop.so libloadop.so

<INSTALLDIR>/sample ldnfyext.c ldnfyext.c ldnfyext.c ldnfyext.c ldnfyext.c



The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Stream Operator.



The following table lists the files and the directories installed for each operating system supported by Teradata Parallel Transporter Update Operator.


An asterisk (*) after a filename in the following table indicates that it is a “softlink” for files that have been moved to the /opt/teradata/client/<version>/lib and the /opt/teradata/client/<version>/opt directories.

The following table lists the files and the directories installed for Teradata WebSphere MQ Access Module.



Sun Solaris SPARC

Sun Solaris Opteron

<INSTALLDIR>/lib libstreamop.sl n/a libstreamop.so libstreamop.so libstreamop.so

<INSTALLDIR>/lib64 libstreamop.sl libstreamop.so libstreamop.so libstreamop.so libstreamop.so

<INSTALLDIR>/sample

stmnfyxt.c stmnfyxt.c stmnfyxt.c stmnfyxt.c stmnfyxt.c



Sun Solaris SPARC

Sun Solaris Opteron

<INSTALLDIR>/lib libupdateop.sl n/a libupdateop.so libupdateop.so libupdateop.so

<INSTALLDIR>/lib64

libupdateop.sl libupdateop.so libupdateop.so libupdateop.so libupdateop.so

<INSTALLDIR>/sample

updnfyxt.c updnfyxt.c updnfyxt.c updnfyxt.c updnfyxt.c


Sun Solaris Opteron

/usr/lib libmqsc.sl* libupdateop.so libmqsc.so* libmqsc.so*

/usr/lib libmqs.sl* libupdateop.so libmqs.so* libmqs.so*

/opt/teradata/client/<version>/opt

mqaxsmod* updnfyxt.c mqaxsmod* mqaxsmod*


libmqsc.sl libupdateop.so libmqsc.so libmqsc.so




libmqs.sl libupdateop.so libmqs.so libmqs.so

/opt/teradata/client/<version>/opt

mqaxsmod updnfyxt.c mqaxsmod mqaxsmod

/usr/lib/hpux64 libmqs.so* n/a n/a n/a

/usr/lib/hpux64 libmqsc.so* n/a n/a n/a

/opt/teradata/client/<version>/hpux64

libmqs.so n/a n/a n/a

/opt/teradata/client/<version>/hpux64

libmqsc.so n/a n/a n/a


Sun Solaris Opteron


CHAPTER 17

Uninstalling Previous Versions on Linux

This section contains information on uninstalling Teradata Tools and Utilities software on Linux client systems.

Task 1: Uninstall Previous Versions on Linux

Teradata Tools and Utilities Release 13.10


Step 1: Uninstall All Teradata Tools and Utilities Products

A Remove previously installed Teradata Tools and Utilities software option has been added to the main installation menu. Selecting the menu item removes all Teradata Tools and Utilities products, except for Teradata Generic Security Services (TeraGSS).

Procedure - Uninstalling All Teradata Tools and Utilities Products

Follow these steps to uninstall all Teradata Tools and Utilities products.

1 Go to the section on installing Teradata Tools and Utilities. for Linux.

2 Follow the installation procedure to mount the installation CD and run setup.bat.

3 Select the “u” option. This option uninstalls all Teradata Tools and Utilities products from the client.

u. Remove previously installed Teradata Tools and Utilities software

4 Unmount the CD and remove the installation CD from the CD-ROM drive.

Step 2: Uninstall Individual Teradata Tools and Utilities Products

[Optional] Individual products can also be uninstalled from the command line.

Uninstall 32-bit Packages

The following examples illustrate the general format for 32-bit packages with no 64-bit components:

For Red Hat and SUSE Linux:


Chapter 17: Uninstalling Previous Versions on LinuxTask 1: Uninstall Previous Versions on Linux

<packagename>-<version>

For Linux for s390x:

<packagename>-<version>.s390.rpm

For example, to uninstall cliv2 32-bit for Red Hat Linuxenter:

cliv2-13.10.00.00-l.i386.rpm

For example, to uninstall cliv2 32-bit for Linux fors390x enter:

cliv2-13.10.00.00-l.s390.rpm

Uninstall 64-bit Packages

The following examples illustrate the general format for 64-bit packages or 32/64-bit combined packages:


<packagename>-<version>


<packagename>-<version>.s390x .rpm

For example, to uninstall cliv2 64-bit for Red Hat Linuxenter:

cliv2-13.10.00.00-l.i386.rpm

For example, to uninstall cliv2 64-bit for Linux fors390x enter:

cliv2-13.10.00.00-l.s390x.rpm

Package Names

The following table lists the package names required when uninstalling individual products.

PackageRed HatPackage Name/Version

SUSE LinuxPackage Name/Version

Linux for s390xPackage Name/Version

Basic Teradata Query (BTEQ) (32-bit)

bteq-13.10.00.00-1.i386.rpm

bteq-13.10.00.00-1.i386.rpm

bteq-13.10.00.00-l.s390.rpm

Named Pipes Access Module (32-bit)

npaxsmod-13.10.00.00-1.i386.rpm

npaxsmod-13.10.00.00-1.i386.rpm

npaxsmod-13.10.00.00-l.s390.rpm

ODBC Driver for Teradata tdodbc-13.10.00.00-1.noarch.rpm

tdodbc-13.10.00.00-1.noarch.rpm

tdodbc-13.10.00.00-l.s390.rpm

Shared Common Components for Internationalization for Teradata (32-bit and 64-bit)

tdicu-13.10.00.00-1.noarch.rpm

tdicu-13.10.00.00-1.noarch.rpm

tdicu-13.10.00.00-l.s390x.rpm

Teradata Archive and Recovery n/a teradata_arc-13.10.00.00-1.noarch.rpm

n/a

Teradata C Preprocessor2 (32-bit)

sqlpp-13.10.00.00-1.noarch.rpm


sqlpp-13.10.00.00-l.s390x.rpm



Teradata C Preprocessor2 (64-bit)



sqlpp-13.10.00.00-l.s390x.rpm

Teradata Call-level Interface version 2 (CLIv2) (32-bit)

cliv2-13.10.00.00-1.noarch.rpm

cliv2-13.10.00.00-1.noarch.rpm

cliv2-13.10.00.00-l.s390x.rpm


cliv2_64-13.10.00.00-1.noarch.rpm

cliv2_64-13.10.00.00-1.noarch.rpm

cliv2-13.10.00.00-l.s390x.rpm

Teradata Data Connector (32-bit)

piom-13.10.00.00-1.noarch.rpm

piom-13.10.00.00-1.noarch.rpm

piom-13.10.00.00-l.s390.rpm

Teradata FastExport (32-bit) fexp-13.10.00.00-1.i386.rpm

fexp-13.10.00.00-1.i386.rpm

fexp-13.10.00.00-l.s390.rpm

Teradata FastLoad (32-bit) fastld-13.10.00.00-1.i386.rpm

fastld-13.10.00.00-1.i386.rpm

fastld-13.10.00.00-l.s390.rpm

Teradata Generic Security Services (32-bit)

teragss_redhatlinux-i386-13.10.00.00-1.i386.rpm

teragss_suselinux-390.32-13.10.00.00-1.390.32.rpm


teragss_suselinux-i386-13.10.00.00-1.x86_64.rpm

Teragss-390-13.10.00.00-l.390rpm

Teradata MultiLoad (32-bit) mload-13.10.00.00-1.i386.rpm

mload-13.10.00.00-1.i386.rpm

mload-13.10.00.00-l.s390.rpm

Teradata Parallel Transporter API (32-bit)

papida00-13.10.00.00-1.i386.rpm

papi_x8664_da00-13.10.00.00-1.x86_64.rpm

papida00-13.10.00.00-1.i386.rpm

papi_x8664_da00-13.10.00.00-1.x86_64.rpm

papida00-13.10.00.00-l.s390x.rpm

Teradata Parallel Transporter Export Operator (32-bit)

pexpda00-13.10.00.00-1.i386.rpm

pexp_x8664_da00-13.10.00.00-1.x86_64.rpm

pexpda00-13.10.00.00-1.i386.rpm

pexp_x8664_da00-13.10.00.00-1.x86_64.rpm

pexpda00-13.10.00.00-l.s390x.rpm

Teradata Parallel Transporter Infrastructure (32-bit)

tbldda00-13.10.00.00-1.i386.rpm

tbldda00-13.10.00.00-1.i386.rpm

tbldda00-13.10.00.00-l.s390x.rpm

Teradata Parallel Transporter Load Operator (32-bit)

plodda00-13.10.00.00-1.i386.rpm

plod_x8664_da00-13.10.00.00-1.x86_64.rpm

plodda00-13.10.00.00-1.i386.rpm

plod_x8664_da00-13.10.00.00-1.x86_64.rpm

plodda00-13.10.00.00-l.s390x.rpm






Uninstallation Order

If uninstalling individual Teradata Tools and Utilities products other than using the “Remove all...” menu option, they must be uninstalled in the following order:






Uninstall Individual Products - Red Hat Linux

Prior to installing the latest version of Teradata Tools and Utilities, previous versions of Teradata Tools and Utilities products must be uninstalled:

Procedure - Uninstall Individual Teradata Tools and Utilities Software Products

Follow these steps to uninstall previous versions of Teradata Tools and Utilities software on Linux system.

1 Log on as root.

2 List all the installed packages:

# rpm -qa

Or, list individual packages installed:

Teradata Parallel Transporter Stream Operator (32-bit)

pstmda00-13.10.00.00-1.i386.rpm

pstm_x8664_da00-13.10.00.00-1.x86_64.rpm

pstmda00-13.10.00.00-1.i386.rpm

pstm_x8664_da00-13.10.00.00-1.x86_64.rpm

pstmda00-13.10.00.00-l.s390x.rpm

Teradata Parallel Transporter Update Operator (32-bit)

pupdda00-13.10.00.00-1.i386.rpm

pupd_x8664_da00-13.10.00.00-1.x86_64.rpm

pupdda00-13.10.00.00-1.i386.rpm

pupd_x8664_da00-13.10.00.00-1.x86_64.rpm

pupdda00-13.10.00.00-l.s390x.rpm

Teradata Query Director qrydir-13.02.00.00-1.i386.rpm

Teradata TPump (32-bit) tpump-13.10.00.00-l.s390.rpm

tpump-13.10.00.00-l.s390.rpm

tpump-13.10.00.00-l.s390.rpm

Teradata WebSphere MQ Access Module (32-bit)

mqaxsmod-13.10.00.00-l.s390.rpm








# rpm -q <rpmname>

The following table lists the commands to check the versions of installed packages.

PackageRed Hat LinuxCommand

SUSE LinuxCommand

Linux for s390xCommand

Basic Teradata Query (BTEQ) (32-bit)

# rpm -q bteq-13.10.00.00-1.i386.rpm

# rpm -q bteq-13.10.00.00-1.i386.rpm

# rpm -q bteq-13.10.00.00-l.s390.rpm


# rpm -q npaxsmod-13.10.00.00-1.i386.rpm

# rpm -q npaxsmod-13.10.00.00-1.i386.rpm

# rpm -q npaxsmod-13.10.00.00-l.s390.rpm

ODBC Driver for Teradata # rpm -q tdodbc-13.10.00.00-1.noarch.rpm

# rpm -q tdodbc-13.10.00.00-1.noarch.rpm

# rpm -q tdodbc-13.10.00.00-l.s390.rpm


# rpm -q tdicu-13.10.00.00-1.noarch.rpm

# rpm -q tdicu-13.10.00.00-1.noarch.rpm

# rpm -q tdicu-13.10.00.00-l.s390x.rpm

Teradata Archive and Recovery n/a # rpm -q teradata_arc-13.10.00.00-1.noarch.rpm

n/a

Teradata C Preprocessor2 (32-bit) # rpm -q sqlpp-13.10.00.00-1.noarch.rpm

# rpm -q sqlpp-13.10.00.00-1.noarch.rpm

# rpm -q sqlpp-13.10.00.00-l.s390x.rpm

Teradata C Preprocessor2 (64-bit) # rpm -q sqlpp-13.10.00.00-1.noarch.rpm

# rpm -q sqlpp-13.10.00.00-1.noarch.rpm

# rpm -q sqlpp-13.10.00.00-l.s390x.rpm


# rpm -q cliv2-13.10.00.00-1.noarch.rpm


# rpm -q cliv2-13.10.00.00-l.s390x.rpm




# rpm -q cliv2-13.10.00.00-l.s390x.rpm

Teradata Data Connector (32-bit) # rpm -q piom-13.10.00.00-1.noarch.rpm

# rpm -q piom-13.10.00.00-1.noarch.rpm

# rpm -q piom-13.10.00.00-l.s390.rpm

Teradata FastExport (32-bit) # rpm -q fexp-13.10.00.00-1.i386.rpm

# rpm -q fexp-13.10.00.00-1.i386.rpm

# rpm -q fexp-13.10.00.00-l.s390.rpm

Teradata FastLoad (32-bit) # rpm -q fastld-13.10.00.00-1.i386.rpm

# rpm -q fastld-13.10.00.00-1.i386.rpm

# rpm -q fastld-13.10.00.00-l.s390.rpm


# rpm -q teragss_redhatlinux-i386-13.10.00.00-1.i386.rpm

# rpm -q teragss_suselinux-390.32-13.10.00.00-1.390.32.rpm




# rpm -q teragss_suselinux-i386-13.10.00.00-1.x86_64.rpm

# rpm -q Teragss-390-13.10.00.00-l.390rpm

Teradata MultiLoad (32-bit) # rpm -q mload-13.10.00.00-1.i386.rpm

# rpm -q mload-13.10.00.00-1.i386.rpm

# rpm -q mload-13.10.00.00-l.s390.rpm


# rpm -q papida00-13.10.00.00-1.i386.rpm

# rpm -q papi_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q papida00-13.10.00.00-1.i386.rpm

# rpm -q papi_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q papida00-13.10.00.00-l.s390x.rpm


# rpm -q pexpda00-13.10.00.00-1.i386.rpm

# rpm -q pexp_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q pexpda00-13.10.00.00-1.i386.rpm

# rpm -q pexp_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q pexpda00-13.10.00.00-l.s390x.rpm


# rpm -q tbldda00-13.10.00.00-1.i386.rpm

# rpm -q tbldda00-13.10.00.00-1.i386.rpm

# rpm -q tbldda00-13.10.00.00-l.s390x.rpm


# rpm -q plodda00-13.10.00.00-1.i386.rpm

# rpm -q plod_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q plodda00-13.10.00.00-1.i386.rpm

# rpm -q plod_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q plodda00-13.10.00.00-l.s390x.rpm


# rpm -q pstmda00-13.10.00.00-1.i386.rpm

# rpm -q pstm_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q pstmda00-13.10.00.00-1.i386.rpm

# rpm -q pstm_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q pstmda00-13.10.00.00-l.s390x.rpm


# rpm -q pupdda00-13.10.00.00-1.i386.rpm

# rpm -q pupd_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q pupdda00-13.10.00.00-1.i386.rpm

# rpm -q pupd_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -q pupdda00-13.10.00.00-l.s390x.rpm


SUSE LinuxCommand




3 Uninstall individual packages:

# rpm -e <rpmname>

The following table lists the commands to remove individual packages.

Teradata Query Director # rpm -q qrydir-13.02.00.00-1.i386.rpm

Teradata TPump (32-bit) # rpm -q tpump-13.10.00.00-1.i386.rpm

# rpm -q tpump-13.10.00.00-1.i386.rpm

# rpm -q tpump-13.10.00.00-l.s390.rpm


# rpm -q mqaxsmod-13.10.00.00-1.i386.rpm

# rpm -q mqaxsmod-13.10.00.00-1.i386.rpm

# rpm -q mqaxsmod-13.10.00.00-l.s390.rpm


SUSE LinuxCommand



SUSE LinuxCommand


Basic Teradata Query BTEQ (32-bit)

# rpm -e bteq-13.10.00.00-1.i386.rpm

# rpm -e bteq-13.10.00.00-1.i386.rpm

# rpm -e bteq-13.10.00.00-l.s390.rpm


# rpm -e npaxsmod-13.10.00.00-1.i386.rpm

# rpm -e npaxsmod-13.10.00.00-1.i386.rpm

# rpm -e npaxsmod-13.10.00.00-l.s390.rpm

ODBC Driver for Teradata # rpm -e tdodbc-13.10.00.00-1.noarch.rpm

# rpm -e tdodbc-13.10.00.00-1.noarch.rpm

# rpm -e tdodbc-13.10.00.00-l.s390.rpm

Shared Common Components for Internationalization for Teradata (64-bit)

# rpm -e tdicu-13.10.00.00-1.noarch.rpm

# rpm -e tdicu-13.10.00.00-1.noarch.rpm

# rpm -e tdicu-13.10.00.00-l.s390x.rpm

Teradata Archive and Recovery n/a # rpm -e teradata_arc-13.10.00.00-1.noarch.rpm

n/a

Teradata C Preprocessor2 (32-bit) # rpm -e sqlpp-13.10.00.00-1.noarch.rpm

# rpm -e sqlpp-13.10.00.00-1.noarch.rpm

# rpm -e sqlpp-13.10.00.00-l.s390x.rpm

Teradata C Preprocessor2 (64-bit) # rpm -e sqlpp-13.10.00.00-1.noarch.rpm

# rpm -e sqlpp-13.10.00.00-1.noarch.rpm

# rpm -e sqlpp-13.10.00.00-l.s390x.rpm


# rpm -e cliv2-13.10.00.00-1.noarch.rpm


# rpm -e cliv2-13.10.00.00-l.s390x.rpm




# rpm -e cliv2-13.10.00.00-l.s390x.rpm



Teradata Data Connector (32-bit) # rpm -e piom-13.10.00.00-1.noarch.rpm

# rpm -e piom-13.10.00.00-1.noarch.rpm

# rpm -e piom-13.10.00.00-l.s390.rpm

Teradata FastExport (32-bit) # rpm -e fexp-13.10.00.00-1.i386.rpm

# rpm -e fexp-13.10.00.00-1.i386.rpm

# rpm -e fexp-13.10.00.00-l.s390.rpm

Teradata FastLoad (32-bit) # rpm -e fastld-13.10.00.00-1.i386.rpm

# rpm -e fastld-13.10.00.00-1.i386.rpm

# rpm -e fastld-13.10.00.00-l.s390.rpm


# rpm -e teragss_redhatlinux-i386-13.10.00.00-1.i386.rpm

# rpm -e teragss_suselinux-390.32-13.10.00.00-1.390.32.rpm


# rpm -e teragss_suselinux-i386-13.10.00.00-1.x86_64.rpm

# rpm -e Teragss-390-13.10.00.00-l.390rpm

Teradata MultiLoad (32-bit) # rpm -e mload-13.10.00.00-1.i386.rpm

# rpm -e mload-13.10.00.00-1.i386.rpm

# rpm -e mload-13.10.00.00-l.s390.rpm


# rpm -e papida00-13.10.00.00-1.i386.rpm

# rpm -e papi_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e papida00-13.10.00.00-1.i386.rpm

# rpm -e papi_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e papida00-13.10.00.00-l.s390x.rpm


# rpm -e pexpda00-13.10.00.00-1.i386.rpm

# rpm -e pexp_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e pexpda00-13.10.00.00-1.i386.rpm

# rpm -e pexp_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e pexpda00-13.10.00.00-l.s390x.rpm


# rpm -e tbldda00-13.10.00.00-1.i386.rpm

# rpm -e tbldda00-13.10.00.00-1.i386.rpm

# rpm -e tbldda00-13.10.00.00-l.s390x.rpm


# rpm -e plodda00-13.10.00.00-1.i386.rpm

# rpm -e plod_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e plodda00-13.10.00.00-1.i386.rpm

# rpm -e plod_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e plodda00-13.10.00.00-l.s390x.rpm


SUSE LinuxCommand





# rpm -e pstmda00-13.10.00.00-1.i386.rpm

# rpm -e pstm_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e pstmda00-13.10.00.00-1.i386.rpm

# rpm -e pstm_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e pstmda00-13.10.00.00-l.s390x.rpm


# rpm -e pupdda00-13.10.00.00-1.i386.rpm

# rpm -e pupd_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e pupdda00-13.10.00.00-1.i386.rpm

# rpm -e pupd_x8664_da00-13.10.00.00-1.x86_64.rpm

# rpm -e pupdda00-13.10.00.00-l.s390x.rpm

Teradata Query Director # rpm -e qrydir-13.02.00.00-1.i386.rpm

Teradata TPump (32-bit) # rpm -e tpump-13.10.00.00-1.i386.rpm

# rpm -e tpump-13.10.00.00-1.i386.rpm

# rpm -e tpump-13.10.00.00-l.s390.rpm


# rpm -e mqaxsmod-13.10.00.00-1.i386.rpm

# rpm -e mqaxsmod-13.10.00.00-1.i386.rpm

# rpm -e mqaxsmod-13.10.00.00-l.s390.rpm


SUSE LinuxCommand



CHAPTER 18

Uninstalling Previous Versionson UNIX Systems

This section contains information on uninstalling Teradata Tools and Utilities software on UNIX clients.

• Task 1: Uninstall Previous Versions on HP-UX

• Task 2: Uninstall Previous Versions on AIX

• Task 3: Uninstall Previous Versions on SPARC

• Task 4: Uninstall Previous Versions on Opteron

Task 1: Uninstall Previous Versions on HP-UX

Teradata Tools and Utilities Release 13.10


Step 1: Uninstall 64-bit BTEQ on HP-UX

All 64-bit BTEQ packages on UNIX systems have been decommissioned with the exception of HP-UX 11iv2 (64-bit on HP-UX Itanium). The install/upgrade procedure will not automatically remove these decommissioned 64-bit BTEQ packages. Uninstalling a 32-bit BTEQ version will remove a previously installed 64-bit version with the exception of HP-UX 11iv2.


[Optional] A “Remove previously installed Teradata Tools and Utilities software” option has been added to the main install installation menus to remove all Teradata Tools and Utilities products, except for TeraGSS.




Chapter 18: Uninstalling Previous Versions on UNIX SystemsTask 1: Uninstall Previous Versions on HP-UX

1 Go to the section on installing Teradata Tools and Utilities on HP-UX.







Package Names

Package names are required when uninstalling individual products.

Package Package Name

Basic Teradata Query (BTEQ) (32-bit) bteq1310

Named Pipes Access Module (32-bit) npaxsmod1310

ODBC Driver for Teradata tdodbc1310


tdicu1310

Teradata C Preprocessor2 (32-bit and 64-bit) sqlpp1310

Teradata Call-level Interface version 2 (CLIv2) (32-bit and 64-bit)

cliv21310

Teradata COBOL Preprocessor2 (32-bit and 64-bit) cobpp1310

Teradata Data Connector (32-bit) piom1310

Teradata FastExport (32-bit) fexp1310

Teradata FastLoad (32-bit) fastld1310

Teradata Generic Security Services (32-bit and 64-bit) teragss1310

Teradata MultiLoad (32-bit) mload1310

Teradata Parallel Transporter API (32-bit) papida001310

Teradata Parallel Transporter Export Operator (32-bit) pexpda001310

Teradata Parallel Transporter Infrastructure (32-bit) tbldda001310

Teradata Parallel Transporter Load Operator (32-bit) plodda001310

Teradata Parallel Transporter Stream Operator (32-bit) pstmda001310

Teradata Parallel Transporter Update Operator (32-bit) pupdda001310

Teradata Query Director qrydir1310


Chapter 18: Uninstalling Previous Versions on UNIX SystemsTask 1: Uninstall Previous Versions on HP-UX








Uninstall Individual Products - HP-UX



Follow these steps to uninstall previous versions of Teradata Tools and Utilities software installed on HP-UX client systems.

1 Log on as the root user.

2 Prior to installing new versions of the Teradata Tools and Utilities, check for previous versions of the software:

/usr/sbin/swlist

Check to see if an individual package is installed:

/usr/sbin/swlist <PkgName>

3 Uninstall packages:

/usr/sbin/swremove <PkgName>

The utilities packages are uninstalled by repeating the command for each of the packages being uninstalled. The packages can be uninstalled in any order, except for the following dependent packages:

• Data Connector (piom)

• Call-Level Interface version 2 (cliv2)

These packages must be removed last, and in the following order:

• Data Connector (piom)

• Call-Level Interface version 2 (cliv2)

Teradata TPump (32-bit) tpump1310

Teradata WebSphere MQ Access Module (32-bit) mqaxsmod1310



Chapter 18: Uninstalling Previous Versions on UNIX SystemsTask 2: Uninstall Previous Versions on AIX

If, for some reason, the Call-Level Interface version 2 (cliv2) package was mistakenly uninstalled before uninstalling dependent packages first, use swremove with the following options to uninstall CLIv2:

swremove -x enforce_dependencies=false <CLI package name>

Task 2: Uninstall Previous Versions on AIX






1 Go to the section on installing Teradata Tools and Utilities for IBM AIX.







Package Names







tdicu1310


Chapter 18: Uninstalling Previous Versions on UNIX SystemsTask 2: Uninstall Previous Versions on AIX








Uninstall Individual Products - IBM AIX

[Optional] Prior to installing the latest version of Teradata Tools and Utilities, previous versions of Teradata Tools and Utilities products must be uninstalled:


Teradata Call-level Interface version 2 (CLIv2) (32-bit) cliv21310

Teradata COBOL Preprocessor2 (32-bit and 64-bit) cobpp1310

















Chapter 18: Uninstalling Previous Versions on UNIX SystemsTask 3: Uninstall Previous Versions on SPARC


Follow these steps to uninstall previous versions of Teradata Tools and Utilities software installed on IBM AIX client systems.

1 Log on as root user.

2 Prior to installing new versions of Teradata Tools and Utilities check for previous versions of the software by entering:

/usr/bin/lslpp -l

Note: To check for an individual package, use one of the following commands:

lslpp -l <clientPkgName>.<clientPkgName>

or

lslpp -l <clientPkgName>

where: <clientPkgName> is the name of the client package being uninstalled.

For example:

root@stationb: [/] > /usr/bin/lslpp -l bteq.bteq

3 To uninstall a package, enter:

/usr/sbin/installp -u <clientPkgName>

where: <clientPkgName> is the name of the client package being uninstalled.

For example, for cliv2.

root@stationb: [/] > installp -u cliv2

Note: During the installation, software names may become truncated. To find the complete software name, enter one of the following commands at the prompt:

lslpp -l <clientPkgName>.<clientPkgName>

or

lslpp -l <clientPkgName>

Task 3: Uninstall Previous Versions on SPARC


Step 1: Uninstall 64-bit Sun Solaris SPARC ODBC Driver for Teradata

If a previous version of the 64-bit Sun Solaris SPARC ODBC driver was installed, it must be uninstalled before installing the ODBC Driver for Teradata 13.10.00 to avoid unpredictable results.







1 Go to the section on installing Teradata Tools and Utilities for Solaris SPARC.







Determine Package Names







tdicu1310


Teradata Call-level Interface version 2 (CLIv2) (32-bit) cliv21310










Follow Uninstallation Order







Uninstall Individual Products - Sun Solaris SPARC



Follow these steps to uninstall previous versions of Teradata Tools and Utilities software installed on Sun Solaris Sparc operating systems.

1 To determine if there are any existing Teradata Tools and Utilities software packages installed on the client, enter the following command:

# pkginfo -l <name of software>

where: -l uses a lowercase “L”. To check for more than one software package at a time, enter the same command, separated by a space.

For example, to search for Basic Teradata Query (BTEQ), Teradata FastExport and Teradata FastLoad enter:

# pkginfo bteq fastexp fastload...

2 If existing Teradata Tools and Utilities software packages are found, uninstall them:

# pkgrm <name of software>










Chapter 18: Uninstalling Previous Versions on UNIX SystemsTask 4: Uninstall Previous Versions on Opteron

To uninstall more than one software package at a time, enter the same command, separating each package name by a space. For example, to remove Basic Teradata Query (BTEQ), Teradata FastExport and Teradata FastLoad, enter:

# pkgrm bteq fastexp fastload ...

3 Messages appear requesting confirmation before uninstalling the selected software

packages. Answer the questions appropriately.

Task 4: Uninstall Previous Versions on Opteron


Step 1: Uninstall All Products - Sun Solaris Opteron




1 Go to the section on installing Teradata Tools and Utilities for Solaris Opteron.





Step 2: Uninstall Individual Products - Sun Solaris Opteron

[Optional] Individual Teradata Tools and Utilities products can also be uninstalled from the command line using the package names listed in the following table.







Follow the Uninstallation Order









tdicu1310


Teradata Call-level Interface version 2 (CLIv2) (32-bit and 64-bit)

cliv21310



















Follow these steps to uninstall previous versions of Teradata Tools and Utilities software on Sun Solaris Opteron systems.

1 To determine if there are any existing Teradata Tools and Utilities software packages installed on the client, enter the following command:

# pkginfo -l <name of software>

where: -l uses a lowercase “L.”

To check for more than one software package at a time, enter the same command, separated by a space. For example, to search for Basic Teradata Query (BTEQ), Teradata FastExport and Teradata FastLoad enter:

# pkginfo bteq fastexp fastload...

2 If existing software is found, uninstall it using the following command:

# pkgrm <name of software>

To remove more than one software package at a time, enter the same command, separated by a space. For example, to remove Basic Teradata Query (BTEQ), Teradata FastExport and Teradata FastLoad, enter:

# pkgrm bteq fastexp fastload ...

3 Answer the messages which appear requesting confirmation that the selected software

packages were removed.


CHAPTER 19

Installation Kit

The Teradata Tools and Utilities 13.10.00 installation kit contains the documentation and CD media for Teradata Tools and Utilities.

Task 1: Inspect the Installation Kit

The kit includes the following documentation:

• Teradata Tools and Utilities Release Definition, Release 13.10.00

• Teradata Tools and Utilities Documentation CD

Also included are one or more of the following purchased CDs. Each CD contains product versions for one or more network-attached platforms.

• CD#1 - Teradata Utility Pack for Windows - Vol 1 of 3

• CD#2 - Teradata Utility Pack for HP-UX-Linux - Vol 2 of 3

• CD#3 - Teradata Utility Pack for AIX-Solaris - Vol 3 of 3

• CD#4 - Database Management (Windows)

• CD#5 - Preprocessors for Windows - Vol 1 of 3

• CD#6 - Preprocessors for HP-UX-Linux - Vol 2 of 3

• CD#7 - Preprocessors for AIX-Solaris - Vol 3 of 3

• CD#8 - Load/Unload for Windows - Vol 1 of 3

• CD#9 - Load/Unload for HP-UX-Linux - Vol 2 of 3

• CD#10 - Load/Unload for AIX-Solaris - Vol 3 of 3

• CD#11 - Parallel Transporter for Windows - Vol 1 of 3

• CD#12 - Parallel Transporter for HP-UX-Linux - Vol 2 of 3

• CD#13 - Parallel Transporter for AIX-Solaris - Vol 3 of 3

• CD#14 - Query Director Linux-Windows

• CD#15 - Tape Storage Management Enablers (Linux-Windows)

• CD#16 - Meta Data Services (Linux-MPRAS (RSG)-Windows)

If all of the CDs ordered were not received, contact the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC). For information on how to contact TSCS-RSC, refer to the Teradata Tools and Utilities Release Definition, Release 13.10.00.


Chapter 19: Installation KitTask 2: Determine the CD Contents

Task 2: Determine the CD Contents

The following table lists the Teradata Tools and Utilities products and dependencies contained on the Installation Kit CDs. Products indicated in the “W” column can be downloaded from the Teradata Download Center.

Product

Teradata Tools and Utilities CDs

W 1 2 3 4 5 6 7 8 910

11

12

13

14

15

16

Basic Teradata Query x x x x x x x

Meta Data Services Core Files x

• Meta Data Development Kit x

• Meta Surf Files x

• Dim Update Files x

Named Pipes Access Module x x x x x x x x x

.NET Data Provider for Teradata x x

ODBC Driver for Teradata x x x x x x

OLE DB Provider for Teradata x


x x x x x x x x x x x x x x x

Teradata Administrator x

Teradata Archive/Recovery Utility x

Teradata C Preprocessor2 x x x x


x x x x x x x x x x x x x x x x

Teradata COBOL Preprocessor2 x x

Teradata Data Connector x x x x x x x x

Teradata FastExport x x x

Teradata FastLoad x x x

Teradata Generic Security Services x x x x x x x x x x x x x x x

Teradata Index Wizard x

Teradata JDBC Driver x x x x

Teradata MultiLoad x x x

Teradata OLE DB Access Module x



Note: Products that can be Installed from the Teradata Download Center - See Installing from the Teradata Download Center for information on products that can be installed from the Teradata Download Center.

Note: Named Pipes Access Module - The installation of Named Pipes Access Module installs a single version of Named Pipes Access Module that works for both the standalone utilities and Teradata Parallel Transporter.

Note: Teradata WebSphere MQ Access Module - The installation of Teradata WebSphere MQ Access Module installs a single version of Teradata WebSphere MQ Access Module that works for both the standalone utilities and Teradata Parallel Transporter.

Note: Teradata Archive and Recovery Utility - Teradata Archive and Recovery Utility is included to support Teradata’s Backup Applications. Teradata ARC is not sold as an individual standalone product for Windows or SUSE Linux, although it is available as a standalone application on mainframes supported by Teradata.

Teradata Performance Manager x

Teradata Query Director x

Teradata Query Scheduler Administrator

x

Teradata Query Scheduler Client x

Teradata SQL Assistant x

Teradata Statistics Wizard x

Teradata Parallel Transporter(Infrastructure)

x x x

• API x x x

• Export Operator x x x

• Load Operator x x x

• Stream Operator x x x

• Update Operator x x x

Teradata System Emulation Tool x

Teradata Parallel Data Pump x x x

Teradata Visual Explain x

Teradata Workload Analyzer x


x x x x x x

Product

Teradata Tools and Utilities CDs

W 1 2 3 4 5 6 7 8 910

11

12

13

14

15

16



Note: Teradata Parallel Transporter - Teradata Parallel Transporter ICU Library and Operator Support Library are installed as part of the Teradata Parallel Transporter API.

Note: Teradata Parallel Transporter Wizard - Teradata Parallel Transporter Wizard is only supported on Windows.

Note: Teradata Parallel Transporter Operators - Teradata Parallel Transporter ICU Library, Operator Support Library, Data Connector Operator, FastExport OUTMOD Adapter Operator, FastLoad INMOD Adapter Operator, the MultiLoad INMOD Adapter Operator, SQL Inserter Operator, SQL Selector Operator, ODBC Operator, OS Command Operator, DDL Operator, and the Teradata Parallel Transporter Wizard are installed as part of the Teradata Parallel Transporter Infrastructure on Windows.


CHAPTER 20

Product Descriptions

Teradata Tools and Utilities is a set of integrated warehouse management and utility software products designed to operate with the Teradata Database. The utilities enable users to get data from any source; extract and load the data quickly; then analyze the data.

Task 1: Review Product Descriptions

The following table lists descriptions of Teradata Tools and Utilities.

Products Description

Basic Teradata Query A general-purpose, command-based program that allows users on a workstation to communicate with one or more Teradata Database systems, and to format reports for both print and screen output.

Named Pipes Access Module Provides an interprocess communication link between a writer process, such as Teradata FastExport, and a reader process, such as Teradata FastLoad.

ODBC Driver for Teradata Enables UNIX®, Linux® and Microsoft® Windows® operating systems to communicate with the Teradata Database across local area networks (LAN) using the open standards ODBC interface. With the ODBC Driver for Teradata, connect Microsoft Windows, Linux, and UNIX applications to the Teradata Database.

Note: Can be downloaded and installed from the web.


A library of routines based on the IBM International Components for Unicode version 3.6. The library provides unicode support.


Chapter 20: Product DescriptionsTask 1: Review Product Descriptions

Teradata Archive/Recovery Utility Writes and reads sequential files on a Teradata client system to archive, restore, recover, and copy Teradata Database table data. Through its associated script language, it also provides an interface between Teradata’s Backup Applications solutions and the Teradata Database.

Note: Teradata Archive and Recovery Utility (ARC) is included to support Teradata’s Backup Applications. Teradata ARC is not sold as an individual standalone product for Windows,or Linux, although it is available as a standalone application on mainframes supported by Teradata.

Teradata C Preprocessor2 Provides the application programmer with a simplified method of reading and changing information stored in a Teradata Database by interpreting and expanding SQL statements that have been incorporated in an application program.

Teradata Call-Level Interface version 2 A library of routines that enable an application program to access data on a Teradata Database.

Note: Can be download ed and installed from the web.

Teradata COBOL Preprocessor2 Provides the application programmer with a simplified method of reading and changing information stored in a Teradata Database by interpreting and expanding SQL statements that have been incorporated in an application program.

Teradata Data Connector Reads and writes flat files, to provide the input/output interface for access modules.

Teradata FastExport A command-driven utility that uses multiple sessions to quickly transfer large amounts of data from tables and views of the Teradata Database to a client based application.

Teradata FastLoad A command-driven utility that quickly loads large amounts of data to empty tables in a Teradata Database. FastLoad uses multiple sessions to load data; however, it loads data into only one table on a Teradata Database per job.

Teradata Generic Security Services Client

Teradata's implementation of industry-standard Generic Security Services APIs in C language. It provides enhanced security services interfaces between Teradata network clients and Teradata Database.

Teradata JDBC Driver Provides access to the Teradata Database using Java® applications.

Note: Download ed and installed from the web.




Teradata Meta Data Services Teradata Meta Data Services (MDS) provides an infrastructure for managing Teradata active data warehouse metadata and for creating tools to interchange metadata with external operational systems, Extraction Transformation and Load (ETL) tools, Business Intelligence tools, Database Modeling tools, and any other metadata sources.

Teradata MultiLoad Provides an efficient way to deal with batch maintenance of large databases. MultiLoad is a command-driven utility for fast, high-volume maintenance on multiple tables and views of a Teradata Database.

Teradata Parallel Data Pump A data loading utility that helps maintain (update, delete, insert, and atomic upsert) the data in a Teradata Database. TPump uses standard Teradata SQL to achieve moderate to high data loading rates to the Teradata Database. Multiple sessions and multi-statement requests are typically used to increase throughput.

Teradata Parallel Transporter API Teradata Parallel Transporter API is a set of application programming interfaces used to load and export data to and from Teradata Database systems.


Teradata Parallel Transporter Export Operator is a producer operator that emulates the Teradata FastExport utility. It exports large volumes of data at high speed from the Teradata Database to a client by outputting the data to a consumer operator, such as a Load, Update, Stream, or SQL Inserter Operator to load data to a Teradata Database table.

Using the DataConnector Operator as a consumer operator, the data can be written to a flat file, passed to an access module provided by Teradata, or passed to a custom access module created by an end user.


Teradata Parallel Transporter Infrastructure is an object-oriented client application that provides scalable, high-speed, parallel data extraction, loading, and updating.


Teradata Parallel Transporter Load Operator is a consumer operator which functions similar to Teradata FastLoad to load a large volume of data at high speed into an empty table on the Teradata Database.

The operator loads tables into the Teradata Warehouse. Multiple parallel instances can be used to improve the performance of the load.





Teradata Parallel Transporter Stream Operator is a consumer operator that emulates the Teradata Parallel Data Pump utility to perform high-speed DML transactions (SQL INSERT, UPDATE, DELETE, or UPSERT) in a near-real-time mode to a table (or tables) while queries are performed on the table (or tables).


Teradata Parallel Transporter Update Operator is a consumer operator that emulates the Teradata MultiLoad utility to load a large volume of data at high speed into up to five tables on the Teradata Database. Use this operator to maintain tables in the Teradata Warehouse.

Teradata WebSphere® MQ Access Module

Allows Teradata utilities to import data using IBM® WebSphere MQ message queuing middleware.



CHAPTER 21

Product Dependencies

The following table lists the dependent products which must be installed to support Teradata Tools and Utilities products installed. Unless otherwise specified, all Teradata Tools and Utilities products and dependencies are version 13.10.00 or later.

Task 1: Review Product Dependencies

The following table lists dependencies of Teradata Tools and Utilities.

Products Dependent Products

Basic Teradata Query Teradata Tools and Utilities Dependencies



• Teradata Generic Security Services (teragss)


Third-party Dependencies

• No third-party dependencies

Named Pipes Access Module Teradata Tools and Utilities Dependencies

• No Teradata Tools and Utilities dependencies


• No third-party dependencies

ODBC Driver for Teradata Teradata Tools and Utilities Dependencies


• Teradata Generic Security Services TeraGSS - Client package


• Microsoft Data Access Components (MDAC), version 2.8 SP1 (on distribution CD)

Required for Windows 2000 only.


Chapter 21: Product DependenciesTask 1: Review Product Dependencies


Teradata Tools and Utilities Dependencies

• No dependencies


• For AIX: IBM XL C/C++ Compiler v9.0 (runtime libraries fileset xlC.rte v9.x.x.x) or later

Teradata Archive/Recovery Utility Teradata Tools and Utilities Dependencies


• Teradata Generic Security ServicesTeraGSS - Client package




• No dependencies

Teradata C Preprocessor2 Teradata Tools and Utilities Dependencies





• No dependencies

Teradata Call-Level Interface version 2 Teradata Tools and Utilities Dependencies

• Teradata Generic Security Services (TeraGSS - Client package)



• No dependencies

Teradata COBOL Preprocessor2 Teradata Tools and Utilities Dependencies





• No dependencies




Teradata Data Connector Teradata Tools and Utilities Dependencies

• No dependencies


• No dependencies

Teradata FastExport Teradata Tools and Utilities Dependencies






• No dependencies

Teradata FastLoad Teradata Tools and Utilities Dependencies






• No dependencies

Teradata Generic Security Services Client


• No dependencies


• No dependencies

Teradata JDBC Driver Teradata Tools and Utilities Dependencies

• No dependencies



• JDK 5.0 is certified for Windows 32-bit

• JDK 5.0 is certified for Windows XP Professional x64 using EM64T

• JDK 6.0 is certified for Windows 64-bit




Teradata Meta Data Services Teradata Tools and Utilities Dependencies





• See Teradata Meta Data Services documentation

• Java Runtime Environment 1.5.0 or later (32-bit)

Teradata MultiLoad Teradata Tools and Utilities Dependencies






• No dependencies

Teradata Parallel Data Pump Teradata Tools and Utilities Dependencies






• No dependencies

Teradata Parallel Transporter API Teradata Tools and Utilities Dependencies





• No dependencies









• (Optional) Teradata Parallel Transporter Infrastructure(for Teradata Parallel Transporter job script users.)

• (Optional) Teradata Parallel Transporter API(for Teradata Parallel Transporter API users.)


• No dependencies








Note: The environment can be downloaded from the Sun website at: http://java.sun.com/products/archive









• No dependencies





Note: Teradata Parallel Transporter version 13.10.00 is certified with Teradata Call-Level Interface version 2 release 13.10.00.

Note: The installation of Teradata Parallel Transporter Infrastructure installs the following software:


• Teradata Parallel Transporter ICU Library

• Teradata Parallel Transporter Operator Support Library

• Teradata Parallel Transporter Data Connector Operator

• Teradata Parallel Transporter DDL Operator

• Teradata Parallel Transporter FastExport OUTMOD Adapter Operator

• Teradata Parallel Transporter FastLoad INMOD Adapter Operator

• Teradata Parallel Transporter MultiLoad INMOD Adapter Operator









• No dependencies









• No dependencies

Teradata WebSphere® MQ Access Module




• IBM WebSphere MQ V5.2



Chapter 21: Product DependenciesTask 2: Installing Dependencies

• Teradata Parallel Transporter ODBC Operator

• Teradata Parallel Transporter OS Command Operator

• Teradata Parallel Transporter SQL Inserter Operator

• Teradata Parallel Transporter SQL Selector Operator

• Teradata Parallel Transporter Wizard

Note: The installation of Teradata Parallel Transporter API installs the following software:


• Teradata Parallel Transporter ICU Library

• Teradata Parallel Transporter Operator Support Library

Task 2: Installing Dependencies

The Teradata Tools and Utilities installation can automatically install dependent products. If a dependent product already exists on the client system for one of the following products, the installation will display one of two messages.

• Product Already Installed, Version the Same - The first message appears if a product is already installed, and its version is the same as the product being installed. For example, the following message is for the ODBC Driver for Teradata:

"ODBC Driver for Teradata 13.10.00.00 is already installed.Do you want to reinstall it?"

• Product Already Installed, Version Different - The second message appears if a product is already installed and its version is not equal to the product being installed. For example, the following message is for the ODBC Driver for Teradata:

"ODBC Driver for Teradata 13.00.00 is already installed. Do you want to overwrite it with version 13.10.00?"


Chapter 21: Product DependenciesTask 2: Installing Dependencies


CHAPTER 22

System Requirements

This section lists the minimum system requirements for installing the Teradata Tools and Utilities software on UNIX and Linux systems.

Task 1: Determine System Requirements

Step 1: Determine Platforms Supported

Teradata Tools and Utilities software is packaged to install and run on systems or nodes supporting one of these operating systems:

• Red Hat Linux

• SUSE Linux

• Linux for s390x

• HP-UX

• HP-UX Itanium

• IBM AIX

• Sun Solaris SPARC

• Sun Solaris Opteron

Teradata Tools and Utilities 13.10.00 Supported Versions spreadsheet lists the Teradata Tools and Utilities products for this release and the operating system versions where they run.

Step 2: Use the Korn Shell

When installing on UNIX system, use the Korn shell (/bin/ksh) before running the installation procedure for Teradata Tools and Utilities. This will ensure correct execution of the installation script.

Step 3: Determine Network Requirements

Red Hat Linux uses the Transmission Control Protocol/Internet Protocol (TCP/IP) to communicate with the Teradata Database.

The client must be connected to one of the following:

• The same Ethernet LAN as the Teradata Database

• An Ethernet LAN that permits the client to communicate with the Teradata Database through one or more routers


Chapter 22: System RequirementsTask 1: Determine System Requirements

• A node that is attached to the Teradata Database through Ynet™ or BYNET®. No separate network controller board or network software is required; the client provides its own

Step 4: Determine Teradata Database Requirements

On every Teradata Database with which the client communicates, the appropriate Ethernet hardware and software supporting a TCP/IP based network must be installed.


CHAPTER 23

Installation Recommendations

This section provides recommendations for installing Teradata Tools and Utilities software on client systems.

Task 1: Determine Recommendations

Before beginning the installation of Teradata Tools and Utilities software on an Red Hat Linux client systems, verify that the software package ordered is complete (see Installation Kit) and that the client systems where the software will be installed are setup with the required software and hardware. If the correct disks were not received, contact the TSCS-RSC.

Recommendation 1: Uninstall Previous Versions

Teradata Tools and Utilities Release 13.00.00 required that all products except for Teradata Generic Security Services (TeraGSS) be uninstalled before installing the new release. See Recommendation 4: Install Teradata Generic Security Services.

With Teradata Tools and Utilities Release 13.10.00, all products in the release except for Teradata Generic Security Services (TeraGSS) uninstall previous versions of Teradata Tools and Utilities products.

Optionally, existing versions of Teradata Tools and Utilities products can be uninstalled prior to installing Release 13.10.00. All existing Teradata Tools and Utilities, except for TeraGSS can be uninstalled from an option on the installation menu, and TeraGSS and other individual products can be uninstalled individually from the command line. See Uninstalling Previous Versions on Linux for more information.

Recommendation 2: Install Upgrade or Maintenance Software

Teradata notifies existing customers whenever software upgrades, higher-level releases, or maintenance releases occur. Upgrades are normally available on CD-ROM, or can be downloaded and installed from the Teradata Download Center.

The Teradata Download Center is located at:

http://www.teradata.com/resources/drivers-udfs-and-toolbox

Online updates to individual Teradata Tools and Utilities software packages are sometimes made available on the Teradata Software Server. These upgrades or software patches can be downloaded by authorized customers, or Teradata field support personnel with access to the Teradata Software Server.


http://www.teradata.com

http://www.teradata.com/resources/drivers-udfs-and-toolbox

Chapter 23: Installation RecommendationsTask 1: Determine Recommendations

The Teradata Software Server is located at:


Note: To re-install a previous version of the software, the original Teradata Tools and Utilities disk must be used.

Note: Normally, network parameters should not have to be reset after making an upgrade.

Note: If new directories for the files are created, change the paths to COPERR, COPLIB, and COPANOMLOG. For more information, see Troubleshooting the Installation.

Recommendation 3: Install Dependent Products

The Teradata Tools and Utilities installation will automatically install dependent products if the main install is used. See Product Dependencies.

Recommendation 4: Install Teradata Generic Security Services

Since it may not be practical to install or upgrade all parts of a system to the latest version of the Teradata Generic Security Services at one time, multiple versions of the software can be installed on the system at the same time. See Installing Individual Products, Teradata Generic Security Services for more information.

Recommendation 5: Upgrade TPump

On Linux operating systems, if TPump is being updated from a TPump version prior to 02.02.00.00, the soft link /usr/bin/tpump will be missing after the upgrade. See Installing Individual Products, Teradata Parallel Pump for more information.

Recommendation 6: Upgrade C/COBOL Preprocessor2

The default installation location for Teradata C Preprocessor2 (sqlp) and Teradata COBOL Preprocessor2 (cobpp) on all UNIX platforms has changed to /opt/teradata/client/<version>. See Installing Individual Products, Teradata C/COBOL Preprocessor2 for more information.



CHAPTER 24

Security and Connectingto a Teradata Database

This section contains procedures and describes how to connect to a Teradata Database.

Note: The figures shown in this document are examples only. Depending on the Teradata Tools and Utilities products used in your installation, some dialogs might vary from those shown in this guide.

Task 1: Make the Database Connection

This section describes:

• How to connect to a Teradata Database from a GUI application.

• How to connect to a Teradata Database from a command line application.

• Where to find the information to programmatically connect to a Teradata Database.

For programmatic interfaces, the User or Reference guide for the specific product provides information about the product interface.

Step 1: Review Logon Procedures

The logon string can be provided while logging on to a Teradata Database if the application allows it. If the application does not provide all the logon information, a Connect to Teradata Database dialog appears that allows entry of the missing logon information.

Note: If the environment variable GUILOGON is set to NO, the Connect to Teradata Database dialog box does not open, allowing the application to log on to the Teradata Database without prompting for the password.

If the Connect to Teradata Database dialog appears, all application-provided parameters are automatically entered into the dialog fields. If the information is incorrect, you can change the value entered in any field. After entering required and optional logon information press Enter or click OK to continue logging on.

The user logon exit routine can be used to manipulate the fields of the Connect to Teradata Database dialog.

Step 2: Connect To a Teradata Database from a GUI Application

This section contains the procedure to connect to a Teradata Database using the Connect to Teradata Database dialog from a Graphical User Interface (GUI) application. The procedure is


Chapter 24: Security and Connecting to a Teradata DatabaseTask 1: Make the Database Connection

for a typical application. The dialog for each product may and do vary in appearance and the fields that it requires. See the product User or Reference guide for specific information about an individual product.

Procedure - Connecting to a Teradata Database

To connect to a Teradata Database, perform the following procedure:

1 If the application connecting to the database has a Connectivity tab in the Tools options menu, select WinCLI or ODBC.

2 Click the Connect button. The Connect to Teradata Database dialog appears.

3 Select or enter the appropriate values for the database.

4 Click OK.

Connect to Teradata Database Dialog

The following figure shows the Connect to Teradata Database dialog:

The following table describes the fields in the Connect to Teradata Database dialog:

Field Name Definition

Database Name (Required) Enter a valid Teradata Database name, or select a Teradata Database Name that was previously entered from the drop down list. This is the name of the database to connect.



Note: Even though the UserId and Password parameters are required to log on to the Teradata Database, entry into the Connect to Teradata Database dialog is not required since they will be filled in by the user logon exit routine.

Authentication Mechanism

(Required) Select the authentication mechanism specified by the client system administrator from the list of authentication mechanisms provided in the drop down list. The Authentication Mechanism identifies the mechanism used for connections to the data source.

Valid authentication mechanism values are:

• Empty - If no Authentication Mechanism is listed in the drop down list, or if the Authentication Mechanism selected is not supported, the mechanism used is the system default

• TD1 - Teradata 1 mechanism


• ldap - ldap mechanism

• KRB5 - Kerberos mechanism

• KRB5C - Kerberos Compatibility mechanism

• SPNEGO - Simple and Protected GSSAPI Negotiation Mechanism

• NTLM - NT LAN Manager mechanism

• NTLMC - NT LAN Manager Compatibility mechanism

• Other - user-defined mechanism

Note: For new installations, TD1, KRB5C and NTLM mechanisms were disabled as of Teradata Tools and Utilities 12.00.00 in both the TdgssLibraryConfigFile.xml and TdgssUserLibraryConfigFile.xml files. Users with existing versions of TdgssLibraryConfigFile.xml and TdgssUserLibraryConfigFile.xml are unaffected. New installations must explicitly enable the TD1, KRBC5 or NTLM mechanisms to use them. See the Security Administration documentation for more information.

Authentication Parameter

(Optional) Enter the parameters required by the selected authentication mechanism. See your System Administrator.

User Name (Required) Select your user name from the drop down list, or enter a valid user name.

Password (Required) Enter your Password for the user name you entered.

Default Database (Optional) Select the default database for the session.

Account String (Optional) Enter a new Account String or select an account string from the drop down list.

The Account String is used to create a user in a Teradata Database, instead of providing account information during configuration of ODBC. It allows Teradata to isolate users, to find out what applications users are running, or to restrict users trying to connect to the database.

Field Name Definition



Step 3: Connect to a Teradata Database from Command Line Driven Applications

This section contains procedures and describes how to connect to a Teradata Database from the command line.

Procedure - Connecting from Command Line Driven Applications

Follow these steps to connect to a Teradata Database from the command line.

1 Enter the .logmech command.

2 Enter the .logdata command.

3 Enter the .logon command.

Use the .logmech Command

The .logmech command identifies the desired logon authentication mechanism (logmech_name_string). The logmech_name_string is limited to 8 bytes and is not case-sensitive.

The syntax for the .logmech command is:

.logmech logmech_name_string

The logmech_name_string supports the following values

• None - If no Authentication Mechanism is entered, or if the Authentication Mechanism selected is not supported, the system will default to TD2



• LDAP - ldap mechanism

• KRB5 - Kerberos mechanism

• KRB5C - Kerberos Compatibility mechanism

• SPNEGO - Simple and Protected GSSAPI Negotiation Mechanism

• NTLM - NT LAN Manager mechanism

• NTLMC - NT LAN Manager Compatibility mechanism

Use the .logdata Command

To successfully authenticate the user, the .logdata command provides all the parameters needed by the authentication mechanism, other than a UserId and Password. The information is entered into and passed by the logdata_string. The logdata_string is limited to 64K bytes.

The syntax for the .logdata command is:

.logdata logdata_string;

If the logdata_string has white space characters or the other special characters embedded, the entire logdata string must be delimited with single quotes:

.logdata ‘logdata_string’;



The exact contents of the logdata_string will vary according to the selected authentication mechanism. The string is not displayed, parsed, nor otherwise processed by the application.

Use the .logon Command

The syntax for the .logon command is:

.logon <DBCName></><UserId><,><Password><,><AccountId>

where:

Example 1: Example Logons from the Command Line

Supported Mechanisms

In general, mechanisms which perform authentication and validation do not require that a Teradata Database Username and Password be included as part of the logon string. If these items are provided in conjunction with an authentication mechanism, they are ignored.

The following table describes the supported mechanisms.

Parameter Definition

DBCName (Required) The DBCName is also referred to as the TDIPD (Teradata Director Program ID). It identifies a particular Teradata Database.

If no identifier is specified, the value of this field is copied from the clispb.dat field, i_dbcpat.

DBCName is not case sensitive.

UserId (Required) The UserId or user name string can be up to 30 characters long. The first character cannot be a numeric character. The UserId is not case sensitive.

Password (Required) The Password string can be up to 30 characters long. The first character cannot be a numeric character. In the dialog box, each character of the Password is displayed with an asterisk (*). The Password is not case sensitive.

AccountId (Optional) - The AccountId is required only if there is a comma after the Password field. The first character cannot be a numeric character. Do not enter the single quote (') that normally surrounds an AccountId. The AccountId is not case sensitive.

Mechanism Mechanism Parameter User ID Password

Td1 Never (disabled in Teradata Tools and Utilities 12.00.00)

Must (disabled in Teradata Tools and Utilities 12.00.00)

Must (disabled in Teradata Tools and Utilities 12.00.00)

Td2 Never Must Must

KRB5 Optional Never Never



The following authentication mechanisms are supported:

Kerberos Examples

In all environments that support Kerberos, a UserId, Password, and a Domain or a Realm can be provided. The Domain or Realm must be supplied separately as authentication mechanism data.

Once the user’s identity has been verified by Kerberos, an implicit logon proceeds using the tendered UserId as the Teradata Username:

.logmech KRB5

.logdata joe@domain1@@mypassword

.logon mydbs/

For single-Domain environments, the gateway can be configured so that the Domain or Realm do not need to be supplied:

.logmech KRB5

.logdata joe@@mypassword

.logon mydbs/

Alternatively, a Kerberos-mediated SSO-style logon can be used by omitting either the UserId, Password and a Domain or a Realm. In this case, Kerberos uses the security credentials associated with the current client session:

.logmech KRB5

.logon mydbs/

If required, Teradata accounting information may be included as part of .logon command as follows:

.logmech KRB5


.logon mydbs/,,2345889909

or

.logmech KRB5



or

.logmech KRB5


KRB5C Optional (disabled in Teradata Tools and Utilities 12.00.00)

Never (disabled in Teradata Tools and Utilities 12.00.00)

Never (disabled in Teradata Tools and Utilities 12.00.00)

SPNEGO Optional Never Never

LDAP Must Never Never

Mechanism Mechanism Parameter User ID Password



In all of the cases above, a Teradata Username must be defined in the target Teradata Database that matches the actual or derived UserId. Further, the Username must have previously been granted the “logon with null password privilege.”

Note: The special “dbc” username cannot be used with Kerberos authentication mechanism since “dbc” cannot be granted the “logon with null password privilege.” If the “dbc” username is passed, the Teradata Database will return error 3790.

KRB5C Examples

The KRB5C mechanism is maintained for compatibility purposes with Teradata Tools and Utilities 8.1 communicating with a pre-V2R6 Teradata Database that supports SSO and logon encryption. It should not generally be specified.

The teraSSO library will automatically determine the appropriate authentication mechanism when interfacing to such a Teradata Database using the same logic as employed in Teradata Tools and Utilities 7.1.

• Windows clients should use NTLMC or KRB5C for SSO

• For non-SSO, Windows clients use TD1

• Non-Windows clients should use TD1

In the event a user manually selects an incompatible mechanism, TERASSO_SECPKGMATCH_FAIL is returned.

SPNEGO

Teradata Database employs the Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) to provide confidentiality and integrity while supporting non-LDAP external authentication for users logging on to Teradata Database through Windows .NET applications. The SPNEGO mechanism functions almost identically to the KRB5 mechanism, except that KRB5 cannot be used in a Windows .Net environment. See “Kerberos Examples” on page 274.

The KRB5 and NTLM mechanisms should be used for legacy installations prior to Release 13.00.00.

Note: SPNEGO requires the download of .NET Framework.

NTLM Examples

The NTLM authentication mechanism should be used in Windows-to-Windows environments only. A UserId, Password, and Domain can be provided. Once the user’s identity has been verified by NTLM, an implicit logon will proceed using the tendered UserId as the Teradata Username.

.logmech NTLM

.logdata joe@domain1@@mypasswordjoe

.logon mydbs/

For single-Domain environments, the gateway can be configured so that the Domain or Realm need not be indicated:

.logmech NTLM

.logdata joe@@mypasswordjoe



.logon mydbs/

Alternatively, an NTLM-mediated SSO-style logon can be used by omitting the UserId, Domain, and Password, or omitting the UserId, Password, and either the Domain or the Realm.

In this second case, NTLM uses the security credentials associated with the current client session:

.logmech NTLM

.logon mydbs/

If required, Teradata accounting information can be provided as part of .logon command as follows:

.logmech NTLM



or

.logmech NTLM



or

.logmech NTLM


In all of the above cases, a Teradata Username defined in the target Teradata Database must exist. The Username must match the actual or derived UserId and must have previously been granted the “logon with null password privilege. “

Note: The special “dbc” username cannot be used with the NTLM authentication mechanism since “dbc” cannot be granted the “logon with null password privilege.” If “dbc” is passed as the username, the Teradata Database will return error 3790.

For compatibility purposes, this is equivalent to the existing SSO feature. The existing third-party sign-on variant of SSO (NTLM only) is supported for compatibility purposes. However, it is recommended that new applications should use the logmech_name, logmech_data_ptr, and logmech_data_len fields in DBCAREA instead.

NTLMC Examples

The NTLMC authentication mechanism is maintained for compatibility purposes only for Teradata Tools and Utilities 8.1 communication with a pre-V2R6 Teradata Database that supports SSO and logon encryption. Generally, do not specify the NTLMC authentication mechanism.

The teraSSO library automatically determines the appropriate mechanism when interfacing to a Teradata Database, and uses the same logic as employed in Teradata Tools and Utilities 7.1.

• Windows clients should use NTLMC or KRB5C for SSO.

• For non-SSO, Windows clients should use TD1.

• Non-Windows clients should use TD1.



In the event a user manually selects an incompatible mechanism, TERASSO_SECPKGMATCH_FAIL will be returned.

LDAP Examples

The LDAP authentication mechanism allows a user to be authenticated via LDAP and, optionally, to assume a role or user identity other than his or her own, as allowed by the appropriate directory settings.

The user may supply a UserId, Password, and Domain or Realm. The exact contents of the LDAP .logdata information necessarily depends largely upon how the site is using LDAP, and how LDAP has been configured. The samples below are generic examples. Once the user’s identity has been verified by LDAP, an implicit logon will proceed using the UserId as the Teradata username:

.logmech LDAP

.logdata domain7authcid=joe password=password real=myrealm

.logon mydbs/joe,password

If required, Teradata accounting information may be included as part of .logon command as follows:

.logmech LDAP

.logdata authcid=joe password=password real=myrealm


If the directory maps the UserId to a specific Teradata Username, that Username must be defined in the target Teradata Database and must have previously been granted the “logon with null password privilege.”

Once the user’s identity has been verified by LDAP, an implicit logon will proceed using the tendered UserId as the Teradata Username.

Note: The special “dbc” Username cannot be used with the LDAP authentication mechanism since “dbc” cannot be granted the “logon with null password privilege.” If “dbc” is used as the username, the Teradata Database will return error 3790.

If the directory does not map the UserId to a specific Teradata Username, a generic username will be used and a role assigned. The role will be derived from information contained in the directory. Logon will be by extended logon.

.logdata information must always be provided for the LDAP authentication mechanism.

TD1 and TD2 Examples

TD1 and TD2 represent the Teradata mechanisms. They do not perform any authentication. Rather, they facilitate encryption/decryption for sessions connected absent the mediation of extended security. Therefore, a valid Teradata Username and Password are always required.

• Only TD1 is used by Teradata Tools and Utilities 7.1.

• TD2 is used by Teradata Tools and Utilities 8.0 and later for the V2R6.0 Teradata Database and later.

• TD1 is used by Teradata Tools and Utilities 8.0 and above for the V2R5.1 Teradata Database.



The difference between the two mechanisms is that the encryption key for TD2 is longer and, therefore, offers a higher degree of security than that of TD1. For TD2, there should be no .logdata parameter; if one is passed to CLIv2, it will be ignored.

TD2 is the default mechanism for the server-based XML configuration file:

.logmech TD2

.logon mydbs/rhh,password

TD1 Examples

TD1 is a deprecated mechanism used by Teradata Tools and Utilities 7.1. It is also used by Teradata Tools and Utilities 8.0 when communicating with a V2R5.x Teradata Database. The difference between the two mechanisms is that the encryption key for TD2 is longer and, therefore, offers a higher degree of security than that of TD1.

The TD1 authentication mechanism is maintained for compatibility purposes only for Teradata Tools and Utilities 8.0 communication with a V2R5.x Teradata Database. Generally, it should not be specified.

The teraSSO library automatically determines the appropriate mechanism when interfacing to a V2R5.x Teradata Database, using the same logic as used in Teradata Tools and Utilities 7.1.

• Windows clients should use NTLMC or KRB5C for SSO

• For non-SSO, Windows clients should use TD1

In the event a user manually selects an incompatible mechanism, TERASSO_SECPKGMATCH_FAIL will be returned.

Step 4: Review Single Sign-On Legacy Considerations

The following table lists single sign-on legacy considerations in order to provide backward compatibility with pre-Teradata Tools and Utilities 8.0 applications which use SSO, the following items apply.



Step 5: Connect to a Teradata Database Programmatically

Several Teradata Tools and Utilities products that allow a programmatic connection to the Teradata Database using SQL and APIs.

The following table lists products that allow a programmatic connection to the Teradata Database using SQL and APIs.

Type Description

Direct sign-on If a Username and Password are not supplied as part of the Teradata logon string,

AND

no authentication mechanism name is specified in .logmech, the client interface will not use the default mechanism.

Rather, it will first determine if the Kerberos mechanism is available. If the Kerberos authentication mechanism is available, the client interface will use it.

If the Kerberos interface is not available, the client interface will next determine if the NTLM authentication mechanism is available. If the NTLM authentication mechanism is available, it will use it.

If neither the NTLM nor the Kerberos authentication mechanism is available, the logon attempt will fail.

If .logmech is specified, and the authentication mechanism turns out to be different from the one automatically determined by the client interface, an error will be returned.

Third-party sign-on If an application uses the programmatic third-party sign-on capability using the CLIv2 DBCAREA extension

AND

no authentication mechanism name is specified in logmech_name, the client interface will not use the default authentication mechanism.

Rather, the client interface will first determine if the Kerberos authentication mechanism is available. If the Kerberos authentication mechanism is available, the client interface will use it.

If the Kerberos authentication mechanism is not available, the client interface will next determine if the NTLM authentication mechanism is available. If the NTLM authentication mechanism is available, it will use it.

If neither the NTLM nor the Kerberos authentication method is available, the logon attempt will fail.

If .logmech is specified, and the authentication mechanism turns out to be different from the one automatically determined by the client interface, an error will be returned.



Step 6: Check Logon Error Messages

The following table lists error messages which apply to the logon and database connection function.

Product Document

ODBC Driver for Teradata ODBC Driver for Teradata User Guide.

Describes SQL Connect, SQLDriverConnect, and SQLBrowseConnect and the parameters implemented for security. Includes information on configuring the ODBC Driver for Teradata.

OLE DB Provider for Teradata OLE DB Provider for Teradata Installation and User Guide.

Describes the security implemented for the OLE DB Provider for Teradata.

Teradata Call-Level Interface version 2 (CLIv2)

Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems.

Describes the CLI APIs implemented for security.

Teradata JDBC Driver Teradata JDBC Driver User Guide.

Describes the security methods implemented for the type 4 driver and illustrates how to connect to the Teradata Database using the Teradata JDBC Driver.

Error Message

UTY1652 Logon mechanism is not supported in the version of CLI.

Explanation: The user specified an option that needs to use the logon authentication mechanism feature but this feature is not supported in the version of CLI.

Generated by: UTYMSG

Remedy: Remove specified logon mechanism options.

UTY6668 Invalid use of the .LOGMECH statement.

Explanation: It is invalid to specify the .LOGMECH statement after the .LOGON statement.


Remedy: Remove the invalid statement and resubmit the program.

UTY6669 Invalid use of the .LOGDATA statement.

Explanation: It is invalid to specify the .LOGDATA statement after the .LOGON statement.


Remedy: Remove the invalid statement and resubmit the program.



Step 7: Reselect Authentication Mechanism on Connection Error

If there is an error in the authentication mechanism selected, “External authentication is not currently allowed” may appear.

If this message, is received an incorrect authentication mechanism has been selected. Reselect it using the authentication mechanism provided by the database administrator and try to connect again.

UTY6670 A .LOGMECH statement has been previously specified, terminating.

Explanation: A .LOGMECH statement has already been processed.


Remedy: Remove the extra statement and resubmit the program.

UTY6671 A .LOGDATA statement has been previously specified, terminating.

Explanation: A .LOGDATA statement has already been processed.


Remedy: Remove the extra statement and resubmit the program.

Error Message


CHAPTER 25


This section includes tips on troubleshooting the Teradata Tools and Utilities installation.

Task 1: Troubleshoot Client Computer Problems

To troubleshoot a problem with your client, perform the following checks. You may not need to try all of them.

Problem 1: Cannot Communicate Over the Network with Teradata Database

To confirm that a UNIX client or Linux client can communicate over the network to a Teradata Database, ping the Teradata Database:

/usr/etc/ping dbcnameCOPn

The following response is returned:

dbcnameCOPn is alive

To perform the second test to verify communication to the Teradata Database, enter:

telnet dbcnameCOPn

The following response is returned:

telnet: connect: Connection refused

If these responses are not received, consult the next section, “Task 2: Troubleshoot Network Problems.”

Note: dbcnameCOPn can appear in upper or lower case.

Problem 2: Incorrect Path Name in COPLIB

Check that the environment variable COPLIB has the correct path name to the CLI system parameter block file, clispb.dat.

COPLIB is set to /usr/lib in the /etc/profile file during the installation of the software.

Use the following command to define COPLIB:

• Bourne shell users, add the following to the .profile file:

COPLIB=/sd;export COPL


Chapter 25: Troubleshooting the InstallationTask 1: Troubleshoot Client Computer Problems

• C shell users, add the following to the .login file:

setenv COPLIB /sd

where: sd (source directory) is the name of the directory you created to receive the object library, the system parameter block file, and the executable files.

Run the .profile or .login file after making changes to these files.

Problem 3: Incorrect Path Name in COPERR

If the error message, “No such error found” appears, check that the environment variable COPERR has the correct path name to the error message catalog file, errmsg.cat.

Use the following command to define COPERR:

• Bourne shell users, add the following to the .profile file:

COPERR=/ed;export COPERR

• C shell users, add to the .login file:

setenv COPERR /ed

where: ed (error directory) is the name of the directory created to contain the error message catalog file.

Run the .profile or .login file after making changes to these files.

Problem 4: errmsg.cat File Not Found

If the error message, “CLI: Message catalog open failed!, the file errmsg.cat cannot be opened. There may be problems with your installation,” the errmsg.cat file cannot be found.

This error is displayed when the errmsg.cat file is not found in the directory specified in the environment variable COPERR or /usr/lib.

Set the COPERR environment variable to the directory where the errmsg.cat is present, /usr/lib.

Problem 5: Incorrect Path Name in COPANOMLOG

To produce an anomaly log file, check that the environment variable COPANOMLOG has the correct path name to the anomaly log file.

Problem 6: Missing Hosts File

Check that the /etc/hosts file exists on the UNIX client or Linux client.

Problem 7: Incorrect Entries in the Hosts File

Check the following entries in the /etc/hosts file or in the hosts file on the NIS master:

• Check all entries for incorrect, missing, or duplicate network addresses of COPs, APs or nodes.


Chapter 25: Troubleshooting the InstallationTask 2: Troubleshoot Network Problems

Remember that a TCP/IP (Internet) address is a 4-byte value in the form a.b.c.d. COPs, APs or nodes on the same logical network must have the same network Id portion of the network address.

• Check that COPs, APs or nodes in the same group for a Teradata have the same dbcname, and that they are numbered sequentially, starting with 1.

Remember that the format of a COP name is dbcnameCOPn, where dbcname must begin with an alphabetic character.

Problem 8: Missing Entries in the /etc/services File

Check for the following lines in the /etc/services file or in the services file on the NIS master:

tdmst 1025/udptdses 1025/tcp

Problem 9: Improper Linking

Check that the software files are linked properly with your application.

If maintenance or upgrade software is installed, all applications must be relinked.

Problem 10: Incorrect clispb.dat Parameters

Check parameters in the system parameter block file, clispb.dat, for correct values.

Note whether the default i_dbcpath corresponds to the dbcnames in the /etc/hosts file or in the hosts file on the NIS master.

Problem 11: Cannot Log On from CLI Application

If the Teradata Database cannot be logged onto from a CLI application, try logging on from BTEQ.

If BTEQ works, then check the application for errors.

Problem 12: Cannot Log On to the Teradata Database

If a Teradata Database cannot be logged onto, try logging on to a different database computer.

If the logon succeeds, then there may be something wrong with the first Teradata Database, or something wrong with the address of the first database computer in the /etc/hosts file, or in the hosts file on the NIS master.

Task 2: Troubleshoot Network Problems

If there is a network problem, the following procedure can be used to troubleshoot whether the problem exists with network hardware or software. All of the steps are not required.


Chapter 25: Troubleshooting the InstallationTask 3: Troubleshoot Teradata Database Problems

Procedure - Determining whether a Network Problem is a Hardware/Software Problem

Follow these steps to determine if a network problem is related to hardware or software.

1 Check that the transceiver is connected to the network, UNIX or Linux client, and Teradata Database.

2 Check for broken or disconnected network cables.

3 Check that drop cables are not too long (they must follow the IEEE 802.3 standards).

4 Check all repeaters, bridges, routers, and gateways for proper functioning.

5 Check that all jumpers are setup correctly on the UNIX client or Linux client's network controller board.

6 Check that the network software is installed and running properly on the UNIX client or Linux client.

7 Check that the network software is compatible with the network controller board installed on the UNIX client or Linux client.

8 Use a network utility program to confirm that the network is operational.

9 Use BTEQ or a network utility program from another UNIX client or Linux client on the same network segment as the first UNIX client or Linux client. If this works, there may be a problem with the first UNIX client or Linux client.

10 Use BTEQ or a network utility program from another UNIX client or Linux client on a different network segment from the first UNIX client or Linux client.

If this works, there may be a problem with the first network segment.

11 If a network controller board is replaced on the UNIX client or Linux client, the Teradata Database must be rebooted so that it can obtain the network address of the new board.

12 If the network configuration was changed, check that all network related files were changed accordingly (see the previous section).

13 Reboot the UNIX client or Linux client to reset network hardware and reload network software.

Task 3: Troubleshoot Teradata Database Problems

Caution: Teradata Database problems should be diagnosed with the assistance of a field service representative.

To determine whether the Teradata Database is operating correctly, use the following procedure.

Note: Steps 2 through 7 apply to the Teradata Database only.


Chapter 25: Troubleshooting the InstallationTask 3: Troubleshoot Teradata Database Problems

Procedure - Determining whether there is a Database Problem

Follow these steps to determine if there is a problem with the Teradata Database.

1 Log on to the database computer from the operator's console, another network-attached host, or a mainframe. If a logon succeeds, the Teradata Database is operational. If unable to log on, contact a field representative.

2 Have a field representative check that the adaptor cable is connected.

3 Have a field representative check the Multibus Adaptor Board (MAB).

4 Perform the following tests for all entries in the CopInfoTbl (on the Teradata Database):

• Check for incorrect, missing, or duplicate cabinet and processor numbers (ccc_p).

• Check for incorrect, missing, or duplicate network addresses.

• Check for the correct network protocol type (CopKind) for each COP.

• Check for the correct host number for each COP, AP, or node.

• Check that the entries in the CopInfoTbl match the entries in the /etc/hosts file (on the UNIX client or Linux client) or in the hosts file on the NIS master.

Use the CopUpdate macro to change the CopInfoTbl.

5 If a COP, AP, or node is added or removed from the Teradata Database or a COP's network address is changed, the CopUpdate macro must be executed so that the Teradata Database can determine changes to network addresses. The Teradata Database must be restarted before the changes can take effect.

6 If using Internet routing (routers), perform the following tests for the CopRoutesTbl:

• Check for incorrect or missing network addresses of destinations.

• Check for incorrect or missing network addresses of routes.

• Check that each router is identified by two (or more) Internet addresses, one for each network on which it resides.

Use the TcpRoute macro to change the CopRoutesTbl.

7 If a subnet outing (subnetting) is used, check the CopOptionsTbl for incorrect or missing subnet masks. Use the AddOption macro to change the CopOptionsTbl.

8 If the Teradata Database goes down and then comes back up, its table of sessions still contains information about the sessions generated by hosts. The Teradata Database expects to receive reconnect messages from hosts. If the Teradata Database does not get the reconnect messages within 20 minutes after it comes back up, it removes from the sessions table the sessions that were generated by hosts that have not reconnected.

The above implies that for 20 minutes after the Teradata Database comes back up, some sessions are being kept that may not be used. If use of the Teradata Database is heavy, users unable to log on during that 20 minute period (because the maximum number of sessions has been reached) can try again after the unclaimed sessions are cleared away.


Chapter 25: Troubleshooting the InstallationTask 4: Troubleshoot Teradata Parallel Transporter Problems

Task 4: Troubleshoot Teradata Parallel Transporter Problems

At the end of the Teradata Parallel Transporter Infrastructure installation, the Teradata Parallel Transporter Infrastructure installation updates some environment variables on the system.

Updates to the environment variables are effective in the next logon. The updates to this environment variables allow users to run the installed version of Teradata Parallel Transporter.

If users do not use the updates to the environment variables, the installed version of Teradata Parallel Transporter does not run correctly.

Problem 1: Unable to Find tbuild

Sometimes the path to tbuild cannot be found. Use the following procedure to locate the file.

Procedure - Finding the Path to tbuild

Follow these steps to find the path to tbuild:

1 Logout from the system and log back in. Then run the Teradata Parallel Transporter job again.

2 If still unable to find tbuild, check that the $TWB_ROOT/bin path is in your PATH environment variable. The TWB_ROOT environment variable is set to the installation directory for Teradata Parallel Transporter.

3 If the $TWB_ROOT/bin path is not in the PATH environment variable, then add the $TWB_ROOT/bin path to the front of the PATH environment variable. Run the Teradata Parallel Transporter job again.

Problem 2: Cannot Run the New Installed Version of Teradata Parallel Transporter

If the new installed version of Teradata Parallel Transporter does not run.

Procedure - Setting the TWB_ROOT Environment Variable

Follow these steps to setup the TWB_ROOT environment variable if Teradata Parallel Transporter does not run.

1 Logout from the system and log back in. Run the Teradata Parallel Transporter job again.

2 If you are still unable to run the new installed version of Teradata Parallel Transporter, check the $TWB_ROOT/bin path is in the PATH environment variable. TWB_ROOT is the environment variable that is set to the installation directory for Teradata Parallel Transporter.



3 If the $TWB_ROOT/bin path is not in the PATH environment variable, then add the $TWB_ROOT/bin path to the front of the PATH environment variable. Run the Teradata Parallel Transporter job again.

Problem 3: Failed to Load libpxcommon Library

If a message similar to the following error message appears when executing a Teradata Parallel Transporter job, logout the system and log back in.

ld.so.1: tbuild: fatal: libpxcommon.so: open failed: No such file or directory Killed

Then run the Teradata Parallel Transporter job again.

Procedure - Loading the libpxcommon Library

Follow these steps to load the libpxcommon library and correct problems causing the fatal error shown above.

1 On AIX, the error message still appears, check the $TWB_ROOT/lib path is in the LIBPATH environment variable. TWB_ROOT is the environment variable that is set to the installation directory for Teradata Parallel Transporter.

If the $TWB_ROOT/lib path is not in theLIBPATH environment variable, then add the $TWB_ROOT/lib path to the front of the LIBPATH environment variable. Run the Teradata Parallel Transporter job again.

2 On HP-UX, the error message still appears, check the $TWB_ROOT/lib path is in the SHLIB_PATH environment variable. TWB_ROOT is the environment variable that is set to the installation directory for Teradata Parallel Transporter.

If the $TWB_ROOT/lib path is not in the SHLIB_PATH environment variable, then add the $TWB_ROOT/lib path to the front of the SHLIB_PATH environment variable. Run the Teradata Parallel Transporter job again.

3 On Linux and Solaris, the error message still appears, check the $TWB_ROOT/lib path is in the LD_LIBRARY_PATH environment variable. TWB_ROOT is the environment variable that is set to the installation directory for Teradata Parallel Transporter.

If the $TWB_ROOT/lib path is not in the LD_LIBRARY_PATH environment variable, then add the $TWB_ROOT/lib path to the front of the LD_LIBRARY_PATH environment variable. Run the Teradata Parallel Transporter job again.

Problem 4: Unable to Find Messages

If the following error messages appears when executing a Teradata Parallel Transporter job, logout of the system and log back in. Then, run the Teradata Parallel Transporter job again.

Message Catalog Error: Message 4000 was not foundMessage Catalog Error: Message 2014 was not foundMessage Catalog Error: Message 2041 was not found



Procedure - Finding Missing Messages

Follow these step to find missing messages.

1 If the error messages still appears, check the $TWB_ROOT/msg/%N path is in your NLSPATH environment variable. TWB_ROOT is the environment variable that is set to the installation directory for Teradata Parallel Transporter.

2 If the $TWB_ROOT/msg/%N path is not in the NLSPATH environment variable, then add the $TWB_ROOT/msg/%N path to the NLSPATH environment variable. Afterwards, run the Teradata Parallel Transporter job again.

Problem 5: Unable to Find Messages on AIX

When the LANG and LC__FASTMSG environment variables are setup to “C” and “true”, respectively, the following messages will appear after running a Teradata Parallel Transporter job using the “tbuild” command:

Message Catalog Error: Message 4000 was not found

Message Catalog Error: Message 2007 was not found

Use one of the following action to solve the error messages”

• Change the value for the LANG environment variable to “en_US”

• Change the value for the LC__FASTMSG environment variable to “false”

Then, re-run the Teradata Parallel Transporter job.


CHAPTER 26

Session Limits

This section lists Teradata session limits for BTEQ and for the entire system.

Task 1: Determine BTEQ Session Limits

The maximum number of BTEQ sessions depends on the host used. BTEQ session limits for Red Hat Linux clients are listed in the following table:

Task 2: Determine System-Wide Session Limits

The maximum number of sessions that can be logged on concurrently to a Teradata Database (through BTEQ or other CLI applications) depends on a system's configuration, including the following:

• Host type

• Protocol used

• Type of host-resident network controller board

• Number of COPs, APs, or nodes installed on a Teradata Database, and

• Whether any other network applications are running, such as the Telnet or FTP utilities, or any user-written applications.

The following table lists the session guidelines for Red Hat Linux clients.

Session Type Maximum Sessions

BTEQ 200


System-wide 64, for single COP group

64 * (# of COPS -1) where number of COPs is > 1.

System-wide for Version 1 (V1) AP systems (for example, 3600)

300 * Number of APs


Chapter 26: Session LimitsTask 2: Determine System-Wide Session Limits

Caution: These are guidelines only. The optimum number of sessions for any system depends on the site's configuration and tuning.

System-wide for Version 2 (V2) “Common Node” systems

600 * Number of Nodes



CHAPTER 27

Technical Assistance

This section provides information on how to get technical assistance for Teradata Tools and Utilities products.

Task 1: Getting Technical Assistance

Technical assistance during installation of the Teradata Tools and Utilities software is available from the TSCS-RSC. For contact information, see the Teradata Tools and Utilities Release Definition, Release 13.10.00.


Chapter 27: Technical AssistanceTask 1: Getting Technical Assistance


Index

Symbols/etc/services File 285

Numerics64-bit Executable

files 145, 15064-bit Library

files 145, 150

Aadhoc 162, 189, 192adhoc.c 162, 189, 192adhoc.cpp 162, 189, 192aix.includes 190, 193alternate directories 145, 150ARC

dependencies 254, 258arcmain.exe 167authentication mechanism 271Automatic DIM Update

action processorstarting/stopping 99

action processor packageinstalling

on Linux 90and RSG 86, 88DDL Gateway 76, 86

database connection information 87installing

/etc/services file 92server 89starting/stopping 99user accounts 87

DDL Gateway packageinstalling

on Linux 90MDS Action Processor 76, 87

installingodbc.ini file 90, 91

MDS Recovery Table 88nodes

configuring 94processes 86, 88RSG

configuration file

Linux 93UNIX systems 93

installing/etc/services file 93

installing on Linux 92installing on UNIX systems 92starting/stopping 94

BBasic Teradata Query (BTEQ)

verifying 160blexitr 212blexitr.c 212blkexit.c 171, 212blkexitr.c 171, 172, 212BlockLoad.cpp 216BTEQ

dependencies 253, 257bteq 160, 186

exiting 156session limits 291verifying 160verifying installation with 155

btnfyext.c 160, 186btnfyext.h 186

Ccheckpoint.h 175cleanupTables.bteq 175, 176, 177, 178, 216, 217CLI User Exit Functions

installing 69, 70, 71CliLgn.Ex.c 170CliPPS.c 170clisamp.c 170clispb.dat 168, 208, 209, 285cliv2 168cliv2if.h 169, 208, 209command-line syntax

mdsconfig 81common.h 178common.includes 162, 189, 190, 192, 193configuring

requirementsnetwork 265

Teradata Parallel Transporter 116, 124, 129, 133, 139connection.h 215


Index

coordinator 222COPANOMLOG 284COPERR 284coperr.h 169, 208, 209coptypes.h 169, 208, 209

DData Definition Language See DDLdatabase information metamodel SeeDIMDataConnector Operator

dependencies 255dbca2px.h 169, 208, 209dbcarea.h 169, 208, 209dbcerr.h 169, 208, 209dbchqep.h 169, 208, 209dconndlg.sl 189, 192DDL Gateway

Automatic DIM Update 76uninstalling on Linux 78

defaultdirectories 150

directoriesalternate 145, 150default 145, 150

DMLGroup.h 215

Eenvironment variables, setting 114errmsg.cat 168, 208, 209, 284errmsg.txt 168, 208, 209error.c 162, 189, 192error.cpp 162, 190, 193executable files, default directory 145, 150executor 222expnfyxt.c 171, 179, 212expnfyxt.h 171, 212

Ffastexp 171fastld 171fastload 171, 212fexp 171, 212fileio.cpp 177fileio.h 177flnfyext.c 171, 172

GGenericDriver.cpp 176, 216GenericDriver.h 176, 216GetBuffer.cpp 176GetBuffer.h 176

GT11.txt 223GT44.txt 223GT62.txt 223GT93.txt 223GT94.txt 223GT95.txt 223GT96.txt 223GT97.txt 223

HHosts File 284

Iibselectop.sl 223ibselectop.so 223includes files, default directory 145, 150infile.bigEndian 216, 217infile.littleEndian 175, 176infilemaster.littleEndian 177infileslave.littleEndian.1 177Infrastructure 179, 221input.exp 176input.lod 176input.stm 176input.txt 175, 176, 178, 216input.upd 176installing

alternate directories 145, 150default directories 145, 150maintenance software 267pre-installation considerations 265Teradata client 40upgrades 267verifying using bteq 155verifying using CLI sample program 157

Jjobvars.txt 181, 224

LLABSBTEQ 168, 207, 210ldnfyext.c 224libcliv2.sl 209libcliv2.sl* 208libcliv2.so 168, 169, 208libcliv2.so* 169, 208libdataconop.sl 223libdataconop.so 223libddlop.sl 223libddlop.so 223libexportop.sl 221


Index

libexportop.so 179, 221libfeomop.sl 223libfeomop.so 223libflimop.sl 223libflimop.so 223libicudatatd.sl 204, 205libicudatatd.sl.36.0 205libicudatatd.so 194, 195, 196, 204, 205libicudatatd.so.36 162, 163, 166libicudatatd.so.36.0 164, 166, 205libicudatatd36.0.so 203, 204, 205libicui18ntd.sl 194, 195, 196, 204, 205libicui18ntd.sl.36.0 205libicui18ntd.so 194, 195, 204, 205libicui18ntd.so.36 162, 163, 166libicui18ntd.so.36.0 164, 166, 205libicui18ntd36.0.so 203, 204, 205libicuiotd.sl 194, 195, 196, 205libicuiotd.sl.36.0 206libicuiotd.so 194, 195, 205libicuiotd.so.36 163, 164, 166libicuiotd.so.36.0 164, 167, 206libicuiotd36.0.so 203, 204, 206libiculetd.sl.36.0 205, 206libiculetd.so.36.0 164, 166, 167, 203, 204, 205, 206libiculxtd.so.36.0 164, 166, 167, 203, 204, 205, 206libicuuctd.sl 194, 195, 196, 204, 205libicuuctd.sl.36.0 206libicuuctd.so 194, 195, 204, 205libicuuctd.so.36 163, 164, 166libicuuctd.so.36.0 164, 167, 206libicuuctd36.0.so 203, 204, 206libinsertop.sl 223libinsertop.so 223libloadop.sl 224libloadop.so 224liblogview.sl 223liblogview.so 223libmlimop.sl 223libmlimop.so 223libmqs.sl 226libmqsc.so 183, 225libodbc.so 161libodbcinst.so 161libodbcop.sl 223libodbcop.so 223libopcommon.sl 215, 223libopcommon.so 174, 215, 223liboscmdop.sl 223liboscmdop.so 223libpm.sl 211libpm.sl* 211libpm.so 170, 211libppb.a 210

libppruntim.sl 206, 207, 210libppruntim.so 168, 206, 207, 210libptmin.sl 223libptmin.so 223libptmos.sl 223libptmos.so 223libptmpi.a 223libptmpi.sl 223libptmpi.so 223libptmpo.sl 223libptmpo.so 223libpxcommon.sl 223libpxcommon.so 223libpxicu.sl 215, 222libpxicu.so 174, 215, 222library files, default directory 145, 150libstreamop.so 182, 225libtdparse.so 161, 189, 191libtdusr.sl 209libtdusr.sl* 208libtdusr.so 169, 208libtdusr.so* 169, 208libtelapi.s1 215libtelapi.so 215libupdateop.so 182, 225, 226loadData.littleEndian 178logon

dialog box 269procedures 269

Mmain.cpp 175, 176, 216maintenance software, installing 267makeblock.aix 217makeblock.hpux 216makeblock.linux 175makeblock.linux_390 175makeblock.sol_o 216makeblock.sol_s 216, 217makecheckpoint.hpux 217makecheckpoint.linux 175makecheckpoint.linux_390 175makecheckpoint.sol_o 217makedriver.aix 216, 217makedriver.hpux 216, 217makedriver.linux 175, 176makedriver.linux_390 175, 176makedriver.sol_o 216, 217makedriver.sol_s 216Makefile 162, 189, 190, 192, 193makemulti.linux 177makemulti.linux_390 177makemultiple.aix 218


Index

makemultiple.hpux 218makemultiple.linux 176makemultiple.linux_390 176makemultiple.sol_o 218makemultiple.sol_s 218makeparallel.linux 177makeparallel.linux_390 177makerdusr.lx 170makerdusr.lx64 170makesamp.lx 170makesamp.lx64 170makinmod.3000 173, 214master.cpp 177master_input.txt 177MDS

base packagedescription 80

core filesMetaBrowse 76MetaManager 76

development kit 76, 80installation prerequisites 74

ASP compliant server 75database size 75Teradata database 75Teradata user account 75Windows workstation 75

installingon Linux 79

repositorycreating

on Linux 82migrating

on Linux 82setting configuration parameters

on Linux 81uninstalling

on Linux 77MDS Action Processor

Automatic DIM Update 76mdsconfig

command-line syntax 81metacreate

MDS repositiorycreating on Linux 82

MetaManagernodes

adding 95MetaSurf

ASP compliant web server 74virtual directory 83

metaviews 75mkbtnfyext.aix 186mkbtnfyext.hpux 186

mkbtnfyext.hpux-ia64 186mkbtnfyext.linux 160mkexpext.aix 212mkexpext.aix* 212mkexpext.hpux 212mkexpext.hpux* 212mkexpext.linux 171mkexpext.unx 212mkexpext.unx* 212mkmldext.aix 214mkmldext.aix* 214mkmldext.hpux 214mkmldext.hpux* 214mkmldext.linux 173mkmldext.linux-390.32 173mkmldext.unx 214mkmldext.unx* 214mldnfyxt.c 173, 214mldnfyxt.h 173, 214mload 173, 214mosiff.h 209mosiif.h 169, 208mqaxsmod 225, 226MultipleOperators.cpp 176MultipleOperators.h 176multitest.cpp 176multitest.h 177

NNamed Pipes Access Module

dependencies 253, 257verifying 160, 186

nodesadding 95configuring for Automatic DIM Update 94

np_axsmod.sl 186np_axsmod.so 186

OODBC Driver for Teradata

dependencies 253, 257Solaris packages 228, 231, 233, 238, 240, 243, 245

ODBC DSNconfiguring

on Linux 75odbc.ini 161odbc.ini file 80, 113

Automatic DIM UpdateMDS Action Processor 90, 91

odbc.m 162, 189, 192odbccurs.so 161odbcinst.h 161, 188, 191odbcinst.ini 161


Index

odbctrac.so 161open database connectivity See ODBCopermsgs.cat 174, 181, 215, 223OptionsManager.cpp 215OptionsManager.h 215OptionsReader.cpp 176OptionsReader.h 176

Pparcel.h 169, 208, 209PerfTestMessage.cpp 177PerfTestMessage.h 178pexp8100 178piom 170pkginfo command 244, 247pkgrm command 244, 247planexecutor 222plod8200 181pmdcomt.h 170, 211pmddamt.h 170, 211pmtypes.h 170, 171, 211ppbmain 210PPCLB1 168, 207PPCLB2 168, 207PPCLB3 168, 207PPCLB4 168, 207PPCLB5 168, 207PPCLB6 168, 207PPCLB7 168, 207PPCLB8 168, 207PPCLB9 168, 208ppcmain 168, 206, 207PPCOBLB1 210PPCOBLB2 210PPCOBLB3 210PPCOBLB4 210PPCOBLB5 210PPCOBLB6 210PPCOBLB7 211PPCOBLB8 211PPCOBLB9 211Preprocessor

dependencies 254, 258product version numbers 3pstm8200 182ptmexec 221ptmgts 221ptmjlgr 222ptmlvs 222ptmtims 221pupd8200 182pxdef.h 222pxdtypes.h 222

pxlogdef.h 222pxmacros.h 222pxoper.h 222pxos.h 222pxstc.h 222pxtypes.h 222pxutypes.h 222pxversion.h 180, 222

RREADME 161Relay Services Gateway See RSGrmdir command 57RSG

stopping 94

Ssample

files 145, 150samples.jar 213schema.h 215SELECT privileges

Teradata user account 75session limits

bteq 28, 38, 46, 54, 291system-wide 291

Setting the Semaphore Parameters 136, 141setupTables.bteq 175, 176, 177, 178, 216, 217Shared 162, 194Shared Common Components for Internationalization for

Teradata 228, 231, 233, 238, 240, 243, 246, 253, 258verifying 162, 194

slave.cpp 177slave_input.txt 177software

uninstalling previous versions 239sql.h 161, 188, 191sql1.txt 224sql2.txt 224sqlext.h 161, 188, 191sqlpp 167sqltypes.h 161, 188, 191sqlucode.h 161, 188, 191sqlunx.h 161, 188, 191stmnfyxt.c 225Stream Operator 182, 224supported software releases 3synchronize.cpp 177synchronize.h 177Synchronizer.cpp 178Synchronizer.h 178


Index

Ttables

accessing 75tbuild 221tbuildexe 222TCP/IP 265tdata.sl 189, 192tdata.so 161, 189, 192tdatpump.cfg 173, 174, 214tdconndlg.so 161, 189, 192tdgssconfig.jar 172, 213tdmst 285tdodbc 160tdodbc.cat 162tdses 285tdsql.h 188, 191tdxwinapp 161, 188, 191Technical Assistance 293TelapiThreadTest.cpp 177Teradata Call-Level Interface version 2 (CLIv2)

dependencies 254, 258verifying 168, 208

Teradata clientinstallion 40

Teradata COBOL Preprocessor2 254, 258verifying 210

Teradata Data Connectordependencies 254, 259

Teradata FastExportdependencies 254, 259verifying 171, 211

Teradata FastLoaddependencies 254, 259verifying 171, 212

Teradata Generic Security Servicesverifying 172, 213

Teradata Generic Security Services Clientdependencies 254, 259

Teradata JDBC Driver 280supported on 254, 259

Teradata MultiLoaddependencies 255, 260verifying 173, 213

Teradata ODBC Driverdefault directory 145, 150odbc.ini file 113

Teradata Parallel Transporterconfiguring after installing 116, 124, 129, 133, 139parameters 134, 140troubleshooting 288

Teradata Parallel Transporter Infrastructureversion 255

Teradata Tools and Utilities 253

Teradata TPumpdependencies 255, 260verifying 173, 214

Teradata user accountSELECT privileges 75

Teradata WebSphere MQ Access Module 256, 262verifying 182, 225

teragss_aix-power 213teragss_aix-power-32 213teragss_hpux-ia64 213teragss_hpux-pa 213teragss_hpux-pa32 213teragss_redhatlinux-i386 172teragss_redhatlinux-i64 172teragss_redhatlinux-ia64 172teragss_solaris-sparc 213teragss_solaris-sparc32 213teragss_suselinux-i386 172teragss_suselinux-i64 172teragss_suselinux-ia64 172terajdbc4.jar 172, 213TestBase.cpp 177TestBase.h 178TestExport.cpp 177TestExport.h 178TestLoad.cpp 177TestLoad.h 178TestSim.cpp 177TestSim.h 178TestStream.cpp 177TestStream.h 178TestUpdate.cpp 178TestUpdate.h 178ThreadTest.cpp 178ThreadTest.h 178ThreadTestParameters.cpp 178ThreadTestParameters.h 178tldnfyxt.c 173, 214tlogview 221tlogviewexe 222tptlaunch 222tpump 173, 214tpumpar.csql 174, 215tpumpexe 214tpumpimd.c 173, 214troubleshooting

network problems 285Teradata RDBMS problems 286

twb_status.txt 224twb_targets.txt 224twbcfg.ini 221twbcmdexe 222twbkill 221twbkillexe 222


Index

twbmsgs.cat 223twboper.ini 221twbpath 222twbpathexe 222twbpkg 224twbpkgrm 222, 224twbrmcp 222twbrmcpexe 222twbstat 221twbstatexe 222

Uumount command 57uninstalling

software 244, 247Update Operator 182, 225updnfyxt.c 225, 226Upgrade or Maintenance Software

installation 267upgrades, installing 267

Vverifying installation 159, 185

using bteq 155version 221version numbers 3vscnctdlg.so 161

Xxsp.cpp 176


Index


Tera data install guide for linux

Software

Transcript of Tera data install guide for linux