Download - Teradata Tools and Utilities - dbmanagement.infodbmanagement.info/Books/MIX/2407_TeraData.pdf · Teradata Tools and Utilities Installation Guide for Microsoft Windows 7 ... Software

Teradata Tools and UtilitiesInstallation Guide for Microsoft Windows

Release 12.00.00B035-2407-067ASeptember 2007

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

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

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

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

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

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

GoldenGate is a trademark of GoldenGate Software, Inc.

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

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

IBM, CICS, DB2, MVS, RACF, Tivoli, and VM 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 trademarks or registered trademarks of QLogic Corporation.

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

SPARC is a registered trademarks of SPARC International, Inc.

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

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

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

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

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

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

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

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

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

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

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

mailto:[email protected]

Preface

Purpose

This book provides information about installing the Teradata Tools and Utilities Release 12.00.00 software on a computer that runs on a Windows operating system. Teradata Tools and Utilities is a group of products designed to work with Teradata Database.

Audience

This book is intended for use by:

• System and application programmers

• System administrators

• Database administrators and relational database developers

• System operators and other database specialists

Supported Releases

This book supports the following releases:

• Teradata Database 12.00.00

• Teradata Tools and Utilities 12.00.00

To locate detailed supported-release information:

1 Go to www.info.teradata.com.

2 Navigate to General Search>Publication Product ID.

3 Enter 3119.

4 Open the version of the Teradata Tools and Utilities 12.00.00 Supported Versions spreadsheet associated with this release.

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

Prerequisites

The following prerequisite knowledge is required for this product:

Teradata Tools and Utilities Installation Guide for Microsoft Windows 3

www.info.teradata.com

PrefaceChanges to This Book

• Computer technology and terminology

• Relational database management systems

• Utilities that load and retrieve data

Changes to This Book

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

Additional Information

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

Date and Release Description

September 200712.00.00

Removed information on Teradata “Dynamic” Query Director.

August 200712.00.00

Removed ESDM information.

July 2007

12.00.00

Updated installation procedures to reflect Teradata products added to Teradata Tools and Utilities Release 12.00.00.

Type of Information Description Access to Information

Release overview

Late information

Use the Release Definition for the following information:

• Overview of all of the products in the release

• Information received too late to be included in the manuals

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

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

• Information about available training and the support center


2 Select the General Search check box.

3 In the Publication Product ID box, type 2029.

4 Click Search.

5 Select the appropriate Release Definition from the search results.

4 Teradata Tools and Utilities Installation Guide for Microsoft Windows


PrefaceAdditional Information

Additional product information

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


2 Select the Teradata Data Warehousing check box.

3 Do one of the following:

• For a list of Teradata Tools and Utilities documents, click Teradata Tools and Utilities and then select a release or a specific title.

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

Specific books related to Teradata Tools and Utilities are as follows:

• MessagesB035-1096-mmyA

• Teradata Tools and Utilities Command SummaryB035-2401-mmyA

• Teradata Manager Installation GuideB035-2402-mmyA

• Teradata Driver for the JDBC Interface User GuideB035-2403-mmyA

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

• Teradata MultiLoad ReferenceB035-2409-mmyA

• Teradata FastExport ReferenceB035-2410-mmyA

• Teradata FastLoad ReferenceB035-2411-mmyA

• Teradata Archive/Recovery Utility ReferenceB035-2412-mmyA

• Basic Teradata Query ReferenceB035-2414-mmyA

• Teradata Director Program ReferenceB035-2416-mmyA

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

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

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





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

• Teradata Tools and Utilities Installation Guide for IBM VMB035-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 GuideB035-2428-mmyA

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

• Teradata Parallel Transporter ReferenceB035-2436-mmyA

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

• Teradata Parallel Transporter User GuideB035-2445-mmyA

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

• IBM IMS/DC Interface for Teradata ReferenceB035-2447-mmyA

• IBM CICS Interface for Teradata ReferenceB035-2448-mmyA

• Interactive Teradata Query ReferenceB035-2451-mmyA

• Interactive Teradata Query User GuideB035-2452-mmyA

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

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




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

• Teradata System Emulation Tool User GuideB035-2492-mmyA

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

• Teradata Administrator User GuideB035-2502-mmyA

• Teradata Statistics Wizard User GuideB035-2503-mmyA

• Teradata Visual Explain User GuideB035-2504-mmyA

• Teradata SQL Assistant/Web Edition User GuideB035-2505-mmyA

• Teradata Index Wizard User GuideB035-2506-mmyA

• ODBC Driver for Teradata User GuideB035-2509-mmyA

• Teradata Query Director User GuideB035-2510-mmyA

• Teradata Query Scheduler Administrator GuideB035-2511-mmyA

• Teradata Query Scheduler User GuideB035-2512-mmyA

• Teradata Dynamic Workload Manager User GuideB035-2513-mmyA

• Teradata Workload Analyzer User GuideB035-2514-mmyA

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

• Teradata Parallel Data Pump ReferenceB035-3021-mmyA

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

• Teradata Meta Data Services Programmer GuideB035-3047-mmyA

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


2 Select the General Search check box.

3 In the Title or Keyword box, type CD-ROM.

4 Click Search.





Ordering information for manuals

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


2 Select the How to Order check box 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:

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

• Technical information, solutions, and expert advice

• Press releases, mentions, and media resources

1 Go to Teradata.com.

2 Select a link.




http://www.teradata.com

Table of Contents

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

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

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

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

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

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

Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

System Configuration Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Installation Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Teradata Software Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

IBM VM and IBM z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Teradata Driver for the JDBC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Teradata Parallel Transporter Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Teradata Tools and Utilities CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 2: Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Installation Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Installing on Windows Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Installing on EM64T Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Minimum and Recommended Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Shared ICU Libraries for Teradata Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Installation of Dependent Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Teradata Generic Security Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

PUT Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45


Table of Contents

Typical, Custom, and Network Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Command Line Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Teradata Download Center Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Teradata Parallel Transporter Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Uninstalling Previous Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Default Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Default Product Response Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Restarting After Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Installing Required Software for Teradata SQL Assistant/Web Edition . . . . . . . . . . . . . . . . . .52

Installing Microsoft Internet Information Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Installing ASP.NET for Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Installing Microsoft .NET Framework (version 1.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Installing Microsoft Visual J#.Net Redistributable Package (version 1.1) . . . . . . . . . . . . .54

Installing the Cumulative Security Patch for IIS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Changing Microsoft Internet Explorer Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . .55

Changing Cookies Settings on Microsoft Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . .56

Setting the Number of Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Setting the Number of Clients on Windows Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Updating the Teradata Parallel Transporter API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Chapter 3: Installing the Teradata Tools and Utilities Software. . . . . . . . . . .61

Types of Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Installing Using PUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Installing Using the Client Main Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Initial Procedure for Typical, Custom or Network Installations. . . . . . . . . . . . . . . . . . . . .63

Typical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Network Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Installing a Package from the Command Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Sample Package Folder Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Installation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Configuring the Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Installing the Teradata Driver for the JDBC Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Installing the OLE DB Provider for Teradata from the Download Center . . . . . . . . . . . . . . . .85


Table of Contents

Chapter 4: Configuring the Teradata Tools and Utilities Software . . . . . . . 87

Configuring Teradata Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring the ODBC Driver, Teradata Query Scheduler, and Teradata Manager . . . . . . 88

Configuring Teradata Call-Level Interface version 2 (CLIv2) for Windows . . . . . . . . . . . . . 89

Setting Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Setting Environment Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Setting System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Adding CLI User Exit Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Configuring Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Changing the twbcfg.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Switching Teradata Parallel Transporter Software Versions . . . . . . . . . . . . . . . . . . . . . . . 95

User Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

System Environment Variable ORACLE_HOME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Uninstalling Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Order to Remove Teradata Parallel Transporter Software. . . . . . . . . . . . . . . . . . . . . . . . . 98

Configuring Teradata Access Module for JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 5: Verifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Verifying the Installation of Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Verifying Basic Teradata Query (BTEQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Verifying Named Pipes Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Verifying ODBC Driver for Teradata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Verifying Shared ICU Libraries for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Verifying Teradata Access Module for JMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Verifying Teradata Access Module for Tivoli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Verifying Teradata Archive/Recovery Utility (ARC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Verifying Teradata C Preprocessor2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Verifying Teradata Call-Level Interface version 2 (CLIv2) . . . . . . . . . . . . . . . . . . . . . . . 107

Verifying Teradata Data Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Verifying Teradata Driver for the JDBC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Verifying Teradata Dynamic Workload Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Verifying Teradata FastExport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Verifying Teradata FastLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Verifying Teradata MultiLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Verifying Teradata MultiTool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Verifying Teradata OLE DB Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Verifying Teradata Parallel Transporter API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113


Table of Contents

Verifying Teradata Parallel Transporter Data Connector Operator . . . . . . . . . . . . . . . . .121

Verifying Teradata Parallel Transporter DDL Operator . . . . . . . . . . . . . . . . . . . . . . . . . .121

Verifying Teradata Parallel Transporter Export Operator . . . . . . . . . . . . . . . . . . . . . . . . .122

Verifying Teradata Parallel Transporter ICU Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

Verifying Teradata Parallel Transporter Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Verifying Teradata Parallel Transporter Load Operator . . . . . . . . . . . . . . . . . . . . . . . . . .125

Verifying Teradata Parallel Transporter ODBC Operator . . . . . . . . . . . . . . . . . . . . . . . . .126

Verifying Teradata Parallel Transporter Operator Support Library . . . . . . . . . . . . . . . . .126

Verifying Teradata Parallel Transporter OS Command Operator . . . . . . . . . . . . . . . . . .127

Verifying Teradata Parallel Transporter SQL Inserter Operator . . . . . . . . . . . . . . . . . . . .127

Verifying Teradata Parallel Transporter SQL Selector Operator. . . . . . . . . . . . . . . . . . . .127

Verifying Teradata Parallel Transporter Stream Operator. . . . . . . . . . . . . . . . . . . . . . . . .128

Verifying Teradata Parallel Transporter Update Operator . . . . . . . . . . . . . . . . . . . . . . . .128

Verifying Teradata Parallel Transporter Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Verifying Teradata Query Scheduler Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Verifying Teradata Query Scheduler Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Verifying Teradata Query Scheduler Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Verifying Teradata TPump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Verifying WebSphere MQ Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Verifying Teradata Workload Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Verifying the Installation Using the CLI Sample Program, clisamp . . . . . . . . . . . . . . . . . . . .132

Chapter 6: Connecting to a Teradata Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Making the Database Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Overview of Logon Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Connecting in GUI Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Connecting in Command Line Driven Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

Example Logons from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Connecting to a Teradata Database Programmatically . . . . . . . . . . . . . . . . . . . . . . . . . . .145

Logon Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

Chapter 7: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Client Computer Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Cannot Communicate Over the Network with Teradata Database . . . . . . . . . . . . . . . . .147

Incorrect Path Name in COPLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148


Table of Contents

File localisation.dll Could Not Be Opened . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

File icuuctd28.dll Could Not Be Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Incorrect Path Name in COPANOMLOG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Incorrect CLIv2 Libraries Referenced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

CLIv2 DLLs Load Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Incorrect Entries in the hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Missing Entries in the services File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Incorrect clispb.dat Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Cannot Log On from CLI Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Cannot Log On to the Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

MSVCR71.DLL not found Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Software Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Error Running ttu.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Install Button Does Not Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

InstallShield 1603 Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

InstallShield 1607 Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

InstallShield 432 Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Teradata Database Hardware Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Silent Installation Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Location of the Setup Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

InstallShield Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159


Table of Contents


List of Figures

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


List of Figures


List of Tables

Table 1: Platforms Supported by Each Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Table 2: Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 3: Teradata Utility Pak CD#1 (Windows Products) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Table 4: Teradata Utility Pak CD#2 (HP-UX, Linux and MP-RAS Products) . . . . . . . . . . . . 33

Table 5: Teradata Utility Pak CD#3 (AIX and Solaris Products) . . . . . . . . . . . . . . . . . . . . . . . 33

Table 6: Data Management CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 7: Preprocessors CD#1 (Windows Products). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 8: Preprocessors CD#2 (HP, Linux, and MP-RAS Products). . . . . . . . . . . . . . . . . . . . . 34

Table 9: Preprocessors CD#3 (AIX and Solaris Products) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table 10: Load/Unload CD#1 (Windows Products) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table 11: Load/Unload CD#2 (HP-UX, Linux and MP-RAS Products) . . . . . . . . . . . . . . . . . 36

Table 12: Load/Unload CD#3 (AIX and Solaris Products) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Table 13: Parallel Transporter CD#1 (Windows Products) . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Table 14: Parallel Transporter CD#2 (HP-UX, Linux, and MP-RAS Products). . . . . . . . . . . 37

Table 15: Parallel Transporter CD#3 (AIX and Solaris Products) . . . . . . . . . . . . . . . . . . . . . . 38

Table 16: Tape Storage Management Enablers CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Table 17: Query Director CD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Table 18: MetaData Services CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Table 19: Minimum Configurations for Teradata Tools and Utilities. . . . . . . . . . . . . . . . . . . 43

Table 20: Recommended Configurations for Teradata Tools and Utilities. . . . . . . . . . . . . . . 44

Table 21: Default CD Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Table 22: Default Folders and Product Response Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Table 23: setup.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Table 24: setup.exe command parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Table 25: Command Prompt Installation Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Table 26: Configuring ODBC, Teradata Query Scheduler and Teradata Manager . . . . . . . . 88

Table 27: Adding an Entry to the hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Table 28: hosts File Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Table 29: Environment Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Table 30: Setting Environment Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Table 31: Logon Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Table 32: Setting <machine name>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92


List of Tables

Table 33: Port Number Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Table 34: Setting TDMSTPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Table 35: Basic Teradata Query (BTEQ) Files 32-bit Platforms . . . . . . . . . . . . . . . . . . . . . . . .103

Table 36: Named Pipes Access Module 32-bit Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

Table 37: ODBC Driver for Teradata 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

Table 38: ODBC Driver for Teradata 64-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Table 39: Share ICU Libraries for Teradata 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Table 40: Shared ICU Libraries for Teradata 64-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Table 41: Teradata Access Module for JMS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Table 42: Teradata Access Module for Tivoli Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Table 43: Teradata Archive/Recovery Utility (ARC) 32-bit Files . . . . . . . . . . . . . . . . . . . . . . .107

Table 44: Teradata C Preprocessor2 32-bit and 64-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Table 45: Teradata Call-Level Interface version 2 (CLIv2), 32-bit Files . . . . . . . . . . . . . . . . .107

Table 46: Teradata Call-Level Interface version 2 (CLIv2), 64-bit Files . . . . . . . . . . . . . . . . .108

Table 47: Teradata Data Connector 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Table 48: Teradata Data Connector 64-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Table 49: Teradata Driver for the JDBC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Table 50: Teradata Dynamic Workload Manager Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Table 51: Teradata FastExport 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Table 52: Teradata FastLoad 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Table 53: Teradata MultiLoad 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Table 54: Teradata MultiTool 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Table 55: Teradata OLE DB Access Module 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Table 56: 32-bit Teradata Parallel Transporter API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Table 57: 64-bit Teradata Parallel Transporter API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Table 58: Teradata Parallel Transporter Data Connector Operator. . . . . . . . . . . . . . . . . . . . .121

Table 59: Teradata Parallel Transporter DDL Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

Table 60: 32-bit Teradata Parallel Transporter Export Operator . . . . . . . . . . . . . . . . . . . . . . .122

Table 61: 64-bit Teradata Parallel Transporter Export Operator . . . . . . . . . . . . . . . . . . . . . . .122

Table 62: 32-bit Teradata Parallel Transporter ICU Library Files . . . . . . . . . . . . . . . . . . . . . .122

Table 63: 64-bit Teradata Parallel Transporter ICU Library Files . . . . . . . . . . . . . . . . . . . . . .122

Table 64: Teradata Parallel Transporter Infrastructure Files . . . . . . . . . . . . . . . . . . . . . . . . . .123

Table 65: 32-bit Teradata Parallel Transporter Load Operator . . . . . . . . . . . . . . . . . . . . . . . .125

Table 66: 64-bit Teradata Parallel Transporter Load Operator . . . . . . . . . . . . . . . . . . . . . . . .126

Table 67: Teradata Parallel Transporter ODBC Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Table 68: 32-bit Teradata Parallel Transporter Operator Support Library . . . . . . . . . . . . . . .126


List of Tables

Table 69: 64-bit Teradata Parallel Transporter Operator Support Library . . . . . . . . . . . . . . 126

Table 70: Teradata Parallel Transporter OS Command Operator . . . . . . . . . . . . . . . . . . . . . 127

Table 71: Teradata Parallel Transporter SQL Inserter Operator . . . . . . . . . . . . . . . . . . . . . . 127

Table 72: Teradata Parallel Transporter SQL Selector Operator . . . . . . . . . . . . . . . . . . . . . . 127

Table 73: 32-bit Teradata Parallel Transporter Stream Operator. . . . . . . . . . . . . . . . . . . . . . 128

Table 74: 64-bit Teradata Parallel Transporter Stream Operator. . . . . . . . . . . . . . . . . . . . . . 128

Table 75: 32-bit Teradata Parallel Transporter Update Operator . . . . . . . . . . . . . . . . . . . . . 128

Table 76: 64-bit Teradata Parallel Transporter Update Operator . . . . . . . . . . . . . . . . . . . . . 128

Table 77: Teradata Parallel Transporter Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Table 78: Teradata Query Scheduler Administrator 32-bit Files . . . . . . . . . . . . . . . . . . . . . . 130

Table 79: Teradata Query Scheduler Client 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Table 80: Teradata Query Scheduler Server 32-bit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Table 81: Teradata TPump 32-bit Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Table 82: WebSphere MQ Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Table 83: Teradata Workload Analyzer Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Table 84: InstallShield Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156


List of Tables


CHAPTER 1

Introduction

This chapter provides background information you will need before installing the Teradata Tools and Utilities software.

The section topics are:

• System Configuration Information

• Software Requirements

• Installation Kit


Chapter 1: IntroductionSystem Configuration Information

System Configuration Information

The Teradata Tools and Utilities software, together with the Teradata Database software, permits communication between a Teradata client and a Teradata Database.

Table 1: Platforms Supported by Each Product

Windows 2000 XP Server 2003 Vista

Product Micr

osof

t Win

dows

2000

Pro

fess

iona

l Ser

ver

and

Adva

nced

Ser

ver,

with

sp4,

runn

ing

on In

tel x

86

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, w

ith sp

2, ru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

XP

Prof

essio

nal, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, x

64, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, x

64, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(6

4-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

an

d St

anda

rd E

ditio

ns, w

ith sp

2, ru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

and

Stan

dard

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on 32

-bit

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

x64 a

nd S

tand

ard

x64

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

x64 a

nd S

tand

ard

x64

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on

(64-

bit T

erad

ata T

ools

and

Utilit

ies)

]Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

nru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

n ru

nnin

g on

EM6

4T/O

pter

on x3

2-bi

t (3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

nru

nnin

g on

EM6

4T/O

pter

on x6

4-bi

t (3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

n ru

nnin

g on

EM6

4T/O

pter

on x6

4-bi

t (6

4-bi

t Ter

adat

a Too

ls an

d Ut

ilities

Basic Teradata Query (BTEQ) YES YES YES YES NO YES YES YES NO YES YES YES NO

BTEQWin YES YES NO YES NO NO YES YES NO NO NO NO NO

Named Pipes Access Module a YES YES YES YES NO YES YES YES NO YES YES YES NO

ODBC Driver for Teradata YES YES YES YES YES YES YES YES YES YES YES YES YES

OLEDB Provider for Teradata YES YES YES YES NO YES YES YES NO YES YES YES NO

Shared ICU Libraries for Teradata

YES YES YES YES YES YES YES YES YES YES YES YES YES

Teradata Access Module for JMS YES YES YES YES YES YES YES YES NO YES YES YES YES

Teradata Access Module for Tivoli

YES NO NO NO NO NO NO NO NO NO NO NO NO

Teradata Administrator YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata Archive/Recovery Utility (ARC) b

*YES *YES

*YES YES NO *YES

*YES

YES NO NO NO NO NO

Teradata C Preprocessor2 YES YES YES YES YES YES YES YES YES YES YES YES YES

Teradata Call-Level Interface version 2 (CLIv2)


Teradata Data Connector YES YES YES YES NO YES YES YES NO YES YES YES NO



Teradata Driver for the JDBC Interface

YES YES NO YES YES YES YES YES YES YES NO YES YES

Teradata Dynamic Workload Manager(Teradata DWM)

YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata FastExport YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata FastLoad YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata Generic Security Services (TeraGSS) Client (Java support)


Teradata Generic Security Services (TeraGSS) Client (C support)


Teradata Index Wizard YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata Manager YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata MultiLoad YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata MultiTool c YES NO NO NO NO YES YES NO NO YES YES YES NO

Teradata OLE DB Access Module YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata Parallel Transporter API


Teradata Parallel Transporter Data Connector Operator


Teradata Parallel Transporter DDL Operator


Table 1: Platforms Supported by Each Product (continued)


Product Micr

osof

t Win

dows

2000

Pro

fess

iona

l Ser

ver

and

Adva

nced

Ser

ver,

with

sp4,

runn

ing

on In

tel x

86

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, w

ith sp

2, ru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

XP

Prof

essio

nal, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, x

64, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, x

64, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(6

4-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

an

d St

anda

rd E

ditio

ns, w

ith sp

2, ru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

and

Stan

dard

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on 32

-bit

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

x64 a

nd S

tand

ard

x64

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

x64 a

nd S

tand

ard

x64

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on

(64-

bit T

erad

ata T

ools

and

Utilit

ies)

]Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

nru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

n ru

nnin

g on

EM6

4T/O

pter

on x3

2-bi

t (3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

nru

nnin

g on

EM6

4T/O

pter

on x6

4-bi

t (3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

n ru

nnin

g on

EM6

4T/O

pter

on x6

4-bi

t (6

4-bi

t Ter

adat

a Too

ls an

d Ut

ilities



Teradata Parallel Transporter Export Operator


Teradata Parallel Transporter FastExport OUTMOD Adapter Operator d


Teradata Parallel Transporter FastLoad INMOD Adapter Operator e


Teradata Parallel Transporter ICU Library


Teradata Parallel Transporter Infrastructure


Teradata Parallel Transporter Load Operator


Teradata Parallel Transporter MultiLoad INMOD Adapter Operatorf


Teradata Parallel Transporter ODBC Operator


Teradata Parallel Transporter Operator Support Library


Teradata Parallel Transporter OS Command Operator


Teradata Parallel Transporter SQL Inserter Operator


Teradata Parallel Transporter SQL Selector Operator




Product Micr

osof

t Win

dows

2000

Pro

fess

iona

l Ser

ver

and

Adva

nced

Ser

ver,

with

sp4,

runn

ing

on In

tel x

86

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, w

ith sp

2, ru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

XP

Prof

essio

nal, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, x

64, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, x

64, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(6

4-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

an

d St

anda

rd E

ditio

ns, w

ith sp

2, ru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

and

Stan

dard

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on 32

-bit

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

x64 a

nd S

tand

ard

x64

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

x64 a

nd S

tand

ard

x64

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on

(64-

bit T

erad

ata T

ools

and

Utilit

ies)

]Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

nru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

n ru

nnin

g on

EM6

4T/O

pter

on x3

2-bi

t (3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

nru

nnin

g on

EM6

4T/O

pter

on x6

4-bi

t (3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

n ru

nnin

g on

EM6

4T/O

pter

on x6

4-bi

t (6

4-bi

t Ter

adat

a Too

ls an

d Ut

ilities



Teradata Parallel Transporter Stream Operator


Teradata Parallel Transporter Update Operator


Teradata Parallel Transporter Wizard


Teradata Performance Monitor YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata Query Director YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata Query Scheduler Administrator


Teradata Query Scheduler Client YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata Query Scheduler Server YES YES YES YES NO YES YES YES YES YES YES NO NO

Teradata SQL Assistant YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata SQL Assistant/Web Edition


Teradata Statistics Wizard YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata System Emulation Tool YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata TPump YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata Visual Explain YES YES YES YES NO YES YES YES NO YES YES YES NO

Teradata Workload Analyzer YES YES YES YES NO YES YES YES NO YES YES YES NO

WebSphere MQ Access Module for Teradata




Product Micr

osof

t Win

dows

2000

Pro

fess

iona

l Ser

ver

and

Adva

nced

Ser

ver,

with

sp4,

runn

ing

on In

tel x

86

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, w

ith sp

2, ru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

XP

Prof

essio

nal, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, x

64, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

XP

Prof

essio

nal, x

64, w

ith sp

2, ru

nnin

g on

Inte

l Xeo

n wi

th E

M64T

/Opt

eron

(6

4-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

an

d St

anda

rd E

ditio

ns, w

ith sp

2, ru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

and

Stan

dard

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on 32

-bit

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

x64 a

nd S

tand

ard

x64

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on

(32-

bit T

erad

ata T

ools

and

Utilit

ies)

Micr

osof

t Win

dows

Ser

ver 2

003 E

nter

prise

x64 a

nd S

tand

ard

x64

Editi

ons,

with

sp2,

runn

ing

on In

tel X

eon

with

EM6

4T/O

pter

on

(64-

bit T

erad

ata T

ools

and

Utilit

ies)

]Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

nru

nnin

g on

Inte

l x86

(3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

n ru

nnin

g on

EM6

4T/O

pter

on x3

2-bi

t (3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

)

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

nru

nnin

g on

EM6

4T/O

pter

on x6

4-bi

t (3

2-bi

t Ter

adat

a Too

ls an

d Ut

ilities

Micr

osof

t Win

dows

Vist

a Ent

erpr

ise E

ditio

n ru

nnin

g on

EM6

4T/O

pter

on x6

4-bi

t (6

4-bi

t Ter

adat

a Too

ls an

d Ut

ilities



a Named Pipes Access Module installs files for both the utility version and the Teradata Parallel Transporter version. It is included as a free product if you ordered any of the following products:

b The Teradata Archive and Recovery Utility (ARC) is included for Open Teradata Backup and is not sold as an individual product.

c Teradata MultiTool cannot be installed if Teradata Database is already installed, because the installation of Teradata Database installs Teradata MultiTool.

d FastExport OUTMOD Adapter Operator is installed as part of the Teradata Parallel Transporter Infrastructure installation.

e FastLoad INMOD Adapter Operator is installed as part of the Teradata Parallel Transporter Infrastructure installation.

f MultiLoad INMOD Adapter Operator is installed as part of the Teradata Parallel Transporter Infrastructure installation.

System Requirements

To use the Teradata Tools and Utilities software, you must have an i386-based or greater computer with:

• An appropriate network card

• Ethernet or Token Ring LAN cards

• 345.9MB of free disk space for a full installation

• FAT or NTFS for Teradata Generic Security Services (TeraGSS) Client

Platform Requirements

Before installing the Teradata Tools and Utilities software, your computer must run on one of the following operating systems:

Windows 2000

• Microsoft Windows 2000 Professional Server and Advanced Server, with sp4, running on Intel x86 (32-bit Teradata Tools and Utilities)

Windows XP Professional

• Microsoft Windows XP Professional, with sp2, running on Intel x86 (32-bit Teradata Tools and Utilities)

• Microsoft Windows XP Professional, with sp2, running on Intel Xeon with EM64T/Opteron (32-bit Teradata Tools and Utilities)

• Microsoft Windows XP Professional, x64, with sp2, running on Intel Xeon with EM64T/Opteron (32-bit Teradata Tools and Utilities)

Archive and Recovery Utility (ARC) Teradata FastLoad

Basic Teradata Query (BTEQ) Teradata MultiLoad

Teradata FastExport Teradata TPump



• Microsoft Windows XP Professional, x64, with sp2, running on Intel Xeon with EM64T/Opteron(64-bit Teradata Tools and Utilities)

Windows Server 2003

• Microsoft Windows Server 2003 Enterprise and Standard Editions, with sp2, running on Intel x86 (32-bit Teradata Tools and Utilities)

• Microsoft Windows Server 2003 Enterprise and Standard Editions, with sp2, running on Intel Xeon with EM64T/Opteron x32-bit (64-bit Teradata Tools and Utilities)

• Microsoft Windows Server 2003 Enterprise x64 and Standard x64 Editions, with sp2, running on Intel Xeon with EM64T/Opteron(32-bit Teradata Tools and Utilities)

• Microsoft Windows Server 2003 Enterprise x64 and Standard x64 Editions, with sp2, running on Intel Xeon with EM64T/Opteron (64-bit Teradata Tools and Utilities)

Windows Vista

• Microsoft Windows Vista Enterprise Edition, running on Intel x86 (32-bit Teradata Tools and Utilities)

• Microsoft Windows Vista Enterprise Edition, running on EM64T/Opteron x32-bit (32-bit Teradata Tools and Utilities)



Table 1 on page 22 shows which Windows platforms are supported by each product.

Administrator Privileges

You must have administrator privileges for the computer on which you will be installing the Teradata Tools and Utilities software.

Network Requirements

Your computer should be able to communicate with a network-attached Teradata Database that is using the TCP/IP protocol with Winsock version 2.0 support.

For an up-to-date description of which software the Teradata Database should be running, refer to the Teradata Tools and Utilities Release Definition, Release 12.0.

Teradata Database Requirements

The appropriate Ethernet hardware and software, supporting a TCP/IP-based network, must be installed on every Teradata Database with which your computer will communicate.


Chapter 1: IntroductionSoftware Requirements

Software Requirements

Product Dependencies

In the following table, the products in the first column are dependent upon, and must be installed with the products in the second column.

Table 2: Product Dependencies

These products... require these installations...

Basic Teradata Query (BTEQ) version 12.00.00 • CLIv2 version 12.00.00 or later

• Teradata Data Connector version 12.00.00 or later

• Shared ICU Libraries for Teradata version 12.00.00 or later

BTEQWin version 12.00.00 • BTEQ version 12.00.00

Named Pipes Access Module version 12.00.00 • No dependencies

NetBackup Teradata Extension version 12.00.00 • No dependencies

ODBC Driver for Teradata version 12.00.00 • Microsoft Data Access Components (MDAC), version 2.8 sp1 (on distribution CD)

• Shared ICU Libraries for Teradata version 12.00.00

• Teradata Generic Security Services version 12.00.00 or laterTeraGSS - Client package

Shared ICU Libraries for Teradata version 12.00.00 • No dependencies

Teradata Access Module for JMS version 12.00.00 • Teradata Data Connector version 12.00.00 or later

• JDK 1.4 or later

• JMS enabled Messaging System

Teradata Access Module for Tivoli version 12.00.00 • No dependencies

Teradata Administrator version 12.00.00 • ODBC Driver for Teradata version 12.00.00 or later

Teradata Archive/Recovery Utility (ARC) version 12.00.00 • CLIv2 version 12.00.00or later


Note: ARC is not distributed as a stand-alone product. It is installed with Open Teradata Backup on MP-RAS and Windows 2000.

Teradata C Preprocessor2 version 12.00.00 • CLIv2 version 12.00.00 or later




Teradata Call-Level Interface version 2 (CLIv2) version 12.00.00

• Shared ICU Libraries for Teradata version 12.00.00 or later

• Teradata Generic Security Services version 12.00.00 or laterTDGSS - Server packageTeraGSS - Client package

Teradata Data Connector version 12.00.00 • No dependencies

Teradata Dynamic Workload Manager version 12.00.00 • CLIv2 version 12.00.00 or later

Teradata FastExport version 12.00.00 • CLIv2 version 12.00.00 or later


Teradata FastLoad version 12.00.00 • CLIv2 version 12.00.00 or later


Teradata Generic Security Services Client (TeraGSS) version 12.00.00

• No dependencies

Teradata Generic Security Services Client Java (TeraGSSJava) version12.00.00

• No dependencies

Teradata Index Wizard version 12.00.00 • CLIv2 version 12.00.00 or later

or

• ODBC Driver for Teradata version 12.00.00 or later

Teradata Manager version 12.00.00 • CLIv2 version 12.00.00or later

Teradata MultiLoad version 12.00.00 • CLIv2 version 12.00.00 or later


Teradata MultiTool version 12.00.00 • Java 2 Runtime Environment 1.4 or later

Note: The environment can be downloaded from the Sun website at: http://java.sun.com/products/archive/j2se/1.4.0/index.html

Teradata OLE DB Access Module version 12.00.00 • ODBC Driver for Teradata version 12.00.00 or later

Teradata Performance Monitor version 12.00.00 • CLIv2 version 12.00.00 or later

Teradata Query Director version 12.00.00 • CLIv2 version 12.00.00 or later


• Teradata_GSS_Client version 12.00.00 or later

Teradata Query Scheduler Administrator version 12.00.00 • CLIv2 version 12.00.00 or later

Teradata Query Scheduler Client version 12.00.00 • CLIv2 version 12.00.00 or later

Teradata Query Scheduler Server version 12.00.00 • CLIv2 version 12.00.00 or later

• Teradata Query Scheduler Client version 12.00.00

Table 2: Product Dependencies (continued)



http://java.sun.com/products/archive/j2se/1.4.0/index.html



a FastExport OUTMOD Adapter Operator is installed as part of the Teradata Parallel Transporter Infrastructure installation.

b FastLoad INMOD Adapter Operator is installed as part of the Teradata Parallel Transporter Infrastructure installation.

c MultiLoad INMOD Adapter Operator is installed as part of the Teradata Parallel Transporter Infrastructure installation.

d Teradata Parallel Transporter12.00.00 is certified with Teradata Call-Level Interface version 2 release 12.00.00.

Teradata SQL Assistant version 12.00.00 • ODBC Driver for Teradata version 12.00.00 or later

Teradata SQL Assistant/Web Edition version 12.00.00 • ODBC Driver for Teradata version 12.00.00 or later

To install, your PC must run one of the following. It will not work with other Windows operating systems:

• Windows 2000 Professional

• Windows 2000 Server

• Windows 2000 Advanced Server

• Windows 2003, or

• 32-bit Windows XP.

Note: See “Installing Required Software for Teradata SQL Assistant/Web Edition” on page 52. This section documents the additional software that must be installed prior to installing Teradata SQL Assistant/Web Edition.

Teradata Statistics Wizard version 12.00.00 • CLIv2 version 12.00.00 or later

Teradata System Emulation Tool version 12.00.00 • CLIv2 version 12.00.00 or later

or


Teradata TPump version 12.00.00 • CLIv2 version 12.00.00 or later



Teradata Visual Explain version 12.00.00 • CLIv2 version 12.00.00 or later

or


• Teradata Parallel Transporter ICU Library version 12.00.00

• Shared ICU Libraries for Teradata 12.00.00 or later

Teradata Workload Analyzer version 12.00.00 • CLIv2 version 12.00.00 or later

WebSphere MQ Access Module version 12.00.00 • Teradata Data Connector 12.00.00 or later

• WebSphere MQ V5.2

Table 2: Product Dependencies (continued)



Chapter 1: IntroductionInstallation Kit

Installation Order

When installing Teradata Tools and Utilities products, four product dependencies must be installed first and in the following order:

1 Install ICU Libraries for Teradata (tdicu).

2 Install Teradata Generic Security Services (TeraGSS).

3 Install Teradata Call-Level Interface version 2 (CLIv2).

4 Install Teradata Data Connector (piom).

Note: ICU Libraries for Teradata should not be uninstalled until all software that have it as a dependency are first uninstalled.

Installation Kit

Your installation kit includes:

• Teradata Tools and Utilities Release Definition, Release 12.00.00

• Teradata Tools and Utilities documentation CD

There will also be one or more of the following CDs, depending on your purchase. Each CD contains product versions for one or more network-attached platforms. Refer to the following tables for more information:

• Teradata Utility Pak - Utilities CD#1 (Windows Products)

• Teradata Utility Pak - Utilities CD#2 (HP-UX, Linux, MP-RAS)

• Teradata Utility Pak - Utilities CD#3 (AIX and Solaris Products)

• Database Management

• Preprocessors - CD # 1 (Windows Products)

• Preprocessors - CD #2 (HP-UX, Linux, MP-RAS)

• Preprocessors - CD #3 (AIX and Solaris Products)

• Load/Unload - CD#1 (Windows Products)

• Load/Unload - CD#2 (HP-UX, Linux, MP-RAS)

• Load/Unload - CD#3 (AIX and Solaris Products)

• Parallel Transporter - CD#1 (Windows Products)

• Parallel Transporter - CD#2 (HP-UX, Linux, MP-RAS)

• Parallel Transporter - CD#3 (AIX and Solaris Products)

• Query Director

• Tape Storage Management Enablers

• Meta Data Services

If you did not receive all the CDs you ordered, contact the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC). For more information, refer to the Teradata Tools and Utilities Release Definition, Release 12.0.



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.ncr.com:8080/TSFS/home.do

IBM VM and IBM z/OS

Teradata Tools and Utilities products are also supported on channel-attached platforms, such as IBM VM and IBM z/OS. On these platforms, the products are loaded from tape. See the installation guides for these systems:

• Teradata Tools and Utilities Installation Guide for IBM VM

• Teradata Tools and Utilities Installation Guide for IBM z/OS

Teradata Driver for the JDBC Interface

The Teradata Driver for the JDBC Interface is downloaded from the World Wide Web. For installation, see “Installing the Teradata Driver for the JDBC Interface” on page 84.

The Java Development Kit is a requirement to use the Teradata Driver for the JDBC Interface. For information how to download the kit, see:

• Teradata Driver for the JDBC Interface User Guide

Teradata Parallel Transporter Wizard

Teradata Parallel Transporter Wizard includes code licensed from RSA Security, Inc. Some portions of the code licensed from IBM are available at:

http://oss.software.ibm.com/icu4j

Teradata Tools and Utilities CDs

The following tables list only the network-attached platform versions contained on the CDs.

Table 3: Teradata Utility Pak CD#1 (Windows Products)

Teradata Utility Pak - Utilities CD#1 Platforms (Windows)

Basic Teradata Query (BTEQ) Windows

Named Pipes Access Module Windows

ODBC Driver for Teradata Windows

Shared ICU Libraries for Teradata Windows

Teradata Administrator Windows

Teradata Call-Level Interface version 2 (CLIv2) Windows

Teradata Data Connector Windows


http://oss.software.ibm.com/icu4j



Teradata Generic Security Services Windows

Teradata MultiTool Windows

Note: Teradata MultiTool has a dependency on JRE 4.0 or later. This product is not part of the Teradata Tools and Utilities Installation Kit.

Teradata SQL Assistant Windows

Teradata SQL Assistant/Web Edition Windows

Table 4: Teradata Utility Pak CD#2 (HP-UX, Linux and MP-RAS Products)

Teradata Utility Pak - Utilities CD#2 Platforms (HP-UX, Linux and MP-RAS)

Basic Teradata Query (BTEQ) HP-UX, Linux, MP-RAS

Named Pipes Access Module HP-UX, Linux, MP-RAS

ODBC Driver for Teradata HP-UX, Linux, MP-RAS

Shared ICU Libraries for Teradata HP-UX, Linux, MP-RAS

Teradata Call-Level Interface version 2 (CLIv2) HP-UX, Linux, MP-RAS

Teradata Data Connector HP-UX, Linux, MP-RAS

Teradata Generic Security Services HP-UX, Linux, MP-RAS

Table 5: Teradata Utility Pak CD#3 (AIX and Solaris Products)

Teradata Utility Pak - Utilities CD#3 Platforms (AIX and Solaris)

Basic Teradata Query (BTEQ) IBM AIX, Solaris SPARC

Named Pipes Access Module IBM AIX, Solaris SPARC

ODBC Driver for Teradata IBM AIX, Solaris SPARC

Shared ICU Libraries for Teradata IBM AIX, Solaris SPARC, Solaris Opteron

Teradata Call-Level Interface version 2 (CLIv2) IBM AIX, Solaris SPARC, Solaris Opteron

Teradata Data Connector IBM AIX, Solaris SPARC

Teradata Generic Security Services IBM AIX, Solaris SPARC

Table 3: Teradata Utility Pak CD#1 (Windows Products) (continued)

Teradata Utility Pak - Utilities CD#1 Platforms (Windows)



Table 6: Data Management CD

Database Management CD Platforms (Windows)

Basic Teradata Query (BTEQ) Product dependency

ODBC Driver for Teradata Product dependency

Shared ICU Libraries for Teradata Product dependency

Teradata Call-Level Interface version 2 (CLIv2) Product dependency

Teradata Data Connector Product dependency

Teradata Dynamic Workload Manager Windows

Teradata Generic Security Services Product dependency

Teradata Index Wizard Windows

Teradata Manager Windows

Teradata Performance Monitor 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 7: Preprocessors CD#1 (Windows Products)

Preprocessors CD#1 Platforms (Windows)


Teradata C Preprocessor2 Windows


Teradata Generic Security Services Product Dependency

Table 8: Preprocessors CD#2 (HP, Linux, and MP-RAS Products)

Preprocessors CD#2 Platforms (HP-UX, Linux, and MP-RAS)


Teradata C Preprocessor2 HP-UX, Linux, MP-RAS




Teradata Cobol Preprocessor2 HP-UX, MP-RAS


Table 9: Preprocessors CD#3 (AIX and Solaris Products)

Preprocessors CD#3 Platforms (AIX and Solaris)


Teradata C Preprocessor2 IBM AIX, Solaris SPARC, Solaris Opteron


Teradata Cobol Preprocessor2 IBM AIX


Table 10: Load/Unload CD#1 (Windows Products)

Load/Unload CD#1 Platforms (Windows)


Teradata Access Module for JMS Windows

Named Pipes Access Module Windows

Note: Named Pipes Access Module contains both the stand-alone version and the Teradata Parallel Transporter version.




Teradata Data Connector Windows

Teradata FastExport Windows

Teradata FastLoad Windows


Teradata MultiLoad Windows

Teradata OLE DB Access Module Windows

Teradata TPump Windows

Table 8: Preprocessors CD#2 (HP, Linux, and MP-RAS Products) (continued)

Preprocessors CD#2 Platforms (HP-UX, Linux, and MP-RAS)



WebSphere MQ Access Module Windows

Note: WebSphere MQ Access Module contains both the stand-alone version and the Teradata Parallel Transporter version.

Table 11: Load/Unload CD#2 (HP-UX, Linux and MP-RAS Products)

Load/Unload CD#2 Platforms (HP-UX, Linux, and MP-RAS)


Teradata Access Module for JMS HP-UX

Named Pipes Access Module MP-RAS, HP-UX, Linux



Teradata Data Connector MP-RAS, HP-UX, Linux

Teradata FastExport MP-RAS, HP-UX, Linux

Teradata FastLoad MP-RAS, HP-UX, Linux


Teradata MultiLoad MP-RAS, HP-UX, Linux

Teradata TPump MP-RAS, HP-UX, Linux

WebSphere MQ Access Module MP-RAS, HP-UX, Linux


Table 12: Load/Unload CD#3 (AIX and Solaris Products)

Load/Unload CD#3 Platforms (AIX and Solaris)


Teradata Access Module for JMS Solaris SPARC

Named Pipes Access Module Solaris SPARC, AIX



Table 10: Load/Unload CD#1 (Windows Products) (continued)

Load/Unload CD#1 Platforms (Windows)





Teradata Data Connector Solaris SPARC, AIX, Solaris Opteron

Teradata FastExport Solaris SPARC, AIX, Solaris Opteron

Teradata FastLoad Solaris SPARC, AIX, Solaris Opteron


Teradata MultiLoad Solaris SPARC, AIX, Solaris Opteron

Teradata TPump Solaris SPARC, AIX, Solaris Opteron

WebSphere MQ Access Module Solaris SPARC, AIX, Solaris Opteron


Table 13: Parallel Transporter CD#1 (Windows Products)

Parallel Transporter CD#1 Platforms (Windows)

Named Pipes Access Module Product dependency





WebSphere MQ Access Module Product dependency


Table 14: Parallel Transporter CD#2 (HP-UX, Linux, and MP-RAS Products)

Parallel Transporter CD#2 Platforms (HP-UX, Linux, and MP-RAS)



Table 12: Load/Unload CD#3 (AIX and Solaris Products) (continued)

Load/Unload CD#3 Platforms (AIX and Solaris)






WebSphere MQ Access Module HP-UX, Linux and MP-RAS


Table 15: Parallel Transporter CD#3 (AIX and Solaris Products)

Parallel Transporter CD#3 Platforms (AIX and Solaris)






WebSphere MQ Access Module Product Dependency


Table 16: Tape Storage Management Enablers CD

Tape Storage Management Enablers CD Platforms (Windows, Linux, MP-RAS)



Teradata Access Module for Tivoli Windows

Teradata Archive/Recovery Utility (ARC) MP-RAS, Linux and Windows

Note: ARC is not distributed as a stand-alone product. It is installed with Open Teradata Backup on MP-RAS and Windows 2000.

Teradata C Preprocessor2 Product dependency


Table 14: Parallel Transporter CD#2 (HP-UX, Linux, and MP-RAS Products) (continued)

Parallel Transporter CD#2 Platforms (HP-UX, Linux, and MP-RAS)



Note: If you did not receive these items, contact the TSCS-RSC. See the Teradata Tools and Utilities Release Definition, Release 12.0 for further instructions.

Note: For information on installing the Teradata Access Module for Tivoli, see the Teradata Access Module for Tivoli Installation and User Guide.

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 UNIX and Linux products, see the Teradata Tools and Utilities Installation Guide for UNIX and Linux.

Teradata Data Connector Product dependency


Table 17: Query Director CD

Query Director CD Platforms (Windows and Linux)




Teradata Query Director Windows, Linux

Table 18: MetaData Services CD

MetaData Services CD Platforms (MP-RAS, Linux, Windows)

Meta Data Services Linux, MP-RAS, Solaris SPARC

Relay Services Gateway Product dependency

Table 16: Tape Storage Management Enablers CD (continued)

Tape Storage Management Enablers CD Platforms (Windows, Linux, MP-RAS)


CHAPTER 2

Before You Install

This chapter describes the procedures to set up the installation of Teradata Tools and Utilities software on Microsoft Windows client systems. This chapter contains the following information:

• Installation Recommendations

• Technical Assistance

• Installing Required Software for Teradata SQL Assistant/Web Edition

Installation Recommendations

Before you begin installing Teradata Tools and Utilities software on Microsoft Windows client systems, make sure your software package is complete (see “Installation Kit” on page 31) and that your PC is set up with the required software and hardware. If you did not receive the correct disks, contact the TSCS-RSC. You should also familiarize yourself with the following issues.

Make sure you have the appropriate Teradata Tools and Utilities CDs. The available CDs are:














• Query Director




Chapter 2: Before You InstallInstallation Recommendations

Note: If you did not receive all the CDs you ordered, contact the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC). For more information, refer to the Teradata Tools and Utilities Release Definition, Release 12.0.

Note: This installation guide does not describe how to install the OLE DB Provider for Teradata. For installation on how to install the OLE DB Provider for Teradata Installation and User Guide.

Note: This installation guide does not describe how to install the Meta Data Services. For installation on how to install the Teradata Meta Data Services Installation and Administration Guide.

Note: This installation guide does not describe how to install the Teradata Query Director. For installation on how to install the Teradata Query Director, see the Teradata Query Director User Guide.

Familiarize yourself with the issues described in the following subsections.

Installing on Windows Vista

Windows Vista does not install the Windows Help program, WinHlp32.exe. This application is required to display 32-bit online help files delivered with Teradata Tools and Utilities products. Use the following procedure to install the Windows Help program.

To install the Windows Help program

The Teradata Tools and Utilities product must be installed before proceeding.

1 Go to http://www.microsoft.com/downloads/

2 In the Search box, type WinHlp32 Vista to locate the WinHlp32.exe file.

Note: Windows Vista users must pass a short validation process before downloading the file. Once validated, specific instructions are given for obtaining the download.

3 Run the executable.

The default location is the c:\Windows directory.

Installing on EM64T Systems

On 64-bit EM64T systems, the following TTU 12.00.00.00 CDs will install only the 32-bit versions of the Teradata Tools and Utilities products that support both 32-bit and 64-bit installations, since the primary Teradata Tools and Utilities products on each CD only support 32-bit installations:


• Query Director

• Load/Unload CD#1




http://www.microsoft.com/downloads/


Preprocessors CD and Parallel Transporter CD

On a 64-bit EM64T system, Preprocessors CD#1, and Parallel Transporter CD#1 will install only the 64-bit versions of Teradata Tools and Utilities products that support both 32-bit and 64-bit installations.

To install the 32-bit version of these products on a 64-bit EM64T system, you must first run a “NETWORK” install on a 32-bit system, and select the desired Teradata Tools and Utilities products. On the EM64T system, mount the network drive containing the 32-bit installation packages and run the installations.

Teradata Utility Pak - Utilities CD#1

To install BTEQ from the Teradata Utility Pak - Utilities CD#1 on a 64-bit EM64T system, select BTEQ in either a “TYPICAL” or “CUSTOM” installation. BTEQ, will install the 32-bit versions of CLIv2, TeraGSS, and ICU, since BTEQ only supports 32-bit installations. To install the 64-bit versions of CLIv2, TeraGSS and ICU, deselect BTEQ.

Minimum and Recommended Configurations

The following sections contain information on the minimum and recommended configurations for systems installing Teradata Tools and Utilities products.

Minimum Configurations

The following table shows the minimum configurations for Teradata Tools and Utilities products.

Table 19: Minimum Configurations for Teradata Tools and Utilities

Product Client Server

Teradata ManagerTeradata Performance Monitor Teradata AdministratorTeradata Statistics WizardTeradata Dynamic Workload ManagerTeradata Query Scheduler

500 MHz Pentium III256 MB RAM10 GB Hard Drive (100 MB for TMGR)CD ROM Drive

1.2 GHz Pentium IV512 MB RAM2*18 GB Hard Drive (100 MB for TMGR)CD ROM DriveModem (required to use the Send a Page action of the Alerts facility)


500 MHz Pentium III256 MB RAM10 Mbps Network Interface Card or Modem1024x768 SVGA Display

1.2 GHz Pentium IV512 MB RAM100 Mbps Network Interface Card1024x768 SVGA DisplayCD ROM Drive or DVD Drive2*18 GB Hard Drive

Teradata SQL Assistant 500 MHz Pentium III64 MB RAMCD ROM DriveSVGA or better, Graphics Controller and MonitorMinimum 50 MB free disk space



Recommended Configurations

The following table shows the recommended configurations for Teradata Tools and Utilities products.

Shared ICU Libraries for Teradata Recommendations

It’s recommended that the Shared ICU Libraries for Teradata be installed to a local drive. If it is installed to a network shared drive, the performance for running the Shared ICU Libraries may be degraded.

Installation of Dependent Products

The Teradata Tools and Utilities installation can automatically install dependent products. If a dependent product already exists on your system for one of the following products:

• Shared Common Components for Internationalization for Teradata

• Teradata Call-Level Interface version 2 (CLIv2)

• Teradata Data Connector

• ODBC Driver for Teradata

• Teradata Generic Security Services

The installation will display one of two messages. The first message is displayed if a dependent product already exists and its version is the same as the dependent product being installed. It asks if you want to reinstall the existing installed product.

For example, the following message is for the ODBC Driver for Teradata:

Table 20: Recommended Configurations for Teradata Tools and Utilities

Product Client Server

Teradata ManagerTeradata Performance Monitor Teradata AdministratorTeradata Statistics WizardTeradata Dynamic Workload ManagerTeradata Query Scheduler

1.2 GHz Pentium IV512 MB RAM40 GB Hard Drive (200 MB for TMGR)CD ROM Drive

2 GHz Pentium IV1 GB RAM2*30 GB Hard Drive (200 MB for TMGR)CD ROM DriveModem (required to use the Send a Page action of the Alerts facility)


1.2 GHz Pentium IV256MB RAM10 Mbps Network Interface Card or Modem1024x768 SVGA Display

2 GHz Pentium IV1 GB RAM100 Mbps Network Interface Card1024x768 SVGA DisplayCD ROM Drive or DVD Drive2*18 GB Hard Drive

Teradata SQL Assistant 1.2 GHz Pentium IV256 MB RAMCD ROM DriveSVGA or better, Graphics Controller and MonitorMinimum 100 MB free disk space



"ODBC Driver for Teradata 12.00.00.00 is already installed.Do you want to reinstall it?"

The second message is displayed if a dependent product already exists and its version is not equal to the dependent product being installed. It asks if you want to overwrite the existing installed product.

For example, the following message is for the ODBC Driver for Teradata:

"ODBC Driver for Teradata 3.6.0.0 is already installed. Do you want to overwrite it with version 12.00.00.00?"

Teradata Generic Security Services

Multiple Versions of Teradata Generic Security Services

Since it may not be practical to install or upgrade all parts of your 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.

FAT or NTS File System for Teradata Generic Security Services

Both the NTS and FAT file systems are now supported for Teradata Generic Security Services (TeraGSS) Client. When installing on a FAT file system an LCLIENT directory is created and files are copied to it.

Whenever tdgssconfig is run, it must be run from the LCLIENT\bin directory on a FAT file system. See the section on “TDGSS File Maintenance Tools” in Teradata Database Security Administration.

PUT Installations

Some of products can be installed using the software Teradata Parallel Upgrade Tool (PUT). Currently the following products are the only Teradata Tools and Utilities products that can be installed using the software Parallel Upgrade Tool (PUT) on Microsoft Windows:

• Basic Teradata Query (BTEQ)

• Named Pipes Access Module

• Shared ICU Libraries for Teradata



• Teradata Generic Security Services - Client

• FastExport

• FastLoad

• MultiLoad

• MQ Access Module

• TPump



To use PUT to install these products, refer to the Parallel Upgrade Tool (PUT) User Guide for Microsoft Windows.

Typical, Custom, and Network Installations

Running the installation you can install:

• All of the Teradata Tools and Utilities products on the current CD (Typical installation)

• Some of the products on the current CD (Custom installation)

• It allows you to copy the product’s setup files to a specified folder (Network installation)

For a list of product dependencies, refer to “Software Requirements” on page 28.

Command Line Installations

You can “silently” install Windows packages from the command prompt:

• Download packages from the Teradata Software Server

• Copy packages using a Network Setup Type, then copy them to the target machine

For a list of product dependencies, refer to “Software Requirements” on page 28.

Teradata Download Center Installations

Some Teradata Tools and Utilities products are available for download on the Teradata Download Center. Some, like the device independent .jar files for the Teradata Driver for the JDBC Interface can only be downloaded from the center.

The following software drivers can be downloaded:

• ODBC Driver for Teradata (ODBC)

• Teradata Driver for the JDBC Interface (JDBC)

• OLE DB Provider for Teradata (OLE DB)

• Call-Level Interface (CLIv2)

The Teradata Download Center is located at:

http://www.teradata.com --> Support Services --> Downloads--> Drivers, UDFs, and Toolbox --> Drivers and Connectivity Software

Teradata Parallel Transporter Installation

Multiple versions of Teradata Parallel Transporter can co-exist on the system. The exception is the emergency fix (e-fix) version of Teradata Parallel Transporter. This version will overwrite the original Teradata Parallel Transporter version.

For example, an installation of Teradata Parallel Transporter 12.00.00.01 version will overwrite the previously released version of Teradata Parallel Transporter 12.0.0.0.

If you have an earlier version of Teradata Parallel Transporter installed, you must install the later version into a different folder.





If you have the following user environment variables, it is recommended that you delete them before running a Teradata Parallel Transporter job:

• TWB_ROOT

• _MSGCATLOCATION

Uninstalling Previous Software

You do not have to uninstall previous versions of Teradata Tools and Utilities software. However, if you have an earlier version of Teradata Manager installed, you must install the later version into a different folder.

Note: The 64-bit BTEQ package on Windows has been decommissioned. The install/upgrade procedure will not automatically remove this decommissioned 64-bit BTEQ package, however uninstalling the 32-bit BTEQ version will remove the previously installed 64-bit version.

Default Folders

The main folders on the application CDs are:

Table 22 shows the default destination and program folders for the Teradata Tools and Utilities products. <Boot Drive> is the drive destination of the Windows boot up drive.

Table 22 also shows the product response files (*.iss files) that are copied from the Windows\TTU\ClientISS folder on the CD to the %TEMP%\ClientISS folder on the local computer during installation. If a product response file already exists on the local computer, it will be copied over. You can review these files to help resolve installation problems.

Default Product Response Files

All product response files can be used for both new installations and upgrades. For all products, except Teradata Manager, the product response file installs all product components. For Teradata Manager, the product response file installs only the client components.

Procedure - Modifying a Product Response file

To modify a product response file in %TEMP%\ClientISS, use Notepad or another text editor. For example, if you want to change the folder name:

Table 21: Default CD Folders

The folder: Contains:

Windows\Bin files used for autorun.

Windows\TTU\ClientISS response files for products that need them to support silent installation.

Windows\TTU\setupdir Files used in installation.



1 Use an editor to open the response file.

2 Change the value of the szFolder field.

3 Save and exit the response file.

If you encounter problems during silent installation, refer to “Silent Installation Result Codes” on page 156.

Table 22: Default Folders and Product Response Files

Product Default Destination Folder (<Boot Drive>) Default Program Folder

Basic Teradata Query (BTEQ)

BTEQ.iss

%Program Files%\NCR\Teradata Client Teradata Client

BTEQWin

No product response file


Named Pipes Access Module

NamedPipes.iss

%SystemRoot%\system32 None

ODBC Driver for Teradata

odbc.iss

%Program Files%\NCR\ODBC Driver for Teradata

ODBC Driver for Teradata

Shared ICU Libraries for Teradata

SharedICULibrariesforTeradata.issSharedICULibrariesforTeradata64.iss

%Program Files%\NCR\Common Files\Shared ICU Libraries for Teradata\Lib

None

Teradata Access Module for Tivoli

Teradata_Access_Module_for_Tivoli.iss

%Program Files%\NCR\Teradata Client Teradata Tivoli Access Module

Teradata Access Module for JMS

Teradata_JMS.iss

%Program Files%\Common Files\NCR\JMSAXSMOD

None

Teradata Administrator


%Program Files%\NCR\Teradata Administrator <version>

Teradata Administrator <version>

Teradata Archive/Recovery Utility (ARC)

ARC.iss


Teradata C Preprocessor2

Preprocessor.iss



CLI_Module.issCLI_Module64.iss

<Boot Drive>:\Program Files\NCR\Teradata Client\cliv2

None

Teradata Data Connector

DataConnector.issDataConnector64.iss

%SystemRoot%\system32 None



Teradata Dynamic Workload Manager (Teradata DWM)Teradata_Dynamic_Workload_Manager.iss

%Program Files%\NCR\Teradata Dynamic Workload Manager<version>

None

Teradata Generic Security Services (TeraGSS) Client

There is no product response file.

%Program Files%\NCR\Teradata GSS\nt-i386\<version> (for 32-bit)

%Program Files%\NCR\Teradata GSS\nt-i386\<version> (for 64-bit)

Same as Default Destination Folder

Teradata Generic Security Services (TeraGSS Java) Client Java

There is no product response file.

Teradata FastExport

FastExport.iss


Teradata FastLoad

FastLoad.iss


Teradata Index Wizard

Teradata_Index_Wizard.iss

%Program Files%\NCR\Teradata Index Wizard <version>

Teradata Index Wizard <version>

Teradata Manager

TMgr.iss

%Program Files%\NCR\Teradata Manager <version>

Teradata Manager <version>

Teradata MultiLoad

MultiLoad.iss


Teradata MultiTool


%Program Files%\NCR\Teradata MultiTool Teradata Client

Teradata OLE DB Access Module

OLE_DB_AM.iss


• Teradata Parallel Transporter ICU Library

Teradata_Parallel_Transporter_ICU_Library.iss

\Program Files\NCR\Teradata Parallel Transporter\<version>\Bin

None

Teradata Performance Monitor

Teradata_Performance_Monitor.iss

%Program Files%\NCR\Teradata Performance Monitor

Teradata Performance Monitor <version>

Teradata Query Director

Query_Director.iss

%Program Files%\NCR\Teradata Query Director Teradata Query Director <version>


TDQM_Admin.iss

%Program Files%\NCR\Teradata Query Scheduler Admin <version>

Teradata Query Scheduler Admin <version>

Table 22: Default Folders and Product Response Files (continued)



Chapter 2: Before You InstallRestarting After Installation

Note: The Teradata SQL Assistant/Web Edition software will be installed on the drive where the Microsoft Internet Information Services (IIS) software was previously installed.

Restarting After Installation

After installation, restart your computer to ensure that the environment variables are set correctly and allow the upgrade of files in use to complete.

Teradata Query Scheduler Client

TDQM_Client.iss

%Program Files%\NCR\Teradata Query Scheduler <version>

Teradata Query Scheduler Utilities <version>

Teradata Query Scheduler Server

TDQM_Server.iss

(use port number 3000)

%Program Files%\NCR\Teradata Query Scheduler Server <version>\server

None

Teradata SQL Assistant


%Program Files%\NCR\Teradata SQL Assistant <version>

None



\inetpub\wwwroot\<SqlAssistantWeb> a None

Teradata Statistics Wizard

Teradata_Statistics_Wizard.iss

%Program Files%\NCR\Teradata Statistics Wizard <version>

None

Teradata System Emulation Tool

Teradata_System_Emulation_Tool.iss

%Program Files%\NCR\Teradata System Emulation Tool <version>

Teradata System Emulation Tool <version>

Teradata TPump

TPump.iss


Teradata Visual Explain

Visual_Explain.iss

%Program Files%\NCR\Teradata Visual Explain <version>

Teradata Visual Explain <version>

Teradata Workload Analyzer

twa.iss

\Program Files\NCR\Teradata Workload Analyzer 12.0

None

WebSphere MQ Access Module

WebSphere_Access_Module_for_Teradata.iss

%Program Files%\Common Files\AXSMOD None

Table 22: Default Folders and Product Response Files (continued)



Chapter 2: Before You InstallTechnical Assistance

Technical Assistance

Technical assistance during installation of the Teradata Tools and Utilities software is available from the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC).

For more information, refer to the

Teradata Tools and Utilities Release Definition, Release 12.0.


Chapter 2: Before You InstallInstalling Required Software for Teradata SQL Assistant/Web Edition

Installing Required Software for Teradata SQL Assistant/Web Edition

This section describes the required software that must be loaded to connect Windows clients to the Teradata SQL Assistant/Web Edition.

• Installing Microsoft Internet Information Services

• Installing ASP.NET for Windows Server 2003

• Installing Microsoft .NET Framework (version 1.1)

• Installing Microsoft Visual J#.Net Redistributable Package (version 1.1)

• Installing the Cumulative Security Patch for IIS

Teradata SQL Assistant/Web Edition uses a Web browser to interface to the Teradata Database. The Teradata SQL Assistant/Web Edition software must be installed on a server computer.

Several client computers can then connect to the server. Clients, which can run on any Windows operating system, requires either Microsoft Internet Explorer, version 5.5 or later, or Netscape 7.0 or higher to access the Teradata Database through the server.

Note: The Windows 2000 Professional and 32-bit Windows XP operating systems support 10 or fewer clients. The Windows 2000 Server, Windows 2000 Advanced Server, Windows Server 2003 and Windows Vista operating systems support more than 10 clients.

You must have Microsoft Internet Explorer, version 5.5 or later, installed on your computer. If you use version 5.5, you must install Internet Explorer 5.5 Service Pack 2. If you use version 6.0, you must install Internet Explorer 6.0 Service Pack 1.

ODBC Driver for Teradata and Microsoft Data Access Components will be installed as part of the Teradata Tools and Utilities installation. To use Teradata SQL Assistant/Web Edition, you must install the versions of these products provided on the Teradata Tools and Utilities 12.0 Teradata Utility Pak CD.

Before installing the Teradata SQL Assistant/Web Edition software, install the following products in the order given. You must have administrator privileges to install the software.

• If your computer runs the Windows 2000 Professional or 32-bit Windows XP operating system, install:

• “Installing Microsoft Internet Information Services” on page 53

Note: To install the Microsoft Internet Information Services (IIS), you must have a Windows 2000 or Windows XP operating system CD or access to Windows 2000 or Windows XP from an alternate location such as a network server.

If your computer runs on the Windows Server 2003, install:

• “Installing ASP.NET for Windows Server 2003” on page 53

On any computer, except one running Windows Vista, that will run Teradata SQL Assistant/Web Edition, install the following:

• “Installing Microsoft .NET Framework (version 1.1)” on page 54



Installing Microsoft Internet Information Services

Procedure - Installing Microsoft Internet Information Services

Follow these steps to install Microsoft Internet Information Services on your client.

1 Go to Start > Settings > Control Panel > Add/Remove Programs.

2 In the left panel of the Add/Remove Programs dialog box, click Add/Remove Windows Components.

3 In the Windows Components Wizard dialog box, select Internet Information Services (IIS).4 Click Next and follow the installation instructions. You must have a Windows Installer CD.

5 After the IIS installation is complete, go to the next section to install Microsoft .NET Framework, version 1.1.

Installing ASP.NET for Windows Server 2003

If your computer runs on the Windows Server 2003 operating system, you must install ASP.NET:

Procedure - Installing ASP.NET for Windows Server 2003

Follow these steps to install ASP.NET for Windows Server 2003 on your client.


2 In the left panel of the Add/Remove Programs dialog box, click Add/Remove Windows Components.

3 In the Windows Components Wizard dialog box, select Application Server.4 Click Details and check the ASP.NET checkbox.

5 Click OK.

6 Click Next to add the software.

7 Click Finish when ASP.NET has been added.

8 Close the Add/Remove Programs control panel.

Procedure - Installing ASP.NET on Windows Vista

Follow these steps to install ASP.NET for Windows Server 2003 on a Windows Vista client.

1 Go to Start > Settings > Programs and Features > Add/Remove Programs.

2 In the left panel of the Add/Remove Programs dialog box, click Turn Windows features on or off.

3 In the Features Wizard dialog box, select Application Server.



4 Under the Internet Information Services tab, go to Web Management Tools->IIS 6 Management Compatibility and click the IIS Metabase and IIS 6 configuration compatibility checkbox.

5 Under the Internet Information Services tab, go to World Wide Web Services->Application Development Features and click the ASP.NET checkbox.

6 Click OK and follow the installation instructions.

Installing Microsoft .NET Framework (version 1.1)

On any computer running an operating system older than Windows Vista, follow these steps to install the Microsoft .NET Framework, version 1.1. Before installing the Microsoft .NET Framework, you must first install the Microsoft .NET Framework Redistributable, version 1.1. This is not necessary on a computer running Windows Vista.

Note: On Windows Vista, it is not necessary to install dotnetetfx.exe.

Procedure - Installing Microsoft .NET Framework (version 1.1)

Follow these steps to install Microsoft .NET Framework (version 1.1) on your client.

1 Go to http://msdn.microsoft.com/downloads.

2 From this page, find the Microsoft .NET Framework Redistibutable, version 1.1 software download page.

3 Download Microsoft .NET Framework Redistibutable, version 1.1 software.

4 In the dotnetfx.exe dialog box, enter the location where you want to place the extracted files, then click OK. Remember this location.

5 From your Explorer window, find the dotnetfx.exe file you just saved and double-click on it.

6 In the Microsoft .NET Framework Setup dialog box, click Yes to install the Microsoft .NET Framework package.

7 If the installation requests, restart your computer; otherwise, continue.

8 After the Microsoft .NET Framework installation is complete, go to the next section to install Microsoft Visual J#.Net Redistributable Package.

Installing Microsoft Visual J#.Net Redistributable Package (version 1.1)

On any computer that will run Teradata SQL Assistant/Web Edition, follow these steps to install the Microsoft Visual J#.Net Redistributable Package (version 1.1).


http://msdn.microsoft.com/downloads


Procedure - Installing the Microsoft Visual J#.Net Redistributable Package

Follow these steps to install Microsoft Visual J#.Net Redistributable Package (version 1.1) on your client.

1 Go to http://msdn.microsoft.com/downloads.

2 From this page, find the Microsoft Visual J#.Net Redistributable Package (version 1.1) software download page.

3 Download Microsoft Visual J#.Net Redistributable Package (version 1.1) software.

Installing the Cumulative Security Patch for IIS

If you use Microsoft Internet Information Services (IIS) to operate a Web site, and are operating the Web site when you are using Teradata SQL Assistant/Web Edition, you must ensure that you have the latest Microsoft Internet Information Services (IIS) patches installed.

The patches are needed because of the previous security vulnerabilities that allow an attacker to take over your computer to the extent that the attacker could change Web pages, install and run software, or reformat the hard drive. Even rarely visited Web sites could be attacked via a virus or worm. You eliminate this vulnerability by staying up-to-date with the latest patches to Microsoft Internet Information Services (IIS).

Search at the following Web site for “IIS Patches”:

http://www.microsoft.com/

Changing Microsoft Internet Explorer Security Settings

To enable Teradata SQL Assistant/Web Edition to return information to you from the Web, you may need to change the security settings in Microsoft Internet Explorer.

Procedure - Changing Microsoft Internet Explorer Security Settings

Follow these steps to change the Explorer settings for version 5.5 or version 6.0:

1 Open Microsoft Internet Explorer.

2 Go to Tools > Internet Options.

3 In the Internet Options dialog box, click the Security tab, then click Custom Level.4 From the Security Settings dialog box, enable the following settings:

a Downloads / File download: click EnableThis allows you to save the query, history, or answer set.

b Miscellaneous / Submit non encrypted form data: click EnableThis allows you to submit HTML forms.

c Scripting / Active scripting: click EnableThis allows you to submit SQL queries.


http://msdn.microsoft.com/downloads

http://www.microsoft.com/


Leave all other settings as is.

5 In the Security Settings dialog box, click OK.

6 In the Internet OptionsOK dialog box, click.

Changing Cookies Settings on Microsoft Internet Explorer

A cookie is a packet of information sent by an HTTP server to a browser, then sent back by the browser each time it accesses that server. Cookies are typically used to identify a user without requiring them to sign in each time they access a Web site.

To differentiate you from other users, Teradata SQL Assistant/Web Edition uses HTTP cookies. Changing the cookies settings in your Microsoft Internet Explorer is necessary for the following reasons:

• So you won't have to log on twice, once for the application and again for the Teradata Database.

• For the history table to be maintained for each specific user.

Changing Cookie Settings on Microsoft Internet Explorer, version 5.5

Procedure - Changing the Cookie Settings on Microsoft Internet Explorer 5.5

Follow these steps to change the settings on Microsoft Internet Explorer, version 5.5:



3 In the Internet Options dialog box, click the Security tab, then click Custom Level.4 In the Security Settings dialog box, enable the following settings:

a Cookies / Allow cookies that are stored on your computer: click Enable

b Cookies / Allow per-session cookies (not stored): click EnableLeave all other settings as is.

5 In the Security Settings dialog box, click OK.

6 In the Internet Options dialog box, click OK.

Changing Cookie Settings on Microsoft Internet Explorer, version 6.0

Procedure - Changing the Cookie Settings on Microsoft Internet Explorer 6.0

Follow these steps to change the settings on Microsoft Internet Explorer, version 6.0:



3 In the Internet Options Privacy Advanced dialog box, click the tab, then click.



4 In the Advanced Privacy Settings dialog box, change your settings as follows:

a Override automatic cookie handling: check this check box

b First-party cookies: select Accept

c Third-party cookies: select Accept

d Always allow session cookies: clear this check box

Leave all the other settings as is.

5 In the Advanced Privacy Settings dialog box, click OK.

6 In the Internet Options dialog box, click OK.

Setting the Number of Client Connections

The Windows 2000 Professional and 32-bit Windows XP operating systems support 10 or fewer clients. The Windows 2000 Server, Windows 2000 Advanced Server and the Windows 2003 Server operating systems support more than 10 clients.

Windows 2000 Professional and Windows 2000 Advanced Server

If your computer runs on the Windows 2000 Server or Windows 2000 Advanced Server operating system, the number of client computers that connect to your server can be changed. This is usually done by the system administrator.

Procedure - Setting the Number of Client Connections on Windows 2000

Follow these steps to change the client connections setting on Windows 2000 and Windows 2000 Advanced Server:

1 Go to Start > Settings > Control Panel > Administrative Tools > Internet Services Manager.2 In the Internet Information Services dialog box, in the left panel, click the plus sign (+) next

to the name of the computer to expand the tree.

3 Right-click to get a pop-up menu, then click Properties.

4 In the Default Web Site Properties dialog box, select the Web Site tab.

5 Choose one of the following options:

a UnlimitedThis allows an unlimited number of connections to occur simultaneously.

b Limited to <number> connections

Select the maximum number of simultaneous connections to be allowed.

6 Click Apply, then click OK.

7 Close the Internet Information Services dialog box.



Windows 2003 Server

If your computer runs on the Windows 2003 Server operating system, the number of client computers that connect to your server can be changed. This is usually done by the system administrator.

Procedure - Setting the Number of Client Connections on Windows 2003 Server

Follow these steps to change the connections setting on Windows 2003 Server:

1 Go to Start > Settings > Control Panel > Administrative Tools > Internet Information Services Manager.

2 In the Internet Information Services dialog box, in the left panel, click the plus sign (+) next to the name of the computer to expand the tree.

3 Expand the WebSites folder to display the Default Web Site.

4 Right-click Default Web Site to get a pop-up menu, then click Properties.

5 In the Default Web Site Properties dialog box, select the Performance tab.

6 Choose one of the following options:

a UnlimitedThis allows an unlimited number of connections to occur simultaneously.

b Limited to <number> connections

Select the maximum number of simultaneous connections to be allowed.

7 Click Apply, then click OK.

8 Close the Internet Information Services dialog box.

Setting the Number of Clients on Windows Vista

Procedure - Setting the Number of Clients on Windows Vista

Follow these steps to set the number of clients on Windows Vista.

1 Go to Start->Settings->Control Panel->Administrative Tools->Internet Information Services.

2 Drill-down to the Default web-site and select it.

3 On the right side of the screen, there is a list of Actions, click on the Limits… link under Configure.

4 Check the Limit number of connections: check-box and enter a session limit.

5 Click OK.

6 Close the Internet Information Services dialog.



Updating the Teradata Parallel Transporter API

The following is a list of major new features in Teradata PT API 12.0. For a complete list of changes to the product, see the Teradata Tools and Utilities Release Definition associated with this release.

• Unicode Support (UTF16)

• Buffer Mode Exporting with Export Driver’s New GetBuffer Function

• Performance Enhancement for the Export Driver’s GetRow Function

• Array Support for the Stream Driver

When upgrading applications built with previous versions of the Teradata Parallel Transporter API to the current release of the Teradata Parallel Transporter API, note that the Teradata Parallel Transporter API header files have been changed in the 12.0 release of the product. Applications built with previous versions of Teradata Parallel Transporter API must be re-compiled with these updated header files in order to use Teradata PT API 12.0.

The Teradata Parallel Transporter ICU library is installed with Teradata Parallel Transporter API and is located in the same directory as the other Teradata Parallel Transporter API libraries.


CHAPTER 3

Installing the Teradata Tools andUtilities Software

This chapter describes how to install and configure the Teradata Tools and Utilities software.

• Types of Installation

• Installing Using PUT

• Installing Using the Client Main Install

• Typical Installation

• Custom Installation

• Network Installation

• Installing a Package from the Command Prompt

• Installing the Teradata Driver for the JDBC Interface

• Installing the OLE DB Provider for Teradata from the Download Center

Types of Installation

There are four methods you can use to install Teradata Tools and Utilities products:

• PUT — The Teradata Parallel Upgrade Tool can be used as an alternative method of installing some of the Teradata Tools and Utilities products you purchased. See “Installing Using PUT” below.

• Using the Client Main Install — All Teradata Tools and Utilities products, except for the Teradata Driver for the JDBC Interface and the OLE DB Provider for Teradata can be installed using the Client Main Install. See “Installing Using the Client Main Install” on page 63. The Client Main Install is typical of Windows installations, allowing three forms of installation:

• Typical Installation — A typical installation installs all the products on each CD. See “Typical Installation” on page 64.

• Custom Installation — A custom installation installs only those products you select from the available products. See “Custom Installation” on page 74.

• Network Installation— A network installation copies of the installation packages for the selected products to a specified folder. The network installation does not actually install the products. This must be done by the user. See “Network Installation” on page 78.


Chapter 3: Installing the Teradata Tools and Utilities SoftwareInstalling Using PUT

• Installing from the Command Prompt — Packages can be downloaded from a patch server, or copied using Network Setup Type, then installed on the target machine by providing the package response file name as an input to the setup.exe command at the command prompt. These packages are installed silently. See “Installing a Package from the Command Prompt” on page 80.

• Downloading Files from the Teradata Download Center — Several Teradata Tools and Utilities products can be downloaded from the Teradata Download Center, including:

• Teradata Call-Level Interface version 2 (CLIv2) — This product and its dependent products: Teradata Generic Security Services (TDGSS) Client, and the Shared ICU Libraries for Teradata, are available for download.

• ODBC Driver for Teradata (ODBC) — This product and its dependent products: Teradata Generic Security Services (TDGSS) Client, and the Shared ICU Libraries for Teradata, are available for download.

Additionally, three other products are available from the Teradata Download Center:

• Teradata Driver for the JDBC Interface. See “Installing the Teradata Driver for the JDBC Interface” on page 84.

• OLE DB Provider for Teradata. See “Installing the OLE DB Provider for Teradata from the Download Center” on page 85.

• .NET Data Provider for Teradata. See the .NET Data Provider for Teradata, Release Definition.

Installing Using PUT

Some of products can be installed using the software Teradata Parallel Upgrade Tool (PUT). Currently the following products are the only Teradata Tools and Utilities products that can be installed using the software Parallel Upgrade Tool (PUT) on Microsoft Windows:

• Basic Teradata Query (BTEQ)

• Named Pipes Access Module

• Shared ICU Libraries for Teradata



• Teradata Generic Security Services - Client

• FastExport

• FastLoad

• MultiLoad

• MQ Access Module

• TPump

To use PUT to install these products, refer to the Parallel Upgrade Tool (PUT) User Guide for Microsoft Windows.


Chapter 3: Installing the Teradata Tools and Utilities SoftwareInstalling Using the Client Main Install

Installing Using the Client Main Install

This section describes how to use the Client Main Install to install Teradata Tools and Utilities products.

Initial Procedure for Typical, Custom or Network Installations

Make sure you have the appropriate Teradata Tools and Utilities CDs. Tables in the “Installation Kit” section beginning on “Installation Kit” on page 31 show which applications are on each CD. The applications can be installed in any order:














• Query Director



Note: This manual does not describe how to install the OLE DB Provider software. Refer to the OLE DB Provider for Teradata Installation and User Guide.

Note: This installation guide does not describe how to install the Meta Data Services. For installation on how to install the Teradata Meta Data Services Installation and Administration Guide.

Note: This installation guide does not describe how to install the Teradata Query Director. For installation on how to install the Teradata Query Director User Guide.

Note: The figures shown in this document are examples only. Depending on the Teradata Tools and Utilities products used in your installation, some dialog boxes and screens might vary from those shown in this guide.

Setup Procedure

The setup procedure for installing the Teradata Tools and Utilities software on your computer is identical for the three types of installation.



Procedure - Beginning an Installation

Follow these steps to begin an installation:

1 Close all active Windows programs and disable any virus protection software running on the computer.

2 Since a “Typical” installation installs Teradata SQL Assistant/Web Edition software, if you haven’t already done so, before you go any further, go to “Installing Required Software for Teradata SQL Assistant/Web Edition” on page 52 and install the prerequisites described for Teradata SQL Assistant/Web Edition.

3 Insert the first Teradata Tools and Utilities CD into the CD drive. The applications can be installed in any order.

4 In the Welcome to Teradata Tools and Utilities dialog box, click Install Product.If the Welcome dialog box does not appear shortly after the CD is inserted, use Windows Explorer to navigate to the main folder of the CD. Double-click the setup.bat file to start the installation process.

5 In the Choose Setup Language dialog box, click the drop-down arrow and select the desired language from the list that appears, then click OK. English and Japanese are the only setup languages currently supported.

6 In the Welcome dialog box, click Next.7 In the Software License Agreement dialog box, read the agreement, then click Yes to accept

it.

8 In the Setup Type dialog box, click the name of the desired installation setup:

• A Typical setup installs all products from the CD. Highlight Typical, click Next, then go to “Typical Installation” on page 64 for further instructions.

• A Network setup copies the setup files for the products to a folder that you specify. The Network setup does not install the products; you must do this in a separate process. Highlight Network, click Next, then go to “Network Installation” on page 78 for further instructions.

• A Custom setup installs only those products selected from the CD. Highlight Custom, click Next, then go to “Custom Installation” on page 74 for further instructions.

Typical Installation

A typical installation installs all the products on each CD.

The screens shown in this section are examples of screens that appear during a Typical Installation. Depending on the Teradata Tools and Utilities products used in your installation, some dialog boxes and screens might vary from those shown in this guide.

Procedure - Performing a Typical Installation

Follow these steps to perform a typical installation of Teradata Tools and Utilities. This installation installs all the Teradata Tools and Utilities products.



1 After highlighting Typical and clicking Next in the initial Setup Type dialog box, the Choose Destination Location dialog box appears. If the default path shown in the Destination Folder block is acceptable, click Next. (This is recommended.)

Note: If you did not uninstall a previous version of the dependent products, you will be asked if you want to overwrite the software. Click Yes for the software you want to overwrite.

To use a destination location other than the default, click Browse, navigate to the location where you want the files installed, click OK, then click Next. Note: You must have write access to the destination folder, the Windows root folder, and the Windows system folder.

2 In the Select Install Method dialog box, select the products you want to be automatically installed (silent install), or clear the products you want to interactively install:

a Highlight the products to be installed silently.

Note: Shared ICU Libraries for Teradata can only be installed in silent mode from the CD media.

Note: The ODBC Driver for Teradata and Teradata Manager can be installed silently or interactively; the default for ODBC Driver for Teradata is silent; the default for Teradata Manager is silent. Upon completion of the Teradata Tools and Utilities installation in this section, complete these installations as described in the following sections:

“Installing the ODBC Driver for Teradata” on page 72

“Installing the Teradata Manager” on page 70



Note: Teradata SQL Assistant/Web Edition can only be installed interactively. Upon completion of the Teradata Tools and Utilities installation in this section, complete these installations as described in the following sections:

“Installing the Teradata SQL Assistant/Web Edition” on page 67

All other products can be installed silently or interactively; the default is silent.

b Those not highlighted will be installed interactively, meaning that the product setup sequence will be activated so you can make adjustments during installation.

c Click Next.

3 An Information window shows the path to the folder containing the product response files for silent installation. If you want to modify a product response file, use a text editor to do so now. When you are finished, click OK in the Information window.

Note: During installation, progress monitors will appear. No action is required.

4 In the Install Wizard Completion screen, click Finish to complete the installation.

Note: The ODBC Driver for Teradata Setup may take several minutes.

Troubleshooting Note: The product setup log is located in the %TEMP%\ ClientISS folder. “Silent Installation Result Codes” on page 156 lists result codes from silent installations that are useful for troubleshooting.

5 After the first phase of the installation is complete, go to the installation procedure for the following products as needed:

• “Installing the ODBC Driver for Teradata” on page 72

• “Installing the Teradata SQL Assistant/Web Edition” on page 67

• “Installing the Teradata MultiTool” on page 69



• “Installing the Teradata Manager” on page 70

Installing the Teradata SQL Assistant/Web Edition

Note: The Teradata SQL Assistant/Web Edition software is only installed from the Teradata Utility Pak CD.

This software will be installed in the following folder on the drive where the Microsoft Internet Information Services (IIS) was previously installed:

<Drive where IIS was installed>:\inetpub\wwwroot

Procedure - Installing the SQL Assistant/Web Edition

Follow these steps to install the Teradata SQL Assistant/Web Edition software interactively:

1 In the Welcome to the Teradata SQL Assistant/Web Edition Setup dialog box, click Next.

2 In the License Agreement dialog box, read the agreement, select I accept the terms in the license agreement, then click Next.

3 In the Select Installation Address dialog box, enter the appropriate virtual directory and port number, then click Next.

Virtual Directory Note: Do not enter a root directory in this text box.

The virtual directory is a pointer to the actual root directory. After you install the Teradata SQL Assistant/Web Edition software, the name entered as the virtual directory is the pathname used as a URL in the browser’s address bar when connecting to the Teradata Database.

For more information, refer to the Teradata SQL Assistant/Web Edition User Guide.

Port Note: Typically you would leave the port number at the default of 80.

This port number enables the system administrator to run several Web servers from the same host. For example, you might have a production Web server running on port 80 (the default) and a test Web server running on port 8080.

You can install the Teradata SQL Assistant/Web Edition software on the test Web server before installing it on the production Web server and releasing it to your general user population.

If you use 80 (the default), it is not necessary to include the port number in the URL.

The port number indicates where the Web server listens for connections from Web browsers.

If a user needs to connect to Teradata SQL Assistant/Web Edition on the test Web server, they must include the port number in the URL. For example, they might use http://myhost:8080/SQLAsssistantWeb.

Disk Cost If you click Disk Cost in the Select Installation Address dialog box, an information-only dialog box appears that shows how much disk space you have, how much disk space is available, and how much disk space is required for each available drive.



4 In the Confirm Installation dialog box, click Next. 5 You may see the following Information window. Click OK.

6 If the machine.config file could not be modified, you will receive the following warning. Click OK to continue the installation process.

7 In the Installation Complete dialog box, click Close.

8 If the machine.config file was not modified successfully above, refer to “Changing the machine.config File” on page 68 for instructions on how to change it manually.

Changing the machine.config File

The machine.config file is in your operating system folder. It was installed on your computer when you installed the “Installing Microsoft .NET Framework (version 1.1)” on page 54.

When using Teradata SQL Assistant/Web Edition, a query that takes longer to process than the time set in the responseDeadlockInterval attribute of the machine.config file is considered deadlocked and you are disconnected from the Teradata Database with an error message from your browser.

The default for responseDeadlockInterval is 00:03:00 (3 minutes).

The Teradata SQL Assistant/Web Edition installation attempts to access the machine.config file and change responseDeadlockInterval to “Infinite.” If the file modification was not successful above, your system administrator, or someone else who has write privileges to the machine.config file, must complete the following steps to modify this file:

Procedure - Changing the machine.config File

Follow these steps to change the machine.config file.

1 Use Notepad or another text editor to open the machine.config file at:

%SystemRoot%\Microsoft.NET\Framework\V1.0.3705\config

2 Locate the processModel tag shown in the figure below.



3 At responseDeadlockInterval, change the number in quotes to “Infinite.” (This is case sensitive so make sure you enter “Infinite” with a capital I.)

4 Save and close the machine.config file.

Installing the Teradata MultiTool

Note: When installing Teradata MultiTool:

• The Teradata MultiTool software is only installed from the Teradata Utility Pak.

• If you are installing Teradata MultiTool and you do not have the Java 2 Runtime Environment, install it when prompted to do so.

• Teradata MultiTool cannot be installed if Teradata Database is already installed. Teradata Database setup installs Teradata MultiTool.

To install the Teradata MultiTool software, your computer must run on the Windows 2000 or 32-bit Windows XP operating system. You cannot install it on a computer running on any other Windows operating system.

Procedure - Installing the Teradata MultiTool

Follow these steps to install the Teradata MultiTool:

1 Before you install Teradata MultiTool, you must download and install Java Runtime Environment (JRE) version 1.4 from the following website: http://java.sun.com/products/archive/j2se/1.4.0/index.html

2 In the Welcome to the InstallShield Wizard for Teradata MultiTool dialog box, click Next.







3 In the License Agreement dialog box, read the agreement, select I accept the terms in the license agreement, then click Next.

4 In the Customer Information dialog box, enter the appropriate information, then click Next.5 In the Setup Type dialog box, select Complete, then click Next.6 In the Ready to Install the Program dialog box, click Install.7 In the InstallShield Wizard Completed dialog box, click Finish.

Installing the Teradata Manager

The Teradata Manager software can only be installed from the Database Management CD.

Procedure - Installing Teradata Manager

Follow these steps to install the Teradata Manager:

1 In the Teradata Manager Setup Welcome dialog box, click Next.2 In the Software License Agreement dialog box, read the agreement, then click Yes to accept

it.

3 In the Choose Destination Location dialog box, if the default path shown in the Destination Folder block is acceptable, click Next. (This is recommended.)


4 In the Setup Type dialog box, highlight the desired option, then click Next.5 In the Select Program Folder dialog box, perform one of the following, then click Next:

• Accept the default program folder

• Enter a new folder name into the Program Folders text block

• Select one of the names in the list of existing folders

6 In the Start Copying Files dialog box, check the settings, then click Next to begin copying the files.

7 You may see a Question message box with text similar to the following:

Setup has found application settings from a previous release of Teradata Manager. Would you like to be able to use these settings?

To use the settings from a previous version, click Yes. You may need to update them to use new features.

If you do not want to use them, click No.

8 You will see one of two InstallShield Wizard Complete dialog boxes:

• If the Teradata Manager installation requires a restart, there will be no options in the dialog box, just click Finish.

• If no restart is required, you may view online Help or begin the Teradata Database setup program. Select the desired option, then click Finish.



If this is a new installation or this version of Teradata Manager has not been run before, you must perform the Teradata Database setup program to establish the appropriate database privileges to run certain applications.

Note: If it is necessary to run the Teradata Database setup program, you can do so now or after completing installation. Refer to the Teradata Manager User Guide, or the online Teradata Manager Help for more information.

Note: After the dbcmngr database is upgraded, only users of the newly installed version of Teradata Manager will be able to successfully execute all Teradata Manager applications. (The Teradata Database, Teradata Manager server, and Teradata Manager clients must have the same version of the dbcmngr database for certain applications, such as monitoring and alerting applications, to work correctly.)

The installation process continues, completing all silent installations.

Completing the Installation

Which Setup Complete dialog box appears next depends on whether the computer should be restarted.

Procedure - Completing the Installation

Follow these steps to complete the installation:

1 If the computer does not require a restart, choose whether or not to view the Release Definition, then click Finish.

2 If the computer does require a restart, you have two options:

• Yes, I want to restart my computer now. • No, I will restart my computer later. We recommend that you select Yes, I want to restart my computer now, remove the CD from the drive, then click Finish.

Troubleshooting Silent Installations

For help in troubleshooting problems during silent installation, refer to “Silent Installation Result Codes” on page 156.

Configuring the Products

Go to the following sections to configure the installed products:

• “Configuring Teradata Administrator” on page 87

• “Configuring the ODBC Driver, Teradata Query Scheduler, and Teradata Manager” on page 88

• “Configuring Teradata Call-Level Interface version 2 (CLIv2) for Windows” on page 89

• “Configuring Teradata Parallel Transporter” on page 94



Installing the ODBC Driver for Teradata

If an earlier version of the ODBC Driver for Teradata is installed on your system, uninstall it using Add/Remove Programs. You must be a member of the Windows Administrators group of the computer on which you are uninstalling the software.

The installation of an ODBC driver will terminate if an older driver is being installed on a system that has a newer ODBC driver installed.

When installing the ODBC Driver for Teradata product on a Windows XP 64-bit system, the install process hangs if all of the following conditions exist:

• The ODBC Driver for Teradata product is already on the system.

• You elect to do a custom install.

• You elect to install the product in silent mode, that is, you select “ODBC_Driver_For_Teradata” in the Select Install Methods dialog.

To prevent the install process from hanging, you must first uninstall all previous versions of the ODBC Driver for Teradata.

The Installation of the ODBC 12.00.00.00 release on a system that already has an ODBC Driver Installed will exhibit a different behavior than when the ODBC Driver for Teradata is installed on a system that has no ODBC Driver for Teradata installed.

In this case, only two dialog boxes are displayed, Resuming the InstallShield Wizard for ODBC Driver for Teradata, and the Installation Wizard Complete dialog boxes.

• When an installation is executed on a system that already has an ODBC Driver installed, Resuming the InstallShield Wizard for ODBC Driver for Teradata appears.

Click Next.• Installation Wizard Complete dialog box appears.

Click Finish.

Note: ODBC 12.00.00.00 is not supported on Microsoft Windows 95, Windows 98, or Windows NT. If you attempt to install ODBC 12.00.00.00 on one of these operating systems, the InstallShield program will detect the operating system and generate an error message indicating the incompatibility, then abort the installation.

Except on 64-bit systems, whenever ODBC is installed, version 2.8 of the Microsoft Data Access Components (MDAC) will also be installed. If MDAC is already installed on your computer and you do not want it upgraded to version 2.8, clear the MDAC check box in the Select Components dialog box. You must install MDAC version 2.8 if you will be using Teradata SQL Assistant/Web Edition.

Note: MDAC is not installed with 64-bit ODBC since it is installed as part of the operating system.

Note: To ensure the highest quality and best performance of the ODBC Driver for Teradata, the most recent critical post-production updates can be downloaded from the Teradata Software Server at:





Procedure - Installing from the Teradata Software Server

Follow these steps to install the ODBC Driver for Teradata from the Teradata Software Server:

1 In the Welcome to the InstallShield Wizard for ODBC Driver for Teradata dialog box, click Next. Note: If you are installing ODBC Driver for Teradata in interactive mode on a computer that runs on the Windows 2000 or Windows XP operating system and you don’t see the Welcome dialog box, press the Alt-Tab keys and bring the dialog box to the foreground. This does not apply to silent installation of this software.



3 In the Setup Type dialog box, click the name of the desired installation setup, then click Next:• Custom is for advanced users who want to choose the options to install.

• Typical is recommended for most users. All ODBC driver programs will be installed.

Note: If you choose Typical, the ODBC installation will also install version 2.8 of the Microsoft Data Access Components (MDAC). If MDAC is already installed on your computer and you do not want it upgraded to version 2.8, select Custom, then clear the MDAC check box in the Select Components dialog box as shown in the following figure.

If you are installing Teradata MultiTool and you do not have the Java 2 Runtime Environment, install it when prompted to do so.

Note: MDAC version 2.8 must be installed Teradata SQL Assistant/Web Edition will be used.



4 In the Select Program Folder dialog box, do one of the following, then click Next:• Accept the default program folder

• Enter a new folder name into the Program Folders text block

• Select one of the names in the list of existing folders

5 In the Start Copying Files dialog box, review the information. When you are satisfied that it is correct, click Next. The driver installation begins. During installation, progress monitors will appear. No action is required.

6 Upon completion of the driver installation, the InstallShield Wizard Complete dialog box appears. Choose to view the Read Me file, run the ODBC Administrator immediately, or do neither, then click Finish.

Note: Configuration Note: You must use the ODBC Administrator to configure the driver. Therefore, if you do not run the ODBC Administrator now, you must do so after completing the Teradata Tools and Utilities installation.

Refer to the configuration section of the ODBC Driver for Teradata User Guide.

Custom Installation

A custom installation installs only those products selected from the list of available products.

The screens shown in this section are examples of screens that appear during a Custom Installation. Depending on the Teradata Tools and Utilities products used in your installation, some dialog boxes and screens might vary from those shown in this guide.



Procedure - Performing a Custom Installation

Follow these steps to perform a custom installation of Teradata Tools and Utilities. Only those products selected will be installed.

1 After highlighting Custom and clicking Next in the initial Setup Type dialog box, the Select Components dialog box appears. Do the following:

a Select the check boxes for the products you want to install.

b Clear the check boxes for the products you do not want to install.

c Click Next. Note: If the product you select is dependent on other products, those will be selected also.

Table 1 on page 22 shows which Windows platforms are supported by each product. If you have questions about the interdependence of products, refer to “Software Requirements” on page 28.





3 In the Select Install Method dialog box, select automatic (silent) or interactive installation for each product.

a Highlight the products to be installed silently.

• Shared ICU Libraries for Teradata can only be installed in the silent mode from the CD media.

• The ODBC Driver for Teradata and Teradata Manager can be installed silently or interactively (the default is silent.) Upon completion of the Teradata Tools and Utilities installation in this section, complete these installations as described in the following sections:


• “Installing the Teradata Manager” on page 70

Teradata SQL Assistant/Web Edition, and Teradata Access Module for Tivoli can only be installed interactively. Upon completion of the Teradata Tools and Utilities installation in this section, complete these installations as described in the following sections:


All other products can be installed silently or interactively; the default is silent.

b The products not highlighted will be installed interactively, meaning that the product setup sequence will be activated so you can make adjustments during installation.

c Click Next.



4 An Information window shows the path to the folder containing the product response files for silent installation. If you want to modify a product response file, use a text editor to do so now. When you are finished, click OK in the Information window.

Installation Notes:

• During installation, progress monitors will appear. No action is required.

• For silent installations, messages such as “Installing BTEQ. Please wait...” will appear. No action is required.

• The Teradata ODBC Driver Setup may take several minutes.

Troubleshooting Notes:

• The product setup log is located in the %TEMP%\ ClientISS folder.

• “Silent Installation Result Codes” on page 156 lists result codes from silent installations that are useful for troubleshooting.

5 If you selected other products to install interactively, those setup programs will execute. Follow the instructions in each dialog box that appears. If you need more help during installation, refer to “Additional Information” on page 4 for a list of product documents.

6 After the first phase of the installation is complete, go to the installation procedure for the following products as needed:



• “Installing the Teradata MultiTool” on page 69

7 Which Setup Complete dialog box appears next depends on whether the computer should be restarted:

a If the computer does not require a restart, choose whether or not to view the Release Definition, then click Finish.



b If the computer does require a restart, you have two options:

• Yes, I want to restart my computer now. • No, I will restart my computer later.

We recommend that you select Yes, I want to restart my computer now, remove the CD from the drive, then click Finish.

Troubleshooting Silent Installations

For help in troubleshooting problems during silent installation, refer to “Silent Installation Result Codes” on page 156.







Network Installation

A network installation copies the setup files for the selected products to a specified folder. The network installation does not actually install the products. This must be done by the user.

The screens shown in this section are examples of screens that appear during a Network Installation. Depending on the Teradata Tools and Utilities products used in your installation, some dialog boxes and screens might vary from those shown in this guide.

Procedure - Performing a Network Installation

Follow these steps to perform a network installation of Teradata Tools and Utilities. This installation only copies the setup files of the selected products to a specified folder.

1 After highlighting Network and clicking Next in the initial Setup Type dialog box, the Select Components dialog box appears. Do the following:

a Select the boxes for the products whose setup files you want to copy.

b Clear the boxes for the products you do not want to copy.

c Click Next. Table 1 on page 22 shows which Windows platforms are supported by each product. If you have questions about interdependence of products, refer to “Software Requirements” on page 28.




To use a destination location other than the default, click Browse, navigate to the location where you want the files installed, click, then click Next. Note: You must have write access to the destination folder, the Windows root folder, and the Windows system folder.

3 As files are copied, progress monitors will appear. No action is required.


Chapter 3: Installing the Teradata Tools and Utilities SoftwareInstalling a Package from the Command Prompt

4 After the installation process copies the necessary files to the specified folder, the Setup Complete dialog box appears. Choose whether or not to view the Release Definition, then click Finish.

Installing the Products

After you have copied the product setup files to the desired folder, you can install the product from that location without a license file.







Installing a Package from the Command Prompt

This section documents the commands needed to install Windows packages silently from the command prompt. Packages can be downloaded from a patch server or copied using a Network Setup Type, then copied to the target machine.

A Package Folder sample installation is included.

Sample Package Folder Installation

This procedure installs the Teradata Performance Monitor using a package folder and a response file. The procedure installs the Teradata Performance Monitor silently.

Procedure - Installing Teradata Performance Monitor

Follow these steps to install Teradata Performance Monitor.

1 Exit all applications, including Microsoft Office and disable any virus protection software running on the system.

2 Copy the response file “Teradata_Performance_Monitor.iss” to your directory. For example:

Table 23: setup.exe

Product Setup File Name Location

All products setup.exe <folder name>\<product name>



C:\PACKAGE

Note: setup.exe must be in C:\PACKAGE, not C:\PACKAGE\DISK1.

3 Make any changes you need in the response file.

4 Copy the Package folder to your directory on your system. For example:

C:\PACKAGE

5 In the command prompt, change directory to:

C:\PACKAGE

6 At the command prompt, type the command:

setup.exe /s /f1"C:\PACKAGE\Teradata_Performance_Monitor.iss"

where C:\PACKAGE\Teradata_Performance_Monitor.iss is an example of how to specify the pathname of the response file.

Installation Commands

To silently install a Teradata Tools and Utilities product from the command prompt, first check Table 25 to determine whether the package has a response file. If it doesn’t have a response file, execute the command shown in the table in the directory where the products package file is located.

If it does, first copy the products package file and it’s response file to a temporary directory, and make the directory the current directory. Then execute the command for the product as shown in Table 25.

The following table includes the setup commands to perform a silent installation of Teradata Tools and Utilities products.

A typical command is:

setup.exe /s /f1<response file> /f2<setup log file>

where:

The values passed to f1 and f2 must be enclosed in double quotes. Other parameters can also be passed.

For example:

setup.exe /s /f1"C:\temp\setup.iss"

Table 24: setup.exe command parameters

Parameters... Description...

<response file> This is the full pathname of the response file input to setup.exe.

<setup log file> This is the full pathname of the log file output by setup.exe.

f1 parameter This is an optional parameter if the response file is in the current directory and the file is named setup.iss.

f2 parameter This is optional parameter. If it is not provided the log file will be created in the current directory as setup.log.



Note: There is no white space between the f1 switch and the pathname of the response file.

Table 25: Command Prompt Installation Command

Product... Commands...

Basic Teradata Query (BTEQ) At the command prompt, type the command:

setup.exe /s /f1"<response file>" /f2"<setup log file>"

ODBC Driver for Teradata At the command prompt, type the command:


To change the destination where the ODBC Driver for Teradata is loaded, change “szDir” in the ODBC_Driver_for_Teradata.iss file.

Shared ICU Libraries for Teradata At the command prompt, type the command:

setup.exe /s /f1"<response file>" /f2"<setup log file>" /w

Note: Shared ICU Libraries for Teradata can only be installed in the silent mode.

Teradata Access Module for JMS At the command prompt, type the command:


Teradata Access Module for Tivoli At the command prompt, type the command:


Teradata Administrator At the command prompt, type the command:

setup.exe /s /v"/qn"

Teradata Archive and Recovery (ARC)

At the command prompt, type the command:


Teradata C Preprocessor2 At the command prompt, type the command:


Teradata Call Level Interface version 2 (CLIv2)



Teradata Data Connector At the command prompt, type the command:


Teradata Dynamic Workload Manager



Teradata FastExport At the command prompt, type the command:


Teradata FastLoad At the command prompt, type the command:


Teradata Generic Security Services


Setup.exe /s /v"/qn"

Teradata Index Wizard At the command prompt, type the command:




Teradata Manager At the command prompt, type the command:


Note: The default setup type is Client. For Server setup enter:

edit TMgr.iss

then find the line:

Result=ClientSetupType

and change it to:

Result=ServerSetupType

Teradata MultiLoad At the command prompt, type the command:


Teradata Named Pipes Access Module



Teradata OLE DB Access Module At the command prompt, type the command:


• Teradata Parallel Transporter ICU Library



Teradata Performance Monitor At the command prompt, type the command:


Teradata Query Director At the command prompt, type the command:





Teradata Query Scheduler Client At the command prompt, type the command:


Teradata Query Scheduler Server At the command prompt, type the command:


Teradata SQL Assistant At the command prompt, type the command:


without test database:

Setup.exe /s /v"/qn TESTDBSSELECTED=0"




Teradata Statistics Wizard At the command prompt, type the command:


Table 25: Command Prompt Installation Command (continued)



Chapter 3: Installing the Teradata Tools and Utilities SoftwareInstalling the Teradata Driver for the JDBC Interface







Installing the Teradata Driver for the JDBC Interface

The Teradata Driver for the JDBC Interface must be downloaded from the Teradata Download Center at:


The files can be copied into a directory of your choice and are machine independent.

For configuration instructions go to “Importing the SQL Package and Loading the Teradata Driver for the JDBC Interface” in chapter 2 of the Teradata Driver for the JDBC Interface User Guide.

Teradata System Emulation Tool At the command prompt, type the command:


Teradata TPump At the command prompt, type the command:


Teradata Visual Explain At the command prompt, type the command:


Teradata Workload Analyzer At the command prompt, type the command:


Websphere Access Module for Teradata



Websphere MQ Access Module At the command prompt, type the command:


Web Tools At the command prompt, type the command:

setup.exe /s /v"/qn"

Table 25: Command Prompt Installation Command (continued)





Chapter 3: Installing the Teradata Tools and Utilities SoftwareInstalling the OLE DB Provider for Teradata from the Download Center

Note: It is recommended, but not required, that any previous release of the Teradata Driver for the JDBC Interface be uninstalled prior to downloading and using this release of the Teradata Driver for the JDBC Interface.

Installing the OLE DB Provider for Teradata from the Download Center

The OLE DB Provider for Teradata must be downloaded from the Teradata Download Center at:


See the OLE DB Provider for Teradata Installation and User Guide for information and procedures for installing the OLE DB Provider and its dependent products from the Download Center.




Chapter 3: Installing the Teradata Tools and Utilities SoftwareInstalling the OLE DB Provider for Teradata from the Download Center


CHAPTER 4

Configuring the Teradata Tools andUtilities Software

This chapter describes how to configure the Teradata Tools and Utilities software.

• Configuring Teradata Administrator

• Configuring the ODBC Driver, Teradata Query Scheduler, and Teradata Manager

• Configuring Teradata Call-Level Interface version 2 (CLIv2) for Windows

• Configuring Teradata Parallel Transporter

Configuring Teradata Administrator

After installation, the Teradata Administrator should be configured to include the Teradata user name.

Procedure - Configuring the Teradata Administrator

Follow these steps to configure the Teradata Administrator.

1 Go to <Boot Drive>:\Program Files\NCR\Teradata Administrator 12.0\ sql

2 Open setup.sql

3 Use the Edit/Replace menu to change all occurrences of the string <User> to the Teradata user name.

4 Execute the query.


Chapter 4: Configuring the Teradata Tools and Utilities SoftwareConfiguring the ODBC Driver, Teradata Query Scheduler, and Teradata Manager

Configuring the ODBC Driver, Teradata Query Scheduler, and Teradata Manager

After installation, configure those of the following products that you have installed:

Table 26: Configuring ODBC, Teradata Query Scheduler and Teradata Manager

To configure... Do the following...

ODBC Driver for Teradata If you have not already done so, use the ODBC Administrator to configure the driver.

For more information, refer to the:

ODBC Driver for Teradata User Guide


To use the Teradata Query Scheduler Administrator, you must first configure a Teradata Director Program ID (TDPID) name for accessing the desired Teradata Database.

For more information, refer to:

Teradata Query Scheduler Administrator Guide

Teradata Query Scheduler Client

For information on configuring the Teradata Query Scheduler Client refer to the:

Teradata Query Scheduler User Guide

Teradata Query Scheduler Server

To start the Teradata Query Scheduler Server, you must first configure a Teradata Director Program ID (TDPID) name.

For more information, refer to:

Teradata Query Scheduler User Guide

Teradata Manager If you have not already done so, and this is a new or upgraded Teradata Manager installation, use the Teradata Database setup program to create a Teradata Database user with appropriate database privileges to run the Teradata Manager applications. Also, configure the Teradata Manager Service according to “Defining System Parameters.”

For more information, refer to the:

Teradata Manager User Guide

or

to the online Teradata Manager Help


Chapter 4: Configuring the Teradata Tools and Utilities SoftwareConfiguring Teradata Call-Level Interface version 2 (CLIv2) for Windows

Configuring Teradata Call-Level Interface version 2 (CLIv2) for Windows

The following sections outline the steps required for setting the Teradata Call-Level Interface version 2 for Windows network, environment, and system parameters:

• Setting the correct network parameters will guarantee that the Teradata Call-Level Interface version 2 for Windows will communicate with your target Teradata Database. These parameters must be set correctly to use the software.

• The environment parameters provide the Teradata Call-Level Interface version 2 for Windows with parameter file location information, as well as the facility for enabling CLIv2 to run in parallel mode. Setting the environment parameters is highly recommended.

• The CLIv2 system parameters are used internally by the Call-Level Interface to customize services and features. Setting system parameters is necessary only if you have special requirements that the default setting cannot meet.

Setting Network Parameters

The Internet address and the symbolic names for the Teradata Database are considered the network parameters. This section assumes that your network software is installed correctly.

hosts File

If you are not running a Name Server, the hosts file contains a list of all systems on the LAN that you can access. The Teradata Database must be identified in this file if a system is going to communicate with it. A hosts file exists on each individual computer system in your network.

If you are running a Name Server, make sure the hosts file is on the Name Server and that your network software is configured to access the Name Server. The Teradata Tools and Utilities software uses generic TCP/IP GetHostByName services.

The hosts file is in the <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter folder.

Identifying a Teradata Database

To identify the Teradata Database, add an entry to the hosts file for each TCP/IP Communications Processor (COP), Applications Processor (AP), or UNIX node running the Teradata Gateway that your computer will be communicating with.

Table 27: Adding an Entry to the hosts File

To communicate with a... Add entries corresponding to the...

Teradata Database on an AP platform (System 3600) APs

Teradata Database on a V2 Computer (UNIX) nodes



Note: Throughout this manual, “AP” refers to the following: TCP/IP Communications Processor (COP), Applications Processor (AP), and the node running the Teradata Gateway.

Syntax

Use the following syntax when adding entries to the hosts file:

<a.b.c.d > <dbcnameCOPn> [aliasCOPn]

where:

Table 28: hosts File Syntax

Parameter... is...

a.b.c.d the Internet address. It is a four-byte numeric value that identifies an “AP” and its location on the network. An Internet address is assigned to each “AP” when the Teradata Database is configured.

dbcname the Teradata Database using the “AP.” It is 1 to 8 characters in length. The first character must be alphabetic; the remaining characters can be alphanumeric.

The System Parameter Block file, <Boot Drive>:\Program Files\ NCR\Teradata Client\clispb.dat, lists dbc as the default dbcname. You can assign dbc as the dbcname of a Teradata Database with which your computer communicates. This simplifies network debugging and avoids problems when name servers become available.

If your computer communicates with more than one Teradata Database on the same TCP/IP LAN, you should use dbc as the dbcname for the more heavily used Teradata Database. Any other name(s) can be used for the remaining Teradata Database(s).

COPn the parameter that assigns a number to a particular “AP” that the Teradata Database uses. COP is a fixed string of characters that you must always specify. The value of n can range from 1 to the total number of “APs” in a COP group.

A COP group is a set of “APs” that will operate together for a particular Teradata Database. “APs” in the same COP group share session balancing and session recovery. Each “AP” within a COP group must be assigned a unique number starting with 1.

aliasCOPn the aliasname, specifying an alternate name for a Teradata Database “AP”. Its use is optional. More than one aliasname is permitted. An aliasname need not be unique across a network, but the hosts file for a computer must not contain the same aliasname for more than one “AP”. Suggestion: the n in each aliasCOPn equal n in the corresponding dbcnameCOPn.



Example

A computer accesses one Teradata Database (named dbc) through two TCP/IP APs with addresses 101.0.0.21 and 101.0.0.22 on the same logical TCP/IP LAN. Each AP is assigned two alias names.

In this case, add these lines to the hosts file:

101.0.0.21 dbcnode1 dbccop1 ncrcop1101.0.0.22 dbcnode2 dbccop2 ncrcop2

Setting Environment Parameters

The environment parameters allow you to specify the runtime environment for each user who will be using the Teradata Tools and Utilities software.

On Windows systems, if system environment parameters are changed, the computer must be rebooted for the changes to take effect. It is not enough to restart your daemon, nor logoff and log on again.

Defining Paths to System Files

You can define the path to the CLIv2 system parameter block file and the anomaly log file by setting the following environment parameters:

Setting the Environment Variables on Windows XP, 2000 and 2003

Use the information in the following table to set the Environment Parameters.

Note: If COPLIB is not specified when the Teradata Tools and Utilities applications are started, the current working folder will be used to find the system parameter block file (.\clispb.dat). If COPANOMLOG is not specified, no anomaly log file will be created.

Table 29: Environment Parameters

Parameter... defines...

COPLIB the path to the CLIv2 system parameter block file, clispb.dat.

COPANOMLOG the path to the anomaly log file, a trace log file displaying CLIv2 activities, including network-related error information. This environment variable should be defined only for debugging purposes.

Table 30: Setting Environment Parameters

To set environment parameters in... go to...

Windows 2000 Start > Control Panel > System, then select the Advanced tab, then click on Environment Variables.

Windows XP or Windows Server 2003 Start > Control Panel > System, then select the Advanced tab, then click on Environment Variables.



Speeding Up the Logon Process

The speed of the logon process can be increased by limiting the number of GetHostByName requests issued by the Teradata Tools and Utilities applications. This is done by setting an environment variable with the name equal to the machine name with a specified number of COPS available for it, as follows:

set <machine_name>=<cops>

where:

Example:

set SHOGUN=3

This will cause CLIv2 to issue GetHostByName for SHOGUNCOP1, SHOGUNCOP2, and SHOGUNCOP3 only. If one of the GetHostByName requests fails, the successive requests will not be issued.

Setting the Port Number

You can specify the port number used by the Teradata Tools and Utilities software by setting the environment variable TDMSTPORT as follows:

set TDMSTPORT=<nnnn>

where:

Table 31: Logon Parameters

Parameter... is...

machine_name the name of the machine.

cops the number of COPS.

Table 32: Setting <machine name>




Table 33: Port Number Parameters

Parameter... is...

nnnn the port number.



NETRACE - Enabling Detailed COPANOMLOG Logging

Setting NETRACE=1 enables detailed network information between the client and the Teradata server. This information is logged into the file defined in the environmental setting COPANOMLOG.

THREADLOGGING - Enabling Multiple COPANOMLOG File Creation

Threadlogging supports multi-threaded Windows applications. Multi-threaded logging is enabled by setting THREADLOGGING=1.

For example, if COPANOMLOG is “c:\temp\coplog” and THREADLOGGING is enabled, logs will be created as c:\temp\coplog0.txt, c:\temp\coplog1.txt, and so on through c:\temp\coplogn.txt. Each thread that uses a CLI connection will create its own individual log file.

Setting System Parameters

The clispb.dat file (the CLIv2 System Parameter Block) contains default values for variables used by CLI application programs. In clispb.dat, the Teradata Database sets the initial values to duplicate the CLIv2 internal defaults.

You can edit the clispb.dat file to meet your site’s most common requirements. Refer to the Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems for more information.

Adding CLI User Exit Functions

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

Procedure - Adding User Exit Functions

Use the following steps to install CLI User Exit functions.

1 Use the following command to set your folder to the folder where the tdusr32.mak file was installed. The default folder is <Boot Drive>:\ Program Files\NCR\Teradata\cli\UserExit.

cd "c:\Progam Files\NCR\Teradata\cli\UserExit"

Table 34: Setting TDMSTPORT





Chapter 4: Configuring the Teradata Tools and Utilities SoftwareConfiguring Teradata Parallel Transporter

2 Modify the CliLgnEx.c or CliPPS.c file in the UserExit folder.

3 Modify the CliLgnEx.c or CliPPS.c file in the UserExit folder.

4 Compile and link using the make facility:

nmake -f userexit.mak CFG="tdusr32 - Win32 Release"

The following configurations are supported:

• tdusr32 - Win32 Release

• tdusr32 - Win32 Debug

The 64-bit configurations must use the correct environment for 64-bit development.

5 Move the tdusr32.dll file into the appropriate folder. This library is by default installed into the %SystemRoot%\system32 folder.

For more information on CLI User Exit Functions, see the:

Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems, Appendix D.

Configuring Teradata Parallel Transporter

After the Teradata Parallel Transporter has been installed, the following file usually requires modification:

• the local configuration file: twbcfg.ini

The file is located in the <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version> folder.

Changing the twbcfg.ini File

After the Teradata Parallel Transporter Infrastructure package is installed, you may edit the configuration file, <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\twbcfg.ini. The configuration file contains default directory for checkpoint and logs.

You can use an editor to modify the configuration file.

You would want to modify the Teradata Parallel Transporter configuration file, if you want to change the checkpoint or logs directory.

No reboot is required after making the change in the configuration file.

An example of the Teradata Parallel Transporter configuration file is shown here:

CheckpointDirectory='C:\Program Files\NCR\Teradata Parallel Transporter\12.0\checkpoint' LogDirectory='C:\Program Files\NCR\Teradata Parallel Transporter\12.0\logs'

CheckpointDirectory refers to the folder that contains the checkpoint files for Teradata Parallel Transporter jobs.



LogDirectory refers to the folder that contains the binary logs for Teradata Parallel Transporter jobs. Each Teradata Parallel Transporter job creates a job log in the jobs directory.

Note: If you change the folder for the LogDirectory and you have the Teradata Parallel Transporter Wizard installed, you must change the LOG_DIRECTORY entry in the %TWB_ROOT%\tptwizard\config\tptwizard.properties file before you run Teradata Parallel Transporter Wizard. %TWB_ROOT% is the system environment variable that holds the value for the Teradata Parallel Transporter installation folder.

For example, if you change the folder for the LogDirectory to C:\Logs\Teradata Parallel Transporter 12.0 and you have the Teradata Parallel Transporter Wizard installed, use the following procedures to update the LOG_DIRECTORY entry in the %TWB_ROOT%\tptwizard\config\tptwizard.properties file

Procedure - Updating the LOG_DIRECTORY

Use the following steps to update the LOG_DIRECTORY.

1 Use an editor (for example, NOTEPAD) to open the tptwizard.properties file in the %TWB_ROOT%\tptwizard\config folder.

2 Update the LOG_DIRECTORY line to this:

LOG_DIRECTORY=C:\\Logs\\Teradata Parallel Transporter 12.00.00\\

3 Save the change.

4 Quit the editor.

The C:\Logs\Teradata Parallel Transporter 12.00.00.00 folder is used as an example. You can use a different folder.

The folder for the LOG_DIRECTORY entry in the tptwizard.properties file must be separated by double backslash “\\” and must end with double backslash “\\”.

Refer to the Teradata Parallel Transporter Reference manual on how to read the job log.

Switching Teradata Parallel Transporter Software Versions

After Teradata Parallel Transporter software is installed, the system is setup to run the installed version of the Teradata Parallel Transporter in the next new window of the MS-DOS Command Prompt.

Determining the Current Teradata Parallel Transporter Version

To find out which version of Teradata Parallel Transporter is currently running on the system, run “tbuild” with no options in a new window of the MS-DOS Command Prompt.

For example:

C:\> tbuildTeradata Parallel Transporter Run Utility Version 12.00.00.



Switching to Teradata Warehouse Builder Version 4.1 or Earlier

If Teradata Warehouse Builder version 4.1 or earlier is installed, you can switch to this version using the following procedure:

Procedure - Switching to Teradata Warehouse Builder Version 4.1 or Earlier

Follow these steps to switch to Teradata Warehouse Builder version 4.1 or earlier.

1 Go to Start > Settings > Control Panel > System

2 In the System Properties dialog box, click on the Advanced tab.

3 In the Advanced tab, click on the Environment Variables button.

4 Make a copy of the system TWB_ROOT environment variable.

5 Delete the system TWB_ROOT environment variable.

6 Click on the OK button.

7 Click on the OK button again.

8 Bring up a new window of the MS-DOS Command Prompt.

The system should be running version 4.1 or earlier of Teradata Warehouse Builder.

Switching Back to the Installed Teradata Parallel Transporter

If the system is running a previous version of the Teradata Parallel Transporter or Teradata Warehouse Builder, use the following procedure to switch to the current version of Teradata Parallel Transporter.

Procedure - Switching Back to the Installed Teradata Parallel Transporter

Follow these steps to switch back to the installed Teradata Parallel Transporter version.




4 Create a new system TWB_ROOT environment variable and set the value to the installed Teradata Parallel Transporter installation folder.

If you made a copy of the system TWB_ROOT environment variable, the value of the copied TWB_ROOT environment variable is the installation folder of the installed Teradata Parallel Transporter.

If you do not know the installation folder of the installed Teradata Parallel Transporter, look at the INSTALLBASE name in the HKEY_LOCAL_MACHINE\SOFTWARE\NCR\Teradata Parallel Transporter Infrastructure 12.0 registry key. The value for the INSTALLBASE name is the installation folder of the installed Teradata Parallel Transporter.






The system will switch back to Teradata Parallel Transporter version 12.0.

Switching to Teradata Warehouse Builder Version 5.0

If Teradata Warehouse Builder 5.0 is installed, use the following procedures to switch to the 5.0 version of Teradata Warehouse Builder:

Procedure - Switching to Teradata Warehouse Builder Version 5.0

Follow these steps to switch to Teradata Warehouse Builder version 5.0.




4 Create a new system TWB_ROOT environment variable and set the value to the installed Teradata Warehouse Builder 5.0 installation folder. If you do not know the installation folder of the Teradata Warehouse Builder 5.0 version, look at the INSTALLBASE name in the HKEY_LOCAL_MACHINE\SOFTWARE\NCR\Teradata Warehouse Builder 5.0 registry key. The value for the INSTALLBASE name is the installation folder of the Teradata Warehouse Builder 5.0 version.




The system should be running version 5.0 of Teradata Warehouse Builder.

User Environment Variables

If the TWB_ROOT user environment variable is used, it is recommended that you delete it before running a Teradata Parallel Transporter job.

Note: Both 32-bit and 64-bit versions of the Teradata Parallel Transporter Operator Support Library can be installed on a 64-bit Windows machine. If both versions of this package are installed on a 64-bit machine, then the TWB_ROOT, _MSGCATLOCATION, and PATH environment variables include the directories of the most recently installed version of the Teradata Parallel Transporter Operator Support Library.

Procedure - Deleting the TWB_ROOT Variable

Follow these steps to delete the TWB_ROOT user variable.






4 Highlight the TWB_ROOT variable in the User variables section and click on the Delete button.



System Environment Variable ORACLE_HOME

The Teradata Parallel Transporter Wizard requires that the ORACLE_HOME system environment variable point to folder where the Oracle client version of software used by the Teradata Parallel Transporter Wizard is located.

Uninstalling Teradata Parallel Transporter

Use the following procedure to uninstall Teradata Parallel Transporter.

Procedure - Uninstalling Teradata Parallel Transporter

Follow these steps to uninstall Teradata Parallel Transporter.


2 In the Add/Remove Programs dialog box, click Change or Remove Programs.

3 Following the order that the “Order to Remove Teradata Parallel Transporter Software” section describes, highlight a Teradata Parallel Transporter software, then click Add/Remove.

4 Confirm the action and, if necessary, follow the instructions presented in the Uninstall Wizard.

Order to Remove Teradata Parallel Transporter Software

Remove these software first, in any order:

• Teradata Parallel Transporter ODBC Operator <version>

• Teradata Parallel Transporter Data Connector Operator <version>

• Teradata Parallel Transporter DDL Operator <version>

• Teradata Parallel Transporter OS Command Operator <version>

• Teradata Parallel Transporter SQL Inserter Operator <version>

• Teradata Parallel Transporter SQL Selector Operator <version>

• Teradata Parallel Transporter Wizard <version>

• Teradata Parallel Transporter API <version>

Remove these software next, in any order:

• Teradata Parallel Transporter Export Operator <version>

• Teradata Parallel Transporter Load Operator <version>

• Teradata Parallel Transporter Stream Operator <version>



• Teradata Parallel Transporter Update Operator <version>

• Teradata Parallel Transporter Operator Support Library <version>

• Teradata Parallel Transporter Infrastructure <version>

• Teradata Parallel Transporter ICU Library<version>

Configuring Teradata Access Module for JMS

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 folder for Teradata Access Module for JMS is <Boot Drive>:\Program Files\Common Files\NCR\JMSAXSMOD. Use an editor, like Notepad, to open the readme file.


CHAPTER 5

Verifying the Installation

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

• Verifying ODBC Driver for Teradata

• Verifying Shared ICU Libraries for Teradata

• Verifying Teradata Access Module for JMS

• Verifying Teradata Access Module for Tivoli

• Verifying Teradata Archive/Recovery Utility (ARC)

• Verifying Teradata C Preprocessor2

• Verifying Teradata Call-Level Interface version 2 (CLIv2)

• Verifying Teradata Data Connector

• Verifying Teradata Driver for the JDBC Interface

• Verifying Teradata Dynamic Workload Manager

• Verifying Teradata FastExport

• Verifying Teradata FastLoad

• Verifying Teradata MultiLoad

• Verifying Teradata MultiTool

• Verifying Teradata OLE DB Access Module

• Verifying Teradata Parallel Transporter API

• Verifying Teradata Parallel Transporter Infrastructure

• Verifying Teradata Parallel Transporter Data Connector Operator

• Verifying Teradata Parallel Transporter DDL Operator

• Verifying Teradata Parallel Transporter Export Operator

• Verifying Teradata Parallel Transporter ICU Library

• Verifying Teradata Parallel Transporter Load Operator

• Verifying Teradata Parallel Transporter ODBC Operator

• Verifying Teradata Parallel Transporter Operator Support Library

• Verifying Teradata Parallel Transporter OS Command Operator

• Verifying Teradata Parallel Transporter SQL Inserter Operator


Chapter 5: Verifying the Installation

• Verifying Teradata Parallel Transporter SQL Selector Operator

• Verifying Teradata Parallel Transporter Stream Operator

• Verifying Teradata Parallel Transporter Update Operator

• Verifying Teradata Parallel Transporter Wizard

• Verifying Teradata Query Scheduler Administrator

• Verifying Teradata Query Scheduler Client

• Verifying Teradata Query Scheduler Server

• Verifying Teradata TPump

• Verifying WebSphere MQ Access Module

• Verifying Teradata Workload Analyzer

• Verifying the Installation Using the CLI Sample Program, clisamp


Chapter 5: Verifying the InstallationVerifying the Installation of Individual Products

Verifying the Installation of Individual Products

After installing Teradata Tools and Utilities, the installation of individual products can be verified.

Procedure - Verifying Installation of Individual Products

Follow these steps to verify the installation of individual products.

1 Check that the directories specified in the tables below have been installed.

2 Check that the files specified in the tables below have been installed.

Verifying Basic Teradata Query (BTEQ)

Table 35: Basic Teradata Query (BTEQ) Files 32-bit Platforms

BTEQ for Windows 32-bit platforms

File Type File Name Default Folder

Executable bteq.exe

bteqwin.exe

<Boot Drive>:\Program Files\NCR\Teradata Client\bin

Help bteqwin_enu.cnt

bteqwin_enu.hlp

bteqwin_jpn.cnt

bteqwin_jpn.hlp


Icon teqtalk.ico <Boot Drive>:\Program Files\NCR\Teradata Client\bin

Library bteqwin_jpn.dll

mgrcli.dll

mgrcli_jpn.dll

ncrtmgr.dll

ncrtmgr_jpn.dll

printman.dll

tdis.dll

tm_dialogs.dll

tm_dialogs_jpn.dll

tm_stat.dll

tm_stat_jpn.dll




Verifying Named Pipes Access Module

Verifying ODBC Driver for Teradata

Library caputl.dll

mfc71.dll

mfc71u.dll

msvcr71.dll

%SystemRoot%\system32

Sample btnfyext.c

btnfyext.def

btnfyext.h

btnfyext.mak

<Boot Drive>:\Program Files\NCR\Teradata Client\btnfy

Table 35: Basic Teradata Query (BTEQ) Files 32-bit Platforms (continued)

BTEQ for Windows 32-bit platforms

Table 36: Named Pipes Access Module 32-bit Files

Named Pipes Access Module for Windows 32-bit platforms


Library np_AXSMOD.dll

np_AXSMODenu.dll

np_AXSMODTWB.dll

np_AXSMODenuTWB.dll


Table 37: ODBC Driver for Teradata 32-bit Files

ODBC Driver for Teradata for Windows 32-bit platforms


_unodbc.dll

Pbocd0x0.txt

Readme.txt

<Boot Drive>:\Program Files\NCR\ODBC Driver for Teradata



Verifying Shared ICU Libraries for Teradata

Table 38: ODBC Driver for Teradata 64-bit Files

ODBC Driver for Teradata for Windows 64-bit platforms


_unodbc.dll

Pbocd0x0.txt

Readme.txt

<Boot Drive>:\Program Files\NCR\ODBC Driver for Teradata

Table 39: Share ICU Libraries for Teradata 32-bit Files

Shared ICU Libraries for Teradata for Windows 32-bit platforms


Dynamic Link Library icudttd341.dll

icuintd34.dll

icuiotd34.dll

iculetd34.dll

iculxtd34.dll

icuuctd34.dll

MSVCR71.DLL

MSVCP71.DLL

%ProgramFiles\NCR\Common Files\Shared ICU Libraries for Teradata\lib



Verifying Teradata Access Module for JMS

Verifying Teradata Access Module for Tivoli

Table 40: Shared ICU Libraries for Teradata 64-bit Files

Shared ICU Libraries for Teradata for Windows 64-bit platforms


Dynamic Link Library icudttd281.dll

icuintd28.dll

icuiotd28.dll

iculetd28.dll

iculxtd28.dll

icuuctd28.dll

%ProgramFiles\NCR\Common Files\Shared ICU Libraries for Teradata\lib

Table 41: Teradata Access Module for JMS Files

Teradata Access Module for JMS for Windows 32-bit platforms


Dynamic Link Library libjmsam.dll <Boot Drive>:\Program Files\Common Files\NCR\JMSAXSMOD

Readme readme <Boot Drive>:\Program Files\Common Files\NCR\JMSAXSMOD

Class Receiver.class <Boot Drive>:\Program Files\Common Files\NCR\JMSAXSMOD

Table 42: Teradata Access Module for Tivoli Files

Teradata Access Module for Tivoli for Windows 32-bit platforms


Executable TDDSNC.EXE <Boot Drive>:\Program Files\NCR\Teradata Client\bin

Library TIVBAR.DLL <Boot Drive>:\Program Files\NCR\Teradata Client\bin

Help ARCDFLT.TXT

TIVDFLT.TXT

Tivoli.Readme.TXT


Configuration TIVARC.BATTIVADM.BAT <Boot Drive>:\Program Files\NCR\Teradata Client\TDBAR

Working Files temporary and diagnostic files

<Boot Drive>:\TDBAR



Verifying Teradata Archive/Recovery Utility (ARC)

Verifying Teradata C Preprocessor2

Verifying Teradata Call-Level Interface version 2 (CLIv2)

Table 43: Teradata Archive/Recovery Utility (ARC) 32-bit Files

Teradata Archive/Recovery Utility (ARC) for Windows 32-bit platforms


Executable arcmain.exe <Boot Drive>:\Program Files\NCR\Teradata Client\bin

Table 44: Teradata C Preprocessor2 32-bit and 64-bit Files

Teradata C Preprocessor2 for Windows 32-bit and 64-bit platforms


Executable ppcmain.exe <Boot Drive>:\Program Files\NCR\Teradata Client\bin

Library ppruntim.dll <Boot Drive>:\Program Files\NCR\Teradata Client\pp2

Library ppruntim.lib <Boot Drive>:\Program Files\NCR\Teradata Client\pp2

Sample LABSBTEQ

PPCLB1

PPCLB2

PPCLB3

PPCLB4

PPCLB5

PPCLB6

PPCLB7

PPCLB8

PPCLB9

<Boot Drive>:\Program Files\NCR\Teradata Client\pp2

Table 45: Teradata Call-Level Interface version 2 (CLIv2), 32-bit Files

CLIv2 for Windows 32-bit platforms


CLI Data clispb.dat <Boot Drive>:\Program Files\NCR\Teradata Client\cliv2

clisamp clisamp.c

makesamp.win




Include cliv2if.h

coperr.h

coptypes.h

dbcacnx.h

dbcarea.h

dbcerr.h

dbchqep.h

mosiif.h

nojunk.h

parcel.h

resource.h

wincliv2.h

<Boot Drive>:\Program Files\NCR\Teradata Client\cliv2\inc

Library tdusr32.lib

wincli32.lib

<Boot Drive>:\Program Files\NCR\Teradata Client\cliv2\lib

User Exit CliLgnEx.c

CliPPS.c

tdusr.def

tdusr.rc

userexit.mak

<Boot Drive>:\Program Files\NCR\Teradata Client\cliv2\UserExit

Dynamic Link Library wincli32.dll

tdusr32.dll

terasso.dll

localisation.dll


Table 45: Teradata Call-Level Interface version 2 (CLIv2), 32-bit Files (continued)


Table 46: Teradata Call-Level Interface version 2 (CLIv2), 64-bit Files



CLI Data clispb.dat <Boot Drive>:\Program Files\NCR\Teradata Client\cliv2

clisamp clisamp.c

makesamp.win




Verifying Teradata Data Connector

Include cliv2if.h

coperr.h

coptypes.h

dbcacnx.h

dbcarea.h

dbcerr.h

dbchqep.h

mosiif.h

nojunk.h

parcel.h

resource.h

wincliv2.h

<Boot Drive>:\Program Files\NCR\Teradata Client\cliv2\inc

Library tdusr32.lib

wincli32.lib

<Boot Drive>:\Program Files\NCR\Teradata Client\cliv2\lib

User Exit CliLgnEx.c

CliPPS.c

tdusr.def

tdusr.rc

userexit.mak

<Boot Drive>:\Program Files\NCR\Teradata Client\cliv2\UserExit

Dynamic Link Library wincli32.dll

tdusr32.dll

terasso.dll

localisation.dll


Table 46: Teradata Call-Level Interface version 2 (CLIv2), 64-bit Files (continued)


Table 47: Teradata Data Connector 32-bit Files

Teradata Data Connector for Windows 32-bit and 64-bit platforms


Header pmdcomt.h

pmddamt.h


Library libpm.dll %SystemRoot%\system32



Verifying Teradata Driver for the JDBC Interface

Verifying Teradata Dynamic Workload Manager

Table 48: Teradata Data Connector 64-bit Files

Teradata Data Connector for Windows 64-bit platforms


Header pmdcomt.h

pmddamt.h


Library libpm.dll %SystemRoot%\system32

Table 49: Teradata Driver for the JDBC Interface

Teradata Driver for the JDBC Interfaces for Windows 32-bit and 64-bit platforms


Executable terajdbc4.jar user selectable

Sample samples.jar user selectable

Security tdgssjava.jar

tdgssconfig.jar

user selectable

Table 50: Teradata Dynamic Workload Manager Files

Teradata Dynamic Workload Manager for Windows 32-bit platforms


Executable tdwm.exe

mpsfs.exe

Verify.exe

verify.dat

<Boot Drive>:\Program Files\NCR\Teradata Dynamic Workload Manager 12.0



Verifying Teradata FastExport

Verifying Teradata FastLoad

Library FPSpread.dll

mfc71.dll

mfc71u.dll

mgrcli.dll

monpm.dll

msvcr71.dll

msvcr80.dll

ncrtmgr.dll

psload.dll

tdapp.dll

tdis.dll

tdmfcis.dll

tdwmutil.dll

tm_dialogs.dll

<Boot Drive>:\Program Files\NCR\Teradata Dynamic Workload Manager 12.0

Table 50: Teradata Dynamic Workload Manager Files (continued)

Teradata Dynamic Workload Manager for Windows 32-bit platforms

Table 51: Teradata FastExport 32-bit Files

Teradata FastExport for Windows 32-bit platforms


Executable fexp.exe <Boot Drive>:\Program Files\NCR\Teradata Client\bin

Sample feimod.c

fenotf.c

feomod.c

<Boot Drive>:\Program Files\NCR\Teradata Client\fexp

Table 52: Teradata FastLoad 32-bit Files

Teradata FastLoad for Windows 32-bit platforms


Executable fastload.exe <Boot Drive>:\Program Files\NCR\Teradata Client\bin



Verifying Teradata MultiLoad

Verifying Teradata MultiTool

Sample blkexit.c

blkexit.mak

blkexitr.c

flnfyext.c

<Boot Drive>:\Program Files\NCR\Teradata Client\fastload

Table 52: Teradata FastLoad 32-bit Files (continued)

Teradata FastLoad for Windows 32-bit platforms

Table 53: Teradata MultiLoad 32-bit Files

Teradata MultiLoad for Windows 32-bit platforms


Executable mload.exe <Boot Drive>:\Program Files\NCR\Teradata Client\bin

Sample mlimod.c

mlnotf.c

<Boot Drive>:\Program Files\NCR\Teradata Client\mload

Table 54: Teradata MultiTool 32-bit Files

Teradata MultiTool for Windows 32-bit platforms


Classes jhall.jar

pdecui.jar

sfc.jar

symbeans.jar

<Boot Drive>:\Program Files\NCR\Teradata MultiTool

Executable cnstool.exe

winjavaloader.exe


Library libnetpde.dll

msvcrtd.dll


Miscellaneous td.ico

version.txt


Shortcut MultiTool <Boot Drive>:\Program Files\NCR\Teradata MultiTool



Verifying Teradata OLE DB Access Module

Verifying Teradata Parallel Transporter API

Table 55: Teradata OLE DB Access Module 32-bit Files

Teradata OLE DB Access Module for Windows 32-bit platforms


Executable oleload.exe <Boot Drive>:\Program Files\NCR\Teradata Client\bin

Library msvcr71.dll

OLEDB_AXSMOD.dll

OLEDB_AXSMODenu.dll

OLEDB_AXSMODjpn.dll

Uninst.dll

<Boot Drive>:\Program Files\Common Files\NCR\AXSMOD

Help OLEDB_AXSMODenu.cnt

OLEDB_AXSMODENU.hlp

OLEDB_AXSMODjpn.cnt

OLEDB_AXSMODJPN.hlp


Icon program.ico <Boot Drive>:\Program Files\Common Files\NCR\AXSMOD

Online Help Online Help files <Boot Drive>:\Program Files\Common Files\NCR\AXSMOD\ Teradata OLE DB Access Module Help

Table 56: 32-bit Teradata Parallel Transporter API

API: Windows 32-bit platforms


Library telapi.dll

telapi.lib

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Header DMLGroup.h

Schema.h

Connection.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\inc

Header generic.h <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\generic\inc

Header BlockLoad.h <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\blockloading\inc

Header MultipleOperators.h <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\multiple\inc



Header fileio.h

multitest.h

synchronize.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\multi_node\inc

Header checkpoint.h <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\checkpoint\inc

Header common.h

Mutex.h

PerfTestMessage.h

TestBase.h

TestExport.h

TestLoad.h

TestSim.h

TestStream.h

TestUpdate.h

ThreadTest.h

ThreadTestParameters.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\threads\inc

Header DMLGroup.h

Schema.h

Connection.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\inc

Header OptionsManager.cpp

OptionsManager.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\common

Header checkpoint.cpp

main.cpp

input.txt

infile.littleEndian

checkpoint.vcproj

checkpoint.sln

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\checkpoint

Table 56: 32-bit Teradata Parallel Transporter API (continued)




Header GenericDriver.cpp

main.cpp

input.txt

infile.littleEndian

generic.vcproj

generic.sln

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\generic

Header BlockLoad.cpp

main.cpp

input.txt

infile.littleEndian

blockload.vcproj

blockload.sln

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\blockloading

Header multitest.cpp

synchronize.cpp

fileio.cpp

master.cpp

slave.cpp

master_input.txt

slave_input.txt

infilemaster.littleEndian

infileslave.littleEndian.1

multinode.sln

masternode.vcproj

slavenode.vcproj

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\multi_node





Header PerfTestMessage.cpp

TelapiThreadTest.cpp

PerfTestMessage.cpp

TelapiThreadTest.sln

TelapiThreadTest.vcproj

TestBase.cpp

TestExport.cpp

TestLoad.cpp

TestSim.cpp

TestStream.cpp

TestUpdate.cpp

ThreadTest.cpp

ThreadTestParameters.cpp

Synchronizer.cpp

input.txt

loadData.littleEndian

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\threads

Get Buffer GetBuffer.cpp

main.cpp

cleanupTables.bteq

setupTables.bteq

getbuffer.sln

getbuffer.vcproj

input.txt

$INSTALLDIR/tptapi/sample/getbuffer

Include GetBuffer.h $INSTALLDIR/tptapi/sample/getbuffer/inc





XSP GenericDriver.cpp

GenericDriver.h

OptionsReader.cpp

OptionsReader.h

xsp.cpp

xsp.sln

xsp.vcproj

input.exp

input.lod

input.stm

input.upd

infile.littleEndian

$INSTALLDIR/tptapi/sample/xsp



Table 57: 64-bit Teradata Parallel Transporter API



Library telapi.dll

telapi.lib

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin64

Header DMLGroup.h

Schema.h

Connection.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\inc

Header generic.h <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\generic\inc

Header BlockLoad.h <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\blockloading\inc

Header MultipleOperators.h <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\multiple\inc

Header fileio.h

multitest.h

synchronize.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\multi_node\inc

Header checkpoint.h <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\checkpoint\inc



Header common.h

Mutex.h

PerfTestMessage.h

TestBase.h

TestExport.h

TestLoad.h

TestSim.h

TestStream.h

TestUpdate.h

ThreadTest.h

ThreadTestParameters.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\threads\inc

Header DMLGroup.h

Schema.h

Connection.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\inc

Header OptionsManager.cpp

OptionsManager.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\common

Header checkpoint.cpp

main.cpp

input.txt

infile.littleEndian

checkpoint64.vcproj

checkpoint64.sln

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\checkpoint

Header GenericDriver.cpp

main.cpp

input.txt

infile.littleEndian

generic64.vcproj

generic64.sln

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\generic





Header BlockLoad.cpp

main.cpp

input.txt

infile.littleEndian

blockload64.vcproj

blockload64.sln

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\blockloading

Header multitest.cpp

synchronize.cpp

fileio.cpp

master.cpp

slave.cpp

master_input.txt

slave_input.txt

infilemaster.littleEndian

infileslave.littleEndian.1

multinode64.sln

masternode64.vcproj

slavenode64.vcproj

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\multi_node





Header PerfTestMessage.cpp

TelapiThreadTest.cpp

PerfTestMessage.cpp

TelapiThreadTest64.sln

TelapiThreadTest64.vcproj

TestBase.cpp

TestExport.cpp

TestLoad.cpp

TestSim.cpp

TestStream.cpp

TestUpdate.cpp

ThreadTest.cpp

ThreadTestParameters.cpp

Synchronizer.cpp

input.txt

loadData.littleEndian

cleanupTables.bteq

setupTables.bteq

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptapi\sample\threads

Get Buffer GetBuffer.cpp

main.cpp

cleanupTables.bteq

setupTables.bteq

getbuffer64.sln

getbuffer.64vcproj

input.txt

$INSTALLDIR/tptapi/sample/getbuffer

Include GetBuffer.h $INSTALLDIR/tptapi/sample/getbuffer/inc





Verifying Teradata Parallel Transporter Data Connector Operator

Verifying Teradata Parallel Transporter DDL Operator

XSP GenericDriver.cpp

GenericDriver.h

OptionsReader.cpp

OptionsReader.h

xsp.cpp

xsp64.sln

xsp64.vcproj

input.exp

input.lod

input.stm

input.upd

infile.littleEndian

$INSTALLDIR/tptapi/sample/xsp



Table 58: Teradata Parallel Transporter Data Connector Operator

DataConnector Operator: Windows 32-bit platforms


Library dataconop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Uninstall UninstDataConnectorOp12.0.isu

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>

Table 59: Teradata Parallel Transporter DDL Operator

DDL Operator: Windows 32-bit platforms


Library ddlop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Uninstall UninstDDLOp12.0.isu <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>



Verifying Teradata Parallel Transporter Export Operator

Verifying Teradata Parallel Transporter ICU Library

Table 60: 32-bit Teradata Parallel Transporter Export Operator

Export Operator: Windows 32-bit platforms


Library exportop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Sample expnfyxt.c <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample

Table 61: 64-bit Teradata Parallel Transporter Export Operator

Export Operator: Windows 64-bit platforms


Library exportop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin64

Sample expnfyxt.c <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample

Table 62: 32-bit Teradata Parallel Transporter ICU Library Files

ICU Library: Windows 32-bit platforms


Library pxicu.dll

msvcp71.dll

msvcr71.dll


Table 63: 64-bit Teradata Parallel Transporter ICU Library Files

ICU Library: Windows 64-bit platforms


Library pxicu.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin64



Verifying Teradata Parallel Transporter Infrastructure

Table 64: Teradata Parallel Transporter Infrastructure Files

Teradata Parallel Transporter Infrastructure: Windows 32-bit platforms


Configuration twbcfg.ini

twboper.ini


Folder checkpoint

logs


Executable coordinator.exe

executor.exe

planexecutor.exe

tbuild.exe

ptmgts.exe

ptmjlgr.exe

ptmlvs.exe

ptmexec.exe

ptmtims.exe

tlogview.exe

twbstat.exe

twbkill.exe

tbuildexe.exe

tlogviewexe.exe

twbcmdexe.exe

twbkillexe.exe

twbstatexe.exe

twbrmcpexe.exe

twbpathexe.exe

tptlaunch.exe

twbpath.exe

twbrmcp.exe




Header pxdtypes.h

pxtypes.h

pxmacros.h

pxoper.h

pxos.h

pxstc.h

pxdef.h

pxlogdef.h

pxutypes.h

pxversion.h

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sdk\inc

Library feomop.dll

flimop.dll

logview.dll

mlimop.dll

msvcirt.dll

msvcirtd.dll

msvcp60.dll

msvcp60d.dll

msvcp71.dll

msvcr71.dll

msvcrt.dll

msvcrtd.dll

oncrpc.dll

pxcommon.dll

ptmin.dll

ptmos.dll

ptmpi.dll

ptmpo.dll


Message Catalog twbmsgs.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\msg

Table 64: Teradata Parallel Transporter Infrastructure Files (continued)




Verifying Teradata Parallel Transporter Load Operator

Sample GT11.txt

GT44.txt

GT62.txt

GT93.txt

GT94.txt

GT95.txt

GT96.txt

GT97.txt

jobvars.txt

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample\etl

Sample sampleoperator.dsw

sampleoperator.dsp

samplefilter.cpp

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sdk\src

Sample data.in

samplescript.txt

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sdk\sample

Sample sql1.txt

sql2.txt

twb_status.txt

twb_targets.txt

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample\metadata

Uninstall uninst.dll

UninstTTPTInfrastructure12.0.isu


Version Text version <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>

Word Document readme.doc <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sdk

Table 64: Teradata Parallel Transporter Infrastructure Files (continued)


Table 65: 32-bit Teradata Parallel Transporter Load Operator

Load Operator: Windows 32-bit platforms


Library loadop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Sample ldnfyext.c <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample



Verifying Teradata Parallel Transporter ODBC Operator

Verifying Teradata Parallel Transporter Operator Support Library

Table 66: 64-bit Teradata Parallel Transporter Load Operator

Load Operator: Windows 64-bit platforms


Library loadop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin64

Sample ldnfyext.c <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample

Table 67: Teradata Parallel Transporter ODBC Operator

Teradata Parallel Transporter ODBC Operator: Windows 32-bit platforms


Library odbcop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Uninstall UninstODBCOp12.0.isu <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>

Table 68: 32-bit Teradata Parallel Transporter Operator Support Library

Operator Support Library: Windows 32-bit platforms


Library opcommon.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Message Catalog opermsgs.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\msg

Table 69: 64-bit Teradata Parallel Transporter Operator Support Library

Operator Support Library: Windows 64-bit platforms


Library opcommon.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin64

Message Catalog opermsgs.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\msg64



Verifying Teradata Parallel Transporter OS Command Operator

Verifying Teradata Parallel Transporter SQL Inserter Operator

Verifying Teradata Parallel Transporter SQL Selector Operator

Table 70: Teradata Parallel Transporter OS Command Operator

OS Command Operator: Windows 32-bit platforms


Library oscmdop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Uninstall UninstOSCmdOp12.0.isu <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>

Table 71: Teradata Parallel Transporter SQL Inserter Operator

SQL Inserter Operator: Windows 32-bit platforms


Library insertop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Uninstall UninstInsertOp12.0.isu <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>

Table 72: Teradata Parallel Transporter SQL Selector Operator

SQL Selector Operator: Windows 32-bit platforms


Library selectop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Uninstall UninstSelectOp12.0.isu <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>



Verifying Teradata Parallel Transporter Stream Operator

Verifying Teradata Parallel Transporter Update Operator

Table 73: 32-bit Teradata Parallel Transporter Stream Operator

Stream Operator: Windows 32-bit platforms


Library streamop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Sample stmnfyxt.c <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample

Table 74: 64-bit Teradata Parallel Transporter Stream Operator

Stream Operator: Windows 64-bit platforms


Library streamop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin64

Sample stmnfyxt.c <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample

Table 75: 32-bit Teradata Parallel Transporter Update Operator

Update Operator: Windows 32-bit platforms


Library updateop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin

Sample updnfyxt.c <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample

Table 76: 64-bit Teradata Parallel Transporter Update Operator

Update Operator: Windows 64-bit platforms


Library updateop.dll <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\bin64

Sample updnfyxt.c <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\sample



Verifying Teradata Parallel Transporter Wizard

Table 77: Teradata Parallel Transporter Wizard

Teradata Parallel Transporter Wizard: Windows 32-bit platforms


Configuration tptwizard.properties <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptwizard\config

Directory jre

help

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptwizard

Java Binary tdgssjava.jar

terajdbc4.jar

tptwizard.jar

tdgssconfig.jar

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptwizard\jars

Icon tptwizard.ico <Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptwizard

Library guisrv.dll

wwhelp.dll


Startup runtbuild.cmd

tptwizard.cmd


Transformation attributes.twb.xsl

base.twb.xsl

columns.twb.xsl

dbms.twb.xsl

file.twb.xsl

job.twb.xsl

jobstep.twb.xsl

logger.twb.xsl

logview.twb.xsl

objects.twb.xsl

operation.twb.xsl

operator.twb.xsl

schema.twb.xsl

table.twb.xsl

tableset.twb.xsl

<Boot Drive>:\Program Files\NCR\Teradata Parallel Transporter\<version>\tptwizard\transformation

Uninstall UninstTPTWizard12.0.isu




Verifying Teradata Query Scheduler Administrator

Verifying Teradata Query Scheduler Client

Verifying Teradata Query Scheduler Server

Table 78: Teradata Query Scheduler Administrator 32-bit Files

Teradata Query Scheduler Administrator for Windows 32-bit platforms


Executable tdqsadm.exe

tdqmdb.exe

<Program Files>\NCR\Teradata Query Scheduler Admin 12.00.00(Program Files can be configured by the system administrator to be on a drive other than the boot drive.)

Readme readme.txt <Program Files>\NCR\Teradata Query Scheduler Admin 12.00.00

Table 79: Teradata Query Scheduler Client 32-bit Files

Teradata Query Scheduler Client for Windows 32-bit platforms


Executable tdqmcomm.exe

tdqmops.exe

tdqmview.exe

<Boot Drive>:\Program Files\NCR\Teradata Query Scheduler\client

Library tdqmcomm.dll

tdqmsr.dll

tdqmsubm.dll


Readme readme.txt <Boot Drive>:\Program Files\NCR\Teradata Query Scheduler\client

Table 80: Teradata Query Scheduler Server 32-bit Files

Teradata Query Scheduler Server for Windows 32-bit platforms


Executable tdqmjob.exe

tdqmlsnr.exe

tdqmreqp.exe

tdqmserv.exe

<Boot Drive>:\Program Files\NCR\Teradata Query Scheduler\server

Library tdqmserv.dll

tdsqlprs.dll




Verifying Teradata TPump

Verifying WebSphere MQ Access Module

Verifying Teradata Workload Analyzer

Parser sqlprs.dfa

sqlprs.llr

<Boot Drive>:\Program Files\NCR\Teradata Query Scheduler\server

Table 80: Teradata Query Scheduler Server 32-bit Files (continued)

Teradata Query Scheduler Server for Windows 32-bit platforms

Table 81: Teradata TPump 32-bit Files

Teradata TPump for Windows 32-bit platforms


Executable tpump.exe <Boot Drive>:\Program Files\NCR\Teradata Client\bin

Sample tdatpump.cfg

tldnfyxt.c

tpumpar.csql

tpumpimd.c

<Boot Drive>:\Program Files\NCR\Teradata Client\tpump

Table 82: WebSphere MQ Access Module

WebSphere MQ Access Module for Windows 32-bit platforms


Library libmqs.dll

libmqsc.dll

libmqsTWB.dll

libmqscTWB.dll


Table 83: Teradata Workload Analyzer Files

Teradata Workload Analyzer for Windows 32-bit platforms


Executable twa.exe

Verify.exe

verify.dat

<Boot Drive>:\Program Files\NCR\Teradata Workload Analyzer 12.0


Chapter 5: Verifying the InstallationVerifying the Installation Using the CLI Sample Program, clisamp

Verifying the Installation Using the CLI Sample Program, clisamp

Another way to verify that you have installed the software properly is to run the sample CLI application, clisamp. The program and its makefile were copied over during installation of the software. Perform the following steps to verify the installation:

1 Modify the makefile makesamp.win with the correct paths to the include files. By default the makesamp.win file is located in:

<Boot Drive>:\ Program Files\NCR\Teradata Client\cli\clisamp.

2 Execute the makefile to create the executable module clisamp:

# nmake -f makesamp.win

The default configuration is CFG=“clisamp - Win32 Debug.” Other supported configurations are “clisamp - Win32 Release” and the 64-bit configurations “clisamp - Win32 IA64Release” and “clisamp - Win32 IA64Debug.” The 64-bit configurations must use the correct environment for 64-bit development.

3 Execute the sample program by entering one of the following commands at the command prompt (change to the appropriate folder first: Release, Debug, IA64Release, or IA64Debug):

To run the sample program using the default logon information (dbc/systemfe,service) enter:

# clisamp

Library fspread.dll

mfc71.dll

mfc71u.dll

mgrcli.dll

monpm.dll

msvcp71.dll

msvcr80.dll

ncrtmgr.dll

psload.dll

tdapp.dll

tdis.dll

tdmfcis.dll

tdwmutil.dll

tm_dialogs.dll

<Boot Drive>:\Program Files\NCR\Teradata Workload Analyzer 12.0

Table 83: Teradata Workload Analyzer Files (continued)

Teradata Workload Analyzer for Windows 32-bit platforms



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

4 The program will log on to the default dbccop1 (no user input supplied) specified in the hosts file and execute a simple query - “SELECT * from dbc.sessioninfo;” and write the output to DAT clisamp.dat file. A display similar to the following appears:

# clisampCLIv2 version is 12.00.00.00MTDP version is 12.00.00.00MOSIOS version is 12.00.00.00MOSIDEP version is 12.00.00.00OSERR version is 12.00.00.00Logging on to --->dbc/systemfe,servicewriting out to--> CLISAMP.DATsubmitting -->select* from dbc.sessioninfo;writing out to --> CLISAMP.DATLogging off.


CHAPTER 6

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 used in your installation, some dialogs might vary from those shown in this guide.

The section topics are:

• Making the Database Connection

• Connecting in GUI Applications

• Connecting in Command Line Driven Applications

• Connecting to a Teradata Database Programmatically

• Logon Error Messages

Making the Database Connection

This section describes:

• how to connect to a Teradata Database from a GUI application.

• how to connect to a Teradata Database from a command line application.

• where to find the information to programmatically connect to a Teradata Database.

For programmatic interfaces, the User or Reference guide for the specific product provides information about the product interface.

Overview of Logon Procedures

You can provide the logon string while logging on to a Teradata Database if the application allows it. If the application does not provide all the logon information, a Connect to Teradata Database dialog will be displayed that allows you to enter the missing logon information.

Note: If the environment variable GUILOGON is set to NO, the Connect to Teradata Database dialog box will not be displayed, allowing the application to log on to the Teradata Database without prompting for the password.

If the Connect to Teradata Database dialog is displayed, all application-provided parameters are automatically entered into the dialog fields. If the information is incorrect, you can change the value entered in any field. After entering required and optional logon information press Enter or click OK to continue logging on.


Chapter 6: Connecting to a Teradata DatabaseMaking the Database Connection

The user logon exit routine can be used to manipulate the fields of the Connect to Teradata Database dialog.

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 your product User or Reference guide for specific information about an individual product.

Procedure - Connect to a Teradata Database

To connect to a Teradata Database, perform the following procedure:

1 If the application you are trying to connect to the database has a Connectivity tab in the Tools options menu, select WinCLI or ODBC.

2 Click the Connect button. The Connect to Teradata Database dialog appears.

3 Select or enter the appropriate values for the database to which you are connecting.

4 Click OK.

Connect to Teradata Database Dialog

The following figure shows the Connect to Teradata Database dialog:

Figure 1: Typical Connect to Teradata Database Dialog



The fields in the Connect to Teradata Database dialog are:

Note: Even though the UserId and Password parameters are required to log on to the Teradata Database, you do not have to enter them in the Connect to Teradata Database dialog box since they will be filled in by the user logon exit routine.

Field Name Definition

Database Name (Required) Enter a valid Teradata Database name, or you can also select a Teradata Database Name that you 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 your system administrator from the list of authentication mechanisms provided in the drop down list. The Authentication Mechanism identifies the mechanism used for connections to the data source.

Valid authentication mechanism values are:

• Empty - If no Authentication Mechanism is listed in the drop down list, or if the Authentication Mechanism selected is not supported, the mechanism used is the system default.

• TD1 - Teradata 1 mechanism.


• ldap - ldap mechanism.

• KRB5 - Kerberos mechanism.

• KRB5C - Kerberos Compatibility mechanism.

• NTLM - NT LAN Manager mechanism.

• NTLMC - NT LAN Manager Compatibility mechanism.

• Other - user-defined mechanism.

Authentication Parameter

(Optional) Enter the parameters required by the selected authentication mechanism. See your System Administrator.

User Name (Required) Select your user name from the drop down list, or enter a valid user name.

Password (Required) Enter your Password for the user name you entered.

Default Database (Optional) Select the default database for the session.

Account String (Optional) Enter a new Account String or select an account string from the drop down list.

The Account String is used to create a user in a Teradata Database, instead of providing account information during configuration of ODBC. It allows Teradata to isolate users, to find out what applications users are running, or to restrict users trying to connect to the database.



Connecting in Command Line Driven Applications

This section describes how to connect to a Teradata Database from the command line.

Procedure - Connecting in Command Line Driven Applications

Follow these steps to connect to a Teradata Database from the command line.

1 Enter the .logmech command.

2 Enter the .logdata command.

3 Enter the .logon command.

.logmech Command

The .logmech command identifies the desired logon authentication mechanism (logmech_name_string). The logmech_name_string is limited to 8 bytes and is not case-sensitive.

The syntax for the .logmech command is:

.logmech logmech_name_string

The logmech_name_string supports the following values

• None - If no Authentication Mechanism is entered, or if the Authentication Mechanism selected is not supported, the system will default to TD2.



• LDAP - ldap mechanism.

• KRB5 - Kerberos mechanism.

• KRB5C - Kerberos Compatibility mechanism.

• NTLM - NT LAN Manager mechanism.

• NTLMC - NT LAN Manager Compatibility mechanism.

.logdata Command

To successfully authenticate the user, the .logdata command provides all the parameters needed by the authentication mechanism, other than a UserId and Password. The information is entered into and passed by the logdata_string. The logdata_string is limited to 64K bytes.

The syntax for the .logdata command is:

.logdata logdata_string;

If the logdata_string has white space characters or the other special characters embedded, the entire logdata string must be delimited with single quotes:

.logdata ‘logdata_string’;

The exact contents of the logdata_string will vary according to the selected authentication mechanism. The string is not displayed, parsed, nor otherwise processed by the application.



.logon Command

The syntax for the .logon command is:

.logon <DBCName></><UserId><,><Password><,><AccountId>

Example Logons from the Command Line

Supported Mechanisms

In general, mechanisms which perform authentication and validation do not require that a Teradata Database Username and Password be included as part of the logon string. If these items are provided in conjunction with an authentication mechanism, they are ignored.

The following 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 user’s identity has been verified by Kerberos, an implicit logon will proceed using the tendered UserId as the Teradata Username:

.logmech KRB5

.logdata joe@domain1@@mypassword

.logon mydbs/

For single-Domain environments, the gateway can be configured so that the Domain or Realm do not need to be supplied:

.logmech KRB5

.logdata joe@@mypassword

.logon mydbs/

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.



Alternatively, a Kerberos-mediated SSO-style logon can be used by omitting either the UserId, Password and a Domain or a Realm. In this case, Kerberos uses the security credentials associated with the current client session:

.logmech KRB5

.logon mydbs/

If required, Teradata accounting information may be included as part of .logon command as follows:

.logmech KRB5


.logon mydbs/,,2345889909

or

.logmech KRB5



or

.logmech KRB5


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

The KRB5C mechanism is maintained for compatibility purposes with Teradata Tools and Utilities 8.1 communicating with a pre-V2R6 Teradata Database that supports SSO and logon encryption. It should not generally be specified.

The teraSSO library will automatically determine the appropriate authentication mechanism when interfacing to such a Teradata Database using the same logic as employed in Teradata Tools and Utilities 7.1.

• Windows clients should use NTLMC or KRB5C for SSO.

• For non-SSO, Windows clients use TD1.

• Non-Windows clients should use TD1.

In the event a user manually selects an incompatible mechanism, TERASSO_SECPKGMATCH_FAIL will be returned.

NTLM

The NTLM authentication mechanism should be used in Windows-to-Windows environments only. You can provide a UserId, Password, and Domain. Once the user’s identity has been verified by NTLM, an implicit logon will proceed using the tendered UserId as the Teradata Username.

.logmech NTLM



.logdata joe@domain1@@mypasswordjoe

.logon mydbs/

For single-Domain environments, the gateway can be configured so that the Domain or Realm need not be indicated:

.logmech NTLM

.logdata joe@@mypasswordjoe

.logon mydbs/

Alternatively, an NTLM-mediated SSO-style logon can be used by omitting the UserId, Domain, and Password, or omitting the UserId, Password, and either the Domain or the Realm.

In this second case, NTLM uses the security credentials associated with the current client session:

.logmech NTLM

.logon mydbs/

If required, you can include Teradata accounting information as part of .logon command as follows:

.logmech NTLM



or

.logmech NTLM



or

.logmech NTLM


In all of the above cases, a Teradata Username defined in the target Teradata Database must exist. The Username must match the actual or derived UserId and must have previously been granted the “logon with null password privilege. “

Note: The special “dbc” username cannot be used with the NTLM authentication mechanism since “dbc” cannot be granted the “logon with null password privilege.” If “dbc” is passed as the username, the Teradata Database will return error 3790.

For compatibility purposes, this is equivalent to the existing SSO feature. The existing third-party sign-on variant of SSO (NTLM only) is supported for compatibility purposes. However, it is recommended that new applications should use the logmech_name, logmech_data_ptr, and logmech_data_len fields in DBCAREA instead.

NTLMC

The NTLMC authentication mechanism is maintained for compatibility purposes only for Teradata Tools and Utilities 8.1 communication with a pre-V2R6 Teradata Database that supports SSO and logon encryption. You should not generally specify the NTLMC authentication mechanism.



The teraSSO library automatically determines the appropriate mechanism when interfacing to a Teradata Database, and uses the same logic as employed in Teradata Tools and Utilities 7.1.


• For non-SSO, Windows clients should use TD1.

• Non-Windows clients should use TD1.


LDAP

The LDAP authentication mechanism allows a user to be authenticated via LDAP and, optionally, to assume a role or user identity other than his or her own, as allowed by the appropriate directory settings.

The user may supply a UserId, Password, and Domain or Realm. The exact contents of the LDAP .logdata information necessarily depends largely upon how the site is using LDAP, and how LDAP has been configured. The samples below are generic examples. Once the user’s identity has been verified by LDAP, an implicit logon will proceed using the UserId as the Teradata username:

.logmech LDAP

.logdata domain7authcid=joe password=password real=myrealm

.logon mydbs/joe,password

If required, Teradata accounting information may be included as part of .logon command as follows:

.logmech LDAP

.logdata authcid=joe password=password real=myrealm


If the directory maps the UserId to a specific Teradata Username, that Username must be defined in the target Teradata Database and must have previously been granted the “logon with null password privilege.”

Once the user’s identity has been verified by LDAP, an implicit logon will proceed using the tendered UserId as the Teradata Username.

Note: The special “dbc” Username cannot be used with the LDAP authentication mechanism since “dbc” cannot be granted the “logon with null password privilege.” If “dbc” is used as the username, the Teradata Database will return error 3790.

If the directory does not map the UserId to a specific Teradata Username, a generic username will be used and a role assigned. The role will be derived from information contained in the directory. Logon will be by extended logon.

.logdata information must always be provided for the LDAP authentication mechanism.

TD1 and TD2

TD1 and TD2 represent the Teradata mechanisms. They do not perform any authentication. Rather, they facilitate encryption/decryption for sessions connected absent the mediation of extended security. Therefore, a valid Teradata Username and Password are always required.



• Only TD1 is used by Teradata Tools and Utilities 7.1.

• TD2 is used by Teradata Tools and Utilities 8.0 and later for the V2R6.0 Teradata Database and later.

• TD1 is used by Teradata Tools and Utilities 8.0 and above for the V2R5.1 Teradata Database.

The difference between the two mechanisms is that the encryption key for TD2 is longer and, therefore, offers a higher degree of security than that of TD1. For TD2, there should be no .logdata parameter; if one is passed to CLIv2, it will be ignored.

TD2 is the default mechanism for the server-based XML configuration file:

.logmech TD2

.logon mydbs/rhh,password

TD1

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.


• For non-SSO, Windows clients should use TD1.




Single Sign-On Legacy Considerations

In order to provide backward compatibility with pre-Teradata Tools and Utilities 8.0 applications which use SSO, the following items will apply:

Type Description

Direct sign-on If you do not supply a Username and Password as part of the Teradata logon string,

AND

no authentication mechanism name is specified in .logmech, the client interface will not use the default mechanism.

Rather, it will first determine if the Kerberos mechanism is available. If the Kerberos authentication mechanism is available, the client interface will use it.

If the Kerberos interface is not available, the client interface will next determine if the NTLM authentication mechanism is available. If the NTLM authentication mechanism is available, it will use it.

If neither the NTLM nor the Kerberos authentication mechanism is available, the logon attempt will fail.

If .logmech is specified, and the authentication mechanism turns out to be different from the one automatically determined by the client interface, an error will be returned.

Third-party sign-on If an application uses the programmatic third-party sign-on capability using the CLIv2 DBCAREA extension

AND

no authentication mechanism name is specified in logmech_name, the client interface will not use the default authentication mechanism.

Rather, the client interface will first determine if the Kerberos authentication mechanism is available. If the Kerberos authentication mechanism is available, the client interface will use it.

If the Kerberos authentication mechanism is not available, the client interface will next determine if the NTLM authentication mechanism is available. If the NTLM authentication mechanism is available, it will use it.

If neither the NTLM nor the Kerberos authentication method is available, the logon attempt will fail.

If .logmech is specified, and the authentication mechanism turns out to be different from the one automatically determined by the client interface, an error will be returned.



Connecting to a Teradata Database Programmatically

Several Teradata Tools and Utilities products allow you to programmatically connect to the Teradata Database using SQL and APIs.

Product Document

ODBC Driver for Teradata ODBC Driver for Teradata User Guide.

Describes SQL Connect, SQLDriverConnect, and SQLBrowseConnect and the parameters implemented for security. Includes information on configuring the ODBC Driver for Teradata.

OLE DB Provider for Teradata OLE DB Provider for Teradata Installation and User Guide.

Describes the security implemented for the OLE DB Provider for Teradata.


Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems.

Describes the CLI APIs implemented for security.

Teradata Driver for the JDBC Interface Teradata Driver for the JDBC Interface User Guide.

Describes the security methods implemented for the type 4 driver and illustrates how to connect to the Teradata Database using the Teradata Driver for the JDBC Interface.



Logon Error Messages

The following error messages apply to the logon and database connection function:

Authentication Mechanism Connection Error

If there is an error in the authentication mechanism selected, “External authentication is not currently allowed” may appear.

If you receive this message, you have selected an incorrect authentication mechanism. Reselect it using the authentication mechanism provided to you by you database administrator and try to connect again.

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.

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.


CHAPTER 7

Troubleshooting

This chapter gives tips on troubleshooting the Teradata Tools and Utilities installation. If you are unable to resolve a problem after reading this chapter, refer to “Technical Assistance” on page 147.

Problems may fall into one of these categories:

• Client Computer Problems

• Network Problems

• Software Problems

• Teradata Database Hardware Problems

Be aware, however, that a problem can overlap these categories, and that more than one problem can occur simultaneously.

Result codes are also included in this chapter:

• Silent Installation Result Codes

Technical Assistance

If you cannot resolve a problem, contact the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC). For contact information, refer to the Teradata Tools and Utilities Release Definition, Release 12.0.

Client Computer Problems

To determine whether a problem is with your client computer, perform the following checks. You may not have to do all of them.

Cannot Communicate Over the Network with Teradata Database

To confirm that your client computer can communicate over the network to the Teradata Database, ping the Teradata Database by opening a command window and typing:

ping dbcnameCOPn

You should receive a response similar to the following:

Pinging cs5100s.sandiegoca.ncr.com [153.64.116.94] with 32 bytes of data:


Chapter 7: TroubleshootingClient Computer Problems

Reply from 153.64.116.94: bytes=32 time=60ms TTL=60Reply from 153.64.116.94: bytes=32 time=40ms TTL=60Reply from 153.64.116.94: bytes=32 time=30ms TTL=60Reply from 153.64.116.94: bytes=32 time=50ms TTL=60Ping statistics for 153.64.116.94:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:

Minimum = 30ms, Maximum = 60ms, Average = 45ms

Use a second test to verify communication to the Teradata Database by entering the following at the command prompt:

telnet dbcnameCOPn

If your telnet service is disabled, you should receive the following response:

telnet: connect: Connection refused

If the connection is successful, you should receive a response similar to the following:

Welcome to the NCR MP-RAS SVR4 UNIX SystemUNIX System V Release 4.0 (cs5100s) (pts/0)login:

If you do not receive one of these responses, consult the next section, “Network Problems” on page 150.

Note: dbcnameCOPn should be upper or lower case.

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 not set during installation.

File localisation.dll Could Not Be Opened

If the localisation.dll file is missing, this message appears:

"File "localisation.dll" could not be opened.There may be problems with your installation.Exiting..."

Please check your installation, and make sure that the environmental variable PATH contains the folder in which the localisation.dll file resides.

File icuuctd28.dll Could Not Be Found

If the icuuctd28.dll file is missing, this message appears:

The dynamic link library icuuctd28.dll could not be found in the sprecified path.

Make sure the environment variable PATH contains the folder where icuuctd28.dll is located.


Chapter 7: TroubleshootingClient Computer Problems

Incorrect Path Name in COPANOMLOG

If you wish to produce an anomaly log file, check that the environment variable COPANOMLOG has the correct path name to the anomaly log file.

Incorrect CLIv2 Libraries Referenced

CLIv2, WinCLI Runtime, and the WinCLI Developer's Kit install CLIv2 DLLs in different directories under Teradata Client. During the installation, the system PATH environment variable is pre-pended with the directory of where the CLIv2 DLLs are located. Where the DLLs are first found in the system PATH determines how an application accesses the CLIv2 DLLs. The system PATH should be modified to access the correct version of the CLIv2 DLLs.

CLIv2 DLLs Load Error

CLIv2 libraries are no longer installed in the %System32% directory. The libraries are now installed under \Teradata Client. The system PATH environment variable is pre-pended with proper installed directories during installation. In order for the system PATH to take effect, reboot the system or restart the command shell. Also, make sure that the old CLIv2 libraries are removed from %system32% directory.

Incorrect Entries in the hosts File

In the %SystemRoot%\system32\drivers\etc\hosts file on your computer or in the hosts file on the NIS master, perform the following checks:

• 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 services File

Check for the following lines in the %SystemRoot%\system32\drivers\etc\ services file or in the services file on the NIS master:

tdmst 1025/udptdses 1025/tcp

Incorrect clispb.dat Parameters

Check the parameter values in the system parameter block file, clispb.dat.

Note whether the default i_dbcpath corresponds to the dbcnames in the %SystemRoot%\system32\drivers\etc\hosts file on your computer or in the hosts file on the NIS master.


Chapter 7: TroubleshootingNetwork Problems

Cannot Log On from CLI Application

If you cannot log on to the Teradata Database from your CLI application, try logging on from BTEQ.

If BTEQ works, then check your application for errors.

Cannot Log On to the Teradata Database

If you cannot log on to a Teradata Database, try logging on to a different Teradata Database.

If you are able to log on to the different Teradata Database, there may be something wrong with the first Teradata Database, or something wrong with the address of the first Teradata Database in the local hosts file or in the hosts file on the NIS master.

MSVCR71.DLL not found Message

If you encounter a “MSVCR71.DLL not found” message when trying to start a CLIv2-based application, reboot the system.

Network Problems

Network problems can be due to network hardware or software.

Procedure - Troubleshooting Network Problems

Follow these steps to determine whether a network problem is due to network hardware or software.

1 Verify that the transceiver is connected to the network, the computer, and the Teradata Database. Completing all steps may not be necessary.

2 Check for broken or disconnected network cables.

3 Check for excess lengths of all drop cables (they should follow the IEEE 802.3 standards).

4 Check all repeaters, bridges, routers, and gateways for correct functioning.

5 Check the network controller board to verify that all jumpers are set correctly.

6 Verify that the network software is installed and running correctly on the computer.

7 Verify that the network software is compatible with the network controller board installed on the computer.

8 Use a network utility program to confirm that the network is operational.

9 Use a network utility program from another computer on the same network segment as the first computer to confirm that the network is operational. If this works, there may be a problem with the first computer.

10 Use a network utility program from another computer on a different network segment than the first computer to confirm that the network is operational. If this works, there may be a problem with the first network segment.


Chapter 7: TroubleshootingSoftware Problems

11 If a network controller board was replaced in the computer, restart the Teradata Database so 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 (refer to the previous section, “Client Computer Problems” on page 147).

13 Restart the computer to reset network hardware and reload network software.

Software Problems

This section contains solutions to software problems you may encounter.

Error Running ttu.exe

You may see the following error message while installing a package copied to a network drive:

The parameter is incorrect

This error can occur if the path to the setup.exe file is too long. To resolve the problem, shorten the path to the setup.exe file. One way to do this is to move the file up in the directory structure.

Map a network drive letter to the Disk1 or other folder further down the pathname to produce a new shorter pathname.

If the Install button does not work, see “Install Button Does Not Work.”

Install Button Does Not Work

If the contents of the CD are copied to a network drive and the path to the ttu.exe file is too long, clicking on the Install button after the DemoShield displays will have no effect.

To resolve the problem, shorten the path to the ttu.exe file. One way to do this is to move the file up in the directory structure.

InstallShield 1603 Error

You may see the following error message when installing:

1603: Fatal Error During Installation

Or you may see the following:

Error 1603: General Windows Installer engine error. Increase DiskSpace requirement in Setup.ini and try again.

Some known causes for this error are as follows:

• The computer does not have enough disk space for the installation.

Solution: Increase your disk space.

• The Temp directory is not clean.

Solution: Find your Temp directory and delete its contents.



• A file on the installation Computer is locked.

Solution: Close all running applications and reboot the computer. Then run the installation again.

• The Windows Installer may not be properly installed.

Solution: Update the installation computer with the latest Windows Installer Service.

• You do not have proper Administrative privileges.

Solution: Confirm you have the proper privileges.

• The installation computer may have traces of a previous installation present.

Solution: Use Microsoft’s Windows Installer Clean Up utility to remove the previous install. Also, manually remove files that may have been installed.


You may see the following error message:

1607: Unable to install InstallShield Scripting Runtime

Little information is known at this time about the specific cause of this initialization error, as it rarely occurs and is typically encountered on an intermittent or machine-specific basis.

Some known causes for this error are as follows:

• There is a special character in the directory path containing the installation files.

If the installation files have been copied to a folder on a hard drive, and the full path contains special characters, such as “&”, “-”, “.”, etc., move the installation files to a path which does not contain special characters.

Example of bad path:

C:\tmp\downloads & packages\PMon\setup.exe

Example without the special character:

C:\tmp\downloads\PMon\setup.exe

• On Windows XP, there is a known issue with the Microsoft Windows Installer Service that affects all MSI-based setups. This error results when an MSI-based setup is run from a virtual drive created via the “subst” command.

If running on a Windows XP machine, make sure the setup is not running from a virtual drive created via the “subst” command.

• The file “IDriver.exe” is not registered properly.

Register the file “IDriver.exe” by using the command line below:

<ProgramFiles>\Common Files\InstallShield\Developer\7\Intel 32\IDriver.exe /REGSERVER

This command line can be entered in the Windows Start | Run dialog, after replacing <ProgramFiles> with the location of the Program Files directory.

• Permissions on the <Temp> folder are insufficient.

Make sure SYSTEM has full permission on the UserID %TEMP% folder. For example, on a computer running the Windows 2000 operating system, if UserID is fsk, the UserID %TEMP% folder may be <Boot Drive>:\Documents and Settings\fsk\Local Settings\Temp.



• Permissions on the <WindowsFolder>\Installer folder are insufficient.

Follow the steps below to set the proper permissions to the

<WindowsFolder>\Installer folder:

Procedure - Setting Permissions to the Installer Folder

Follow these steps to set permissions to the Installer Folder.

1 Locate the folder <WindowsFolder>\Installer. (For example, on Windows 2000 this folder would be “C:\WINNT\Installer”)*

2 Right-click the Installer folder, and choose “Properties.”

3 Select the “Security” tab.

4 Make sure the system, as well as the specific user, has full control of this folder.

Note: This folder is hidden by default in the Windows environment. Therefore it may be necessary to enter this path directly in the Windows Start | Run dialog to access this folder.

• The file “msiexec.exe” is not registered properly.

Register the file “msiexec.exe” by using the command line below:

<WindowsFolder>\System32\msiexec.exe /REGSERVER

This command line can be entered in the Windows Start | Run dialog, after replacing <WindowsFolder> with the location of the Windows folder.

• There are insufficient privileges in Windows.

Make sure you have full administrative permissions for this Windows machine.

• Another instance of the file “msiexec.exe” is running.

Kill unproductive copies of msiexec.exe using the Task Manager Processes tab.

• Another MSI-based setup is running simultaneously.

Make sure no other MSI-based installations are running simultaneously.

• DCOM impersonation level is set incorrectly.

The solution for the Windows 2000 Professional is to change the value for the “Default Impersonation Level” from “Anonymous” to “Identify” using the “dcomcnfg” utility.

Procedure - Changing the Default Impersonation Level on Windows 2000

For Windows 2000, follow these steps to change the Default Impersonation Level from “Anonymous” to “Identify.”

1 Click Start->Run and type dcomcnfg in the Open field.

2 Click OK.

3 Select “Default Properties” tab.

4 In the “Default Impersonation Level” list, select “Identify.”

5 Click OK.


Chapter 7: TroubleshootingTeradata Database Hardware Problems

Here is the procedure to change the “Default Impersonation Level” to “Identify” using the “dcomcnfg” utility on Windows XP Professional:

Procedure - Changing the Default Impersonation Level on Windows XP

For Windows XP, follow these steps to change the Default Impersonation Level from “Anonymous” to “Identify.”

1 Click Start->Run and type dcomcnfg in the Open field.

2 Click OK.

3 In the console tree of the Component Services administrative tool, right-click the computer whose machine-wide impersonation level you want to modify and then click “Properties.”

4 Select the “Default Properties” tab.

5 Ensure that “Enable Distributed COM on this computer” is checked.

6 In the “Default Impersonation Level” box, select “Identify.”

7 Click OK.


If you are installing from the CD to a computer that runs on the Windows 2000, or Windows XP operating system, you can receive an error indicating that UnInstallShield is running (InstallShield Error 432).

Procedure - Deleting ISUnist.exe

Follow these procedures if you receive and InstallShield 432 error.

1 Verify that you have administrative privileges.

2 Delete all instances of IsUninst.exe from the Windows folder and run the setup again.

3 If IsUninst.exe cannot be deleted because it is in use, reboot the machine and run the setup again.

Teradata Database Hardware Problems

Note: Teradata Database hardware problems should be diagnosed with the assistance of your Teradata field service representative.

The following procedure helps determine if there is a database hardware problem, where it is located.


Chapter 7: TroubleshootingTeradata Database Hardware Problems

Procedure - Determine whether Database Hardware is Working Properly

Follow these steps to determine whether Database hardware is working properly. Steps 2 through 7 apply to the Teradata Database only.

1 Log on to the Teradata Database from the operator console, another network-attached host, or a mainframe. If you are able to log on, the hardware is operational. If you are unable to log on, contact your Teradata field service representative.

2 Have your field service representative verify that the adapter cable is connected.

3 Have your field service representative check the Multibus Adapter Board (MAB).

4 Check for the following characteristics in all entries of the CopInfoTbl file on the Teradata Database:

• Incorrect, missing, or duplicate cabinet and processor numbers (ccc_p) for applications processors (APs)

• Incorrect, missing, or duplicate network addresses

• Correct network protocol type (CopKind) for each AP

• Correct host number for each AP

• Entries in the CopInfoTbl file match the entries in the <Boot Drive>: \Program Files\NCR\Teradata Parallel Transporter\hosts file (on the computer) or in the hosts file on the NIS master; use the CopUpdate macro to change the CopInfoTbl file.

5 If necessary, run the CopUpdate macro.

If an AP is added or removed from the Teradata Database or if an AP’s network address is changed, the CopUpdate macro must be executed so the Teradata Database can determine changes to network addresses. (The Teradata Database must be restarted before the changes can take effect.)

6 If you are using Internet routing (routers), check the CopRoutesTbl file for the following:

• Incorrect or missing network addresses of destinations

• Incorrect or missing network addresses of routes

• 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 file

7 If you are using subnet routing (subnetting), check the CopOptionsTbl file for incorrect or missing subnet masks.

(To change the CopOptionsTbl file, use the AddOption macro.)

8 If the Teradata Database goes down and then comes back up, its sessions table still contains information generated by the hosts that were connected when it went down.

The Teradata Database expects to receive reconnect messages from those hosts. If it does not receive a reconnect message within 20 minutes after it comes back up, it will remove the sessions generated by hosts that have not reconnected.

Therefore, 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


Chapter 7: TroubleshootingSilent Installation Result Codes

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.

Silent Installation Result Codes

Silent installation creates a product setup log file, setup.log. The last section in the setup.log file, called Response Result, gives the status of the installation. Any value other than 0 for the Result Code means the installation has failed. If failure occurs, refer to the Remedy entries in Table 84.

Location of the Setup Log

The product setup log file is in the %TEMP%\ClientISS folder. The name of the product setup log file is <product>Setup.log. For example, BTEQ’s setup log file would be BTEQSetup.log and MultiLoad’s setup log file would be MultiLoadSetup.log.

InstallShield Result Codes

Table 84 shows the InstallShield result codes of a silent install.

Table 84: InstallShield Result Codes

Description Result Code

Code:

Explanation:

Remedy:

0

Success

None

Code:

Explanation:

Remedy:

-1

General error

If this result recurs, contact the TSCS-RSC. Try to install the product in interactive mode.

Code:

Explanation:

Remedy:

-2

Invalid mode


Code:

Explanation:

Remedy:

-3

Required data not found in the setup.iss file

Correct the problem in the product’s setup.iss file and reinstall the product in silent mode.




Code:

Explanation:

Remedy:

-4

Not enough memory available

Exit other currently running Windows programs or increase the memory size, then reinstall the product in silent mode.

Code:

Explanation:

Remedy:

-5

File does not exist

Make sure the response file exists in the %TEMP%\ClientISS or CD ClientISS folder, then reinstall the product in silent mode.

Code:

Explanation:

Remedy:

-6

Cannot write to the response file

Correct the write permission problem, then reinstall the product in silent mode.

If this result recurs, install the product in interactive mode.

Code:

Explanation:

Remedy:

-7

Unable to write to the log file



Code:

Explanation:

Remedy:

-8

Invalid path to the InstallShield response file

Make sure the %TEMP%\ClientISS folder exists or the CD is inserted, then reinstall the product in silent mode.

Code:

Explanation:

Remedy:

-9

Not a valid list type (string or number)


Code:

Explanation:

Remedy:

-10

Data type is invalid


Code:

Explanation:

Remedy:

-11

Unknown error during setup


Table 84: InstallShield Result Codes (continued)




Code:

Explanation:

Remedy:

-12

Dialog boxes are out of order


Code:

Explanation:

Remedy:

-51

Cannot create the specified folder



Code:

Explanation:

Remedy:

-52

Cannot access the specified file or folder



Code:

Explanation:

Remedy:

-53

Invalid option selected


Table 84: InstallShield Result Codes (continued)



Index

Symbols.iss files 47_unodbc.dll 104

Aan 48application, cannot log on 150ARC

default destination folder 48default program folder 48dependencies 28product response file name 48

ARCDFLT.TXT 106arcmain.exe 107attributes.twb.xsl 129authentication mechanism 137

Bbase.twb.xsl 129blkexit.c 112blkexit.mak 112blkexitr.c 112BlockLoad.h 113BTEQ 34, 35, 36

default destination folder 48default program folder 48dependencies 28platforms supported 22product response file name 48

bteq.exe 103BTEQWin

default destination folder 48default program folder 48dependencies 28platforms supported 22

bteqwin.exe 103bteqwin_enu.cnt 103bteqwin_enu.hlp 103bteqwin_jpn.cnt 103bteqwin_jpn.dll 103bteqwin_jpn.hlp 103btnfyext.c 104btnfyext.def 104btnfyext.h 104btnfyext.mak 104

Ccannot communicate over network 147cannot log on from CLI application

CLI 150cannot log on to database 150caputl.dll 104checkpoint 123cleanupTables.bteq 116, 120CLI

configuring 89CLI_Module 48client connections

setting number of 57clisamp.c 107, 108clispb.dat 107, 108, 149CLIv2

product response file name 48cliv2if.h 108, 109cnstool.exe 112columns.twb.xsl 129computer problems

troubleshooting 147Connection.h 113connections

setting number of 57contacting Teradata 147coordinator.exe 123COPANOMLOG 91

incorrect path name 149coperr.h 108, 109COPLIB 91

incorrect path name 148coptypes.h 108, 109custom installation 74

Ddata.in 125DataConnector Operator

platforms supported 23dataconop.dll 121dbcacnx.h 108, 109dbcarea.h 108, 109dbcerr.h 108, 109dbms.twb.xsl 129DDL Operator

platforms supported 23


Index

ddlop.dll 121dependencies 28Disk Cost

Teradata SQL Assistant/Web Edition 67DMLGroup.h 113

Eenvironment parameters

setting 91executor.exe 123expnfyxt.c 122Export Operator

platforms supported 24exportop.dll 122

FFastExport OUTMOD Adapter Operator

platforms supported 24FastLoad INMOD Adapter Operator

platforms supported 24fastload.exe 111feimod.c 111fenotf.c 111feomod.c 111feomop.dll 124fexp.exe 111file.twb.xsl 129files

installed 101flimop.dll 124flnfyext.c 112FPSpread.dll 111fspread.dll 132

Ggeneric.h 113GenericDriver.cpp 117, 121GenericDriver.h 117, 121GetBuffer.h 116, 120getbuffer.sln 116getbuffer.vcproj 116getbuffer64.sln 120getbuffer64.vcproj 120GetHostByName

limiting requests 92GT11.txt 125GT44.txt 125GT62.txt 125GT93.txt 125GT94.txt 125GT95.txt 125GT96.txt 125

GT97.txt 125guisrv.dll 129

Hhardware problems

troubleshooting 154help 129hosts file 89

adding entries to 90incorrect entries 149

Iicudttd281.dll 105, 106icuintd28.dll 105, 106icuiotd28.dll 105, 106iculetd28.dll 105, 106iculxtd28.dll 105, 106icuuctd28.dll 105, 106incorrect

clispb.dat parameters 149incorrect entries in hosts file 149incorrect path name in COPANOMLOG 149incorrect path name in COPLIB 148parameter is incorrect 151

infile.littleEndian 117, 121input.exp 117, 121input.lod 117, 121input.stm 117, 121input.txt 116, 120input.upd 117, 121insertop.dll 127installation

custom 74kit 31network 78typical 64

InstallShieldresult codes 156

Internet Information Servicesinstallation 53

JJava 2 Runtime Environment 69, 73jhall.jar 112job.twb.xsl 129jobstep.twb.xsl 129jobvars.txt 125jre 129

LLABSBTEQ 107


Index

ldnfyext.c 125, 126libjmsam.dll 106libmqs.dll 131libmqsc.dll 131libmqscTWB.dll 131libmqsTWB.dll 131libnetpde.dll 112libpm.dll 109, 110limiting GetHostByName requests 92Load Operator

platforms supportedplatforms supported 24

loadop.dll 125, 126localisation.dll 108, 109

file could not be opened 148logger.twb.xsl 129logon

dialog box 135procedures 135

logs 123logview.dll 124logview.twb.xsl 129

Mmain.cpp 116, 120makesamp.win 107, 108mfc71.dll 104, 111, 132mfc71u.dll 104, 111, 132mgrcli.dll 103, 111, 132mgrcli_jpn.dll 103Microsoft .NET Framework

installation 54Microsoft Internet Explorer Cookie Settings

changing, version 5.5 56changing, version 6.0 56

Microsoft Internet Explorer Security Settingschanging 55

missing entries in services file 149mlimod.c 112mlimop.dll 124mlnotf.c 112mload.exe 112monpm.dll 111, 132mosiif.h 108, 109mpsfs.exe 110msvcirt.dll 124msvcirtd.dll 124msvcp60.dll 124msvcp60d.dll 124MSVCP71.DLL 105msvcp71.dll 122, 124, 132MSVCR71.DLL 105msvcr71.dll 104, 111, 113, 122, 124

msvcr80.dll 111, 132msvcrt.dll 124msvcrtd.dll 112, 124MultiLoad INMOD Adapter Operator

platforms supported 24MultiTool 112

NNamed Pipes Access Module 35, 36, 37, 38

default destination folder 48default program folder 48dependencies 28platforms supported 22product response file 48

ncrtmgr.dll 103, 111, 132ncrtmgr_jpn.dll 103NetBackup Teradata Extension 28network

installation 78parameters, setting 89troubleshooting 150

nojunk.h 108, 109np_AXSMOD.dll 104np_AXSMODenu.dll 104np_AXSMODenuTWB.dll 104np_AXSMODTWB.dll 104

Oobjects.twb.xsl 129ODBC Driver for Teradata 34, 35, 36, 38

configuring 88default destination folder 48default program folder 48dependencies 28installing 72platforms supported 22product response file name 48

ODBC Operatorplatforms supported 24

odbcop.dll 126OLEDB_AXSMOD.dll 113OLEDB_AXSMODenu.cnt 113OLEDB_AXSMODenu.dll 113OLEDB_AXSMODENU.hlp 113OLEDB_AXSMODjpn.cnt 113OLEDB_AXSMODjpn.dll 113OLEDB_AXSMODJPN.hlp 113oleload.exe 113oncrpc.dll 124opcommon.dll 126operating systems 26operation.twb.xsl 129Operator Support Library


Index

platforms supported 24operator.twb.xsl 129opermsgs.dll 126OptionsReader.cpp 117, 121OptionsReader.h 117, 121OS Command Operator

platforms supported 24oscmdop.dll 127

Pparameters

setting environment 91setting network 89setting system 93

parcel.h 108, 109Pbocd0x0.txt 104pdecui.jar 112planexecutor.exe 123pmdcomt.h 109, 110pmddamt.h 109, 110port number

setting using TDMSTPORT 92Teradata SQL Assistant/Web Edition 67

PPCLB1 107PPCLB2 107PPCLB3 107PPCLB4 107PPCLB5 107PPCLB6 107PPCLB7 107PPCLB8 107PPCLB9 107ppcmain.exe 107ppruntim.dll 107ppruntim.lib 107Preprocessor

default destination folder 48default program folder 48dependencies 28platforms supported 22product response file name 48

printman.dll 103product dependencies 28product version numbers 3program.ico 113psload.dll 111, 132ptmexec.exe 123ptmgts.exe 123ptmin.dll 124ptmjlgr.exe 123ptmlvs.exe 123ptmos.dll 124ptmpi.dll 124

ptmpo.dll 124ptmtims.exe 123pxcommon.dll 124pxdef.h 124pxdtypes.h 124pxicu.dll 122pxlogdef.h 124pxmacros.h 124pxoper.h 124pxos.h 124pxstc.h 124pxtypes.h 124pxutypes.h 124pxversion.h 124

Rreadme 106readme.doc 125Readme.txt 104readme.txt 130Receiver.class 106requests

GetHostByName 92requirements

software 28resource.h 108, 109result codes 156runtbuild.cmd 129

Ssamplefilter.cpp 125sampleoperator.dsp 125sampleoperator.dsw 125samples.jar 110samplescript.txt 125Schema.h 113schema.twb.xsl 129selectop.dll 127services file

missing entries 149setup.log 156setupTables.bteq 116, 120sfc.jar 112Shared ICU Libraries for Teradata 28, 34, 35, 36, 37, 38, 39, 48

platforms supported 22SharedICULibrariesforTeradata.iss 48SharedICULibrariesforTeradata64.iss 48silent installation

troubleshooting 156software problems

troubleshooting 151software requirements 28SQL Inserter Operator


Index

platforms supported 24SQL Selector Operator

platforms supported 24sql1.txt 125sql2.txt 125sqlprs.dfa 131sqlprs.llr 131stmnfyxt.c 128Stream Operator

platforms supported 25streamop.dll 128support 51supported software releases 3symbeans.jar 112syntax

for hosts file entries 90

Ttable.twb.xsl 129tableset.twb.xsl 129tbuild.exe 123tbuildexe.exe 123td.ico 112tdapp.dll 111, 132tdatpump.cfg 131TDDSNC.EXE 106tdgssconfig.jar 110, 129tdgssjava.jar 110, 129tdis.dll 103, 111, 132tdmfcis.dll 111, 132TDMSTPORT

setting the port number 92tdqmcomm.dll 130tdqmcomm.exe 130tdqmdb.exe 130tdqmjob.exe 130tdqmlsnr.exe 130tdqmops.exe 130tdqmreqp.exe 130tdqmserv.dll 130tdqmserv.exe 130tdqmsr.dll 130tdqmsubm.dll 130tdqmview.exe 130tdqsadm.exe 130tdsqlprs.dll 130tdusr32.dll 108, 109tdusr32.lib 108, 109tdwm.exe 110tdwmutil.dll 111, 132technical support 51telapi.dll 113telapi.lib 113

teqtalk.ico 103Teradata 34Teradata Access Module for JMS 22, 28, 35, 36, 48Teradata Access Module for Tivoli 38, 48

dependencies 28platforms supported 22

Teradata Administratorconfiguring 87default destination folder 48default program folder 48dependencies 28platforms supported 22

Teradata Archive/Recovery Utility 38, 48platforms supported 22

Teradata C Preprocessor 22, 34, 35, 38Teradata Call-Level Interface version 2 (CLIv2) 34, 35, 36, 37,

38, 39default destination folder 48default program folder 48dependencies 29installation order 31platforms supported 22

Teradata Cobol Preprocessor 35Teradata Data Connector 34, 35, 36, 37, 39

default destination folder 48default program folder 48dependencies 29installation order 31platforms supported 22product response file name 48

Teradata Databasecannot log on to 150identifying 89

Teradata DQM Administratorconfiguring 88

Teradata DQM Scheduled Requests Clientconfiguring 88default destination folder 50default program folder 50platforms supported 25product response file name 50

Teradata DQM Scheduled Requests Serverconfiguring 88default destination folder 50default program folder 50platforms supported 25product response file name 50

Teradata Driver for the JDBC Interfaceplatforms supported 23, 145

Teradata Dynamic Workload Manager 29, 34, 49platforms supported 23

Teradata FastExport 35, 36, 37default destination folder 49default program folder 49


Index

dependencies 29platforms supported 23product response file name 49

Teradata FastLoad 35, 36, 37default destination folder 49default program folder 49dependencies 29platforms supported 23product response file name 49

Teradata Generic Security Services 34, 35, 36, 37, 38, 39, 49Teradata Generic Security Services Client

dependencies 29platforms supported 23, 26

Teradata Index Wizard 34default destination folder 49default program folder 49dependencies 29platforms supported 23product response file name 49, 50

Teradata Manager 34configuring 88default destination folder 49default program folder 49dependencies 29installing 70platforms supported 23product response file name 49

Teradata MultiLoad 35, 36, 37default destination folder 49default program folder 49dependencies 29platforms supported 23product response file name 49

Teradata MultiTooldefault destination folder 49default program folder 49dependencies 29installing 69platforms supported 23

Teradata OLE DB Access Module 35default destination folder 49default program folder 49dependencies 29platforms supported 23product response file name 49

Teradata Parallel Transporterconfiguring 94

Teradata Parallel Transporter APIplatforms supported 23

Teradata Parallel Transporter ICU Librarydefault destination folder 49default program folder 49

Teradata Parallel Transporter Infrastructureplatforms supported 24

product response file name 49Teradata Parallel Transporter Wizard

platforms supported 25Teradata Performance Monitor 34


Teradata Query Director 39dependencies 29platforms supported 25

Teradata Query Scheduler Administrator 29, 34platforms supported 25

Teradata Query Scheduler Client 29, 34default destination folder 50default program folder 50

Teradata Query Scheduler Server 29, 34default destination folder 50default program folder 50

Teradata Scheduled Requests Clientconfiguring 88

Teradata Scheduled Requests Serverconfiguring 88

Teradata Software Server 32Teradata SQL Assistant


Teradata SQL Assistant/Web Editiondefault destination folder 50default program folder 50dependencies 30installing 67platforms supported 25

Teradata Statistics Wizard 34default destination folder 50default program folder 50dependencies 30platforms supported 25

Teradata System Emulation Tool 34default destination folder 50default program folder 50dependencies 30platforms supported 25product response file name 50

Teradata TPump 35, 36, 37default destination folder 50default program folder 50dependencies 30platforms supported 25product response file name 50

Teradata Visual Explain 34default destination folder 50


Index

default program folder 50dependencies 30platforms supported 25product response file name 50

Teradata Workload Analyzer 30, 34default destination folder 50default program folder 50platforms supported 25product response file 50

Teradata_Access_Module_for_Tivoli.iss 48Teradata_JMS.iss 48terajdbc4.jar 110, 129terasso.dll 108, 109TIVARC.BATTIVADM.BAT 106TIVBAR.DLL 106TIVDFLT.TXT 106Tivoli.Readme.TXT 106tldnfyxt.c 131tlogview.exe 123tlogviewexe.exe 123tm_dialogs.dll 103, 111, 132tm_dialogs_jpn.dll 103tm_stat.dll 103tm_stat_jpn.dll 103tptlaunch.exe 123tptwizard.cmd 129tptwizard.ico 129tptwizard.jar 129TPump, see Teradata TPumptpump.exe 131tpumpar.csql 131tpumpimd.c 131troubleshooting

client computer problems 147client problems 147hardware problems 154network problems 150silent installation 156Teradata Database problems 154

TSCS-RSC 51twa.exe 131twb_status.txt 125twb_targets.txt 125twbcfg.ini 123twbcmdexe.exe 123twbkill.exe 123twbkillexe.exe 123twbmsgs.dll 124twboper.ini 123twbpath.exe 123twbpathexe.exe 123twbrmcp.exe 123twbrmcpexe.exe 123twbstat.exe 123

twbstatexe.exe 123twbwizard.properties 129typical installation 64

UUninst.dll 113uninst.dll 125uninstalling previous software 47UninstDataConnectorOp8.1.isu 121UninstDDLOp8.1.isu 121UninstInsertOp8.1.isu 127UninstODBCOp8.1.isu 126UninstOSCmdOp8.1.isu 127UninstSelectOp8.1.isu 127UninstTPTWizard8.1.isu 129Update Operator

platforms supported 25updateop.dll 128updnfyxt.c 128User Exit functions 93

CLI 93

Vverify.dat 110, 131Verify.exe 110, 131verifying installation 101version 125version numbers 3version.txt 112Virtual directory

Teradata SQL Assistant/Web Edition 67

WWebSphere MQ Access Module 30, 36, 37, 38

default destination folder 50default program folder 50platforms supported 25product response file 50

wincli32.dll 108, 109wincli32.lib 108, 109wincliv2.h 108, 109winjavaloader.exe 112wwhelp.dll 129

Xxsp.cpp 117xsp.sln 117xsp.vcproj 117xsp64.sln 121xsp64.vcproj 121


Index
