Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu

Transcription

1 What would you do if you knew? Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release B K May 2017

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Applications-Within, Aster, BYNET, Claraview, DecisionCast, Gridscale, QueryGrid, 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. Amazon Web Services, AWS, Amazon Elastic Compute Cloud, Amazon EC2, Amazon Simple Storage Service, Amazon S3, AWS CloudFormation, and AWS Marketplace are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. Apache, Apache Avro, Apache Hadoop, Apache Hive, 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. CENTOS is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Cloudera and CDH are trademarks or registered trademarks of Cloudera Inc. in the United States, and in jurisdictions throughout the world. Data Domain, EMC, PowerPath, SRDF, and Symmetrix are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries. 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 of Quest Software, Inc. 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. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. Simba, the Simba logo, SimbaEngine, SimbaEngine C/S, SimbaExpress and SimbaLib are registered trademarks of Simba Technologies Inc. SPARC is a registered trademark of SPARC International, Inc. 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. Veritas, the Veritas Logo and NetBackup are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. 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 noninfringement. 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 teradata-books@lists.teradata.com Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright by Teradata. All Rights Reserved.

3 Table of Contents Preface...7 Purpose... 7 Audience...7 Prerequisites...7 Revision History...7 Supported Releases...7 Additional Information...8 Product Safety Information... 8 Chapter 1: Preparing for Installation...9 About Using sudo for Login During Installation... 9 Installing sudo... 9 Configuring sudo... 9 Using sudo...9 About Teradata Tools and Utilities Installation Kit Contents...10 Software Packages About the Yum Repository File Execute the mkrepo.sh Script Setting up the TTU Repository on the Server Adding the TTU Repository to the YUM Configuration on the Client...13 Using the Bundle Available on the Local Machine to Configure the TTU Repository...14 Use the Repository with a Package Management Utility Product Descriptions...15 Product Dependencies...17 System Requirements Chapter 2: Uninstalling Software...21 About Retaining Existing Files for Teradata GSS Client...21 Uninstallation Script Overview...21 Uninstallation Script Operation...22 Uninstallation Script Usage and Parameters...22 List of Packages that are Uninstalled...23 Typical Output (rpm or deb)...25 Library File Checking Output Manually Uninstalling Packages...26 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

4 Table of Contents Chapter 3: Installing New Software About Installing Third-Party Software Installing Third-Party Software for Teradata Access Module for WebSphere MQ About Installing Teradata Tools and Utilities Disk Space Requirements...30 User Selectable Install Location Shared Drive Install Location...30 MultiVersion Support tdwallet Versions...31 Installation Order...31 Linux Setup Wrapper Install Configuration File...32 About Retaining and Deleting Data in Teradata Wallet Ensuring You Are Prompted About Teradata Wallet Data...33 Preparing to Install Teradata Tools and Utilities Interactively Installing Teradata Tools and Utilities...34 Silently Installing Teradata Tools and Utilities...36 Third-Party.ENV Files Installed Files Installing Missing Library Files...38 About Teradata Community Products Available from Teradata Community Downloading a Product from the Teradata Community...39 Installing Products Downloaded from Teradata Community...40 About Teradata Software Server (Patch Server) Downloading Updated Software Packages...40 Installing Updated (Patched) Software Packages Adding CLI User Exit Functions Chapter 4: Configuring New Software...43 About Configuring ODBC Driver for Teradata Configuring Teradata Parallel Transporter...43 About Configuring Teradata Parallel Transporter...43 Editing twbcfg.ini...43 Selecting Checkpoint and Log Directories in the Configuration File...44 Setting Parameters for Shared Memory...44 Setting Semaphore Parameters...45 Switching IPC Memory to Shared Memory...45 Switching IPC Memory to Mapped Memory Initializing Custom Configuration Settings for Teradata GSS Client Chapter 5: Verifying the Complete Installation About Verifying the Installation Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

5 Table of Contents Validating the BTEQ Installation Validating the ODBC Installation Verifying the Installation Using CLI Sample Program...49 Setting the JDBC Driver Classpath...50 Accessing Lists of Installed Files Chapter 6: Validating Product Readiness TTU Install Directory Path...53 Validating AccessModuleAmazonS3 (RedHat, SUSE)...53 Validating AccessModuleAzure (RedHat, SUSE) Validating AccessModuleKafka (RedHat, SUSE)...54 Validating AccessModuleMQ Validating AccessModuleNP...55 Validating DataConnector...55 Validating FastExport...55 Validating FastLoad...56 Validating MultiLoad Validating Teradata Java Message Service (JMS) Validating Teradata PT Validating Teradata Wallet...57 Validating TPump Chapter 7: Deploying Teradata Tools and Utilities with TAR...59 About Deploying Applications with TAR About the TAR File...59 TAR Script Compatibility with Platform Operating Systems...59 Verifying TAR Script Dependencies are Installed...60 The TAR Script Command...60 TAR Script Usage Considerations Downloading Windows Utility Software for TAR Deployment TAR Script Examples...64 Archiving Oracle Solaris SPARC Packages Archiving Linux Packages...65 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

6 Table of Contents 6 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

7 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 Prerequisites You should be familiar with: Computer technology and terminology Relational database management systems Utilities that load and retrieve data Revision History Date Release Description May Added Ubuntu operating system support Updated Teradata GSS client information to reflect the new Teradata GSS Administrative Package Supported Releases This document supports the following versions of Teradata products: Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

8 Preface Additional Information 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. Additional Information If you need additional information or assistance, contact your 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. Related Links URL Description Use Teradata At Your Service to access Orange Books, technical alerts, and knowledge repositories, view and join forums, and download software patches. External site for product, service, resource, support, and other customer information. Related Documents Title Publication ID Teradata Tools and Utilities Release Definition B Product Safety Information This document may contain information addressing product safety practices related to data or property damage, identified by the word Notice. A notice indicates a situation which, if not avoided, could result in damage to property, such as equipment or data, but not related to personal injury. Example Notice: Improper use of the Reconfiguration utility can result in data loss. 8 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

9 CHAPTER 1 Preparing for Installation About Using sudo for Login During Installation sudo allows a permitted user to execute a command as the super user or another user, as specified in the sudoers file, which enables you to grant the root access required for installing/uninstalling TTU packages. Installing sudo 1. Log on as the root user. 2. Download sudo at 3. Install sudo. Configuring sudo 1. Log on as the root user. 2. Run the following command to open the sudoers file: visudo 3. Add the appropriate line for the operating system to the sudoers file: Operating System AIX HPUX Linux (CentOS, RedHat, s390x, SUSE) Linux (Ubuntu) Solaris File Name ALL ALL=(root) NOPASSWD: /usr/sbin/installp *,/usr/bin/lslpp *,/usr/sbin/mount *,/usr/sbin/umount * ALL ALL=(root) NOPASSWD: /usr/sbin/swinstall *,/usr/ sbin/swremove *,/usr/sbin/swlist *,/usr/sbin/mount *,/usr/sbin/umount * ALL ALL=(root) NOPASSWD: /bin/rpm -ivh *,/bin/rpm -e *,/bin/mount *,/bin/umount * Ubuntu ALL ALL=(root) NOPASSWD: /bin/dpkg -i *,/bin/ dpkg -r*,/bin/dpkg -P *,/bin/mount *,/bin/umount * ALL ALL=(root) NOPASSWD: /usr/sbin/pkgadd *,/usr/ sbin/pkgrm *,/sbin/mount *,/sbin/umount * Using sudo 1. Run the sudo command to list the allowed commands for the user on the current host. sudo -l Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

10 Chapter 1: Preparing for Installation About Teradata Tools and Utilities 2. Run the sudo install/uninstall command. sudo command Example command for Linux: sudo rpm -ivh package About Teradata Tools and Utilities Before you perform the procedures in this document, you must meet the following prerequisites: Have network access Have Administrator privileges on the target machine Know which Teradata Tools and Utilities applications you are going to install Be familiar with naming conventions for Linux files and paths Have access to a bill of materials or similar list of Teradata Tools and Utilities software that was ordered Be familiar with software installation Installation Kit Contents The installation kit contains the following documentation media and application media: Teradata User Documentation (Teradata Database 16.10, Teradata Tools and Utilities 16.10) (B ) Teradata Tools and Utilities Release (IBM AIX, HP-UX, Solaris, Linux, Windows, Apple OS X), BCD Teradata Tools and Utilities Tape Storage Management Enablers (Windows, Linux), BCD If you did not receive all the installation media that you ordered, contact your Teradata Sales Representative. Software Packages The table below contains a list of the Teradata Tools and Utilities products that are in each software package. Products that support a specific operating system are noted. Note: In the table, the package titles are abbreviated: Abbreviation Base Database Management Tape Storage Management Software Package Teradata Tools and Utilities Release , BCD (IBM AIX, HP-UX, Linux, Solaris, Windows, Apple OS X) Teradata Tools and Utilities Database Management Release , BCD (Windows) Teradata Tools and Utilities Tape Storage Management Enablers Release , BCD (Windows, Linux) 10 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

11 Table 1: Products in Each Software Package Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Base Basic Teradata Query X X Open Database Connectivity (ODBC) Driver for Teradata X X Package Title (Abbreviated) Database Management Shared ICU Libraries for Teradata X X X Teradata Access Module for Amazon S3 (RedHat, SUSE) Teradata Access Module for Azure (RedHat, SUSE) Teradata Access Module for JMS Teradata Access Module for Kafka (RedHat, SUSE) Teradata Access Module for Named Pipes Teradata Access Module for WebSphere MQ Teradata Archive/Recovery Utility (Linux, Windows) Teradata C Preprocessor2 X X Teradata Call-Level Interface version 2 X X X Teradata Data Connector API X X X Teradata FastExport Teradata FastLoad Teradata GSS Administrative Package X X X Teradata JDBC Driver Teradata MultiLoad Teradata Parallel Data Pump Teradata Parallel Transporter Base Teradata Parallel Transporter Stream Teradata Wallet X X X X X X X X X X X X X X X X Tape Storage Management X Related Information Products Available from Teradata Community About the Yum Repository File A script file named mkrepo.sh is provided that can be used to create a local or URL yum repository: Teradata Tools and Utilities Release , BCD (IBM AIX, HP-UX, Linux, Solaris, Windows, Apple OS X) Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

12 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Teradata Tools and Utilities Tape Storage Management Enablers Release , BCD (Windows, Linux) The script is in the following directory:.../linux/i386-x8664 or.../ubuntu/i386-x8664 Complete the following steps: Execute the mkrepo.sh Script Setting up the TTU Repository on the Server Adding the TTU Repository to the YUM Configuration on the Client Using the Bundle Available on the Local Machine to Configure the TTU Repository Use the Repository with a Package Management Utility Execute the mkrepo.sh Script The mkrepo.sh script has to be executed from the.../linux/i386-x8664 folder. Usage:./mkrepo.sh [-u server -n <destination>] [-u client -n <repourl>] Parameters: [-u server -n <destination>] -u server: Script will set up the TTU YUM repository on the local Server -n <destination>: Denotes the absolute path of the destination folder to copy the TTU packages This destination must be the root folder of the web server or it should have symbolic link created to the root folder. Example Web server: Apache Note: httpd has to be installed on the server. [-u client -n <repourl>] -u client: Script will add existing TTU repository to YUM configuration -n <repourl> denotes weburl from which YUM can download the TTU packages Here, the assumption is that the TTU repository is available for download on the web server. Example repourl: If no input is given, the script assumes that the TTU Bundle is copied and extracted to the local machine. So, the script adds the local TTU repository to the YUM configuration. The script will prompt to copy the repository file to the system-specific repository location: For CentOS and RedHat - /etc/yum.repos.d For SUSE and s390x - /etc/zypp/repos.d Setting up the TTU Repository on the Server Set up the TTU repository that can be accessible via a URL. 1. Make sure the bundle is copied to target machine. 12 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

13 2. Make sure the web server is up and running on the target machine. Example web server: Apache 3. Log in to the target machine and change directory to the repository location available inside Bundle. cd <Bundle-Location>/<Linux Ubuntu>/<Arch> Here: <Bundle-Location> is the absolute location of the Bundle. <Linux Ubuntu>: Use Ubuntu on a Ubuntu system or Linux for all other Linux flavors. <Arch> is the TTU bundle-supported architectures, for example, i386-x8664, s390x. 4. Run the mkrepo.sh script as below: sh mkrepo.sh u server n <destination> -u server: Script will set up the TTU YUM repository on the local Server. -n denotes the absolute path of the destination folder to copy the TTU packages. This <destination> must be the root folder of the web server, or it should have a symbolic link created to the root folder. Example: sh mkrepo.sh u server n /var/www/html Successfully copied rpms from <Bundle-Location>/Linux/i386-x8664 to destination:/var/www/html/<ttu-version>/linux/<arch>/<mediatype> Please refresh your web server URL to check if rpms are available for download. Example url: Example RPM location: HYPERLINK " Linux/%3cArch%3e/%3cmediatype" <Arch>/<mediatype> Here: <Bundle-Location> is the absolute path of the Bundle. <TTU-Version> is the version of the TTU. Ex: <Arch> is the TTU bundle-supported architectures. Ex: i386-x8664, s390x. <Mediatype> is the type of the TTU media. Ex: BASE, TSME. Chapter 1: Preparing for Installation About Teradata Tools and Utilities Adding the TTU Repository to the YUM Configuration on the Client Add the TTU repository that can be accessible via an URL to YUM configuration 1. Copy the mkrepo.sh file from the Bundle (available on the server) that has to be installed to the client. 2. Make sure the TTU YUM repository is available for download on web server. 3. Run mkrepo.sh script as below: sh mkrepo.sh u client -n <repourl> -u client: Script will add the existing TTU repository to the local YUM configuration. -n denotes the weburl from which YUM can download the TTU packages. Here, the assumption is that the TTU repository is available for download on the web server. Example <repourl>: HYPERLINK " <TTU-Version> /Linux/<Arch>/<Mediatype> Ex: sh mkrepo.sh u client n x8664/base Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

14 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Adding to YUM configuration Use the following Yum repository file: Filename: /etc/yum.repos.d/ttu-foundation-1600.repo [ttu-foundation-1600] name=ttu Foundation 1600 i386-x8664 baseurl= i386-x8664/base/ enabled=1 gpgcheck= Copy /tmp/ttu-foundation-1600.repo to /etc/yum.repos.d? [y/n]: y 4. Provide y as input so that TTU repo will be added to YUM configuration. Here: <TTU-Version> is the version of the TTU. Ex: <Arch> is the TTU bundle-supported architectures. Ex: i386-x8664, s390x. <Mediatype> is the type of the TTU media. Ex: BASE, TSME. Using the Bundle Available on the Local Machine to Configure the TTU Repository Install TTU suites or packages through YUM using the bundle available on the local machine. 1. Make sure the Bundle is copied to target machine. 2. Change directory to the repository location available inside the Bundle: cd <Bundle>\Linux\i386-x Run the mkrepo.sh shell script (without any inputs) which will add the Teradata repository to the local YUM configuration: sh mkrepos.sh Use the following Yum repository file: Filename: /etc/yum.repos.d/teradata-ttu-foundation- <svernodot>.repo [teradata-ttu-foundation-<svernodot>]name=teradata TTU Foundation <svernodot> i386-x8664#baseurl= x8664baseurl=hyperlink "file:///\\" file:///<bundle-location>/linux/i386- x8664enabled=1gpgcheck= Copy /tmp/teradata-ttu-foundation-<svernodot>.repo to /etc/ yum.repos.d? [y/n]: y 4. Provide y as input so that the TTU repo will be added to the YUM configuration. Here: <Bundle-Location> is the absolute path of the Bundle. <svernodot> is the short version of the release version with no dot. 14 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

15 Use the Repository with a Package Management Utility After you create the repository file, you can use it with one of the following package management utilities or a similar product: For CentOS and RedHat - PackageKit For SUSE and s390x - YaST For Ubuntu - apt-get For all Linux OSs except Ubuntu - Yum For more information, see Using Yum to Manage Teradata Client Software. Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Descriptions Product Basic Teradata Query Open Database Connectivity (ODBC) Driver for Teradata Shared ICU Libraries for Teradata Teradata Access Module for Amazon S3 (RedHat, SUSE) Teradata Access Module for Azure (RedHat, SUSE) Teradata Access Module for JMS Teradata Access Module for Kafka (RedHat, SUSE) Teradata Access Module for Named Pipes Description 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. The Open Database Connectivity (ODBC) Driver for Teradata enables ODBC applications running on Microsoft Windows, UNIX/Linux and Apple OS X operating systems to communicate with the Teradata Database using the open standard ODBC interface. Shared ICU Libraries for Teradata is a library of routines based on IBM International Components for Unicode. The library provides Unicode support. Teradata Access Module for Amazon S3 is a component that allows to export data from Amazon S3 and to import data to Amazon S3. This utility works with the Teradata Parallel Transporter products. Teradata Access Module for Azure is a component that allows to export data from Micorsoft Azure Blob Storage and to import data to Microsoft Azure Blob Storage. This utility works with the Teradata Parallel Transporter 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 Access Module for Kafka is a component that allows to export data from Apache Kafka and to import data to Apache Kafka. This utility works with the Teradata Parallel Transporter products. Teradata Access Module for Named Pipes 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 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

16 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Teradata Access Module for WebSphere MQ Teradata Archive/Recovery Utility Description with Teradata FastExport, Teradata FastLoad, Teradata MultiLoad, and Teradata Parallel Data Pump. It is accessible from the command line. Teradata Access Module for WebSphere MQ 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 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 third-party backup applications. Teradata C Preprocessor2 Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata FastExport Teradata FastLoad Teradata GSS Administrative Package 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 and BTEQ. For additional information about Teradata Data Connector API, see the following documents: Teradata Tools and Utilities Access Module Programmer Guide (B ). Teradata Tools and Utilities Access Module Reference (B ). Teradata FastExport uses multiple sessions to quickly transfer large amounts of data from tables and views of a Teradata Database to a clientbased 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 Administrative Package is a collection of tools used to configure the embedded TeraGSS and debug those configurations when configuration is required. 16 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

17 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Teradata JDBC Driver Teradata MultiLoad Teradata Parallel Data Pump Teradata Parallel Transporter Base Teradata Parallel Transporter Stream Teradata Studio Express Teradata Wallet Description 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, highvolume maintenance on multiple tables and views of a Teradata Database. This utility is accessible from the command line or a script. 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. Teradata Parallel Transporter Base is a package that contains the scriptdriven interface (Teradata Parallel Transporter) and the application programming interface (Teradata Parallel Transporter API). Teradata Parallel Transporter is an object-oriented and scalable client application that allows you to perform high-speed, parallel data operations (extraction, loading, and updating) on a Teradata Database. 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 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 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. Product Dependencies Product Teradata Tools and Utilities Dependencies Third-party Dependencies Basic Teradata Query Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 None Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

18 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata Data Connector API Teradata Access Module for Amazon S3 (RedHat, SUSE) Teradata Access Module for Azure (RedHat, SUSE) Teradata Access Module for Kafka (RedHat, SUSE) Teradata Access Module for Named Pipes Open Database Connectivity (ODBC) Driver for Teradata Shared ICU Libraries for Teradata Teradata Archive/ Recovery Utility Teradata C Preprocessor2 Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata FastExport Teradata FastLoad Teradata GSS Administrative Package Teradata JDBC Driver None None None None Shared ICU Libraries for Teradata None Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Shared ICU Libraries for Teradata None Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API None None None None None None None None None None None None None None None JDK 1.4.2, JDK 5.0, JDK 6.0, JDK 7.0, JDK Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

19 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Teradata Tools and Utilities Dependencies Third-party Dependencies Note: The environment can be downloaded from Java Downloads. Teradata Access Module for JMS Teradata MultiLoad Teradata Access Module for WebSphere MQ None JRE 1.4.2, JRE 1.5, JRE 1.6, JRE 1.7, JRE 1.8 Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API 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 Parallel Data Pump Teradata Parallel Transporter Base Teradata Parallel Transporter Stream Teradata Studio Express Teradata Studio Teradata Plug-in for Eclipse Teradata Wallet Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Parallel Transporter Base None For Teradata Wallet help, at the command prompt enter tdwallet help. For more information about Teradata Wallet, see Security Administration (B ). None Progress DataDirect ConnectXE ODBC driver for Teradata (required only if you will use the ODBC operator) None Java Runtime Environment (JRE) 1.8 Note: JRE can be downloaded from Java Downloads. None Dependent Products During installation of Teradata Tools and Utilities, the following dependent products are automatically installed: Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

20 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API If a Dependent Product Is Already Installed If a dependent product already exists on the client system, one of the following messages is displayed: If the version of the product on the system is the same as the version of the product being installed, a message like this appears: ODBC Driver for Teradata version is already installed. Do you want to reinstall it? If the version of the product on the system is different than the version of the product being installed, a message like this appears: ODBC Driver for Teradata version is already installed. Do you want to overwrite it with version version? System Requirements When installing on a Linux system, use the Korn shell (/bin/ksh) before running the installation procedure for Teradata Tools and Utilities. This ensures correct execution of the installation script. Transmission Control Protocol/Internet Protocol (TCP/IP) is used to communicate with the Teradata Database. The client must be connected to one of the following: The same Ethernet LAN as the Teradata Database An Ethernet LAN that permits the client to communicate with the Teradata Database through one or more routers A node that is attached to the Teradata Database through BYNET. No separate network controller board or network software is required; the client provides its own. The appropriate Ethernet hardware and software supporting a TCP/IP-based network must be installed on every Teradata Database with which the client communicates. 20 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

21 CHAPTER 2 Uninstalling Software About Retaining Existing Files for Teradata GSS Client If you have custom configuration information in the TdgssUserConfigFile.xml file, make a copy of the file before uninstalling the software. After installing the new version, copy the configuration file to the appropriate location and execute run_tdgssconfig to initialize the custom configuration. See Initializing Custom Configuration Settings for Teradata GSS Client. For information on accessing and making changes to the TdgssUserConfigFile.xml file, refer to Security Administration (B ). Uninstallation Script Overview If you have an earlier version than of Teradata Tools and Utilities packages then use the uninstallation script, uninstall_ttu.sh, to uninstall previous versions of the packages before you install a new version unless you have a or later version that you want to co-exist with (see MultiVersion Support). The script uninstalls dependency packages in the correct order. The script is located on the installation media in the root directory. When the uninstallation script is executed from the install script, it prompts you to choose whether to uninstall packages from previous versions of Teradata Tools and Utilities and leave any currently installed versions installed. Run the uninstallation script before you do either of the following actions: install another version of Teradata Tools and Utilities (a version other than the existing one) decommission Teradata Tools and Utilities on a particular system Note: It is not necessary to uninstall previous versions of Teradata Wallet before you install another version of it. For information about retaining data in Teradata Wallet, see About Retaining and Deleting Data in Teradata Wallet. 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 Open Database Connectivity (ODBC) Driver for Teradata Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

22 Chapter 2: Uninstalling Software Uninstallation Script Overview When you run the script, you can specify individual packages to be uninstalled. Teradata recommends that you uninstall the dependency packages (CLIv2, PIOM, and TDICU) last; however they can be uninstalled individually regardless of the order. Notice: If a dependency package is uninstalled without reinstalling a new version of that dependency package, the products that depend on that package stop functioning. For example, if CLIv2 is uninstalled, all products that depend on CLIv2 stop functioning. In this case, the script warns you and asks if you are sure you want to uninstall it. The script does not require any parameters to execute. When the script runs, all information within the script is displayed. The script uses system packaging commands to uninstall packages, so it must be executed as root (or with root privileges). Uninstallation Script Operation The uninstallation script performs the following steps: 1. Searches for packages with "Teradata" in the package name installed on the system. 2. Creates an internal list of currently installed Teradata Tools and Utilities packages. 3. Checks the created list against a list of known Teradata Tools and Utilities packages (so only Teradata Tools and Utilities packages will be removed). 4. Reorders the created list to remove dependency products last. 5. Displays the list with additional information so you can decide whether to remove the packages or not. After the package removal process is complete, the script checks to see if any Teradata Tools and Utilities packages remain on the system. If any Teradata Tools and Utilities packages are found, it displays a list of those packages. Not all packages with "Teradata" in the package name are Teradata Tools and Utilities packages. Teradata DBS packages, for example, might contain "Teradata" in the package name, but would not be in the list of known Teradata Tools and Utilities packages. Uninstallation Script Usage and Parameters Usage Command uninstall_ttu.sh uninstall_ttu.sh priorto xx.xx.xx.xx uninstall_ttu.sh noremove uninstall_ttu.sh nocheck Description Executes the script to remove packages Removes all packages before a specific version number Executes the script, but does not remove any packages Executes the script, but does not check against known Teradata Tools and Utilities packages 22 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

23 Chapter 2: Uninstalling Software Uninstallation Script Overview Parameters priorto xx.xx.xx.xx noremove nocheck Removes packages prior to a specified version For example, if the packages to be installed on a system are from Teradata Tools and Utilities version 16.10, and packages prior to this version (15.10, 15.00, 14.10, 14.00, 13.10, 13.00, or 12.00) need to be removed, enter priorto The number parameter must contain all four version numbers, and can be specific enough to remove all packages before, for example, Typically the last two sets of digits would just be Executes the script without removing packages This parameter can be used to test the script without removing the packages. The package remove commands that would have been used to remove each package are displayed. This may be useful to do a test package remove without actually removing the packages, to see in what order the packages would have been removed, or to capture the commands used to remove the packages for use in another script. Executes the script looking for packages with "Teradata" in the package name, but skipping the check against the known list of Teradata Tools and Utilities packages This may be useful for packages the script does not know about or additional "Teradata" packages (not Teradata Tools and Utilities) that you may want to remove. Notice: Use this parameter with care, particularly if run on a Teradata DBS node, as important Database packages could be removed. debug Outputs useful debugging input to a file in /tmp/remove-tcp-debug-processid.out This may be useful for debugging purposes. It lists the known Teradata Tools and Utilities packages, the initial list of the packages selected, and the final ordered list, and could be helpful in determining why a package was not removed. List of Packages that are Uninstalled The uninstallation script recognizes the following Teradata Tools and Utilities packages: Basic Teradata Query (bteq) DUL/Dultape (dul and dultape) Open Database Connectivity (ODBC) Driver for Teradata (tdodbc) Shared ICU Libraries for Teradata (tdicu, tdicu_64, and so on) SQL C Preprocessor (sqlpp) Teradata Access Module for Amazon S3 (s3axsmod) Teradata Access Module for Azure (azureaxsmod) Teradata Access Module for JMS (jmsaxsmod) Teradata Access Module for Kafka (kafkaaxsmod) Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

24 Chapter 2: Uninstalling Software Uninstallation Script Overview Teradata Archive/Recovery Utility (teradata_arc) Teradata Call-Level Interface version 2 (cliv2, cliv2_64, cliv2so, and so on) Teradata Data Connector API (piom) Teradata FastExport (fastexp) Teradata FastLoad (fastld) Teradata GSS Administrative Package (teragssadmin) Teradata MultiLoad (mload) Teradata Access Module for Named Pipes (npaxsmod) Teradata Parallel Data Pump (tpump) Teradata Parallel Transporter Base (tptbase) Teradata Parallel Transporter Stream (tptstream) Teradata Wallet (tdwallet) Teradata Access Module for WebSphere MQ (mqaxsmod) This list is subject to change as future products are added to Teradata Tools and Utilities. On rare occasions files are left on systems after improper installations or uninstallations or if very old Teradata Tools and Utilities packages were installed by copying files to the /usr/bin or /usr/lib directories. The uninstallation script checks and displays a warning message that the files still exist and may cause problems. The script offers to rename the files and displays the command to remove them. The script does not delete the files automatically. If the files for the following products exist in the /usr/lib directory, the script renames them and adds the extension teradata-package-remove.old: Open Database Connectivity (ODBC) Driver for Teradata Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API 24 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10

25 Typical Output (rpm or deb) Package Removal Type: rpm... The following packages are installed: 1. bteq fastexp fastld mload mload mqaxsmod npaxsmod npaxsmod tdodbc tdwallet tptstream tpump tpump tptbase piom cliv cliv tdicu tdicu teragssadmin f. Display the full package information on the packages listed. a. Remove all of the above software. h. Display help information. q. Quit the package remove script. Enter one or more selections (separated by space): 16 cliv is a product dependency. Are you sure you wish to remove it? [Y/N] > Chapter 2: Uninstalling Software Uninstallation Script Overview Library File Checking Output If all files are not removed, output similar to this appears: WARNING: Teradata Libraries were found after post package removal. /usr/lib/libcliv2.so /usr/lib/libtdusr.so /usr/lib/libpm.so /usr/lib/libicudatatd.so /usr/lib/libicui18ntd.so /usr/lib/libicuiotd.so /usr/lib/libiculetd.so /usr/lib/libiculxtd.so /usr/lib/libicuuctd.so These files/softlinks may be the result of broken package uninstall and may interfere with future Teradata Client installations. Would you like to move these files to <filename>.teradata-package-remove.old in order to prevent this conflict? [Y/N] (default N): Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release

26 Chapter 2: Uninstalling Software Uninstallation Script Overview If you answer yes when asked if you would like to move these files, output similar to this appears: Moving /usr/lib/libcliv2.so to /usr/lib/libcliv2.so-teradata-package-remove.old Moving /usr/lib/libtdusr.so to /usr/lib/libtdusr.so-teradata-package-remove.old Moving /usr/lib/libpm.so to /usr/lib/libpm.so-teradata-package-remove.old Moving /usr/lib/libicudatatd.so to /usr/lib/libicudatatd.so-teradata-packageremove.old Moving /usr/lib/libicui18ntd.so to /usr/lib/libicui18ntd.so-teradata-packageremove.old Moving /usr/lib/libicuiotd.so to /usr/lib/libicuiotd.so-teradata-packageremove.old Moving /usr/lib/libiculetd.so to /usr/lib/libiculetd.so-teradata-packageremove.old Moving /usr/lib/libiculxtd.so to /usr/lib/libiculxtd.so-teradata-packageremove.old Moving /usr/lib/libicuuctd.so to /usr/lib/libicuuctd.so-teradata-packageremove.old To permanently remove these files execute the command : $ rm /usr/lib/*-teradata-package-remove.old If you answer no when asked if you would like to move these files, output similar to this appears: The following listed files have not been moved: /usr/lib/libcliv2.so /usr/lib/libtdusr.so /usr/lib/libpm.so /usr/lib/libicudatatd.so /usr/lib/libicui18ntd.so /usr/lib/libicuiotd.so /usr/lib/libiculetd.so /usr/lib/libiculxtd.so /usr/lib/libicuuctd.so These could cause problems later. It is recommended that these files be manually moved or removed before installing new Teradata Client Packages. Manually Uninstalling Packages Before installing a new version of Teradata GSS Client, you must first uninstall the previous version if the version is less than Note: When you uninstall previous versions, custom configuration settings are deleted. If you have custom configuration information in the TdgssUserConfigFile.xml file, make a copy of the file before uninstalling the software. After installing the new version, copy the configuration file to the appropriate location and execute run_tdgssconfig to initialize the custom configuration. See Initializing Custom Configuration Settings for Teradata GSS Client. For information on accessing and making changes to the TdgssUserConfigFile.xml file, refer to Security Administration (B ). If a package was not properly uninstalled by the uninstallation script, run the script again. To uninstall a package manually, follow these steps: 1. To see if a package is still installed, type: CentOS, RedHat, s390x, SUSE: rpm q packagename 26 Installation Guide CentOS, RedHat, SUSE, s390x, Ubuntu Release 16.10