Teradata Tools and Utilities for Microsoft Windows Installation Guide Release B K March 2013

Transcription

1 Teradata Tools and Utilities for Microsoft Windows Installation Guide Release B K March 2013

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Active Data Warehousing, Active Enterprise Intelligence, Applications-Within, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast, Gridscale, MyCommerce, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata ServiceConnect, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and other countries. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. Apache, Apache Hadoop, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. Apple, Mac, and OS X all are registered trademarks of Apple Inc. Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda Access, Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and Maximum Support are servicemarks of Axeda Corporation. Data Domain, EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of Oracle. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other countries. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/os are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI is a registered trademark 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. NetVault is a trademark or registered trademark of Dell Inc. in the United States and/or other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries. Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. 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 registered trademark of Unicode, Inc. in the United States and other countries. 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 [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 by Teradata. All Rights Reserved.

3 Table of Contents Preface...9 Purpose... 9 Audience... 9 Supported Releases... 9 Prerequisites... 9 Changes to This Documentation...10 Technical Assistance...10 Chapter 1: Preparing for Installation What's New...11 About Product Suites About Installing a Product Suite...11 About Log Files...11 About Uninstalling a Product Suite About efixes...12 About Standalone Products...12 About Installing Teradata Tools and Utilities from DVD Installation Kit Contents DVD Contents Product Descriptions Product Dependencies...19 Dependent Products System Requirements...23 Chapter 2: Uninstalling Software...25 About Uninstalling Previous Versions of Teradata Tools and Utilities About Retaining Existing Files for TeraGSS Client Package...25 Generating a List of Installed Products Silently Uninstalling Teradata Tools and Utilities...26 Uninstallation Script Prerequisites...26 Teradata Tools and Utilities for Microsoft Windows Installation Guide 3

4 Table of Contents Uninstallation Script Overview Using a Script to Silently Uninstall Teradata Tools and Utilities...28 Using a Batch File to Silently Uninstall Teradata Tools and Utilities Product Parameter Values for Use With Batch Files Interactively Uninstalling Teradata Tools and Utilities Chapter 3: Installing New Software...35 About Installing Third-Party Software Determining the Current Version of.net Framework Installing Third-Party Software for Teradata Parallel Transporter Base Installing Third-Party Software for Teradata Parallel Transporter Wizard...35 Downloading and Installing Third-Party Software for Teradata SQL Assistant...36 Installing Third-Party Software for Teradata WebSphere MQ Access Module...36 About Installing Teradata Tools and Utilities Interactively Installing Teradata Tools and Utilities Products...37 About Installation Log Files Silently Installing Teradata Tools and Utilities Products Installing.NET Data Provider for Teradata About Installing.NET Data Provider for Teradata...39 About Security Requirements for.net Data Provider for Teradata...40 Known Issues for.net Data Provider for Teradata Uninstalling.NET Data Provider for Teradata...41 Installing Third-Party Microsoft.NET Framework...41 Downloading.NET Data Provider for Teradata Installing.NET Data Provider for Teradata...42 Verifying Installation of the.net Data Provider for Teradata About Teradata Developer Exchange...44 Products Available from Teradata Developer Exchange Connectivity...44 Tools Downloading a Product from the Teradata Developer Exchange Installing Products Downloaded from Teradata Developer Exchange About Teradata Software Server (Patch Server) Downloading Updated Software Packages...46 Installing Updated (Patched) Software Packages Installing Third-Party Windows Help Program Teradata Tools and Utilities for Microsoft Windows Installation Guide

5 Table of Contents Chapter 4: Configuring New Software About Setting Network Parameters...49 About Configuring Teradata Call-Level Interface version Verifying the Existence of the hosts File Identifying a Teradata Database Adding and Editing AP Entries in the hosts File...50 About Setting Up Environment Parameters...51 Defining Paths to System Files Setting Up Environment Variables Speeding Up the CLIv2 Logon Process Setting Up Port Number, Netrace, and Threadlogging...53 About clispb.dat...53 Setting System Parameters...54 About Configuring ODBC Driver for Teradata...54 Configuring ODBC Driver for Teradata...54 Configuring Data Source for ODBC Driver for Teradata About Configuring Teradata Query Scheduler Administrator...54 Modifying the hosts File Configuring Teradata Query Scheduler Client...55 About Configuring Teradata Query Scheduler Server...55 Specifying a Default Teradata Query Scheduler Server...55 Changing Teradata Query Scheduler Server Configurations Configuring Teradata Administrator Configuring Teradata Parallel Transporter Editing the Teradata Parallel Transporter Configuration File...57 Editing the Teradata Parallel Transporter Properties File...58 Configuring Teradata Access Module for JMS...58 Chapter 5: Verifying the Complete Installation...59 About Verifying the Installation Verifying the Installation Using CLI Sample Program...59 Generating a List of Installed Products List of Files About the program-files Variable in the Default Installation Path...61 Basic Teradata Query Files and Folders...61 Teradata Tools and Utilities for Microsoft Windows Installation Guide 5

6 Table of Contents Teradata Access Module for JMS Files and Folders Named Pipes Access Module Files and Folders...62.NET Data Provider for Teradata Files and Folders...62 ODBC Driver for Teradata Files and Folders OLE DB Provider for Teradata Files and Folders...65 Shared ICU Libraries for Teradata Files and Folders...65 Teradata Administrator Files and Folders...66 Teradata Archive/Recovery Utility Files and Folders Teradata C Preprocessor2 Files and Folders Teradata Call-Level Interface version 2 Files and Folders...67 Teradata Data Connector API Files and Folders...68 Teradata FastExport Files and Folders...68 Teradata FastLoad Files and Folders...69 Teradata Generic Security Services Files and Folders Teradata Index Wizard Files and Folders Teradata JDBC Driver Files and Folders Teradata MultiLoad Files and Folders Teradata OLE DB Access Module Files and Folders...75 Teradata Parallel Data Pump Files and Folders (32-bit Platform)...76 Teradata Performance Monitor Object Files and Folders Teradata Query Scheduler Administrator Files and Folders Teradata Query Scheduler Client Files and Folders...76 Teradata Query Scheduler Server Files and Folders Teradata SQL Assistant Files and Folders Teradata Statistics Wizard Files and Folders Teradata System Emulation Tool Files and Folders Teradata Visual Explain Files and Folders...86 Teradata Wallet Files and Folders...90 Teradata WebSphere MQ Access Module Files and Folders...90 Teradata Workload Analyzer Files and Folders...90 Chapter 6: Deploying Teradata Tools and Utilities with SCCM About Deploying Products with SCCM Third-Party Dependency Products on Client Computers Uninstalling Existing Products from Client Computers Creating a Software Repository Creating a Batch File to Install the Products...95 Deploying the Batch File and the Packages via SCCM Teradata Tools and Utilities for Microsoft Windows Installation Guide

7 Table of Contents Chapter 7: Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR About the TAR File TAR Script Compatibility with Platform Operating Systems Verifying TAR Script Dependencies are Installed The TAR Script Command TAR Script Usage Considerations Downloading Windows Utility Software for TAR Deployment TAR Script Examples Archiving Oracle Solaris SPARC Packages Archiving an HP-UX Package Archiving Linux Packages Teradata Tools and Utilities for Microsoft Windows Installation Guide 7

8 Table of Contents 8 Teradata Tools and Utilities for Microsoft Windows Installation Guide

9 Preface Purpose This book describes how to install and deploy Teradata Tools and Utilities Release software on a computer that runs on a supported operating system. Teradata Tools and Utilities is a group of products designed to work with the Teradata Database. Audience This guide is intended for use by: Database administrators and relational database developers System administrators System and application programmers System operators and other database specialists Supported Releases This document supports the following versions of Teradata products: Teradata Database Release Teradata Tools and Utilities Release To locate detailed information about supported releases, refer to the spreadsheet Teradata Tools and Utilities Supported Platforms and Product Versions, B The spreadsheet contains detailed information about supported Teradata Database releases, platforms, and product release numbers. Prerequisites You should be familiar with: Computer technology and terminology Relational database management systems Utilities that load and retrieve data Teradata Tools and Utilities for Microsoft Windows Installation Guide 9

10 Preface Changes to This Documentation Changes to This Documentation Date March Description Initial release Technical Assistance For more information, see Teradata Tools and Utilities Release Definition, B If you need additional information or assistance, contact your Teradata Customer Service Representative. If you purchased an Enterprise System Support (ESS) contract, a customized support plan was created for you. For contact information, refer to your support plan. To learn more about Teradata Customer Services, go to Your Service, tays.teradata.com. 10 Teradata Tools and Utilities for Microsoft Windows Installation Guide

11 CHAPTER 1 Preparing for Installation What's New About Product Suites Beginning with version 14.10, all Teradata Tools and Utilities products are bundled in one of the following three suites. Each suite is on a separate DVD: Teradata Tools and Utilities - Base Teradata Tools and Utilities - Database Management Teradata Tools and Utilities - Tape Storage Management For more information, see DVD Contents. About Installing a Product Suite The Installer window contains a list of each product name in the suite. A checkbox next to each product allows you to install a subset of products. The following dependent products are automatically installed: Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata Generic Security Services Client About Log Files When you silently install products or when you perform a special interactive installation using the setup.exe /debuglog command, log files are created. These files include a main log file named InstallShield.log and a log file for each individual product that is installed. You can use these files if you need to debug the installation. About Uninstalling a Product Suite When you uninstall a suite, all of the primary products in that suite are uninstalled. In the Add/Remove programs applet, the name of the suite is removed. All of the dependent products are uninstalled when the last suite is uninstalled. Teradata Tools and Utilities for Microsoft Windows Installation Guide 11

12 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD About efixes Suites that include efixes are available for download from Teradata Software Server (Patch Server). For products that are available in a 32-bit version and a 64-bit version, each suite contains both versions (bitnesses) of the products. When you install a new version of the suite, efixes are applied automatically. The installer recognizes products that need to be upgraded and it upgrades them. efixes can be installed via SCCM. About Standalone Products You can still download the following standalone products from Teradata Developer Exchange:.NET Data Provider for Teradata ODBC Driver for Teradata Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata Generic Security Services Client Teradata Wallet Note: If you download these products from Teradata Developer Exchange, they are intended to be used only for connecting to Teradata Database via non-teradata products. They are not intended to be used for updating the Teradata Tools and Utilities suite of products available on DVD. About Installing Teradata Tools and Utilities from DVD Before performing the procedures in this document, you must have: Internet access Network access Administrative privileges on the target machine Knowledge of which Teradata Tools and Utilities are to be installed Familiarity with Windows file and path name conventions Access to a bill of materials or similar list of Teradata Tools and Utilities software that was ordered Familiarity with software installation Installation Kit Contents The installation kit contains the following documentation media and application media: Teradata User Documentation CD (Teradata Database 14.0, Teradata Tools and Utilities 14.10) 12 Teradata Tools and Utilities for Microsoft Windows Installation Guide

13 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities Database Management WINDOWS Release DVD Teradata Tools and Utilities Tape Storage Management Enablers Linux & WINDOWS Release DVD If you did not receive all the installation media that you ordered, contact your Teradata Sales Representative. DVD Contents The table below contains a list of the Teradata Tools and Utilities products that are on the media in the installation kit. Note: In the table, the media titles are abbreviated: Abbreviation Base Database Management Tape Storage Management Media Title Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities Database Management WINDOWS Release DVD Teradata Tools and Utilities Tape Storage Management Enablers Linux & WINDOWS Release DVD Table 1: Products and the Media They Reside On Product.NET Data Provider for Teradata X Base Basic Teradata Query X X ODBC Driver for Teradata X X Media Title (Abbreviated) Database Management Shared ICU Libraries for Teradata X X X Teradata Access Module for JMS X Teradata Administrator X Teradata Archive/Recovery Utility X Teradata C Preprocessor2 X X Teradata Call-Level Interface version 2 X X X Teradata Data Connector API X X X Teradata FastExport X Teradata FastLoad X Teradata GSS Client X X X Tape Storage Management Teradata Tools and Utilities for Microsoft Windows Installation Guide 13

14 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Base Teradata Index Wizard X Teradata MultiLoad X Teradata Named Pipes Access Module X Teradata OLE DB Access Module X Teradata Parallel Data Pump X Teradata Parallel Transporter Base X Teradata Parallel Transporter Stream X Teradata Performance Monitor Object X Teradata Query Scheduler Administrator X Teradata Query Scheduler Client X Teradata Query Scheduler Server X Teradata SQL Assistant X Teradata Statistics Wizard X Teradata System Emulation Tool X Teradata Visual Explain X Media Title (Abbreviated) Database Management Teradata Wallet X X X Teradata WebSphere MQ Access Module X Teradata Workload Analyzer X Related Topics Products Available from Teradata Developer Exchange, on page 44 Tape Storage Management Product Descriptions Product.NET Data Provider for Teradata Basic Teradata Query Description.NET Data Provider for Teradata is a library of routines that Microsoft.NET Framework applications use for uniform and standard-based (ADO.NET) access to data sources such as a Teradata Database. This is the data access component of the.net Framework Class Library. Basic Teradata Query (BTEQ) is a general-purpose utility that allows users on a workstation to communicate with one or more Teradata Database systems and to format reports for output to print and screen. This utility is accessible from the command line or a script. 14 Teradata Tools and Utilities for Microsoft Windows Installation Guide

15 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product ODBC Driver for Teradata OLE DB Provider for Teradata Shared ICU Libraries for Teradata Teradata Access Module for JMS Teradata Administrator Teradata Archive/Recovery Utility Teradata C Preprocessor2 Teradata Call-Level Interface version 2 Teradata Data Connector API Description ODBC Driver for Teradata is a library of routines that enables UNIX, Linux, and Windows applications to communicate with a Teradata Database across local area networks (LANs) using the open standards ODBC interface. OLE DB Provider for Teradata is a set of Component Object Model (COM) interfaces and objects that provides applications with uniform, standard access to any data store. In this case, the data store is in the Teradata Database. This library of routines allows access to data stores that do not use Structured Query Language (SQL). Using this utility, an application requests database information from an intermediate program, which in turn accesses the Teradata Database. The intermediate program receives the response from the Teradata Database and returns a copy of the desired data to the application. Shared ICU Libraries for Teradata is a library of routines based on IBM International Components for Unicode. The library provides Unicode support. Note: Shared ICU Libraries for Teradata is a core product that must be installed in the correct sequence with other core products. Normally when you install the suite of Teradata Tools and Utilities products from media, the library is automatically installed as a dependency for other Teradata Tools and Utilities products. Teradata Access Module for JMS is a command line utility that provides a fast, reliable, asynchronous way to transfer data between any JMS-enabled messaging system and a Teradata Database. This utility works with the Teradata Parallel Transporter products and with Teradata FastExport, Teradata FastLoad, Teradata MultiLoad, and Teradata Parallel Data Pump. Teradata Administrator (TDAdmin) is a Windows-based GUI application that allows you to perform database administration tasks on a Teradata Database. It provides access to the Teradata Database Data Dictionary. Teradata Archive/Recovery Utility (ARC) is a command line utility that writes and reads sequential files on a Teradata client system to archive, restore, recover, and copy data in a Teradata Database table. Through its associated script language, it also provides an interface between the Teradata backup applications solutions and the Teradata Database. Note: Teradata Archive/Recovery Utility is included to support the Teradata thirdparty backup applications. Teradata C Preprocessor2 (PP2) is a command line utility that provides the programmer of a C-based application a simplified way to read and change information stored in a Teradata Database. This utility interprets and expands SQL statements that have been incorporated in an application program. Teradata Call-Level Interface version 2 (CLIv2) is a library of routines that enable an application program to access data in a Teradata Database. Teradata Data Connector API is a component that reads and writes flat files to provide the input/output interface for access modules. For additional information about Teradata Data Connector API, see the following documents: Teradata Tools and Utilities Access Programmer Guide, B Teradata Tools and Utilities for Microsoft Windows Installation Guide 15

16 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Description Teradata Tools and Utilities Access Module Reference, B Teradata FastExport Teradata FastLoad Teradata GSS Client Teradata Index Wizard Teradata JDBC Driver Teradata MultiLoad Teradata Named Pipes Access Module Teradata OLE DB Access Module Teradata Parallel Data Pump Teradata FastExport uses multiple sessions to quickly transfer large amounts of data from tables and views of a Teradata Database to a client-based application. This utility is accessible from the command line or a script. Teradata FastLoad quickly loads large amounts of data to empty tables in a Teradata Database. This utility uses multiple sessions to load data. However, it loads data into only one table in the database per job. This utility is accessible from the command line or a script. Teradata GSS Client is the Teradata implementation of industry-standard Generic Security Services APIs in C language. This utility provides enhanced security services interfaces between Teradata network clients and a Teradata Database. Teradata Index Wizard (TIWiz) is a Windows-based GUI application that allows a Teradata Database administrator to create or identify a workload, perform index analysis for a workload, and then verify and apply index recommendations. This utility helps to increase efficiency and maximize system performance. Teradata JDBC Driver is a library of routines that enables Java applications to connect to a Teradata Database. Teradata MultiLoad (MultiLoad) provides an efficient way to deal with batch maintenance of large databases. Useful for performing fast, high-volume maintenance on multiple tables and views of a Teradata Database. This utility is accessible from the command line or a script. Teradata Named Pipes Access Module is a component that provides an interprocess communication link between a writer process (such as Teradata FastExport) and a reader process (such as Teradata FastLoad). This utility works with the Teradata Parallel Transporter products and with Teradata FastExport, Teradata FastLoad, Teradata MultiLoad, and Teradata Parallel Data Pump. It is accessible from the command line. Teradata OLE DB Access Module is a command line utility that acts as an interface between Teradata load and export utilities (Teradata FastLoad, Teradata FastExport, Teradata MultiLoad, Teradata Parallel Data Pump, Teradata Parallel Transporter, and Basic Teradata Query) and data sources for which an OLE DB provider is available. The access module quickly moves data between an OLE DB data source and a Teradata Database without requiring intermediate storage. Teradata Parallel Data Pump (TPump) is a data loading utility that helps maintain (update, delete, insert, and atomic upsert) the data in a Teradata Database. This utility uses standard Teradata SQL to achieve moderate to high data loading rates. Multiple sessions and multi-statement requests are typically used to increase throughput. It is accessible from the command line. 16 Teradata Tools and Utilities for Microsoft Windows Installation Guide

17 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Teradata Parallel Transporter Base Teradata Parallel Transporter Stream Teradata Performance Monitor Object Teradata Query Scheduler Administrator Teradata Query Scheduler Client Description Teradata Parallel Transporter Base is a package that contains the script-driven interface (Teradata Parallel Transporter) and the application programming interface (Teradata Parallel Transporter API). An object-oriented, scalable, command line client application allows you to perform high-speed, parallel data operations (extraction, loading, and updating) on a Teradata Database. Note: The following Teradata Parallel Transporter Operators are installed as part of the Teradata Parallel Transporter Base: DataConnector Operator DDL Operator Export Operator FastExport OUTMOD Adapter Operator FastLoad INMOD Adapter Operator Load Operator MultiLoad INMOD Adapter Operator ODBC Operator Operator Support Library OS Command Operator Schema Mapping Operator SQL Inserter Operator SQL Selector Operator Teradata Parallel Transporter API Teradata Parallel Transporter ICU Library Teradata Parallel Transporter Wizard Update Operator Teradata Parallel Transporter Stream (Teradata PT Stream) contains the Teradata Parallel Transporter Stream Operator. Before you install Teradata Parallel Transporter Stream, Teradata Parallel Transporter Base must be installed. The Stream Operator emulates the Teradata Parallel Data Pump utility to perform high-speed DML transactions (SQL INSERT, UPDATE, DELETE, or UPSERT). Transactions are executed in a near-real-time mode on one or more tables in a Teradata Database while queries are performed on those tables. Teradata Performance Monitor Object is a COM object that makes real-time Teradata Database performance information available to a Windows application in a simple object-oriented manner. The data is generally returned as a collection of performance objects. Each object contains many performance-related properties. Teradata Query Scheduler Administrator (TQS Administrator) is a Windowsbased GUI application that enables the database administrator to manage workloads submitted to a Teradata Database. Teradata Query Scheduler Client (TQS Client) is a Windows-based GUI application that allows you to submit scheduled SQL requests to Teradata Query Scheduler Server and view information about scheduled jobs. Teradata Tools and Utilities for Microsoft Windows Installation Guide 17

18 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Teradata Query Scheduler Server Teradata SQL Assistant Teradata Statistics Wizard Teradata Studio Express Teradata System Emulation Tool Teradata Visual Explain Teradata Wallet Teradata WebSphere MQ Access Module Teradata Workload Analyzer Description Teradata Query Scheduler Server (TQS Server) is a Windows service that saves, processes, and executes requests that are scheduled from the Teradata Query Scheduler Client. Teradata SQL Assistant is a Windows-based GUI application that allows you to retrieve, manipulate, and store data from ODBC-compliant database servers. Teradata Statistics Wizard (TSWiz) is a Windows-based GUI application that that can improve the performance of queries and, as a result, improve the efficiency of the entire Teradata Database. This utility can also reduce the time required to collect data and can eliminate the need for frequent customization. Teradata Studio Express formerly known as Teradata SQL Assistant Java Edition, is an information discovery tool that retrieves data from Teradata Database systems and allows the data to be manipulated and stored on the desktop. It is built on top of the Eclipse Rich Client Platform (RCP). This allows the product to take advantage of the RCP framework for building and deploying native GUI applications to a variety of desktop operating systems. Teradata System Emulation Tool is a Windows-based GUI application that emulates (imitates) Optimizer-generated data from a target system, generates query plans, and then imports that information to a test system where queries can be run without impacting the production system. Teradata Visual Explain is a Windows-based GUI application that adds another dimension to the EXPLAIN modifier by depicting the execution plan of complex SQL statements in a simplified manner. It presents a graphical view of the statement broken down into discrete steps that show the flow of data during execution. Teradata Wallet is a package that contains a library and a command line tool (tdwallet) that allows users to securely store private information such as Teradata Database passwords on client computers. The stored information can then be recalled when logging in to a Teradata Database. Teradata WebSphere MQ Access Module is a component that allows Teradata utilities to import data using IBM WebSphere MQ Access Module message queuing middleware. This utility works with the Teradata Parallel Transporter products and with Teradata FastLoad, Teradata MultiLoad, and Teradata Parallel Data Pump. It is accessible from a command line. Teradata Workload Analyzer (TWA) is a Windows-based GUI application that analyzes and generates candidate workloads. This utility provides three major areas of guidance: Recommends workload group definitions (the database administrator guides these definitions based on business knowledge and existing workload mix and characteristics) Recommends appropriate workload goals Recommends mapping of workloads to allocation groups (AGs) and priority scheduler weights 18 Teradata Tools and Utilities for Microsoft Windows Installation Guide

19 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Dependencies Product Teradata Tools and Utilities Dependencies Third-party Dependencies Basic Teradata Query Teradata Named Pipes Access Module.NET Data Provider for Teradata ODBC Driver for Teradata OLE DB Provider for Teradata Shared ICU Libraries for Teradata Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client None None Shared ICU Libraries for Teradata Teradata GSS Client Shared ICU Libraries for Teradata Teradata GSS Client None None None Microsoft.NET Framework Version 3.5 SP1 Redistributable Package or Microsoft.NET Framework Version 4.0 Redistributable Package None Note: During the silent installation of the OLE DB Provider for Teradata package, when the user is part of the administrator group, but not an inbuilt administrator on Windows 7, Windows 2008 R2, or Windows Vista, a User Account Control dialog box appears. The dialog prompts you to allow the program to make changes to the computer. Click OK. None Teradata Administrator ODBC Driver for Teradata Teradata Archive/ Recovery Utility Teradata C Preprocessor2 Teradata Call-Level Interface version 2 Teradata Data Connector API Shared ICU Libraries for Teradata Teradata GSS Client Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Shared ICU Libraries for Teradata Teradata GSS Client None None None None None None Teradata Tools and Utilities for Microsoft Windows Installation Guide 19

20 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata FastExport Teradata FastLoad Teradata Generic Security Services Client Teradata Index Wizard Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client None Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 or ODBC Driver for Teradata Teradata GSS Client None None None None Teradata JDBC Driver None JDK 1.4, JDK 5.0, or JDK 6.0 Note: JDK 5.0 is certified for Windows 32-bit. JDK 5.0 is certified for Windows XP Professional x64 using EM64T. JDK 6.0 is certified for Windows 64-bit. Note: The environment can be downloaded from Java Downloads. Teradata Access Module for JMS Teradata MultiLoad Teradata OLE DB Access Module Teradata Parallel Data Pump None Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client ODBC Driver for Teradata Shared ICU Libraries for Teradata Teradata GSS Client Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client None None None None 20 Teradata Tools and Utilities for Microsoft Windows Installation Guide

21 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata Parallel Transporter Base Teradata Parallel Transporter Stream Teradata Performance Monitor Object Teradata Query Scheduler Administrator Teradata Query Scheduler Client Teradata Query Scheduler Server Teradata SQL Assistant Teradata Statistics Wizard Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Teradata Parallel Transporter Base Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Teradata Query Scheduler Client Install at least one of the following:.net Data Provider for Teradata version or later ODBC Driver for Teradata Note: Teradata SQL Assistant uses ODBC Driver for Teradata or.net Data Provider for Teradata to connect to the Teradata Database. ODBC Driver for Teradata and.net Data Provider for Teradata can be installed concurrently. Shared ICU Libraries for Teradata Java 2 Runtime Environment 1.4.2_06 or later Note: The environment can be downloaded from Java Downloads. Progress DataDirect ConnectXE ODBC driver for Teradata (required only if you will use the ODBC operator) None None Teradata Query Scheduler Administrator has dependencies on TCP/IP and Ethernet drivers. Although the standard networking-enabled Windows installation includes a TCP/IP driver with WinSock support for Windows version 2.0 or later and an Ethernet driver that is compatible with the TCP/IP driver, ensure that these drivers are also on the Windows client system. None None Microsoft.NET Framework Version 3.5 SP1 Redistributable Package or Microsoft.NET Framework Version 4.0 Redistributable Package None Teradata Tools and Utilities for Microsoft Windows Installation Guide 21

22 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata Studio Express Teradata Call-Level Interface version 2 or ODBC Driver for Teradata Teradata GSS Client Java Runtime Environment (JRE) 1.6 or later Note: JRE can be downloaded from Java Downloads. Teradata System Emulation Tool Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 or ODBC Driver for Teradata Teradata GSS Client Teradata Visual Explain Shared ICU Libraries for Teradata Teradata Wallet Teradata WebSphere MQ Access Module Teradata Call-Level Interface version 2 or ODBC Driver for Teradata Teradata GSS Client None Note: If Teradata Call-Level Interface version 2 (CLIv2) is installed before Teradata Wallet and if Teradata Wallet is installed using a different directory prefix than the default /opt, CLIv2 will not be able to use Teradata Wallet. To avoid this situation, do either of the following: Install Teradata Wallet before you install CLIv2 Install Teradata Wallet using the default directory prefix To rectify this situation, reinstall CLIv2. For Teradata Wallet help, at the command prompt enter tdwallet help. For more information about Teradata Wallet, see Security Administration, B None None None Teradata Data Connector API IBM WebSphere MQ 7.5 Note: To display the version of WebSphere that is installed on the system, run the dspmqver command from the command line. Teradata Workload Analyzer Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client None 22 Teradata Tools and Utilities for Microsoft Windows Installation Guide

23 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Dependent Products During installation of Teradata Tools and Utilities, the following dependent products are automatically installed: Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata Generic Security Services Client System Requirements Note: You must have administrator privileges for the computer you will install the software on. Note: The client computer must be able to communicate with a network-attached Teradata Database that is using the TCP/IP protocol with Winsock version 2.0 support. To find out which version of Teradata Database is compatible with Teradata Tools and Utilities, refer to Teradata Tools and Utilities Release Definition, B Table 2: Hardware Specifications for Client and Server Systems Component CPU RAM Disk space, free Video display resolution Network card Media drive Operating system Specification 1.5 GHz Pentium 4 (2.0 GHz recommended) 1 GB (2 GB recommended) 800 MB minimum 1024 x 768 minimum required required For a list of supported operating systems, refer to Teradata Tools and Utilities Supported Platforms and Product Versions, B Teradata Tools and Utilities for Microsoft Windows Installation Guide 23

24 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD 24 Teradata Tools and Utilities for Microsoft Windows Installation Guide

25 CHAPTER 2 Uninstalling Software About Uninstalling Previous Versions of Teradata Tools and Utilities Before you install a new version of Teradata Tools and Utilities products, you must uninstall all existing Teradata Tools and Utilities products. Note: If you need to reinstall v14.10, you must use the Add/Remove Programs applet to uninstall the existing instance of the product. For more information, see Interactively Uninstalling Teradata Tools and Utilities. Note: Before you uninstall the Teradata Generic Security Services Client package, see About Retaining Existing Files for TeraGSS Client Package for special considerations. About Retaining Existing Files for TeraGSS Client Package Before you uninstall any older versions of the Teradata Generic Security Services Client package in preparation for installing a new version, determine whether to retain any of the files for the old version. You might need to retain existing files if you need to do either of the following: Return to an older version of the client package later for client compatibility with an older version of the Teradata Database system: If you require such compatibility, you need to retain the entire set of client package files for the older version(s), rather than uninstall them. Then you can use the version switching tool (tdgssversion) to switch from the new version to an older version to allow access to a compatible older Teradata Database system. For information on using the tdgssversion tool, refer to Security Administration, B Retain custom configuration information in the TdgssUserConfigFile.xml file and transfer it to the new version of the client package: If you do not need the version compatibility mentioned above, simply copy the configuration file for the old version and make the corresponding changes to the configuration file for the new version. For information on accessing and making changes to the TdgssUserConfigFile.xml file, refer to Security Administration, B Teradata Tools and Utilities for Microsoft Windows Installation Guide 25

26 Chapter 2 Uninstalling Software Generating a List of Installed Products Generating a List of Installed Products Note: The application that generates the list of products is available in Teradata Tools and Utilities version 14.10, so version must be installed in order to use this application. However, when you run the application, any version of products that are installed will be listed. 1 Start the application that generates a list of products using either of the following methods: Method From the Start menu From a command prompt Procedure a. Choose Start > All Programs > Teradata Client version > Teradata List Products. Alternatively, in the \Windows\TTU\version\ folder, double-click TTUListProducts.exe. a. Open a command prompt. b. Change directory to the \Windows\TTU\ folder (or to the appropriate folder on the physical media): cd Windows\TTU\ c. Run the following command: TTUListProducts.exe -s -f filename Options: -s causes the application to run in silent mode -f filename allows you to specify the name of the output file /help displays information about how to use the command You can specify -s and -f filename at the same time. A file named TTUListProductstimestamp.txt is created on the Desktop, where timestamp is the time (MM-DD-YYYY_HHMMSS) the file was created. It contains a list of all of the Teradata Tools and Utilities products that are installed on the system. Note: If you started the application from a command prompt and if you used the -f filename option to specify the name of the output file, the filename matches what you specified. Silently Uninstalling Teradata Tools and Utilities Uninstallation Script Prerequisites Note: Use the uninstall_ttu.vbs script to uninstall pre products. To uninstall products, use the Add/Remove Programs applet. 26 Teradata Tools and Utilities for Microsoft Windows Installation Guide

27 Chapter 2 Uninstalling Software Silently Uninstalling Teradata Tools and Utilities To run the uninstall_ttu.vbs script, the following software is required on the target machine. Windows Installer version must be 3.0 or above. To see the version of Windows Installer, enter the msiexec command at the command prompt. Windows Script Host (WSH) version must be 5.6 or above. To see the version of Windows Script Host, enter the cscript command at the command prompt. Uninstallation Script Overview Note: It is not necessary to uninstall previous versions of Teradata Wallet before you install another version of it. Before you install a new version of Teradata Tools and Utilities packages, you must use the uninstallation script to uninstall previous versions of the packages. The script is on the installation media: \Windows\uninstall_TTU.vbs It creates a log file that contains a record of all of the steps taken during execution. %TEMP%\uninstall_script_timestamp.log msi logging is turned on during package installation from the media. The msi uninstallation log files are stored in the %TEMP% folder in the following file format: uninstall_package_name_package_version.log These logs provide useful information to support personnel if any issues are observed in the uninstallation of Teradata Tools and Utilities packages. Run the uninstallation script before you do any of the following: install a new version of a package install a specific version of a package (a version other than the latest version) decommission Teradata Tools and Utilities software on a particular system Note: In order to use Teradata Wallet, the version of the product that uses Teradata Wallet and the version of Teradata Wallet must match. This applies to the following products: Teradata Call-Level Interface version 2 ODBC Driver for Teradata When you run the script, you can specify individual packages to be uninstalled. Teradata recommends that you uninstall the dependency products (CLIv2, PIOM, TDICU, TDODBC, and TeraGSS) last; however they can be uninstalled individually regardless of the order. Caution: If a dependency product is uninstalled without reinstalling a new version, the products that depend on that product stop functioning. For example, if CLIv2 is uninstalled, all products that depend on CLIv2 stop functioning. In order for the script to run, the command must include the PRODUCT parameter. Without it, the script displays usage information. The script supports two parameters: /PRIORTOVERSION Teradata Tools and Utilities for Microsoft Windows Installation Guide 27

28 Chapter 2 Uninstalling Software Silently Uninstalling Teradata Tools and Utilities /FORCE As an argument to the script, a version can be specified using the /PRIORTOVERSION parameters (for example: /PRIORTOVERSION: ). The uninstallation script only uninstalls versions of the specified packages that are earlier than the version specified in the / PRIORTOVERSION parameter. When the /PRIORTOVERSION parameter is not specified, the default value is /PRIORTOVERSION: The default behavior handles uninstallations of Teradata Tools and Utilities packages, except corrupted installations which are handled using the /FORCE parameter. When this parameter is specified, the uninstallation script performs an extensive registry search for all versions and components that were installed by a particular Teradata Tools and Utilities package. If the registry entries are found, the script deletes them. This parameter should be used with care because it takes time to search the registry for versions and components of a package. If multiple packages are passed as arguments, the script can take a long time to run. When both parameters are specified, the /FORCE:TRUE parameter performs uninstallation and cleanup of only the versions of the packages that are earlier than those specified using the /PRIORTOVERSION parameter. The script uses system packaging commands to uninstall packages, so it must be executed by an admin user (or by someone with admin privileges). Using a Script to Silently Uninstall Teradata Tools and Utilities 1 Run the uninstall_ttu.vbs script. Command cscript uninstall_ttu.vbs cscript uninstall_ttu.vbs PRODUCT cscript uninstall_ttu.vbs ALL Description Displays usage information Uninstalls the product(s) that you specify [14.10 only] Uninstalls all products PRODUCT One or more products that will be uninstalled The values of the packages must be listed in their order of dependency as specified in the table below. The values are case sensitive. Example of uninstalling BTEQ and its dependencies: cscript uninstall_ttu.vbs BTEQ PIOM CLIv2 TDICU TERAGSS Example of uninstalling SQLA and its dependencies: cscript uninstall_ttu.vbs SQLA TDODBC TDICU TERAGSS TDNETDP Table 3: Products and their Parameter Values Products are listed in order of uninstallation (the reverse order from installation). 28 Teradata Tools and Utilities for Microsoft Windows Installation Guide

29 Chapter 2 Uninstalling Software Silently Uninstalling Teradata Tools and Utilities Note: Teradata Parallel Transporter Base and Teradata Parallel Transporter Stream are part of Teradata Tools and Utilities All of the other Teradata Parallel Transporter products that are listed in the table are legacy products (they are part of earlier versions of Teradata Tools and Utilities). They are listed in case you need to uninstall them. Product Name [14.10 only] (All products) ALL Teradata Wallet Teradata Parallel Transporter Selector Operator Teradata Parallel Transporter OS Command Operator Teradata Parallel Transporter ODBC Operator Teradata Parallel Transporter Inserter Operator Teradata Parallel Transporter DDL Operator Teradata Parallel Transporter Data Connector Operator Teradata Parallel Transporter Operator Support Library Teradata Parallel Transporter ICU Teradata Parallel Transporter Stream Operator Teradata Parallel Transporter Update Operator Teradata Parallel Transporter Export Operator Teradata Parallel Transporter Load Operator Teradata Parallel Transporter Infrastructure Teradata Parallel Transporter API Teradata Parallel Transporter Base Teradata Parallel Transporter Stream Teradata Administrator Teradata Workload Analyzer Teradata Query Scheduler Client Teradata Query Scheduler Server Teradata Query Scheduler Administrator Teradata Performance Monitor Object Teradata Statistics Wizard Teradata Index Wizard Teradata Visual Explain Teradata System Emulation Tool Parameter Value TDWALLET TPTSELECTOP TPTOSCMDOP TPTODBCOP TPTINSERTOP TPTDDLOP TPTDATACONOP TPTOSL TPTICU TPTSTREAMOP TPTUPDATEOP TPTEXPORTOP TPTLOADOP TPTINFRA TPTAPI TPTBASE TPTSTREAM TDADMIN TWA TQSCLIENT TQSSERVER TQSADMIN MONITOROBJ TSWIZ TIWIZ VECOMP TSET Teradata Tools and Utilities for Microsoft Windows Installation Guide 29

30 Chapter 2 Uninstalling Software Silently Uninstalling Teradata Tools and Utilities Product Name Teradata SQL Assistant Teradata Access Module for JMS Teradata OLE DB Access Module Teradata WebSphere MQ Access Module Teradata Named Pipes Access Module Teradata C Preprocessor2 OLE DB Provider for Teradata Teradata Archive/Recovery Utility Teradata Parallel Data Pump Teradata FastExport Teradata MultiLoad Teradata FastLoad Basic Teradata Query Teradata Data Connector API ODBC Driver for Teradata.NET Data Provider for Teradata Teradata Call-Level Interface version 2 Teradata Wallet Shared ICU Libraries for Teradata Teradata Generic Security Services Client package Parameter Value SQLA JMSAXSMOD OLEDBAXSMOD MQAXSMOD NPAXSMOD SQLPP TDOLEDB ARC TPUMP FASTEXP MLOAD FASTLD BTEQ PIOM TDODBC TDNETDP CLIv2 TDWALLET TDICU TERAGSS PRIORTOVERSION Removes products prior to a specified version For example, if you are installing BTEQ from Teradata Tools and Utilities and you need to uninstall packages prior to this version (for example, 14.00, 13.10, or 13.0), enter the following command: cscript uninstall_ttu.vbs BTEQ PIOM CLIv2 TDICU TERAGSS / PRIORTOVERSION: The number parameter must contain all four pairs of digits, and can be specific enough to remove all packages before, for example, Typically the last two pair of digits would just be FORCE Removes all traces of the product(s) by force The default is /FORCE:FALSE. If you specify /FORCE:TRUE, the installation process performs a thorough investigation of the registry for all known product keys and removes all traces. The process can take a long time. It is recommended that you use the /FORCE:TRUE 30 Teradata Tools and Utilities for Microsoft Windows Installation Guide

31 Chapter 2 Uninstalling Software Silently Uninstalling Teradata Tools and Utilities option only if the default /FORCE:FALSE option did not successfully uninstall the products that you specified. For example, to force uninstallation of BTEQ, enter the following command: cscript uninstall_ttu.vbs BTEQ PIOM CLIv2 TDICU TERAGSS / FORCE:TRUE Using a Batch File to Silently Uninstall Teradata Tools and Utilities You can use a single DOS command to silently uninstall Teradata Tools and Utilities products. 1 Close all active Windows programs and disable any virus protection software running on the client computer. 2 Open a command prompt. 3 Change directory to the folder that contains the silent_uninstall.bat file. 4 Enter the appropriate command to uninstall the products. To uninstall all products: silent_uninstall.bat ALL To uninstall fewer than all products: silent_uninstall.bat "PRODUCT" For a list of PRODUCT parameter values and other details about the command syntax to run the batch file, see Product Parameter Values for Use With Batch Files. Product Parameter Values for Use With Batch Files You can use batch files to silently uninstall and install Teradata Tools and Utilities products. The command to run the batch file must include a value for the PRODUCT parameter. Table 4: Product Parameter Values Name of Product Suite Name of Product Parameter Value Base.NET Data Provider for Teradata TDNETDP Basic Teradata Query Teradata Access Module for JMS Teradata Administrator Teradata FastExport Teradata FastLoad Teradata MultiLoad Teradata Named Pipes Access Module BTEQ JMSAM TDAdmin FastExport FastLoad MultiLoad NamedPipesAM Teradata Tools and Utilities for Microsoft Windows Installation Guide 31

32 Chapter 2 Uninstalling Software Silently Uninstalling Teradata Tools and Utilities Name of Product Suite Name of Product Parameter Value Teradata OLE DB Access Module Teradata C Preprocessor2 Teradata Parallel Data Pump Teradata Parallel Transporter Base Teradata Parallel Transporter Stream Teradata SQL Assistant Teradata Wallet Teradata WebSphere MQ Access Module OLEDBAM Preprocessor TPump TPTBase TPTStream SQLA TDWallet Database Management Basic Teradata Query BTEQ Teradata Index Wizard Teradata Performance Monitor Object Teradata Statistics Wizard Teradata Query Scheduler Administrator Teradata Query Scheduler Client Teradata Query Scheduler Server Teradata System Emulation Tool Teradata Visual Explain Teradata Wallet Teradata Workload Analyzer WebsphereAM IndexWizard PMonObject StatWizard TQSAdmin TQSClient TQSServer TSET VisualExplain TDWallet TWA Tape Storage Management Teradata Archive/Recovery Utility ARC Teradata C Preprocessor2 Teradata Wallet Preprocessor TDWallet Note: For your convenience, a text string that contains a set of parameter values for each product in a suite is in the following table. You can copy the appropriate text string for use with batch file commands. Name of Product Suite Base Database Management Tape Storage Management Text String (set of parameter values) BTEQ,FastExport,FastLoad,JMSAM,MultiLoad,NamedPipes AM,OLEDBAM,Preprocessor,SQLA,TDAdmin,TDNETDP,T DWallet,TPTBase,TPTStream,TPump,WebsphereAM BTEQ,IndexWizard,PMonObject,StatWizard,TDWallet,TQSA dmin,tqsclient,tqsserver,tset,twa,visualexplain ARC,Preprocessor,TDWallet The command syntax for running a batch file is as follows: 32 Teradata Tools and Utilities for Microsoft Windows Installation Guide

33 Chapter 2 Uninstalling Software Interactively Uninstalling Teradata Tools and Utilities batch_file_name "PRODUCT" where batch_file_name is the name of the batch file: silent_uninstall.bat silent_install.bat and where PRODUCT is a set of parameter values associated with the suite of products you are uninstalling. The parameter values are case-sensitive. Be sure to include the quote marks (""). Separate the parameter values with a comma, but do not include a space. For example, to install the products that are part of the Tape Storage Management suite, use the following command: silent_uninstall.bat "ARC,Preprocessor,TDWallet" Note: When you run a batch file, all of the dependent products are handled automatically (they are uninstalled or installed, depending on whether you are uninstalling products or installing products). You do not have to specify their parameter values. Interactively Uninstalling Teradata Tools and Utilities 1 Open the Add/Remove Programs applet. Tip: To open the applet, open a command prompt and type APPWIZ.CPL. 2 Uninstall the Teradata Tools and Utilities products. [pre-14.10] Because of dependencies between Teradata Tools and Utilities products, you must manually uninstall products in a specific order. Uninstall the following products last (after you uninstall all other products) and uninstall them in the order that they are listed. You can uninstall all other Teradata Tools and Utilities products in any order. a. Teradata Query Scheduler Server b. Teradata Query Scheduler Client c. Teradata Parallel Transporter Stream d. Teradata Parallel Transporter Base e. Teradata SQL Assistant f. ODBC Driver for Teradata g..net Data Provider for Teradata h. Teradata Call-Level Interface version 2 i. Shared ICU Libraries for Teradata j. Teradata Generic Security Services Client package [14.10] Teradata Tools and Utilities products are part of one of three suites. When you uninstall a suite, all of the Teradata Tools and Utilities primary products are uninstalled. Dependent products are uninstalled when the last suite is uninstalled. Teradata Tools and Utilities - Base Teradata Tools and Utilities - Database Management Teradata Tools and Utilities - Tape Storage Management Teradata Tools and Utilities for Microsoft Windows Installation Guide 33

34 Chapter 2 Uninstalling Software Interactively Uninstalling Teradata Tools and Utilities 34 Teradata Tools and Utilities for Microsoft Windows Installation Guide

35 CHAPTER 3 Installing New Software About Installing Third-Party Software Some Teradata Tools and Utilities products require the installation of third-party software. Before you install Teradata Tools and Utilities, install all of the required third-party software. You can download most third-party software from the developer's website. Determining the Current Version of.net Framework Prerequisite: You must install Microsoft.NET Framework 3.5 SP1 or later before you install.net Data Provider for Teradata. 1 Determine the current version of Microsoft.NET Framework installed on the system by doing one of the following: Open a command prompt and type APPWIZ.CPL. The version of Microsoft.NET Framework is displayed in the list of installed programs. See the article How to determine which versions and service pack levels of the Microsoft.NET Framework are installed. 2 If the system does not have the correct version installed, download the Microsoft.NET Framework Version 3.5 SP1 Redistributable Package or Microsoft.NET Framework Version 4.0 Redistributable Package. 3 Select the Microsoft.NET Framework Redistributable Package for your platform. 4 Follow recommendations on the installation page for installing Microsoft.NET Framework. Installing Third-Party Software for Teradata Parallel Transporter Base 1 Download and install Java 2 Runtime Environment 1.4.2_06 or later from Java Downloads. 2 Download and install Progress DataDirect ConnectXE ODBC driver for Teradata. Installing Third-Party Software for Teradata Parallel Transporter Wizard The Teradata Parallel Transporter Wizard software must use the 32-bit Java SE Runtime Environment (JRE) version 1.4.2_06 or later on the 32-bit and 64-bit Windows platforms, but the PATH to the JRE is not added automatically. Teradata Tools and Utilities for Microsoft Windows Installation Guide 35

36 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities On the 64-bit Windows platform, the Teradata Parallel Transporter Wizard cannot use the 64-bit JRE version. 1 Download and install the 32-bit JRE from Java SE Downloads on the 32-bit or 64-bit Windows platform. 2 On a 64-bit Windows platform, add the path to the 32-bit JRE java.exe command to the front of the PATH system environment variable. Downloading and Installing Third-Party Software for Teradata SQL Assistant Prerequisite: You must install Microsoft.NET Framework 3.5 SP1 or later before you install Teradata SQL Assistant. 1 Determine the current version of Microsoft.NET Framework installed on the system by doing one of the following: Open a command prompt and type APPWIZ.CPL. The version of Microsoft.NET Framework is displayed in the list of installed programs. See the article How to determine which versions and service pack levels of the Microsoft.NET Framework are installed. 2 If the system does not have the correct version installed, download the Microsoft.NET Framework Version 3.5 SP1 Redistributable Package. 3 Select the Microsoft.NET Framework Redistributable Package for your platform. 4 Follow recommendations on the installation page for installing Microsoft.NET Framework. Installing Third-Party Software for Teradata WebSphere MQ Access Module Note: To display the version of WebSphere that is installed on the system, run the dspmqver command from the command line. 1 Before you run Teradata WebSphere MQ Access Module, download IBM WebSphere MQ 7.5 and install it according to the instructions in the downloaded package. About Installing Teradata Tools and Utilities Note: Before you install Teradata Tools and Utilities products, you must first uninstall all earlier versions of the products (except TeraGSS). This helps prevent problems that might be caused by having different versions of products installed. Note: Client applications can cause a Windows path overrun if the PATH system environment variable or a user environment variable exceeds 1024 characters, causing programs not to run. If the problem is encountered, upgrade the system to the latest service pack for Windows XP or install the Microsoft hotfix to increase the PATH size to 2048 characters. 36 Teradata Tools and Utilities for Microsoft Windows Installation Guide

37 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities Note: For ODBC on all platforms, because the installation process installs both 32-bit and 64-bit versions of the ODBC Driver for Teradata, both the 32-bit and 64-bit versions of Teradata GSS Client must be installed before installing ODBC Driver for Teradata. Teradata Tools and Utilities package files are digitally signed. Interactively Installing Teradata Tools and Utilities Products Note: When you install Teradata Tools and Utilities products from media, all dependent products for your selection are installed in silent mode. On a 64-bit system, both 32-bit and 64-bit versions of the dependent products are installed. 1 Close all active Windows programs and disable any virus protection software running on the client computer. 2 If the installation source files are not on the system disk, insert the appropriate media into the media drive. Note: For a list of products and the media each one resides on, see DVD Contents. 3 In the Welcome to Teradata Tools and Utilities dialog box, click Install Product. Note: If the Welcome dialog box does not appear shortly after the media is inserted, use Windows Explorer to navigate to the main folder of the DVD. Double-click setup.bat to start the installation process. 4 If you want an installation log file to be created, perform the following steps: a b c d e If the Windows installer automatically starts, exit the installer. On the system disk where the source files and folders are located, be sure the folder where the setup.exe file is located is writable. Open a command prompt. On the system disk, change directory to the folder where the setup.exe file is located. Run either of the following commands as appropriate: setup.exe /debuglog A log file named InstallShield.log will be created in the folder where the setup.exe file is located. setup.exe /debuglog"path\filename" where path is the path (absolute or relative) where you want the log file to be created and filename is the name of the log file. Be sure to add the quote marks ("). f Wait for the Windows installer to start. 5 In the Choose Setup Language dialog box, select the desired language, then click Next. Note: English and Japanese are the only languages currently supported. Teradata Tools and Utilities for Microsoft Windows Installation Guide 37

38 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities 6 In the Welcome dialog box, click Next. 7 Read the terms of the software license agreement, accept them (click the appropriate radio button), and then click Next. 8 In the Choose Destination Location dialog box, if the default path shown in the Destination Folder block is acceptable, click Next. (Recommended) Note: To use a destination location other than the default, click Browse, navigate to the location where the files are installed, click OK, then click Next to end the procedure. Note: You must have write access to the destination folder, the Windows root folder, and the Windows system folder. Progress monitors appear during the installation process. No action is required. 9 In the Select Features dialog box, select the products that you want to install. Note: The checkbox for ODBC Driver for Teradata is always selected and you cannot deselect it because this product is always installed. 10 Choose whether you want the installation process to uninstall previous versions of the following products: Teradata Administrator Teradata Index Wizard Teradata Performance Monitor Object Teradata Query Scheduler Teradata SQL Assistant Teradata Statistics Wizard Teradata System Emulation Tool Teradata Visual Explain Teradata Workload Analyzer At the bottom of the Select Features dialog box, the Uninstall previous versions checkbox is selected by default. If you leave it selected, these products will be uninstalled. If you deselect it, these products will remain on the system. 11 Click Install. 12 When the installation is complete, click Finish. 13 Click Exit to dismiss the Welcome dialog box. 14 Remove the media from the drive. Note: Beginning with Teradata Tools and Utilities 14.10, you can start Teradata Wallet from the Start menu. About Installation Log Files When you install Teradata Tools and Utilities, you can choose to have a log file named InstallShield.log created. You can use the log file to troubleshoot problems with the installation if necessary. 38 Teradata Tools and Utilities for Microsoft Windows Installation Guide

39 Chapter 3 Installing New Software Installing.NET Data Provider for Teradata To have a log file created, you need to start the installation from the command line (DOS prompt). When you insert the DVD to install Teradata Tools and Utilities, if the Windows installer automatically starts, you will need to exit it, open a command line window, and run the setup.exe command with the /debuglog parameter. Silently Installing Teradata Tools and Utilities Products You can use a single DOS command to silently install all Teradata Tools and Utilities products. 1 Close all active Windows programs and disable any virus protection software running on the client computer. 2 Uninstall previous versions of the Teradata Tools and Utilities software. 3 If the installation source files are not on the system disk, insert the appropriate media into the media drive. Note: For a list of products and the media each one resides on, see DVD Contents. 4 Open a command prompt. 5 If the installation source files are not on the system disk, change directory to the media drive. 6 Change directory to \Windows\TTU\. 7 Run the batch file: silent_install.bat "PRODUCT" For a list of PRODUCT parameter values and other details about the command syntax to run the batch file, see Product Parameter Values for Use With Batch Files. Note: Some products include a 32-bit version and a 64-bit version. On a 32-bit system, only the 32-bit version of the product is installed. On a 64-bit system, both versions of the product are installed. Note: Beginning with Teradata Tools and Utilities 14.10, you can start Teradata Wallet from the Start menu. Related Topics About Uninstalling Previous Versions of Teradata Tools and Utilities, on page 25 Installing.NET Data Provider for Teradata About Installing.NET Data Provider for Teradata When you install.net Data Provider for Teradata, you must perform several tasks: 1. Review security requirements for using Microsoft.NET Framework. 2. Check that the required version of Microsoft.NET Framework is installed on your computer. Teradata Tools and Utilities for Microsoft Windows Installation Guide 39

40 Chapter 3 Installing New Software Installing.NET Data Provider for Teradata 3. Install.NET Data Provider for Teradata from the following media: Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD 4. Verify the installation. The.NET Data Provider for Teradata has no dependencies on other Teradata Tools and Utilities client products. About Security Requirements for.net Data Provider for Teradata The Microsoft Developer Network Library provides extensive documentation for Microsoft.NET Framework. The following topics are recommended reading before you start developing applications to access the Teradata Database with Microsoft.NET Framework, Microsoft Visual Studio, and.net Data Provider for Teradata: ADO.NET Specification and.net Data Providers at ADO.NET Overview FullTrust permission set at Security in the.net Framework Additional security information at Administering Security Policy Known Issues for.net Data Provider for Teradata The following installation issues are recognized for.net Data Provider for Teradata. Suggestions are provided for working around the installation issues. Installing a newer version of.net Data Provider for Teradata without first uninstalling the older version, a side-by-side installation, is not recommended. If you uninstall any version of.net Data Provider for Teradata after a side-by-side installation, the registry key HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\.NETFramework \AssemblyFolders\Teradata Data Provider is removed. In addition, Microsoft Visual Studio no longer lists.net Data Provider for Teradata in the AddReference dialog box. To resolve this uninstallation issue after a side-by-side installation, do the following: 1. Open the Add/Remove Programs applet. 2. In the list of installed programs, do one of the following for.net Data Provider for Teradata depending on the Windows version: Click Change, select Repair, and click Next Right-click the item and click Repair Use the FullTrust permission set of Microsoft.NET Framework to run.net Data Provider for Teradata. Security in the.net Framework provides more information about the FullTrust permission set. For Microsoft Visual Studio 2008, note the following integration issues: TableAdapter Query Configuration Wizard does not generate correct parameters for the INSERT Query type. Visual Studio 2008 Dataset bug provides more information about this issue. TdDataAdapter Configuration Wizard does not generate unique names for commands. The wizard always generates the names SelectCommand, InsertCommand, 40 Teradata Tools and Utilities for Microsoft Windows Installation Guide

41 Chapter 3 Installing New Software Installing.NET Data Provider for Teradata UpdateCommand, and DeleteCommand for the corresponding instances of the TdCommand class. To configure more than one TdDataAdapter, change the name of auto-generated commands to prevent conflict with the command names generated for the first instance of TdDataAdapter. For example, if the first instance of TdDataAdapter uses the name SelectCommand, rename the second instance to SelectCommand1. Uninstalling.NET Data Provider for Teradata It is recommended to uninstall previous versions of.net Data Provider for Teradata before installing the most recent version. 1 Open the Add/Remove Programs applet. Tip: To open the applet, open a command prompt and type APPWIZ.CPL. 2 If.NET Data Provider for Teradata appears in the list of installed programs and is older than the version you are installing, right-click the entry and select Uninstall or Change/ Remove, depending on the Windows version. 3 In the.net Data Provider for Teradata - InstallShield Wizard dialog box, select Remove and click Next. 4 In the Maintenance Complete dialog box, click Finish. Installing Third-Party Microsoft.NET Framework Prerequisite: You must install Microsoft.NET Framework 3.5 SP1 or later before you install.net Data Provider for Teradata. 1 Determine the current version of Microsoft.NET Framework installed on the system by doing one of the following: Open the Add/Remove Programs applet. The version of Microsoft.NET Framework is displayed in the list of installed programs. See the article How to determine which versions and service pack levels of the Microsoft.NET Framework are installed. 2 If the system does not have the correct version installed, download the Microsoft.NET Framework Version 3.5 SP1 Redistributable Package or Microsoft.NET Framework Version 4.0 Redistributable Package. 3 Select the Microsoft.NET Framework Redistributable Package for your platform. 4 Follow recommendations on the installation page for installing Microsoft.NET Framework. Downloading.NET Data Provider for Teradata Prerequisite: You must be a registered user of Teradata Developer Exchange before you can download installation files for.net Data Provider for Teradata. Teradata Tools and Utilities for Microsoft Windows Installation Guide 41

42 Chapter 3 Installing New Software Installing.NET Data Provider for Teradata The executable file for.net Data Provider for Teradata, along with a README in text format and a.zip archive of help files in.chm format, are available for download from Teradata Developer Exchange. 1 Go to.net Data Provider for Teradata download files. 2 Click Sign In to log on to Teradata Developer Exchange. If you are not a registered user for the site, click the create an account link and complete the forms to register. 3 Click the link to download the executable file tdnetdp windows_indep.version.exe. 4 Accept the license agreement. 5 [Optional] Click the link to download a.zip archive of the help files. 6 Accept the license agreement. 7 [Optional] Click the link to view the README in the browser. The README provides detailed information about this version of.net Data Provider for Teradata as well as information on security requirements, supported platforms, development environments, and versions of the Teradata Database. Installing.NET Data Provider for Teradata 1 Browse to the installation file tdnetdp windows_indep.version.exe that you downloaded. 2 Double-click the executable to launch the installer. 3 If the User Account Control dialog box prompts you to allow the program to make changes to the computer, click Yes. 4 In the Choose Setup Language dialog box, select the desired language, then click Next. Note: English and Japanese are the only languages currently supported. 5 In the Welcome dialog box, click Next. 6 Accept the default Destination Folder or select a different destination folder and click Next. On 32-bit systems, the default installation folder is %PROGRAMFILES%\Teradata \NET Data Provider for Teradata\version\. On 64-bit systems, the folder is %PROGRAMFILES(x86)%\Teradata\NET Data Provider for Teradata\version\. 7 Select one of the following in the Setup Type dialog box: Complete to install all program files for.net Data Provider for Teradata. Custom to install all program files for.net Data Provider for Teradata and include the following optional features: 42 Teradata Tools and Utilities for Microsoft Windows Installation Guide

43 Chapter 3 Installing New Software Installing.NET Data Provider for Teradata Feature Description Notes Microsoft Visual Studio 2010 Integration Microsoft Visual Studio 2008 Integration Publisher Policy If Microsoft Visual Studio 2010 is installed on the system,.net Data Provider for Teradata is integrated into Microsoft Visual Studio. If Microsoft Visual Studio 2008 is installed on the system,.net Data Provider for Teradata is integrated into Microsoft Visual Studio. If Microsoft SQL Server Business Intelligence Development Studio is also installed on the system,.net Data Provider for Teradata is also integrated into the Development Studio. A publisher policy assembly configures the policy that is used when the Microsoft.NET Framework runtime binds to an assembly. The publisher policy assembly is installed into the Global Assembly Cache. Integration with Microsoft Visual Studio products is selected by default if the installer detects that they are on the system. You can clear the option to integrate.net Data Provider for Teradata with Microsoft Visual Studio if integration is not required. When integration is not selected, the installation time is shortened. The Publisher Policy feature is selected by default. Leave Publisher Policy selected if you are upgrading a previous version of.net Data Provider for Teradata or other applications are installed that are dependent on an earlier version of.net Data Provider for Teradata. Clear Publisher Policy if no previous installations of.net Data Provider for Teradata exist on the system and no other applications are dependent on an earlier version of.net Data Provider for Teradata. Suppose you upgrade from version to version of.net Data Provider for Teradata and you bind all existing applications to the version. You must place the publisher policy assembly policy. 1.2.Teradata.Client.Provider.dll in the Global Assembly Cache to redirect (bind) an existing application built with the version of.net Data Provider for Teradata to the version. 8 Click Install in the Ready to Install the Program dialog box. 9 [Optional] To display the readme file, select Show the readme file in the InstallShield Wizard Complete dialog box. 10 Click Finish to complete the installation. Verifying Installation of the.net Data Provider for Teradata The complete installation of.net Data Provider for Teradata includes an unsupported adhoc query tool NQuery.exe. Use this tool to test successful installation of.net Data Provider for Teradata and to verify connection to a Teradata Database. 1 Navigate to %PROGRAMFILES%\Teradata\NET Data Provider for Teradata \version\samples\bin\ or %PROGRAMFILES(x86)%\Teradata\NET Data Provider for Teradata\version\Samples\Bin\, depending on the Windows platform. Teradata Tools and Utilities for Microsoft Windows Installation Guide 43

44 Chapter 3 Installing New Software About Teradata Developer Exchange 2 Double-click NQuery.exe. 3 Select Connection > Connect. 4 Select.NET Data Provider for Teradata for the Data Provider. 5 Enter values in the Connection String box. The connection string is a semicolon-separated list of name=value pairs. It uses the format Data Source = system_name ; User Id = username ; Password = password ; where: Data Source = system_name (the tdpid of the Teradata Database system) User Id = username (the logon name by which the user of this client computer accesses the Teradata Database) Password = password, the password for the username For example, to connect to database vixen with user name jackieo and password svnglass3s, type: Data Source = vixen ; User Id = jackieo ; Password = svnglass3s ; 6 Click Connect. 7 Type Select Date; in the SQL Command pane and click Execute. The Teradata Database that you connect to returns the current system date in the Command Result pane. 8 Click Connection > Disconnect. 9 Click File > Exit. About Teradata Developer Exchange Some Teradata Tools and Utilities products can be downloaded from the Teradata Developer Exchange Downloads page. Note: Products downloaded from the Teradata Developer Exchange Downloads page are intended to be used only for connecting to Teradata Database via non-teradata products. They are not intended to be used for updating the Teradata Tools and Utilities suite of products available on DVD. Products Available from Teradata Developer Exchange Note: Products and versions of them available from Teradata Developer Exchange Downloads are subject to change. This list is limited to Teradata Tools and Utilities applications. Connectivity Teradata Call-Level Interface version 2 suite (includes Teradata GSS Client and Teradata International Components for Unicode) Teradata JDBC Driver Teradata JMS Universal Connector 44 Teradata Tools and Utilities for Microsoft Windows Installation Guide

45 Chapter 3 Installing New Software About Teradata Developer Exchange.NET Data Provider for Teradata ODBC Driver for Teradata suite (includes Teradata GSS Client and Teradata International Components for Unicode) OLE DB Provider for Teradata Note: Download and install the Teradata Call-Level Interface version 2 suite to obtain the dependent packages for OLE DB Provider for Teradata. Tools Teradata Plug-in for Eclipse Teradata Studio Express Teradata Wallet Downloading a Product from the Teradata Developer Exchange 1 Go to Teradata Developer Exchange Downloads. The Teradata Developer Exchange Downloads page with a list of selectable products appears. 2 Click the product name or the platform next to the product name. The list of available downloads by software version and processor or platform appears. 3 Click the software package or text file to download. 4 You may be asked to enter a user name and password or to create a user name and password. 5 Read the License Agreement, then click I Agree. A page with a link to the Download file appears. 6 If a readme file is included, click on the readme file link and read and print any special download or installation instructions before continuing. 7 Return to the DOWNLOADS page. 8 Click the package to download. This is typically a.tar,.tar.gz, or.zip file. 9 Click Save. 10 Select a location where to save the file and click Save. The file is saved to the location chosen. Installing Products Downloaded from Teradata Developer Exchange Note: On 64-bit systems, when you install TTU from media, the 32-bit version and the 64- bit version of the product is installed. However, when you install Teradata Tools and Utilities from packages that you downloaded from Teradata Developer Exchange, only the version of the product you downloaded (32-bit or 64-bit) is installed. 1 Go to the location where you saved the compressed file. Teradata Tools and Utilities for Microsoft Windows Installation Guide 45

46 Chapter 3 Installing New Software About Teradata Software Server (Patch Server) 2 Read the readme file to see if it contains additional installation instructions or a list of dependencies. 3 Uninstall the previous version of software. 4 Extract the package files to the folder. 5 Run the setup.exe file to install the software. Note: Install any dependencies listed first. About Teradata Software Server (Patch Server) To ensure the highest quality and best performance of Teradata Tools and Utilities products, download the most recent critical post-production updates from Teradata Software Server. Downloading Updated Software Packages To ensure the highest quality and best performance of Teradata Tools and Utilities products, you should download the most recently updated software packages from the Teradata Software Server. 1 Log on to Your Service, 2 Click Software Downloads. 3 In the Home tab, click the Teradata Client button. 4 Click the platform. 5 In the Teradata Client Released Software pane, select the Software base. 6 Filter the list of available software. Select Current to display the most recent release. Select All to display all versions of the software. 7 Click Submit. 8 Select the suite you want to download. 9 Select the Download Type and the Download Readme Files if desired, enter your User Name and , then click Submit. 10 Click Download. 11 Click Save. 12 Specify a location to save the downloaded files and click Save to start the download. Installing Updated (Patched) Software Packages 1 Go to the location where you saved the compressed file. 46 Teradata Tools and Utilities for Microsoft Windows Installation Guide

47 Chapter 3 Installing New Software Installing Third-Party Windows Help Program 2 Read the readme file to see if it contains additional installation instructions or a list of dependencies. 3 Extract the suite file to a folder. 4 Run the setup.exe file to install the software. Installing Third-Party Windows Help Program This task must be performed for all clients that are running Windows 7, Windows 8, Windows Vista, or Windows Server The application is necessary to run online help files with a.hlp extension. 1 Install Teradata Tools and Utilities software before proceeding. 2 Go to Microsoft Support (Windows Help). 3 In the Search box, type WinHlp32.exe 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. 4 Run the executable. Teradata Tools and Utilities for Microsoft Windows Installation Guide 47

48 Chapter 3 Installing New Software Installing Third-Party Windows Help Program 48 Teradata Tools and Utilities for Microsoft Windows Installation Guide

49 CHAPTER 4 Configuring New Software About Setting Network Parameters The Internet address and the symbolic names for the Teradata Database are considered the network parameters. It is assumed that network software is installed correctly. About Configuring Teradata Call-Level Interface version 2 Note: These same parameters for resolution of host name to IP address also need to be configured for ODBC Driver for Teradata and any other connection driver. Set the following parameters so Teradata Call-Level Interface version 2 will work properly: Network Parameters Setting the correct network parameters guarantees that Teradata Call-Level Interface version 2 communicates with the target Teradata Database. These parameters must be set correctly to use the software. Environment Parameters The environment parameters provide Teradata Call-Level Interface version 2 with parameter file location information, as well as the facility for enabling Teradata Call- Level Interface version 2 to run in parallel mode. Teradata strongly recommends that you set the environment parameters. System Parameters The Teradata Call-Level Interface version 2 system parameters are used internally by Teradata Call-Level Interface version 2 to customize services and features. Setting system parameters is only necessary if there are special requirements that the default setting cannot meet. Verifying the Existence of the hosts File 1 Verify that the hosts file is located in the following folder: %windir%\system32\drivers\etc Teradata Tools and Utilities for Microsoft Windows Installation Guide 49

50 Chapter 4 Configuring New Software Identifying a Teradata Database 2 If you are running a Name Server, verify that the hosts file is on the Name Server and that network software is configured to access the Name Server. The Teradata Tools and Utilities software uses generic TCP/IP GetHostByName services. 3 If not running a Name Server, verify the hosts file contains a list of all systems on the LAN that can be accessed. The Teradata Database must be identified in this file if a system is going to communicate with it. A hosts file exists on each computer system in the network. Identifying a Teradata Database 1 Identify each TCP/IP Communications Processor (COP), Applications Processor (AP), or UNIX node running the Teradata Gateway that the client computer will be communicating to the Teradata Database. In the table below, AP refers to all of the following: TCP/IP Communications Processor (COP) Applications Processor (AP) Node running the Teradata Gateway 2 Make an entry in the hosts file for each TCP/IP Communications Processor (COP), Applications Processor (AP), or UNIX node running the Teradata Gateway. The following table includes the entries to the hosts file. Platform Teradata Database on an AP platform (System 3600) Teradata Database on a V2 computer (UNIX) hosts File Entries APs nodes Adding and Editing AP Entries in the hosts File 1 Once the Application Processor (APs) are identified, use a text editor to open the client hosts file and add or edit the AP entries. Use the following syntax when adding entries to the hosts file: a.b.c.d dbcnamecopn [aliascopn] a.b.c.d The Internet address 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 is 1 to 70 characters in length. The first character must be alphabetic; where the remaining characters can be alphanumeric. The System Parameter Block file, %Program Files%\Teradata\Client 50 Teradata Tools and Utilities for Microsoft Windows Installation Guide

51 Chapter 4 Configuring New Software About Setting Up Environment Parameters COPn \version\clispb.dat, lists dbc as the default dbcname. dbc can be assigned as the dbcname of a Teradata Database with which the client computer communicates. This simplifies network debugging and avoids problems when name servers become available. If the client computer communicates with more than one Teradata Database on the same TCP/IP LAN, use dbc as the dbcname for the more heavily used Teradata Database. Any other names can be used for any remaining Teradata Databases. The parameter that assigns a number to a particular AP that the Teradata Database uses. COP is a fixed string of characters that must always be specified. 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 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 alias name, specifies 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 alias COPn equals n in the corresponding dbcname COPn. For example, a client computer accesses one Teradata Database (named dbc) through two TCP/IP APs with addresses and on the same logical TCP/IP LAN. Each AP is assigned two alias names. The following lines show example entries in the hosts file for the two APs: dbcnode1 dbccop1 tdcop dbcnode2 dbccop2 tdcop2 About Setting Up Environment Parameters Environment parameters allow the runtime environment to be specified for each Teradata Tools and Utilities user. On Windows systems, if system environment parameters are changed, the client computer must be rebooted for the changes to take effect. It is not sufficient to restart the daemon, or to log off and log on again. Defining Paths to System Files 1 Define the path to the Teradata Call-Level Interface version 2 system parameter block file by setting the COPLIB environment variable. COPLIB is the path to the Teradata Call-Level Interface version 2 system parameter block file, clispb.dat. 2 Define the path to the Teradata Call-Level Interface version 2 anomaly log file by setting the COPANOMLOG environment variable. Teradata Tools and Utilities for Microsoft Windows Installation Guide 51

52 Chapter 4 Configuring New Software Setting Up Environment Variables COPANOMLOG is the path to the anomaly log file, a trace log file that displays Teradata Call-Level Interface version 2 activities including network-related error information. This environment variable should be defined only for debugging purposes. Setting Up Environment Variables 1 Open the System Properties dialog box. Tip: To open the dialog box, open a command prompt and type SYSDM.CPL. 2 Click the Advanced tab. 3 Click Environment Variables to add a new variable or edit an existing variable. Speeding Up the CLIv2 Logon Process Increase the speed of the CLIv2 logon process by limiting the number of host name resolution requests issued by the applications. 1 Set an environment variable with the name equal to the machine name with a specified number of COPS available for it. set machine_name=cops machine_name cops name of the name of the Teradata Database system, or tdpid number of COPS 2 Open the System Properties dialog box. Tip: To open the dialog box, open a command prompt and type SYSDM.CPL. 3 Click the Advanced tab. 4 Click Environment Variables and add or edit the machine_name system environment variable. 5 Set the SHOGUN system environment variable to 3 as follows: set SHOGUN=3 Setting SHOGUN=3 causes CLIv2 to issue GetHostByName for SHOGUNCOP1, SHOGUNCOP2, and SHOGUNCOP3 only. If one of the GetHostByName requests fails, the successive requests are not issued. 6 Add or edit the SHOGUN system environment variable. 52 Teradata Tools and Utilities for Microsoft Windows Installation Guide

53 Chapter 4 Configuring New Software Setting Up Port Number, Netrace, and Threadlogging Setting Up Port Number, Netrace, and Threadlogging Note: Before you change the TDMSTPORT system environment variable to use a port number other than the default of 1025, contact Teradata Support to understand the ramifications. 1 Specify the port number nnnn used by the Teradata Tools and Utilities software by setting the TDMSTPORT system environment variable as follows: set TDMSTPORT=nnnn 2 Open the System Properties dialog box. Tip: To open the dialog box, open a command prompt and type SYSDM.CPL. 3 Click the Advanced tab. 4 Click Environment Variables and add or edit the TDMSTPORT system environment variable. 5 Enable Detailed COPANOMLOG Logging by setting up the system environment variable NETRACE as follows: set NETRACE=1 Setting NETRACE=1 enables detailed network information between the client computer and the Teradata Database server. This information is logged in the file defined in the system environment variable COPANOMLOG. 6 Add or edit the NETRACE system environment variable. 7 Enable Multiple COPANOMLOG File Creation by setting up the system environment variable THREADLOGGING as follows: set THREADLOGGING=1 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 are created as coplog.xxx.txt, where xxx is the thread_id in hexadecimal: c:\temp\coplog.1a4.txt c:\temp\coplog.db8.txt c:\temp\coplog.b34.txt etc. Each thread that uses a CLI connection creates its own individual log file. 8 Add or edit the THREADLOGGING system environment variable. About clispb.dat The clispb.dat file (the Teradata Call-Level Interface version 2 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 Teradata Call-Level Interface version 2 internal defaults. Teradata Tools and Utilities for Microsoft Windows Installation Guide 53

54 Chapter 4 Configuring New Software Setting System Parameters Setting System Parameters 1 Edit the clispb.dat file to meet system requirements. For more information, refer to Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems, B About Configuring ODBC Driver for Teradata To use the ODBC Driver for Teradata, you must first configure the ODBC driver and an ODBC data source. Configuring ODBC Driver for Teradata 1 Complete procedures to configure the ODBC Driver for Teradata are included in ODBC Driver for Teradata User Guide, B Configuring Data Source for ODBC Driver for Teradata 1 For information about configuring the data source for ODBC Driver for Teradata, see ODBC Driver for Teradata User Guide, B About Configuring Teradata Query Scheduler Administrator Starting with Teradata Tools and Utilities Release , before using Teradata Query Scheduler Administrator for the first time, you must run the tqssetup.bteq script included in the Teradata Query Scheduler Administrator package. This creates the required scheduling tables on the Teradata Database. Default Communications, as well as Client and Server configuration parameters, are changeable within the program. For more information, refer to the following documents: Teradata Query Scheduler Administrator Guide, B Teradata Query Scheduler User Guide, B Modifying the hosts File Prerequisite: If your site does not use DNS, you must define the IP address and the Teradata Database name to use in the system hosts file on the computer. 1 Locate the hosts file on the computer. This file is typically located in the following folder: %SystemRoot%\system32\drivers\etc 54 Teradata Tools and Utilities for Microsoft Windows Installation Guide

55 Chapter 4 Configuring New Software Configuring Teradata Query Scheduler Client 2 Open the file with a text editor, such as Notepad. 3 Add the following entry to the file: xxx.xx.xxx.xxx ssscop1 where xxx.xx.xxx.xxx is the IP address and where sss is the Teradata Database name. 4 Save the hosts file. Configuring Teradata Query Scheduler Client 1 Starting with Teradata Tools and UtilitiesRelease , before using Teradata Query Scheduler Client for the first time, you must run the tqssetup.bteq script included in the Teradata Query Scheduler Administrator package. This creates the required scheduling tables on the Teradata Database. Default Communications, as well as Client and Server configuration parameters are changeable within the program. For more information, refer to the following documents: Teradata Query Scheduler Administrator Guide, B Teradata Query Scheduler User Guide, B About Configuring Teradata Query Scheduler Server To start the Teradata Query Scheduler Server, you must first configure database logon credentials using the Teradata Query Scheduler Operations Utility. For more information, refer to Teradata Query Scheduler User Guide, B Specifying a Default Teradata Query Scheduler Server Teradata Query Scheduler Viewer temporarily establishes a Teradata Database session using Teradata Call-Level Interface version 2 to validate the logon parameters and find the location of an active Teradata Query Scheduler Server. If Teradata Call-Level Interface version 2 cannot establish a session, or if there is an application that accesses the Teradata Query Scheduler Client library functions directly, a default Teradata Query Scheduler Server location can be configured. 1 Use the Teradata Query Scheduler Client library functions to configure the location. For instructions, see Changing Default Server Information in Teradata Query Scheduler User Guide, B After you configure a default Teradata Query Scheduler Server, begin using the Teradata Query Scheduler Viewer or the Teradata Query Scheduler Operations utility. If you are working with various character sets, continue with Working with Character Sets in the User Guide. To learn how to start using the Teradata Query Scheduler Operations utility, see Working with the Teradata Query Scheduler Operation Utility in the User Guide. To Teradata Tools and Utilities for Microsoft Windows Installation Guide 55

56 Chapter 4 Configuring New Software About Configuring Teradata Query Scheduler Server learn more about the Teradata Query Scheduler Viewer, see Getting Started in the User Guide. Changing Teradata Query Scheduler Server Configurations 1 Click Start > Programs > Teradata Query Scheduler Utilities > Scheduler to open the Teradata Query Scheduler Operations window. 2 Click Configuration > Server. The Server Parameters dialog box displays. 3 Modify the fields as desired: Character Set Select the Teradata session character set to use. On a Kanji system (having KANJI1 database object names), select the KANJISJIS_0S character set. Shared Memory Size (KB) Specify the size of the memory area on this system used to store server information. This memory is shared among all the server processes. Request Processor Processes Specify the number of server processes created for handling client messages. Encrypt Client Data Specify whether client data is encrypted through CLIv2. If selected, encryption provides data security in communications between the Teradata Query Scheduler client and server components over network socket connections. The default setting is blank, meaning data is unencrypted. Select the check box to select encryption. Selecting the Encrypt Client Data option also causes encryption to be used for data passed between the Teradata Query Scheduler server and the Teradata Database. Note: After changing the encryption option, stop and restart both the Teradata Query Scheduler clients and server. Listener Address Select the IP address of the Teradata QS Listener to which remote client systems will connect. Tip: Teradata recommends that the default (topmost) address be selected. An administrator may need to change the selection if, for example, the server system is configured for both IPv4 (default) and IPv6 (non-default) networks, and clients are on the IPv6 network. 4 Click OK to close the Server Parameters dialog box and return to the Teradata Query Scheduler Operations tool. 56 Teradata Tools and Utilities for Microsoft Windows Installation Guide

57 Chapter 4 Configuring New Software Configuring Teradata Administrator Configuring Teradata Administrator After installation, Teradata Administrator must be configured to include the Teradata user name. 1 Navigate to %Program Files%\Teradata\Teradata Administrator version \sql. 2 Edit setup.sql to replace all occurrences of the string User with the Teradata user name and save the file. 3 Execute the query setup.sql. Configuring Teradata Parallel Transporter Editing the Teradata Parallel Transporter Configuration File If you installed Teradata Parallel Transporter Base, the local configuration file twbcfg.ini can be modified to change the location of the checkpoint files. 1 Clear the read-only attribute for the configuration file TPT_install_directory \Teradata\Client\version\Teradata Parallel Transporter \twbcfg.ini. By default, an installation of Teradata Parallel Transporter sets this file to read-only. 2 Use any text editor to edit the default log and checkpoint directories in the configuration file. No reboot is required after making the change in the configuration file. The following are sample default configuration files: 32-bit CheckpointDirectory= 'C:\Program Files\Teradata\Client \14.10\Teradata Parallel Transporter\checkpoint' LogDirectory='C:\Program Files\Teradata\Client\14.10\Teradata Parallel Transporter\logs' 64-bit CheckpointDirectory= 'C:\Program Files (x86)\teradata\client \14.10\Teradata Parallel Transporter\checkpoint' LogDirectory='C:\Program Files (x86)\teradata\client \14.10\Teradata Parallel Transporter\logs' CheckpointDirectory A folder that contains the checkpoint files for Teradata Parallel Transporter jobs. Teradata Parallel Transporter uses checkpoint files to store temporary information needed to restart a job that does not complete successfully. Teradata Tools and Utilities for Microsoft Windows Installation Guide 57

58 Chapter 4 Configuring New Software Configuring Teradata Access Module for JMS LogDirectory A folder that contains the binary logs for Teradata Parallel Transporter jobs. Each Teradata Parallel Transporter job writes a log in the jobs directory. Note: If a change is made to the folder for the log directory and the Teradata Parallel Transporter Wizard is installed, the LOG_DIRECTORY variable in the TPT_install_directory\tptwizard\config\tptwizard.properties file must be changed before running Teradata Parallel Transporter Wizard. Editing the Teradata Parallel Transporter Properties File If the folder for the Log Directory to C:\Logs\Teradata Parallel Transporter version is changed and the Teradata Parallel Transporter Wizard is installed, use the following procedure to update the LOG_DIRECTORY entry in the following file: TPT_install_directory\tptwizard\config\tptwizard.properties 1 Using any text editor, open the tptwizard.properties file. 2 Update the LOG_DIRECTORY line to LOG_DIRECTORY=c:\Program Files \Teradata\Client\version\Teradata Parallel Transporter\logs\\ The folder C:\Logs\Teradata Parallel Transporter version is an example. You can specify a different folder. Note: The folder for the LOG_DIRECTORY entry in the tptwizard.properties file must be separated by double backslashes (\\) and must end with double backslashes (\ \). Note: For information about how to interpret the job log, refer to Teradata Parallel Transporter Reference, B Configuring Teradata Access Module for JMS 1 For instructions on how to configure Teradata Access Module for JMS, see the readme file. To open the readme file, use a text editor such as Notepad. Architecture 32-bit 64-bit File Path %Program Files%\Teradata\Client\version\JMSAXSMOD %Program Files(x86)%\Teradata\Client\version\JMSAXSMOD 58 Teradata Tools and Utilities for Microsoft Windows Installation Guide

59 CHAPTER 5 Verifying the Complete Installation About Verifying the Installation You can verify successful installation of Teradata Tools and Utilities using either or both of the following methods: Run clisamp. This sample CLI program and its makefile are copied to the PC during the installation. Generate a list of installed products. Related Topics Verifying the Installation Using CLI Sample Program, on page 59 Generating a List of Installed Products, on page 26 Verifying the Installation Using CLI Sample Program 1 In the makefile makesamp.win, add the correct paths to the include files. By default the makesamp.win file is located in the following folder: \program-files\teradata\client\version\cliv2\clisamp For information about the program-files variable, see About the program-files Variable in the Default Installation Path. 2 Open a command prompt. 3 Run the makefile to create the executable module clisamp: # nmake -f makesamp.win The default configuration is CFG="clisamp - Win32 Debug". Also supported is CFG="clisamp - Win32 Release". 4 Change directory to the appropriate subfolder: Release Debug 5 Run the sample program by entering one of the following commands: Run the sample program using the default logon information (dbc/ systemfe,service): clisamp Show help for the sample program using the -h option: Teradata Tools and Utilities for Microsoft Windows Installation Guide 59

60 Chapter 5 Verifying the Complete Installation About Verifying the Installation clisamp -h Run the sample program using a user-provided input string: clisamp proddev/dbc,password where proddev is the tdpid, dbc is the user, and password is the password. The program does the following: 1. Logs on using the default logon information (or the user-specified logon information) as shown above. 2. Executes a simple query: SELECT * from dbc.sessioninfo; 3. Writes the results of the query to a CLISAMP.DAT file and displays information similar to the following: clisamp CLIv2 version is version MTDP version is version MOSIOS version is version MOSIDEP version is version OSERR version is version Logging on to --> dbc/systemfe,service writing out to --> CLISAMP.DAT submitting --> select * from dbc.sessioninfo; writing out to --> CLISAMP.DAT Logging off. Note: For information about security and connecting to a Teradata Database, see Security Administration, B Generating a List of Installed Products Note: The application that generates the list of products is available in Teradata Tools and Utilities version 14.10, so version must be installed in order to use this application. However, when you run the application, any version of products that are installed will be listed. 1 Start the application that generates a list of products using either of the following methods: Method From the Start menu From a command prompt Procedure a. Choose Start > All Programs > Teradata Client version > Teradata List Products. Alternatively, in the \Windows\TTU\version\ folder, double-click TTUListProducts.exe. a. Open a command prompt. 60 Teradata Tools and Utilities for Microsoft Windows Installation Guide

61 Chapter 5 Verifying the Complete Installation List of Files Method Procedure b. Change directory to the \Windows\TTU\ folder (or to the appropriate folder on the physical media): cd Windows\TTU\ c. Run the following command: TTUListProducts.exe -s -f filename Options: -s causes the application to run in silent mode -f filename allows you to specify the name of the output file /help displays information about how to use the command You can specify -s and -f filename at the same time. A file named TTUListProductstimestamp.txt is created on the Desktop, where timestamp is the time (MM-DD-YYYY_HHMMSS) the file was created. It contains a list of all of the Teradata Tools and Utilities products that are installed on the system. Note: If you started the application from a command prompt and if you used the -f filename option to specify the name of the output file, the filename matches what you specified. List of Files About the program-files Variable in the Default Installation Path In the list of installed files and folders, the path to the default installation folder (installdir) contains a program-files variable that represents a system environment variable. The following table provides the value (path) for that variable: Package Platform System Environment Variable Name Value (Path) 32-bit 32-bit %ProgramFiles% C:\Program Files 64-bit %ProgramFiles(x86)% C:\Program Files (x86) 64-bit 64-bit %ProgramFiles% C:\Program Files Basic Teradata Query Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. Teradata Tools and Utilities for Microsoft Windows Installation Guide 61

62 Chapter 5 Verifying the Complete Installation List of Files \installdir\bin\ bteq.exe bteqwin.exe bteqwin_enu.chm bteqwin_jpn.chm bteqwin_jpn.dll teqtalk.ico \installdir\btnfy\ btnfyext.c btnfyext.def btnfyext.h btnfyext.mak C:\windows\WinSxS\ Visual C CRT (x86) Visual C MFC (x86) Visual C MFCLOC (x86) Teradata Access Module for JMS Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\jmsaxsmod\ jmsam.jar jmsam_charsets.properties libjmsam.dll readme Named Pipes Access Module Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\axsmod\ np_axsmod.dll np_axsmodenu.dll [64-bit].NET Data Provider for Teradata Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\net Data Provider for Teradata version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ 62 Teradata Tools and Utilities for Microsoft Windows Installation Guide

63 Chapter 5 Verifying the Complete Installation List of Files Readme.txt \installdir\bin\ SchemaLoader.exe SetLogLevel.exe Teradata.Client.Provider.dll Teradata.Client.Provider.xml \installdir\bin\ja\ Teradata.Client.Provider.resources.dll \installdir\config\ LogAllDebug.config LogAllError.config LogAllInfo.config LogAllTraceExternal.config LogAllTraceInternal.config LogAllWarn.config LogOff.config SDKExtensions.xsd TdgssNetConfig.exe TdgssUserConfigFile.xml \installdir\config\ja\ TdgssNetConfig.resources.dll \installdir\help\ COL_TDNETDP.HxC COL_TDNETDP.hxt COL_TDNETDP_A.hxk COL_TDNETDP_D.hxk COL_TDNETDP_F.hxk COL_TDNETDP_K.hxk COL_TDNETDP_N.hxk helpcontentsetup.msha tdnetdp.cab tdnetdp.chm tdnetdp.hxs \installdir\privateassemblies\ policy.1.0.teradata.client.provider.config policy.1.0.teradata.client.provider.dll policy.1.1.teradata.client.provider.config policy.1.1.teradata.client.provider.dll policy.1.2.teradata.client.provider.config policy.1.2.teradata.client.provider.dll policy.12.0.teradata.client.provider.config policy.12.0.teradata.client.provider.dll policy.13.0.teradata.client.provider.config policy.13.0.teradata.client.provider.dll policy.13.1.teradata.client.provider.config policy.13.1.teradata.client.provider.dll policy teradata.client.provider.config Teradata Tools and Utilities for Microsoft Windows Installation Guide 63

64 Chapter 5 Verifying the Complete Installation List of Files policy teradata.client.provider.dll policy teradata.client.provider.config policy teradata.client.provider.dll Teradata.Client.Entity.dll Teradata.Client.VS.dll Teradata.Net.Security.Tdgss.dll \installdir\privateassemblies\ja\ Teradata.Client.VS.resources.dll Teradata.Net.Security.Tdgss.resources.dll \installdir\samples\bin\ NQuery.application NQuery.exe NQuery.exe.config NQuery.exe.maifest \installdir\samples\learningexamples\ readme.doc T20000DP.cs through T21300DP.cs \installdir\tracelog\ Teradata.Client.Entity.dll Teradata.Client.Provider.dll \installdir\tracelog\ja\ Teradata.Client.Provider.resources.dll ODBC Driver for Teradata Files and Folders Note: In the list(s) below, installdir represents the following path: [32-bit platform]: \program-files\teradata\client\version\odbc Driver for Teradata [64-bit platform]\program-files\teradata\client\version\odbc Driver for Teradata nt-x8664 where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ Pbocd0x0.txt Readme.txt tdodbcdsn.vbs tdsql.h \installdir\bin\ tdxodbc \installdir\help\ catalog.css document.css images (folder) odbc_help.htm odbc-1-01.html through odbc-2-6.html 64 Teradata Tools and Utilities for Microsoft Windows Installation Guide

65 Chapter 5 Verifying the Complete Installation List of Files scripts (folder) wwhdata (folder) wwhelp (folder) wwhelp4.jar \installdir\lib\ _unodbc.dll tdata32.dll tdatas32.dll tdprsr32.dll terasso.dll \installdir\samples\c\ adhoc.c error.c getopt.c getopt.h OLE DB Provider for Teradata Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ole DB Provider for Teradata\ tdoledb.h TD_OC.dll TD_OCPR.dll TD_RT.dll TD_TL.dll TDOLEDB.dll TDOLEDB_TEST.udl TDOLEDBR.dll terasso.dll MSVCRT.DLL Shared ICU Libraries for Teradata Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\shared ICU Libraries for Teradata\lib\ icudttd46.dll icuintd46.dll icuiotd46.dll iculetd46.dll iculxtd46.dll Teradata Tools and Utilities for Microsoft Windows Installation Guide 65

66 Chapter 5 Verifying the Complete Installation List of Files icuuctd46.dll Teradata Administrator Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata \Teradata Administrator version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\bin\ ctl3d32.dll history.txt mfc42u.dll msvcr80.dll msvcrt.dll shfolder.dll teradata.syn teradata_sp.syn verify.dat Verify.exe winddi.exe winddi_enu.chm Winddi_enu.dll winddird.txt \installdir\sql\ setup.sql udtistinct.txt udtstruct.txt winddi.def winddix.def XViews.sql Teradata Archive/Recovery Utility Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\bin\ arcmain.exe arcmain.pdb Teradata C Preprocessor2 Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For 66 Teradata Tools and Utilities for Microsoft Windows Installation Guide

67 Chapter 5 Verifying the Complete Installation List of Files information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\bin\ [32-bit] ppcmain.exe \installdir\bin64\ [64-bit] ppcmain.exe \installdir\pp2\ [32-bit] LABSBTEQ PPCLB1 PPCLB2 PPCLB3 PPCLB4 PPCLB5 PPCLB6 PPCLB7 PPCLB8 PPCLB9 ppruntim.dll ppruntim.lib \installdir\pp2_64\ [64-bit] LABSBTEQ PPCLB1 PPCLB2 PPCLB3 PPCLB4 PPCLB5 PPCLB6 PPCLB7 PPCLB8 PPCLB9 ppruntim.dll ppruntim.lib Teradata Call-Level Interface version 2 Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\cliv2 clisamp.c clispb.dat localisation.dll makesamp.win tdusr32.dll wincli32.dll Teradata Tools and Utilities for Microsoft Windows Installation Guide 67

68 Chapter 5 Verifying the Complete Installation List of Files \installdir\cliv2\inc cliv2if.h coperr.h coptypes.h dbcacnx.h dbcarea.h dbcerr.h dbchqep.h mosiif.h nojunk.h parcel.h resource.h wincliv2.h \installdir\cliv2\lib wincli32.lib \installdir\cliv2\userexit CliLgnEx.c CliPPS.c tdusr.def tdusr.rc userexit.mak Teradata Data Connector API Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\bin\ libpm.dll \installdir\inc\ pmdcomt.h pmddamt.h Teradata FastExport Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\bin\ fexp.exe \installdir\fexp\ feimod.c fenotf.c feomod.c 68 Teradata Tools and Utilities for Microsoft Windows Installation Guide

69 Chapter 5 Verifying the Complete Installation List of Files Teradata FastLoad Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\bin\ fastload.exe \installdir\fastload\ blkexit.c blkexit.mak blkexitr.c flnfyext.c Teradata Generic Security Services Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata \Teradata GSS\version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\nt-i386\version\ version \installdir\nt-i386\version\bin\ dumpcfg.exe gethost.exe gssp2ldap.dll gssp2sspi.dll gssp2td1.dll gssp2tdl2.dll ldapcompare.exe ldapdelete.exe ldap.dll ldap.exe ldapmodify.exe ldapmodrdn.exe ldappassword.exe ldapwhoami.exe run_tdgssconfig.bat tdgss.dll tdgssconfig.exe tdgssversion.exe tdlink.exe tdsbind.exe tdssearch.exe tdstcl.exe tests.exe Teradata Tools and Utilities for Microsoft Windows Installation Guide 69

70 Chapter 5 Verifying the Complete Installation List of Files tfclient.exe tfserver.exe \installdir\nt-i386\version\bin\microsoft.vc80.crt\ Microsoft.VC80.CRT.manifest msccm80.dll mdvcp80.dll msvcr80.dll \installdir\nt-i386\version\bin\doc\html\ dumpcfg.html gethost.html ldap_license.html regex_license.html sasl_license.html tdgssconfig.html tdgssversion.html tdlink.html tdsbind.html toc.html xerces_license.html \installdir\nt-i386\version\doc\pod\ dumpcfg.pod gethost.pod ldap_license.pod regex_license.pod sasl_license.pod tdgssconfig.pod tdgssversion.pod tdlink.pod tdsbind.pod toc.pod xerces_license.pod \installdir\nt-i386\version\lclient\etc\ algerrors.h GlobalTypes.xsd ipfilter.actdir.schema ipfilter.edir.schema ipfilter.openldap.schema ipfilter.sunone.schema ldaperrors.h loadtdgsserrors.h spnegoerrors.h sspierrors.h systemdlls.txt SDKExtensions.xsd tdat.actdir.schema tdat.edir.schema tdat.openldap.schema 70 Teradata Tools and Utilities for Microsoft Windows Installation Guide

71 Chapter 5 Verifying the Complete Installation List of Files tdat.sunone.schema td1errors.h td2errors.h tdgssapi.h tdgssdefines.h tdgsserrors.h TdgssConfigFile.xsd TdgssLibraryConfigFile.xml TdgssUserConfigFile.xml \installdir\nt-i386\version\lclient\lib\ loadtgss.lib \installdir\nt-i386\version\lclient\lib\java\ jtests.jar Login.config tdgssdefines.java tdgsstf.jar \installdir\nt-i386\version\lclient\lib\tcl\tds\ dntest.tcl pkgindex.tcl \installdir\site\ TdgssUserConfigFile.xml Teradata Index Wizard Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \Teradata Index Wizard version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ DBCVXViews120.bteq DBCVXViews62.bteq mgrcli.dll monpm.dll msvcr80.dll qcfsetup.def tdapp.dll tddaw.dll tdis.dll tdmfcis.dll tdtmgr.dll tdwmutil.dll tiwapiw.dll Tiwiz.exe tm_dialogs.dll tseapiw.dll tvecapiw.dll Teradata Tools and Utilities for Microsoft Windows Installation Guide 71

72 Chapter 5 Verifying the Complete Installation List of Files verify.dat Verify.exe \installdir\help\enu\ catalog.ccc document.css tiwiz html thru tiwiz html tiwiz_help.htm wwhelp4.jar \installdir\help\enu\images\ numerous *.gif and *.ico files \installdir\help\enu\scripts\ expand.js \installdir\help\enu\winhelp\ books.xml messages.xml settings.xml splash.jpg \installdir\help\enu\winhelp\images\ altclose.gif altopen.gif splash.jpg \installdir\help\enu\winhelp\wwhimpl\ api.htm version.htm \installdir\help\enu\winhelp\wwhimpl\common\html\ alinks.htm blank.htm bookmark.htm content.htm controll.htm controlr.htm default.htm document.htm first.htm frameset.htm int0.htm int1.htm int2.htm int3.htm pagenav.htm popup.htm reset.htm switch.htm title.htm 72 Teradata Tools and Utilities for Microsoft Windows Installation Guide

73 Chapter 5 Verifying the Complete Installation List of Files wwhelp.htm \installdir\help\enu\winhelp\wwhimplcommon\images\ numerous *.gif \installdir\help\enu\winhelp\wwhimpl\common\private\ books.js locale.js options.js popupf.js title.js \installdir\help\enu\winhelp\wwhimpl\common\scripts\ bklst1s bookgrps.js booklist.js browser.js control.js documt1.js filelist.js handler.js help.js highlit.js pophash.js popup.js related.js strutils.js switch.js \installdir\help\enu\winhelp\wwhimpl\java\html\ explore6.htm explorer.htm javainfo.htm javainfo.jar mozzila.htm mozzillau.htm netscape.htm winhelp.htm \installdir\help\enu\winhelp\wwhimpl\java\private\ books.xml locale.xml options.js options.xml \installdir\help\enu\winhelp\wwhimpl\java\scripts\ handler.js java.js javainfo.js \installdir\help\enu\wwhdata\common\ ailinks.js context.js Teradata Tools and Utilities for Microsoft Windows Installation Guide 73

74 Chapter 5 Verifying the Complete Installation List of Files files.js popups.js synomyms.xml title.js towwhdir.js wwhpagef.js \installdir\help\enu\wwhdata\java\ files.xml ix.xml search.xml toc.xml \installdir\help\enu\wwhdata\js\ index.js search.js toc.js \installdir\help\enu\wwhdata\js\search\ rch0.js search1.js \installdir\help\enu\wwhdata\java\ indexsel.htm navigate.htm panelfni.htm panelfns.htm panelfsi.htm panelfss.htm panelini.htm panelmsg.htm panelnav.htm panelvie.htm tabs.htm wwhelp.htm \installdir\help\enu\wwhelp\wwhimpl\js\images\ tabsbg.gif \installdir\help\enu\wwhelp\wwhimpl\js\private\ locale.js options.js \installdir\help\enu\wwhelp\wwhimpl\js\scripts\ handler.js index1s.js index.js javascript.js outfast.js outlin1s.js outline.js outsafe.js panels.js 74 Teradata Tools and Utilities for Microsoft Windows Installation Guide

75 Chapter 5 Verifying the Complete Installation List of Files search1s.js search 2s.js search3s.js search4s.js search.js tabs.js Teradata JDBC Driver Files and Folders \user-selectable\ terajdbc4.jar samples.jar tdgssconfig.jar Teradata MultiLoad Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\bin\ mload.exe \installdir\mload\ mlimod.c mlnotf.c Teradata OLE DB Access Module Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\bin oleload.exe \installdir\axsmod OLEDB_AXSMOD.dll OLEDB_AXSMODenu.dll OLEDB_AXSMODjpn.dll program.ico Uninst.dll \installdir\axsmod\teradata OLE DB Access Module Help Online Help files C:\windows\WinSxS MSVC80.dll MFC80.dll Teradata Tools and Utilities for Microsoft Windows Installation Guide 75

76 Chapter 5 Verifying the Complete Installation List of Files Teradata Parallel Data Pump Files and Folders (32-bit Platform) Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\bin\ tpump.exe \installdir\tpump\ tdatpump.cfg tldnfyxt.c tpumpar.csql tpumpimd.c Teradata Performance Monitor Object Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata \Teradata Performance Monitor Object version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ Mfc42u.dll Monitor.dll MonitorUserGuide.pdf Msvcrt.dll TDMon_enu.chm TDMon8.dll Verify.dat Verify.exe \installdir\samples\ Teradata Query Scheduler Administrator Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata \Teradata Query Scheduler version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ readme.txt tdqmdb.exe tqsadm.exe Teradata Query Scheduler Client Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata \Teradata Query Scheduler version\, where version is the version of the product 76 Teradata Tools and Utilities for Microsoft Windows Installation Guide

77 Chapter 5 Verifying the Complete Installation List of Files (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ readme.txt \installdir\client\ tdqmcomm.exe tdqmops.exe tdqmview.exe %SYSTEMROOT%\system32 tdqmcomm.dll tdqmsr.dll tdqmsubm.dll Teradata Query Scheduler Server Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata \Teradata Query Scheduler Server version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\server\ sqlprs.dfa sqlprs.llr tdqmjob.exe tdqmlsnr.exe tdqmreqp.exe tdqmserv.exe %SYSTEMROOT%\system32 tdqmserv.dll tdsqlprsu.dll bignumu.dll Teradata SQL Assistant Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\teradata SQL Assistant\ access.lng ansi.lng AxInterop.CodeMax4.dll base.lng db2.lng explain.lng FarPoint.CalcEngine.dll FarPoint.Excel.dll Teradata Tools and Utilities for Microsoft Windows Installation Guide 77

78 Chapter 5 Verifying the Complete Installation List of Files FarPoint.PDF.dll FarPoint.PluginCalendar.WinForms.dll FarPoint.Win.dll FarPoint.Win.Chart.dll FarPoint.Win.Spread.dll FarPoint.Win.Spread.Html.dll informix.lng Infragistics2.Shared.v11.2.dll Infragistics2.Win.Misc.v11.2.dll Infragistics2.Win.UltraWinDock.v11.2.dll Infragistics2.Win.UltraWinEditors.v11.2.dll Infragistics2.Win.UltraWinGrid.v11.2.dll Infragistics2.Win.UltraWinListView.v11.2.dll Infragistics2.Win.UltraWinMaskedEdit.v11.2.dll Infragistics2.Win.UltraWinStatusBar.v11.2.dll Infragistics2.Win.UltraWinTabbedMdi.v11.2.dll Infragistics2.Win.UltraWinTabControl.v11.2.dll Infragistics2.Win.UltraWinToolbars.v11.2.dll Infragistics2.Win.UltraWinTree.v11.2.dll Infragistics2.Win.v11.2.dll ingres.lng Interop.CodeMax4.dll Interop.DAO.dll mysql.lng neoview.lng Netezza.lng Office2000.isl Office2003.isl Office2007Black.isl Office2007Blue.isl Office2007Silver.isl oracle.lng outmsg.lng Pink.isl postgresql.lng ReleaseNotes.htm report.lng soliddb.lng SQLA.exe SQLA.exe.config SQLA.pdb SQLA.XmlSerializers.dll sqlacm_en.dll sqla_enu.chm sqlserver.lng startup.exe stdole.dll 78 Teradata Tools and Utilities for Microsoft Windows Installation Guide

79 Chapter 5 Verifying the Complete Installation List of Files sybase.lng teradata.lng verify.dat verify.exe Windows7.isl WindowsVista.isl Teradata Statistics Wizard Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata \Teradata Statistics Wizard version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ DBCVXViews120.bteq DBCVXViews62.bteq mgrcli.dll msvcr80.dll qcfsetup.def tdapp.dll tddaw.dll tdis.dll tdmfcis.dll tdtmgr.dll tdwmutil.dll tiwapiw.dll tm_dialogs.dll tm_stats.dll tswiz.exe TSEAPIw.dll tvecapiw.dll verify.dat Verify.exe \installdir\help\enu\ catalog.ccc document.css tiwiz html through tiwiz html tiwiz_help.htm wwhelp4.jar \installdir\help\enu\images\ numerous *.gif and *.ico files \installdir\help\enu\scripts\ expand.js \installdir\help\enu\wwhdata\common\ ailinks.js context.js Teradata Tools and Utilities for Microsoft Windows Installation Guide 79

80 Chapter 5 Verifying the Complete Installation List of Files files.js popups.js synomyms.xml title.js towwhdir.js wwhpagef.js \installdir\help\enu\wwhdata\java\ files.xml ix.xml search.xml toc.xml \installdir\help\enu\wwhdata\js\ index.js search.js toc.js \installdir\help\enu\wwhdata\js\search\ search0.js \installdir\help\enu\wwhelp\ books.xml messages.html settings.html \installdir\help\enu\wwhelp\images\ altclose.gif altopen.gif splash.jpg \installdir\help\enu\wwhelp\wwhimpl\ api.htm version.htm \installdir\help\enu\wwhelp\wwhimpl\common\html\ alinks.htm blank.htm bookmark.htm content.htm controll.htm controlr.htm default.htm document.htm first.htm frameset.htm int0.htm int1.htm int2.htm int3.htm pagenav.htm popup.htm reset.htm 80 Teradata Tools and Utilities for Microsoft Windows Installation Guide

81 Chapter 5 Verifying the Complete Installation List of Files switch.htm title.htm wwhelp.htm \installdir\help\enu\wwhelp\wwhimpl\common\images\ *.gif \installdir\help\enu\wwhelp\wwhimpl\common\private\ books.js locale.js options.js popupf.js title.js \installdir\help\enu\wwhelp\wwhimpl\common\scripts\ bklst1s bookgrps.js booklist.js browser.js controls.js documt1.js filelist.js handler.js help.js highlt.js pophash.js popup.js related.js strutils.js switch.js \installdir\help\enu\wwhelp\wwhimpl\java\html\ explore6.htm explorer.htm javainfo.htm javainfo.jar mozzila.htm mozzillau.htm netscape.htm wwhelp.htm \installdir\help\enu\wwhelp\wwhimpl\java\private\ books.xml locale.xml options.js options.xml \installdir\help\enu\wwhelp\wwhimpl\java\scripts\ handler.js java.js javainfo.js \installdir\help\enu\wwhelp\wwhimpl\js\html\ Teradata Tools and Utilities for Microsoft Windows Installation Guide 81

82 Chapter 5 Verifying the Complete Installation List of Files indexsel.htm navigate.htm panelfni.htm panelfns.htm panelfsi.htm panelfss.htm panelini.htm panelmsg.htm panelnav.htm panelvie.htm tabs.htm wwhelp.htm \installdir\help\enu\wwhelp\wwhimpl\js\images\ tabsbg.gif \installdir\help\enu\wwhelp\wwhimpl\js\private\ locale.js options.js \installdir\help\enu\wwhelp\wwhimpl\js\scripts\ handler.js index1s.js index.js javascript.js outfast.js outlin1s.js outline.js outsafe.js panels.js search1s.js search2s.js search3s.js search4s.js search.js tabs.js Teradata System Emulation Tool Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata \Teradata System Emulation Tool version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ DBCVXViews120.bteq DBCVXViews62.bteq mgrcli.dll monpm.dll msvcr80.dll 82 Teradata Tools and Utilities for Microsoft Windows Installation Guide

83 Chapter 5 Verifying the Complete Installation List of Files qcfsetup.def tdapp.dll tddaw.dll tdis.dll tdmfcis.dll tdtmgr.dll tdwmutil.dll tm_dialogs.dll tseapiw.dll TSET.exe tvecapiw.dl verify.dat Verify.exe \installdir\help\enu\ catalog.ccc document.css tset htmlthru tset html tset_help.htm wwhelp4.jar \install dir\help\enu\images\ numerous *.gif and *.icofiles \install dir\help\enu\scripts\ expand.js \install dir\help\enu\scripts\wwhdata\common\ ailinks.js context.js files.js popups.js synomyms.xml title.js topics.js towwhdir.js wwhpagef.js \install dir\help\enu\scripts\wwhdata\java\ files.xml ix.xml search.xml toc.xml \install dir\help\enu\scripts\wwhdata\js\ index.js search.js toc.js \install dir\help\enu\wwhdata\js\search search0.js search1.js \install dir\help\enu\wwhelp\ Teradata Tools and Utilities for Microsoft Windows Installation Guide 83

84 Chapter 5 Verifying the Complete Installation List of Files books.xml messages.html settings.html \install dir\help\enu\wwhelp\images\ altclose.gif altopen.gif splash.jpg \install dir\help\enu\wwhelp\wwhimpl\ api.htm version.htm \install dir\help\enu\wwhelp\wwhimpl\common\html\ alinks.htm blank.htm bookmark.htm content.htm controll.htm controlr.htm default.htm document.htm first.htm frameset.htm int0.htm int1.htm int2.htm int3.htm pagenav.htm popup.htm reset.htm switch.htm title.htm wwhelp.htm \install dir\help\enu\wwhelp\wwhimpl\common\images numerous *.gif \install dir\help\enu\wwhelp\wwhimpl\common\private\ books.js locale.js options.js popupf.js title.js \install dir\help\enu\wwhelp\wwhimpl\common\scripts\ bklst1s bookgrps.js booklist.js browser.js controls.js documt1.js filelist.js 84 Teradata Tools and Utilities for Microsoft Windows Installation Guide

85 Chapter 5 Verifying the Complete Installation List of Files handler.js help.js highlt.js pophash.js popup.js related.js strutils.js switch.js \install dir\help\enu\wwhelp\wwhimpl\java\html\ explore6.htm explorer.htm javainfo.htm javainfo.jar mozzila.htm mozzillau.htm netscape.htm wwhelp.htm \install dir\help\enu\wwhelp\wwhimpl\java\private\ books.xml locale.xml options.js options.xml \install dir\help\enu\wwhelp\wwhimpl\java\scripts\ handler.js java.js javainfo.js \install dir\help\enu\wwhelp\wwhimpl\js\html\ indexsel.htm navigate.htm panelfni.htm panelfns.htm panelfsi.htm panelfss.htm panelini.htm panelmsg.htm panelnav.htm panelvie.htm tabs.htm wwhelp.htm \install dir\help\enu\wwhelp\wwhimpl\js\images\ tabsbg.gif \install dir\help\enu\wwhelp\wwhimpl\js\private\ locale.js options.js \install dir\help\enu\wwhelp\wwhimpl\js\scripts\ handler.js Teradata Tools and Utilities for Microsoft Windows Installation Guide 85

86 Chapter 5 Verifying the Complete Installation List of Files index1s.js index.js javascript.js outfast.js outlin1s.js outline.js outsafe.js panels.js search1s.js search2s.js search3s.js search4s.js search.js tabs.js Teradata Visual Explain Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata \Teradata Visual Explain version\, where version is the version of the product (for example, 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\ DBCVXViews120.bteq DBCVXViews62.bteq mgrcli.dll monpm.dll msvcr80.dll qcfsetup.def tdapp.dll tddaw.dll tdis.dll tdmfcis.dll tdtmgr.dll tdwmutil.dll tiwapiw.dll Tiwiz.exe tm_dialogs.dll tseapiw.dll tvecapiw.dll verify.dat Verify.exe \installdir\help\enu\ catalog.ccc document.css tiwiz html thru tiwiz html tiwiz_help.htm 86 Teradata Tools and Utilities for Microsoft Windows Installation Guide

87 Chapter 5 Verifying the Complete Installation List of Files wwhelp4.jar \installdir\help\enu\images\ numerous *.gif and *.ico files \installdir\help\enu\images\scripts\ expand.js \installdir\help\enu\wwhdata\common\ ailinks.js context.js files.js popups.js synomyms.xml title.js topics.js towwhdir.js wwhpagef.js \installdir\help\enu\wwhdata\java\ files.xml ix.xml search.xml toc.xml \installdir\help\enu\wwhdata\js\ index.js search.js toc.js \installdir\help\enu\wwhdata\js\search\ search0.js search1.js \installdir\help\enu\wwhdata\js\search\wwhelp\ books.xml messages.html settings.html \installdir\help\enu\wwhelp\images\ altclose.gif altopen.gif splash.jpg \installdir\help\enu\wwhelp\wwhimpl\ api.htm version.htm \installdir\help\enu\wwhelp\wwhimpl\common\html\ alinks.htm blank.htm bookmark.htm content.htm controll.htm controlr.htm default.htm Teradata Tools and Utilities for Microsoft Windows Installation Guide 87

88 Chapter 5 Verifying the Complete Installation List of Files document.htm first.htm frameset.htm int0.htm int1.htm int2.htm int3.htm pagenav.htm popup.htm reset.htm switch.htm title.htm wwhelp.htm \installdir\help\enu\wwhelp\wwhimpl\common\images\ numerous *.gif \installdir\help\enu\wwhelp\wwhimpl\common\private\ books.js locale.js options.js popupf.js title.js \installdir\help\enu\wwhelp\wwhimpl\common\scripts\ bklst1s bookgrps.js booklist.js browser.js controls.js documt1.js filelist.js handler.js help.js highlt.js pophash.js popup.js related.js strutils.js switch.js \installdir\help\enu\wwhelp\wwhimpl\java\html\ explore6.htm explorer.htm javainfo.htm javainfo.jar mozzila.htm mozzillau.htm netscape.htm wwhelp.htm \installdir\help\enu\wwhelp\wwhimpl\java\private\ 88 Teradata Tools and Utilities for Microsoft Windows Installation Guide

89 Chapter 5 Verifying the Complete Installation List of Files books.xml locale.xml options.js options.xml \installdir\help\enu\wwhelp\wwhimpl\java\scripts\ handler.js java.js javainfo.js \installdir\help\enu\wwhelp\wwhimpl\js\html\ indexsel.htm navigate.htm panelfni.htm panelfns.htm panelfsi.htm panelfss.htm panelini.htm panelmsg.htm panelnav.htm panelvie.htm tabs.htm wwhelp.htm \installdir\help\enu\wwhelp\wwhimpl\js\images\ tabsbg.gif \installdir\help\enu\wwhelp\wwhimpl\js\private\ locale.js options.js \installdir\help\enu\wwhelp\wwhimpl\js\scripts\ handler.js index1s.js index.js javascript.js outfast.js outlin1s.js outline.js outsafe.js panels.js search1s.js search 2s.js search3s.js search4s.js search.js tabs.js Teradata Tools and Utilities for Microsoft Windows Installation Guide 89

90 Chapter 5 Verifying the Complete Installation List of Files Teradata Wallet Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\tdwallet\ config.xml \installdir\tdwallet\nt-i386\ [32-Bit] tdlink.exe tdwallet.dll tdwallet.exe \installdir\tdwallet\nt-x8664\ [64-Bit] tdlink.exe tdwallet.dll tdwallet.exe Teradata WebSphere MQ Access Module Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\axsmod\ libmqs.dll libmqsc.dll Teradata Workload Analyzer Files and Folders Note: In the list(s) below, installdir represents \program-files\teradata\client \version\, where version is the version of the product (for example 1410). For information about the program-files variable, see About the program-files Variable in the Default Installation Path. \installdir\teradata Workload Analyzer\ fspread.dll mgrcli.dll monpm.dll tdtmgr.dll twa.exe psaload.dll tdapp.dll tdis.dll tdwmutil.dll tm_dialogs.dll verify.dat Verify.exe 90 Teradata Tools and Utilities for Microsoft Windows Installation Guide

91 Chapter 5 Verifying the Complete Installation List of Files \%SYSTEMROOT%\system32 msvcr80.dll Teradata Tools and Utilities for Microsoft Windows Installation Guide 91

92 Chapter 5 Verifying the Complete Installation List of Files 92 Teradata Tools and Utilities for Microsoft Windows Installation Guide

93 CHAPTER 6 Deploying Teradata Tools and Utilities with SCCM About Deploying Products with SCCM A summary of tasks required to deploy products using SCCM follows: 1. Install third-party product dependencies on the client computers. 2. Uninstall existing products from the client computers. Note: Alternatively, you can have the batch file uninstall existing products before it installs the new products. 3. Create a software repository on the system that is running the SCCM server. 4. Create the batch file that will install the products during SCCM deployment. 5. Use System Center Configuration Manager to deploy the batch file and the product packages to the client computers. Third-Party Dependency Products on Client Computers Third-Party Dependency Product IBM WebSphere MQ 7.5 Note: To display the version of WebSphere that is installed on the system, run the dspmqver command from the command line. Java 2 Runtime Environment 1.4.2_06 or later Note: The environment can be downloaded from Java Downloads. JDK 1.4, JDK 5.0, or JDK 6.0 Note: JDK 5.0 is certified for Windows 32-bit. JDK 5.0 is certified for Windows XP Professional x64 using EM64T. JDK 6.0 is certified for Windows 64-bit. Supported Teradata Tools and Utilities Product Teradata WebSphere MQ Access Module Teradata Parallel Transporter Base Teradata JDBC Driver Teradata Tools and Utilities for Microsoft Windows Installation Guide 93

94 Chapter 6 Deploying Teradata Tools and Utilities with SCCM Uninstalling Existing Products from Client Computers Third-Party Dependency Product Supported Teradata Tools and Utilities Product Note: The environment can be downloaded from Java Downloads. Microsoft.NET Framework Version 3.5 SP1 Redistributable Package or Microsoft.NET Framework Version 4.0 Redistributable Package Progress DataDirect ConnectXE ODBC driver for Teradata (required only if you will use the ODBC operator).net Data Provider for Teradata ODBC Driver for Teradata Uninstalling Existing Products from Client Computers It is not necessary to uninstall existing products from client computers at this point if you include the command below in the batch file that you will create later. 1 On each client computer, run the following command: cscript uninstall_ttu.vbs ALL All existing Teradata Tools and Utilities products are uninstalled. Creating a Software Repository 1 On the system that runs the SCCM server software, create a folder that will act as the root of the software repository. For example, name the folder TTU15.00_SoftwareRepository. 2 Check Teradata Software Server to see if a newer version of the package file for the Teradata Tools and Utilities bundled suite is available. If a newer version is available, download it, extract it, and use it as the source instead of the installation media. 3 In the file structure of the source, browse to the \Windows\TTU folder. 4 Create an x86 folder and an x64 folder in the root of the software repository. 5 For each Teradata Tools and Utilities product, copy the folder to the x86 or x64 folder of the software repository based on the package bitness. The 32-bit packages must be in the x86 folder, and the 64bit packages in the x64 Folder. For example, the CLIv2-32bit folder should be copied to the x86 folder at the root of the repository. After you copy each folder, the folder and file structure should look like this: TTU15.00_SoftwareRepository setup.exe silent_install.bat 94 Teradata Tools and Utilities for Microsoft Windows Installation Guide

95 Chapter 6 Deploying Teradata Tools and Utilities with SCCM Creating a Batch File to Install the Products TTUSuiteSilent.exe uninstall_ttu.vbs X86 BTEQ... setup.exe X64 CLIv2-32bit... setup.exe CLIv2-64bit... setup.exe DataConnector-32bit... setup.exe Copy the following files from the \Windows\TTU folder to the root of the software repository: setup.exe silent_install.bat TTUSuiteSilent.exe uninstall_ttu.vbs Creating a Batch File to Install the Products The batch file that you create in this procedure will be used during SCCM deployment to automatically perform the following tasks: uninstall existing Teradata Tools and Utilities products (if you include that instruction in the batch file) install new Teradata Tools and Utilities products 1 Create a batch file on the root of the software repository. For example, name the file Deploy_TTU.bat. 2 Add the appropriate text to the file. [If you already uninstalled existing products from the client computers]: REM Input: REM Logging: No input required The log file for each package will be located in the %temp% folder silent_install.bat "PRODUCT" [If you did not already uninstall existing products from the client computers]: Teradata Tools and Utilities for Microsoft Windows Installation Guide 95

96 Chapter 6 Deploying Teradata Tools and Utilities with SCCM Deploying the Batch File and the Packages via SCCM REM Input: REM Logging: No input required The log file for each package will be located in the %temp% folder cscript uninstall_ttu.vbs ALL silent_install.bat "PRODUCT" where PRODUCT is a set of parameter values associated with the products that will be installed: Suite of Products Teradata Tools and Utilities - Base Teradata Tools and Utilities - Database Management Teradata Tools and Utilities - Tape Storage Management Parameter Values of Products on the Suite BTEQ, FastExport, FastLoad, JMSAM, MultiLoad, NamedPipesAM, OLEDBAM, Preprocessor, SQLA, TDAdmin, TDNETDP, TDWallet, TPTBase, TPTStream, TPump, WebsphereAM BTEQ, IndexWizard, PMonObject, StatWizard, TDWallet, TQSAdmin, TQSClient, TQSServer, TSET, TWA, VisualExplain ARC, Preprocessor, TDWallet The values are case-sensitive. Be sure to enclose them in quote marks (""). Separate the values with a comma, but do not include a space. For example, to install all of the products that are part of the Tape Storage Management suite, add the following text to the file: silent_install.bat "ARC,Preprocessor,TDWallet" ODBC Driver for Teradata is always installed. You do not need to specify the value for this product, but be sure to copy the product package file for it to the root of the software repository You do not need to specify the values for the dependent products because they will automatically be installed. However, be sure to copy the following dependent product package files to the root of the software repository: Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata Generic Security Services Client Deploying the Batch File and the Packages via SCCM 1 Create a package and configure it for deployment. a Select Start > All Programs > Microsoft System Center 2012 > Configuration Manager. 96 Teradata Tools and Utilities for Microsoft Windows Installation Guide

97 Chapter 6 Deploying Teradata Tools and Utilities with SCCM Deploying the Batch File and the Packages via SCCM Allow a few seconds for the software to connect to SQL Server. b c d e In the left pane, select Software Library. In the left pane, expand Overview > Application Management > Packages. Right-click Packages and select Create Package. The Create Package and Program Wizard is displayed. In the right pane, add information to the following text boxes: Text Box Name Manufacturer Language Value The name of the package you are creating (for example, TTU Base 14.10) Teradata Corporation EN Version f g h i j k l Select the checkbox labeled This package contains source files. The Set Source Folder dialog box is displayed. For the Source folder text box, click Browse and browse to the folder that contains the source files (the software repository). Click OK. In the Create Package and Program Wizard, click Next. Options to choose the program type are displayed. Click Standard program. Click Next. The Standard Program section of the Wizard is displayed. In the Name text box, enter the name of the program. For example, enter TTU Base In the Command line text box, enter the following command: batch_filename "PRODUCT" where batch_filename is the name of the batch file on the root of the software repository and where PRODUCT is a set of parameter values associated with the products you want to install. Note: If the batch file you enter into the Command line text box contains a command to execute silent_install.bat, do not add PRODUCT parameter values to the Command line text box. An example of a batch file that contains a command to execute silent_install.bat is the file named Deploy_TTU.bat mentioned in Creating a Batch File to Install the Products. This file already contains a list of PRODUCT parameter values. Teradata Tools and Utilities for Microsoft Windows Installation Guide 97

98 Chapter 6 Deploying Teradata Tools and Utilities with SCCM Deploying the Batch File and the Packages via SCCM Suite of Products Teradata Tools and Utilities - Base Teradata Tools and Utilities - Database Management Teradata Tools and Utilities - Tape Storage Management Parameter Values of Products on the Suite BTEQ, FastExport, FastLoad, JMSAM, MultiLoad, NamedPipesAM, OLEDBAM, Preprocessor, SQLA, TDAdmin, TDNETDP, TDWallet, TPTBase, TPTStream, TPump, WebsphereAM BTEQ, IndexWizard, PMonObject, StatWizard, TDWallet, TQSAdmin, TQSClient, TQSServer, TSET, TWA, VisualExplain ARC, Preprocessor, TDWallet The values are case-sensitive. Be sure to enclose them in quote marks (""). Separate the values with a comma, but do not include a space. Command Example 1: Install all products that are part of the Base suite: silent_install.bat "TDWallet,BTEQ,FastExport,FastLoad,MultiLoad,TPump,NamedPipesAM,OLEDBAM,WebsphereAM,JMSAM,Preprocessor,SQLA,TDAdmin,TPTBase,TP TStream" Command Example 2: Install all products that are part of the Database Management suite: silent_install.bat "TDWallet,BTEQ,IndexWizard,StatWizard,PMonObject,TQSAdmin,TQSCl ient,tqsserver,tset,visualexplain,twa" Command Example 3: Install all products that are part of the Tape Storage Management suite: silent_install.bat "TDWallet,ARC,Preprocessor" ODBC Driver for Teradata is always installed. You do not need to specify the value for this product, but be sure to copy the product package file for it to the root of the software repository. You do not need to specify the values for the dependent products because they will automatically be installed. However, be sure to copy the following dependent product package files to the root of the software repository: Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata Generic Security Services Client m In the Run drop-down list, select Normal. When the package is deployed to the client, a command prompt will be displayed. If you do not want the command prompt to be displayed, select Hide. n o In the Program can run drop-down list, select Whether or not user is logged in. Click Next. 98 Teradata Tools and Utilities for Microsoft Windows Installation Guide

99 Chapter 6 Deploying Teradata Tools and Utilities with SCCM Deploying the Batch File and the Packages via SCCM The Requirements section of the Wizard is displayed. p q r Click Next to accept the default settings. Click Next again. Click Close. The name of the package (for example, TTU Base 14.10) is displayed in the right pane of the SCCM interface. 2 Deploy the package (make the package available to clients). a In the right pane, right-click the name of the package (for example, TTU Base 14.10) and select Deploy. The Deploy Software Wizard is displayed. b Next to the Collections text box, click Browse. The Select Collection dialog box is displayed. c Select All Systems and click OK. The Deploy Software Wizard is displayed. d Click Next. The Content section of the Wizard is displayed. e Click the Add drop-down button and select Distribution Point. The Add Distribution Points dialog box is displayed. f g In the Name column, select the checkbox next to the distribution point and click OK. Click Next. The Deployment Settings section of the Wizard is displayed. h i Click the Purpose drop-down list and select one of the following options: Available: During deployment, installation on the client will be interactive. Required: During deployment, installation on the client will be silent. When you select this option, if a dialog box appears, you can choose to select Allow user to interact with installation. Click Next. The Scheduling section of the Wizard is displayed. j k [Optional] Schedule when the deployment will become available and when it will expire. Click Next. The User Experience section of the Wizard is displayed. l Select the Software installation checkbox and click Next. Teradata Tools and Utilities for Microsoft Windows Installation Guide 99

100 Chapter 6 Deploying Teradata Tools and Utilities with SCCM Deploying the Batch File and the Packages via SCCM The Distribution Points section of the Wizard is displayed. m In the Deployment options drop-down list (for a fast network), select the appropriate item from the list (in most cases, you should select Download content from distribution point and run locally). n o p In the Deployment options drop-down list (for a slow network), select the appropriate item from the list (in most cases, you should select Do not run program). Click Next. The Summary section of the Wizard is displayed. Click Next. q Click Close. Note: It might take some time for the deployed software to become available on the client. 3 [Optional] Manually install the package at the client. a At the client, select Start > All Programs > Microsoft System Center 2012 > Configuration Manager > Software Center. The Software Center window is displayed. b Select the package you want to install. c In the lower right corner, click Install. The package is installed on the client. 100 Teradata Tools and Utilities for Microsoft Windows Installation Guide

101 CHAPTER 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR The tar_teradata_client_packages script is intended for use by system administrators. The script aids with deploying Teradata Tools and Utilities products across a network. About the TAR File A tar file is an archive of files that you typically create on a UNIX or Linux system. The folder and file structure in the archive mirrors the structure of the source files. You can use the tar_teradata_client_packages script on the Teradata Tools and Utilities installation media to create a compressed archive of Teradata Tools and Utilities client packages for a specific platform or operating system from the installation media. You can also compress the tar file. A compressed tar file is like a zip or 7z or rar or cab file on a Windows system. On a 32-bit Windows system, you can create a tar file for bundling individual UNIX or Linux packages and their dependencies or the entire set of Teradata Tools and Utilities packages for UNIX or Linux. The tar archive can be copied to a network machine and deployed to UNIX or Linux clients through FTP. Use this option if for example the target UNIX or Linux clients have a CD drive but not a DVD drive. You can build the tar file to contain all of the packages for a specified platform, or all the files for a specified package. It also includes all of the required dependencies for the selected packages. TAR Script Compatibility with Platform Operating Systems The tar_teradata_client_packages script provided on the installation media runs on 32-bit Windows using the command prompt. Verifying TAR Script Dependencies are Installed The tar executable must be located in the PATH on the system running the script. A standard Windows installation does not include tar.exe or gzip.exe. These utilities must be installed manually. 1 Ensure that the tar executable is located in the PATH on the system by running the script. Teradata Tools and Utilities for Microsoft Windows Installation Guide 101

102 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR If the tar.exe executable is not found on the system, the script aborts. The script displays a download location for the GNU version of tar.exe at ftp:// ftp.gnu.org/pub/pub/gnu/tar/tar-1.12.msdos.exe. This version of tar.exe works on 32-bit Windows only. If the gzip.exe compression utility is in the PATH, the script uses the utility to compress the tar file. The TAR Script Command To launch the TAR script, run tar_teradata_client_packages.bat. Note: For the commands in the following table, the package-version identifier is not required. For example, the package names bteq and bteqxxxx (where xxxx is the version number) are equivalent. Command tar_teradata_client_packages or tar_teradata_client_packages help tar_teradata_client_packages list tar_teradata_client_packages list platform tar_teradata_client_packages platform package Description Displays the available commands Displays the platforms and packages that are available on the installation media Lists the products for a specific platform that are available on the installation media Run the script with platform as the first parameter to create a tar file in the default target path. The resulting archive contains all Teradata client packages on the media for that platform. The value of the platform parameter can be one of the following: aix i386 ia64 opteron pa-risc s390x sparc The path for the output can be changed. The output filename is in the following format: teradata-client-platform-media-name.tar. If the archive is compressed with gzip.exe, the script appends.gz to the filename. Run the script with platform as the second parameter after the list parameter to list the packages available for the specified platform. Creates a tar file for a specific platform and one package Add the name of a package after the platform parameter. For example, to archive the bteq package for the aix platform, type: 102 Teradata Tools and Utilities for Microsoft Windows Installation Guide

103 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR Command Description tar_teradata_client_packages aix bteq tar_teradata_client_packages platform package1 package2 etc. If you specify a package other than a dependent package, all of the following dependent packages are included in the archive: cliv2 piom tdicu teragss If you specify package names after the platform parameter, the script includes the dependent packages if they are available on the media. If you specify individual packages, all of the dependendent packages are included in the archive. Creates a tar file for a specific platform and specific packages Add the name of packages after the platform parameter. For example, to archive the bteq and fastload packages for the aix platform, type: TAR Script Usage Considerations tar_teradata_client_packages aix bteq fastld If you specify packages other than the dependent packages, all of the dependent packages are included in the archive: cliv2 piom tdicu teragss If you specify package names after the platform parameter, the script includes the dependent packages if they are available on the media. If you specify individual packages, all of the dependendent packages are included in the archive. Subject Default Directory Multiple and Dependent Packages Getting Help on the Script Description The tar_teradata_client_packages script prompts for a directory to create the tar file. To use the default user directory, press Enter. By convention, the default home directory is %USERPROFILE%. The script attempts to create the directory if it does not exist. If the location is read-only or unable to be written, the script ends. If a single package or multiple packages are selected, all of the dependent products are included, even if the product selected is one of the single dependent packages. Dependent packages typically have mutual dependencies. For example, dependent package cliv2 depends on the dependent packages tdicu and TeraGSS. To view command usage and optional command parameters, run tar_teradata_client_packages by itself or with the optional help parameter: tar_teradata_client_packages tar_teradata_client_packages help Teradata Tools and Utilities for Microsoft Windows Installation Guide 103

104 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR Subject Description A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v.xx.xx.xx.xx * ************************************************************************ Tar Teradata Client Packages Usage: tar_teradata_client_packages list tar_teradata_client_packages list {platform} tar_teradata_client_packages {platform} [{package1} {package2}...] Parameters: commands : help, list, {platform} [{package1} {package2}...] help : Display this help message. list : List the available platforms and packages from the media. list {platform} : List the packages available for the specified platform. {platform} : Available platforms: aix, ia64, pa-risc, i386, s390x, opteron, sparc Create the tar file for the supplied platform and include all packages or individual packages. {package} : Specify the packages available on this media for the specific platform. The parameter "all" (or blank) will include all available packages. To specify individual packages, list the packages separated by a space. Example: ttcp.bat linux bteq fastld Listing the Available Packages and Platforms The dependencies will automatically be included and do not need to be listed individually. The following packages are included: ---TeraGSS cliv2 tdicu piom All of the platforms and packages contained on the installation media can be listed by running the tar_teradata_client_packages script with the list parameter, for example: tar_teradata_client_packages list To list all packages for a specific platform available on the installation media, run tar_teradata_client_packages list platform where platform is the value of one of the platforms, for example: tar_teradata_client_packages list hp-ux A screen similar to the following appears as a result. It lists all the platforms and packages on the current installation media: ************************************************************************ * Tar Teradata Client Packages v.xx.xx.xx.xx * ************************************************************************ TTU Foundation 104 Teradata Tools and Utilities for Microsoft Windows Installation Guide

105 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR Subject Description The available platforms are: HP-UX Linux The available packages are: --- HP-UX Products bteq fastexp mload npaxsmod tdicu tpump cliv2 fastld mqaxsmod piom TeraGSS --- Linux Products bteq fastexp mload npaxsmod tdicu tpump cliv2 fastld mqaxsmod piom TeraGSS Downloading Windows Utility Software for TAR Deployment To create a compressed tar archive of Linux or UNIX packages for Teradata Tools and Utilities products on a 32-bit Windows platform from the installation media, the tar.exe and gzip.exe archiving and compression utilities must be installed. 1 Enter the following command to verify if tar.exe is installed: D:\tar_teradata_client_packages If tar.exe is not installed, a message similar to the following appears, directing you to a location where the tar.exe archiving utility is available for download: ************************************************************************ * Tar Teradata Client Packages v.xx.xx.xx.xx * ************************************************************************ TTU Foundation ERROR: The executable tar.exe doesn't exist on this system or isn't in the PATH. Please download the GNU tar executable from the following address: ftp://ftp.gnu.org/pub/pub/gnu/tar/tar-1.12.msdos.exe Save the file as tar.exe in the C:\WINDOWS directory, or to another directory in the PATH, then rerun this script again. GNU Tar version 1.12 is the recommended tar for DOS to use. For more information see: 2 If tar.exe is not installed, download tar-1.12.msdos.exe from ftp:// ftp.gnu.org/pub/pub/gnu/tar/tar-1.12.msdos.exe. This version of tar.exe works on 32-bit Windows only. 3 Save the download to the C:\Windows directory and rename the file to tar.exe. 4 Enter the following command to verify if gzip.exe is installed: D:\tar_teradata_client_packages Teradata Tools and Utilities for Microsoft Windows Installation Guide 105

106 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR If gzip.exe is not installed, a message similar to the following appears during the creation of the tar file: Notice: The executable gzip.exe is not found. Download from for MSDOS to automatically compress the output tar file to a gzip file. 5 If gzip.exe is not installed, download the MSDOS version of gzip.exe from gzip home page. The MSDOS version of gzip.exe works on 32-bit Windows only. 6 Save the download to the C:\Windows directory. TAR Script Examples The file tar_teradata_client_packages is available on all installation media. The examples list available packages and create tar files that include all packages or individual packages and their dependent packages. Examples also show the commands for creating tar package archives for UNIX and Linux platforms on Windows. Archiving Oracle Solaris SPARC Packages This example archives packages and dependencies that are required for the deployment of Teradata Tools and Utilities products to Oracle Solaris SPARC clients. The packages and dependencies are copied from the installation media and archived as a tar file. The archive can be copied to Oracle Solaris SPARC machines and expanded. The example assumes that you run the archiving script on a 32-bit Windows system on which tar.exe is installed but gzip.exe is not installed. The procedure involves the following steps: 1. Listing available products 2. Copying and archiving products 1 Run the script with the list parameter to display a list of the products available for each product and platform: D:\tar_teradata_client_packages list A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v * ************************************************************************ TTU Foundation The available platforms are: AIX Solaris For Solaris Sparc use "sparc" for the platform parameter. For Solaris Opteron use "opteron" for the platform parameter. The available packages are: --- AIX Products cliv2 cobpp sqlpp tdicu 106 Teradata Tools and Utilities for Microsoft Windows Installation Guide

107 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR TeraGSS --- Solaris Sparc Products cliv21410 sqlpp1410 tdicu1410 TeraGSS TeraGSS Solaris Opteron Products cliv21410 sqlpp1410 tdicu1410 TeraGSS_solaris-i386 TeraGSS_solaris-x Enter the following commands to create an archive of the Oracle Solaris SPARC packages and dependencies. a D:\tar_teradata_client_packages sparc A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v * ************************************************************************ TTU Foundation Platform: Solaris\Sparc Default Path and Output File: C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar Hit [Enter] to accept the path: "C:\Documents and Settings\<user>", or input a different save directory :Output File "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar" b Press Enter to accept the default path, copy the packages, and create the tar archive. A screen similar to the following appears: ---Archiving all packages for sparc. tar cvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar" Solaris\Sparc Solaris/Sparc/ Solaris/Sparc/TeraGSS/ Solaris/Sparc/TeraGSS/install/ Solaris/Sparc/TeraGSS/install/depend.. (more files). Solaris/Sparc/tdicu1410/reloc/$LIBDIR64/libiculxtd.so.46.0 Solaris/Sparc/tdicu1410/reloc/$LIBDIR64/libicuuctd.so.46.0 tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar".setup.sh.setup.sh tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar" setup.bat setup.bat tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar" MEDIALABEL Teradata Tools and Utilities for Microsoft Windows Installation Guide 107

108 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR MEDIALABEL tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar" tar_teradata_client_packages.* tar_teradata_client_packages.bat tar_teradata_client_packages.sh Notice: The executable gzip.exe is not found. Download from for MSDOS to automatically compress the output tar file to a gzip file. The file has been saved at : C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar Archiving an HP-UX Package This example archives the bteq package and its dependencies that are required for the deployment of bteq to HP-UX clients. The package and dependencies are copied from the installation media, archived as a tar file, and compressed. The compressed archive can be copied to HP-UX machines and expanded. The example assumes that you run the archiving script on a 32-bit Windows system on which tar.exe and gzip.exe are installed. 1 Run the script with hp-ux as the value of the platform parameter and bteq as the value of the product name: D:\tar_teradata_client_packages hp-ux bteq A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v * ************************************************************************ Load/Unload - Volume 2 Platform: HP-UX Default Path and Output File: C:\Documents and Settings\user\teradata-client-hp-ux-load-unload-volume-2.tar Hit [Enter] to accept the path: "C:\Documents and Settings\username", or input a different save directory : "C:\Documents and Settings\username" Output File "C:\Documents and Settings\username\teradata-client-hp-ux-load-unloadvolume-2.tar" ---Archiving setup files and dependency packages for hp-ux tar cvf "C:\Documents and Settings\username\teradata-client-hp-ux-load-unloadvolume-2.tar" HPUX\TeraGSS* a HP-UX/TeraGSS/ia64/pkginfo.txt 1 block a HP-UX/TeraGSS/ia64/TeraGSS_hpux-ia64_ depot blocks a HP-UX/TeraGSS/ia64/TeraGSS_hpux-ia64_ psf 3 blocks a HP-UX/TeraGSS/pa32/pkginfo.txt 1 block a HP-UX/TeraGSS/pa32/TeraGSS_hpux-pa32_ depot blocks a HP-UX/TeraGSS/pa32/TeraGSS_hpux-pa32_ psf 3 blocks tar rvf "C:\Documents and Settings\username\teradata-client-hp-ux-load-unloadvolume-2.tar" HP-UX\tdicu* tar: blocksize = 20 a HP-UX/tdicu/ia64/swagent.log 3 blocks a HP-UX/tdicu/ia64/tdicu1410/tdicu1410/opt/teradata/client/14.10/tdicu/ lib/libicudatatd.so blocks a HP-UX/tdicu/ia64/tdicu1410/tdicu1410/opt/teradata/client/14.10/tdicu/ 108 Teradata Tools and Utilities for Microsoft Windows Installation Guide

109 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR lib/libicui18ntd.so blocks a HP-UX/tdicu/ia64/tdicu1410/tdicu1410/opt/teradata/client/14.10/tdicu/ lib/libicuiotd.so blocks a HP-UX/bteq/pa32/catalog/swlock 0 blocks a HP-UX/bteq/pa32/catalog/INDEX 9 blocks a HP-UX/bteq/pa32/catalog/bteq1410/bteq1410/INFO 4 blocks a HP-UX/bteq/pa32/catalog/bteq1410/bteq1410/INDEX 1 block a HP-UX/bteq/pa32/catalog/bteq1410/bteq1410/postinstall 10 blocks a HP-UX/bteq/pa32/catalog/bteq1410/bteq1410/postremove 5 blocks a HP-UX/bteq/pa32/catalog/bteq1410/bteq1410/preinstall 11 blocks a HP-UX/bteq/pa32/catalog/bteq1410/pfiles/INFO 1 block a HP-UX/bteq/pa32/catalog/bteq1410/pfiles/INDEX 8 blocks a HP-UX/bteq/pa32/catalog/bteq1410/pfiles/README 1 block a HP-UX/bteq/pa32/catalog/bteq1410/pfiles/_ACL 1 block a HP-UX/bteq/pa32/catalog/bteq1410/pfiles/_LOCK_FILE 0 blocks a HP-UX/bteq/pa32/catalog/bteq1410/pfiles/_OWNER 1 block a HP-UX/bteq/pa32/catalog/dfiles/INFO 1 block a HP-UX/bteq/pa32/catalog/dfiles/INDEX 1 block a HP-UX/bteq/pa32/catalog/dfiles/_ACL 1 block a HP-UX/bteq/pa32/catalog/dfiles/_PROD_DFLT_ACL 1 block a HP-UX/bteq/pa32/catalog/dfiles/_LOCK_FILE 0 blocks a HP-UX/bteq/pa32/catalog/dfiles/_OWNER 1 block The file has been saved at : C:\Documents and Settings\username\teradata-client-hp-ux-load-unload-volume-2.tar.gz Archiving Linux Packages This example archives packages and dependencies that are required for the deployment of Teradata Tools and Utilities products to SUSE Linux or Red Hat Linux clients. The packages and dependencies are copied from the installation media, archived as a tar file, and compressed. The compressed archive can be copied to SUSE Linux or Red Hat Linux machines and expanded. The example assumes that you run the archiving script on a 32-bit Windows system on which tar.exe and gzip.exe are installed. 1 Run the script with linux as the value of the platform parameter: D:\tar_teradata_client_packages linux A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v * ************************************************************************ TTU Foundation Platform: Linux Default Path and Output File: C:\Documents and Settings\user\teradata-client-linux-ttu-foundation.tar Hit [Enter] to accept the path: "C:\Documents and Settings\user", or input a different save directory : Output File "C:\Documents and Settings\user\teradata-client-linux-ttu-foundation.tar" ---Archiving all packages for linux. tar cvf "C:\Documents and Settings\user\teradata-client-linux-ttu-foundation.tar" Linux a Linux/mqaxsmod/mqaxsmod i386.rpm 118 blocks Teradata Tools and Utilities for Microsoft Windows Installation Guide 109

110 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR a Linux/mload/mload i386.rpm 374 blocks a Linux/piom/piom i386.rpm 79 blocks a Linux/tdicu/tdicu noarch.rpm blocks a Linux/fastld/fastld i386.rpm 189 blocks a Linux/TeraGSS/TeraGSS_redhatlinux-i i386.rpm blocks a Linux/fastexp/fastexp i386.rpm 341 blocks a Linux/tpump/tpump i386.rpm 478 blocks a Linux/npaxsmod/npaxsmod i386.rpm 272 blocks a Linux/cliv2/cliv x86_64.rpm 766 blocks a Linux/bteq/bteq i386.rpm 303 blocks tar rvf "C:\Documents and Settings\user\teradata-client-linux-ttufoundation.tar".setup.sh tar: blocksize = 20 a.setup.sh 282 blocks tar rvf "C:\Documents and Settings\user\teradata-client-linux-ttu-foundation.tar" setup.bat tar: blocksize = 20 a setup.bat 1 block tar rvf "C:\Documents and Settings\user\teradata-client-linux-ttu-foundation.tar" MEDIALABEL tar: blocksize = 20 a MEDIALABEL 1 block The file has been saved at : C:\Documents and Settings\user\teradata-client-linux-ttu-foundation.tar.gz 110 Teradata Tools and Utilities for Microsoft Windows Installation Guide