2459

Teradata Tools and Utilities
Installation Guide for UNIX and Linux
Release 13.00.00
B035-2459-088A
April 2009
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 Youve 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: teradata-books@lists.teradata.com
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-2009 by Teradata Corporation. All Rights Reserved.
Preface
Purpose
This book provides information about installing Teradata Tools and Utilities 13.00.00
products on a client system that runs on IBM AIX, HP-UX, Sun Solaris 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 database developers
System operators and other database specialists
Supported Releases
This book supports the following releases:
Teradata Database 13.00.00
Teradata Tools and Utilities 13.00.00
To locate detailed supported-release information:

1
Go to http://www.info.teradata.com/.
Click General Search under Online Publications.
Type 3119 in the Publication Product ID box.
Under Sort By, select Date.
Click Search.
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
Preface
Prerequisites
Prerequisites
The following prerequisite knowledge is required for this product:
Computer technology
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
April 2009
13.00.00
The following changes were made to support Teradata Tools and Utilities
13.00.00 installation:
Discontinued MultiTool. Removed references to the product from the
installation guide.
Teradata JDBC Driver added to Utility Pack CDs.
.NET Data Provider added to Utility Pack CD.
JMS Access Module is only available from the Teradata Download
Center.
Tar Teradata Client Packages script made available on CD ROM.
Added HP-UX filenames for WebSphere 64-bit.
Added Solaris Opteron filenames for Teradata Parallel Transporter
Infrastructure 32-bit.
September 2008
13.00.00
Updated installation procedures to reflect changes made to products since

Teradata Tools and Utilities 13.00.00 release.
Updated the information on installing (see Teradata WebSphere Access
Module on page 65) and verifying Teradata WebSphere Access Module
(see Verifying Teradata WebSphere MQ Access Module (mqaxsmod)
on page 214).
Updated information on configuring ODBC Diver for Teradata (see
Configuring the ODBC Driver for Teradata on page 160) and verifying
ODBC Driver for Teradata (see Verifying ODBC Driver for Teradata
(tdodbc) on page 185).
Added warning about installing both 32-bit and 64-bit Teragss for
ODBC.
Changed default and directory names where ODBC for Teradata is
installed.
Updated tdicu filenames and directories (see Verifying Shared
Common Components for Internationalization for Teradata (tdicu) on
page 187).
Preface
Additional Information
Date and Release
Description
August 2008
13.00.00
Updated installation procedures to reflect Teradata products added to

Teradata Tools and Utilities 13.00.00.
Teradata Tools and Utilities 13.0 Client Products package names now
include the version in the package name, (bteq130, cliv2130, piom130)
exceptions: arc, dul, and dultape.
The package name for Arc on Linux is "teradata_arc".
A new directory structure for UNIX TTU 13.0 Client products where
the default location is /opt/teradata/client/13.0/.
Changes to support the new Teradata Corporation branding that
include a new ASCII splash screen, copyright, license text, and logo.
Directories and references to NCR, now correctly refer to Teradata
Reduced the number of UNIX TPT products on the Parallel Transporter
CDs from 15 to 6.
For those UNIX Client products that have a 32-bit and a 64-bit
installation packages, those packages have been merged into a single
package, except for UNIX systems where the chipset is different (pa-risc
vs. ia64).
Added a menu item to the UNIX setup script for AIX, HPUX, Linux and
Solaris to uninstall previously installed versions of the Teradata Tools
and Utilities software.
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.
Type of Information
Description
Access to Information
Release overview
Use the Release Definition for the following

information:
1 Go to http://www.info.teradata.com/.
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
3 Type 2029 in the Publication Product ID box.
Late information
2 Click General Search under Online Publications.

4 Click Search.
5 Select the appropriate Release Definition from
the search results.
Preface
Type of Information
Description
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 Click Data Warehousing under Online
Publications, Browse by Category.

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 Tools and
Utilities are as follows:
Messages
B035-1096-mmyA
Teradata Tools and Utilities Command Summary
B035-2401-mmyA
Teradata Manager Installation Guide
B035-2402-mmyA
Teradata JDBC Driver User Guide
B035-2403-mmyA
Teradata Tools and Utilities Installation Guide for
Microsoft Windows
B035-2407-mmyA
Teradata MultiLoad Reference
B035-2409-mmyA
Teradata FastExport Reference
B035-2410-mmyA
Teradata FastLoad Reference
B035-2411-mmyA
Teradata Archive/Recovery Utility Reference
B035-2412-mmyA
Basic Teradata Query Reference
B035-2414-mmyA
Teradata Director Program Reference
B035-2416-mmyA
Teradata Call-Level Interface Version 2 Reference
for Channel-Attached Systems
B035-2417-mmyA
Teradata Call-Level Interface Version 2 Reference
for Network-Attached Systems
B035-2418-mmyA
Teradata Transparency Series/ Application
Programming Interface User Guide
B035-2419-mmyA
Preface
Type of Information
Description
(Continued from the bulleted list above) in the
Publication Product ID field, enter one of the
following book numbers:
IBM z/VM
B035-2422-mmyA
Teradata Tools and Utilities Access Module
Programmer Guide
B035-2424-mmyA
Teradata Tools and Utilities Access Module
Reference
B035-2425-mmyA
Teradata Manager User Guide
B035-2428-mmyA
Teradata SQL Assistant for Microsoft Windows
User Guide
B035-2430-mmyA
Teradata Parallel Transporter Operator
Programmer Guide
B035-2435-mmyA
Teradata Parallel Transporter Reference
B035-2436-mmyA
Teradata Access Module for Tivoli Installation and
User Guide
B035-2444-mmyA
Teradata Parallel Transporter User Guide
B035-2445-mmyA
Teradata Preprocessor2 for Embedded SQL
Programmer Guide
B035-2446-mmyA
IBM IMS/DC Interface for Teradata Reference
B035-2447-mmyA
IBM CICS Interface for Teradata Reference
B035-2448-mmyA
Interactive Teradata Query Reference
B035-2451-mmyA
Interactive Teradata Query User Guide
B035-2452-mmyA
IBM z/OS
B035-2458-mmyA
UNIX and Linux
B035-2459-mmyA
Preface
Type of Information
Description
(Continued from the bulleted list above) in the
Publication Product ID field, enter one of the
following book numbers:
Teradata System Emulation Tool User Guide
B035-2492-mmyA
OLE DB Provider for Teradata Installation and
User Guide
B035-2498-mmyA
Teradata Administrator User Guide
B035-2502-mmyA
Teradata Statistics Wizard User Guide
B035-2503-mmyA
Teradata Visual Explain User Guide
B035-2504-mmyA
Teradata SQL Assistant/Web Edition User Guide
B035-2505-mmyA
Teradata Index Wizard User Guide
B035-2506-mmyA
ODBC Driver for Teradata User Guide
B035-2509-mmyA
Teradata Query Director User Guide
B035-2510-mmyA
Teradata Query Scheduler Administrator Guide
B035-2511-mmyA
Teradata Query Scheduler User Guide
B035-2512-mmyA
Teradata Dynamic Workload Manager User
Guide
B035-2513-mmyA
Teradata Workload Analyzer User Guide
B035-2514-mmyA
Teradata Parallel Transporter Application
Programming Interface Programmer Guide
B035-2516-mmyA
Teradata Parallel Data Pump Reference
B035-3021-mmyA
Teradata Meta Data Services Installation and
Administration Guide
B035-3118-mmyA
Teradata Meta Data Services Programmer Guide
B035-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 Click Data Warehousing under Online
Publications, Browse by Category.

3 Click CD-ROM List and Images.
Preface
Type of Information
Description
Ordering
information for
manuals
Use the Teradata Information Products web

site to order printed versions of manuals.
2 Click How to Order under Print & CD
Publications.
3 Follow the ordering instructions.
General information
about Teradata
The Teradata home page provides links to

numerous sources of information about
Teradata. Links include:
1 Go to Teradata.com.
2 Select a link.
Executive reports, case studies of

customer experiences with Teradata,
and thought leadership
Technical information, solutions, and
expert advice
Press releases, mentions, and media
resources
Preface
10
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Changes to This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Chapter 1:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Teradata Tools and Utilities Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Definitions of Client and Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Product Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installation Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Installation Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teradata Software Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBM z/VM and IBM z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teradata Tools and Utilities CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
37
37
37
38
38
Chapter 2:
Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Installation Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling Previous Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Upgrade or Maintenance Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation of Dependent Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teradata Generic Security Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading TPump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
49
49
50
51
51
11
Table of Contents
Upgrading C/COBOL Preprocessor2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

PUT Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
pkgadd Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Tar Teradata Client Packages Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Available Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
LD_LIBRARY_PATH, SHLIB_PATH and LIBPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Upgrading Teradata ARC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Package Name Change on SUSE Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Teradata Parallel Transporter Package Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Uninstalling Teradata Warehouse Builder and
Teradata Parallel Transporter Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Teradata Parallel Transporter Install Information File . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Switching Back to the Installed Teradata Parallel Transporter Version . . . . . . . . . . . . . . .61
Teradata Generic Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
TeraGSS Package Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Uninstalling TeraGSS Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Switching Versions of TeraGSS Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Teradata WebSphere Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Manual Install for Teradata WebSphere MQ Access Module . . . . . . . . . . . . . . . . . . . . . . .65
Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Chapter 3:
Installing on IBM AIX Client Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Installing Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
IBM AIX Operating Systems Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Installation CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
IBM AIX Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Installation/Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Installation Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Uninstalling Previous Versions of Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Software Name Truncation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Teradata Parallel Transporter Default and Alternate Directory . . . . . . . . . . . . . . . . . . . . .71
Silent Installation of ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Installing Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Installing Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Installing the Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Installing the Teradata JDBC Driver from the Download Center. . . . . . . . . . . . . . . . . . . .76
Installing the Teradata Access Module for JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
12
Table of Contents
Adding CLI User Exit Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Chapter 4:
Installing on HP-UX Client Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Installing Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX Operating Systems Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
79
79
80
Installation/Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Uninstalling Previous Versions of HP-UX Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Uninstalling at the HP-UX Terminal Interface Window . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Teradata Parallel Transporter Default and Alternate Directory . . . . . . . . . . . . . . . . . . . . 84
Installing the Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Teradata Tools and Utilities Products Silently . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Teradata Tools and Utilities Products Interactively. . . . . . . . . . . . . . . . . . . . . .
Installing Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Teradata JDBC Driver from the Download Center. . . . . . . . . . . . . . . . . . .
Installing the Teradata Access Module for JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding CLI User Exit Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
85
86
88
92
92
92
92
Chapter 5:
Installing on Sun Solaris SPARC
Client Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Installing Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sun Solaris SPARC Operating Systems Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sun Solaris SPARC Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
95
95
95
96
Installation/Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Uninstalling Previous Versions of Sun Solaris SPARC Software . . . . . . . . . . . . . . . . . . . . . . . 97
Teradata Parallel Transporter Default and Alternate Directories . . . . . . . . . . . . . . . . . . . 97
Screen Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Solaris Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Default Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
13
Table of Contents
Installing Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Installing Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Installing the Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
Installing the Teradata JDBC Driver from the Download Center. . . . . . . . . . . . . . . . . . .106
Installing the Teradata Access Module for JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
Adding CLI User Exit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
Chapter 6:
Installing on Sun Solaris Opteron
Client Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Installing Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Sun Solaris Opteron Systems Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Installation CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Sun Solaris Opteron Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Installation/Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Installation Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Uninstalling Previous Versions of Sun Solaris Opteron Software . . . . . . . . . . . . . . . . . . . . . .111
Default and Alternate Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Solaris Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Installing Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Installing Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Installing the Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Installing the Teradata JDBC Driver from the Download Center. . . . . . . . . . . . . . . . . . .119
Installing the Teradata Access Module for JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Adding CLI User Exit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Chapter 7:
Installing on Red Hat Linux
Client Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Installing Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Red Hat Linux Operating Systems Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Installation of Teradata Tools and Utilities Products Using PUT. . . . . . . . . . . . . . . . . . .121
Installation CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Red Hat Linux Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Installation/Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Installation Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
14
Table of Contents
Uninstalling Previous Versions of Red Hat Linux Software . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Installing Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Teradata Tools and Utilities Products Silently on Red Hat Linux . . . . . . . . .
Installing Teradata Tools and Utilities Products Interactively on Red Hat Linux . . . . .
Installing Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Teradata JDBC Driver from the Download Center. . . . . . . . . . . . . . . . . .
Installing the Teradata Access Module for JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding CLI User Exit Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126
126
128
132
135
136
136
136
Chapter 8:
Installing on SUSE Linux
Client Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Installing Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SUSE Linux Operating Systems Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SUSE Linux Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
139
139
139
140
Installation/Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Installation Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Installing Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Teradata Tools and Utilities Products Silently on SUSE Linux . . . . . . . . . . .
Installing Teradata Tools and Utilities Products Interactively on SUSE Linux . . . . . . .
Installing the Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Teradata JDBC Driver from the Download Center. . . . . . . . . . . . . . . . . .
Installing the Teradata Access Module for JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding CLI User Exit Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
141
143
147
147
148
148
Chapter 9:
Installing with Tar Teradata Client Packages . . . . . . . . . . . . . . . . . 149
Tar Teradata Client Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Script Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Using the tar Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Script Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Typical Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
15
Table of Contents
Chapter 10:
Configuring Teradata Tools and Utilities. . . . . . . . . . . . . . . . . . . . . . . . .157
Configuring Environment Variables for CLIv2, Data Connector, and TeraGSS . . . . . . . . . .158
Setting the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
Configuring the ODBC Driver for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Configuring the ODBC Driver for IBM AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Configuring the ODBC Driver for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
Configuring the ODBC Driver for Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
Configuring the ODBC Driver for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
Configuring Teradata Access Module for JMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Configuring Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Configuring Teradata Parallel Transporter for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Configuring Teradata Parallel Transporter for Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . .170
Configuring Teradata Parallel Transporter for Red Hat Linux . . . . . . . . . . . . . . . . . . . . .176
Chapter 11:
After You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
Verifying the Installation of Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
Verifying Basic Teradata Query (bteq) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
Verifying Named Pipes Access Module (npaxsmod) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Verifying ODBC Driver for Teradata (tdodbc). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Verifying Shared Common Components for Internationalization
for Teradata (tdicu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
Verifying Teradata Access Module for JMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Verifying Teradata Archive/Recovery Utility (arc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
Verifying Teradata Call-Level Interface version 2 (cliv2). . . . . . . . . . . . . . . . . . . . . . . . . .193
Verifying Teradata C Preprocessor2 (sqlpp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Verifying Teradata COBOL Preprocessor2 (cobpp). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
Verifying Teradata Data Connector (piom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
Verifying Teradata JDBC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
Verifying Teradata FastExport (fastexp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
Verifying Teradata FastLoad (fastld) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
Verifying Teradata Generic Security Services (TeraGSS). . . . . . . . . . . . . . . . . . . . . . . . . .202
Verifying Teradata MultiLoad (mload) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
Verifying Teradata TPump (tpump) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
Verifying Teradata Parallel Transporter
API (papid000). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204
Export Operator (pexpd000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
16
Table of Contents

Infrastructure (tbldd000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load Operator (plodd000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stream Operator (pstmd000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Update Operator (pupdd000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying Teradata WebSphere MQ Access Module (mqaxsmod) . . . . . . . . . . . . . . . . .
214
214
Verifying the Installation Using BTEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Log onto the Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Submit a Sample Teradata SQL Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exit BTEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
215
215
216
217
210
213
213
Verifying the Installation Using the CLI Sample Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Run clisamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Chapter 12:
Connecting to a Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Making the Database Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Logon Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting in GUI Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting in Command Line Driven Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example Logons from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to a Teradata Database Programmatically . . . . . . . . . . . . . . . . . . . . . . . . . .
Logon Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
219
219
220
222
223
227
228
Chapter 13:
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Client Computer Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Communicate Over the Network with Teradata Database . . . . . . . . . . . . . . . .
Incorrect Path Name in COPLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Incorrect Path Name in COPERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
errmsg.cat File Not Found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Incorrect Path Name in COPANOMLOG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Missing Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Incorrect Entries in the Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Missing Entries in the /etc/services File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
231
231
232
232
232
232
233
233
233
17
Table of Contents
Improper Linking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233

Incorrect clispb.dat Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
Cannot Log On from CLI Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
Cannot Log On to the Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234
Teradata Database Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234
Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
Unable to Find tbuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
Cannot Run the New Installed Version of Teradata Parallel Transporter . . . . . . . . . . . .236
Failed to Load libpxcommon Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
Unable to Find Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
Unable to Find Messages on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238
Appendix A:
Session Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239
BTEQ Session Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239
System-Wide Session Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241
18
List of Figures
Figure 1: Typical Connect to Teradata Database Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
19
List of Figures
20
List of Tables
Table 1: Teradata Tools and Utilities supported on UNIX and Linux. . . . . . . . . . . . . . . . . . . 25

Table 2: Definition of Client and Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 3: Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 4: Teradata Utility Pack - Vol 1 of 3 CD (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 5: Teradata Utility Pack - Vol. 2 of 3 CD (HP-UX and Linux) . . . . . . . . . . . . . . . . . . . 39
Table 6: Teradata Utility Pack - Vol. 3 of 3 CD (AIX and Solaris) . . . . . . . . . . . . . . . . . . . . . . 39
Table 7: Data Management CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 8: Preprocessors Vol 1 of 3 CD (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 9: Preprocessors Vol 2 of 3 CD (HP-UX and Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 10: Preprocessors Vol 3 of 3 CD (AIX and Solaris) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 11: Load/Unload Vol 1 of 3 CD (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 12: Load/Unload Vol 2 of 3 CD (HP-UX and Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 13: Load/Unload Vol 3 of 3 CD (AIX and Solaris) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 14: Parallel Transporter Vol 1 of 3 CD (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Table 15: Parallel Transporter Vol 2 of 3 CD (HP-UX and Linux) . . . . . . . . . . . . . . . . . . . . . 45
Table 16: Parallel Transporter Vol 3 of 3 CD (AIX and Solaris) . . . . . . . . . . . . . . . . . . . . . . . 46
Table 17: Tape Storage Management Enablers CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 18: Query Director CD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 19: MetaData Services CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 20: Short Names for Teradata Parallel Transporter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 21: Teradata WebSphere MQ Access Module Libraries on HP-UX Itanium . . . . . . . . 65
Table 22: Environment Variables Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 23: Kernel Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Table 24: Environment Variables Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 25: Default and Alternative Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Table 26: Screen Navigation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Table 27: CD-ROM Mount Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Table 28: Selecting the Packages to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Table 29: Kernel Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Table 30: Environment Variables Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Table 31: Default and Alternative Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Table 32: CD-ROM Mount Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
21
List of Tables
Table 33: Selecting the Packages to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Table 34: Kernel Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Table 35: Environment Variables Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Table 36: Checking for Previous Versions of Software on Linux . . . . . . . . . . . . . . . . . . . . . . .123
Table 37: Uninstalling Previous Versions of Software on Linux . . . . . . . . . . . . . . . . . . . . . . .124
Table 38: Changing Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Table 39: Installing Teradata Tools and Utilities on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Table 40: Verifying the Installation on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
Table 41: Kernel Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Table 42: Environment Variables Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Table 43: Changing Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Table 44: Installing Teradata Tools and Utilities on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Table 45: Verifying the Installation on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Table 46: tar_teradata_client_packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Table 47: tar_teradata_client_packages Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Table 48: HP-UX Shared Memory Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
Table 49: HP-UX Semaphore Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
Table 50: HP-UX Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Table 51: Sun Solaris Shared Memory Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
Table 52: Sun Solaris Semaphore Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Table 53: Sun Solaris Environment Variables Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Table 54: Linux Red Hat Shared Memory Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
Table 55: Red Hat Linux Semaphore Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
Table 56: Red Hat Linux Environment Variables Updated . . . . . . . . . . . . . . . . . . . . . . . . . . .178
Table 57: Basic Teradata Query Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
Table 58: Named Pipes Access Module Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Table 59: ODBC Driver for Teradata Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Table 60: Shared Common Components for Internationalization for Teradata Files . . . . . .187
Table 61: Teradata Access Module for JMS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
Table 62: Teradata Archive/Recovery Utility (ARC) 32-bit Files . . . . . . . . . . . . . . . . . . . . . . .193
Table 63: Teradata Call-Level Interface version 2 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
Table 64: Teradata C Preprocessor2 Files for IBM AIX, HP-UX,
HP Itanium, Solaris SPARC, Solaris Opteron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Table 65: Teradata C Preprocessor2 Files for Red Hat Linux 32-bit,
Red Hat Linux 64-bit, SUSE Linux 64-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
Table 66: Teradata COBOL Preprocessor2 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
22
List of Tables
Table 67: Teradata Data Connector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Table 68: Teradata JDBC Driver Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Table 69: Teradata FastExport Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Table 70: Teradata FastLoad Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Table 71: Teradata Generic Security Services Version Files . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Table 72: Teradata MultiLoad Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Table 73: Teradata TPump Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Table 74: Teradata Parallel Transporter API Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Table 75: Teradata Parallel Transporter Export Operator Files . . . . . . . . . . . . . . . . . . . . . . . 210
Table 76: Teradata Parallel Transporter Infrastructure Files . . . . . . . . . . . . . . . . . . . . . . . . . 210
Table 77: Teradata Parallel Transporter Load Operator Files. . . . . . . . . . . . . . . . . . . . . . . . . 213
Table 78: Teradata Parallel Transporter Stream Operator Files . . . . . . . . . . . . . . . . . . . . . . . 213
Table 79: Teradata Parallel Transporter Update Operator Files. . . . . . . . . . . . . . . . . . . . . . . 214
Table 80: Teradata WebSphere MQ Access Module Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Table 81: Teradata WebSphere MQ Access Module Files for HP-UX Itanium . . . . . . . . . . 215
Table 82: .logon Command Parameter Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Table 83: Supported Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Table 84: Single-Sign-On for Legacy Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Table 85: Connecting Programmatically to a Teradata Database. . . . . . . . . . . . . . . . . . . . . . 228
Table 86: Logon Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Table 87: Session Guidelines for Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
23
List of Tables
24
CHAPTER 1
Introduction
This chapter provides the background information need before installing the Teradata Tools
and Utilities software for IBM AIX, HP-UX, Sun Solaris, Red Hat Linux and SUSE Linux.
This chapter contains the following information:
Teradata Tools and Utilities Compatibility
System Requirements
Software Requirements
Installation Kit Contents

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.
The Teradata Tools and Utilities 13.00.00 Supported Platforms and Product Versions spreadsheet
lists the products versions associated with this release and the specific platforms supported.
See Supported Releases on page 3 for information how to access this spreadsheet.
Table 1 lists the products for UNIX and Linux that are available in Teradata Tools and Utilities
13.00.00.
Table 1: Teradata Tools and Utilities supported on UNIX and Linux
Product
Description
Basic Teradata Query (BTEQ)
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.
25
Chapter 1: Introduction
Table 1: Teradata Tools and Utilities supported on UNIX and Linux (continued)
26
Product
Description
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.
Shared Common Components for

Internationalization for Teradata
A library of routines based on the IBM

International Components for Unicode version
3.6. The library provides unicode support.
Teradata Access Module for JMS
A utility in the Teradata Tools and Utilities

product set that offers a fast, asynchronous
method to transfer data from any JMS-enabled
messaging system into Teradata Database. With
this access module, data can be imported directly
from any JMS-enabled messaging system, which
are generally referred to as Message Oriented
Middleware (MOM) or Enterprise Services Bus
(ESB) systems.
Teradata Archive/Recovery Utility (ARC)
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 Teradatas Backup Applications
solutions and the Teradata Database.
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 (CLIv2)
A library of routines that enable an application

program to access data on a Teradata Database.
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 (also known as PIOM)
Reads and writes flat files, to provide the input/

output interface for access modules.
Teradata JDBC Driver
Provides access to the Teradata Database using

Java applications.
Product
Description
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
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 Generic Security Services Java
Teradata's implementation of industry-standard

Generic Security Services APIs in Java language. It
provides enhanced security services interfaces
between Teradata network clients and Teradata
Database.
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 Transporter
Provides high-performance data extraction,

loading, and updating operations for the Teradata
Database.
Teradata Parallel Transporter API
A set of application programming interfaces used

to load and export data to and from Teradata
Database systems.
Teradata Parallel Transporter Data Connector

Operator
Reads and writes flat files, to provide the input/

output interface for access modules. It also can
function as both a producer and consumer
operator when interfacing with an access module
that reads or writes data from an external source.
Teradata Parallel Transporter DDL Operator
A standalone operator that allows use of DDL

SQL statements in a Teradata PT script.
27
Product
Description
Teradata Parallel Transporter Export Operator 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 FastExport
OUTMOD Adapter Operator
A consumer operator that functions similar to

Teradata FastExport utility OUTMOD routines.
The FastExport OUTMOD Adapter operator
allows Teradata FastExport utility OUTMOD
routines as part of a Teradata PT job.
A producer operator which functions similar to
Teradata FastLoad utility INMOD routines.
Teradata Parallel Transporter FastLoad

INMOD Adapter Operator
The FastLoad INMOD Adapter operator allows

use of the Teradata FastLoad utility INMOD
routines as part of a Teradata PT job.
Teradata Parallel Transporter Infrastructure
Object-oriented client application that provides

scalable, high-speed, parallel data extraction,
loading, and updating.
Teradata Parallel Transporter Load Operator
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 MultiLoad

INMOD Adapter Operator
Operator which functions similar to Teradata

MultiLoad INMOD routines.
The MultiLoad INMOD Adapter operator allows
use of the Teradata MultiLoad utility INMOD
routines a part of a Teradata PT job.
This operator can be used as either a producer
operator or a filter operator.
Teradata Parallel Transporter ODBC Operator The ODBC operator is a producer operator that
enables universal open data access to retrieve data
from many ODBC-compliant data sources.
28
Product
Description
Teradata Parallel Transporter OS Command

Operator
The OS Command operator is a standalone

operator that allows OS commands to be
submitted to a client environment during
Teradata PT job execution.
Teradata Parallel Transporter SQL Inserter

Operator
A consumer operator that accepts data from other

operators from the Teradata PT operator
interface. The operator inserts the data into the
specified table on the Teradata Database.
Teradata Parallel Transporter SQL Selector

Operator
A producer operator that submits a single

Teradata SQL SELECT statement to the Teradata
Database to retrieve data from a table.
The operator passes the SELECT statement result
data to other operators from the Teradata PT
operator interface.
Teradata Parallel Transporter Stream

Operator
A consumer operator that emulates the Teradata

TPump 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
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 Query Director
Increases database availability and efficiency by

routing sessions between two or more Teradata
Databases.
Teradata TPump
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 WebSphere MQ Access Module
Allows Teradata utilities to import data using

IBM WebSphere MQ message queuing
middleware.
Note: Teradata Archive and Recovery Utility (ARC) is included to support Teradatas Backup
Applications. Teradata ARC is not sold as an individual standalone product for MP-RAS,
Windows, or Linux, although it is available as a standalone application on mainframes
supported by Teradata.
29
System Requirements
Note: Refer to the Teradata Tools and Utilities Release Definition, Release 13.00.00 for specific
information about individual Teradata Tools and Utilities products, including information on
which products are supported on the various operating systems and platforms.
Definitions of Client and Server

Table 2 lists the definitions that apply to this installation guide.
Table 2: Definition of Client and Server
Term
Definition
Teradata client software
Software that installs and runs on a IBM AIX, HP-UX, Sun Solaris
SPARC, Sun Solaris Opteron, Red Hat Linux or SUSE Linux
operating system. This software allows access to a Teradata
Database.
Teradata server
Refers to the system running the Teradata Database.
System Requirements
Platforms Supported
Teradata Tools and Utilities software is packaged to install and run on systems or nodes
supporting one of these operating systems:
IBM AIX
HP-UX
Sun Solaris SPARC
Sun Solaris Opteron
Red Hat Linux
SUSE Linux
The Teradata Tools and Utilities ##.##.## Supported Platforms and Product Versions spreadsheet
Network Requirements
IBM AIX, HP-UX, Sun Solaris, and Linux use the Transmission Control Protocol/Internet
Protocol (TCP/IP) to communicate with the Teradata Database.
The client must be connected to one of the following:
30
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
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
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.
Product Dependencies
Table 3 lists the products in the column 1 which are dependent upon the products in column
2. The products in the column 2 must be installed for the products in column 2 to operate.
Table 3: Product Dependencies
Products
Dependent Products
Basic Teradata Query (BTEQ) 13.00.00
For Sun Solaris SPARC, Sun Solaris Opteron, IBM AIX, HPUX, Red Hat Linux and SUSE Linux:
Shared Common Components for Internationalization for
Teradata 13.00.00 or later
Teradata Data Connector 13.00.00 or later
Teradata Call-Level Interface version 2 (CLIv2) 13.00.00 or
later
Teradata Generic Security Services 13.00.00 or later
TeraGSS - Client package
Named Pipes Access Module 13.00.00
Installation of the Named Pipes Access Module on Sun Solaris

SPARC, Sun Solaris Opteron, IBM AIX and HP-UX is not
required, but provides access functionality for these products:
Teradata Archive/Recovery Utility (ARC) 13.00.00 or later

Basic Teradata Query (BTEQ) 13.00.00 or later
Teradata FastExport 13.00.00 or later
Teradata FastLoad 13.00.00 or later
Teradata MultiLoad 13.00.00 or later
Teradata TPump 13.00.00 or later
Teradata Parallel Transporter 13.00.00 or later
31
Table 3: Product Dependencies (continued)
Products
Dependent Products
ODBC Driver for Teradata 13.00.00
For Sun Solaris SPARC, Sun Solaris Opteron, HP-UX, Red Hat
Linux and SUSE Linux:
Teradata 13.00.00
For IBM AIX:
xlC.rte 5.0.2.1
xlC.aix.50.rte 5.0.2.2

Teradata 13.00.00
No dependencies
Teradata Access Module for JMS 13.00.00
JDK 1.4 or later
JMS enabled Messaging System
Teradata Archive/Recovery Utility (ARC) 13.00.00
For Windows, MP-RAS and SUSE Linux:

Teradata 13.00.00
TeraGSS - Client packageCLIv2 version 13.00.00 or later
Teradata Data Connector version 13.00.00 or later
Note: Teradata Archive and Recovery Utility (ARC) is
included to support Teradatas Backup Applications.
Teradata ARC is not sold as an individual standalone
product for MP-RAS, Windows, or SUSE Linux, although it
is available as a standalone application on mainframes
Teradata Call-Level Interface version 2 (CLIv2) 13.00.00
Teradata 13.00.00
Teradata C Preprocessor2 13.00.00
Teradata 13.00.00
later
32
Products
Dependent Products
Teradata COBOL Preprocessor2 13.00.00
For Sun Solaris SPARC, Sun Solaris Opteron, Red Hat Linux
and SUSE Linux:
No dependencies
For IBM AIX, and HP-UX:
later
Teradata Data Connector 13.00.00
No dependencies
Teradata JDBC Driver 13.00.00
See Teradata JDBC Driver
Teradata FastExport 13.00.00
For Sun Solaris SPARC, Sun Solaris Opteron, IBM AIX, HPUX, and Red Hat Linux and SUSE Linux:
Teradata 13.00.00
later
Teradata FastLoad 13.00.00
Teradata 13.00.00
later
Teradata Generic Security Services client 13.00.00
No dependencies
Teradata Generic Security Services Java client 13.00.00
No dependencies
33
Products
Dependent Products
Teradata MultiLoad 13.00.00
Teradata 13.00.00
later
Teradata Parallel Transporter 13.00.00

Teradata Parallel Transporter API 13.00.00
For Sun Solaris SPARC, Sun Solaris Opteron, IBM AIX, Red
Hat Linux and SUSE Linux and HP-UX:
Teradata Parallel Transporter Load Operator 13.00.00 or
later
Teradata Parallel Transporter Update Operator 13.00.00 or
later
Teradata Parallel Transporter Stream Operator 13.00.00 or
later
Teradata Parallel Transporter Export Operator 13.00.00 or
later
later
Teradata Parallel Transporter Export Operator 13.00.00 For Sun Solaris SPARC, Sun Solaris Opteron, IBM AIX, Red
Hat Linux and SUSE Linux, and HP-UX:
Teradata Parallel Transporter Infrastructure 13.00.00 or later
Teradata Parallel Transporter Infrastructure 13.00.00
For Sun Solaris SPARC, IBM AIX, HP-UX, Red Hat Linux and
SUSE Linux:
later
Teradata Parallel Transporter Load Operator 13.00.00
For Sun Solaris SPARC, Sun Solaris Opteron, IBM AIX, Red
Hat Linux and SUSE Linux and HP-UX:
Teradata Call-Level Interface version 2 (CLIv2) version
13.00.00 or later
34
Products
Dependent Products
Teradata Parallel Transporter Stream Operator 13.00.00 For Sun Solaris SPARC, Sun Solaris Opteron, IBM AIX, Red
13.00.00 or later
Teradata Parallel Transporter Update Operator 13.00.00 For Sun Solaris SPARC, Sun Solaris Opteron, IBM AIX, Red
13.00.00 or later
Teradata TPump 13.00.00
Teradata 13.00.00
Teradata Call-Level Interface version 2 (CLIv2) 13.00.00
Teradata WebSphere MQ Access Module 13.00.00
For Sun Solaris SPARC, Sun Solaris Opteron, IBM AIX and HPUX:
Basic Teradata Query (BTEQ) 13.00.00 or later
Teradata FastExport 13.00.00 or later
Teradata FastLoad 13.00.00 or later
Teradata MultiLoad 13.00.00 or later
Teradata TPump 13.00.00 or later
Teradata Parallel Transporter 13.00.00 or later
For IBM AIX:
WebSphere MQ (AIX) 5.3
For HP-UX:
WebSphere MQ (HP-UX) 5.2
Note: Teradata Parallel Transporter Infrastructure 13.00.00 is certified with Teradata CLIv2
version 13.00.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
35
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
Teradata Parallel Transporter ODBC Operator
Teradata Parallel Transporter OS Command Operator
Teradata Parallel Transporter SQL Inserter Operator
Teradata Parallel Transporter SQL Selector Operator
Note: The installation of Teradata Parallel Transporter API installs the following software:
Teradata Parallel Transporter ICU Library
Teradata Parallel Transporter Operator Support Library
Installation Order
Before installing Teradata Tools and Utilities products, four product dependencies must be
installed in the following order:
1
Shared Common Components for Internationalization for Teradata (tdicu).
Teradata Generic Security Services (TeraGSS).
Teradata Call-Level Interface version 2 (CLIv2).
Teradata Data Connector (piom).
Note: If products are uninstalled, do not uninstall Shared Common Components for
Internationalization for Teradata until all software that have it as a dependency are first
uninstalled.

The Teradata Tools and Utilities 13.00.00 installation kit includes the following
documentation:
Teradata Tools and Utilities Release Definition, Release 13.00.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. Refer to Table 4 through Table 19 for a
list of the products and dependencies on each CD:
36
Teradata Utility Pack - Vol 1 of 3 (Windows)
Teradata Utility Pack - Vol 2 of 3 (HP-UX-Linux)
Teradata Utility Pack - Vol 3 of 3 (AIX-Solaris)
Database Management
Preprocessors - Vol 1 of 3 (Windows)

Preprocessors - Vol 2 of 3 (HP-UX-Linux)
Preprocessors - Vol 3 of 3 (AIX-Solaris)
Load/Unload - Vol 1 of 3 (Windows)
Load/Unload - Vol 2 of 3 (HP-UX-Linux)
Load/Unload - Vol 3 of 3 (AIX-Solaris)
Parallel Transporter - Vol 1 of 3 (Windows)
Parallel Transporter - Vol 2 of 3 (HP-UX-Linux)
Parallel Transporter - Vol 3 of 3 (AIX-Solaris)
Query Director (Linux-Windows)
Tape Storage Management Enablers (Linux-MP-RAS-Windows)
Meta Data Services (Linux-MP-RAS (RSG)-Windows)
If all of the CDs ordered were not received, contact the Teradata Solutions Customer Services
Remote Services Center (TSCS-RSC). For more information, refer to the Teradata Tools and
Utilities Release Definition, Release 13.00.00.
Teradata 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 downloaded from the Teradata
Software Server at:
http://tssprod.teradata.com:8080/TSFS/home.do
IBM z/VM and IBM z/OS

Teradata Tools and Utilities products are also supported on channel-attached platforms, such
as IBM z/VM and IBM z/OS. On these platforms, the products are loaded from tape.
The following installation guides contain the procedures to install Teradata Tools and Utilities
on IBM z/VM and IBM z/OS systems.
Teradata Tools and Utilities Installation Guide for IBM z/VM
Teradata Tools and Utilities Installation Guide for IBM z/OS

The Teradata JDBC Driver has been added to the Utility Pack CDs starting in Teradata Tools
and Utilities Release 13.00.00. The driver files, readme.txt, terajdbc4.jar and tdgssconfig.jar,
must be manually downloaded to a directory of choice on the target client from \TeraJDBC in
the root directory of the installation CD ROM.
The Teradata JDBC Driver can also be downloaded from the World Wide Web. For
installation, see Installing the Teradata JDBC Driver on page 87.
The Java Development Kit is a requirement to use the Teradata JDBC Driver. For information
how to download the kit, see:
37
Installing the Teradata JDBC Driver

The Teradata JDBC Driver must be downloaded from the Teradata Download Center at:
http://www.teradata.com/resources/drivers-udfs-and-toolbox
The files can be copied into a directory of choice and are machine independent.
For configuration instructions go to Importing the SQL Package and Loading the Teradata
JDBC Driver in chapter 2 of the Teradata JDBC Driver User Guide.
Note: It is recommended, but not required, that any previous release of the Teradata JDBC
Driver be uninstalled prior to downloading and using this release of the Teradata JDBC
Driver.
Teradata Tools and Utilities CDs

Table 4 lists the Windows products and dependencies on the Teradata Utility Pack Vol 1CD.
Table 4: Teradata Utility Pack - Vol 1 of 3 CD (Windows)
Teradata Utility Pack - Vol 1 of 3 CD
Platforms (Windows)
Windows
Windows
Note: 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.
Windows
Shared ICU Libraries for Teradata
Windows
Teradata Administrator
Windows
Windows
Teradata Data Connector
Windows
Dependency
Note: Teradata JDBC Driver is distributed on
all Utility Pack CDs. Its located in the
\TeraJDBC directory located in the root
directory of each CD.
The three files in the directory, readme.txt,
terajdbc4.jar and tdgssconfig.jar must be
manually copied to a directory of choice on the
target client.
38
Windows
.NET Data Provider for Teradata
Dependency
Teradata SQL Assistant
Windows
Table 4: Teradata Utility Pack - Vol 1 of 3 CD (Windows) (continued)
Platforms (Windows)
Teradata SQL Assistant/Web Edition
Windows
Table 5 lists the HP-UX and Linux products and dependencies on the Teradata Utility Pack Vol
2 CD.
Table 5: Teradata Utility Pack - Vol. 2 of 3 CD (HP-UX and Linux)
Teradata Utility Pack - Vol 2of 3 CD
Platforms (HP-UX and Linux)
HP-UX and Linux
HP-UX and Linux

Transporter.
HP-UX and Linux
HP-UX and Linux
HP-UX and Linux
HP-UX and Linux
HP-UX and Linux
Dependency
target client.
Table 6 lists the Sun Solaris and IBM AIX products and dependencies on the Teradata Utility
Pack Vol 3 CD.
Table 6: Teradata Utility Pack - Vol. 3 of 3 CD (AIX and Solaris)
Platforms (AIX-Solaris)
IBM AIX, Solaris SPARC
39
Table 6: Teradata Utility Pack - Vol. 3 of 3 CD (AIX and Solaris) (continued)
Platforms (AIX-Solaris)

Transporter.
IBM AIX, Solaris SPARC, Solaris Opteron
Dependency
target client.
Table 7 lists the products and dependencies on the Data Management CD.
Table 7: Data Management CD
40
Database Management CD
Platforms (Windows)
Product dependency
Product dependency
Product dependency
Product dependency
Product dependency
Teradata Dynamic Workload Manager
Windows
Product dependency
Teradata Index Wizard
Windows
Teradata Manager
Windows
Teradata Performance Monitor
Windows
Table 7: Data Management CD (continued)
Database Management CD
Platforms (Windows)
Teradata Query Scheduler Administrator
Windows
Teradata Query Scheduler Client
Windows
Teradata Query Scheduler Server
Windows
Teradata Statistics Wizard
Windows
Teradata System Emulation Tool
Windows
Teradata Visual Explain
Windows
Teradata Workload Analyzer
Windows
Table 8 lists the Windows products and dependencies on the Preprocessors Vol 1 CD
Table 8: Preprocessors Vol 1 of 3 CD (Windows)
Preprocessors Vol 1 of 3 CD
Platforms (Windows)
Product dependency
Windows
Product dependency
Product Dependency
Table 9 lists the HP-UX and Linux products and dependencies on the Preprocessors Vol 2 CD.
Table 9: Preprocessors Vol 2 of 3 CD (HP-UX and Linux)
Product dependency
HP-UX
Product dependency
Teradata Cobol Preprocessor2
HP-UX and AIX
Product dependency
Table 10 lists the IBM AIX and Solaris products and dependencies on the Preprocessors Vol 3
CD.
41
Table 10: Preprocessors Vol 3 of 3 CD (AIX and Solaris)
Platforms (AIX- and Solaris)
Product dependency
Product dependency
Teradata Cobol Preprocessor2
IBM AIX
Product dependency
Table 11 lists the Windows products and dependencies on the Load/Unload Vol 1 CD.
Table 11: Load/Unload Vol 1 of 3 CD (Windows)
Load/Unload Vol 1 of 3 CD
Platforms (Windows)
Product dependency
Windows
Windows
Access Module that works for both the standalone
utilities and Teradata Parallel Transporter.
Product dependency
Product dependency
Product dependency
Windows
Teradata FastExport
Windows
Teradata FastLoad
Windows
Product dependency
Teradata MultiLoad
Windows
Teradata OLE DB Access Module
Windows
Teradata TPump
Windows
Windows
Note: 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.
42
Table 12 lists the HP-UX and Linux products and dependencies on the Load/Unload Vol 2 CD.
Table 12: Load/Unload Vol 2 of 3 CD (HP-UX and Linux)
Product dependency
HP-UX
HP-UX, Linux
Product dependency
Product dependency
HP-UX, Linux
Teradata FastExport
HP-UX, Linux
Teradata FastLoad
HP-UX, Linux
Product dependency
Teradata MultiLoad
HP-UX, Linux
Teradata TPump
HP-UX, Linux
HP-UX, Linux
Table 13 lists the Sun Solaris and IBM AIX products and dependencies on the Load/Unload Vol
3 CD.
Table 13: Load/Unload Vol 3 of 3 CD (AIX and Solaris)
Platforms (AIX and Solaris)
Product dependency
Solaris SPARC
Solaris SPARC, AIX

43
Table 13: Load/Unload Vol 3 of 3 CD (AIX and Solaris) (continued)
Product dependency
Product dependency
Product dependency
Solaris SPARC, AIX, Solaris Opteron
Teradata FastExport
Teradata FastLoad
Product dependency
Teradata MultiLoad
Teradata TPump

Table 14 lists the Windows products and dependencies on the Parallel Transporter Vol 1 CD.
Table 14: Parallel Transporter Vol 1 of 3 CD (Windows)
Parallel Transporter Vol 1 of 3 CD
Platforms (Windows)
Product dependency
44
Product dependency
Product dependency
Product dependency
Table 14: Parallel Transporter Vol 1 of 3 CD (Windows) (continued)
Platforms (Windows)
Teradata Parallel Transporter:
Windows
Note: Teradata Parallel Transporter ICU Library

and Operator Support Library are installed as
part of the Teradata Parallel Transporter API.

Teradata Parallel Transporter Export Operator
Teradata Parallel Transporter Stream Operator
Operator
Note: 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.
Note: Teradata Parallel Transporter Wizard is
only supported on Windows.
Product dependency
Table 15 lists the HP-UX and Linux products and dependencies on the Parallel Transporter Vol
2 CD.
Table 15: Parallel Transporter Vol 2 of 3 CD (HP-UX and Linux)
Product dependency
Product dependency
Product dependency
Product dependency
45
Table 15: Parallel Transporter Vol 2 of 3 CD (HP-UX and Linux) (continued)
HP-UX and Linux


Operator

Operator are installed as part of the Teradata
Parallel Transporter Infrastructure.
HP-UX and Linux

Table 16 lists the Sun Solaris and IBM AIX products and dependencies on the Parallel
Transporter Vol 3 CD.
Table 16: Parallel Transporter Vol 3 of 3 CD (AIX and Solaris)
Product dependency
46
Product dependency
Product dependency
Product dependency
Table 16: Parallel Transporter Vol 3 of 3 CD (AIX and Solaris) (continued)
IBM AIX, Solaris SPARC, and Solaris Opteron


Operator

Operator are installed as part of the Teradata
Parallel Transporter Infrastructure.
Note: Teradata Parallel Transporter
Infrastructure is not supported on Solaris
Opteron.
Product Dependency
Table 17 lists the products and dependencies on the Tape Storage Management Enablers CD.
Table 17: Tape Storage Management Enablers CD
Tape Storage Management Enablers CD
Platforms (Windows, MP-RAS and Linux)
Product dependency
Product dependency
Linux and Windows

Note: Teradata Archive and Recovery Utility
(ARC) is included to support Teradatas Backup
Applications. Teradata ARC is not sold as an
individual standalone product for MP-RAS,
Windows, or SUSE Linux, although it is available
as a standalone application on mainframes
Product dependency
Product dependency
47
Table 17: Tape Storage Management Enablers CD (continued)
Tape Storage Management Enablers CD
Platforms (Windows, MP-RAS and Linux)
Product dependency
Product dependency
Table 18 lists the products and dependencies on the Query Director CD.
Table 18: Query Director CD
Query Director CD
Platforms (Windows and Linux)
Product dependency
Product dependency
Product dependency
Windows, Linux
Table 19 lists the Linux, MP-RAS (RSG) and Windows products and dependencies on the
MetaData Services CD.
Table 19: MetaData Services CD
MetaData Services CD
Platforms (Windows, MP-RAS (RSG) and Linux)
Meta Data Services
Windows and Linux
Relay Services Gateway
Product dependency
Note: If these items were not received, contact the TSCS-RSC. See the Teradata Tools and
Utilities Release Definition, Release 13.0 for further instructions.
Note: For installation instructions for Teradata Query Director, see the Teradata Query
Director User Guide.
Note: For installation instructions for OLE DB Provider for Teradata, see the OLE DB
Provider for Teradata Installation and User Guide.
Note: For installation instructions for Meta Data Services, see the Teradata Meta Data Services
Installation and Administration Guide.
Note: For Windows products, see the Teradata Tools and Utilities Installation Guide for
Microsoft Windows.
48
CHAPTER 2
Before You Install
This chapter provides preliminary installation information and procedures that need to be
performed prior to installing Teradata Tools and Utilities software on IBM AIX, HP-UX, Sun
Solaris SPARC, Sun Solaris Opteron, Red Hat Linux and SUSE Linux client systems.
This chapter contains information on the following:
Installation Recommendations
Upgrading Teradata ARC
Teradata WebSphere Access Module
Technical Assistance
Before beginning the installation of Teradata Tools and Utilities software on an IBM AIX, HPUX, Sun Solaris SPARC, Sun Solaris Opteron, Red Hat Linux or SUSE Linux client systems,
verify that the software package ordered is complete (see Installation Kit Contents on
page 36) and that the client systems where the software will be installed are set up with the
required software and hardware. If the correct disks were not received, contact the TSCS-RSC.
Uninstalling Previous Versions

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.
Note: All 64-bit BTEQ packages on UNIX 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.
Installing Upgrade or Maintenance Software

Teradata makes information available to customers whenever software upgrades, higher-level
releases, or maintenance releases occur. Upgrades are normally available on CD-ROM.
49
Chapter 2: Before You Install

When installing the Teradata Client Tools and Utilities on UNIX, use the Korn shell (/bin/
ksh) before running setup.bat. This will ensure correct execution of the installation
script.
An exception is the Teradata Generic Security Services software, which does not have to be
uninstalled. See Teradata Generic Security Services on page 51.
Note: If a previous version of the 64-bit Solaris-SPARC ODBC driver was installed, it must
be uninstalled before installing the ODBC Driver for Teradata 13.00.00 to avoid
unpredictable results.
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.
To re-install a previous version of the software, the original Teradata Tools and Utilities disk
must be used.
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 Chapter 13: Troubleshooting.
Note: An exception is the Teradata Parallel Transporter software. Teradata Parallel
Transporter does not have to be uninstalled.
Installation of Dependent Products

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:
Shared Common Components for Internationalization for Teradata
The first message appears if a dependent product already exists, and its version is the same as
the dependent product being installed. It asks if the existing installed product can be installed.
For example, the following message is for the ODBC Driver for Teradata:
"ODBC Driver for Teradata 13.00.00.00 is already installed.
Do you want to reinstall it?"
The second message appears if a dependent product already exists and its version is not equal
to the dependent product being installed. It asks if the existing installed product can be
overwritten.
For example, the following message is for the ODBC Driver for Teradata:
"ODBC Driver for Teradata 12.00.00 is already installed.
Do you want to overwrite it with version 13.00.00?"
50


Multiple Versions of 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 the section on TDGSS File Maintenance Tools
in Teradata Database Security Administration guide for more information.
Upgrading 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. The softlink is a
pointer to /opt/teradata/client/<version>/bin/tpump. When upgrading from version
02.02.00.00 or later, the anomaly does not occur.
The solution is to first uninstall the existing version of TPump, and then upgrade to the new
version of TPump.
Upgrading 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>.
Softlinks from /usr/lib and /usr/bin will be created to /opt/teradata/client/<version>/lib and /
opt/teradata/client/<version>/bin respectively. Similarly, softlinks will be created for 64-bit
libraries and binaries.
To avoid installation errors while creating these softlinks, it is recommended to uninstall the
previous release of Teradata C Preprocessor2 and Teradata COBOL Preprocessor2 packages
before installing the Teradata Tools and Utilities 13.0 packages of Teradata C Preprocessor2
and Teradata COBOL Preprocessor2.
PUT Installations
Some of the Teradata Tools and Utilities products can be installed using the software Teradata
Parallel Upgrade Tool (PUT).
FastExport
FastLoad
MultiLoad
MQ Access Module
Shared Common Components for Internationalization for Teradata
51

TPump
See the Parallel Upgrade Tool (PUT) for UNIX MP-RAS and Linux for more information.
pkgadd Installations
On Sun Solaris operating systems, the pkgadd utility can install almost all of the Teradata Tools
and Utilities software.
When using pkgadd, the installer may not automatically select dependent products. See
System Requirements on page 30 to determine which products need to be installed
manually.
Tar Teradata Client Packages Install

Teradata packages can be installed across the network using Tar Teradata Client Packages.
The Tar Teradata Client Packages script is contained on the installation CD ROM. It allows the
creation of a subset of the Teradata client packages from the CD ROM media, and simple
copying of a single file across the network. See Chapter 9 Installing with Tar Teradata Client
Packages on page 149.
Available Disk Space

On Sun Solaris SPARC, the installation, may ask multiple questions depending on which
products were selected for installation. Afterwards, a check is done to ensure there is enough
disk space to install the software. This does not require any interaction unless there is not
enough space. In this case, the installation notifies which of the file systems are lacking space.
The main install screen will appear asking whether to remove packages or exit the installation
process to free up space. Assuming space is available on the system, the rest of the installation
is automatic.
A screen, similar to the following appears indicating how many packages were installed and if
any installation failed.
Teradata Tools and Utilities PACKAGE INSTALLATION
(Packages will now be installed onto the system.)
Number of packages to process: 1
Number successfully processed: 1
Failures: 0
All packages processed successfully.
Please see the logfile [/var/ncr/logs/pkgadd.log] for any specific
package instructions.
If a failure occurs, check the .log file and then contact TSCS-RSC.
LD_LIBRARY_PATH, SHLIB_PATH and LIBPATH

On Sun Solaris and Linux operating systems, the LD_LIBARY_PATH environment variable
must be exported for all Teradata Tools and Utilities products.
The following environment variables must be exported,
52

LD_LIBRARY_PATH on Sun Solaris, and Linux
SHLIB_PATH on HP-UX 32-bit
SHLIB_PATH or LD_LIBRARY_PATH on HP-UX 64-bit
LIBPATH on IBM AIX
for the following Teradata Tools and Utilities products:

The default installation location for Teradata ARC (ARC) on all UNIX platforms is now /opt/
teradata/client/<version>/bin. A softlink in /usr/bin/arcmain is created to point to /opt/
teradata/client/<version>/bin/arcmain.
To avoid installation errors while creating these softlinks, uninstall the previous release of
Teradata ARC before installing the Teradata Tools and Utilities 13.0 package for Teradata ARC.
Package Name Change on SUSE Linux

On SUSE Linux operating systems, a conflict exists with a Linux system package named arc,
therefore, the name of the Teradata ARC package has been changed in 13.00.00.00 from arc
to teradata_arc. To ensure a clean install with the new package name, uninstall the previous
arc package before installing the new teradata_arc package.
rpm -e arc
rpm -ivh teradata_arc-13.00.00.00-1.i386.rpm

Teradata Parallel Transporter is an object-oriented software system that executes multiple
instances of data extraction, transformation, and load functions in a scalable, high-speed
parallel processing environment. Teradata Parallel Transporter replaces the functionality
formerly seen in Teradata Warehouse Builder.
Teradata Parallel Transporter requires the installation of the Teradata Parallel Transporter
Infrastructure and the basic set of Teradata Parallel Transporter operators, such as Load,
Export, Update, and Stream. See Installation Recommendations on page 49.
53

Teradata Parallel Transporter Package Names

The package name for Teradata Parallel Transporter changes from release-to-release to
support multiple-installed versions of Teradata Parallel Transporter.
The format of the package name is <short name><short version>. For example, tbldd000 is
the package name for Teradata Parallel Transporter Infrastructure version 13.00.00.00.
In this version, the number of Teradata Parallel Transporter packages has been reduced from
15 to 6 packages.
Table 20 lists the short names for Teradata Parallel Transporter.
Table 20: Short Names for Teradata Parallel Transporter
Utility
Short Names
API
papi
Export Operator
pexp
Infrastructure
tbld
Load Operator
plod
Stream Operator
pstm
Update Operator
pupd
Uninstalling Teradata Warehouse Builder and Teradata Parallel

Transporter Packages
It is not necessary to uninstall previous versions of Teradata Warehouse Builder or its
replacement, Teradata Parallel Transporter, prior to installing a new version of the Teradata
Parallel Transporter. Multiple versions may coexist on a system.
To uninstall either an older version of Teradata Warehouse Builder or a previously installed
version of Teradata Parallel Transporter software from a system, a tool named twbpkgrm is
included in the Teradata Parallel Transporter Infrastructure package, version 13.00.00.00.
The twbpkgrm Tool
The twbpkgrm tool can be found in the /usr/bin directory.
Note: The twbpkgrm tool requires Perl version 5.0 or above to be installed on the system. The
path to the Perl executable must be in the PATH environment variable. Versions of Perl can be
downloaded from the website:
http://www.perl.com
The following lists the usage for the twbpkgrm tool:
Usage: twbpkgrm [-a] [-h] [-p <package(s)>] [-t <trace file>]
54
-a option uninstalls all versions of Teradata Warehouse Builder and Teradata Parallel
Transporter software on the system

-h option displays the usage
-p option uninstalls the specified <package(s)> on the system. Multiple packages can be
specified within single or double quotes, and separated by space. For example:
twbpkgrm -p "pseld000 pexpd000"
Package(s) will be uninstalled in the order specified
-t option enables trace information for this program and saves the trace information in
the <trace file>.
Note: Options -a, -h, and -p are mutually exclusive.

Note: All options are case-sensitive.
When run with no options, the twbpkgrm tool appears, displaying information on installed
Teradata Warehouse Builder and Teradata Parallel Transporter versions.
When twbpkgrm tool is run with no options, the following additional functions can be
performed:
Remove all installed Teradata Parallel Transporter packages (selection a). Use caution
when removing all versions of Teradata Parallel Transporter.
Sort Teradata Parallel Transporter software name in ascending order (selection b)
Sort Teradata Parallel Transporter software name in descending order (selection c)
Sort Teradata Parallel Transporter package name in ascending order (selection d)
Sort Teradata Parallel Transporter package name in descending order (selection e)
Sort Teradata Parallel Transporter version number in ascending order (selection f)
Sort Teradata Parallel Transporter version number in descending order (selection g)
Quit the twbpkgrm tool (selection q)
Note: Sorting is performed within the Teradata Parallel Transporter and Teradata Warehouse
Builder software groups.
The selection in the twbpkgrm tool is case sensitive. The twbpkgrm tool will remain in the
/usr/bin directory even after Teradata Parallel Transporter software is uninstalled. To remove
the twbpkgrm tool in the /usr/bin directory, logon as the root user and enter the rm /usr/bin/
twbpkgrm command:
# rm /usr/bin/twbpkgrm
Uninstalling Teradata Warehouse Builder or Teradata Parallel

Transporter
Use one of the following procedures to uninstall a Teradata Warehouse Builder or Teradata
Parallel Transporter package.
Method 1 - uninstalling Teradata Warehouse Builder or Teradata Parallel Transporter with

twbpkgrm with no options
Method 2 - uninstalling Teradata Warehouse Builder or Teradata Parallel Transporter with

twbpkgrm with -p option selected
Method 3 -uninstalling Teradata Warehouse Builder or Teradata Parallel Transporter with

twbpkgrm with -a option selected
55

Uninstalling Teradata Parallel Transporter with Method 1
Procedure - Uninstalling Teradata Parallel Transporter with Method 1

Follow these steps to uninstall Teradata Warehouse Builder or Teradata Parallel Transporter
with twbpkgrm with no options selected.
1
Log on as the root user.
Run the twbpkgrm tool with no options.

# /usr/bin/twbpkgrm
twbpkgrm Version 12.00.00.00
File revision: 12.00.00.00
Copyright 2005-2008, Teradata Corporation. All Rights Reserved.
Platform: UNIX
Checking for Teradata Parallel Transporter and Teradata Warehouse
Builder
software. This may take several seconds. Please wait ...
Here is the currently installed Teradata Parallel Transporter (TPT)
software:
Num Software
Package
Version
Install
Directory
=== ========
=======
=======
=================
1 TPT Infrastructure tbldc000 12.00.00.00 /usr/tbuild/12.00.00.00
2 Operator Support Library poslc000 12.00.00.00 /usr/tbuild/
12.00.00.00
3 Data Connector Operator pdtcc000 12.00.00.00 /usr/tbuild/
12.00.00.00
4 DDL Operator pddlc000 12.00.00.00 /usr/tbuild/12.00.00.00
5 Export Operator pexpc000 12.00.00.00 /usr/tbuild/12.00.00.00
6 Load Operator plodc000 12.00.00.00 /usr/tbuild/12.00.00.00
7 ODBC Operator podbcc000 12.00.00.00 /usr/tbuild/12.00.00.00
8 OS Command Operator poscc000 12.00.00.00 /usr/tbuild/12.00.00.00
9 SQL Inserter Operator pinsc000 12.00.00.00 /usr/tbuild/12.00.00.00
10 SQL Selector Operator pselc000 12.00.00.00 /usr/tbuild/
12.00.00.00
11 Stream Operator pstmc000 12.00.00.00 /usr/tbuild/12.00.00.00
12 Update Operator pupdc000 12.00.00.00 /usr/tbuild/12.00.00.00
13 TPT API
papic000 12.00.00.00 /usr/tbuild/
12.00.00.00
Here is the currently installed Teradata Warehouse Builder (TWB)
software:
Num Software
Directory
=== ========
=================
14 PIPC for TWB
15 TWB Infrastructure
05.00.00.00
16 TWB Infrastructure
56
Package
Version
Install
=======
=======
pipc
tbld5000
02.04.00.00
05.00.00.00
/etc/pipc
/usr/tbuild/
tbuild
04.01.00.00
/usr

17 Operator Support Library posl5000
05.00.00.00
05.00.00.00
18 Operator Support Library pcommon
01.04.00.00
19 Data Connector Operator
pdtc5000
05.00.00.00
05.00.00.00
20Data Connector Operator
pdatacon
03.01.00.00
21 DDL Operator
pddl5000
05.00.00.00
05.00.00.00
22 DDL Operator
pddl
01.01.00.00
23 Export Operator
pexp5000
05.00.00.00
05.00.00.00
24 Export Operator
pexport
02.04.00.00
25 Load Operator
plod5000
05.00.00.00
05.00.00.00
26 Load Operator
pload
03.04.00.00
27 ODBC Operator
podbc5000 05.00.00.00
05.00.00.00
28 ODBC Operator
podbc
01.01.00.00
29 OS Command Operator
posc5000
05.00.00.00
05.00.00.00
30 SQL Inserter Operator
pins5000
05.00.00.00
05.00.00.00
31 SQL Inserter Operator
pinsert
04.01.00.00
32 SQL Selector Operator
psel5000
05.00.00.00
05.00.00.00
33 SQL Selector Operator
pselect
04.01.00.00
34 Stream Operator
pstm5000
05.00.00.00
05.00.00.00
35 Stream Operator
pstream
01.03.00.00
36 Update Operator
pupd5000
05.00.00.00
05.00.00.00
37 Update Operator
pupdate
01.04.00.00
a
b
c
d
e
f
g
q
/usr/tbuild/
/usr
/usr/tbuild/
/usr
/usr/tbuild/
/usr
/usr/tbuild/
/usr
/usr/tbuild/
/usr
/usr/tbuild/
/usr
/usr/tbuild/
/usr/tbuild/
/usr
/usr/tbuild/
/usr
/usr/tbuild/
/usr
/usr/tbuild/
/usr
Remove all of the above package(s)

Sort by software in ascending order
Sort by software in descending order
Sort by package in ascending order
Sort by package in descending order
Sort by version in ascending order
Sort by version in descending order
Quit this program
Which package(s) do you want to remove?

Enter selection and/or selection ranges separated by commas.
For examples: 1,2-3
Enter a selection.
12
The system will ask for confirmation.

Are you sure you want to remove the following software?
Num Software
Package
Version
=== ========
=======
=======
12 Update Operator pupdc000 12.00.00.00 /usr/tbuild/12.00.00.00
Enter y for yes or n for no [ default: y ]: y
Enter Y to confirm that the package(s) should be uninstalled.

Removing package <pupdc000> version 12.00.00.00. Please wait ...
57

The following package is currently installed:
pupdc000 Teradata Parallel Transporter Update Operator
(AT486) 12.00.00.00
Do you want to remove this package [y,n,?,q] y
Enter Y to confirm that the package is the correct version to uninstall.

##
##
##
##
##
##
##
Removing installed package instance <pupd8100>

Verifying package dependencies.
Processing package information.
Removing pathnames in <none> class
Executing postremove script.
Removing Entries from Update Directory
Updating system information.
Removal of <pupdc000> was successful.
In the example above, Teradata Parallel Transporter Update Operator, version

12.00.00.00, was selected by entering 12. Entering y confirmed the selection, and
initiated its uninstallation.
Note: Only a user logged in as root user can remove a package on the system.
Note: The selection number may vary from the example, depending on the system
configuration, selecting 12 may not always select Teradata Parallel Transporter Update
Operator version 12.00.00.00.
Another way to remove a Teradata Parallel Transporter package is to be the root user, run the
twbpkgrm tool with the -p option and valid Teradata Parallel Transporter package name(s),
enter y to confirm that the package(s) should be uninstalled. Multiple packages can be
specified within single or double quotes and separated by space. Package(s) will be removed in
the order specified.
For example, to remove pupd8100 package (Teradata Parallel Transporter Update Operator
version 12.00.00.00), run twbpkgrm -p pupdc000 as the root user and y to confirm that the
pupdc000 package should be removed.

with twbpkgrm with the -p option selected.
1
Run the twbpkgrm tool with the -p option.

For example:
# /usr/bin/twbpkgrm -p pupd8100
A screen similar to the following appears:

Copyright 2005-2008, Teradata Corporation. All Rights Reserved.
User specified package to be removed: 'pupdc000'
58

NOTE: Package(s) will be removed in the order specified.

Are you sure you want to remove the <pupdc000> package?
Enter Y to confirm that the package should be uninstalled.

Removing package <pupdc000>. Please wait ...
<pupdc000> Teradata Parallel Transporter Update Operator
(AT486) 12.00.00.00

##
##
##
##
##
##
##
Removing installed package instance <pupdc000>

Note: You must be the root user in order to uninstall a package on the system
The following procedure is another example of using the -p option. The procedure
uninstalls two packages, pupdc000 package (Teradata Parallel Transporter Update Operator
version 12.00.00.00), and pexpc000 package (Teradata Parallel Transporter Export Operator
version 12.00.00.00).
Uninstalling Teradata Parallel Transporter with Method 2, Multiple
Package Names
Procedure - Uninstalling Teradata Parallel Transporter Using Method 2 with Multiple

Package Names
Follow these steps to uninstall more than one Teradata Warehouse Builder or Teradata Parallel
Transporter package with a single command.
1
Run the twbpkgrm tool with the -p option with a list of the programs to uninstall.
For example:
# /usr/bin/twbpkgrm -p "pupd8100 pexp8100"
Copyright 2005-2008, Teradata Corporation. All Rights
Reserved.Platform: <operating system>
User specified package(s) to be removed: 'pupdc000 pexpc000'
NOTE: Package(s) will be removed in the order specified.
59

Are you sure you want to remove the following package(s)? <pupdc000
pexpc000>
Enter Y to confirm the pupdc000 and pexpc000 packages should be uninstalled:

Removing package(s) <pupdc000 pexpc000>. Please wait ...
pupdc000 Teradata Parallel Transporter Update Operator
(AT486) 12.00.00.00

##
##
##
##
##
##
##
Removing installed package instance <pupdc000>


pexpc000 Teradata Parallel Transporter Export Operator
(AT486) 12.00.00.00

##
##
##
##
##
##
##
Removing installed package instance <pexp8100>

Removal of <pexpc000> was successful.
Note: Log on as the root user to uninstall a package on the system

All the packages contained in Teradata Parallel Transporter can be uninstalled at one time
using the -a option to the twbprgm command.

using twbpkgrm with the -a option selected.
60
Run the twbpkgrm tool with the -a option.

For example:

# /usr/bin/twbpkgrm -a
Note: Use caution when uninstalling all versions of Teradata Parallel Transporter.
Teradata Parallel Transporter Install Information File

The /var/twbpkg file stores Teradata Parallel Transporter installation information. No backup
file exists for the /var/twbpkg file.
Caution:
Do not modify the /var/twbpkg file.

Modification or uninstallation of the /var/twbpkg file causes installation and uninstallation
problems for Teradata Parallel Transporter.
When all packages of Teradata Parallel Transporter software are properly uninstalled from the
system, the /var/twbpkg file is properly uninstalled by the Teradata Parallel Transporter
uninstall program.
Switching Back to the Installed Teradata Parallel Transporter Version

To switch back to the installed Teradata Parallel Transporter version, use one of the following
two methods.
Method 1 - Update Environment Variables at the Command Prompt
Method 2 - Update Environment Variables in the System Login Files for a Shell User
Switching the Parallel Transporter Version Using Method 1
Procedure - Switching the Teradata Parallel Transporter Version using Method 1

Follow these steps to switch the Teradata Parallel Transporter Version by updating
environment variables at from the command prompt.
1
Find the Teradata Parallel Transporter installation directory by running the

/usr/bin/twbpkgrm tool with no options.
/usr/bin/twbpkgrm
Set the TWB_ROOT environment variable to the installation directory of the installed
Teradata Parallel Transporter version.
Bourne and Korn shell users, enter these commands:
# TWB_ROOT=<Teradata Parallel Transporter installation directory>
# export TWB_ROOT
<Teradata Parallel Transporter installation directory> is the Teradata Parallel Transporter

installation directory.
C-shell users, enter this command:
# setenv TWB_ROOT <Teradata Parallel Transporter installation
directory>

3
Add the $TWB_ROOT/bin path to the PATH environment variable.
61

Bourne and Korn shell users, enter these commands:

# PATH=$TWB_ROOT/bin:$PATH
# export PATH
C-shell users, enter this command:

# setenv PATH $TWB_ROOT"/bin:$PATH"
This method is only valid for the duration of the logon.

Switching the Parallel Transporter Version Using Method 2
Procedure - Switching the Teradata Parallel Transporter Version using Method 2

Follow these steps to switch the Teradata Parallel Transporter Version by updating
environment variables in the system login files for a shell user.
1
Log on as the root user to perform this procedure. This method applies to the system for all
users in the next logon.
Bourne/Korn shell users: The system login file is /etc/profile on HP-UX, AIX, Sun Solaris,
and Linux.
C-shell users: The system login file is /etc/csh.login for HP-UX, Linux, and AIX. The system
login file is /etc/.login for Sun Solaris.
Find the Teradata Parallel Transporter installation directory by running the

/usr/bin/twbpkgrm tool with no options.
# /usr/bin/twbpkgrm
Set the TWB_ROOT environment variable to the installation directory of the installed
Teradata Parallel Transporter version in the system login files for shell users.
Bourne and Korn shell users: In the system login file, add these lines to the file:
TWB_ROOT=<Teradata Parallel Transporter installation directory>
export TWB_ROOT
Note: <Teradata Parallel Transporter installation directory> is the Teradata Parallel

Transporter installation directory.
C-shell users, add these lines to the system login file:
setenv TWB_ROOT <Teradata Parallel Transporter installation
directory>
Note: <Teradata Parallel Transporter installation directory> is the Teradata Parallel

4
Add the $TWB_ROOT/bin path to the PATH environment variable in the system login
files for shell user.
Bourne and Korn shell users, add these lines to the system login file:
if [ "$PATH" = "" ]; then
PATH="$TWB_ROOT"/bin
else
PATH="$TWB_ROOT"/bin:"$PATH"
fi
export PATH
62

C-shell users, add these lines to the system login file:

if {$?PATH} then
setenv PATH $TWB_ROOT"/bin:$PATH"
else
setenv PATH $TWB_ROOT/bin
endif
This method applies to the system for all users in the next logon.

This section discusses general information about the Teradata Generic Security Services
feature. It describes how to remove TeraGSS packages and switch versions. See Chapter 12:
Connecting to a Teradata Database, for additional information on security and logging onto
Teradata.
TeraGSS Package Names

With the exception of the Teradata Generic Security Service package for TeraGSS, all of the
Teradata Generic Security Service packages include the target architecture as part of the
package name. For example, the Teradata Generic Security Service package for Sun Solaris
TeraGSS_solaris-sparc.
The architecture is not included as part of the package name (the package name is TeraGSS)
due to a restriction on the length of the package name.
Uninstalling TeraGSS Packages

It is not necessary to uninstall previous versions of TeraGSS prior to installing a new version,
multiple versions of TeraGSS may coexist on a node. TeraGSS software can be removed from a
node using the tdgsspkgrm utility included in the installation package. This allows cleanup up
of obsolete (non-current versions) of TeraGSS.
The tdgsspkgrm utility can be found at /usr/teragss/<architecture>/client/bin/tdgsspkgrm, where
<architecture> is the architecture for the TeraGSS package.
For example: solaris-sparc.
# tdgsspkgrm -h
Usage: tdgsspkgrm [version to remove]
e.g. tdgsspkgrm 12.00.00.00
Procedure - Removing the TeraGSS Package

Follow these steps to remove obsolete, non-current versions of the TeraGSS package from the
client.
63

1
Run the tdgsspkgrm tool without any options to list the versions of TeraGSS installed.
For example:
# tdgsspkgrm
When run with no arguments, the tdgsspkgrm utility lists information about installed
versions.
TeraGSS current version:
12G.02.00.00
TeraGSS versions available for removal:
12H.02.00.00
To remove an obsolete version, run tdgsspkgrm and specify the version to uninstall.
For example:
# tdgsspkgrm 12H.02.00.00
Note: The current version cannot be uninstalled using tdgsspkgrm. To uninstall the current
version, use the appropriate utility for the operating system.
Switching Versions of TeraGSS Software

Switching between installed versions of TeraGSS software is allowed. After a new version of
TeraGSS is installed, the new version can be set as the current version. The switch must be
done manually. To facilitate version switching, a utility named tdgssversion is included in the
package.
The tdgssversion utility is located at:
usr/TeraGSS/<architecture>/client/bin/tdgssversion
Usage: tdgssversion [-switch nn.nn.nn.nn]

where: <architecture> is the architecture for the TeraGSS package.
For example: solaris-sparc.
where: nn.nn.nn.nn is the version of TeraGSS.
Procedure - Switching between versions of TeraGSS

Follow these steps to switch between versions of TeraGSS.
1
Run the tdgssversion tool without any options to list the versions of TeraGSS installed, by
entering:
# tdgssversion
In the following example, the output indicates the Teradata GSS Client available versions
are: 12H.02.00.00 and 12G.02.00.00 *. The asterisk (*) denotes the current version.
TeraGSS current version:
12G.02.00.00*
TeraGSS versions available for removal:
12H.02.00.00
64

3
To switch to the 12H.02.00.00 version enter:

# tdgssversion -h

Manual Install for Teradata WebSphere MQ Access Module
Teradata WebSphere MQ Access Module cannot be automatically installed using the Load/
Unload installation CD on Hewlett-Packard HP-UX 11i v2 (11.23) and 11i v3 (11.31) with
Intel Itanium. Several libraries must be manually copied from the /HP-UX/mqaxsmod/ia64
directory on the Load/Unload installation CD.
Before copying the libraries, ensure the following Teradata WebSphere MQ Access Module
product dependencies have been installed in the correct order.
Teradata Data Connector 13.00.00
IBM WebSphere MQ (HP-UX) 5.2
Table 21 lists the libraries and the corresponding directories where the file must be copied. An
asterisk (*) after a file name indicates a softlink for files located in this directory:
/opt/teradata/client/<version>/hpux64.
Table 21: Teradata WebSphere MQ Access Module Libraries on HP-UX Itanium
HP-UX Itanium
Directory
libmqs.so*
/usr/lib/hpux64
libmqsc.so*
/usr/lib/hpux64
libmqs.so
/opt/teradata/client/<version>/hpux64
libmqsc.so
/opt/teradata/client/<version>/hpux64
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.00.00.
65

66
CHAPTER 3
Installing on IBM AIX Client Systems
This chapter contains the procedures to install and uninstall the Teradata Tools and Utilities
software on IBM AIX client systems.
Installing Individual Products
Uninstalling Previous Versions of Software
Installing Teradata Tools and Utilities
Installing Teradata Parallel Transporter
Installing the Teradata Access Module for JMS
Adding CLI User Exit Functions

This section describes how to install individual Teradata Tools and Utilities products on an
IBM AIX operating system.
IBM AIX Operating Systems Supported

Installation CD-ROMs
Install Teradata Tools and Utilities products using setup.bat from one of the following CDs:
Database Management
67
Chapter 3: Installing on IBM AIX Client Systems

Installation/Uninstallation Order
IBM AIX Packages

Teradata Tools and Utilities application packages can be installed and uninstalled manually,
provided they are installed or uninstalled in the proper order. To avoid manually induced
installation errors, use the Teradata installation script provided (setup.bat) to install Teradata
Tools and Utilities packages. The script follows the correct installation order and loads the
required dependencies.
Installation Order
If installing the Teradata Tools and Utilities application packages manually, install the
dependent packages first, in this order.
Warning:
Teradata Generic Security Services (TeraGSS)
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.
Shared Common Components for Internationalization for Teradata (tdicu)
Teradata Data Connector (piom)
Then, all other non-dependent Teradata Tools and Utilities applications can be installed, in
any order.
Uninstallation Order
When removing the Teradata Tools and Utilities application packages, the packages should be
removed in reverse order.
68
All non-dependent Teradata Tools and Utilities Applications, in any order


Prior to installing Teradata Tools and Utilities, check for existing versions of the software and
uninstall them by performing the following:
Note: Teradata Parallel Transporter software does not have to be uninstalled.
Note: Teradata Generic Security Services (TeraGSS) software, does not have to be uninstalled.
Procedure - Uninstalling Previous Versions of Teradata Tools and Utilities Software

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.
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:
For bteq, a screen similar to the following appears.
root@stationb: [/] > /usr/bin/lslpp -l bteq.bteq
Fileset
Level State
Description
--------------------------------------------------------------------Path: /usr/lib/objrepos
bteq.bteq 12.0.0.0 COMMITTED Teradata BTEQ Application
(12.00.00.000) for
IBM-AIX
5.1/5.2
Path: /etc/objrepos
bteq.bteq 12.0.0.0 COMMITTED
Teradata BTEQ Application

(12.00.00.000) for
IBM-AIX
5.1/5.2
Note: For TeraGSS packages, the command is:

lslpp -l <clientPkgName>.<clientPkgName>_<version>
For example:
69

To list the installed versions of TeraGSS_aix-power, use the following command:

lslpp -l TeraGSS_aix-power.*
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, a screen similar to the following appears.
root@stationb: [/] > installp -u cliv2
+----------------------------------------------------------------+
Pre-deinstall Verification...
+----------------------------------------------------------------+
Verifying selections...done
Verifying requisites...done
Results...
SUCCESSES
--------Filesets listed in this section passed pre-deinstall verification
and will be removed.
Selected Filesets
----------------cliv2.cliv2 12.0.0.0
# TTU8.2 Teradata CLIV2 packag...
<< End of Success Section >>
FILESET STATISTICS
-----------------1 Selected to be deinstalled, of which:
1 Passed pre-deinstall verification
---1 Total to be deinstalled
+----------------------------------------------------------------+
Deinstalling Software...
+----------------------------------------------------------------+
installp: DEINSTALLING software for:
cliv2.cliv2 12.0.0
Removing CLI environment variables from /etc/profile
Finished processing all filesets. (Total time: 5 secs).
+----------------------------------------------------------------+
Summaries:
+----------------------------------------------------------------+
Installation Summary
-------------------Name
Level
Part
Event
Result
-----------------------------------------------------------------cliv2.cliv2
12.0.0.0 ROOT
DEINSTALL
SUCCESS
cliv2.cliv2 12.0.0.0 USR
DEINSTALL
SUCCESS
------------------------------------------------------------------
Software Name Truncation

During the installation, software names may become truncated.
For example, the Teradata Parallel Transporter Update Operator:
Selected Filesets
-----------------pupdd000 13.0.0.0
#Teradata Parallel Transporter U...
To find the complete software name, enter one of the following commands at the prompt:
70

lslpp -l <clientPkgName>.<clientPkgName>
or
lslpp -l <clientPkgName>
The following is an example of the Teradata Parallel Transporter Update Operator:

# lslpp -l pupdd000
Fileset
Level
Path: /usr/lib/objrepos
pupdd000
13.0.0.0
State
Description
COMMITTED
Update Operator Version 13.00.00.00
Teradata Parallel Transporter Default and Alternate Directory

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.00.00.00 is:
/opt/teradata/client/13.0/tbuild
Installation Directory Restrictions

The following are the restrictions on the installation directory 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
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.00.00.01
overwrites the Teradata Parallel Transporter Infrastructure 13.00.00.00 package.
Silent Installation of ODBC

TDODBC_SILENT_INSTALL_DIR is an environment variable for the AIX silent install
feature for both the 32-bit and 64-bit AIX installations. Setting the
TDODBC_SILENT_INSTALL_DIR environment variable to the install directory path
71

bypasses prompting a user for the install path and uses the
TDODBC_SILENT_INSTALL_DIR value as the install directory for the AIX installation.
In the Korn Shell:
TDODBC_SILENT_INSTALL_DIR=<installpath>;
export TDODBC_SILENT_INSTALL_DIR
Or, in the C Shell:

setenv TDODBC_SILENT_INSTALL_DIR <installpath>
where <installpath> is the install directory path for the user portion of the TTU install.
For example:
/opt

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.
If a /mnt directory does not exist, create one:

# mkdir /mnt
Insert the installation CD 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:

# cd /mnt
# ./setup.bat
For the Load/Unload CD, a screen similar to the following appears:

Welcome to the Teradata Tools and Utilities 13.00.00.00 installation
Copyright 2008. Teradata Corporation. All Rights Reserved.
Media: Load/Unload
Platform: AIX
Which software
1. TeraGSS
2. tdicu
3. tdodbc
4. cliv2
5. piom
6. npaxsmod
72
do you want to install?

- Teradata GSS client package
- Teradata Shared Component for Internationalization
- Teradata ODBC Driver
- Teradata CLIv2
- Teradata Data Connector API
- Teradata Named Pipes Access Module

7.
8.
9.
10.
11.
12.
mqaxsmod
bteq
fastexp
fastld
mload
tpump
Teradata
Teradata
Teradata
Teradata
Teradata
Teradata
WebSphere(r) MQ Access Module

BTEQ Application
FastExport Utility
FastLoad Utility
MultiLoad Utility
TPump Utility
a. Install all of the above software

u. Remove previously installed Teradata Tools and Utilities software
q. Quit the installation
Enter one or more selection (separated by space):
Software must be installed in the order shown in Software Requirements on page 31.
After reviewing product dependencies, enter the products to install at the prompt:
One or more numbers for the product(s), separated by spaces, or
a to install all the software,
u to uninstall all the software, or
q to quit the installation
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
Remove the installation CD from the CD-ROM drive.

This section contains instructions for installing the Teradata Parallel Transporter on IBM AIX.
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.0/
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.
73

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 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.0/
tbuild/logs ]:
When prompted, press the Enter key, to use the default logs directory.
Logs Directory Restrictions
The following are the logs directory restrictions for Teradata Parallel Transporter:
The logs directory cannot be a relative directory path
The whitespace character cannot be in the name of the logs directory
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 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.
The memory mapped file directory
Transporter job files.
free space.
Please specify the memory mapped
teradata/client/13.0/tbuild/mmap
contains temporary Teradata Parallel

should be in a partition with a large
file directory [ default: /opt/
]:
Respond by pressing the Enter key, to use the default memory mapped file directory.
Memory Mapped File Directory Restrictions
The following are the memory mapped file directory restrictions for Teradata Parallel
Transporter:
74
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 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.
Updating Environment Variables
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.
Table 22 lists the Environment variables updated.
Table 22: Environment Variables Updated
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.
LIBPATH
Add $TWB_ROOT/lib to the front of the LIBPATH

NLSPATH
Add $TWB_ROOT/msg/%N to the front of the

NLSPATH environment variable.
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
$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.
75

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: The updates to the environment variables must be used to run the installed version of
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.

and Utilitiess Release 13.00.00. The driver files, readme.txt, terajdbc4.jar and tdgssconfig.jar,
Installing the Teradata JDBC Driver from the Download Center

The Teradata JDBC Driver can also be downloaded from the Teradata Download Center at:
The files are copied into a directory of choice. The files are machine independent.
Driver.

The Teradata Access Module for JMS version 13.00.00 must be downloaded from the Teradata
Download Center at:
76


CLI User Exit functions are general purpose facilities that can be added to the CLI workstation
architecture on IBM AIX systems. These functions allow user-defined processing to take place.
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.
1
Change directories to /opt/teradata/client/sample, using the following command:

# cd /opt/teradata/client/sample
Modify the CliLgnEx.c or CliPPS.c file in the sample directory.
Compile and link using either the 32-bit or 64-bit version of the makefile to create a new
shared object, libtdusr32.so. This command compiles the 32-bit version:
# make -f maketdusr.aix
Move the libtdusr32.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.
77

78
CHAPTER 4
Installing on HP-UX Client Systems
This chapter contains the procedures to install and uninstall Teradata Tools and Utilities
software on HP-UX client systems.
Uninstalling Previous Versions of HP-UX Software
Installing the Teradata Tools and Utilities

This section describes the HP-UX operating systems supported and the Teradata Tools and
Utilities products that can be installed on them.
HP-UX Operating Systems Supported

Database Management
79
Chapter 4: Installing on HP-UX Client Systems

HP-UX Packages
Installation Order
Warning:
any order.
80

Uninstalling Previous Versions of HP-UX

Software
Prior to the installing Teradata Tools and Utilities, check for existing versions of the software
and uninstall them by performing the following procedure.
Note: Previous versions of Teradata Call-Level Interface version 2 (cliv2) software must be
uninstalled before installing a newer version.
Note: Teradata Generic Security Services (TeraGSS) software, does not have to be uninstalled.
Note: Teradata Parallel Transporter does not have to be uninstalled.

installed on HP-UX client systems.
1
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>
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)
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>
81

Uninstalling at the HP-UX Terminal Interface Window

Optionally, the HP-UX Terminal Interface Window can uninstall Teradata Tools and Utilities
software from the HP-UX client system.
Procedure - Uninstalling Teradata Tools and Utilities Software Using the HP-UX Terminal
Interface Window
Follow these steps to uninstall Teradata Tools and Utilities software using the HP-UX Terminal
Interface Window.
1
Prior to installing new versions of the Teradata Tools and Utilities, check for previous
versions of the software:
/usr/sbin/swlist <PkgName>
Activate the SD Remove interface window:

/usr/sbin/swremove
Select the products to remove:

a
In the SD Remove window, use the Tab and Arrow keys to move the highlight bar to the
name of the package being removed.
Press Space Bar to select the package.
In the upper menu bar, use the Tab key to move across to Actions.
Use the Arrow key to move down to Mark For Remove, then press Space Bar.
A Yes appears under the Marked? column in front of the product name. This indicates it
has been designated for removal.
82
Repeat Step 4 for each product being removed.
Remove the selected product packages:

a
In the upper menu bar, use the Tab key to move across to Actions and press Space Bar.
In the Actions menu, press R. Or, use the Arrow key to move down to Remove
(analysis)... then press the Space Bar.
After an analysis of the system is successfully completed, Ready appears in the Status line
of the Remove Analysis window.
7
If the removal setup is correct, highlight OK and press Enter. Otherwise, return to the
previous menu, press Tab to highlight the word Cancel. Then press Space Bar.
In the confirmation display that appears, confirm the removal. Highlight Yes and press the
Space Bar. Otherwise, press Tab to move to the word No. Then press Space Bar.
Complete the removal process, highlight Done. Then press Space Bar.
The updated list of the installed packages appears in the Remove window.
83

10 Exit the process:
a
In the upper menu bar, highlight File and press Space Bar.
In the File menu, press E. Or, highlight Exit and press Space Bar.
Teradata Parallel Transporter Default and Alternate Directory

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.00.00.00 is:
/opt/teradata/client/13.0/tbuild

The following are the installation directory restrictions for Teradata Parallel Transporter:
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.
84


The Teradata Tools and Utilities can be installed silently or interactively through the external
interface window. These two methods are described below.
Note: Teradata Parallel Transporter packages cannot be installed interactively through the
external interface window. Teradata Parallel Transporter packages can only be installed using
the silent mode.
Installing Teradata Tools and Utilities Products Silently

This section contains the procedures to install Teradata Tools and Utilities products silently.
Teradata Parallel Transporter packages must be installed using this method.
Procedure - Installing Teradata Tools and Utilities Products Silently on HP-UX

Follow these steps to install the Teradata Tools and Utilities products silently on HP-UX client
operating systems:
1
Log on to the HP-UX client as the root user.

# mkdir /mnt

3
Insert the installation CD 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
To begin the installation process, enter:

# cd /mnt
# ./setup.bat
A screen similar to the following appears.

Welcome to the Teradata Tools and Utilities 13.0 installation
Copyright 2002-2008. Teradata Corporation. All Rights Reserved.
Media: Load/Unload
Platform: HP-UX
Which software do you want to install?
1. TeraGSS - Teradata GSS client package
2. tdicu
3. tdodbc
4. cliv2
- Teradata CLIv2
5. piom
6. npaxsmod
7. mqaxsmod
- Teradata WebSphere(r) MQ Access Module
85

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):
Note: Teradata Parallel Transporter packages are contained on Load/Unload CD #2.

5
Software must be installed in the order shown in Product Dependencies on page 31.
After reviewing product dependencies, enter a selection:
One or more numbers for the product(s) being installed, separated by spaces, or
Change back to the root directory, and unmount the CD:

# umount /mnt
Installing Teradata Tools and Utilities Products Interactively

Teradata Tools and Utilities products can also be installed interactively.
Note: Teradata Parallel Transporter packages cannot be installed interactively through the
HP-UX external interface window. Teradata Parallel Transporter packages can only be
installed using the silent mode.
Procedure - Installing Teradata Tools and Utilities Products Interactively

Follow these steps to install the Teradata Tools and Utilities interactively:
1
Log on to the HP-UX UNIX client as root.
If a /mnt directory does not exist, create one by entering the following command at the
prompt:
# mkdir /mnt
where: the CD-ROM mount point is /mnt, although an alternate can be used.
3
Insert the installation CD into the CD-ROM drive, and then enter the following at the
command prompt:
# mount /dev/dsk/<device name> /mnt
If the CD-ROM device name is c0t1d0enter:

# mount /dev/dsk/c0t1d0 /mnt
where: the CD-ROM mount point is /mnt, although an alternate may be entered.
Note: To find a CD-ROM device, enter the following at the command prompt:
86

ioscan -fnC disk
Register the CD-ROM containing the installation software as the depot by entering the
following at the command prompt:
# /usr/sbin/swreg -l depot /mnt/HP-UX/<package dirname>
where: the term -l uses the lower case letter L.

5
Install the utilities using the terminal interface window by entering the following at the
command prompt:
swinstall
If Press Return appears in the swinstall help screen, press Enter.

6
Go to Source Depot and select the product in the Source Depot Path.
In the Install screen of the HP-UX terminal interface window, perform the following:
a
In the Bundles and Products list, highlight the product being installed.
In the upper menu bar, press Tab to move the cursor to Actions, then press Space Bar.
In the Actions menu, press M to mark the product for installation.
Highlight OK, then press Enter.
Press Space Bar to select the product.
10 In the Actions menu, select Install (Analysis).
The Install Analysis window appears. After an analysis of the system is completed, Ready
appears in the Status line.
11 If the installation setup is correct, highlight OK and press Enter.
Otherwise, press Tab to highlight the word Cancel, and then press Space Bar to halt the
process and return to the previous menu.
12 In the confirmation display that appears, highlight Yes and press Space Bar to confirm the
installation.
Otherwise, Tab to move the cursor to No and press Space Bar.
87

After confirmation, the installation begins. The Install window reappears, similar to the
one shown below.
The Percent Complete line monitors installation progress. When the installation is
complete, Completed appears in the Status line.
Monitor the progress of the installation by selecting the Logfile.

13 After the installation is completed, highlight Done and press Enter.
The updated list of installed products appears in the SD Install window.

14 To exit the process:
a
In the upper menu bar, highlight File and press Space Bar.
In the File menu, press E. Or, highlight Exit and press Space Bar.
15 To verify the package is installed, use the swlist command:

# /usr/sbin/swlist <PkgName>
16 To change back to the root directory and unmount the CD, enter:
# umount /mnt
17 Remove the installation CD from the CD-ROM drive.

This section contains instructions for installing the Teradata Parallel Transporter on HP-UX.
The installation of a new version of Teradata Parallel Transporter prompts for the Teradata
tbuild]:
Press Enter to use the default install directory.
88

The restrictions for the Teradata Parallel Transporter installation directory include:
Do not use / or /usr as the installation directory.
Logs Directory
Transporter Infrastructure package prompts for the location of the Teradata Parallel
Transporter logs directory.
tbuild/logs ]:
Press Enter to use the default logs directory.

The restrictions for the Teradata Parallel Transporter logs directory include:

memory choice.
Press Enter or 1, to make the IPC memory choice shared memory.

Or, press 2, to make the IPC memory choice memory mapped file. The Teradata Parallel
Transporter package then prompts for the memory mapped file directory.
largefree space.

should be in a partition with a
]:
Press Enter to use the default memory mapped file directory will be used.
89

The restrictions for the Teradata Parallel Transporter memory mapped file directory include:
Note: During the reinstall of the same Teradata Parallel Infrastructure version, the Teradata
Parallel Infrastructure reinstall does not request for the IPC memory choice. The reinstall uses
the existing IPC memory choice.
Note: The first Teradata Parallel Transporter package requests 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 package.
System Kernel Values
The Teradata Parallel Transporter Infrastructure package checks include the following system
kernel values.
Table 23 lists the kernel values.
Table 23: Kernel Values
Kernel Parameter
Required
Minimum Value
semmap
1000
Description
Maximum number of entries in a semaphore
map.
Note: Only checked on HP-UX 32-bit.
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

segments per process.
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 for an increase the formula value.
90

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. A kernel rebuild is not required
to change the value for the kernel parameter (shmmax).
Note: This install recommends increasing the value to the minimum
required value.
Note: A reboot is not required to make the 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 yes or n for no [y,n,? (default : y)]
Press y or Enter to change the kernel value.

Press n to leave the kernel value unchanged.
Note: If there is a change to the kernel value, the following kernel parameters require a kernel
rebuild, and a reboot: semmap, semmni, semmns, semmnu, and 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 and shmseg.
Table 24 lists the environment variables updated.
TWB_ROOT
Set to the Teradata Parallel Transporter

PATH

SHLIB_PATH
Add $TWB_ROOT/lib to the front of the

SHLIB_PATH environment variable.
NLSPATH

Updates to the environment variables are effective after 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.
If the Teradata Parallel Transporter API package was installed, then the SHLIB_PATH and
NLSPATH environment variables must be updated. 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.
91

The environment variables are updated from 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
Note: Environment variables must be updated to run the installed version of Teradata Parallel
Transporter properly. If updates are not made to the environment variables, the installed
version of Teradata Parallel Transporter will not run properly.

and Utilities 13.00.00. The driver files, readme.txt, terajdbc4.jar and tdgssconfig.jar, must be
manually downloaded to a directory of choice on the target client from \TeraJDBC in the root
directory of the installation CD ROM.

Driver.

Download Center at:

CLI User Exit functions are general purpose facilities that may be added to the CLI
workstation architecture on HP-UX systems. These functions allow user-defined processing to
take place.
92

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.
1
Change directories to /opt/teradata/client/sample:

Compile and link using either the 32-bit or 64-bit version of the makefile to create a new
shared object, libtdusr32.so. This command uses the 32-bit version of the make facility:
# make -f maketdusr.hpux
Note: The Native compiler on IA64 is not supported.

4
the same directory.
93

94
CHAPTER 5
Installing on Sun Solaris SPARC

Client Systems
This chapter contains procedures to install and uninstall Teradata Tools and Utilities software
on Sun Solaris client systems.
Uninstalling Previous Versions of Sun Solaris SPARC Software

This section describes the Sun Solaris Operating systems supported and the Teradata Tools
and Utilities products that can be installed on them.
Sun Solaris SPARC Operating Systems Supported

Database Management
95
Chapter 5: Installing on Sun Solaris SPARC Client Systems

Sun Solaris SPARC Packages

Installation Order
Warning:
any order.
96

Uninstalling Previous Versions of Sun Solaris

SPARC Software
Prior to installing Teradata Tools and Utilities, previous versions of Teradata Tools and
Utilities programs must be uninstalled:
Note: Teradata Generic Security Services software does not have to be uninstalled.

installed on 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>
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.
Teradata Parallel Transporter Default and Alternate Directories

Table 25 lists the default and alternate directories where the software is installed.
97

Table 25: Default and Alternative Directories
Item
Default Directory
ODBC driver files
/opt/teradata/client/ODBC_32
and/or
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
where: <version> is the version number for
For example, the default install directory for
Teradata Parallel Transporter version 13.00.00.00
is /opt/teradata/client/13.0/tbuild.
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.
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.
Screen Navigation
To navigate between and within screen elements during the installation or uninstallation
process, use screen navigation commands.
Table 26 lists the screen navigation commands.
98

Solaris Zones
Table 26: Screen Navigation Commands
Action
Command
Navigate to the product you want to install
Arrow keys
Install each product
Press Enter, or the press the space bar
Display licenses
View product packages
Select all
Unselect all
Continue
Exit the screen without installing any products or to

abort
Solaris Zones
To support Solaris 10 Zones, the Teradata Tools and Utilities <product> installation packages
were changed. The destination location of the <product> components being installed can be
specified. The limitation of specifying only the <product> install directory has been removed.
Default Directories
When a Teradata Tools and Utilities <product> is installed, the installation package prompts
for the following directory input:
Which directory should be used as installation for installing files?
(Files will be installed in : <installation>/teradata/client/13.0/
[odbc_32 | odbc_64])
(default installation: /opt):
Using </opt> as the package base directory.
Optionally, the default values provided can be selected, or another directory location can be
entered for each of the prompts.
Having the ability to specify an install directory for the 32-bit libraries, and the placement of
man pages allows complete control over where the <product> components are placed, and
supports Solaris zones that have been created on a Solaris system.
Incorrect Directory
In the case where an unacceptable directory is erroneously selected, the installation issues a
warning and prompts for a new directory.
For example:
Enter installation directory [ default: /opt/teradata/client/<version>/
odbc ]: /usr/odbc
99

ERROR: /usr/odbc does not have write permissions. Please enter a writable
directory.
Write Permission
Operating under a Solaris zone limits the selection of only those directories that have write
permissions in the active zone. Users must have the ability to determine these directories.
Running within the Global zone is equivalent to a Solaris system that does not have Solaris
zones setup.

If all the products on a CD are not being installed, review System Requirements on page 30.
Note: Before beginning the installation, remove all previous versions of the software (see
Technical Assistance on page 65)
Note: Previous versions of Teradata Parallel Transporter do not have to be uninstalled.
Procedure - Installing Teradata Tools and Utilities Products on Sun Solaris SPARC
Follow these steps to install Teradata Tools and Utilities on Sun Solaris SPARC.
1
Insert the installation CD in the CD-ROM drive on the server running Sun Solaris SPARC.
From the console, log on as root or change to root and enter your password.
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>.
Table 27 lists the CD mount points.
Table 27: CD-ROM Mount Point
CD
Directory
Teradata Utility Pak
cd1a_tera_util_pak
Database Management
cd2_database_mgnt
Preprocessors
cd3_preprocessors
Load/Unload
cd4_load_unload
Tape Storage Management Enablers
cd5_tape_stor_mgnt_ena
Type:
# ./setup.bat
A Teradata Tools and Utilities CD Installation screen similar to the following appears:
100

Welcome to the Teradata Tools and Utilities 13 installation
Platform: Solaris Sparc 64-bit
Media: Load/Unload - Volume 3
1. teragss - Teradata GSS client package
2. tdicu
3. cliv2
- Teradata CLIv2
4. piom
5. npaxsmod
6. mqaxsmod
7. bteq
8. fastexp
9. fastld
10. mload
11. tpump
- Teradata TPump Utility
Enter one or more selections (separated by space):
Select the packages to install. Table 28 lists the packages.

Table 28: Selecting the Packages to Install
Install
Action
All packages
Enter a. The number of products you selected will be shown in the bottom right
corner of the screen. The packages selected for installation will have an asterisk
beside them.
Selected
packages
Use the arrow keys to move to the package(s) to install. Then, press Space Bar
to select the package. An asterisk indicates the selection.
Repeat the previous step to select other packages.
Select dependent modules that are required, such as CLIv2 or Data Connector
API (PIOM), and repeat step 1 if necessary. For information on dependent
modules, see Software Requirements on page 31.
Enter c to accept the selected packages and continue with the installation.
Installation information appears for the selected products. Read the information and
respond to the prompts to begin the installation.
After the installation, a screen similar to the following appears indicating how many
Teradata Tools and Utilities packages were installed, and if any failed.
If any failures occurred, check the .log file and then call Teradata Solutions Customer
Services Remote Service Center (TSCS-RSC).
Teradata Tools and Utilities PACKAGE INSTALLATION
(Packages will now be installed onto the system.)
Number of packages to process: 12
Number successfully
processed: 12
101

Failures: 0
All packages processed successfully.
Please see the logfile [/var/ncr/logs/pkgadd.log] for any specific
package instructions.
From the root directory, enter the following command and remove the installation CD
from the CD-ROM drive:
# umount /cdrom
To remove the CD-ROM mount point, enter the following command (this step is
optional):
# rmdir /cdrom/<mount point>
Review the log file (/var/ncr/logs/pkgadd.log) for specific information about the packages
installed.
If a reboot is required, reboot the machine to fully enable the software packages to take effect.

This section contains instructions for installing the Teradata Parallel Transporter on Sun
Solaris SPARC.
The install of a new version of Teradata Parallel Transporter prompts for the Teradata Parallel
tbuild]:
Press Enter to use the default installation directory.

The restrictions for the Teradata Parallel Transporter installation directory include:
Do not use / or /usr as the installation directory
Logs Directory
directory.
tbuild/logs ]:
102

The following are the restrictions for the Teradata Parallel Transporter logs directory:

memory choice.
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.
free space.

]:
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:
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.
installation directory, but uses the same installation directory as the first Teradata Tools and
Utilities package installed.
The Teradata Parallel Transporter Infrastructure package checks for the system kernel values.
103

Kernel Parameter
Required Minimum
Value
Description
SEMMNI
1000

system.
SEMMNS
1000

system.
SEMMNU
2500

SHMMAX
4194304
SHMMNI
200

SHMSEG
10

Note: Checked only on Sun Solaris 8.
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.
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.
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:
104

# cd; /usr/sbin/shutdown -y -g60 -i6

profile and /etc/.login files.
Table 30 lists the environment variables.
TWB_ROOT

PATH

LD_LIBRARY_PATH

LD_LIBRARY_PATH environment variable.
NLSPATH

Updates to the environment variables are effective in the next login only if the Teradata
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.
Environment variables are updated on the command line, in the user's profile, or in the
system profile.
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.
105


and Utilities 13.00.00. The driver files, readme.txt, terajdbc4.jar and tdgssconfig.jar, must be
manually downloaded to a directory of choice on the target client from \TeraJDBC in the root
directory of the installation CD ROM.

Driver.

Download Center at:

workstation architecture on Sun Solaris SPARC systems. These functions allow user-defined
processing to take place.
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.
1

Compile and link using either the 64-bit version or the 32-bit version of the makefile to
create a new shared object, libtdusr32.so. The following command compiles the 32-bit
version:
# make -f makedusr.sols
106

4
the same directory.
Refer to Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems,

Appendix D.
107

108
CHAPTER 6
Installing on Sun Solaris Opteron

Client Systems
This chapter contains the procedures to install and uninstall the Teradata Tools and Utilities
software onSun Solaris Opteron client system.
Uninstalling Previous Versions of Sun Solaris Opteron Software

This section describes how to install Teradata Tools and Utilities on a Sun Solaris operating
system.
Sun Solaris Opteron Systems Supported

Database Management
109
Chapter 6: Installing on Sun Solaris Opteron Client Systems

Sun Solaris Opteron Packages

Installation Order
Warning:
any order.
110

Uninstalling Previous Versions of Sun Solaris

Opteron Software
Before beginning the installation process, use the following procedure to check for previous
versions of Teradata Tools and Utilities programs:
Note: A previous version of cliv2 must be uninstalled before installing a newer version.

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.
Default and Alternate Directories

Table 31 lists the default directories where the software is installed.
111

Table 31: Default and Alternative Directories
Item
Default Directory
ODBC driver files
and/or
Executable files
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
where: <version> is the version number for
For example, the default install directory for
Teradata Parallel Transporter version 13.00.00.00
is /opt/teradata/client/13.0/tbuild.
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.
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.
112

Solaris Zones
Solaris Zones
To support Solaris 10 Zones, the Teradata Tools and Utilities <product> installation packages
were changed to allow users to specify where the Teradata Tools and Utilities <product>
components are installed, to remove the limitation of specifying only the Teradata Tools and
Utilities <product> install directory.
When a Teradata Tools and Utilities <product> is installed, the installation package prompts
for the following directory input:
Which directory should be used as installation for installing files?
(Files will be installed in : <installation>/teradata/client/13.0/
[odbc_32 | odbc_64])
(default installation: /opt):
Using </opt> as the package base directory.
Optionally, the default values provided can be selected, or another directory location can be
selected for each of the three prompts above.
Having the ability to specify the Teradata Tools and Utilities <product> installation directory,
the 32-bit libraries, and the placement of man pages allows complete control over where the
Teradata Tools and Utilities<product> components are placed and supports the Solaris zones
that have been created on a Solaris Opteron system.
In the case where an unacceptable directory is erroneously selected, the installation for the
Teradata Tools and Utilities <product> issues a warning and prompts for a new directory.
For example:
Enter installation directory [ default: /opt/teradata/client/<version>/
odbc ]: /usr/odbc
ERROR: /usr/odbc does not have write permissions. Please enter a writable
directory.
Operating under a Solaris zone limits the selection of only those directories that have write
permissions in the active zone. Users must have the ability to determine which directories
these are. Running within the Global zone is equivalent to a Solaris system that does not have
Solaris zones setup.
After the Teradata Tools and Utilities <product> has been installed, the directories for the
Teradata Tools and Utilities <product> install directory, the 32-bit libraries, and the icu
libraries must be included in the LD_LIBRARY_PATH, since the typical symbolic links will no
longer be available in the /usr/lib directory when using Solaris zones.
For example, the LD_LIBRARY_PATH that includes the ODBC Driver for Teradata would be:
LD_LIBRARY_PATH=/opt/teradata/client/<version>/odbc/drivers:/opt/
teradata/client/<version>/odbc/lib:/opt/teradata/client/<version>/lib:/
opt/tdicu/lib
113


If all the products on the CD are not being installed, review System Requirements on
page 30.
Note: Before beginning the installation, remove all previous versions of the software (see
Technical Assistance on page 65)
Note: Previous versions of Teradata Parallel Transporter do not have to be removed.
Procedure - Installing Teradata Tools and Utilities Products on Sun Solaris Opteron
Follow these steps to install Teradata Tools and Utilities on Sun Solaris Opteron.
1
Insert the installation CD in the CD-ROM drive on the server running Sun Solaris.
From the console, log on as root or change to root and enter your password.
Change directories to the 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>
Table 32 lists the CD-ROM mount points.
Table 32: CD-ROM Mount Point
If you have this CD
change the directory to
Teradata Utility Pak
cd1a_tera_util_pak
Database Management
cd2_database_mgnt
Preprocessors
cd3_preprocessors
Load/Unload
cd4_load_unload
Tape Storage Management Enablers
cd5_tape_stor_mgnt_ena
Enter:
# ./setup.bat
A Teradata Tools and Utilities CD Installation screen similar to the following appears:
Welcome to the Teradata Tools and Utilities 13 installation
Platform: Solaris Opteron 64bit
Media: Load/Unload - Volume 3
2. tdicu
3. cliv2
- Teradata CLIv2
4. piom
114

5.
6.
7.
8.
9.
10.
11.
npaxsmod
mqaxsmod
bteq
fastexp
fastld
mload
tpump
Teradata
Teradata
Teradata
Teradata
Teradata
Teradata
Teradata

BTEQ Application
FastExport Utility
FastLoad Utility
MultiLoad Utility
TPump Utility

Select the packages to install. See Table 33.

Table 33: Selecting the Packages to Install
Package
Action
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.
Selected
Packages
After reviewing product dependencies, enter selections at the prompt: one or

more numbers for the product(s) to be installed, separated by spaces, or enter a
to install all the software, or enter q to quit the installation.
Repeat the previous step to select other packages.
Select any dependent products that are required, such as CLIv2 or Data
Connector API (PIOM), and repeat step 1 if necessary. For information on
dependent products, see Software Requirements on page 31.
From the root directory, enter the following command and remove the installation CD
from the CD-ROM drive:
# umount /cdrom
To remove the installation CD-ROM mount point, enter the following command (this
step is optional):
# rmdir /cdrom/<mount point>
Review the log file (/var/ncr/logs/pkgadd.log) for specific information about packages installed.
Reboot the system to fully enable the newly installed software packages to take effect.

This section contains instructions for installing the Teradata Parallel Transporter on Sun
Solaris Opteron.
tbuild]:
115


The following are the restrictions for the Teradata Parallel Transporter installation directory:
Logs Directory
directory.
tbuild/logs ]:


memory choice.
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.
free space.
116

]:

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.
The Teradata Parallel Transporter Infrastructure package checks for system kernel values.
Kernel Parameter
Required Minimum
Value
Description
SEMMNI
1000

system.
SEMMNS
1000

system.
SEMMNU
2500

SHMMAX
4194304
SHMMNI
200

SHMSEG
10

Note: Checked only on Sun Solaris 8.
installation will display a warning message.
Infrastructure installation prompts to increase the value to the minimum required value.
117

Warning: The current value of 1048675 for the kernel parameter (SHMMAX)
is less than the minimum required value of 4194304. SHMMAX refers to the
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.
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:

profile and /etc/.login files. Table 35 lists the environment variables updated.
TWB_ROOT

PATH

LD_LIBRARY_PATH

NLSPATH

Updates to the environment variables are effective at the next login only if the Teradata
allow the installed version of Teradata Parallel Transporter to run properly.
118

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.
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: Updates to the environment variables are not required run the installed version of
Note: Updates to the environment variables are not done, the installed version of Teradata
Parallel Transporter does not run properly.


Driver.

Download Center at:
119


workstation architecture on Sun Solaris Opteron systems. These functions allow user-defined
processing to take place.
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.
1

create a new shared object, libtdusr32.so.
The following command compiles the 32-bit version:
# make -f makedusr.sols
the same directory.
Refer to Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems,

Appendix D.
120
CHAPTER 7
Installing on Red Hat Linux

Client Systems
This chapter contains procedures to install and uninstall Teradata Tools and Utilities software
on Red Hat Linux systems.
Uninstalling Previous Versions of Red Hat Linux Software
Installing Teradata Tools and Utilities Products Silently on Red Hat Linux
Installing Teradata Tools and Utilities Products Interactively on Red Hat Linux

This section describes how to install Teradata Tools and Utilities products on a Red Hat Linux
operating system.
Red Hat Linux Operating Systems Supported

Installation of Teradata Tools and Utilities Products Using PUT

The Teradata Parallel Upgrade Tool (PUT) is not supported for Linux Red Hat operating
systems.
121
Chapter 7: Installing on Red Hat Linux Client Systems

Database Management
Red Hat Linux Packages

Installation Order
Warning:
Teradata Generic Security Services (teragss)
any order.
122

Teradata Generic Security Services (teragss)
Uninstalling Previous Versions of Red Hat Linux

Software
Prior to the installation process, check for any existing software and remove it.
Note: Previous versions of cliv2 must be uninstalled before installing the newer version.
Note: Teradata Parallel Transporter software does not have to be uninstalled.

Follow these steps to uninstall previous versions of Teradata Tools and Utilities software on
Red Hat Linux system.
1
Log on as root.
List all the installed packages:

# rpm -qa
Or, list individual packages installed:

# rpm -q <rpmname>
Table 36 lists the commands to check the versions of installed packages.

Table 36: Checking for Previous Versions of Software on Linux
Package
Command
Basic Teradata Query (BTEQ) (32-bit)
# rpm -q bteq
Named Pipes Access Module (32-bit)
# rpm -q npaxsmod
# rpm -q tdodbc
Shared Common Components for Internationalization

for Teradata (32-bit)
# rpm -q tdicu

# rpm -q tdicu_64
123

Table 36: Checking for Previous Versions of Software on Linux (continued)
Package
Command
Teradata C Preprocessor2 (32-bit)
# rpm -q sqlpp
# rpm -q sqlpp
Teradata Call-level Interface version 2 (CLIv2) (32-bit)
# rpm -q cliv2
# rpm -q cliv2_64
Teradata Data Connector (32-bit)
# rpm -q piom
Teradata FastExport (32-bit)
# rpm -q fexp
Teradata FastLoad (32-bit)
# rpm -q fastld
Teradata Generic Security Services (32-bit)
# rpm -q
teragss_redhatlinux-i386
# rpm -q
teragss_redhatlinux-ia64
Teradata MultiLoad (32-bit)
# rpm -q mload
Teradata Parallel Transporter API (32-bit)
# rpm -q papid000
Teradata Parallel Transporter Export Operator (32-bit)
# rpm -q pexpd000
Teradata Parallel Transporter Infrastructure (32-bit)
# rpm -q tbldd000
Teradata Parallel Transporter Load Operator (32-bit)
# rpm -q plodd000
Teradata Parallel Transporter Stream Operator (32-bit)
# rpm -q pstmd000
Teradata Parallel Transporter Update Operator (32-bit)
# rpm -q pupdd000
# rpm -q qrydir
Teradata TPump (32-bit)
# rpm -q tpump
Teradata WebSphere MQ Access Module (32-bit)
# rpm -q mqaxsmod
Uninstall individual packages:

# rpm -e <rpmname>
Table 37 lists the commands to remove individual packages.

Table 37: Uninstalling Previous Versions of Software on Linux
124
Package
Command
Basic Teradata Query BTEQ (32-bit)
# rpm -e bteq
# rpm -e npaxsmod
# rpm -e tdodbc

# rpm -e tdicu

Table 37: Uninstalling Previous Versions of Software on Linux (continued)
Package
Command

# rpm -e tdicu_64
# rpm -e sqlpp
# rpm -e sqlpp
# rpm -e cliv2
# rpm -e cliv2_64
# rpm -e piom
# rpm -e fastexp
# rpm -e fastld
# rpm -e
# rpm -e
# rpm -e mload
# rpm -e papid000
# rpm -e pexpd000
# rpm -e tbldd000
# rpm -e plodd000
# rpm -e pstmd000
# rpm -e pupdd000
# rpm -e qrydir
# rpm -e tpump
# rpm -e mqaxsmod
125


To install Teradata Tools and Utilities products, run the setup.bat command for Teradata Tools
and Utilities and select the products to install.
Teradata Tools and Utilities can be installed:
Silently (See Installing Teradata Tools and Utilities Products Silently on Red Hat Linux
on page 126)
Interactively (See Installing Teradata Tools and Utilities Products Interactively on Red
Hat Linux on page 128)
Installing Teradata Tools and Utilities Products Silently on Red Hat Linux
This section contains procedures to install Teradata Tools and Utilities products silently on
Red Hat Linux operating systems.
Procedure - Installing Teradata Tools and Utilities Products Silently on Red Hat Linux
Follow these steps to install Teradata Tools and Utilities products silently on Red Hat Linux
client operating systems.
1
Log on to the Red Hat Linux client as root.
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 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

# cd /mnt
# ./setup.bat

Platform: Linux 32bit (i386)
Media: Load/Unload
2. tdicu
3. tdodbc
4. cliv2
- Teradata CLIv2
5. piom
126

6.
7.
8.
9.
10.
11.
12.
13.
npaxsmod
mqaxsmod
bteq
fastexp
fastld
mload
tpump
qrydir
Teradata
Teradata
Teradata
Teradata
Teradata
Teradata
Teradata
Teradata

BTEQ Application
FastExport Utility
FastLoad Utility
MultiLoad Utility
TPump Utility
Query Director

After reviewing product dependencies, enter selections at the prompt:
one or more numbers for the product(s) to install, separated by spaces, or
u to install all the software, or
Change back to the root directory and unmount the CD:

# umount /mnt

Following the installation, verify that the installation executed successfully. See Verifying
the Installation of Individual Products on page 184 and Verifying the Installation Using
the CLI Sample Program on page 217.
127

Installing Teradata Tools and Utilities Products Interactively on Red Hat

Linux
This section contains procedures to install Teradata Tools and Utilities products interactively
on Red Hat Linux operating systems. Teradata Tools and Utilities products can also be
installed silently, see Installing Teradata Tools and Utilities Products Silently on Red Hat
Linux on page 126.
Procedure - Installing Teradata Tools and Utilities Products Interactively on Red Hat
Linux
Follow these steps to install Teradata Tools and Utilities products on Red Hat Linux client
interactively.
1
Log on to the Red Hat Linux client as root.

# mkdir /mnt
3
Insert the installation CD into the CD-ROM drive, then enter:

For example:
If the CD-ROM device name is cdrom, enter:
4
Go to the directory where the rpm for the Teradata Tools and Utilities product is present.
# cd <CD mount point>/Linux
# cd <package directory name>
Table 38 lists the commands to change directories.

Table 38: Changing Directories
128
Package
Command
# cd bteq
# cd npipes
# cd tdodbc

# cd tdicu

# cd tdicu
# cd sqlpp
# cd sqlpp
Teradata Call-level Interface version 2(CLIv2) (32-bit)
# cd cliv2

Table 38: Changing Directories (continued)
Package
Command
# cd cliv2
# cd piom
# cd fexp
# cd fastld
# cd mload
# cd teragss
# cd teragss
# cd papid000
# cd pexpd000
# cd tbldd000
# cd plodd000
# cd pstmd000
# cd pupdd000
# cd qrydir
# cd tpump
# cd mqaxsmod
To install a Teradata Tools and Utilities product enter:

# rpm -ivh <rpmname>
For example, to install BTEQ, enter:

# rpm -ivh bteq-13.00.00.00-1.i386.rpm
Note: A special case is installing an individual Teradata Parallel Transporter product. To

install a Teradata Parallel Transporter product, enter:
# ./tptinstall -r <rpmname>
Note: To install the Teradata Parallel Transporter API, enter:

# ./tptinstall -r papid000-13.00.00.00-1.i386.rpm
Then respond to the questions asked:

Which version of the 32-bit TPT API library do you want to install?
Enter 1 for 32-bit TPT API library built with the gcc 2.96 compiler
enter option 1 to install binary built with gcc 2.96 compiler
Table 39 lists the commands to install individual packages.
129

Table 39: Installing Teradata Tools and Utilities on Linux
Package
Command
Basic Teradata Query (BTEQ) (32bit)
# rpm -ivh bteq-13.00.00.00-1.i386.rpm
Named Pipes Access Module (32bit)
# rpm -ivh npaxsmod-13.00.00.00-1.i386.rpm
# rpm --nodeps -i tdodbc-13.00.00.001.i386.rpm

(32-bit)
# rpm -ivh tdicu-13.00.00.00-1.i386.rpm

(64-bit)
# rpm -ivh tdicu_64-13.00.00.00-1.ia64.rpm
Teradata Call-level Interface version

2 (CLIv2) (32-bit)
# rpm -ivh cliv2-13.00.00.00-1.i386.rpm

2 (CLIv2) (64-bit)
# rpm -ivh cliv2_64-13.00.00.00-1.ia64.rpm
# rpm -ivh piom-13.00.00.00-1.i386.rpm
# rpm -ivh fexp-13.00.00.00-1.i386.rpm
# rpm -ivh fastld-13.00.00.00-1.i386.rpm

(32-bit)
# rpm -ivh teragss_redhatlinux-1.i38613.00.00.00-1.i386.rpm

(64-bit)
# rpm -ivh teragss_redhatlinux-1.ia6413.00.00.00-1.ia64.rpm
# rpm -ivh mload-13.00.00.00-1.i386.rpm
# rpm -ivh sqlpp-13.00.00.00-1.i386.rpm
# rpm -ivh sqlpp-13.00.00.00-1.ia64.rpm

(32-bit)
# ./tptinstall -r papid000-13.00.00.001.i386.rpm
Teradata Parallel Transporter Export # ./tptinstall -r pexpd000-13.00.00.001.i386.rpm

Operator (32-bit)
Infrastructure (32-bit)
# ./tptinstall -r tbldd000-13.00.00.001.i386.rpm
Teradata Parallel Transporter Stream # ./tptinstall -r pstmd000-13.00.00.001.i386.rpm

Operator (32-bit)
Update Operator (32-bit)
130
# ./tptinstall -r pupdd000-13.00.00.001.i386.rpm

Table 39: Installing Teradata Tools and Utilities on Linux (continued)
Package
Command
# rpm -ivh qrydir-13.00.00.00-1.i386.rpm
# rpm -ivh tpump-13.00.00.00-1.i386.rpm
Teradata WebSphere MQ Access

Module (32-bit)
# rpm -ivh mqaxsmod-13.00.00.00-1.i386.rpm
Chapter 11: After You Install, contains a list of the files in each package. Verify all the
files in the package are installed using the Red Hat Package Manager command:
# rpm -ql <rpmname>
Table 40 lists the commands to verify the installation of individual packages.

Table 40: Verifying the Installation on Linux
Package
Command
# rpm -ql bteq
# rpm -ql npaxsmod
# rpm -ql tdodbc

Internationalization for Teradata (32-bit)
# rpm -ql tdicu

# rpm -ql tdicu_64
Teradata C Preprocessor (32-bit)
# rpm -ql sqlpp
# rpm -ql sqlpp
Teradata Call-level Interface version 2 (CLIv2) (32bit)
# rpm -ql cliv2
# rpm -ql cliv2_64
# rpm -ql piom
# rpm -ql fastexp
# rpm -ql fastld
# rpm -ql teragss_redhatlinuxi386
# rpm -ql teragss_redhatlinuxia64
# rpm -ql mload
# rpm -ql papid000
131

Table 40: Verifying the Installation on Linux (continued)
Package
Command
Teradata Parallel Transporter Export Operator (32bit)
# rpm -ql pexpd000
# rpm -ql tbldd000
# rpm -ql plodd000
Teradata Parallel Transporter Stream Operator (32bit)
# rpm -ql pstmd000
Teradata Parallel Transporter Update Operator (32bit)
# rpm -ql pupdd000
# rpm -ql qrydir
# rpm -ql tpump
# rpm -ql mqaxsmod

# umount /mnt

This section contains instructions for installing the Teradata Parallel Transporter on Red Hat
Linux.
Here is a sample of the prompt:
Please specify the install directory [default: /opt/teradata/client/
13.0/tbuild/]:

The restrictions for the Teradata Parallel Transporter installation directory:
132

Logs Directory
Transporter Infrastructure package will prompt for the Teradata Parallel Transporter logs
directory.
tbuild/logs ]:


memory choice.
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.
free space.

]:
Press Enter to use the default memory mapped file directory:

The restrictions for the Teradata Parallel Transporter memory mapped file directory include:
133

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.
installation directory, instead, they use the same installation directory as the first installation
package.
The Teradata Parallel Transporter Infrastructure package checks for the following system
kernel values.
Table 41 lists the kernel values checked.
Kernel Parameter
Required
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.
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
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.
134


TWB_ROOT
Set to the Teradata Parallel Transporter installation directory.
PATH
Add $TWB_ROOT/bin to the front of the PATH environment variable.
LD_LIBRARY_PATH
Add $TWB_ROOT/lib to the front of the LD_LIBRARY_PATH

NLSPATH
Add $TWB_ROOT/msg/%N to the front of the NLSPATH environment

variable.
and NLSPATH environment variables must be updated manually.
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.
The environment variables must be updated on the command line, in the user's profile, or in
the system profile.
Note: Updates to the environment variables must be made, to run the installed version of
Note: If updates to the environment variables are not made, then the installed version of
Teradata Parallel Transporter does not run properly.

135


Driver.

Download Center at:

architecture on Linux systems. These functions allow user-defined processing to take place.
Procedure - Adding CLI User Exit Functions to a Red Hat Linux Client
Follow these steps to add CLI User Exit functions to a Red Hat Linux client.
1

create a new shared object, libtdusr32.so. 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
136
Move the libtdusr32.so file into the /usr/lib directory. The CLIv2 libcliv2.so is located in the
same directory.

137

138
CHAPTER 8
Installing on SUSE Linux

Client Systems
This chapter the procedures to install and uninstall Teradata Tools and Utilities software on
SUSE Linux client systems.
Installing Teradata Tools and Utilities Products Silently on SUSE Linux
Installing Teradata Tools and Utilities Products Interactively on SUSE Linux

This section describes how to install Teradata Tools and Utilities products on a SUSE Linux
operating system.
SUSE Linux Operating Systems Supported

Database Management
139
Chapter 8: Installing on SUSE Linux Client Systems

SUSE Linux Packages

Installation Order
Warning:
any order.
140


To install Teradata Tools and Utilities products, run the setup.bat command for Teradata Tools
and Utilities and select the products to install.
Teradata Tools and Utilities can be installed:
Silently (See Installing Teradata Tools and Utilities Products Silently on SUSE Linux on
page 141)
Interactively (See Installing Teradata Tools and Utilities Products Interactively on SUSE
Linux on page 143)
Installing Teradata Tools and Utilities Products Silently on SUSE Linux

This section contains procedures to install Teradata Tools and Utilities products silently on
SUSE Linux operating systems.
Procedure - Installing Teradata Tools and Utilities Products Silently

Follow these steps to install Teradata Tools and Utilities products silently on SUSE Linux client
operating systems.
1
Log on to the SUSE Linux client as root.

# mkdir /mnt
In the command shown, the CD-ROM mount point is /mnt, although an alternate may be
used.
3
Insert the installation CD into the CD-ROM drive, then enter the following at the
command prompt:
For example, if the CD-ROM device name is cdrom, you would type:
In the example, the CD-ROM mount point is /mnt, but an alternate may be entered.
4

# cd /mnt
# ./setup.bat

Platform: Linux 32bit (i386)
141

Media: Load/Unload
2. tdicu
3. tdodbc
4. cliv2
- Teradata CLIv2
5. piom
6. npaxsmod
7. mqaxsmod
8. bteq
9. fastexp
10. fastld
11. mload
12. qrydir
- Teradata Query Director
After reviewing product dependencies, enter selections at the prompt:
one or more numbers for the product(s) to install, separated by spaces, or

# umount /mnt

Following the installation, verify that the installation executed successfully. See Verifying
the Installation of Individual Products on page 184 and Verifying the Installation Using
the CLI Sample Program on page 217.
142

Installing Teradata Tools and Utilities Products Interactively on SUSE

Linux
This section contains procedures to install Teradata Tools and Utilities products interactively
on SUSE Linux operating systems. Teradata Tools and Utilities products can also be installed
silently, see Installing Teradata Tools and Utilities Products Silently on SUSE Linux on
page 141.
Procedure - Installing Teradata Tools and Utilities Products Interactively on SUSE Linux
Follow these steps to install Teradata Tools and Utilities products interactively on SUSE Linux.
1
Log on to the SUSE Linux client as root.

# mkdir /mnt
3
Insert the installation CD into the CD-ROM drive, then enter:

For example:
If the CD-ROM device name is cdrom, enter:
4
Go to the directory where the rpm for the Teradata Tools and Utilities product is present.
# cd <rpmname>
Table 43 lists the commands to change directories.

Table 43: Changing Directories
Package
Command
# cd bteq
# cd npipes
# cd tdodbc

for Teradata
# cd tdicu
Teradata Archive/Recovery Utility (ARC) (32-bit)
# cd arc
# cd sqlpp
# cd sqlpp
Teradata Call-level Interface version 2(CLIv2) (32-bit)
# cd cliv2
# cd cliv2
# cd piom
143

Table 43: Changing Directories (continued)
Package
Command
# cd fexp
# cd fastld
# cd mload
# cd teragss
# cd papid000
# cd pexpd000
# cd tbldd000
# cd plodd000
# cd pstmd000
# cd pupdd000
# cd qrydir
# cd tpump
# cd mqaxsmod
To install an individual Teradata Tools and Utilities product enter:

# rpm -ivh <rpmname>
For example, to install BTEQ, enter:

# rpm -ivh bteq-13.00.00.00-1.i386.rpm
Note: A special case is installing an individual Teradata Parallel Transporter product. To

install a Teradata Parallel Transporter product, enter:
# ./tptinstall -r <rpmname>
Note: To install the Teradata Parallel Transporter API, enter:

# ./tptinstall -r papid000-13.00.00.00-1.i386.rpm
Then respond to the questions asked:

Which version of the 32-bit TPT API library do you want to install?
Table 44 lists the commands to install an individual package.
144

Table 44: Installing Teradata Tools and Utilities on Linux
Package
Command
Basic Teradata Query (BTEQ) (32bit)
# rpm -ivh bteq-13.00.00.00-1.i386.rpm
Named Pipes Access Module (32bit)
# rpm -ivh npaxsmod-13.00.00.00-1.i386.rpm
ODBC Driver for Teradata (32-bit)

and (64-bit)
# rpm -i tdodbc-13.00.00.00-1.noarch.rpm

(32-bit)
# rpm -ivh tdicu-13.00.00.00-1.i386.rpm

(64-bit)
# rpm -ivh tdicu_64-13.00.00.00-1.x8664.rpm
Teradata Archive/Recovery Utility

(ARC) (32-bit)
# rpm -ivh teradata_arc-13.00.00.001.i386.rpm
Note: Since there is a Linux system package named arc

that conflicts with the Teradata naming convention, the
Teradata ARC package has been renamed to
teradata_arc effective in Teradata Tools and Utilities
version 13.0.
Before updating to, or installing Teradata ARC version
13.0, Teradata ARC version 12.0 must be uninstalled first.
# rpm -ivh sqlpp-13.00.00.00-1.i386.rpm
# rpm -ivh sqlpp-13.00.00.00-1.x8664.rpm

2 (CLIv2) (32-bit)
# rpm -ivh cliv2-13.00.00.00-1.i386.rpm

2 (CLIv2) (64-bit)
# rpm -ivh cliv2_64-13.00.00.00-1.x8664.rpm
# rpm -ivh piom-13.00.00.00-1.i386.rpm
# rpm -ivh fexp-13.00.00.00-1.i386.rpm
# rpm -ivh fastld-13.00.00.00-1.i386.rpm

(64-bit)
# rpm -ivh teragss_suselinux-x866413.00.00.00-1.x86_64.rpm
# rpm -ivh mload-13.00.00.00-1.i386.rpm

(32-bit)
# ./tptinstall -r papid000-13.00.00.001.i386.rpm
Teradata Parallel Transporter Export # ./tptinstall -r pexpd000-13.00.00.001.i386.rpm

Operator (32-bit)
145

Table 44: Installing Teradata Tools and Utilities on Linux (continued)
Package
Command

Infrastructure (32-bit)
# ./tptinstall -r tbldd000-13.00.00.001.i386.rpm
Teradata Parallel Transporter Load

Operator (32-bit)
# ./tptinstall -r plodd000-13.00.00.001.i386.rpm
Teradata Parallel Transporter Stream # ./tptinstall -r pstmd000-13.00.00.001.i386.rpm

Operator (32-bit)

Update Operator (32-bit)
# ./tptinstall -r pupdd000-13.00.00.001.i386.rpm
# rpm -ivh qrydir-13.00.00.00-1.i386.rpm
# rpm -ivh tpump-13.00.00.00-1.i386.rpm
Teradata WebSphere MQ Access

Module (32-bit)
# rpm -ivh mqaxsmod-13.00.00.00-1.i386.rpm
Chapter 11: After You Install contains a list of the files in each package. Verify all the files
in the package are installed using the SUSE Package Manager command:
# rpm -ql <rpmname>
Table 45 lists the commands to verify the installation of individual packages.

Table 45: Verifying the Installation on Linux
146
Package
Command
# rpm -ql bteq
# rpm -ql npaxsmod
# rpm -ql tdodbc

# rpm -ql tdicu

# rpm -ql tdicu_64
Teradata Archive/Recovery Utility (ARC) (32-bit)
# rpm -ql teradata_arc
# rpm -ql sqlpp
# rpm -ql sqlpp
# rpm -ql cliv2
# rpm -ql cliv2_64
# rpm -ql piom

Table 45: Verifying the Installation on Linux (continued)
Package
Command
# rpm -ql fastexp
# rpm -ql fastld
# rpm -ql teragss_suselinuxx8664
# rpm -ql mload
# rpm -ql papid000
Teradata Parallel Transporter Export Operator (32bit)
# rpm -ql pexd000
# rpm -ql tbldd000
# rpm -ql plodd000
Teradata Parallel Transporter Stream Operator (32bit)
# rpm -ql pstmd000
Teradata Parallel Transporter Update Operator (32bit)
# rpm -ql pupdd000
# rpm -ql qrydir
# rpm -ql tpump
# rpm -ql mqaxsmod

# umount /mnt


147

Driver.

Download Center at:

architecture on Linux systems. These functions allow user-defined processing to take place.
Procedure - Adding CLI User Exit Functions to a SUSE Linux Client

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

create a new shared object, libtdusr32.so. 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
the same directory.
148
CHAPTER 9
Installing with Tar Teradata Client

Packages
This section describes how to install Teradata Tools and Utilities packages across the network
using Tar Teradata Client Packages.
Tar Teradata Client Packages

The Tar Teradata Client Packages script is contained on the installation CD ROM. It allows the
creation of a subset of the Teradata client packages from the CD ROM media, and simple
copying of a single file across the network.
The tar file created:
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
Script Name
The name of the script is: tar_teradata_client_packages.bat
Note: The UNIX version is tar_teradata_client_packages.sh
Usage
The scripts and a description of what they do are contained in Table 46.
Table 46: tar_teradata_client_packages
Command
Description
tar_teradata_client_package
Runs the script, and creates a tar file with one

package and its dependent packages
tar_teradata_client_packages list
Lists the platforms and available packages
tar_teradata_client_packages list {platform}
Lists the products available for a specific platform
tar_teradata_client_packages {platform}
Runs the script creating a tar file for a specific

platform, including all packages
tar_teradata_client_packages {platform}
[{package1} {package2} ]
Runs the script creating a tar file for a specific

platform, and specific packages
149
Chapter 9: Installing with Tar Teradata Client Packages

Using the tar Script
where the Parameters are:

Table 47: tar_teradata_client_packages Parameters
Command
Description
help
Displays the help information.
list
Lists the system and packages available on the

media.
{platform}
Lists the packages available for the specified

platform.
{platform}
Creates a tar file for the UNIX system

specified with the platform parameter. Can
be one of: aix, hp-ux, linux, mpras, sparc, or
opteron (for Solaris Sparc or Solaris Opteron).
[{package1} {package2} ]
Optional parameters following <platform>.

These are a list of specific packages including;
bteq, cliv2, fastexp, fastld, mload. If any packages
specified other than the four dependent
packages are all included: TeraGSS, CLIv2,
TDICU, and Data Connector (piom).
Note: The version of the package isn't needed with the package name. Solaris displays the
package as bteq130. The parameter bteq will work as well as bteq130.

The tar_teradata_client_packages script is intended for system administrators. The script
creates a tar file containing all the packages for a particular UNIX operating system, or a tar
file containing all the files for a specified product. The files are copied from the Teradata Client
media.
The script runs on all of the major UNIX platforms that Teradata Client supports: AIX, HP/
UX, Linux, NCR MP-RAS, Sun Solaris Sparc and Solaris Opteron, executed within a Windows
command window (DOS), or on UNIX machine with the Korn shell (/bin/ksh).
The script copies Teradata client packages from a Windows or UNIX disk mount to another
UNIX system while including all packages, or specific packages. Dependent packages for the
Teradata Client Utilities are also automatically included in the file.
150
No parameters, or help - Executing the script, tar_teradata_client_packages without any

parameters, or with the help parameter specified, displays the available commands.
list parameter - Specifying the single parameter list displays the available platforms
and packages for that media. The parameter list followed by a platform that is available
on the media (aix, hpux, linux, hp-ux, sparc, or opteron) lists the packages
available for that specified platform.

[platform] - Executing the script with [platform] as the first parameter creates a tar file
in the default target path. The file contains all of the Teradata Client packages on that
media for that system.
The path for the output can be changed, but the output file name will be in the format:
teradata-client-{platform}-{media name}.tar (.gz if compressed)
[package] - 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.
The tar script prompts for a directory where you will create the tar file, and accepts Enter for
the default. The default is the user directory HOME for Windows (usually C:\Documents and
Settings\username) and the UNIX user's home directory for UNIX. If the script is run as root
on UNIX, the default directory will be /tmp.
The script attempts to create the directory if it doesn't exist. If the location is read-only or
unable to be written, the script ends.
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.
Script Dependencies
The tar executable must be located in the PATH on the system running the script. Windows
does not provide tar.exe. If the tar executable isn't located on the system, the script 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
On UNIX, 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.
The Linux tar file only compresses a small amount, compared to the other platform's
packages.
Typical Output
Windows
Run the tar executable on the Windows system:
D:\>tar_teradata_client_packages
Windows Example
***************************************************************************
*
Tar Teradata Client Packages v.13.00.00.00
*
***************************************************************************
151

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:
ftp://ftp.gnu.org/pub/pub/gnu/tar/tar-1.12.msdos.exe
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/
Help Parameter
Run the tar executable without parameters, or with the parameter help:
D:\>tar_teradata_client_packages help
Help Parameter Example

***************************************************************************
*
*
***************************************************************************
Tar Teradata Client Packages
Usage: tar_teradata_client_packages list
tar_teradata_client_packages list {platform}
tar_teradata_client_packages {platform} [{package1} {package2} ...]
Parameters:
commands
help
list
list {platform}
{platform}
{package}
:
:
:
:
:
help, list, {platform} [{package1} {package2} ...]

Display this help message.
List the available platforms and packages from the media.
List the packages available for the specified platform.
Available platforms: aix, hpux, linux, mpras, opteron, sparc
Create the tar file for the supplied platform and include
all packages or individual packages.
: 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
list Parameter
Run the tar executable with the list parameter (platforms and packages vary):
/mount/LoadUnloadVol2> tar_teradata_client_packages.sh list
list Parameter Example

***************************************************************************
152

*
*
***************************************************************************
The available platforms are:
HP-UX
Linux
The available packages are:
--- HP-UX Products
bteq
fastexp
mload
cliv2
fastld
mqaxsmod
npaxsmod
piom
tdicu
TeraGSS
tpump
--- Linux Products

bteq
fastexp
cliv2
fastld
npaxsmod
piom
tdicu
TeraGSS
tpump
mload
mqaxsmod
Linux
Run the tar executable for Linux (all packages), with automatic gzip of output file:
D:\>tar_teradata_client_packages linux
Linux Example
***************************************************************************
*
*
***************************************************************************
Platform: 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-volume2.tar"
---Archiving all packages for linux.
tar cvf "C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar"
Linux
a Linux/mqaxsmod/mqaxsmod-13a.00.00.00-1.i386.rpm 118 blocks
a Linux/mload/mload130-13b.00.00.00-1.i386.rpm 374 blocks
a Linux/piom/piom130-13b.00.00.00-1.i386.rpm 79 blocks
a Linux/tdicu/tdicu-13c.00.00.00-1.noarch.rpm 20564 blocks
a Linux/fastld/fastld130-13d.00.00.00-1.i386.rpm 189 blocks
a Linux/TeraGSS/TeraGSS_redhatlinux-i386-13i.00.00.00-1.i386.rpm 12240 blocks
a Linux/fastexp/fastexp130-13b.00.00.00-1.i386.rpm 341 blocks
a Linux/tpump/tpump130-13c.00.00.00-1.i386.rpm 478 blocks
a Linux/npaxsmod/npaxsmod-13a.00.00.00-1.i386.rpm 272 blocks
a Linux/cliv2/cliv2-13e.00.00.00-1.x86_64.rpm 766 blocks
a Linux/bteq/bteq130-13c.00.00.00-1.i386.rpm 303 blocks
a Linux/jmsaxsmod/jmsaxsmod-13a.00.00.00-1.i386.rpm 81 blocks
tar rvf "C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar"
.setup.sh
tar: blocksize = 20
a .setup.sh 282 blocks
setup.bat
tar: blocksize = 20
153

a setup.bat 1 block
MEDIALABEL
tar: blocksize = 20
a MEDIALABEL 1 block
The file has been saved at :
C:\Documents and Settings\user\teradata-client-linux-load-unload-volume-2.tar.gz
HP-UX with BTEQ

Run the tar executable with tar for HP-UX, with BTEQ only, saving to D:\:
D:\>tar_teradata_client_packages tar hp-ux bteq
HP-UX with BTEQ Example

***************************************************************************
*
*
***************************************************************************
Platform: HP-UX
Default Path and Output File:
C:\Documents and Settings\user\teradata-client-hp-ux-load-unload-volume-2.tar
Hit [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 block
a HP-UX/TeraGSS/ia64/TeraGSS_hpux-ia64_13i.00.00.00.depot 164540 blocks
a HP-UX/TeraGSS/ia64/TeraGSS_hpux-ia64_13i.00.00.00.psf 3 blocks
a HP-UX/TeraGSS/pa32/pkginfo.txt 1 block
a HP-UX/TeraGSS/pa32/TeraGSS_hpux-pa32_13i.00.00.00.depot 114340 blocks
a HP-UX/TeraGSS/pa32/TeraGSS_hpux-pa32_13i.00.00.00.psf 3 blocks
tar rvf "d:\teradata-client-hp-ux-load-unload-volume-2.tar" HP-UX\tdicu*
tar: blocksize = 20
a HP-UX/tdicu/ia64/swagent.log 3 blocks
a HP-UX/tdicu/ia64/tdicu130/tdicu130/opt/teradata/client/13.0/tdicu/lib/
libicudatatd.so.36.0 16206 blocks
libicui18ntd.so.36.0 24941 blocks
libicuiotd.so.36.0 773 blocks
a HP-UX/bteq/pa32/catalog/swlock 0 blocks
a HP-UX/bteq/pa32/catalog/INDEX 9 blocks
a HP-UX/bteq/pa32/catalog/bteq130/bteq130/INFO 4 blocks
a HP-UX/bteq/pa32/catalog/bteq130/bteq130/INDEX 1 block
a HP-UX/bteq/pa32/catalog/bteq130/bteq130/postinstall 10 blocks
a HP-UX/bteq/pa32/catalog/bteq130/bteq130/postremove 5 blocks
a HP-UX/bteq/pa32/catalog/bteq130/bteq130/preinstall 11 blocks
a HP-UX/bteq/pa32/catalog/bteq130/pfiles/INFO 1 block
a HP-UX/bteq/pa32/catalog/bteq130/pfiles/INDEX 8 blocks
a HP-UX/bteq/pa32/catalog/bteq130/pfiles/README 1 block
a HP-UX/bteq/pa32/catalog/bteq130/pfiles/_ACL 1 block
a HP-UX/bteq/pa32/catalog/bteq130/pfiles/_LOCK_FILE 0 blocks
a HP-UX/bteq/pa32/catalog/bteq130/pfiles/_OWNER 1 block
a HP-UX/bteq/pa32/catalog/dfiles/INFO 1 block
154

a HP-UX/bteq/pa32/catalog/dfiles/INDEX 1 block
a HP-UX/bteq/pa32/catalog/dfiles/_ACL 1 block
a HP-UX/bteq/pa32/catalog/dfiles/_PROD_DFLT_ACL 1 block
a HP-UX/bteq/pa32/catalog/dfiles/_LOCK_FILE 0 blocks
a HP-UX/bteq/pa32/catalog/dfiles/_OWNER 1 block
The file has been saved at :
d:\teradata-client-hp-ux-load-unload-volume-2.tar.gz
155

156
CHAPTER 10
Configuring Teradata Tools and Utilities
Several of the Teradata Tools and Utilities products require that you manually configure the
products prior to operating the product. Configuration information or procedures for these
products are contained in this chapter:
Configuring Environment Variables for CLIv2, Data Connector, and TeraGSS
Setting IBM AIX Environment Variables for CLIv2, Data Connector, and TeraGSS on
page 158
Setting HP-UX Environment Variables for CLIv2 and Data Connector on page 158
Setting Sun Solaris Environment Variables for CLIv2 and Data Connector on
page 158
Setting Linux Environment Variables for CLIv2 on page 159
Configuring the ODBC Driver for Teradata
Configuring the ODBC Driver for IBM AIX on page 160
Configuring the ODBC Driver for HP-UX on page 161
Configuring the ODBC Driver for Sun Solaris on page 161
Configuring the ODBC Driver for Linux on page 162
Configuring Teradata Access Module for JMS
Configuring Teradata Parallel Transporter
Configuring Teradata Parallel Transporter for HP-UX on page 163
Configuring Teradata Parallel Transporter for Sun Solaris on page 170
Configuring Teradata Parallel Transporter for Red Hat Linux on page 176
157
Chapter 10: Configuring Teradata Tools and Utilities

Configuring Environment Variables for CLIv2,

Data Connector, and TeraGSS
Setting the Environment Variables
Environment variables must be set to reflect the location of the CLIv2, Data Connector, and
TeraGSS libraries. These products are installed as dependencies for all Teradata Tools and
Utilities products. To set CLIv2, Data Connector, and TeraGSS environment variables perform
the following procedures.
Setting IBM AIX Environment Variables for CLIv2, Data Connector,
and TeraGSS
If CLIv2, Data Connector, and TeraGSS were installed on IBM AIX, set the environment
variables for those products.
Include the installation directory path where CLIv2, Data Connector, and TeraGSS software
files are located in LIBPATH.
Bourne shell users, use this command to add the installation directory to the LIBPATH:
LIBPATH=$LIBPATH:<installation directory>;export LIBPATH
C shell users, use this command to add the installation directory to the LIBPATH:
setenv LIBPATH $LIBPATH:<installation directory>
To ensure that IBM AIX can find the correct version of libtdgss.so, include
the following path as the first path in LIBPATH.
For 64-bit applications:
usr/teragss/aix-power/client/lib
Setting HP-UX Environment Variables for CLIv2 and Data

Connector
If CLIv2 and Data Connector were installed on HP-UX, set the environment variables for
those products.
Include the installation directory path where CLIv2 and Data Connector software files are
located in SHLIB_PATH.
Bourne shell users, use this command to add the installation directory to the
SHLIB_PATH.
SHLIB_PATH=$LD_LIBRARY_PATH:<onstallation directory>;
export SHLIB_PATH
C shell users, use this command to add the installation directory to the SHLIB_PATH
setenv SHLIB_PATH $SHLIB_PATH:<installation directory>
Setting Sun Solaris Environment Variables for CLIv2

and Data Connector
If CLIv2 and Data Connector were installed on Sun Solaris, set the environment variables for
those products.
158

include the basedir path, where basedir is the directory path of the CLIv2 and Data Connector
software files in LD_LIBRARY_PATH.
Bourne shell users, use this command to add basedir path to the LD_LIBRARY_PATH:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/basedir:
export LD_LIBRARY_PATH
C shell users, use this command to add basedir path to the LD_LIBRARY_PATH:
setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH":/basedir"
Setting Linux Environment Variables for CLIv2

If CLIv2 was installed on Linux, set the environment variables for those products.
Include the installation directory path where CLIv2 software files are located in
LD_LIBRARY_PATH.
Bash and Bourne shell users, use this command to add the installation directory path to
the
LD_LIBRARY_PATH:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<installation directory>;
export LD_LIBRARY_PATH
C shell users, use this command to add the installation directory path to the
LD_LIBRARY_PATH:
setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH":<installation directory>"
159


This section describes how to configure the ODBC Driver for Teradata for each of the UNIX
and Linux operating systems. Find the Configuration section for your platform and perform
the procedures to configure the ODBC Driver for Teradata.
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.
Configuring the ODBC Driver for IBM AIX

Follow the procedures in this section to configure the ODBC Driver for Teradata on IBM AIX.
Copying the Template odbc.ini File for ODBC on IBM AIX
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
Setting Environment Variables for ODBC on IBM AIX

The LIBPATH environment variable must reflect the location of the ODBC libraries on IBM
AIX.
Procedure - Setting the Environment Variables for the ODBC Libraries on IBM AIX
Follow these steps to set the LIBPATH environment variable to include the path to the ODBC
Libraries:
1
Set LIBPATH for IBM AIX.
If the ODBC driver was installed in /opt/teradata/client/ODBC_32, or /opt/teradata/client/

ODBC_64, set LIBPATH to:
or
160

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.
Configuring the ODBC Driver for HP-UX

Follow the procedures in this section to configure the ODBC Driver for Teradata on HP-UX.
Copying the Template odbc.ini File for ODBC on HP-UX
software is installed. Before using an ODBC driver, copy this file to your home directory and
The default location of the .odbc.ini file is your home directory, but a different path for the file
or
Setting Environment Variables for ODBC on HP-UX

The SHLIB_PATH environment variable no longer has to be set 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.
Configuring the ODBC Driver for Sun Solaris

Follow the procedures in this section to configure the ODBC Driver for Teradata on Sun
Solaris.
Copying the Template odbc.ini File for ODBC on Sun Solaris
or
161

Setting Environment Variables for ODBC on Sun Solaris

The LD_LIBRARY_PATH environment variable no longer has to be set on Sun Solaris.
used.
Configuring the ODBC Driver for Linux

Follow the procedures in this section to configure the ODBC Driver for Teradata on Linux.
Copying the Template odbc.ini File for ODBC on Linux
or
Setting Environment Variables for the ODBC Libraries for ODBC on

Red Hat and SUSE Linux
The LD_LIBRARY_PATH environment variable no longer has to be set on Red Hat and SUSE
Linux.
used.
162


After the Teradata Access Module for JMS has been installed, see the readme file in the
installation folder for Teradata Access Module for JMS. The default installation directory for
Teradata Access Module for JMS is /opt/teradata/client/jmsaxsmod. Use an editor, like vi, to
open the readme file.

This section describes how to configure the Teradata Parallel Transporter for each of the UNIX
operating systems. Find the Configuration section for a platform and perform the procedures
to configure the Teradata Parallel Transporter.
For complete configuration information on the Teradata Parallel Transporter, see: Teradata
Parallel Transporter Reference.
Configuring Teradata Parallel Transporter for HP-UX

Follow the procedures in this section to configure the Teradata Parallel Transporter on HPUX.
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 shmseg
Semaphore parameters: semmni, semmns, semmnu and semmap
The following environment variables may also need to be modified:
TWB_ROOT
PATH
SHLIB_PATH
NLSPATH
Changing 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.
163

No kernel rebuild or reboot is required after making the change in the configuration file.
Configuration File Defaults on HP-UX
The configuration file contains parameters that determine the default behavior for Teradata
Parallel Transporter Infrastructure, such as:
Default checkpoint directory
Default log directory
The following is an example of the Teradata Parallel Transporter configuration file defaults:
CheckpointDirectory='/opt/teradata/client/13.0/tbuild/checkpoint'
LogDirectory='/opt/teradata/client/13.0/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.
Setting the Shared Memory Parameters on HP-UX
The Teradata Parallel Transporter Infrastructure installation process checks the values of the
shared memory parameters for the required minimum values:
Table 48 lists the HP-UX shared memory parameters.
Table 48: HP-UX Shared Memory Parameters
Parameter
Description
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.
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
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 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.
164

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
To increase the shmseg parameter to 10:

# /usr/sbin/kmtune -s shmseg=10
After the shared memory parameters are changed, rebuild the kernel using the mk_kernel
command as the root user:
# /usr/sbin/mk_kernel
After rebuilding the kernel, save the current vmunix file:

# cp /stand/vmunix /stand/vmunix.prev
Then, move the new vmunix file into the /stand directory:
# mv /stand/build/vmunix_test /stand/vmunix
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
Setting the Semaphore Parameters on HP-UX

semaphore parameters and increases them if they are not set properly:
Table 49 lists the HP-UX Semaphore parameters.
Table 49: HP-UX Semaphore Parameters
Parameter
Description
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
165

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.
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
After the semaphore parameters are changed, rebuild the kernel using the mk_kernel
command as the root user:
# /usr/sbin/mk_kernel
After rebuilding the kernel, save the current vmunix file:

# cp /stand/vmunix /stand/vmunix.prev
Move the new vmunix file into the /stand directory:

# mv /stand/build/vmunix_test /stand/vmunix
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.
Setting the Environment Variables on HP-UX
The Teradata Parallel Transporter Infrastructure installation updates the environment
variables in the system /etc/profile and /etc/csh.login files.
Table 50: HP-UX Environment Variables
166
TWB_ROOT

PATH
Add $TWB_ROOT/bin to the front of the

PATH environment variable.

Table 50: HP-UX Environment Variables (continued)
SHLIB_PATH

SHLIB_PATH environment variable.
NLSPATH
Add $TWB_ROOT/msg/%N to the front of

the NLSPATH 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.
system profile.
If the environment variables are updated in the system profile then the updates will be
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 set up the environment variables:
Bourne and Korn shell users
To set the TWB_ROOT environment variable:

# export TWB_ROOT

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:

# export PATH
To update the SHLIB_PATH environment variable:

# SHLIB_PATH=$TWB_ROOT/lib:$SHLIB_PATH
# export SHLIB_PATH
167

To update the NLSPATH environment variable:

# NLSPATH=$TWB_ROOT/msg/%N:$NLSPATH
# export NLSPATH
C-shell users

directory>
where: <Teradata Parallel Transporter installation directory> is the Teradata Parallel

Transporter installation directory. Run the /usr/bin/twbpkgrm tool to find the Teradata

To update the SHLIB_PATH environment variable:

# setenv SHLIB_PATH $TWB_ROOT"/lib:$SHLIB_PATH"

# setenv NLSPATH $TWB_ROOT"/msg/%N:$NLSPATH"
Switching the IPC Memory Choice to Shared Memory on HP-UX

Use the following procedure to switch the IPC Memory Choice to Shared Memory.
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.
Change directories to the Teradata Parallel Transporter install directory.

cd <install dir>
Remove the mmap directory using this command:

# rm -rf mmap
After following the above steps, Teradata Parallel Transporter will use shared memory as the
IPC memory choice.
The change does not require a kernel rebuild or a reboot.
Switching the IPC Memory Choice to Memory Mapped File
Use the following procedure to switch 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:
1

cd <install dir>
168

3
Create the mmap directory with 777 permission using these commands:
# mkdir mmap
# chmod 777 mmap
Teradata Parallel Transporter uses memory mapped file as the IPC memory choice. The
change does not require a kernel rebuild or a reboot.
Uninstalling Teradata Parallel Transporter Packages on HP-UX
There are two methods to uninstall Teradata Parallel Transporter software packages. The first
method to uninstall a software package is to use the twbpkgrm command.
The following procedure uninstalls the Teradata Parallel Transporter package.
Procedure - Uninstalling Teradata Parallel Transporter Packages Using twbpkgrm

Follow these steps to uninstall Teradata Parallel Transporter packages.
1
Run:
/usr/bin/twbpkgrm
and follow the instructions. See Uninstalling Teradata Warehouse Builder and Teradata
Parallel Transporter Packages on page 54 for information on using /usr/bin/twbpkgrm.
The second method to uninstall Teradata Parallel Transporter software is to use the swremove
command. The following procedures uses swremove to uninstall Teradata Parallel Transporter
packages.
Procedure - Uninstalling Teradata Parallel Transporter Packages Using swremove

Follow these steps to uninstall Teradata Parallel Transporter packages using swremove.
1
Log on as root
List all installed packages:

/usr/sbin/swlist
Alternately, if a specific package is installed enter:

/usr/bin/swlist <PkgName>
Following the order that the next section describes, uninstall the package:
/usr/sbin/swremove <PkgName>
Order to Uninstall Teradata Parallel Transporter 13.00.00

Packages
Remove the following packages in order.
pexpd000
plodd000
pstmd000
pupdd000
169

Then remove these packages in order:
tbldd000
papid000
Configuring Teradata Parallel Transporter for Sun Solaris

The procedures in this section configure the Teradata Parallel Transporter on Sun Solaris.
Teradata Parallel Transporter configuration normally requires modifications to one file in the
Teradata Parallel Transporter installation directory: twbcfg.ini.
Additionally, your system configuration may require modification of the following
parameters:
Shared memory parameters: SHMMAX and SHMMNI
Semaphore parameters: SEMMNI, SEMMNU and SEMMNS
You may need to modify the following environment variables:
TWB_ROOT
PATH
LD_LIBRARY_PATH
NLSPATH
Changing the twbcfg.ini File on Sun Solaris

file, $TWB_ROOT/twbcfg.ini, can be edited to change the default directory for checkpoint and
To make a change in this configuration file, log on as the root user, and use an editor to modify
the configuration 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 changes in the configuration file.
Configuration File Defaults on Sun Solaris
The Teradata Parallel Transporter configuration file defaults are:

Teradata Parallel Transporter jobs.
170

Setting the Shared Memory Parameters on Sun Solaris
shared memory parameters for the required minimum values.
Table 50 lists the Sun Solaris shared memory parameters.
Table 51: Sun Solaris Shared Memory Parameters
Parameter
Description
SHMMAX (minimum value of 4194304)
The SHMMAX value determines the

SHMMNI (minimum value of 200)
The SHMMNI value determines the system

SHMSEG (minimum value of 10)
The SHMSEG value determines the

maximum number of shared memory
Note: This is checked only on Solaris 8.
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 by updating the /etc/system file as the root user.
The following procedure increases the shared memory parameter to the minimum value.
Procedure - Increasing the Shared Memory Parameter to the Minimum Value

Follow these steps to increase the shared memory parameter to the minimum value.
1
To check the value of the shmseg parameter:

# /usr/sbin/sysdef -i |grep shmseg
To increase the shmseg parameter to 10:

# set shmsys:shminfo_shmseg=10
After the shared memory parameters are changed, a kernel rebuild is not required.
After the shared memory parameters are changed, reboot the system using the shutdown
command as the root user. The following command shuts down the system in 60 seconds:
171

Setting the Semaphore Parameters on Sun Solaris

semaphore parameters for the required minimum value:
Table 52 lists the Sun Solaris Semaphore parameters.
Table 52: Sun Solaris Semaphore Parameters
Parameter
Description
SEMMNI (set to 1000)
The SEMMNI value
SEMMNS (set to 1000)
The SEMMNS value
SHMMNU (set to 2500)
The SHMMNU value
The most significant is the SEMMNS semaphore parameter, which determines the number of
concurrent use.
Setting the Environment Variables on Sun Solaris
variables in the system /etc/profile and /etc/.login files.
Table 53 lists the Sun Solaris environment variables updated.
Table 53: Sun Solaris Environment Variables Updated
TWB_ROOT

PATH

LD_LIBRARY_PATH

LD_LIBRARY_PATH environment
variable.
NLSPATH

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

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.
The environment variables are updated on the command line, in the user's profile, or in the
system profile.
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:

# export TWB_ROOT


# export PATH
To update the LD_LIBRARY_PATH environment variable:

# LD_LIBRARY_PATH=$TWB_ROOT/lib:$LD_LIBRARY_PATH
# export LD_LIBRARY_PATH

# export NLSPATH
C-shell users

directory>

173


# setenv LD_LIBRARY_PATH $TWB_ROOT"/lib:$LD_LIBRARY_PATH"

Switching the IPC Memory Choice to Shared Memory on Sun

Solaris
The following procedure switches the IPC Memory choice to Shared Memory.

1

cd <install dir>

# rm -rf mmap
Teradata Parallel Transporter will use shared memory as the IPC memory choice.
Switching the IPC Memory Choice to Memory Mapped File on Sun
Solaris
The following procedure switches the IPC Memory choice to Memory Mapped File.

1

cd <install dir>
Create the mmap directory with 777 permission using these commands:
# mkdir mmap
# chmod 777 mmap
Teradata Parallel Transporter will use memory mapped file as the IPC memory choice.
Uninstalling Teradata Parallel Transporter on Sun Solaris
There are two methods to uninstall Teradata Parallel Transporter software packages.
The first method is to uninstall the software packages using the twbpkgrm command.
174

Procedure - Uninstalling Teradata Parallel Transporter Packages Using twbpkgrm

Follow these steps to uninstall Teradata Parallel Transporter packages using the twbpkgrm
command.
1
Log on as root.
Run:
/usr/bin/twbpkgrm
The second way to uninstall Teradata Parallel Transporter software is to use the pkgrm
command.
Procedure - Uninstalling Teradata Parallel Transporter Packages pkgrm

Follow these steps to uninstall Teradata Parallel Transporter packages using the pkgrm
command.
1
List all installed packages:

/usr/bin/pkginfo
Alternately, check for a specific package:

/usr/bin/pkginfo <PkgName>
Following the order described in the next section, uninstall the package:
/usr/sbin/pkgrm <PkgName>
175


Packages
pexpd000
plodd000
pstmd000
pupdd000
tbldd000
papid000
Configuring Teradata Parallel Transporter for Red Hat Linux

The procedures in this section configure the Teradata Parallel Transporter on Red Hat Linux.
Normally modifications to twbcfg.ini in the Teradata Parallel Transporter installation
directory are required.
Additionally, the system configuration requires modification of the following parameters:
Shared memory parameters: shmmax and shmmni
Semaphore parameters: semmni and semmnu
The following environment variables also need to be modified:
TWB_ROOT
PATH
LD_LIBRARY_PATH
NLSPATH
Changing the twbcfg.ini File on Red Hat Linux

file, $TWB_ROOT/twbcfg.ini can be edited to change the default directory for checkpoint and
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.
Configuration File Defaults on Red Hat Linux
176

The Teradata Parallel Transporter configuration file defaults are:

Teradata Parallel Transporter jobs.
Setting the Shared Memory Parameters on Red Hat Linux
shared memory parameters for the required minimum values:
Table 54 lists the Linux Red Hat shared memory parameters.
Table 54: Linux Red Hat Shared Memory Parameters
Parameter
Description
shmmax (minimum value of 4194304)
The shmmax value determines the

shmmni (minimum value of 200)
The shmmni value determines the system

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.
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
to increase the shmmni parameter to 200, you must be a root user:
On Red Hat Linux, add this line in the /etc/rc.d/rc.local file:

echo 200 > /proc/sys/kernel/shmmni
177

4
To shutdown the system in 1 minute:

# /sbin/shutdown -r +1
Setting the Semaphore Parameters on Red Hat Linux

semaphore parameters for the required minimum value:
Table 55 lists the Linux Red Hat Semaphore parameters.
Table 55: Red Hat Linux Semaphore Parameters
Parameter
Description
semmni (set to 1000)
The semmni value
semmns (set to 1000)
The semmns value
The most significant is the semmns semaphore parameter, which determines the number of
concurrent use.
Setting the Environment Variables on Red Hat Linux
variables in the system /etc/profile and /etc/csh.login files.
Table 56 lists the Red Hat Linux environment variables updated.
Table 56: Red Hat Linux Environment Variables Updated
TWB_ROOT

PATH

LD_LIBRARY_PATH

NLSPATH

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

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

# export TWB_ROOT


# export PATH

# LD_LIBRARY_PATH=$TWB_ROOT/lib:$LD_LIBRARY_PATH
# export LD_LIBRARY_PATH

# export NLSPATH
C-shell users

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


# setenv LD_LIBRARY_PATH $TWB_ROOT"/lib:$LD_LIBRARY_PATH"

Switching the IPC Memory Choice to Shared Memory on Red Hat

Linux
The following procedure increases the Shared Memory value to the minimum value.

1

cd <install dir>

# rm -rf mmap
Teradata Parallel Transporter will use shared memory as the IPC memory choice.
Switching the IPC Memory Choice to Memory Mapped File on Red
Hat Linux
The following procedure switches the IPC Memory Choice to Memory Mapped File:

1

cd <install dir>
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.
Uninstalling Teradata Parallel Transporter Software on Red Hat
Linux
There are two methods to uninstall Teradata Parallel Transporter software. The first method is
uninstalling using the twbpkgrm command.
180

Procedure - Uninstalling Teradata Parallel Transporter Using twbpkgrm

Follow these steps to uninstall Teradata Parallel Transporter using the twbpkgrm command.
1
Run:
/usr/bin/twbpkgrm
The second method is to uninstall Teradata Parallel Transporter software using the rpm
command:
Procedure - Uninstalling Teradata Parallel Transporter Using rpm

Follow these steps to uninstall Teradata Parallel Transporter software using the rpm command:
1
Log on as root.
Following the order indicated in the next section, uninstall the Teradata Parallel
Transporter package:
rpm -e <package name>

Packages
pexpd000
plodd000
pstmd000
pupdd000
tbldd000
papid000
181

182
CHAPTER 11
After You Install
This chapter describes how to verify that Teradata Tools and Utilities software has been
installed properly. This chapter provides the following topics:
Verifying the Installation of Individual Products
Verifying Basic Teradata Query (bteq)
Verifying Named Pipes Access Module (npaxsmod)
Verifying ODBC Driver for Teradata (tdodbc)
Verifying Shared Common Components for Internationalization for Teradata (tdicu)
Verifying Teradata Access Module for JMS
Verifying Teradata Archive/Recovery Utility (arc)
Verifying Teradata Call-Level Interface version 2 (cliv2)
Verifying Teradata C Preprocessor2 (sqlpp)
Verifying Teradata COBOL Preprocessor2 (cobpp)
Verifying Teradata Data Connector (piom)
Verifying Teradata JDBC Driver
Verifying Teradata FastExport (fastexp)
Verifying Teradata FastLoad (fastld)
Verifying Teradata Generic Security Services (TeraGSS)
Verifying Teradata MultiLoad (mload)
Verifying Teradata TPump (tpump)
Verifying Teradata Parallel Transporter API (papid000)
Verifying Teradata Parallel Transporter Export Operator (pexpd000)
Verifying Teradata Parallel Transporter Infrastructure (tbldd000)
Verifying Teradata Parallel Transporter Load Operator (plodd000)
Verifying Teradata Parallel Transporter Stream Operator (pstmd000)
Verifying Teradata Parallel Transporter Update Operator (pupdd000)
Verifying Teradata WebSphere MQ Access Module (mqaxsmod)
Verifying the Installation Using BTEQ
Verifying the Installation Using the CLI Sample Program
183
Chapter 11: After You Install

Verifying the Installation of Individual

Products
Procedure - Verifying Teradata Tools and Utilities Installation
Follow these steps to verify that Teradata Tools and Utilities product files have been properly
installed:
1
Verify that the directories specified in the following tables have been installed.
Verify that the files specified in the tables below have been installed in the directories
indicated.
Verifying Basic Teradata Query (bteq)

An asterisk (*) after a filename in Table 57 indicates that it is a softlink for a file that has
been installed in the directory (default) /opt/teradata/client/usr/<version>/bin.
Table 57 lists the files and the directories installed for each operating system supported by
Basic Teradata Query.
Table 57: Basic Teradata Query Files
Directory
IBM AIX
HP-UX
Solaris
Red Hat
Linux
SUSE
Linux
/usr/bin
bteq*
bteq*
bteq*
bteq*
bteq*
/usr/include
btnfyext.h*
btnfyext.h*
btnfyext.h*
btnfyext.h*
btnfyext.h*
/usr/sample
n/a
n/a
n/a
n/a
n/a
bteq
bteq
bteq
bteq
bteq
/opt/teradata/client/<version>/
sample
btnfyext.c
btnfyext.c
btnfyext.c
btnfyext.c
btnfyext.c
mkbtnfyext.aix
mkbtnfyext.hpu
x
mkbtnfyext.unx
mkbtnfyext.lin
ux
mkbtnfyext.li
nux
btnfyext.h
btnfyext.h
btnfyext.h
mkbtnfyext.hpu
x-ia64
include
184
btnfyext.h
btnfyext.h

Verifying Named Pipes Access Module (npaxsmod)

An asterisk (*) after a name in the Table 58 indicates that it is a softlink for files that have
been moved to the /opt/teradata/client/<version>/lib directories.
Named Pipes Access Module.
Table 58: Named Pipes Access Module Files
Directory
IBM AIX
HP-UX
Solaris
Red Hat
Linux
SUSE
Linux
/usr/lib
np_axsmod.so*
np_axsmod.sl*
np_axsmod.so*
np_axsmod.so*
np_axsmod.so*
np_axsmod.sl
np_axsmod.so
np_axsmod.so
np_axsmod.so
/opt/teradata/client/<version>/ np_axsmod.so
lib
Verifying ODBC Driver for Teradata (tdodbc)

The default directory for the ODBC Driver for Teradata for all platforms is:
and/or
An asterisk (*) after a name in the Table 59 indicates that it is a softlink for files that have
been moved to the /opt/teradata/client/<version>/lib directories.
Table 59 lists the files and the directories installed for each operating system supported by the
ODBC Driver for Teradata.
Table 59: ODBC Driver for Teradata Files
Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/lib
n/a
libivicu23*
libivicu23*
libivicu23*
/usr/lib
n/a
libddicu23*
libddicu23*
libddicu23*
/user/lib
n/a
libtdsso.sl*
libtdsso.so*
libtdsso.so*
/usr/lib
n/a
libodbcinst.sl*
libodbcinst.so*
libodbcinst.so*
/usr/lib
n/a
libtdparse.sl*
libtdparse.so*
libtdparse.so*
installation directory
README
README
README
README
odbc.ini
odbc.ini
odbc.ini
odbc.ini
odbcinst.ini
odbcinst.ini
odbcinst.ini
odbcinst.ini
/lib
tdata.so
tdata.sl
tdata.so
tdata.so
/bin
tdxwinapp
tdxwinapp
tdxwinapp
tdxwinapp
/include
odbcinst.h
odbcinst.h
odbcinst.h
odbcinst.h
185

Table 59: ODBC Driver for Teradata Files (continued)
Directory
IBM AIX
HP-UX
Solaris
Linux
/include
sql.h
sql.h
sql.h
sql.h
/include
sqlext.h
sqlext.h
sqlext.h
sqlext.h
/include
sqltypes.h
sqltypes.h
sqltypes.h
sqltypes.h
/include
sqlucode.h
sqlucode.h
sqlucode.h
sqlucode.h
/include
sqlunx.h
sqlunx.h
sqlunx.h
sqlunx.h
/include
tdsql.h
tdsql.h
tdsql.h
tdsql.h
/lib
libodbc.so
libodbc.sl
libodbc.so
libodbc.so
/<install dir>/lib
n/a
libivicu23
libivicu23
libivicu23
/<install dir>/lib
n/a
libddicu23
libddicu23
libddicu23
/<install dir>/lib
libodbcinst.so
libodbcinst.sl
libodbcinst.so
libodbcinst.so
/<install dir>/lib
libtdparse.so
libtdparse.sl
libtdparse.so
libtdparse.so
/<install dir>/lib
odbccurs.so
odbccurs.sl
odbccurs.so
odbccurs.so
/<install dir>/lib
odbctrac.so
odbctrac.sl
odbctrac.so
odbctrac.so
/<install dir>/lib
tdconndlg.so
dconndlg.sl
tdconndlg.so
tdconndlg.so
/<install dir>/lib
vscnctdlg.so
vscnctdlg.sl
vscnctdlg.so
vscnctdlg.so
/<install dir>/lib
odbc.so
n/a
n/a
n/a
/<install dir>/lib
tdata.so
tdata.sl
tdata.so
tdata.so
opt/teradata/client/<version>/
odbc_32/help/man/man5
tdata.man
tdata.man
tdata1.man
tdata.man
n/a
odbc.m
n/a
odbc.m
/<install dir>/samples/C
Makefile
Makefile
Makefile
Makefile
adhoc
adhoc
adhoc
adhoc
adhoc.c
adhoc.c
adhoc.c
adhoc.c
aix.includes
common.includes
common.includes
common.includes
or
/opt/teradata/client/
<version>/odbc_64/msg/man/
man5
ODBC_32/locale/en_US/
LC_MESSAGES
or/opt/teradata/client/
ODBC_64/locale/en_US/
LC_MESSAGES
186

Table 59: ODBC Driver for Teradata Files (continued)
Directory
IBM AIX
HP-UX
Solaris
Linux
error.c
error.c
error.c
error.c
/<install dir>/samples/C++
Makefile
Makefile
Makefile
Makefile
adhoc
adhoc
adhoc
adhoc
adhoc.cpp
adhoc.cpp
adhoc.cpp
adhoc.cpp
aix.includes
common.includes
common.includes
common.includes
error.cpp
error.cpp
error.cpp
error.cpp
<version>/odbc_32/msg
tdodbc.cat
tdodbc.cat
tdodbc.cat
tdodbc.cat
or
odbc_64/msg
Verifying Shared Common Components for Internationalization

for Teradata (tdicu)
Shared Common Components for Internationalization for Teradata.
Table 60: Shared Common Components for Internationalization for Teradata Files
Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/lib
libicudatatd.so
-> /opt/teradata/client/
<version>/tdicu/lib/
libicudatatd36.0.so
libicudatatd.sl
libicudatatd36.0.sl
libicudatatd.so
->/opt/teradata/client/
libicudatatd.so.36.0
libicudatatd.so.36
/usr/lib
libicui18ntd.so
libicui18ntd36.0.so
libicui18ntd.sl
libicui18ntd.sl.36.0
libicui18ntd.so
libicui18ntd.so.36.0
libicui18ntd.so.36
/usr/lib
libicuuctd.so
libicuuctd36.0.so
libicuuctd.sl
libicuuctd.sl.36.0
libicuuctd.so
libicuuctd.so.36.0
libicuuctd.so.36
libicuuctd.so.36.0
/usr/lib
libicuiotd.so
libicuiotd36.0.so
libicuiotd.sl
libicuiotd.sl.36.0
libicuiotd.so
libicuiotd.so.36.0
libicuiotd.so.36
libicuiotd.so.36.0
/usr/lib
libiculxtd36.so ->
libiculxtd36.0.so
libiculxtd36.sl ->
libiculxtd36.0.sl
libiculxtd36.so ->
libiculxtd36.0.so
libiculxtd36.so ->
libiculxtd36.0.so
187

Table 60: Shared Common Components for Internationalization for Teradata Files (continued)
Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/lib
libiculetd36.so ->
libiculetd36.0.so
libiculetd36.sl ->
libiculetd36.0.sl
libiculetd36.so ->
libiculetd36.0.so
libiculetd36.so ->
libiculetd36.0.so
<version>/tdicu/lib
libicudatatd.so
-> libicudatatd36.0.so
libicudatatd.sl
-> libicudatatd.sl.36.0
libicudatatd.so
-> libicudatatd.so.36.0
libicudatatd.so.36
<version>/tdicu/lib
libicui18ntd.so
-> libicui18ntd36.0.so
libicui18ntd.sl
-> libicui18ntd.sl.36.0
libicui18ntd.so
-> libicui18ntd.so.36.0
libicui18ntd.so.36
<version>/tdicu/lib
libicuuctd.so >libicuuctd36.0.so
libicuuctd.sl ->
libicuuctd.sl.36.0
libicuuctd.so ->
libicuuctd.so.36.0
libicuuctd.so.36 ->
libicuuctd.so.36.0
<version>/tdicu/lib
libicuiotd.so
->libicuiotd36.0.so
libicuiotd.sl
-> libicuiotd.sl.36.0
libicuiotd.so
-> libicuiotd.so.36.0
libicuiotd.so.36
<version>/tdicu/lib
libicudatatd36.0.so
libicudatatd.sl.36.0
<version>/tdicu/lib
libicui18ntd36.0.so
<version>/tdicu/lib
libicuuctd36.0.so
libicuuctd.sl.36.0
libicuuctd.so.36.0
libicuuctd.so.36.0
<version>/tdicu/lib
libicuiotd36.0.so
libicuiotd.sl.36.0
libicuiotd.so.36.0
libicuiotd.so.36.0
<version>/tdicu/lib
libiculetd.so.36.0
libiculetd.sl.36.0
libiculetd.so.36.0
libiculetd.so.36.0
<version>/tdicu/lib
libiculxtd.so.36.0
libiculxtd.sl.36.0
libiculxtd.so.36.0
libiculxtd.so.36.0
/usr/lib/lib_64
libicudatatd.so ->
<version>/tdicu/
lib_64/
libicudatatd36.0.so
n/a
n/a
n/a
/usr/lib/lib_64
n/a
libicuuctd.so ->
<version>/tdicu/
lib_64/libicuuctd36.0.so
n/a
n/a
/usr/lib/lib_64
libiculxtd36.so ->
<version>/tdicu/
lib_64/libiculxtd36.0.so
n/a
n/a
n/a
/usr/lib/lib_64
libiculetd36.so ->
<version>/tdicu/
lib_64/libiculetd36.0.so
n/a
n/a
n/a
188

Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/lib/lib_64
libicuiotd36.so ->
<version>/tdicu/
lib_64/libicuiotd36.0.so
n/a
n/a
n/a
/usr/lib/lib_64
libicui18ntd36.so ->
<version>/tdicu/
lib_64/
libicui18ntd36.0.so
n/a
n/a
n/a
/usr/lib/hpux64
n/a
libicudatatd.so ->
<version>/tdicu/
lib_64/
libicudatatd36.0.so
n/a
n/a
/usr/lib/hpux64
n/a
n/a
libicuuctd.so ->
<version>/tdicu/
n/a
/usr/lib/hpux64
n/a
libiculxtd36.so ->
<version>/tdicu/
n/a
n/a
/usr/lib/hpux64
n/a
libiculetd36.so ->
<version>/tdicu/
n/a
n/a
/usr/lib/hpux64
n/a
libicuiotd36.so ->
<version>/tdicu/
n/a
n/a
/usr/lib/hpux64
n/a
<version>/tdicu/
lib_64/
libicui18ntd36.0.so
n/a
n/a
/usr/lib/pa20_64
n/a
libicudatatd.sl ->
<version>/tdicu/
lib_64/
libicudatatd36.0.sl
n/a
n/a
/usr/lib/pa20_64
n/a
libicuuctd.sl ->
<version>/tdicu/
lib_64/libicuuctd36.0.sl
n/a
n/a
189

Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/lib/pa20_64
n/a
libiculxtd36.sl ->
<version>/tdicu/
lib_64/libiculxtd36.0.sl
n/a
n/a
/usr/lib/pa20_64
n/a
libiculetd36.sl ->
<version>/tdicu/
lib_64/libiculetd36.0.sl
n/a
n/a
/usr/lib/pa20_64
n/a
libicuiotd36.sl ->
<version>/tdicu/
lib_64/libicuiotd36.0.sl
n/a
n/a
/usr/lib/pa20_64
n/a
libicui18ntd36.sl ->
<version>/tdicu/
lib_64/
libicui18ntd36.0.sl
n/a
n/a
usr/lib/sparcv9
n/a
n/a
libicudatatd.so ->
<version>/tdicu/
lib_64/
libicudatatd36.0.so
n/a
usr/lib/sparcv9
n/a
n/a
libicuuctd.so ->
<version>/tdicu/
usr/lib/sparcv9
n/a
usr/lib/sparcv9
n/a
usr/lib/sparcv9
usr/lib/sparcv9
190
libiculxtd36.so ->
<version>/tdicu/
n/a
n/a
libiculetd36.so ->
<version>/tdicu/
n/a
n/a
n/a
libicuiotd36.so ->
<version>/tdicu/
n/a
n/a
n/a
<version>/tdicu/
lib_64/
libicui18ntd36.0.so
n/a

Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/lib/amd64
n/a
n/a
libicudatatd.so ->
<version>/tdicu/
lib_64/
libicudatatd36.0.so
n/a
/usr/lib/amd64
n/a
n/a
n/a
libicuuctd.so ->
<version>/tdicu/
/usr/lib/amd64
n/a
n/a
libiculxtd36.so ->
<version>/tdicu/
n/a
/usr/lib/amd64
n/a
n/a
libiculetd36.so ->
<version>/tdicu/
n/a
/usr/lib/amd64
n/a
n/a
libicuiotd36.so ->
<version>/tdicu/
n/a
/usr/lib/amd64
n/a
n/a
<version>/tdicu/
lib_64/
libicui18ntd36.0.so
n/a
/usr/lib/64
n/a
n/a
n/a
libicudatatd.so ->
<version>/tdicu/
lib_64/
libicudatatd36.0.so
/usr/lib/64
n/a
n/a
n/a
libicuuctd.so ->
<version>/tdicu/
/usr/lib/64
n/a
n/a
n/a
libiculxtd36.so ->
<version>/tdicu/
/usr/lib/64
n/a
n/a
n/a
libiculetd36.so ->
<version>/tdicu/
191

Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/lib/64
n/a
n/a
n/a
libicuiotd36.so ->
<version>/tdicu/
/usr/lib/64
n/a
n/a
n/a
<version>/tdicu/
lib_64/
libicui18ntd36.0.so
<version>/tdicu/lib_64
libicudatatd.so
-> libicudatatd36.0.so
libicudatatd.sl
-> libicudatatd.sl.36.0
libicudatatd.so
libicudatatd.so.36
libicui18ntd.so
-> libicui18ntd36.0.so
libicui18ntd.sl
-> libicui18ntd.sl.36.0
libicui18ntd.so
libicui18ntd.so.36
libicuuctd.so
->libicuuctd36.0.so
libicuuctd.sl
-> libicuuctd.sl.36.0
libicuuctd.so ->
libicuuctd.so.36.0
libicuuctd.so.36 ->
libicuuctd.so.36.0
libicuiotd.so
->libicuiotd36.0.so
libicuiotd.sl
-> libicuiotd.sl.36.0
libicuiotd.so
libicuiotd.so.36
libiculetd.so
->libiculetd.so.36.0
libiculetd.sl
->libiculetd.sl.36.0
libiculetd.so
->libiculetd.so.36.0
libiculetd.so>libiculetd.so.36.0
libiculxtd.so
->libiculxtd.so.36.0
libiculxtd.sl
->libiculxtd.sl.36.0
libiculxtd.so
libiculxtd.so
libicudatatd36.0.so
libicudatatd.sl.36.0
libicui18ntd36.0.so
libicuuctd36.0.so
libicuuctd.sl.36.0
libicuuctd.so.36.0
libicuuctd.so.36.0
libicuiotd36.0.so
libicuiotd.sl.36.0
libicuiotd.so.36.0
libicuiotd.so.36.0
libiculetd.so.36.0
libiculetd.sl.36.0
libiculetd.so.36.0
libiculetd.so.36.0
libiculxtd.so.36.0
libiculxtd.sl.36.0
libiculxtd.so.36.0
libiculxtd.so.36.0
Verifying Teradata Access Module for JMS

Teradata Access Module for JMS.
192

Table 61: Teradata Access Module for JMS Files
SUSE
Linux
32-bit
SUSE
Linux
64-bit
libjmsam.so
n/a
Directory
IBM AIX
HP-UX
Solaris
Red Hat
Linux
<version>/lib
libjmsam.so
libjmsam.sl
libjmsam.so
libjmsam.so
jmsam_charse
ts.properties
jmsam_charse jmsam_charset jmsam_charset jmsam_charset n/a

s.properties
s.properties
s.properties
ts.properties
<version>/ bin /jmsaxsmod
readme
readme
readme
readme
readme
n/a
jmsam.jar
jmsam.jar
jmsam.jar
jmsam.jar
jmsam.jar
n/a
Verifying Teradata Archive/Recovery Utility (arc)

An asterisk (*) after a filename in Table 62 indicates that it is a softlink for files that have
been moved to the /opt/teradata/client/<version>/bin directory.
Table 62 lists Teradata Archive/Recovery Utility (ARC) installed for 32-bit platforms.
Table 62: Teradata Archive/Recovery Utility (ARC) 32-bit Files
Directory
MP-RAS
IBM AIX
HP-UX
Solaris
Red Hat
Linux
SUSE
Linux
/usr/bin
arcmain.exe*
n/a
n/a
n/a
n/a
arcmain.exe*
n/a
n/a
n/a
n/a
arcmain.exe
/opt/teradata/client/<version>/ arcmain.exe
bin
Verifying Teradata Call-Level Interface version 2 (cliv2)

been moved to the /opt/teradata/client/<version>/include and the /opt/teradata/client/
<version>/lib directories.
Teradata Call-Leval Interface version 2.
Table 63: Teradata Call-Level Interface version 2 Files
SUSE
Linux
32-bit
SUSE
Linux
64-bit
Directory
IBM AIX
HP-UX
Solaris
Red Hat
Linux
/usr/lib
clispb.dat*
clispb.dat*
clispb.dat*
clispb.dat*
clispb.dat*
clispb.dat*
/usr/lib
errmsg.cat*
errmsg.cat*
errmsg.cat*
errmsg.cat*
errmsg.cat*
errmsg.cat*
/usr/lib
errmsg.txt
errmsg.txt*
errmsg.txt*
errmsg.txt*
errmsg.txt*
errmsg.txt*
/usr/lib
libcliv2.so*
libcliv2.sl*
libcliv2.so*
libcliv2.so*
libcliv2.so*
libcliv2.so*
/usr/lib
libtdusr.so*
libtdusr.sl*
libtdusr.so*
libtdusr.so*
libtdusr.so*
libtdusr.so*
193

Table 63: Teradata Call-Level Interface version 2 Files (continued)
SUSE
Linux
32-bit
SUSE
Linux
64-bit
Directory
IBM AIX
HP-UX
Solaris
Red Hat
Linux
/usr/include
cliv2if.h*
cliv2if.h*
cliv2if.h*
cliv2if.h*
cliv2if.h*
cliv2if.h*
/usr/include
coptypes.h*
coptypes.h*
coptypes.h*
coptypes.h*
coptypes.h*
coptypes.h*
/usr/include
coperr.h*
coperr.h*
coperr.h*
coperr.h*
coperr.h*
coperr.h*
/usr/include
dbca2px.h*
dbca2px.h*
dbca2px.h*
dbca2px.h*
dbca2px.h*
dbca2px.h*
/usr/include
dbcarea.h*
dbcarea.h*
dbcarea.h*
dbcarea.h*
dbcarea.h*
dbcarea.h*
/usr/include
dbcerr.h*
dbcerr.h*
dbcerr.h*
dbcerr.h*
dbcerr.h*
dbcerr.h*
/usr/include
dbchqep.h*
dbchqep.h*
dbchqep.h*
dbchqep.h*
dbchqep.h*
dbchqep.h*
/usr/include
parcel.h*
parcel.h*
parcel.h*
parcel.h*
parcel.h*
parcel.h*
/usr/include
mosiif.h*
mosiif.h*
mosiif.h*
mosiif.h*
mosiif.h*
mosiif.h*
/usr/lib/lib_64
libcliv2.so*
n/a
n/a
n/a
n/a
n/a
/usr/lib/lib_64
libtdusr.so*
n/a
n/a
n/a
n/a
n/a
/usr/lib/pa20_64
n/a
libcliv2.sl*
n/a
n/a
n/a
n/a
/usr/lib/pa20_64
n/a
libtdusr.sl*
n/a
n/a
n/a
n/a
/usr/lib/sparcv9
n/a
n/a
libcliv2.so*
n/a
n/a
n/a
/usr/lib/sparcv9
n/a
n/a
libtdusr.so*
n/a
n/a
n/a
/usr/lib/lib-i386
n/a
n/a
n/a
libcliv2.so*
n/a
n/a
/usr/lib/lib-i386
n/a
n/a
n/a
libtdusr.so*
n/a
n/a
<version>/lib64
libcliv2.so
libcliv2.sl
libcliv2.so
libcliv2.so
libcliv2.so
libcliv2.so
<version>/lib64
libtdusr.so
libtdusr.sl
libtdusr.so
libtdusr.so
libtdusr.so
libtdusr.so
<version>/lib64
errmsg.cat
errmsg.cat
errmsg.cat
errmsg.cat
errmsg.cat
errmsg.cat
<version>/lib64
errmsg.txt
errmsg.txt
errmsg.txt
errmsg.txt
errmsg.txt
errmsg.txt
<version>/lib64
clispb.dat
clispb.dat
clispb.dat
clispb.dat
clispb.dat
clispb.dat
<version>/include
coptypes.h
coptypes.h
coptypes.h
coptypes.h
coptypes.h
coptypes.h
<version>/include
dbchqep.h
dbchqep.h
dbchqep.h
dbchqep.h
dbchqep.h
dbchqep.h
194

Table 63: Teradata Call-Level Interface version 2 Files (continued)
SUSE
Linux
32-bit
SUSE
Linux
64-bit
Directory
IBM AIX
HP-UX
Solaris
Red Hat
Linux
<version>/include
dbca2px.h
dbca2px.h
dbca2px.h
dbca2px.h
dbca2px.h
dbca2px.h
<version>/include
cliv2if.h
cliv2if.h
cliv2if.h
cliv2if.h
cliv2if.h
cliv2if.h
<version>/include
coperr.h
coperr.h
coperr.h
coperr.h
coperr.h
coperr.h
<version>/include
dbcarea.h
dbcarea.h
dbcarea.h
dbcarea.h
dbcarea.h
dbcarea.h
<version>/include
parcel.h
parcel.h
parcel.h
parcel.h
parcel.h
parcel.h
<version>/include
dbcerr.h
dbcerr.h
dbcerr.h
dbcerr.h
dbcerr.h
dbcerr.h
<version>/include
mosiff.h
mosiff.h
mosiff.h
mosiff.h
mosiff.h
mosiff.h
/opt/teradata/client<version>/ errmsg.cat
/lib
errmsg.cat
errmsg.cat
errmsg.cat
errmsg.cat
errmsg.cat
/opt/teradata/client<version>/ errmsg.txt
/lib
errmsg.txt
errmsg.txt
errmsg.txt
errmsg.txt
errmsg.txt
/opt/teradata/client<version>/ clispb.dat
/lib
clispb.dat
clispb.dat
clispb.dat
clispb.dat
clispb.dat
<version>/sample
n/a
n/a
n/a
n/a
CliLgn.Ex.c
CliLgn.Ex.c
<version>/sample
n/a
n/a
n/a
n/a
CliPPS.c
CliPPS.c
/opt/teradata/client<version>/ n/a
/sample
n/a
n/a
n/a
clisamp.c
clisamp.c
/opt/teradata/client<version>/ n/a
/sample
n/a
n/a
n/a
makesamp.lx
makesamp.lx
<version>/sample
n/a
n/a
n/a
n/a
makerdusr.lx
makerdusr.lx
<version>/sample
n/a
n/a
n/a
n/a
n/a
makesamp.lx
64
<version>/sample
n/a
n/a
n/a
n/a
n/a
makerdusr.lx6
4
195

Verifying Teradata C Preprocessor2 (sqlpp)

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.
Table 64 lists the files and the directories installed for each operating system supported by C
Preprocessor2.
Table 64: Teradata C Preprocessor2 Files for IBM AIX, HP-UX, HP Itanium, Solaris SPARC, Solaris Opteron
Directory
IBM AIX
HP-UX
HP-UX Itanium
Solaris SPARC
Solaris Opteron
/usr/bin
ppcmain*
ppcmain*
ppcmain*
ppcmain*
ppcmain*
/usr/lib
libppruntim.so*
libppruntim.sl*
n/a
libppruntim.so*
libppruntim.so*
/usr/lib/hpux64
n/a
n/a
libppruntim.so*
n/a
n/a
/usr/bin/bin_64
ppcmain*
n/a
n/a
n/a
n/a
/usr/lib/lib_64
libppruntim.so*
n/a
n/a
n/a
n/a
/usr/bin/pa20_64
n/a
ppcmain*
n/a
n/a
n/a
/usr/lib/pa20_64
n/a
libppruntim.sl*
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*
<version>/bin
ppcmain
ppcmain
ppcmain
ppcmain
ppcmain
<version>/bin64
ppcmain
ppcmain
n/a
ppcmain
ppcmain
<version>/lib
libppruntim.so
libppruntim.sl
n/a
libppruntim.so
libppruntim.so
<version>/lib64
libppruntim.so
libppruntim.sl
libppruntim.so
libppruntim.so
libppruntim.so
<version>/sample
n/a
LABSBTEQ
LABSBTEQ
LABSBTEQ
LABSBTEQ
<version>/sample
PPCLB1
PPCLB1
PPCLB1
PPCLB1
PPCLB1
<version>/sample
PPCLB2
PPCLB2
PPCLB2
PPCLB2
PPCLB2
<version>/sample
PPCLB3
PPCLB3
PPCLB3
PPCLB3
PPCLB3
196

Table 64: Teradata C Preprocessor2 Files for IBM AIX, HP-UX, HP Itanium, Solaris SPARC, Solaris Opteron (continued)
Directory
IBM AIX
HP-UX
HP-UX Itanium
Solaris SPARC
Solaris Opteron
<version>/sample
PPCLB4
PPCLB4
PPCLB4
PPCLB4
PPCLB4
<version>/sample
PPCLB5
PPCLB5
PPCLB5
PPCLB5
PPCLB5
<version>/sample
PPCLB6
PPCLB6
PPCLB6
PPCLB6
PPCLB6
<version>/sample
PPCLB7
PPCLB7
PPCLB7
PPCLB7
PPCLB7
<version>/sample
PPCLB8
PPCLB8
PPCLB8
PPCLB8
PPCLB8
<version>/sample
PPCLB9
PPCLB9
PPCLB9
PPCLB9
PPCLB9
Table 65 lists the files and the directories installed on Linux operating systems supported by
Teradata C Preprocessor.
Table 65: Teradata C Preprocessor2 Files for Red Hat Linux 32-bit, Red Hat Linux 64-bit, SUSE Linux 64-bit
Directory
Red Hat Linux

32-bit
Red Hat Linux

64-bit Itanium
SUSE Linux
64-bit
/usr/bin
ppcmain*
n/a
n/a
/usr/lib
lippruntim.so*
n/a
n/a
/usr/bin64
n/a
ppcmain*
ppcmain*
/usr/lib64
n/a
lippruntim.so*
lippruntim.so*
bin
ppcmain
n/a
n/a
bin64
n/a
ppcmain
ppcmain
lib
lippruntim.so
n/a
n/a
/opt/teradata/client<version>/
lib64
n/a
lippruntim.so
lippruntim.so
sample
LABSBTEQ
LABSBTEQ
LABSBTEQ
197

Table 65: Teradata C Preprocessor2 Files for Red Hat Linux 32-bit, Red Hat Linux 64-bit, SUSE Linux 64-bit (continued)
Red Hat Linux

32-bit
Red Hat Linux

64-bit Itanium
SUSE Linux
64-bit
sample
PPCLB1
PPCLB1
PPCLB1
sample
PPCLB2
PPCLB2
PPCLB2
sample
PPCLB3
PPCLB3
PPCLB3
sample
PPCLB4
PPCLB4
PPCLB4
sample
PPCLB5
PPCLB5
PPCLB5
sample
PPCLB6
PPCLB6
PPCLB6
sample
PPCLB7
PPCLB7
PPCLB7
sample
PPCLB8
PPCLB8
PPCLB8
sample
PPCLB9
PPCLB9
PPCLB9
Directory
Verifying Teradata COBOL Preprocessor2 (cobpp)

Teradata COBOL Preprocessor2.
Table 66: Teradata COBOL Preprocessor2 Files
Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/bin
ppbmain*
ppbmain*
n/a
n/a
/usr/bin/bin_64
ppbmain*
n/a
n/a
n/a
/usr/lib
libppruntim.so*
libppruntim.sl*
n/a
n/a
/usr/lib/lib_64
libppruntim.so*
n/a
n/a
n/a
bin
ppbmain
ppbmain
n/a
n/a
bin64
ppbmain
n/a
n/a
n/a
198

Table 66: Teradata COBOL Preprocessor2 Files (continued)
Directory
IBM AIX
HP-UX
Solaris
Linux
lib
libppruntim.so
libppruntim.sl
n/a
n/a
lib64
libppruntim.so
n/a
n/a
n/a
sample
n/a
LABSBTEQ
n/a
n/a
sample
PPCOBLB1
PPCOBLB1
n/a
n/a
usr/sample
PPCOBLB2
PPCOBLB2
n/a
n/a
usr/sample
PPCOBLB3
PPCOBLB3
n/a
n/a
usr/sample
PPCOBLB4
PPCOBLB4
n/a
n/a
usr/sample
PPCOBLB5
PPCOBLB5
n/a
n/a
usr/sample
PPCOBLB6
PPCOBLB6
n/a
n/a
usr/sample
PPCOBLB7
PPCOBLB7
n/a
n/a
usr/sample
PPCOBLB8
PPCOBLB8
n/a
n/a
usr/sample
PPCOBLB9
PPCOBLB9
n/a
n/a
Verifying Teradata Data Connector (piom)

been moved to the /opt/teradata/client/<version>/include and the /opt/teradata/client/
<version>/lib directories.
Teradata Data Connector.
Table 67: Teradata Data Connector Files
Directory
IBM AIX
HP-UX
Solaris
Red Hat
Linux
SUSE
Linux
/usr/lib
libpm.so*
libpm.sl*
libpm.so*
libpm.so*
libpm.so*
/usr/include
pmdcomt.h*
pmdcomt.h*
pmdcomt.h*
pmdcomt.h*
pmdcomt.h*
199

Table 67: Teradata Data Connector Files (continued)
Directory
IBM AIX
HP-UX
Solaris
Red Hat
Linux
SUSE
Linux
/usr/include
pmddamt.h*
pmddamt.h*
pmddamt.h*
pmddamt.h*
pmddamt.h*
/usr/include
pmtypes.h*
pmtypes.h*
pmtypes.h*
pmtypes.h*
pmtypes.h*
lib
libpm.so
libpm.sl
libpm.so
libpm.so
libpm.so
include
pmdcomt.h
pmdcomt.h
pmdcomt.h
pmdcomt.h
pmdcomt.h
include
pmddamt.h
pmddamt.h
pmddamt.h
pmddamt.h
pmddamt.h
include
pmtypes.h
pmtypes.h
pmtypes.h
pmtypes.h
pmtypes.h
Verifying Teradata JDBC Driver

Teradata JDBC Driver.
Table 68: Teradata JDBC Driver Files
Directory
IBM AIX
HP-UX
Solaris
Linux
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
Verifying Teradata FastExport (fastexp)

been moved to the /opt/teradata/client/<version>/bin, /opt/teradata/client/<version>/include,
and the /opt/teradata/client/<version>/sample directories.
200

Teradata FastExport.
Table 69: Teradata FastExport Files
Directory
IBM AIX
HP-UX
Solaris
Linux
/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.aix*
mkexpext.hpux*
mkexpext.unx*
mkexpext.linux*
<version>/bin
fexp
fexp
fexp
fexp
<version>/include
expnfyxt.h
expnfyxt.h
expnfyxt.h
expnfyxt.h
<version>/sample
expnfyxt.c
expnfyxt.c
expnfyxt.c
expnfyxt.c
<version>/sample
mkexpext.aix
mkexpext.hpux
mkexpext.unx
mkexpext.linux
Verifying Teradata FastLoad (fastld)

been moved to the /opt/teradata/client/<version>/bin and the /opt/teradata/client/<version>/
sample directories.
Teradata FastLoad.
Table 70: Teradata FastLoad Files
Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/bin
fastload*
fastload*
fastload*
fastload*
/usr/sample
blexit.c*
blkexit.c*
blkexit.c*
blkexit.c*
/usr/sample
blexitr.c*
blkexitr.c*
blkexitr.c*
blkexitr.c*
/usr/sample
flnfyext.c*
flnfyext.c*
flnfyext.c*
flnfyext.c*
<version>/bin
fastload
fastload
fastload
fastload
<version>/sample
blexit.c
blkexit.c
blkexit.c
blkexit.c
<version>/sample
blexitr.c
blkexitr.c
blkexitr.c
blkexitr.c
201

Table 70: Teradata FastLoad Files (continued)
Directory
IBM AIX
HP-UX
Solaris
Linux
<version>/sample
flnfyext.c
flnfyext.c
flnfyext.c
flnfyext.c
Verifying Teradata Generic Security Services (TeraGSS)

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.
Teradata Generic Security Services.
Table 71: Teradata Generic Security Services Version Files
Platform
Package
File
AIX
teragss_aix-power
/usr/teragss/aix-power/<version>
AIX
teragss_aix-power-32
/usr/teragss/aix-power.32/<version>
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>
Solaris
teragss_solaris-sparc
/usr/teragss/solaris-sparc/<version>
Solaris
teragss_solaris-sparc32
/usr/teragss/solaris-sparc.32/<version>
Red Hat Linux
/usr/teragss/redhatlinux-i386/<version>
Red Hat Linux
/usr/teragss/redhatlinux-i64/<version>
Red Hat Linux
/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
/usr/teragss/suselinux-ia64/<version>
Verifying Teradata MultiLoad (mload)

been moved to the /opt/teradata/client/<version>/bin, /opt/teradata/client/<version>/include,
and the /opt/teradata/client/<version>/sample directories.
Teradata MultiLoad.
202

Table 72: Teradata MultiLoad Files
Directory
IBM AIX
HP-UX
Solaris
Linux
/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.aix*
mkmldext.hpux*
mkmldext.unx*
mkmldext.linux*
<version>/bin
mload
mload
mload
mload
<version>/include
mldnfyxt.h
mldnfyxt.h
mldnfyxt.h
mldnfyxt.h
<version>/sample
mldnfyxt.c
mldnfyxt.c
mldnfyxt.c
mldnfyxt.c
<version>/sample
mkmldext.aix
mkmldext.hpux
mkmldext.unx
mkmldext.linux
Verifying Teradata TPump (tpump)

been moved to the /opt/teradata/client/<version>/bin and /opt/teradata/client/<version>/lib
directories.
Teradata TPump.
Table 73: Teradata TPump Files
Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/bin
tpumpexe*
tpumpexe*
tpumpexe*
tpumpexe*
/usr/bin
tpump*
tpump*
tpump*
n/a
/usr/lib
tdatpump.cfg*
tdatpump.cfg*
tdatpump.cfg*
tdatpump.cfg*
<version>/bin
tpumpexe
tpumpexe
tpumpexe
tpumpexe*
<version>/bin
tpump
tpump
tpump
n/a
<version>/lib
tdatpump.cfg
tdatpump.cfg
tdatpump.cfg
tdatpump.cfg
<version>/sample
makinmod.3000
makinmod.3000
makinmod.3000
makinmod.3000
<version>/sample
tldnfyxt.c
tldnfyxt.c
n/a
tldnfyxt.c
203

Table 73: Teradata TPump Files (continued)
Directory
IBM AIX
HP-UX
Solaris
Linux
<version>/sample
tpumpimd.c
tpumpimd.c
tpumpimd.c
tpumpimd.c
<version>/sample
tpumpar.csql
tpumpar.csql
tpumpar.csql
tpumpar.csql

API (papid000)
The default value for <INSTALLDIR> is /opt/teradata/client/<version>/tbuild.
Teradata Parallel Transporter API.
Table 74: Teradata Parallel Transporter API Files
Directory
IBM AIX
HP-UX
Itanium
HP-UX
Risc
Solaris
SPARC
Solaris
Opteron
Linux
<INSTALLDIR>/lib
libtelapi.so
n/a
libtelapi.s1
libtelapi.so
libtelapi.so
libtelapi.so
libopcommon.s
o
libopcommon. libopcommon. libopcommo

n.so
sl
so
libopcommo
n.so
libopcommon
.so
libpxicu.so
libpxicu.so
libpxicu.sl
libpxicu.so
libpxicu.so
libpxicu.so
libtelapi.so
libtelapi.so
libtelapi.s1
libtelapi.so
libtelapi.so
libtelapi.so
libopcommon.s
o
libopcommon. libopcommon. libopcommo

n.so
sl
so
libopcommo
n.so
libopcommon
.so
libpxicu.so
libpxicu.so
libpxicu.sl
libpxicu.so
libpxicu.so
libpxicu.so
<INSTALLDIR>/msg
opermsgs.cat
opermsgs.cat
opermsgs.cat
opermsgs.cat
opermsgs.cat
opermsgs.cat
<INSTALLDIR>/nsg64
opermsgs.cat
opermsgs.cat
opermsgs.cat
opermsgs.cat
opermsgs.cat
opermsgs.cat
<INSTALLDIR>/tptapi/inc
connection.h
connection.h
connection.h
connection.h
connection.h
connection.h
DMLGroup.h
DMLGroup.h
DMLGroup.h
DMLGroup.
h
DMLGroup.
h
DMLGroup.h
schema.h
schema.h
schema.h
schema.h
schema.h
schema.h
<INSTALLDIR>/tptapi/
sample/inc
connection.h
connection.h
connection.h
connection.h
connection.h
connection.h
sample/inc
DMLGroup.h
DMLGroup.h
DMLGroup.h
DMLGroup.
h
DMLGroup.
h
DMLGroup.h
sample/inc
schema.h
schema.h
schema.h
schema.h
schema.h
schema.h
sample/common
OptionsManag
er.cpp
OptionsMana OptionsMana OptionsMan

ger.cpp
ger.cpp
ager.cpp
OptionsMan
ager.cpp
OptionsMan
ager.cpp
<INSTALLDIR>/lib64
204

Table 74: Teradata Parallel Transporter API Files (continued)
Directory
IBM AIX
HP-UX
Itanium
sample/common
OptionsManag
er.h
OptionsMana OptionsMana OptionsMan

ger.h
ger.h
ager.h
sample/generic
GenericDriver.
cpp
GenericDriver GenericDriver GenericDrive GenericDrive GenericDrive

.cpp
.cpp
r.cpp
r.cpp
r.cpp
sample/generic
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
sample/generic
input.txt
input.txt
input.txt
input.txt
input.txt
input.txt
sample/generic
infile.bigEndia
n
infile.bigEndi
an
infile.bigEndi
an
infile.bigEndi infile.littleEn
an
dian
sample/generic
makedriver.aix
makedriver.hp makedriver.hp makedriver.s

ux
ux
ol_s
makedriver.s
ol_o
makedriver.li
nux
sample/generic
cleanupTables.
bteq
cleanupTables
.bteq
cleanupTable
s.bteq
cleanupTable
s.bteq
sample/generic
setupTables.bte
q
setupTables.bt setupTables.bt setupTables.b setupTables.b setupTables.b

eq
eq
teq
teq
teq
sample/generic/inc
GenericDriver.
h
GenericDriver GenericDriver GenericDrive GenericDrive GenericDrive

.h
.h
r.h
r.h
r.h
sample/blockloading
BlockLoad.cpp
BlockLoad.cpp BlockLoad.cpp BlockLoad.cp BlockLoad.cp BlockLoad.cp

p
p
p
sample/blockloading
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
sample/blockloading
input.txt
input.txt
input.txt
input.txt
input.txt
input.txt
sample/blockloading
infile.bigEndia
n
infile.bigEndi
an
infile.bigEndi
an
an
dian
sample/blockloading
makeblock.aix
makeblock.hp
ux
makeblock.hp
ux
makeblock.so makeblock.so makeblock.lin

l_s
l_o
ux
sample/blockloading
cleanupTables.
bteq
cleanupTables
.bteq
cleanupTables
.bteq
cleanupTable
s.bteq
sample/blockloading
setupTables.bte
q

eq
eq
teq
teq
teq
sample/blockloading/inc
BlockLoad.h
BlockLoad.h
BlockLoad.h
BlockLoad.h
sample/checkpoint
checkpoint.cpp
checkpoint.cp
p
checkpoint.cp
p
checkpoint.cp checkpoint.cp checkpoint.cp

p
p
p
HP-UX
Risc
cleanupTables
.bteq
Solaris
SPARC
cleanupTable
s.bteq
Solaris
Opteron
Linux
OptionsMan
ager.h
OptionsMan
ager.h
cleanupTable
s.bteq
BlockLoad.h
infile.littleEn
dian
infile.littleEn
dian
cleanupTable
s.bteq
BlockLoad.h
205

Directory
IBM AIX
HP-UX
Itanium
HP-UX
Risc
Solaris
SPARC
Solaris
Opteron
Linux
sample/checkpoint
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
sample/checkpoint
input.txt
input.txt
input.txt
input.txt
input.txt
input.txt
sample/checkpoint
infile.bigEndia
n
infile.bigEndi
an
infile.bigEndi
an
an
dian
sample/checkpoint
makecheckpoin makecheckpoi
t.aix
nt.hpux
makecheckpoi
nt.hpux
makecheckpo makecheckpo makecheckpo

int.sol_s
int.sol_o
int.linux
sample/checkpoint
cleanupTables.
bteq
cleanupTables
.bteq
cleanupTables
.bteq
cleanupTable
s.bteq
sample/checkpoint
setupTables.bte
q

eq
eq
teq
teq
teq
sample/checkpoint/inc
checkpoint.h
checkpoint.h
checkpoint.h
checkpoint.h
checkpoint.h
checkpoint.h
sample/getbuffer
GetBuffer.cpp
GetBuffer.cpp
GetBuffer.cpp
GetBuffer.cp
p
GetBuffer.cp
p
GetBuffer.cpp
sample/getbuffer
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
sample/getbuffer
input.txt
input.txt
input.txt
input.txt
input.txt
input.txt
sample/getbuffer
makedriver.aix
makedriver.hp makedriver.hp makedriver.s

ux
ux
ol_s
makedriver.s
ol_o
makedriver.li
nux
sample/getbuffer
cleanupTables.
bteq
cleanupTables
.bteq
cleanupTable
s.bteq
cleanupTable
s.bteq
cleanupTable
s.bteq
cleanupTable
s.bteq
sample/getbuffer
setupTables.bte
q
setupTables.b
teq
setupTables.b
teq
setupTables.b setupTables.b setupTables.b

teq
teq
teq
sample/getbuffer/inc
GetBuffer.h
GetBuffer.h
GetBuffer.h
GetBuffer.h
GetBuffer.h
GetBuffer.h
sample/xsp
n/a
n/a
n/a
n/a
n/a
GenericDrive
r.cpp
sample/xsp
n/a
n/a
n/a
n/a
n/a
GenericDrive
r.h
sample/xsp
n/a
n/a
n/a
n/a
n/a
OptionsRead
er.cpp
sample/xsp
n/a
n/a
n/a
n/a
n/a
OptionsRead
er.h
206
cleanupTable
s.bteq
infile.littleEn
dian
cleanupTable
s.bteq

Directory
IBM AIX
HP-UX
Itanium
HP-UX
Risc
Solaris
SPARC
Solaris
Opteron
sample/xsp
n/a
n/a
n/a
n/a
n/a
makedriver.li
nux
sample/xsp
n/a
n/a
n/a
n/a
n/a
xsp.cpp
sample/xsp
n/a
n/a
n/a
n/a
n/a
input.lod
sample/xsp
n/a
n/a
n/a
n/a
n/a
input.exp
sample/xsp
n/a
n/a
n/a
n/a
n/a
input.stm
sample/xsp
n/a
n/a
n/a
n/a
n/a
input.upd
sample/xsp
n/a
n/a
n/a
n/a
n/a
infile.littleEn
dian
sample/multiple
MultipleOperat MultipleOper
ors.cpp
ators.cpp
MultipleOper
ators.cpp
MultipleOpe
rators.cpp
MultipleOpe
rators.cpp
MultipleOper
ators.cpp
sample/multiple
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
main.cpp
sample/multiple
input.txt
input.txt
input.txt
input.txt
input.txt
input.txt
sample/multiple
makemultiple.
aix
makemultiple. makemultiple. makemultipl makemultipl makemultiple

hpux
hpux
e.sol_s
e.sol_o
.linux
sample/multiple
cleanupTables.
bteq
cleanupTables
.bteq
sample/multiple
setupTables.bte
q

eq
eq
teq
teq
teq
sample/multiple/inc
MultipleOperat MultipleOper
ors.h
ators.h
MultipleOper
ators.h
MultipleOpe
rators.h
MultipleOpe
rators.h
MultipleOper
ators.h
sample/multi_node
multitest.cpp
multitest.cpp
multitest.cpp
multitest.cpp
multitest.cpp
multitest.cpp
sample/multi_node
synchronize.cp
p
synchronize.c
pp
synchronize.c
pp
synchronize.c synchronize.c synchronize.c

pp
pp
pp
sample/multi_node
fileio.cpp
fileio.cpp
fileio.cpp
fileio.cpp
fileio.cpp
fileio.cpp
sample/multi_node
master.cpp
master.cpp
master.cpp
master.cpp
master.cpp
master.cpp
cleanupTables
.bteq
cleanupTable
s.bteq
cleanupTable
s.bteq
Linux
cleanupTable
s.bteq
207

Directory
IBM AIX
HP-UX
Itanium
HP-UX
Risc
Solaris
SPARC
Solaris
Opteron
Linux
sample/multi_node
slave.cpp
slave.cpp
slave.cpp
slave.cpp
slave.cpp
slave.cpp
sample/multi_node
master_input.t
xt
master_input. master_input. master_input master_input master_input

txt
txt
.txt
.txt
.txt
sample/multi_node
slave_input.txt
slave_input.tx slave_input.tx slave_input.t

t
t
xt
sample/multi_node
infilemaster.big infilemaster.b infilemaster.b infilemaster.b infilemaster.l

Endian
igEndian
igEndian
igEndian
ittleEndian
sample/multi_node
infileslave.bigE
ndian.1
infileslave.big
Endian.1
sample/multi_node
makemulti.aix
makemulti.hp makemulti.hp makemulti.so makemulti.so makemulti.li

ux
ux
l_s
l_o
nux
sample/multi_node
cleanupTables.
bteq
cleanupTables
.bteq
sample/multi_node
setupTables.bte
q

eq
eq
teq
teq
teq
sample/multi_node/inc
fileio.h
fileio.h
fileio.h
fileio.h
fileio.h
fileio.h
multitest.h
multitest.h
multitest.h
multitest.h
multitest.h
multitest.h
synchronize.h
synchronize.h
synchronize.h
synchronize.
h
synchronize.
h
synchronize.h
sample/threads
PerfTestMessag
e.cpp
PerfTestMessa PerfTestMessa PerfTestMess

ge.cpp
ge.cpp
age.cpp
PerfTestMess
age.cpp
PerfTestMess
age.cpp
sample/threads
TelapiThreadT
est.cpp
TelapiThread
Test.cpp
TelapiThread
Test.cpp
TelapiThread TelapiThread TelapiThread

Test.cpp
Test.cpp
Test.cpp
sample/threads
makeparallel.ai makeparallel.
x
hpux
makeparallel.
hpux
makeparallel. makeparallel. makeparallel.

sol_s
sol_s
linux
sample/threads
TestBase.cpp
TestBase.cpp
TestBase.cpp
TestBase.cpp
sample/threads
TestExport.cpp
TestExport.cp
p
TestExport.cp
p
TestExport.cp TestExport.cp TestExport.cp

p
p
p
sample/threads
TestLoad.cpp
TestLoad.cpp
TestLoad.cpp
TestLoad.cpp
TestLoad.cpp
TestLoad.cpp
sample/threads
TestSim.cpp
TestSim.cpp
TestSim.cpp
TestSim.cpp
TestSim.cpp
TestSim.cpp
208
infileslave.big
Endian.1
cleanupTables
.bteq
slave_input.t
xt
slave_input.t
xt
infilemaster.li
ttleEndian
infileslave.big infileslave.litt infileslave.litt

Endian.1
leEndian.1
leEndian.1
cleanupTable
s.bteq
cleanupTable
s.bteq
TestBase.cpp
cleanupTable
s.bteq
TestBase.cpp

HP-UX
Itanium
HP-UX
Risc
Solaris
SPARC
Solaris
Opteron
Linux
TestStream.cp
p
TestStream.cp
p
TestStream.c
pp
TestStream.c
pp
TestStream.c
pp
sample/threads
TestUpdate.cpp TestUpdate.cp TestUpdate.cp TestUpdate.c

p
p
pp
TestUpdate.c
pp
TestUpdate.c
pp
sample/threads
ThreadTest.cpp ThreadTest.cp
p
ThreadTest.cp ThreadTest.c
p
pp
ThreadTest.c
pp
ThreadTest.c
pp
sample/threads
ThreadTestPar
ameters.cpp
ThreadTestPa
rameters.cpp
ThreadTestPa
rameters.cpp
ThreadTestP ThreadTestPa
arameters.cp rameters.cpp
p
sample/threads
Synchronizer.c
pp
Synchronizer.c Synchronizer.c Synchronizer. Synchronizer. Synchronizer.

pp
pp
cpp
cpp
cpp
sample/threads
input.txt
input.txt
sample/threads
loadData.bigE
ndian
loadData.bigE loadData.bigE loadData.big

ndian
ndian
Endian
loadData.littl loadData.littl
eEndian
eEndian
sample/threads
cleanupTables.
bteq
cleanupTables
.bteq
cleanupTable
s.bteq
sample/threads
setupTables.bte
q

eq
eq
teq
teq
teq
sample/threads/inc
common.h
common.h
sample/threads/inc
PerfTestMessag
e.h
sample/threads/inc
Directory
IBM AIX
sample/threads
TestStream.cpp
input.txt
cleanupTables
.bteq
input.txt
cleanupTable
s.bteq
common.h
input.txt
input.txt
cleanupTable
s.bteq
common.h
common.h
PerfTestMessa PerfTestMessa PerfTestMess

ge.h
ge.h
age.h
PerfTestMess
age.h
PerfTestMess
age.h
TestBase.h
TestBase.h
TestBase.h
TestBase.h
TestBase.h
TestBase.h
sample/threads/inc
TestExport.h
TestExport.h
TestExport.h
TestExport.h TestExport.h TestExport.h
sample/threads/inc
TestLoad.h
TestLoad.h
TestLoad.h
TestLoad.h
TestLoad.h
TestLoad.h
sample/threads/inc
TestSim.h
TestSim.h
TestSim.h
TestSim.h
TestSim.h
TestSim.h
sample/threads/inc
TestStream.h
TestStream.h
TestStream.h
TestStream.h
TestStream.h
TestStream.h
sample/threads/inc
TestUpdate.h
TestUpdate.h
TestUpdate.h
TestUpdate.h TestUpdate.h TestUpdate.h
sample/threads/inc
ThreadTest.h
ThreadTest.h
ThreadTest.h
ThreadTest.h ThreadTest.h ThreadTest.h
common.h
ThreadTestP
arameters.cp
p
209

Directory
IBM AIX
HP-UX
Itanium
HP-UX
Risc
Solaris
SPARC
Solaris
Opteron
Linux
sample/threads/inc
ThreadTestPar
ameters.h
ThreadTestPa
rameters.h
ThreadTestPa
rameters.h
ThreadTestP
arameters.h
ThreadTestP
arameters.h
ThreadTestPa
rameters.h
sample/threads/inc
Synchronizer.h
Synchronizer.
h
Synchronizer.
h
Synchronizer. Synchronizer. Synchronizer.

h
h
h

Export Operator (pexpd000)
Teradata Parallel Transporter Export Operator.
Table 75: Teradata Parallel Transporter Export Operator Files
Directory
IBM AIX
HP-UX
PA-RISC
HP-UX
Itanium
Solaris
Linux
<INSTALLDIR>/lib
libexportop.so
libexportop.sl
n/a
libexportop.so
libexportop.so
<INSTALLDIR>/lib64
libexportop.so
libexportop.sl
libexportop.so
libexportop.so
libexportop.so
<INSTALLDIR>/sample
expnfyxt.c
expnfyxt.c
expnfyxt.c
expnfyxt.c
expnfyxt.c

Infrastructure (tbldd000)
Teradata Parallel Transporter Infrastructure.
Table 76: Teradata Parallel Transporter Infrastructure Files
Directory
IBM AIX
HP-UX
Solaris
Solaris Opteron
Linux
<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
ptmcmd
ptmcmd
ptmcmd
ptmcmd
ptmcmd
<INSTALLDIR>/bin
ptmgts
ptmgts
ptmgts
ptmgts
ptmgts
210

Table 76: Teradata Parallel Transporter Infrastructure Files (continued)
Directory
IBM AIX
HP-UX
Solaris
Solaris Opteron
Linux
<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
twbcmd
twbcmd
twbcmd
twbcmd
twbcmd
<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>/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.so
libpxicu.sl
libpxicu.so
libpxicu.so
libpxicu.so
211

Directory
IBM AIX
HP-UX
Solaris
Solaris Opteron
Linux
<INSTALLDIR>/lib
libdataconop.so
libdataconop.sl
libdataconop.so
libdataconop.so
libdataconop.so
<INSTALLDIR>/lib
libddlop.so
libddlop.sl
libddlop.so
libddlop.so
libddlop.so
<INSTALLDIR>/lib
libodbcop.so
libodbcop.sl
libodbcop.so
libodbcop.so
libodbcop.so
<INSTALLDIR>/lib
liboscmdop.so
liboscmdop.sl
liboscmdop.so
liboscmdop.so
liboscmdop.so
<INSTALLDIR>/lib
libinsertop.so
libinsertop.sl
libinsertop.so
libinsertop.so
libinsertop.so
<INSTALLDIR>/lib
libselectop.so
libselectop.sl
libselectop.so
libselectop.so
libselectop.so
<INSTALLDIR>/lib
libopcommon.so
libopcommon.sl
libopcommon.so
libopcommon.so
libopcommon.s
o
<INSTALLDIR>/lib
libptmos.so
libptmos.sl
libptmos.so
libptmos.so
libptmos.so
<INSTALLDIR>/lib
libptmpo.so
libptmpo.sl
libptmpo.so
libptmpo.so
libptmpo.so
<INSTALLDIR>/lib
libptmpi.so
libptmpi.sl
libptmpi.so
libptmpi.so
libptmpi.so
<INSTALLDIR>/lib
libptmpi.a
libptmpi.a
libptmpi.a
libptmpi.a
libptmpi.a
<INSTALLDIR>/lib
n/a
libptmin.sl
libptmin.so
libptmin.so
libptmin.so
<INSTALLDIR>/lib
liblogview.so
liblogview.sl
liblogview.so
liblogview.so
liblogview.so
<INSTALLDIR>/lib
libpxcommon.so
libpxcommon.sl
libpxcommon.so
libpxcommon.so
libpxcommon.s
o
<INSTALLDIR>/lib
libflimop.so
libflimop.sl
libflimop.so
libflimop.so
libflimop.so
<INSTALLDIR>/lib
libfeomop.so
libfeomop.sl
libfeomop.so
libfeomop.so
libfeomop.so
<INSTALLDIR>/lib
libmlimop.so
libmlimop.sl
libmlimop.so
libmlimop.so
libmlimop.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
GT44.txt
GT44.txt
GT44.txt
GT44.txt
GT44.txt
GT62.txt
GT62.txt
GT62.txt
GT62.txt
GT62.txt
GT93.txt
GT93.txt
GT93.txt
GT93.txt
GT93.txt
GT94.txt
GT94.txt
GT94.txt
GT94.txt
GT94.txt
GT95.txt
GT95.txt
GT95.txt
GT95.txt
GT95.txt
GT96.txt
GT96.txt
GT96.txt
GT96.txt
GT96.txt
GT97.txt
GT97.txt
GT97.txt
GT97.txt
GT97.txt
jobvars.txt
jobvars.txt
jobvars.txt
jobvars.txt
jobvars.txt
212

Directory
IBM AIX
HP-UX
Solaris
Solaris Opteron
Linux
<INSTALLDIR>/sample/
metadata
sql1.txt
sql1.txt
sql1.txt
sql1.txt
sql1.txt
metadata
sql2.txt
sql2.txt
sql2.txt
sql2.txt
sql2.txt
metadata
twb_status.txt
twb_status.txt
twb_status.txt
twb_status.txt
twb_status.txt
metadata
twb_targets.txt
twb_targets.txt
twb_targets.txt
twb_targets.txt
twb_targets.txt
/usr/bin
twbpkgrm
twbpkgrm
twbpkgrm
twbpkgrm
twbpkgrm
/var
twbpkg
twbpkg
twbpkg
twbpkg
twbpkg

Load Operator (plodd000)
Teradata Parallel Transporter Load Operator.
Table 77: Teradata Parallel Transporter Load Operator Files
Directory
IBM AIX
HP-UX
PA-RISC
HP-UX
Itanium
Solaris
Linux
<INSTALLDIR>/lib
libloadop.so
libloadop.sl
n/a
libloadop.so
libloadop.so
<INSTALLDIR>/lib64
libloadop.so
libloadop.sl
libloadop.so
libloadop.so
libloadop.so
<INSTALLDIR>/sample
ldnfyext.c
ldnfyext.c
ldnfyext.c
ldnfyext.c
ldnfyext.c

Stream Operator (pstmd000)
Teradata Parallel Transporter Stream Operator.
Table 78: Teradata Parallel Transporter Stream Operator Files
Directory
IBM AIX
HP-UX
PA-RISC
HP-UX
Itanium
Solaris
Linux
<INSTALLDIR>/lib
libstreamop.so
libstreamop.sl
n/a
libstreamop.so
libstreamop.so
<INSTALLDIR>/lib64
libstreamop.so
libstreamop.sl
libstreamop.so
libstreamop.so
libstreamop.so
<INSTALLDIR>/sample
stmnfyxt.c
stmnfyxt.c
stmnfyxt.c
stmnfyxt.c
stmnfyxt.c
213


Update Operator (pupdd000)
Teradata Parallel Transporter Update Operator.
Table 79: Teradata Parallel Transporter Update Operator Files
Directory
IBM AIX
HP-UX
PA-RISC
HP-UX
Itanium
Solaris
Linux
<INSTALLDIR>/lib
libupdateop.so
libupdateop.sl
n/a
libupdateop.so
libupdateop.so
<INSTALLDIR>/lib64
libupdateop.so
libupdateop.sl
libupdateop.so
libupdateop.so
libupdateop.so
<INSTALLDIR>/sample
updnfyxt.c
updnfyxt.c
updnfyxt.c
updnfyxt.c
updnfyxt.c
Verifying Teradata WebSphere MQ Access Module (mqaxsmod)

been moved to the /opt/teradata/client/<version>/lib and the /opt/teradata/client/<version>/
opt directories.
Teradata WebSphere MQ Access Module, except for HP-UX Itanium, they are listed in
Table 81.
Table 80: Teradata WebSphere MQ Access Module Files
Directory
IBM AIX
HP-UX
Solaris
Linux
/usr/lib
libmqsc.so*
libmqsc.sl*
libmqsc.so*
libmqsc.so*
/usr/lib
libmqs.so*
libmqs.sl*
libmqs.so*
n/a
<version>/opt
mqaxsmod*
mqaxsmod*
mqaxsmod*
n/a
<version>/lib
libmqsc.so
libmqsc.sl
libmqsc.so
libmqsc.so
<version>/lib
libmqs.so
libmqs.sl
libmqs.so
n/a
<version>/opt
mqaxsmod
mqaxsmod
mqaxsmod
n/a
The Teradata WebSphere MQ Access Module for HP-UX Itanium cannot be installed from the
Main Installation. If installing on HP-UX Itanium, the files listed in Table 81 must be copied
from /HP-UX/mqaxsmod/ia64 on the Installation CD to the directories indicated.
Since the files for HP-UX Itanium are copied manually, ensure that the dependent products
for Teradata WebSphere MQ Access Module listed in Dependent Products, in Table 3 on
page 31 are installed first and in the correct order.
214

An asterisk (*) after a filename in Table 81 indicates that it is a softlink for files that are
located in the /opt/teradata/client/<version>/hpux64 directory.
Table 81: Teradata WebSphere MQ Access Module Files for HP-UX Itanium
Directory
HP-UX Itanium
/usr/lib/hpux64
libmqs.so*
/usr/lib/hpux64
libmqsc.so*
<version>/hpux64
libmqs.so
<version>/hpux64
libmqsc.so

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.
Start BTEQ by entering:

bteq
The following appears:

Teradata BTEQ 13.00.00.00 for UNIX5.
Copyright 1984-2007, Teradata Corporation. ALL RIGHTS RESERVED.
Enter your logon or BTEQ command:
Log on to the Teradata Database. See Log onto the Teradata Database on page 215.
Submit a sample query. See Submit a Sample Teradata SQL Query on page 216.
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 Making the Database Connection on page 219 for complete information about
logging onto Teradata.
215

Procedure - Logging onto the Teradata Database

Follow these steps to log onto the Teradata Database.
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
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/fml
Password: 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:
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
216

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.
Verifying the Installation Using the CLI Sample

Program
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.
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.
Execute the makefile to create the executable module clisamp:

# make -f makesamp.3000
Change the mode of the executable to run by entering the following command:
# chmod +x clisamp
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
217

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:
CLIv2 version is 13.00.00.00
MTDP version is 13.00.00.00
MOSIOS version is 13.00.00.00
MOSIDEP version is 13.00.00.00
OSERR version is 13.00.00.00
Logging on to --->dbc/systemfe,service
writing out to--> CLISAMP.DAT
submitting -->select* from dbc.sessioninfo;
writintg out to --> CLISAMP.DAT
Logging off.
218
CHAPTER 12
Connecting to a Teradata Database
This chapter 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 installed, some dialogs might vary from those shown in this
guide.
Topics include:
Making the Database Connection
Connecting in GUI Applications
Connecting in Command Line Driven Applications
Connecting to a Teradata Database Programmatically
Logon Error Messages

This section describes how to connect to a Teradata Database:
from a GUI
from a command line

and
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.
Overview of Logon Procedures

The logon string can be provided while logging onto 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. The dialog allows entry of the missing logon information.
If the Connect to Teradata Database dialog appears, all application-provided parameters are
automatically entered into the dialog fields. If the information is incorrect, change the values
entered. After entering required and optional logon information press Enter or click OK to
continue logging on.
The user logon exit routine can manipulate the fields of the Connect to Teradata Database
dialog.
219
Chapter 12: Connecting to a Teradata Database

Connecting in GUI Applications

This section describes how to connect to a Teradata Database using the Connect to Teradata
Database dialog from a Graphical User Interface (GUI) application. The procedure is for a
typical application. See product User or Reference guides for specific information about an
individual product.
Procedure - Connecting to a Teradata Database

Follow these steps to connect to a Teradata Database:
1
If the application connecting to the database has a Connectivity tab in the Tools options
menu, select ODBC.
Click the Connect button. The Connect to Teradata Database dialog appears.
Select or enter the appropriate values for the database to which you are connecting.
Click OK.
Connect to Teradata Database Dialog

Figure 1 contains the Connect to Teradata Database dialog:
Figure 1: Typical Connect to Teradata Database Dialog
220

The fields in the Connect to Teradata Database dialog are:

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 with which you want to connect.
Authentication
Mechanism
(Required) Select the authentication mechanism specified by the 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 system uses
the configured default.
TD1 - Teradata 1 mechanism (disabled in Teradata Tools and Utilities
12.00.00)
TD2 - Teradata 2 mechanism
ldap - ldap mechanism
KRB5 - Kerberos mechanism
KRB5C - Kerberos Compatibility mechanism (disabled in Teradata Tools
and Utilities 12.00.00)
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.
Parameter
(Optional) Enter the parameters required by the selected authentication

mechanism. See the System Administrator.
Username
(Required) Select a user name from the drop down list, or enter a valid user
name.
Password
(Required) Enter the Password for the user name entered.
Optional
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 creates 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 are running, or to restrict users
connecting to the database.
221

Note: Even though the UserId and Password parameters are required to log onto the Teradata
Database, they do not have to be entered in the Connect to Teradata Database dialog box, since
they are filled in by the user logon exit routine.
Connecting in Command Line Driven Applications

This section describes how to connect to a Teradata Database from the command line.
Procedure - Connecting to a Teradata Database from the Command Line

Follow these steps to connect to a Teradata Database from the command line:
1
Enter the .logmech command.
Enter the .logdata command.
Enter the .logon command.
.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 casesensitive.
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 use the configured default.
TD1 - Teradata 1 mechanism (disabled in Teradata Tools and Utilities 12.00.00)
TD2 - Teradata 2 mechanism
LDAP - ldap mechanism
KRB5 - Kerberos mechanism
KRB5C - Kerberos Compatibility mechanism (disabled in Teradata Tools and Utilities

12.00.00)
.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;
222

The exact contents of the logdata_string vary according to the selected authentication
mechanism. The string is not displayed, parsed, nor otherwise processed by the application.
.logon Command
The syntax for the .logon command is:
.logon <DBCName></><UserId><,><Password><,><AccountId>
Table 82 defines the .logon command parameters.

Table 82: .logon Command Parameter Definitions
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.
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.
Table 83 describes the supported mechanisms.
Table 83: Supported Mechanisms
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
223

Table 83: Supported Mechanisms (continued)
Mechanism
Mechanism Parameter
User ID
Password
KRB5
Optional
Never
Never
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)
LDAP
Must
Never
Never
The following authentication mechanisms are supported:

Kerberos
In all environments that support Kerberos, you can provide a UserId, Password, and a Domain
or a Realm. The Domain or Realm must be supplied separately as authentication mechanism
data.
Once the users 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 neither the Domain
nor Realm need to be provided:
.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 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
.logdata joe@domain1@@mypassword
.logon mydbs/,,2345889909
or
.logmech KRB5
.logdata joe@@mypassword
or
.logmech KRB5
224

In all of the above cases, 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
Note: KRB5C was disabled in Teradata Tools and Utilities 12.00.00. See the Security
Administration documentation for more information.
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 automatically determines the appropriate authentication mechanism
when interfacing to a Teradata Database using the same logic 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 an incompatible mechanism is selected, TERASSO_SECPKGMATCH_FAIL is

returned.
LDAP
The LDAP authentication mechanism allows authentication using LDAP and, optionally, a
user assumes a role or user identity other than his or her own, as allowed by the appropriate
directory settings.
A UserId and Password must be provided, a Domain or Realm can also be supplied. The exact
contents of the LDAP .logdata information depends largely upon how the site is using LDAP,
and how LDAP has been configured. The following samples are generic. Once a users identity
has been verified by LDAP, an implicit logon proceeds 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 is included as part of .logon command:

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

Once a users identity has been verified by LDAP, an implicit logon proceeds 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 returns error 3790.
If the directory does not map the UserId to a specific Teradata Username, a generic username
and role are assigned. The role is derived from information contained in the directory. Logon
is by extended logon.
.logdata information must always allow the LDAP authentication mechanism.
TD1 and TD2
Note: TD1 was disabled in Teradata Tools and Utilities 12.00.00. See the Security Administration
documentation for more information.
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 above for the V2R6 Teradata Database.
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
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.
.logmech TD2
.logon mydbs/rhh,password
TD1
Note: TD1 was disabled in Teradata Tools and Utilities 12.00.00. See the Security Administration
documentation for more information.
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.
226
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 is returned.
Single Sign-On Legacy Considerations
In order to provide backward compatibility with pre-Teradata Tools and Utilities 8.0
applications that use SSO, the following items apply.
Table 84 lists Single-Sign-On information for legacy applications.
Table 84: Single-Sign-On for Legacy Applications
Type
Description
Direct sign-on
If a Username and Password are not provided as part of the Teradata

logon string,
AND
no authentication mechanism name is specified in .logmech, the client
interface does not use the default mechanism.
Rather, it first determines if the Kerberos mechanism is available. If the
Kerberos authentication mechanism is available, the client interface
uses it.
If the Kerberos interface is not available,
the logon attempt fails.
If .logmech is specified, and the authentication mechanism turns out
to be different from the one automatically determined by the client
interface, an error is 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 does not use the default authentication mechanism.
Rather, the client interface first determines if the Kerberos
authentication mechanism is available. If the Kerberos authentication
mechanism is available, the client interface uses it.
If the Kerberos authentication mechanism is not available, the logon
attempt fails.
If .logmech is specified, and the authentication mechanism turns out to
be different from the one automatically determined by the client
interface, an error is returned.
Connecting to a Teradata Database Programmatically

Several Teradata Tools and Utilities products allow a programmatic connection to the
Teradata Database using SQL and APIs.
Table 85 lists the manuals to consult regarding connecting to the Programmatically to a
Teradata Database.
227

Table 85: Connecting Programmatically to a Teradata Database
Product
Document
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 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 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.
Logon Error Messages

Table 86 lists the error messages which apply to the logon and database connection function.
Table 86: Logon Error Messages
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.
228

Table 86: Logon Error Messages (continued)
Error Message
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.
Authentication Mechanism Connection Error

If there is an error in the authentication mechanism selected, the message, External
authentication is not currently allowed may appear.
If this message, you have selected an incorrect authentication mechanism. Reselect it using
the authentication mechanism provided by the database administrator and try to connect
again.
229

230
CHAPTER 13
Troubleshooting
This chapter contains troubleshooting tips for:
Client Computer Problems
Network Problems
Teradata Database Problems
Note: A problem can affect more than one area, or there can be more than one problem.
If a problem cannot be resolved, contact the Teradata Solutions Customer Services Remote
Services Center (TSCS-RSC). For contact information, refer to the Teradata Tools and Utilities
Release Definition, Release 13.00.00.

To determine whether or not there is a problem with your client, perform the following
checks. You may not need to try all of them.
Cannot Communicate Over the Network with Teradata Database

To confirm that a UNIX/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, Network Problems on page 234.
Note: dbcnameCOPn can appear in upper or lower case.
231
Chapter 13: Troubleshooting

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
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.
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.
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.
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. Refer to Chapter 2: Before You Install for more
detail.
232

Missing Hosts File

Check that the /etc/hosts file exists on the UNIX/Linux client.
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.
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.
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
tdses
1025/udp
1025/tcp
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.
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.
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.
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.
233

Network Problems
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.
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/Linux client, and Teradata
Database.
Check for broken or disconnected network cables.
Check that drop cables are not too long (they must follow the IEEE 802.3 standards).
Check all repeaters, bridges, routers, and gateways for proper functioning.
Check that all jumpers are set correctly on the UNIX/Linux client's network controller
board.
Check that the network software is installed and running properly on the UNIX/Linux
client.
Check that the network software is compatible with the network controller board installed
on the UNIX/Linux client.
Use a network utility program to confirm that the network is operational.
Use BTEQ or a network utility program from another UNIX/Linux client on the same
network segment as the first UNIX/Linux client. If this works, there may be a problem
with the first UNIX/Linux client.
10 Use BTEQ or a network utility program from another UNIX/Linux client on a different
network segment from the first UNIX/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/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/Linux client to reset network hardware and reload network software.

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

Note: Steps 2 through 7 apply to the Teradata Database only.
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 afield representative.
Have afield representative check that the adaptor cable is connected.
Have afield representative check the Multibus Adaptor Board (MAB).
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/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.
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.
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.
235


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.
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.
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.
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.
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 set the TWB_ROOT environment variable if Teradata Parallel
Transporter does not run.
236
Logout from the system and log back in. Run the Teradata Parallel Transporter job again.
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.
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.

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.
On HP-UX, the error message still appears, check the $TWB_ROOT/lib path is in
theSHLIB_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.
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.
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 found
Procedure - Finding Missing Messages

Follow these step to find missing messages.
237

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.
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.
Unable to Find Messages on AIX

When the LANG and LC__FASTMSG environment variables are set to C and true,
respectively, the following messages will appear after running a Teradata Parallel Transporter
job using the tbuild command:
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.
238
APPENDIX A
Session Limits
This appendix lists Teradata session limits for BTEQ and for the entire system.
BTEQ Session Limits

The maximum number of BTEQ sessions depends on the host used. BTEQ session limits for
the UNIX client are listed in Table 87.
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.
Table 87 lists the session guidelines for clients.

Table 87: Session Guidelines for 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
System-wide for Version 2 (V2) Common Node

systems
600 * Number of Nodes
239
Appendix A: Session Limits

System-Wide Session Limits
Caution:
240
These are guidelines only. The optimum number of sessions for any system depends on the
site's configuration and tuning.
Index
Symbols
.logdata 222
command 222
.logmech 222
command 222
.logon 222
command 223
/etc/services File 233
Numerics
64-bit
executable files 98, 112
library files 98, 112
A
adhoc 186, 187
adhoc.c 186
adhoc.cpp 187
AIX packages 68
aix.includes 187
alternate directories 97, 111
API 54
arcmain.exe 193
Authentication Mechanism
KRB5 221
KRB5C 221
ldap 221
other 221
TD1 221
TD2 221
B
product dependencies 31, 35
supported on 25
verifying 184
blexitr 201
blexitr.c 201
blkexit.c 201
blkexitr.c 201
BlockLoad.cpp 205
BlockLoad.h 205
Bourne shell 158
BTEQ 40, 42, 43
bteq 184
exiting 217
session limits 239
verifying 184
verifying installation with 215
btnfyext.c 184
btnfyext.h 184
C
C shell 158
CD-ROM
installing 67, 79, 95, 109, 121, 139
Changing the twbcfg.ini File 170
checkpoint.cpp 205
checkpoint.h 206
cleanupTables.bteq 205, 206, 207, 208, 209
CLI sample program
verifying installation with 217
CLI user exit functions
installing 77, 93, 136, 148
CliLgn.Ex.c 195
CliPPS.c 195
clisamp.c 195
clispb.dat 193, 194, 195, 233
cliv2 193
cliv2if.h 194, 195
cobpp 198
common.h 209
common.includes 186, 187
configuring
requirements
network 30
Teradata Parallel Transporter 163, 170
connection.h 204
contacting Teradata 231
coordinator 211
COPANOMLOG 232
COPERR 232
coperr.h 194, 195
coptypes.h 194
D
Database Name 221
DataConnector Operator 27
dbca2px.h 194, 195
dbcarea.h 194, 195
dbcerr.h 194, 195
241
Index
dbchqep.h 194
dconndlg.sl 186
DDL Operator 27
default
directories 97, 111
default directories 97, 111
dependencies 31
directories
alternate 97, 111
default 97, 111
disk space, available 52
DMLGroup.h 204
E
empty
Authentication Mechanism 221
environment variables, setting 158, 161, 162
errmsg.cat 193, 194, 195, 232
errmsg.txt 193, 194, 195
error.c 187
error.cpp 187
executable files, default directory 98, 112
executor 211
expnfyxt.c 201, 210
expnfyxt.h 201
Export Operator 28, 34, 45, 46, 47, 54
F
fastexp 200
FastExport OUTMOD Adapter Operator 28
fastld 201
fastload 201
FastLoad INMOD Adapter Operator 28
fexp 201
fileio.cpp 207
fileio.h 208
flnfyext.c 201, 202
G
GenericDriver.cpp 205, 206
GenericDriver.h 205, 206
GetBuffer.cpp 206
GetBuffer.h 206
GT11.txt 212
GT44.txt 212
GT62.txt 212
GT93.txt 212
GT94.txt 212
GT95.txt 212
GT96.txt 212
GT97.txt 212
242
H
hosts file 233
HP-UX packages 80
I
includes files, default directory 98, 112
individual products
installing 79, 121, 139
infile.bigEndian 205
infile.littleEndian 206, 207
infilemaster.littleEndian 208
infileslave.littleEndian.1 208
Infrastructure 28, 34, 45, 46, 47, 54, 210
input.exp 207
input.lod 207
input.stm 207
input.txt 205, 206, 207, 209
input.upd 207
installing
alternate directories 97, 111
default directories 97, 111
individual products 67
maintenance software 49
pre-installation considerations 25
Teradata client 72
upgrades 49
verifying using bteq 215
verifying using CLI sample program 217
J
jmsam.jar 193
jmsam_charsets.properties 193
jobvars.txt 212
K
KRB5
KRB5C
L
LABSBTEQ 196, 197, 199
LD_LIBRARY_PATH 159
ldap
ldnfyext.c 213
libcliv2.sl 194
libcliv2.sl* 193, 194
libcliv2.so 193, 194
libcliv2.so* 194
libdataconop.sl 212
Index
libdataconop.so 212
libddlop.sl 212
libddlop.so 212
libexportop.sl 210
libexportop.so 210
libfeomop.sl 212
libfeomop.so 212
libflimop.sl 212
libflimop.so 212
libicudatatd.sl 188, 192
libicudatatd.sl.36.0 188, 192
libicudatatd.so 187, 188, 192
libicudatatd.so.36 187, 188, 192
libicudatatd.so.36.0 188, 192
libicudatatd36.0.so 188, 192
libicui18ntd.sl 187, 188, 192
libicui18ntd.sl.36.0 188, 192
libicui18ntd.so 187, 188, 192
libicui18ntd.so.36 187, 188, 192
libicui18ntd.so.36.0 188, 192
libicui18ntd36.0.so 188, 192
libicuiotd.sl 187, 188, 192
libicuiotd.sl.36.0 188, 192
libicuiotd.so 187, 188, 192
libicuiotd.so.36 187, 188, 192
libicuiotd.so.36.0 188, 192
libicuiotd36.0.so 188, 192
libiculetd.sl.36.0 188, 192
libiculetd.so.36.0 188, 192
libiculxtd.so.36.0 188, 192
libicuuctd.sl 187, 188, 192
libicuuctd.sl.36.0 188, 192
libicuuctd.so 187, 188, 192
libicuuctd.so.36 187, 188, 192
libicuuctd.so.36.0 188, 192
libicuuctd36.0.so 188, 192
libinsertop.sl 212
libinsertop.so 212
libjmsam.sl 193
libjmsam.so 193
libloadop.sl 213
libloadop.so 213
liblogview.sl 212
liblogview.so 212
libmlimop.sl 212
libmlimop.so 212
libmqs.sl 214
libmqs.so 214
libmqsc.so 214
libodbc.sl 186
libodbc.so 186
libodbcinst.sl 185, 186
libodbcinst.so 185, 186
libodbcop.sl 212
libodbcop.so 212
libopcommon.sl 204, 212
libopcommon.so 204, 212
liboscmdop.sl 212
liboscmdop.so 212
libpm.sl 200
libpm.sl* 199
libpm.so 199, 200
libppb.a 198, 199
libppruntim.sl 196, 199
libppruntim.so 196, 197, 198, 199
libptmin.sl 212
libptmin.so 212
libptmos.sl 212
libptmos.so 212
libptmpi.a 212
libptmpi.sl 212
libptmpi.so 212
libptmpo.sl 212
libptmpo.so 212
libpxcommon.sl 212
libpxcommon.so 212
libpxicu.sl 204, 211
libpxicu.so 204, 211
library files, default directory 98, 112
libselectop.sl 212
libselectop.so 212
libstreamop.so 213
libtdparse.so 185, 186
libtdusr.sl 194
libtdusr.sl* 193, 194
libtdusr.so 193, 194
libtdusr.so* 194
libtelapi.s1 204
libtelapi.so 204
libupdateop.so 214
Load Operator 28, 34, 45, 46, 47, 54
loadData.littleEndian 209
logon
dialog box 219
procedures 219
M
main.cpp 205, 206, 207
maintenance software, installing 49
makeblock.aix 205
makeblock.hpux 205
makeblock.linux 205
makeblock.sol_o 205
makeblock.sol_s 205
makecheckpoint.aix 206
makecheckpoint.hpux 206
makecheckpoint.linux 206
243
Index
makecheckpoint.sol_o 206
makecheckpoint.sol_s 206
makedriver.aix 205, 206
makedriver.hpux 205, 206
makedriver.linux 205, 206, 207
makedriver.sol_o 205, 206
makedriver.sol_s 205, 206
Makefile 186, 187
makemulti.linux 208
makemultiple.aix 207
makemultiple.hpux 207
makemultiple.linux 207
makemultiple.sol_o 207
makemultiple.sol_s 207
makeparallel.linux 208
makerdusr.lx 195
makerdusr.lx64 195
makesamp.lx 195
makesamp.lx64 195
makinmod.3000 203
master.cpp 207
master_input.txt 208
mkbtnfyext.aix 184
mkbtnfyext.hpux 184
mkbtnfyext.hpux-ia64 184
mkbtnfyext.linux 184
mkexpext.aix 201
mkexpext.aix* 201
mkexpext.hpux 201
mkexpext.hpux* 201
mkexpext.linux 201
mkexpext.unx 201
mkexpext.unx* 201
mkmldext.aix 203
mkmldext.aix* 203
mkmldext.hpux 203
mkmldext.hpux* 203
mkmldext.linux 203
mkmldext.unx 203
mkmldext.unx* 203
mldnfyxt.c 203
mldnfyxt.h 203
mload 202, 203
mosiff.h 195
mosiif.h 194
mqaxsmod 214
MultiLoad
product dependencies 35
MultiLoad INMOD Adapter Operator 28
MultipleOperators.cpp 207
MultipleOperators.h 207
multitest.cpp 207
multitest.h 208
244
N
Named Pipes Access Module 42, 43, 44, 45, 46
supported on 25
verifying 185
navigating screens 98
np_axsmod.sl 185
np_axsmod.so 185
O
ODBC Driver for Teradata 40, 42, 44, 47
Solaris packages 123, 124, 128, 143
supported on 26
ODBC Operator 28
odbc.ini 185
odbc.ini file 160, 161, 162
odbc.m 186
odbc.so 186
odbccurs.sl 186
odbccurs.so 186
odbcinst.h 185
odbcinst.ini 185
odbctrac.sl 186
odbctrac.so 186
opermsgs.cat 204, 212
OptionsManager.cpp 204
OptionsManager.h 205
OptionsReader.cpp 206
OptionsReader.h 206
OS Command Operator 29
other
P
papi 54
parcel.h 194, 195
PerfTestMessage.cpp 208
PerfTestMessage.h 209
Perl 54
pexp 54
pexp8100 210
pexpd000 169, 176, 181
piom 199
pkgadd.log file 102, 115
pkginfo command 97, 111
pkgrm command 97, 111
planexecutor 211
plod 54
plod8200 213
plodd000 169, 176, 181
pmdcomt.h 199, 200
Index
pmddamt.h 200
pmtypes.h 200
ppbmain 198
PPCLB1 196, 198
PPCLB2 196, 198
PPCLB3 196, 198
PPCLB4 197, 198
PPCLB5 197, 198
PPCLB6 197, 198
PPCLB7 197, 198
PPCLB8 197, 198
PPCLB9 197, 198
ppcmain 196, 197
PPCOBLB1 199
PPCOBLB2 199
PPCOBLB3 199
PPCOBLB4 199
PPCOBLB5 199
PPCOBLB6 199
PPCOBLB7 199
PPCOBLB8 199
PPCOBLB9 199
product version numbers 3
pstm 54
pstm8200 213
pstmd000 169, 176, 181
ptmcmd 210
ptmexec 211
ptmgts 210
ptmjlgr 211
ptmlvs 211
ptmtims 211
pupd 54
pupd8200 214
pupdd000 169, 176, 181
pxdef.h 211
pxdtypes.h 211
pxlogdef.h 211
pxmacros.h 211
pxoper.h 211
pxos.h 211
pxstc.h 211
pxtypes.h 211
pxutypes.h 211
pxversion.h 211
R
README 185
readme 193
requirements
software 31
rmdir command 102, 115
S
sample
files 98, 112
samples.jar 200
schema.h 204
screen
navigation 98
session limits
bteq 239
system-wide 239
setting the semaphore parameters 165, 172
setupTables.bteq 205, 206, 207, 208, 209
Teradata 26, 31, 32, 33, 34, 35, 36, 123, 124, 125, 128, 130,
131, 143, 145, 146
Shared ICU Libraries for Teradata 40, 41, 42, 43, 44, 45, 46,
47, 48
verifying 187
SHMMAX 170
slave.cpp 208
slave_input.txt 208
software
uninstalling previous versions 81, 97, 111
software releases
supported 3
Solaris SPARC Packages 96, 110
SQL Inserter Operator 29
SQL Selector Operator 29
sql.h 186
sql1.txt 213
sql2.txt 213
sqlext.h 186
sqlpp 196
sqltypes.h 186
sqlucode.h 186
sqlunx.h 186
stmnfyxt.c 213
Stream Operator 29, 35, 45, 46, 47, 54, 213
synchronize.cpp 207
synchronize.h 208
Synchronizer.cpp 209
Synchronizer.h 210
T
tbld 54
tbuild 210
tbuild8200 210
tbuildexe 211
TCP/IP 30
TD1
TD2
245
Index
tdata.man 186
tdata.sl 185, 186
tdata.so 185, 186
tdatpump.cfg 203
tdconndlg.so 186
tdgssconfig.jar 200
tdmst 233
tdodbc 185
tdodbc.cat 187
tdses 233
tdsql.h 186
tdxwinapp 185
technical assistance 65
TelapiThreadTest.cpp 208
Teradata 41
Teradata Access Module for JMS 26, 32, 42, 43
configuring 163
Teradata Archive/Recovery Utility 31, 47
supported on 26
Teradata C Preprocessor 41, 42, 47
supported on 26
Teradata Call-Level Interface version 2 (CLIv2) 36, 40, 41, 42,
43, 44, 45, 46, 47, 48
installation order 36
supported on 26
verifying 193
Teradata client
installion 72
Teradata COBOL Preprocessor2 41, 42
supported on 26
verifying 198
Teradata Data Connector 40, 42, 43, 44, 48
supported on 26
Teradata Dynamic Workload Manager 40
Teradata FastExport 42, 43, 44
supported on 27
verifying 200
Teradata FastLoad 42, 43, 44
supported on 27
verifying 201
Teradata Generic Security Services 36, 40, 41, 42, 43, 44, 45,
46, 48
supported on 27
verifying 202
Teradata Generic Security Services Java
246
supported on 27
Teradata Index Wizard 40
Teradata JDBC Driver 33
platforms supported 228
supported on 26
Teradata Manager 40
Teradata MultiLoad 42, 43, 44
product dependencies 31, 34, 35
supported on 27
verifying 202
Teradata ODBC Driver
default directory 98, 112
odbc.ini file 160, 161, 162
Teradata OLE DB Access Module 42
configuring after installing 163, 170
parameters 164, 171
troubleshooting 236
uninstalling 169, 174
Teradata Parallel Transporter API 27, 34, 45, 46, 47
Teradata Performance Monitor 40
Teradata Query Director 29, 48
Teradata Query Scheduler Administrator 41
Teradata Query Scheduler Client 41
Teradata Query Scheduler Server 41
Teradata Statistics Wizard 41
Teradata System Emulation Tool 41
Teradata Tools and Utilities 25
Teradata TPump 42, 43, 44
supported on 29
verifying 203
Teradata Visual Explain 41
Teradata WebSphere MQ Access Module 42, 43, 44, 45, 46, 47
supported on 29
verifying 214
Teradata Workload Analyzer 41
teragss_aix-power 202
teragss_aix-power-32 202
teragss_hpux-ia64 202
teragss_hpux-pa 202
teragss_hpux-pa32 202
teragss_redhatlinux-i386 202
teragss_redhatlinux-i64 202
teragss_redhatlinux-ia64 202
teragss_solaris-sparc 202
teragss_solaris-sparc32 202
teragss_suselinux-i386 202
teragss_suselinux-i64 202
teragss_suselinux-ia64 202
TeraJDBC
Bourne shell 159
Index
C shell 159
terajdbc4.jar 193, 200
TestBase.cpp 208
TestBase.h 209
TestExport.cpp 208
TestExport.h 209
TestLoad.cpp 208
TestLoad.h 209
TestSim.cpp 208
TestSim.h 209
TestStream.cpp 209
TestStream.h 209
TestUpdate.cpp 209
TestUpdate.h 209
ThreadTest.cpp 209
ThreadTest.h 209
ThreadTestParameters.cpp 209
ThreadTestParameters.h 210
tldnfyxt.c 203
tlogview 210
tlogviewexe 211
tptlaunch 211
tpump 203
tpumpar.csql 204
tpumpexe 203
tpumpimd.c 204
troubleshooting
network problems 234
Teradata RDBMS problems 234
UNIX client problems 231
TSCS-RSC 52
twb_status.txt 213
twb_targets.txt 213
twbcfg.ini 210
twbcmd 211
twbcmdexe 211
twbkill 210
twbkillexe 211
twbmsgs.cat 212
twboper.ini 210
twbpath 211
twbpathexe 211
twbpkg 213
twbpkgrm 54, 55, 58, 211, 213
twbrmcp 211
twbrmcpexe 211
twbstat 210
twbstatexe 211
Update Operator 29, 35, 45, 46, 47, 54, 214

updating
hosts file 106, 120
updnfyxt.c 214
Upgrade or Maintenance Software
installation 49
upgrades, installing 49
V
Verifying 187
verifying installation 183
using bteq 215
with CLI sample program 217
version 210
version numbers 3
vscnctdlg.sl 186
vscnctdlg.so 186
X
xlC.aix.50.rte
dependency for ODBC 32
xlC.rte
dependency for ODBC 32
xsp.cpp 207
U
umount command 102, 115
uninstalling
software 97, 111
247
Index
248

2459

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2459

Uploaded by

Copyright:

Available Formats

Teradata Tools and Utilities

Installation Guide for UNIX and Linux

System and application programmers

Database administrators and database developers

System operators and other database specialists

Teradata Database 13.00.00

Teradata Tools and Utilities 13.00.00

To locate detailed supported-release information:

Click General Search under Online Publications.

Type 3119 in the Publication Product ID box.

Under Sort By, select Date.

Database management systems

Utilities that load and retrieve data

Changes to This Book

Updated installation procedures to reflect changes made to products since

Date and Release

Updated installation procedures to reflect Teradata products added to

Use the Release Definition for the following

Overview of all of the products in the

3 Type 2029 in the Publication Product ID box.

2 Click General Search under Online Publications.

the search results.

Use the Teradata Information Products web

Publications, Browse by Category.

For a list of Teradata Tools and Utilities

Access a link to a downloadable CD-ROM

Publications, Browse by Category.

Use the Teradata Information Products web

The Teradata home page provides links to

Executive reports, case studies of

Upgrading C/COBOL Preprocessor2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Adding CLI User Exit Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Installing Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Uninstalling Previous Versions of Red Hat Linux Software . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Installation/Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Verifying Teradata Parallel Transporter

Verifying the Installation Using BTEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying the Installation Using the CLI Sample Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Improper Linking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233

Figure 1: Typical Connect to Teradata Database Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Table 1: Teradata Tools and Utilities supported on UNIX and Linux. . . . . . . . . . . . . . . . . . . 25

Table 33: Selecting the Packages to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Table 67: Teradata Data Connector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Teradata Tools and Utilities Compatibility

Installation Kit Contents

Teradata Tools and Utilities Compatibility

Basic Teradata Query (BTEQ)

A general-purpose, command-based program

Named Pipes Access Module

Provides an interprocess communication link

ODBC Driver for Teradata

Enables UNIX, Linux and Microsoft

Shared Common Components for

A library of routines based on the IBM

Teradata Access Module for JMS

A utility in the Teradata Tools and Utilities

Teradata Archive/Recovery Utility (ARC)

Writes and reads sequential files on a Teradata

Provides the application programmer with a

Teradata Call-Level Interface version 2 (CLIv2)

A library of routines that enable an application

Teradata COBOL Preprocessor2

Provides the application programmer with a