Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Teradata Tools and Utilities for Linux Installation Guide CentOS
Document related concepts
no text concepts found
Transcript
What would you do if you knew?™ Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 B035-3160-086K November 2016 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, MyCommerce, 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, [any other AWS Marks used in such materials] 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, CDH, [any other Cloudera Marks used in such materials] 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 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. 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. 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 e-mail: [email protected] Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright © 2008 - 2016 by Teradata. All Rights Reserved. Table of Contents Preface...................................................................................................................................................................7 Purpose............................................................................................................................................................................ 7 Audience..........................................................................................................................................................................7 Prerequisites....................................................................................................................................................................7 Revision History.............................................................................................................................................................7 Supported Releases.........................................................................................................................................................8 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........................................................................................................................... 10 Installation Kit Contents.................................................................................................................................10 Software Packages............................................................................................................................................ 10 About the Yum Repository File..................................................................................................................... 11 Execute the mkrepo.sh Script............................................................................................................. 12 Setting up the TTU Repository on the Server.................................................................................. 12 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............................................................... 15 Product Descriptions.......................................................................................................................................15 Product Dependencies.....................................................................................................................................17 System Requirements...................................................................................................................................... 20 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................................................................................................................................................. 25 Library File Checking Output........................................................................................................................ 25 Manually Uninstalling Packages....................................................................................................................27 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 3 Table of Contents Chapter 3: Installing New Software............................................................................................................ 29 About Installing Third-Party Software..................................................................................................................... 29 Installing Third-Party Software for Teradata Access Module for WebSphere MQ............................... 29 About Installing Teradata Tools and Utilities......................................................................................................... 29 Disk Space Requirements................................................................................................................................30 User Selectable Install Location..................................................................................................................... 30 Shared Drive Install Location.........................................................................................................................30 MultiVersion Support..................................................................................................................................... 30 tdwallet Versions..................................................................................................................................31 Installation Order.............................................................................................................................................31 Linux Setup Wrapper...................................................................................................................................... 31 Install Configuration File................................................................................................................................32 About Retaining and Deleting Data in Teradata Wallet............................................................................ 32 Ensuring You Are Prompted About Teradata Wallet Data....................................................................... 32 Preparing to Install Teradata Tools and Utilities........................................................................................ 33 Interactively Installing Teradata Tools and Utilities.......................................................................33 Silently Installing Teradata Tools and Utilities................................................................................36 Third-Party .ENV Files................................................................................................................................... 38 Installed Files.................................................................................................................................................... 38 Installing Missing Library Files......................................................................................................................38 About Teradata Community.......................................................................................................................... 38 Products Available from Teradata Community.............................................................................. 39 Downloading a Product from the Teradata Community...............................................................39 Installing Products Downloaded from Teradata Community...................................................... 40 About Teradata Software Server (Patch Server).......................................................................................... 40 Downloading Updated Software Packages.......................................................................................40 Installing Updated (Patched) Software Packages............................................................................ 41 Adding CLI User Exit Functions................................................................................................................... 41 Chapter 4: Configuring New Software......................................................................................................43 About Configuring ODBC Driver for Teradata...................................................................................................... 43 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.............................................................................................. 45 Initializing Custom Configuration Settings for Teradata GSS Client.................................................................. 46 Chapter 5: Verifying the Complete Installation.......................................................................... 47 About Verifying the Installation................................................................................................................................ 47 4 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Table of Contents Validating the BTEQ Installation.................................................................................................................. 47 Validating the ODBC Installation................................................................................................................. 48 Verifying the Installation Using CLI Sample Program...............................................................................49 Setting the JDBC Driver Classpath............................................................................................................................50 Accessing Lists of Installed Files................................................................................................................................ 51 Chapter 6: Validating Product Readiness............................................................................................ 53 Validating AccessModuleAmazonS3 (RedHat, SUSE)...........................................................................................53 Validating AccessModuleKafka (RedHat, SUSE)....................................................................................................53 Validating AccessModuleMQ.................................................................................................................................... 54 Validating AccessModuleNP......................................................................................................................................54 Validating DataConnector..........................................................................................................................................54 Validating FastExport..................................................................................................................................................55 Validating FastLoad.....................................................................................................................................................55 Validating MultiLoad.................................................................................................................................................. 55 Validating Teradata Java Message Service (JMS).................................................................................................... 56 Validating Teradata PT............................................................................................................................................... 56 Validating Teradata Wallet.........................................................................................................................................56 Validating TPump........................................................................................................................................................57 Chapter 7: Troubleshooting the Installation...................................................................................59 Client Computer Problem: Cannot Communicate Over the Network with Teradata Database..................... 59 Client Computer Problem: Incorrect Path Name in COPANOMLOG...............................................................59 Client Computer Problem: Missing hosts File.........................................................................................................59 Client Computer Problem: Incorrect Entries in the hosts File..............................................................................59 Client Computer Problem: Missing Entries in the services File............................................................................60 Client Computer Problem: Improper Linking.........................................................................................................60 Client Computer Problem: Incorrect clispb.dat Parameters................................................................................. 60 Client Computer Problem: Cannot Log On from CLI Application..................................................................... 60 Client Computer Problem: Cannot Log On to Teradata Database.......................................................................60 Network Problems....................................................................................................................................................... 61 Teradata Database Problem........................................................................................................................................61 Teradata Parallel Transporter Problem: Unable to Find tbuild............................................................................ 62 Teradata Parallel Transporter Problem: Cannot Run New Version of TPT....................................................... 62 Teradata Parallel Transporter Problem: Unable to Find Messages...................................................................... 63 Chapter 8: Deploying Teradata Tools and Utilities with TAR...................................65 About Deploying Applications with TAR................................................................................................................ 65 About the TAR File..........................................................................................................................................65 TAR Script Compatibility with Platform Operating Systems........................................................65 Verifying TAR Script Dependencies are Installed...........................................................................65 The TAR Script Command.................................................................................................................66 TAR Script Usage Considerations..................................................................................................... 67 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 5 Table of Contents Downloading Windows Utility Software for TAR Deployment............................................................... 69 TAR Script Examples.......................................................................................................................................70 Archiving Oracle Solaris SPARC Packages...................................................................................... 70 Archiving Linux Packages...................................................................................................................72 6 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Preface Purpose This book describes how to install and deploy Teradata Tools and Utilities Release 16.00 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 November 2016 16.00 • CentOS: Initial release • RedHat, SUSE: Added support for Teradata Access Module for Amazon S3 and Teradata Access Module for Kafka • Added multiversion support • Added user selectable installation location support • Added information to the Yum Repository section Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 7 Preface Supported Releases Supported Releases This document supports the following versions of Teradata products: • Teradata Database Release 16.00 • Teradata Tools and Utilities Release 16.00 • To locate detailed information about supported releases, refer to the spreadsheet Teradata Tools and Utilities Supported Platforms and Product Versions (B035-3119). 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 https://tays.teradata.com Use Teradata At Your Service to access Orange Books, technical alerts, and knowledge repositories, view and join forums, and download software patches. http://www.info.teradata.com External site for product, service, resource, support, and other customer information. Related Documents Title Publication ID Teradata Tools and Utilities Release Definition B035-2029 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 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 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 http://www.sudo.ws/sudo/download.html. 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 File Name AIX ALL ALL=(root) NOPASSWD: /usr/sbin/installp *,/usr/bin/lslpp *,/usr/sbin/mount *,/usr/sbin/umount * Linux ALL ALL=(root) NOPASSWD: /bin/rpm -ivh *,/bin/rpm -e *,/bin/mount *,/bin/umount * Solaris ALL ALL=(root) NOPASSWD: /usr/sbin/pkgadd *,/usr/ sbin/pkgrm *,/sbin/mount *,/sbin/umount * HPUX ALL ALL=(root) NOPASSWD: /usr/sbin/swinstall *,/usr/ sbin/swremove *,/usr/sbin/swlist *,/usr/sbin/mount *,/usr/sbin/umount * Using sudo 1. Run the sudo command to list the allowed commands for the user on the current host. sudo -l 2. Run the sudo install/uninstall command. sudo command Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 9 Chapter 1: Preparing for Installation About Teradata Tools and Utilities 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.00, Teradata Tools and Utilities 16.00) (B035-1909) • Teradata Tools and Utilities Release 16.00 (IBM AIX, HP-UX, Solaris, Linux, Windows, Apple OS X), BCD0-2090-0000 • Teradata Tools and Utilities Tape Storage Management Enablers 16.00 (Windows, Linux), BCD0-2092-0000 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: 10 Abbreviation Software Package Base Teradata Tools and Utilities Release 16.00, BCD0-2090-0000 (IBM AIX, HP-UX, Linux, Solaris, Windows, Apple OS X) Database Management Teradata Tools and Utilities Database Management Release 16.00, BCD0-2091-0000 (Windows) Tape Storage Management Teradata Tools and Utilities Tape Storage Management Enablers Release 16.00, BCD0-2092-0000 (Windows, Linux) Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Table 1: Products in Each Software Package Product Package Title (Abbreviated) Base Database Tape Storage Management Management Basic Teradata Query X X Open Database Connectivity (ODBC) Driver for Teradata X X Shared ICU Libraries for Teradata X X Teradata Access Module for Amazon S3 (RedHat, SUSE) X Teradata Access Module for JMS X Teradata Access Module for Kafka (RedHat, SUSE) X Teradata Access Module for Named Pipes X Teradata Access Module for WebSphere MQ X Teradata Archive/Recovery Utility (Linux, Windows) X 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 Teradata JDBC Driver X Teradata MultiLoad X Teradata Parallel Data Pump X Teradata Parallel Transporter Base X Teradata Parallel Transporter Stream X Teradata Wallet X X 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 16.00, BCD0-2090-0000 (IBM AIX, HP-UX, Linux, Solaris, Windows, Apple OS X) • Teradata Tools and Utilities Tape Storage Management Enablers Release 16.00, BCD0-2092-0000 (Windows, Linux) Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 11 Chapter 1: Preparing for Installation About Teradata Tools and Utilities The script is in the following directory: • .../Linux/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: http://server-address/16.00.00.00/Linux/i386-x8664/BASE 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. 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. 12 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 1: Preparing for Installation About Teradata Tools and Utilities cd <Bundle-Location>/Linux/<Arch> Here: • <Bundle-Location> is the absolute location of the Bundle. • <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: http://server-address/ Example RPM location: HYPERLINK "http://server-address/%3cTTU-Version%3e/ Linux/%3cArch%3e/%3cmediatype" http://server-address/<TTU-Version>/Linux/ <Arch>/<mediatype> Here: • • • • <Bundle-Location> is the absolute path of the Bundle. <TTU-Version> is the version of the TTU. Ex: 16.00.00.00. <Arch> is the TTU bundle-supported architectures. Ex: i386-x8664, s390x. <Mediatype> is the type of the TTU media. Ex: BASE, TSME. 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 "http://server-address/%3cTTU-Version" http://server-address/ <TTU-Version> /Linux/<Arch>/<Mediatype> Ex: sh mkrepo.sh –u client –n http://server-address/16.00.00.00/Linux/i386x8664/BASE Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 13 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Adding http://sdlc8682.labs.teradata.com/16.00.00.00/Linux/i386-x8664/BASE/ 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=http://sdlc8682.labs.teradata.com/16.00.00.00/Linux/ i386-x8664/BASE/ enabled=1 gpgcheck=0 ----------------------------------------------------------------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: 16.00.00.00 • <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-x8664 3. 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=http://server-address/path/i386x8664baseurl=HYPERLINK "file:///\\" file:///<Bundle-Location>/Linux/i386x8664enabled=1gpgcheck=0----------------------------------------------------------------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 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 1: Preparing for Installation About Teradata Tools and Utilities 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 all Linux OSs - Yum For more information, see Using Yum to Manage Teradata Client Software . Product Descriptions Product Description Basic Teradata Query 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. Open Database Connectivity (ODBC) Driver for Teradata 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 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 (RedHat, SUSE) 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 JMS 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 (RedHat, SUSE) 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 Teradata Access Module for Named Pipes is a component that provides an Pipes 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 Access Module for WebSphere MQ 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 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 15 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Description MultiLoad, and Teradata Parallel Data Pump. It is accessible from a command line. Teradata Archive/Recovery Utility 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 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 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 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 (B035-2424). • Teradata Tools and Utilities Access Module Reference (B035-2425). Teradata FastExport 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 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 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 JDBC Driver Teradata JDBC Driver is a library of routines that enables Java applications to connect to a Teradata Database. Teradata MultiLoad 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. 16 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Description Teradata Parallel Data Pump 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 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 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 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 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 Teradata Data Connector API Teradata GSS Client None Teradata Access None Module for Amazon S3 (RedHat, SUSE) Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 None 17 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata Access Module for Kafka (RedHat, SUSE) None None Teradata Access Module for Named Pipes None None Open Database Connectivity (ODBC) Driver for Teradata Shared ICU Libraries for Teradata Teradata GSS Client None Shared ICU Libraries None for Teradata None Teradata Archive/ Recovery Utility Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client None Teradata C Preprocessor2 Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client None Teradata Call-Level Interface version 2 Shared ICU Libraries for Teradata Teradata GSS Client None Teradata Data Connector API None None Teradata FastExport Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client None Teradata FastLoad Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client None Teradata GSS Client None None Teradata JDBC Driver None JDK 1.4 , JDK 5.0, or JDK 6.0 Teradata Access Module for JMS None 18 Note: The environment can be downloaded from Java Downloads. JRE 1.4 or later Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 1: Preparing for Installation About Teradata Tools and Utilities Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata MultiLoad Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client None Teradata Access Module for WebSphere MQ Teradata Data Connector API IBM WebSphere MQ 7.5 Teradata Parallel Data Pump Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client None Teradata Parallel Transporter Base Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Progress DataDirect ConnectXE ODBC driver for Teradata (required only if you will use the ODBC operator) Teradata Parallel Transporter Stream Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Teradata Parallel Transporter Base None Note: To display the version of WebSphere that is installed on the system, run the dspmqver command from the command line. Java Runtime Environment (JRE) 1.6 or later Teradata Studio Express Teradata Studio Teradata Plug-in for Eclipse Teradata Wallet Note: JRE can be downloaded from Java Downloads. None None For Teradata Wallet help, at the command prompt enter tdwallet help . For more information about Teradata Wallet, see Security Administration (B035-1100). 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 Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 19 Chapter 1: Preparing for Installation About Teradata Tools and Utilities • Teradata GSS Client 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 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 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 (B035-1100). Uninstallation Script Overview If you have an earlier version than 15.10.10 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 15.10.10 or later version that you want to co-exist with 16.00 (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 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 21 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, TDICU, and TeraGSS) 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 22 Command Description uninstall_ttu.sh Executes the script to remove packages uninstall_ttu.sh priorto xx.xx.xx.xx Removes all packages before a specific version number uninstall_ttu.sh noremove Executes the script, but does not remove any packages uninstall_ttu.sh nocheck Executes the script, but does not check against known Teradata Tools and Utilities packages Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 2: Uninstalling Software Uninstallation Script Overview Parameters priorto xx.xx.xx.xx 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.00, 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 16.00.00.00. The number parameter must contain all four version numbers, and can be specific enough to remove all packages before, for example, 16.00.00.01. Typically the last two sets of digits would just be 00.00. noremove 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. nocheck 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 JMS (jmsaxsmod) Teradata Access Module for Kafka (kafkaaxsmod) Teradata Archive/Recovery Utility (teradata_arc) Teradata Call-Level Interface version 2 (cliv2, cliv2_64, cliv2so, and so on) Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 23 Chapter 2: Uninstalling Software Uninstallation Script Overview • • • • • • • • • • • • • Teradata Data Connector API (piom) Teradata FastExport (fastexp) Teradata FastLoad (fastld) Teradata GSS Client (teragss) Teradata MultiLoad (mload) Teradata Access Module for Named Pipes (npaxsmod) Teradata Parallel Data Pump (tpump) Teradata Query Director (qrydir and sockclient) All Teradata Parallel Transporter packages up to Teradata Tools and Utilities 13.10 (Teradata Tools and Utilities 13.10, 13.0, and 12.0; TWB 5.0; TPT 8.1, 8.2, and 12.0) 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: • • • • • 24 Open Database Connectivity (ODBC) Driver for Teradata Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 2: Uninstalling Software Uninstallation Script Overview Typical Output Package Removal Type: rpm .............................................................. The following packages are installed: 1. bteq1510 - 15.10.00.00 2. fastexp1510 - 15.10.00.00 3. fastld1510 - 15.10.00.00 4. mload1510 - 15.10.00.00 5. mload1510 - 15.10.00.00 6. mqaxsmod1510 - 15.10.00.00 7. npaxsmod1510 - 15.10.00.00 8. npaxsmod1510 - 15.10.00.00 9. tdodbc1510 - 15.10.00.00 10. tdwallet1510 - 15.10.00.00 11. tptstream1510 - 15.10.00.00 12. tpump1510 - 15.10.00.00 13. tpump1510 - 15.10.00.00 14. tptbase1510 - 15.10.00.00 15. piom1510 - 15.10.00.00 16. cliv21510 - 15.10.00.00 17. cliv21510 - 15.10.00.00 18. tdicu1510 - 15.10.00.00 19. tdicu1510 - 15.10.00.00 20. TeraGSS - 15.10.00.00 21. TeraGSS32 - 15.10.00.00 f. a. h. q. Display the full package information on the packages listed. Remove all of the above software. Display help information. Quit the package remove script. Enter one or more selections (separated by space): 16 cliv21510 - 15.10.00.00 is a product dependency. Are you sure you wish to remove it? [Y/N] > Library File Checking Output If all files are not removed, output similar to this appears: Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 25 Chapter 2: Uninstalling Software Uninstallation Script Overview … 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): 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. 26 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 2: Uninstalling Software Uninstallation Script Overview 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 15.10.01.00. 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 (B035-1100). 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: rpm –q packagename 2. To manually uninstall a package, type: rpm –erase --ignoredeps packagename Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 27 Chapter 2: Uninstalling Software Uninstallation Script Overview 28 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 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. Installing Third-Party Software for Teradata Access Module for WebSphere MQ Note: To display the version of WebSphere that is installed on the system, run the dspmqver command from the command line. • Before you run Teradata Access Module for WebSphere MQ, download IBM WebSphere MQ 7.5 and install it according to the instructions in the downloaded package. About Installing Teradata Tools and Utilities Before you install Teradata Tools and Utilities software, always compare the versions available from the following resources: • Teradata Software Server • Teradata Community In general, software on the Teradata Software Server (TSS) will contain the most recent point release of a software product, followed by the Teradata Community. Note: The 16.00 release is not compatible with any pre-15.10.10 release. The main installer will provide the option to remove any pre-15.10.10 release before installing 16.00. If not removed, the pre-15.10.10 release will not work properly, and the 16.00 release also may have issues. Installation Type Description Installing from a Web URL Some Teradata Tools and Utilities have third-party dependencies. Install these dependencies from their respective URLs. Installing Bundle from TSS The initial distribution of software is avaliable on TSS. Using the installation script, install products on a single computer from the media. Installing from Teradata Community The download center may contain more current software packages. Packages on the download center include drivers and connectivity software. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 29 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities Installation Type Description Installing from Teradata Software Server Check the Teradata Software Server (also known as the Patch Server) for the latest version of software packages and patches. Installing from Teradata ESDM Server For more information about the Teradata Electronic Software Distribution Management (ESDM) program, see Electronic Software Distribution (ESD) Guide, BCD0-0718. Deploying using tar The Bundle includes files that allow you to deploy Teradata Tools and Utilities products across your network using tar.gz files and tar. Disk Space Requirements The following amount of disk space is required to install this release: 350 MB User Selectable Install Location The Teradata Tools and Utilities (TTU) Products can now be installed at a location provided by the user. All products of the same release (for example, 15.10, 16.00, etc.) must be installed at the same prefix. Shared Drive Install Location Installing on a shared drive is also supported. Installing in one location and then moving the files to a shared location is not supported. The installation has to be done on the shared drive. In this case, the .env files located in <prefix>/teradata/client/16.00/etc folder should be used by clients to access the release. <prefix> is provided during install and the default is "/opt". See Third-Party .ENV Files for a description of the .env files. MultiVersion Support The 16.00 release can co-exist with the 15.10.10.00 release and later versions. The active release will be the last release installed. For example, if 15.10.10.00 is installed then 15.10.10.00 is the active release. Now, if 16.00 is installed after installing 15.10.10.00, then 16.00 will become the active release. The releases can be installed in any order. Installing 16.00 then 15.10.10.00 makes 15.10.10.00 the active release. There is a script in the bin folder named ttulistproducts_unix.sh that can be used to set the active version if more than one release is installed. This script also indicates the current active version and lists all the products that are installed on the system. The difference between the active release and the non-active release is that the bin folder will be on PATH, /usr/lib and /usr/bin symbolic links will be created by default. The "Install Configuration File" section indicates how to change the default behavior. The notion of an active release will not apply when our software is installed on a shared location. See ThirdParty .ENV Files for a description of how to access a particular release. 30 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities tdwallet Versions If different versions of tdwallet are installed on the same system, then all versions have to be installed at the same prefix. This is to enable all versions of tdwallet installed on the same system to share the wallet data. If tdwallet 15.10 is installed at prefix /abc then the install path will be /abc/teradata/client/15.10. If tdwallet 16.00 is then installed on the same system then the prefix has to be the same as the installed 15.10 tdwallet which implies that the install path for 16.00 tdwallet will be /abc/teradata/client/16.00. Installation Order The main installer for UNIX should be used to install the initial release. The main installer automatically installs all products and their dependencies in the correct order. Using an alternative method to do the installation requires you to manually install the products in the correct order. The main installer supports installing silently so it should be used for deployment. The process is described in Silently Installing Teradata Tools and Utilities. It is strongly recommended that the UNIX main installer is used to do the initial install of 16.00 but we still support installing using "swinstall" to install the TTU packages. When installing individual products, they must be installed in the following order. 1. 2. 3. 4. 5. 6. Teradata GSS Client (teragss) Shared ICU Libraries for Teradata (tdicu) Teradata Wallet Teradata Call-Level Interface version 2 (cliv2) Teradata Data Connector API (piom) Any other products Note: If a pre-15.10.10.00 release is installed, the 16.00 installation will fail due to incompatible issues. Linux Setup Wrapper If installing products individually, the setup_wrapper.sh script should be used to ensure proper installation. The help information for the script is as follows: setup_wrapper.sh: usage: setup_wrapper.sh [-i installation directory] [-r rpm to install] [-h] [-s] -i:Takes an installation directory (prefix) as its argument. -r:Takes an rpm to install, from the current directory, as its argument. -h:Provides usage information. -s:Turns on silent installation. All products of the same version must be installed at the same prefix, so the setup_wrapper.sh script ensures the products are installed correctly. If the install prefix is specified in the Install Configuration file, then that will be used unless the install prefix is also specified on the command line. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 31 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities Note: The setup_wrapper.sh can be used to install an efix package, but the UNIX main installer should be used to do the initial install of 16.00. Install Configuration File An install configuration file can be provided to change the default behavior during install. The name of the file is ttu_install.cfg, and it should be placed in /var/opt/teradata. We support the following options (case insensitive): InstallDir=prefix ShareLibs=yes|no updateETC=yes|no If the ttu_install.cfg file is not found in /var/opt/teradata, then the value for both those options will default to yes. OptionName Value Meaning InstallDir prefix Install root location; for example, InstallDir=/abc ShareLibs no Symbolic links will not be created in /usr/lib, /usr/lib64, /usr/ include, and /usr/bin. ShareLibs yes Symbolic links will be created in /usr/lib, /usr/lib64, /usr/ include, and /usr/bin, if we are able to write to /usr/lib and /usr/bin. If we are not able to create the symbolic links, the install will fail. updateETC no /etc/profile and /etc/csh.login will not be updated. updateETC yes /etc/profile and /etc/csh.login will be updated. About Retaining and Deleting Data in Teradata Wallet When you uninstall Teradata Tools and Utilities, by default the data associated with Teradata Wallet is retained (not deleted). You can choose to have wallet data deleted by the uninstallation process. You do this by setting the TDWALLET_INTERACTIVE_INSTALL environment variable to 1 before you install Teradata Tools and Utilities. If the environment variable has been set to 1, you will be prompted during installation of Teradata Tools and Utilities to choose whether you want wallet data to be deleted during uninstallation. Related Information Ensuring You Are Prompted About Teradata Wallet Data Ensuring You Are Prompted About Teradata Wallet Data Before you install Teradata Tools and Utilities, perform this procedure to ensure you are prompted to retain or delete Teradata Wallet data. You will be prompted during installation of Teradata Tools and Utilities. If you choose to delete data, it will be deleted during uninstallation. 1. Set the TDWALLET_INTERACTIVE_INSTALL environment variable to 1: 32 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities # TDWALLET_INTERACTIVE_INSTALL=1 2. Export the environment variable: # export TDWALLET_INTERACTIVE_INSTALL Related Information About Retaining and Deleting Data in Teradata Wallet Preparing to Install Teradata Tools and Utilities Prerequisite To delete existing Teradata Wallet data, you must set the TDWALLET_INTERACTIVE_INSTALL environment variable to 1 before beginning installation; otherwise the prompt will not display. See: Ensuring You Are Prompted About Teradata Wallet Data 1. Untar the downloaded TTU release in some location and cd to that location. 2. Choose an installation type: Installation Type Description Interactively Installing Teradata Tools and Utilities Use menu selections to interactively install Teradata Tools and Utilities. Note: If you plan to delete Teradata Wallet data and you already set the environment variable to 1, use this installation process to receive the prompt. Silently Installing Teradata Tools and Use command line options to have a silent installation process. Utilities If you choose this method, the installer will uninstall previous releases and install the new ones without any interaction from you. About the Yum Repository File Use a TTU repository to install the software. Related Information Ensuring You Are Prompted About Teradata Wallet Data Software Packages Installing Missing Library Files Product Dependencies Interactively Installing Teradata Tools and Utilities Silently Installing Teradata Tools and Utilities Interactively Installing Teradata Tools and Utilities Use these steps to interactively install Teradata Tools and Utilities using menu selections. 1. Run ./setup.bat. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 33 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities Note: If an error message about one or more missing library files appears, use the yum install command to download and install the files. a. If a pre-15.10.10 version of TTU Client Utilities is installed, those packages are incompatible with this version and must be removed. A screen similar to the following will display: The following product(s) are incompatible with the version (16.00.00) of TTU to be installed: tdicu-14.10.00.00 The above product(s) must be removed before installing 16.00.00. The above products can be automatically removed at this time. Enter "Yes" to remove the above products and continue with the installation or "No" to cancel the installation? ([y/n] default: Y): 'Y' (Yes) Removes the previous packages. 'N' (No) Cancels the installation. A screen similar to the following displays: Cancelling the installation. Leaving packages prior to pre-15.10.10 installed. These packages should be removed before installing 16.00 packages. The installer exits if 'N' is entered. b. If a 15.10.10 or later release is installed, a screen similar to the following displays: The 15.10 TTU Client Software is currently installed and can co-exist with the 16.00 release. Enter "Yes" to remove the previous release(s) and continue with the installation or "No" to keep the previous release? ([y/n] default: Y): 2. If a previous release is installed and Yes was chosen, after the previous packages are uninstalled, the Teradata Tools and Utilities installation menu appears. It contains the following information and options: • Identifies the platform and media • Lists numbered products that can be installed, the package version numbers, and package sizes • Provides options for: ∘ Installing all software ∘ Removing previously installed software ∘ Displaying the sizes of the installed package ∘ Quitting the installation 3. If you are prompted about retaining Teradata Wallet data, choose whether to retain existing data or delete it: Option Action Y (Yes) Data is retained during uninstallation. 34 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities Option Action N (No) Data is deleted during uninstallation (if this is the last remaining version of Teradata Wallet to be uninstalled). 4. Select the packages to install. If a selected package has dependencies, the script automatically installs the dependencies in the correct order. Software will be installed in the following order: a. b. c. d. e. Teradata GSS Client (teragss) Shared ICU Libraries for Teradata (tdicu) Teradata Call-Level Interface version 2 (cliv2) Teradata Data Connector API (piom) Other Products For Teradata Wallet help, at the command prompt enter tdwallet help . For more information about Teradata Wallet, see Security Administration (B035-1100). 5. After reviewing product dependencies, select one of the following: Command Action Install All TTU Products Type the letter a. This installs all TTU products available on the media Except TDWallet (a) except for TDWallet. Install All TTU Products Type the letter w. This installs all TTU products available on the media, (w) including TDWallet. Install Selected Packages Type the numbers of the desired products and dependencies, separated by spaces, and press Enter. • Dependencies: If individual products are to be installed, first determine the product dependencies, such as CLIv2 or Teradata Data Connector API (piom). Enter the numbers for the dependencies at the prompt, separated by spaces. • Products: Enter the numbers for the products at the prompt, separated by spaces. Quit (q) Type the letter q to cancel the installation. 6. If this is the first install of this release and the installdir flag was not provided on the command line, enter the base directory (prefix) for installing files: Which directory should be used as a base dir (prefix) for installing files? <base_dir>/teradata/client/16.00 (default base dir: /opt): Note: All products must be installed to the same prefix, so subsequent installs of this release will automatically be installed to the same prefix. 7. Change back to the root directory. 8. Unmount the media drive. umount /mnt Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 35 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities 9. Remove the installation media from the media drive. Related Information Software Packages Installing Missing Library Files Product Dependencies About Retaining and Deleting Data in Teradata Wallet Silently Installing Teradata Tools and Utilities Use these steps to silently install Teradata Tools and Utilities from the command line. 1. Run ./setup.bat with one of the following command line options: Option Action ./setup.bat a Installs all packages and any required dependencies except tdwallet. ./setup.bat w Installs all packages and any required dependencies, including tdwallet. ./setup.bat bteq Installs one package (in this example, BTEQ) and any required dependencies. ./setup.bat arc bteq cobpp Installs three packages and any required dependencies (you can specify as many package names as you want). ./setup.bat 1 2 3 Installs package numbers 1, 2, and 3 and any required dependencies (you can specify as many package numbers as you want). ./setup.bat bteq installdir=/abc Installs BTEQ (in this example) in /abc/teradata/client/ 16.00 unless another 16.00 product is already installed at a different prefix. Note: If an error message about one or more missing library files appears, use the yum install command to download and install the files. A screen similar to the following will display. This example is from a Linux install using the setup.bat a command. Actual output will be specific to the platform. 36 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities ############# ### ### ### ###### ####### ## ### ## ## ## #### ### ## ## ## ## ## ### ## ## ## ## ## ### ##### ## ## ## ## ### ## ## ## ###### ## ### ## ## ## ## ## ### ## ## ## ## ## ### ######## #### ## ## ###### ## ######### ## ## ## #### ## #### ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ###### ## ## ###### ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##### ## ## # ## ## Welcome to the Teradata Tools and Utilities 16.00 installation v.16.00.00.00 Copyright 2002-2016 by Teradata. All rights reserved. IF YOU OR THE ENTITY FOR WHOM YOU ARE INSTALLING THIS SOFTWARE DOES NOT HAVE A WRITTEN LICENSE AGREEMENT WITH TERADATA FOR THIS SOFTWARE, DO NOT INSTALL, USE, OR ALLOW USE OF THIS SOFTWARE. … There is a previous release installed that is incompatible with the version of TTU to be installed. The XX.XX TTU Client Software should be removed before installing 16.00. The previously installed packages will be automatically removed at this Removing packages prior to version 15.10.10.00. … ....................................................................... The following packages are installed: 1. product XX.XX.XX.XX 2. product XX.XX.XX.XX … 15. product XX.XX.XX.XX 16. product XX.XX.XX.XX Removing: prod-XX.XX.XX.XX - XX.XX.XX.XX Removing: prod-XX.XX.XX.XX - XX.XX.XX.XX … Removing: prod-XX.XX.XX.XX - XX.XX.XX.XX ...................................................... Installing: Product-16.00.00.00 Preparing... ########################################### 1:Product ########################################### Installing: Product Preparing... ########################################### 1:Product ########################################### Installing: Product 1:Product ########################################### Adding xxxxx entry to /etc/services file. setting soft links in /usr/lib Installing: Product Preparing... ########################################### 1:Product ########################################### … > time. [100%] [100%] [100%] [100%] [100%] [100%] [100%] 2. Change back to the root directory. 3. Unmount the media drive. umount /mnt 4. Remove the installation media from the media drive. Related Information Software Packages Installing Missing Library Files Product Dependencies About Retaining and Deleting Data in Teradata Wallet Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 37 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities Third-Party .ENV Files The following .env files will be installed in the/opt/teradata/client/16.00/etc folder: ttu_bash_1600.env ttu_csh_1600.env These files can be sourced by third-party applications or used in a terminal window to allow easy access to that Teradata Tools and Utilities release (public executables and libraries). These files will be necessary when we support multiple releases. Installed Files Teradata Tools and Utilities products no longer depend on LD_LIBRARY_PATH and/or the symbolic links created in /usr/lib and /usr/lib64 to find and load any dependent Teradata Tools and Utilities library. The Teradata Tools and Utilities products now use relative paths to find and load Teradata Tools and Utilities dependent libraries. This implies that the installed files should not be moved. Moving any of the installed files to a different location can, and most likely will, result in failures. The symbolic links created in /usr/lib and /usr/lib64 are to allow third party applications, such as Informatica, to find our shared libraries. Installing Missing Library Files Prerequisite To be able to download library files from the Red Hat repository, you must have a Red Hat subscription. When you install Teradata Tools and Utilities, if an error message about one or more missing library files appears, use the yum install command. This command downloads the missing files from the Red Hat repository and installs them. For more information, see Using Yum to Manage Teradata Client Software . 1. Enter the following command: yum install library-file where library-file is one or more of the following library filenames (if you specify more than one file, separate the filenames with a space): • libstdc++.so.6 • libc.so.6 • libgcc_s.so.6 The appropriate library files are downloaded from the Red Hat repository and installed. About Teradata Community Some Teradata Tools and Utilities products can be downloaded from the Teradata Community Downloads page. 38 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities Note: Products downloaded from the Teradata Community 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 media or in the downloaded suite install package. Products Available from Teradata Community Note: Products and versions of them available from Teradata Community 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 • Open Database Connectivity (ODBC) Driver for Teradata suite (includes Teradata GSS Client and Teradata International Components for Unicode) Tools • Teradata Plug-in for Eclipse • Teradata Studio Express • Teradata Wallet Downloading a Product from the Teradata Community 1. Go to Teradata Community Downloads. The Teradata Downloads page with a list of selectable products appears. 2. Click the product name or the platform next to the product name. 3. Click the software package or text file to download. 4. You may be asked to enter a username and password or to create a username 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. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 39 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities Installing Products Downloaded from Teradata Community Note: [64-bit systems] When you install Teradata Tools and Utilities from media or the full suite downloaded install package, the 32-bit version and the 64-bit version of the product is installed. However, when you install Teradata Tools and Utilities from individual product packages that you downloaded from Teradata Software Server (the Patch Server) or from Teradata Community, only the version of the product that you downloaded (32-bit, 64-bit, or both) is installed. 1. 2. 3. 4. Log on as root (or change to root and enter the root password). Go to the location where you saved the compressed file. Read the readme file to see if it contains additional installation instructions or a list of dependencies. Uncompress and untar the files and dependent product packages into a folder for the setup packages. gunzip package_name | tar xvf 5. Uninstall the previous version of software: rpm -e package_name 6. If the product has dependencies, install them in the following order before you install the downloaded patch: a. Teradata GSS Client (teragss) b. Shared ICU Libraries for Teradata (tdicu) c. Teradata Call-Level Interface version 2 (cliv2) d. Teradata Data Connector API (piom) e. Other Products 7. Install the downloaded software: rpm -ivh --nodeps package_name 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. Note: [64-bit systems] When you install Teradata Tools and Utilities, the 32-bit version and the 64-bit version of the product is installed. 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. 2. 3. 4. 5. 6. 40 Log on to Teradata @ Your Service at https://tays.teradata.com. Click Software Downloads. In the Home tab, click the Teradata Client button. Click the platform. In the Teradata Client Released Software pane, select the Software base. Filter the list of available software. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities • 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 EMail, 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. 2. 3. 4. Log on as root (or change to root and enter the root password). Go to the location where you saved the compressed file. Read the readme file to see if it contains additional installation instructions or a list of dependencies. Uncompress and untar the files and dependent product packages into a folder for the setup packages. gunzip package_name | tar xvf 5. Uninstall the previous version of software: rpm -e package_name 6. If the product has dependencies, install them in the following order before you install the downloaded patch: a. Teradata GSS Client (teragss) b. Shared ICU Libraries for Teradata (tdicu) c. Teradata Call-Level Interface version 2 (cliv2) d. Teradata Data Connector API (piom) e. Other Products 7. Install the downloaded software: rpm -ivh --nodeps package_name Adding CLI User Exit Functions CLI User Exit functions are general purpose facilities that can be added to the CLI workstation architecture on the selected operating system. These functions allow user-defined processing to take place. 1. Change directories to the sample directory: cd /opt/teradata/client/16.00/sample 2. Modify the CliLgnEx.c or CliPPS.c file in the sample directory. 3. Compile and link using either the 32-bit or 64-bit version of the makefile to create a new shared object,libtdusr.so. Note: The Native compiler on IA64 is not supported. To compile the 32-bit version, type: make -f maketdusr.lx Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 41 Chapter 3: Installing New Software About Installing Teradata Tools and Utilities On 64-bit Red Hat Linux, the compiler always generates 64-bit binaries. The 32-bit makefile is not supported on 64-bit Red Hat Linux platforms. 4. Move the libtdusr.so file into the cli installation directory, and verify that libcliv2 exists in the same directory. 5. For more information on CLI User Exit Functions, see Teradata Call-Level Interface Version 2 Reference for Workstation-Attached Systems (B035-2418), Appendix D. 42 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 CHAPTER 4 Configuring New Software About Configuring ODBC Driver for Teradata After you install the Open Database Connectivity (ODBC) Driver for Teradata, you might need to configure the following items: • Environment variables • The odbc.ini template • ODBC data sources For complete information about configuring the Open Database Connectivity (ODBC) Driver for Teradata, see ODBC Driver for Teradata User Guide (B035-2509). Configuring Teradata Parallel Transporter About Configuring Teradata Parallel Transporter The Teradata Parallel Transporter configuration normally requires modifications to only one file in the Teradata Parallel Transporter installation directory: twbcfg.ini. Additionally, the system configuration may require modification of the following parameters: • Shared memory parameters ∘ shmesg ∘ shmmax ∘ shmmni • Semaphore parameters ∘ ∘ ∘ ∘ semmap semmni semmnu semmns Related Information Setting Parameters for Shared Memory Editing twbcfg.ini After the Teradata Parallel Transporter Base package is installed, the configuration file, TPT_install_directory/twbcfg.ini can be edited to change the default directory for checkpoint and logs. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 43 Chapter 4: Configuring New Software Configuring Teradata Parallel Transporter 1. Log on as the root user. 2. Use a text editor to edit the configuration file to change the checkpoint or logs directory. For example, if the logs directory is full, then you should change the logs directory to another directory with free disk space. Note: No kernel rebuild or reboot is required after making the changes in the configuration file. Selecting Checkpoint and Log Directories in the Configuration File The configuration file contains parameters that determine the default behavior for Teradata Parallel Transporter Base, such as default checkpoint and log directories. These must be selected. • Edit the configuration file and specify the Teradata Parallel Transporter default directory and default log directory. CheckpointDirectory='/opt/teradata/client/short version/tbuild/checkpoint', where ∘ CheckpointDirectory is the directory that contains the checkpoint files for Teradata Parallel Transporter jobs ∘ short version is the product version in short form (for example, 16.00) LogDirectory='/opt/teradata/client/short version/tbuild/logs', where ∘ LogDirectory is the directory that contains the binary logs for Teradata Parallel Transporter jobs ∘ short version is the product version in short form (for example, 16.00) Each Teradata Parallel Transporter job creates a job log in the jobs directory. Refer to Teradata Parallel Transporter Reference (B035-2436) on how to read the job log. Setting Parameters for Shared Memory The Teradata Parallel Transporter Base installation checks the values of the shared memory parameters for the required minimum values. If the value for a shared memory parameter is less than the minimum value, the installation recommends increasing the value to the minimum value. The shmmni parameter determines the system-wide limit on the number of shared memory segments that can be created. The shmmax parameter determines the maximum size of a shared memory segment. The minimum value is 4194304. 1. Log on as the root user. 2. Check the value of the shmmni parameter; the minimum value is 200: /sbin/sysctl kernel.shmmni 3. Add the following line in the /etc/rc.d/rc.local file to increase the shmmni parameter value to 200: echo 200 > /proc/sys/kernel/shmmni 4. To shut down the system in one minute, type: 44 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 4: Configuring New Software Configuring Teradata Parallel Transporter /sbin/shutdown -r +1 Setting Semaphore Parameters The Teradata Parallel Transporter Base installation checks the values of the semaphore parameters for the required minimum values. The installation does not support a formula value for a kernel parameter. If the value for a kernel parameter is less than the required minimum value, the installation recommends increasing the value to the minimum value. The most significant parameter is the semmns semaphore parameter, which determines the number of semaphores in the entire system. The default configuration allows 1000 semaphores in concurrent use. The default semmni parameter value is 1000. The default semmns parameter value is 1000. 1. Log on as the root user. 2. Check the value of the semmns semaphore parameter: /sbin/sysctl kernel.semmns 3. Add the following line in the /etc/rc.d/rc.local file to increase the semmns parameter value to 1000: echo 1000 > /proc/sys/kernel/semmns 4. To shut down the system in one minute, type: /sbin/shutdown -r +1 Switching IPC Memory to Shared Memory The default Interprocess Communication (IPC) memory choice is memory mapped. You can switch to shared memory. 1. Log on as the root user. 2. Change directory to the Teradata Parallel Transporter installation directory: cd TPT_install_directory 3. Remove the mmap directory: rm -rf mmap Teradata Parallel Transporter will use shared memory as the IPC memory choice. The change does not require a kernel rebuild or a reboot. Switching IPC Memory to Mapped Memory This task is only required when the Interprocess Communication (IPC) method has been changed from the default (memory mapped) to shared memory. 1. Log on as the root user. 2. Change directory to the Teradata Parallel Transporter installation directory: cd TPT_install_directory 3. Create the mmap directory and set the permissions to 777: mkdir mmap Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 45 Chapter 4: Configuring New Software Initializing Custom Configuration Settings for Teradata GSS Client chmod 777 mmap Teradata Parallel Transporter will use memory mapped as the IPC memory choice. The change does not require a kernel rebuild or a reboot. Initializing Custom Configuration Settings for Teradata GSS Client Prerequisite You must have already installed the new version of Teradata GSS Client and have a copy of the previously used TdgssUserConfigFile.xml file. Use these steps to reuse the TdgssUserConfigFile.xml file that you saved from the previous installation. For information on accessing and making changes to the TdgssUserConfigFile.xml file, refer to Security Administration (B035-1100). For the file paths listed in the steps below, prefix refers to the user selected directory (/opt is the default prefix). 1. Execute run_tdgssconfig to create the directory for the configuration file. It is located in the following directory: /prefix/teradata/client/version/bin 2. Copy TdgssUserConfigFile.xml to this directory: /prefix/teradata/client/etc/site 3. Execute run_tdgssconfig again to initialize the custom configuration. It is located in the following directory: /prefix/teradata/client/version/bin 46 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 CHAPTER 5 Verifying the Complete Installation About Verifying the Installation Use one or all of the following methods to verify the installation of Teradata Tools and Utilities: • Validating the BTEQ Installation • Validating the ODBC Driver Installation • Verifying the installation using the CLI Sample Program Validating the BTEQ Installation Refer to Basic Teradata Query Reference (B035-2414) for detailed information on how to use BTEQ. 1. Add the directory where BTEQ resides to the search path. 2. Change directory to the BTEQ directory. 3. Start BTEQ: bteq Output similar to the following appears: Teradata BTEQ 16.00.00.00 for platform. Copyright 1984-2014, Teradata Corporation. ALL RIGHTS RESERVED. Enter your logon or BTEQ command: 4. Log on to the Teradata Database: .logon dbcpath/username Enter the BTEQ logon command with a logon ID. Include the dbcpath if the Teradata Database dbcpath is not the default i_dbcpath specified in clispb.dat. 5. When prompted, enter the password. For example, if the Teradata Database has a dbcpath of Finance, the username is fml, and the password is fml, type: .logon Finance/fml Password: fml Output similar to the following appears: *** *** *** *** *** Logon successfully completed. Teradata Database Release is 16.00.00.00 Teradata Database Version is 16.00.00.00 Transaction Semantics are BTET. Session Character Set Name is 'ASCII'. *** Total elapsed time was 1 second. BTEQ -- Enter your DBC/SQL request or BTEQ command: Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 47 Chapter 5: Verifying the Complete Installation About Verifying the Installation Note: For information about security and connecting to a Teradata Database, see Security Administration (B035-1100). 6. Submit a sample Teradata SQL query: SELECT time; If the test passes, output similar to the following appears. *** Query completed. One row found. One column returned. *** Total elapsed time was 1 second. Time -------11:09:11 7. To see the version numbers for BTEQ and the key Teradata software it depends on, use the following BTEQ command: .SHOW VERSIONS which produces output similar to the following: .SHOW VERSIONS BTEQ Version 16.00.00.00 for platform CLIV2 : 16.00.00.00 COPERR.H : 16.00.00.00 COPTYPES.H : 16.00.00.00 DBCAREA.H : 16.00.00.00 DBCERR.H : 16.00.00.00 DBCHQEP.H : 16.00.00.00 MOSIIF.H : 16.00.00.00 PARCEL.H : 16.00.00.00 TERAGSS : 16.00.00.00 PIOM : 16.00.00.00 TDICU : 16.00.00.00 TDWALLET : 16.00.00.00 Database : 16.00.00.00 BTEQ linking date is Feb 4 2014 8. Log off of the Teradata Database and exit BTEQ. Related Information Client Computer Problem: Cannot Log On to Teradata Database Validating the ODBC Installation Refer to ODBC Driver for Teradata User Guide (B035-2509) for detailed information on how to use ODBC. The tdxodbc (32-bit) or tdxodbc64 (64-bit) tool can be used to validate the installation of ODBC Driver for Teradata. It is located in the directory: prefix/teradata/client/version/bin 1. Export the ODBCINI environment variable. export ODBCINI=prefix/teradata/client/ODBC/odbc.ini where 48 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 5: Verifying the Complete Installation About Verifying the Installation prefix – Base installation directory, which is usually /opt. ODBC – ODBC_32 for 32-bit or ODBC_64 for 64-bit. 2. Run the command: Use tdxodbc for 32-bit and tdxodbc64 for 64-bit. tdxodbdc -c SQLDriverConnect -C "DRIVER={Teradata};DBCName=databasename;UID=username;PWD=password;" -t where databasename – Name or IP address of the Teradata database username – Database username password – Database password If the ODBC Driver for Teradata is installed correctly, the tool displays information that it successfully connected to the database. Verifying the Installation Using CLI Sample Program To verify that the Teradata Tools and Utilities software installed properly, run the sample CLI application, clisamp. The program and its makefile are installed during installation of Teradata Tools and Utilities. 1. Modify the following makefile so it contains the correct directory paths to the include files: Operating System Directory Path RedHat or SUSE [32-bit] makesamp.lx RedHat or SUSE [64-bit] makesamp.lx64 s390x [32-bit] makesamp.390-32 s390x [64-bit] makesamp.390 2. Execute the makefile: make -f filename where filename is the name of the file in the previous step. The executable module named clisamp is created. 3. Change the mode of the executable to run: Operating System Mode to Run RedHat or SUSE [32-bit] chmod +x clisamp RedHat or SUSE-[64-bit] chmod +x clisamp_lx64 s390x [32-bit] chmod +x clisamp_390.32 s390x [64-bit] chmod +x clisamp_390.64 4. Run the sample program using one of the following commands: • Run the sample program using the default logon information (dbc/systemfe,service): Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 49 Chapter 5: Verifying the Complete Installation Setting the JDBC Driver Classpath Operating System Sample Program to Run RedHat or SUSE [32-bit] clisamp RedHat or SUSE [64-bit] clisamp_lx64 s390x [32-bit] clisamp_390.32 s390x [64-bit] clisamp_390.64 • Show help for the sample program: Operating System Command to Show Help RedHat or SUSE [32-bit] clisamp -h RedHat or SUSE [64-bit] clisamp_lx64 -h s390x [32-bit] clisamp_390.32 -h s390x [64-bit] clisamp_390.64 -h • Run the sample program using a user-provided input string: Operating System User-Provided Input String RedHat or SUSE [32-bit] clisamp tdpid/user,password RedHat or SUSE [64-bit] clisamp_lx64 tdpid/user,password s390x [32-bit] clisamp_390.32 tdpid/user,password s390x [64-bit] clisamp_390.64 tdpid/user,password The program logs on to the default dbccop1 (no user input supplied) specified in the /etc/hosts file, runs a simple query SELECT * from dbc.sessioninfo, and writes the output to the clisamp.dat file. A display similar to the following appears: CLIv2 version is 16.00.00.00 MTDP version is 16.00.00.00 MOSIOS version is 16.00.00.00 MOSIDEP version is 16.00.00.00 OSERR version is 16.00.00.00 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 (B035-1100). Setting the JDBC Driver Classpath The Teradata JDBC Driver is distributed as platform-independent jar files. 1. Copy the jar files into a directory. 50 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 5: Verifying the Complete Installation Accessing Lists of Installed Files 2. Set the classpath to refer to the necessary jar files. The classpath must include: • terajdbc4.jar • tdgssconfig.jar Accessing Lists of Installed Files You can verify that the installation created all the necessary files for the operating system by checking the lists of installed files. 1. Log into https://tays.teradata.com. 2. Click the Knowledge Search tab. 3. Enter the Knowledge Article Number in the search window. Operating System Knowledge Article Number Apple OS X KAP2C009E HP-UX KAP2C00A2 IBM AIX KAP2C00A6 IBM s390s, RedHat and SUSE KAP2C00AA Oracle Solaris on SPARC and Opteron KAP2C00AE Windows KAP2C00B2 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 51 Chapter 5: Verifying the Complete Installation Accessing Lists of Installed Files 52 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 CHAPTER 6 Validating Product Readiness Validating AccessModuleAmazonS3 (RedHat, SUSE) For more information about Teradata Access Module for Amazon S3, see Teradata Tools and Utilities Access Module Reference (B035-2425). 1. 2. 3. 4. 5. Open a command prompt. Create the $HOME/.aws directory. Create the config File and the credentials File under $HOME/.aws directory. Change directory to S3AXSMOD_install_directory/sample/validate. Run the command /validate.sh S3BucketName S3DirectoryName S3ObjectName where the following is true: • S3BucketName is the Amazon S3 bucket name. • S3DirectoryName is the folder name which will be created under Amazon S3 bucket to store the Amazon S3 object. • S3ObjectName is the Amazon S3 object name. Validating AccessModuleKafka (RedHat, SUSE) For more information about Teradata Kafka Access Module, see Teradata Tools and Utilities Access Module Reference (B035-2425). 1. 2. 3. 4. Open a command prompt. Create a database username and password. Change directory to KAFKAAXSMOD_install_directory/sample/validate. Run the command ./kafkaaxsmod_validate.ksh <NODEID> <UserName> <UserPassword> <TOPICNAME> <BROKER> <PARTITIONS> where the following is true: • • • • • <NODEID> is a database name id. <UserName> is database User Name. <TOPICNAME> is a Kafka Message Server topic name. <BROKER> is a kafka Message Server Broker, e.g., KAFKASERVERIPADDRESS:PORTNO. <PARTITIONS> is partitions of the topic, e.g., 0,1. The script will execute kafkaaxsmod_qstart.tpt in the quickstart directory. User needs to ensure that Teradata Parallel Transpoter is installed on the system. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 53 Chapter 6: Validating Product Readiness Validating AccessModuleMQ Validating AccessModuleMQ For more information about Teradata AccessModuleMQ, see Teradata Tools and Utilities Access Module Reference (B035-2425). 1. 2. 3. 4. 5. 6. Open a command prompt. Create a database username and password. Change directory to MQAXSMOD_install_directory/sample/quickstart. Update mqaxsmod_parmfile accordingly. Change directory to MQAXSMOD_install_directory/sample/validate. Run the command ./mqaxsmodvalidate.ksh Tdpid UserName UserPassword, where the following is true: • • • • The validation script executes mqaxsmodqstart.fl in the quickstart directory Tdpid is a database ID UserName is a database username UserPassword is a database user password Validating AccessModuleNP For more information about Teradata AccessModuleNP, see Teradata Tools and Utilities Access Module Reference (B035-2425). 1. 2. 3. 4. 5. Open a command prompt. Create a database username and password. Change directory to NPAXSMOD_install_directory/sample/quickstart. Change directory to NPAXSMOD_install_directory/sample/validate. Run the command ./npaxsmodvalidate.ksh Tdpid UserName UserPassword, where the following is true: • The validation script executes npaxsmodqstart.fl and npaxsmodqstart.fe in the quickstart directory • Tdpid is a database ID • UserName is a database username • UserPassword is a database user password Validating DataConnector For more information about the Teradata Data Connector, see the Teradata Tools and Utilities Access Module Reference (B035-2425). 1. 2. 3. 4. 54 Open a command prompt. Create a database username and password. Change directory to PIOM_install_directory/sample/validate. Run the command ./piomvalidate.ksh Tdpid UserName UserPassword, where the following is true: Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 6: Validating Product Readiness Validating FastExport • • • • The validation script executes piomqstart.fl in the quickstart directory Tdpid is a database ID UserName is a database username UserPassword is a database user password Validating FastExport For more information about FastExport, see the Teradata FastExport Reference (B035-2410). 1. 2. 3. 4. Open a command prompt. Create a database username and password. Change directory to FastExport_install_directory/sample/validate. Run the command ./fexpvalidate.ksh Tdpid UserName UserPassword, where the following is true: • • • • The validation script executes fexp_sample.fe in the quickstart directory Tdpid is a database ID UserName is a database username UserPassword is a database user password Validating FastLoad For more information about Teradata FastLoad, see Teradata FastLoad Reference (B035-2411). 1. 2. 3. 4. Open a command prompt. Create a database username and password. Change directory to fastLoad_install_directory/sample/validate. Run the command ./flodvalidate.ksh Tdpid UserName UserPassword, where the following is true: • • • • The validation script executes flod_sample.ml in the quickstart directory Tdpid is a database ID UserName is a database username UserPassword is a database user password Validating MultiLoad For more information about Teradata MultiLoad, see Teradata MultiLoad Reference (B035-2409). 1. 2. 3. 4. Open a command prompt. Create a database username and password. Change directory to mload_install_directory/sample/validate. Run the command ./mloadvalidate.ksh Tdpid UserName UserPassword, where the following is true: • The validation script executes mload_sample.ml in the quickstart directory Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 55 Chapter 6: Validating Product Readiness Validating Teradata Java Message Service (JMS) • Tdpid is a database ID • UserName is a database username • UserPassword is a database user password Validating Teradata Java Message Service (JMS) For more information about Teradata JMS, see the Teradata Tools and Utilities Access Module Reference (B035-2425). 1. 2. 3. 4. 5. 6. Open a command prompt. Create a database username and password. Change directory to JMSAXSMOD_install_directory/sample/quickstart. Update jmsaxsmod_parmfile accordingly. Change directory to JMSAXSMOD_install_directory/sample/validate. Run the command ./jmsaxsmodvalidate.ksh Tdpid UserName UserPassword, where the following is true: • • • • The validation script executes jmsaxsmodqstart.fl in the quickstart directory Tdpid is a database ID UserName is a database username UserPassword is a database user password Validating Teradata PT For more information about Teradata Parallel Transporter, see Teradata Parallel Transporter Reference (B035-2436). 1. 2. 3. 4. Open a command prompt. Create a database username and password. Change directory to TPT_install_directory/sample/validate. Run the command ./tptvalidate.ksh Tdpid UserName UserPassword, where the following is true: • Tdpid is a database ID • UserName is a database username • UserPassword is a database user password Validating Teradata Wallet For more information about Teradata Wallet, see Security Administration (B035-1100). To see the Teradata Wallet help, enter tdwallet help from the command prompt. 1. Open a command prompt. 2. Change directory to Teradata Wallet install directory. 3. Run the command ./validate.sh. 56 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 6: Validating Product Readiness Validating TPump Validating TPump Refer to Teradata Parallel Data Pump Reference (B035-3021) for detailed information on how to use TPump. 1. 2. 3. 4. Open a command prompt. Create a database username and password. Change directory to TPump_install_directory/sample/validate. Run the command ./tpumpvalidate.ksh Tdpid UserName UserPassword, where the following is true: • • • • The validation script executes tpump_sample.tp in the quickstart directory Tdpid is a database ID UserName is a database username UserPassword is a database user password Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 57 Chapter 6: Validating Product Readiness Validating TPump 58 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 CHAPTER 7 Troubleshooting the Installation Client Computer Problem: Cannot Communicate Over the Network with Teradata Database 1. To confirm that a client can communicate over the network to a Teradata Database, ping the Teradata Database: /usr/etc/ping dbcnameCOPn dbcnameCOPn can appear in upper or lower case. The following is returned as a positive response: dbcnameCOPn is alive 2. To perform the second test to verify communication to the Teradata Database, type: telnet dbcnameCOPn The following response is returned: telnet: connect: Connection refused 3. If these responses are not received, consult Troubleshooting Network Problems. Client Computer Problem: Incorrect Path Name in COPANOMLOG • To produce an anomaly log file, verify that the COPANOMLOG environment variable has the correct path name to the anomaly log file. Client Computer Problem: Missing hosts File • Verify that the /etc/hosts file exists on the client. Client Computer Problem: Incorrect Entries in the hosts File • Check the following entries in the /etc/hosts file or in the hosts file on the NIS master: ∘ Check all entries for incorrect, missing, or duplicate network addresses of COPs, APs, or nodes. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 59 Chapter 7: Troubleshooting the Installation Client Computer Problem: Missing Entries in the services File Remember that a TCP/IP (Internet) address is a 4-byte value in the form a.b.c.d. COPs, APs, or nodes on the same logical network must have the same network ID portion of the network address. ∘ Check that COPs, APs, or nodes in the same group for a Teradata Database have the same dbcname and are numbered sequentially, starting with 1. Remember that the format of a COP name is dbcnameCOPn, where dbcname must begin with an alphabetic character. Client Computer Problem: Missing Entries in the services File • Verify that the following lines are in the /etc/services file or the services file on the NIS master. tdmst tdses 1025/udp 1025/tcp Client Computer Problem: Improper Linking • Check that the software files are linked properly with your application. Whenever maintenance or upgrade software is installed, relink all applications. Client Computer Problem: Incorrect clispb.dat Parameters 1. Verify that the parameters in the system parameter block file, clispb.dat, have correct values. 2. Set the default i_dbcpath to correspond to the dbcnames in the /etc/hosts file or in the hosts file on the NIS master. Client Computer Problem: Cannot Log On from CLI Application 1. If you cannot log on to the Teradata Database from a CLI application, try to log on from Basic Teradata Query (BTEQ). 2. If you can log on from BTEQ, check the CLI application for errors. Client Computer Problem: Cannot Log On to Teradata Database • If you cannot log on to a Teradata Database, try logging on to a different database. 60 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 7: Troubleshooting the Installation Network Problems If you can log on to a different database, there is a problem with the first database or an incorrect address for the first database computer in the /etc/hosts file or the hosts file on the NIS master. Network Problems If there is a network problem, use the following procedure to troubleshoot whether the problem is with network hardware or software. All steps may not be required. 1. 2. 3. 4. 5. 6. 7. Verify that the transceiver is connected to the network, client, and Teradata Database. Check for broken or disconnected network cables. Verify that drop cables are not too long. The cables must comply with IEEE 802.3 standards. Verify that all repeaters, bridges, routers, and gateways are functioning properly. Verify that all jumpers are setup correctly on the client's network controller board. Verify that the network software is installed and running properly on the client. Verify that the network software is compatible with the network controller board installed on the client. Confirm that the network is operational by using a network utility program. Use Basic Teradata Query or a network utility program from another client on the same network segment as the first client. If this works, there may be a problem with the first client. Use Basic Teradata Query or a network utility program from another client on a different network segment from the first client. If this works, there may be a problem with the first network segment. If a network controller board is replaced on the client, reboot Teradata Database so it can obtain the network address of the new board. If the network configuration was changed, check that all network related files were changed accordingly. Reboot the client to reset network hardware and reload network software. 8. 9. 10. 11. 12. 13. Teradata Database Problem Teradata Database problems should be diagnosed with the assistance of a field service representative. 1. Log on to the Teradata Database computer from the operator's console, another network-attached host, or a mainframe. If the logon succeeds, the Teradata Database is operational. If you are unable to log on, contact a field representative. 2. Have a field representative verify that the adaptor cable is connected. 3. Have a field representative check the Multibus Adaptor Board (MAB). 4. Perform the following tests for all entries in CopInfoTbl on the Teradata Database. • • • • • Check for incorrect, missing, or duplicate cabinet and processor numbers (ccc_p). Check for incorrect, missing, or duplicate network addresses. Check for the correct network protocol type (CopKind) for each COP. Check for the correct host number for each COP, AP, or node. Verify that the entries in CopInfoTbl match the entries in the /etc/hosts file (on the client) or the hosts file on the NIS master. Use the CopUpdate macro to change CopInfoTbl. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 61 Chapter 7: Troubleshooting the Installation Teradata Parallel Transporter Problem: Unable to Find tbuild 5. If a COP, AP, or node is added to or removed from the Teradata Database or if the network address a COP is changed, execute the CopUpdate macro so the Teradata Database can determine changes to network addresses. Restart the Teradata Database for the changes to take effect. 6. If using Internet routing (routers), perform the following tests for CopRoutesTbl: • Check for incorrect or missing network addresses of destinations. • Check for incorrect or missing network addresses of routes. • Verify that each router is identified by two (or more) Internet addresses, one for each network on which it resides. Use the TcpRoute macro to change CopRoutesTbl. 7. If a subnet outing (subnetting) is used, check CopOptionsTbl for incorrect or missing subnet masks. 8. Use the AddOption macro to change CopOptionsTbl. 9. If the Teradata Database goes down and then comes back up, its sessions table still contains information about the sessions generated by hosts. The Teradata Database expects to receive reconnect messages from hosts. If the Teradata Database does not receive the reconnect messages within 20 minutes after it comes back up, it removes the sessions that were generated by hosts that have not reconnected from the sessions table. This implies that for 20 minutes after the Teradata Database comes back up, some sessions are being kept that may not be used. If use of the Teradata Database is heavy, users unable to log on during that 20 minute period (because the maximum number of sessions has been reached) can try again after the unclaimed sessions are cleared away. Teradata Parallel Transporter Problem: Unable to Find tbuild If the path to tbuild cannot be found: 1. Log off of the system and then log on again. 2. Rerun the Teradata Parallel Transporter job. 3. If you still cannot find tbuild, verify that the TTU_install_directory/bin path is in the PATH environment variable. 4. If the TTU_install_directory/bin path is not in the environment variable, add it to the front (the beginning) of the environment variable. 5. Run the Teradata Parallel Transporter job again. Teradata Parallel Transporter Problem: Cannot Run New Version of TPT If you cannot run the newly installed version of Teradata Parallel Transporter: 1. Log off of the system and then log on again. 2. Run the Teradata Parallel Transporter job again. 62 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 7: Troubleshooting the Installation Teradata Parallel Transporter Problem: Unable to Find Messages 3. If you are still unable to run the new installed version of Teradata Parallel Transporter, verify that the TTU_install_directory/bin path is in the PATH environment variable. 4. If the TTU_install_directory/bin path is not in the environment variable, add it to the front (the beginning) of the environment variable. 5. Run the Teradata Parallel Transporter job again. Teradata Parallel Transporter Problem: Unable to Find Messages 1. If an error messages similar to the following appears when executing a Teradata Parallel Transporter job, log off of the system and log on again. Message Catalog Error: Message 4000 was not found Message Catalog Error: Message 2014 was not found Message Catalog Error: Message 2041 was not found 2. Rerun the Teradata Parallel Transporter job. 3. If the error messages still appears, verify that the TTU_install_directory/msg path is in the PATH environment variable. 4. If the TTU_install_directory/msg path is not in the environment variable, add it to the front (the beginning) of the environment variable. 5. Rerun the Teradata Parallel Transporter job. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 63 Chapter 7: Troubleshooting the Installation Teradata Parallel Transporter Problem: Unable to Find Messages 64 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 CHAPTER 8 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 UNIX and Linux using the Korn shell /bin/ksh for the following platforms: • • • • • • • IBM AIX HP-UX Oracle Solaris SPARC Oracle Solaris Opteron SUSE Linux Red Hat Linux s390x zLinux Verifying TAR Script Dependencies are Installed The tar executable must be located in the PATH on the system running the script. On UNIX and Linux, tar is typically in the /bin directory. Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 65 Chapter 8: Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR • Ensure that the tar executable is located in the PATH on the system by running the script. tar only compresses a small amount, compared to the other platform's packages. The TAR Script Command To launch the TAR script, run tar_teradata_client_packages.sh. 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 Description tar_teradata_client_packages or tar_teradata_client_packages help Displays the available commands tar_teradata_client_packages list Displays the platforms and packages that are available on the installation media tar_teradata_client_packages list platform 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 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. tar_teradata_client_packages platform package 66 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: tar_teradata_client_packages aix bteq If you specify a package other than a dependent package, all of the following dependent packages are included in the archive: Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 8: Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR Command Description • • • • 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 dependent packages are included in the archive. tar_teradata_client_packages platform package1 package2 etc. 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_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 dependent packages are included in the archive. TAR Script Usage Considerations Subject Description Default Directory 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: • /home/username if you run the script as a standard user • /tmp if you run the script as root 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. Multiple and If a single package or multiple packages are selected, all of the dependent products are Dependent Packages 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. Getting Help on the Script To view command usage and optional command parameters, run tar_teradata_client_packages by itself or with the optional help parameter: Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 67 Chapter 8: Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR Subject Description • tar_teradata_client_packages • tar_teradata_client_packages help A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v.16.00.00.01 ************************************************************************ Usage: tar_teradata_client_packages list tar_teradata_client_packages list {platform} tar_teradata_client_packages {platform} [{package1} {package2} ...] Parameters: * commands help list : help, list, {platform} [{package1} {package2} ...] : Display this help message. : List the available platforms and packages from the media. list {platform} : List the packages available for the specified platform. {platform} : Available platforms: aix, ia64, i386, s390x, opteron, sparc, or terajdbc for the TeraJDBC product. 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: ./tar_teradata_client_packages.sh i386 bteq fastld The dependencies will automatically be included and do not need to be listed individually. The following packages are included: ---TeraGSS cliv2 tdicu piom Listing the Available All of the platforms and packages contained on the installation media can be listed by Packages and running the tar_teradata_client_packages script with the list parameter, for Platforms 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: 68 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 8: Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR Subject Description ************************************************************************ * Tar Teradata Client Packages v.xx.xx.xx.xx ************************************************************************ TTU Foundation * The available platforms are: HP-UX Linux The available packages are: --- HP-UX Products bteq fastexp mload npaxsmod cliv2 fastld mqaxsmod piom tdicu TeraGSS tpump --- Linux Products bteq fastexp mload cliv2 fastld mqaxsmod tdicu TeraGSS tpump npaxsmod piom 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: http://www.gnu.org/software/tar/ 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 Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 69 Chapter 8: 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 www.gzip.org 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. 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: 70 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 8: Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR ************************************************************************ * Tar Teradata Client Packages v.xx.xx.xx.xx * ************************************************************************ 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 TeraGSS --- Solaris Sparc Products cliv2xxxx sqlppxxxx tdicuxxxx TeraGSS TeraGSS32 --- Solaris Opteron Products cliv2xxxx sqlppxxxx tdicuxxxx TeraGSS_solaris-i386 TeraGSS_solaris-x8664 2. 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.xx.xx.xx.xx * ************************************************************************ 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: Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 71 Chapter 8: Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR ---Archiving all packages for sparc. tar cvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar" \Sparc Solaris/Sparc/ Solaris/Sparc/TeraGSS/ Solaris/Sparc/TeraGSS/install/ Solaris/Sparc/TeraGSS/install/depend . . (more files) . Solaris/Sparc/tdicuxxxx/reloc/$LIBDIR64/libiculxtd.so.52.1 Solaris/Sparc/tdicuxxxx/reloc/$LIBDIR64/libicuuctd.so.52.1 tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar" .setup.sh tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar" setup.bat tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar" MEDIALABEL tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar" tar_teradata_client_packages.* tar_teradata_client_packages.bat tar_teradata_client_packages.sh Solaris .setup.sh setup.bat MEDIALABEL Notice: The executable gzip.exe is not found. Download from www.gzip.org for MSDOS to automatically compress the output tar file to a gzip file. The file has been saved at : C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar 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. • 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: 72 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 Chapter 8: Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR ************************************************************************ * Tar Teradata Client Packages v.xx.xx.xx.xx ************************************************************************ 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-xx.xx.xx.xx-1.i386.rpm 118 blocks a Linux/mload/mloadxxxx-xx.xx.xx.xx-1.i386.rpm 374 blocks a Linux/piom/piomxxxx-xx.xx.xx.xx-1.i386.rpm 79 blocks a Linux/tdicu/tdicu-xx.xx.xx.xx-1.noarch.rpm 20564 blocks a Linux/fastld/fastldxxxx-xx.xx.xx.xx-1.i386.rpm 189 blocks a Linux/TeraGSS/TeraGSS_redhatlinux-i386-xx.xx.xx.xx-1.i386.rpm 12240 blocks a Linux/fastexp/fastexpxxxx-xx.xx.xx.xx-1.i386.rpm 341 blocks a Linux/tpump/tpumpxxxx-xx.xx.xx.xx-1.i386.rpm 478 blocks a Linux/npaxsmod/npaxsmod-xx.xx.xx.xx-1.i386.rpm 272 blocks a Linux/cliv2/cliv2-xx.xx.xx.xx-1.x86_64.rpm 766 blocks a Linux/bteq/bteq-xx.xx.xx.xx-1.i386.rpm 303 blocks tar rvf "C:\Documents and Settings\user\teradata-client-linux-ttu-foundation.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 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00 73 Chapter 8: Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR 74 Teradata Tools and Utilities for Linux Installation Guide CentOS, RedHat, SUSE, s390x Release 16.00
