Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide Release 15.00 B035-3121-034K March 2014 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Active Data Warehousing, Active Enterprise Intelligence, Applications-Within, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast, Gridscale, MyCommerce, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata ServiceConnect, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and other countries. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. Apache, Apache Hadoop, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. Apple, Mac, and OS X all are registered trademarks of Apple Inc. Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda Access, Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and Maximum Support are servicemarks of Axeda Corporation. Data Domain, EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of Oracle. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other countries. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI is a registered trademark of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. NetVault is a trademark or registered trademark of Dell Inc. in the United States and/or other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries. Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a registered trademark of Unicode, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. The information contained in this document is provided on an "as-is" basis, without warranty of any kind, either express or implied, including the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. In no event will Teradata Corporation be liable for any indirect, direct, special, incidental, or consequential damages, including lost profits or lost savings, even if expressly advised of the possibility of such damages. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please 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 - 2014 by Teradata. All Rights Reserved. Table of Contents Preface.............................................................................................................................................................7 Purpose.................................................................................................................................................................. 7 Audience................................................................................................................................................................ 7 Supported Releases............................................................................................................................................... 7 Prerequisites.......................................................................................................................................................... 7 Revision History................................................................................................................................................... 8 Technical Assistance.............................................................................................................................................8 Product Safety Information.................................................................................................................................8 Chapter 1: Preparing for Installation............................................................................................................ 9 About Installing Teradata Tools and Utilities from DVD............................................................................... 9 Installation Kit Contents.............................................................................................................................. 9 DVD Contents............................................................................................................................................... 9 About the Yum Repository File................................................................................................................. 11 Product Descriptions.................................................................................................................................. 11 Product Dependencies................................................................................................................................14 Dependent Products............................................................................................................................ 16 If a Dependent Product Is Already Installed.................................................................................... 16 System Requirements..................................................................................................................................16 Chapter 2: Uninstalling Software.....................................................................................................................19 About Retaining Existing Files for Teradata GSS Client............................................................................... 19 Uninstallation Script Overview........................................................................................................................ 19 Uninstallation Script Operation................................................................................................................ 20 Uninstallation Script Usage and Parameters........................................................................................... 21 Usage...................................................................................................................................................... 21 Parameters.............................................................................................................................................21 List of Packages that are Uninstalled........................................................................................................ 22 Typical Output............................................................................................................................................. 22 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 3 Table of Contents Library File Checking Output.....................................................................................................................23 Manually Uninstalling Packages.................................................................................................................24 Chapter 3: Installing New Software...............................................................................................................25 About Installing Third-Party Software............................................................................................................. 25 Installing Third-Party Software for Teradata WebSphere MQ Access Module....................................25 About Installing Teradata Tools and Utilities.................................................................................................. 25 Installation Order......................................................................................................................................... 26 About Retaining and Deleting Data in Teradata Wallet..........................................................................26 Ensuring You Are Prompted About Teradata Wallet Data..................................................................... 26 Installing Teradata Tools and Utilities....................................................................................................... 27 Installing Missing Library Files.................................................................................................................. 29 About Teradata Developer Exchange.........................................................................................................29 Products Available from Teradata Developer Exchange..................................................................30 Connectivity....................................................................................................................................30 Tools................................................................................................................................................. 30 Downloading a Product from the Teradata Developer Exchange.................................................. 30 Installing Products Downloaded from Teradata Developer Exchange..........................................31 About Teradata Software Server (Patch Server)....................................................................................... 31 Downloading Updated Software Packages........................................................................................ 32 Installing Updated (Patched) Software Packages.............................................................................. 32 Adding CLI User Exit Functions................................................................................................................ 33 Chapter 4: Configuring New Software......................................................................................................... 35 Creating Environment Variables....................................................................................................................... 35 About Configuring ODBC Driver for Teradata...............................................................................................35 Configuring Teradata Parallel Transporter...................................................................................................... 36 About Configuring Teradata Parallel Transporter................................................................................... 36 Editing twbcfg.ini......................................................................................................................................... 36 Selecting Checkpoint and Log Directories in the Configuration File................................................... 36 Setting Parameters for Shared Memory.....................................................................................................37 Setting Semaphore Parameters................................................................................................................... 37 Switching IPC Memory to Shared Memory..............................................................................................38 Switching IPC Memory to Mapped Memory........................................................................................... 38 Switching From 64-bit to 32-bit Environment......................................................................................... 38 4 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Table of Contents Chapter 5: Verifying the Complete Installation............................................................................................41 About Verifying the Installation.................................................................................................................................. 41 Verifying the Installation Using Basic Teradata Query..................................................................................... 41 Verifying the Installation Using CLI Sample Program...................................................................................... 42 Setting the JDBC Driver Classpath..............................................................................................................................43 Accessing Lists of Installed Files.................................................................................................................................. 43 Chapter 6: Troubleshooting the Installation................................................................................................... 45 Client Computer Problem: Cannot Communicate Over the Network with Teradata Database........................ 45 Client Computer Problem: Incorrect Path Name in COPLIB................................................................................. 45 Client Computer Problem: Incorrect Path Name in COPERR................................................................................46 Client Computer Problem: errmsg.cat File Not Found............................................................................................ 46 Client Computer Problem: Incorrect Path Name in COPANOMLOG..................................................................46 Client Computer Problem: Missing hosts File .......................................................................................................... 47 Client Computer Problem: Incorrect Entries in the hosts File................................................................................ 47 Client Computer Problem: Missing Entries in the services File..............................................................................47 Client Computer Problem: Improper Linking...........................................................................................................47 Client Computer Problem: Incorrect clispb.dat Parameters....................................................................................47 Client Computer Problem: Cannot Log On from CLI Application........................................................................48 Client Computer Problem: Cannot Log On to Teradata Database ........................................................................ 48 Network Problems......................................................................................................................................................... 48 Teradata Database Problem..........................................................................................................................................49 Teradata Parallel Transporter Problem: Unable to Find tbuild............................................................................... 50 Teradata Parallel Transporter Problem: Cannot Run New Version of TPT...........................................................50 Teradata Parallel Transporter Problem: Failed to Load libpxcommon Library.................................................... 51 Teradata Parallel Transporter Problem: Unable to Find Messages..........................................................................51 Technical Assistance...................................................................................................................................................... 51 Chapter 7: Deploying Teradata Tools and Utilities with TAR..........................................................53 About Deploying Applications with TAR...................................................................................................................53 About the TAR File.................................................................................................................................................53 TAR Script Compatibility with Platform Operating Systems....................................................................53 Verifying TAR Script Dependencies are Installed.......................................................................................54 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 5 Table of Contents The TAR Script Command...................................................................................................................54 TAR Script Usage Considerations....................................................................................................... 55 Downloading Windows Utility Software for TAR Deployment.............................................................57 TAR Script Examples................................................................................................................................... 58 Archiving Oracle Solaris SPARC Packages........................................................................................ 58 Archiving Linux Packages.................................................................................................................... 60 6 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Preface Purpose This book describes how to install and deploy Teradata Tools and Utilities Release 15.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 Supported Releases This document supports the following versions of Teradata products: • Teradata Database Release 15.0 • Teradata Tools and Utilities Release 15.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. Prerequisites You should be familiar with: • Computer technology and terminology • Relational database management systems • Utilities that load and retrieve data Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 7 Preface Revision History Revision History Date Description March 2014 Documented usage of sudo. 15.00 Technical Assistance For more information, see Teradata Tools and Utilities Release Definition, B035-2029. If you need additional information or assistance, contact your Teradata Customer Service Representative. If you purchased an Enterprise System Support (ESS) contract, a customized support plan was created for you. For contact information, refer to your support plan. To learn more about Teradata Customer Services, go to Teradata @ Your Service at tays.teradata.com 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 Red Hat Enterprise Linux Installation Guide, Release 15.00 CHAPTER 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Before you perform the procedures in this document, you must: • • • • • 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 CD (Teradata Database 15.0, Teradata Tools and Utilities 15.00) • Teradata Tools and Utilities Database Management WINDOWS Release 15.00.00 DVD • Teradata Tools and Utilities Tape Storage Management Enablers Linux & WINDOWS Release 15.00.00 DVD • Teradata Tools and Utilities IBM z/OS 15.00.00 CD If you did not receive all the installation media that you ordered, contact your Teradata Sales Representative. DVD Contents The table below contains a list of the Teradata Tools and Utilities products that are on the media in the installation kit. Note: In the table, the media titles are abbreviated: Abbreviation Media Title Base Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 15.00.00 DVD Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 9 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Abbreviation Media Title Database Management Teradata Tools and Utilities Database Management WINDOWS Release 15.00.00 DVD Tape Storage Management Teradata Tools and Utilities Tape Storage Management Enablers Linux & WINDOWS Release 15.00.00 DVD Table 1: Products and the Media They Reside On Product Media Title (Abbreviated) Base Database 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 JMS X Teradata Archive/Recovery Utility Tape Storage Management X X Teradata C Preprocessor2 X Teradata Call-Level Interface version 2 X Teradata COBOL Preprocessor2 X Teradata Data Connector API X Teradata FastExport X Teradata FastLoad X Teradata Geospatial Utilities X Teradata GSS Client X Teradata MultiLoad X Teradata Named Pipes Access Module X Teradata Parallel Data Pump X Teradata Parallel Transporter Base X Teradata Parallel Transporter Stream X Teradata Wallet X Teradata WebSphere MQ Access Module X X X X X X X X X X Related Topics Products Available from Teradata Developer Exchange, on page 30 10 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD About the Yum Repository File The following media contains a script file named mkrepo.sh that you can use to create a Yum repository file: • Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 15.00.00 DVD • Teradata Tools and Utilities Tape Storage Management Enablers Linux & WINDOWS Release 15.00.00 DVD The script is in the following directory: • /Linux/i386-x8664/repodata When you run the script it creates a repository file (.xml format) named teradata-ttufoundation-1500.repo and puts it into the /tmp folder. The file contains a list of product dependencies and libraries. The script can also copy the repository file to the system-specific repository location: • /etc/yum.repos.d After you create the repository file, you can use it with one of the following package management utilities or a similar product: • PackageKit • 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 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 Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 11 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Description 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 thirdparty 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 COBOL Preprocessor2 Teradata COBOL Preprocessor2 is a command line tool that provides the programmer of a COBOL-based application with 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 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 client-based 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 Geospatial Utilities Teradata Geospatial Utilities loads Shape file data into tables in a Teradata Database. It uses multiple sessions to load data, but it loads data into one table per layer on a Teradata Database. 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, high-volume maintenance on multiple tables and views of a Teradata Database. This utility is accessible from the command line or a script. 12 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Description Teradata Named Pipes Access Module Teradata Named Pipes Access Module is a component that provides an interprocess communication link between a writer process (such as Teradata FastExport) and a reader process (such as Teradata FastLoad). This utility works with the Teradata Parallel Transporter products and with Teradata FastExport, Teradata FastLoad, Teradata MultiLoad, and Teradata Parallel Data Pump. It is accessible from the command line. Teradata 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 script-driven 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 highspeed, 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. Teradata WebSphere MQ Access Module Teradata WebSphere MQ Access Module is a component that allows Teradata utilities to import data using IBM WebSphere MQ Access Module message queuing middleware. This utility works with the Teradata Parallel Transporter products and with Teradata FastLoad, Teradata MultiLoad, and Teradata Parallel Data Pump. It is accessible from a command line. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 13 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Dependencies Product Teradata Tools and Utilities Dependencies Third-party Dependencies Basic Teradata Query Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client Teradata Named Pipes Access Module None None Open Database Connectivity (ODBC) Driver for Teradata Shared ICU Libraries for Teradata None Shared ICU Libraries for Teradata None None Teradata Archive/ Recovery Utility Shared ICU Libraries for Teradata None Teradata GSS Client Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client Teradata C Preprocessor2 Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata GSS Client Teradata Call-Level Interface version 2 Shared ICU Libraries for Teradata Teradata COBOL Preprocessor2 Shared ICU Libraries for Teradata None Teradata GSS Client None Teradata Call-Level Interface version 2 Teradata GSS Client Teradata Data Connector API None None Teradata FastExport Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client Teradata FastLoad Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client 14 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata GSS Client None None Teradata JDBC Driver None JDK 1.4 , JDK 5.0, or JDK 6.0 Note: The environment can be downloaded from Java Downloads. Teradata Access Module for JMS None None Teradata MultiLoad Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client Teradata Parallel Data Pump Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client Teradata Parallel Transporter Base Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata GSS Client Teradata Parallel Transporter Stream Shared ICU Libraries for Teradata Progress DataDirect ConnectXE ODBC driver for Teradata (required only if you will use the ODBC operator) None Teradata Call-Level Interface version 2 Teradata GSS Client Teradata Parallel Transporter Base Teradata Studio Express Teradata Wallet Java Runtime Environment (JRE) 1.6 or later Note: JRE can be downloaded from Java Downloads. None None Note: If Teradata Call-Level Interface version 2 (CLIv2) is installed before Teradata Wallet and if Teradata Wallet is installed using a different directory prefix than the default /opt, CLIv2 will not be able to use Teradata Wallet. • To avoid this situation, do either of the following: • Install Teradata Wallet before you install CLIv2 • Install Teradata Wallet using the default directory prefix • To rectify this situation, reinstall CLIv2. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 15 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD Product Teradata Tools and Utilities Dependencies Third-party Dependencies For Teradata Wallet help, at the command prompt enter tdwallet help. For more information about Teradata Wallet, see Security Administration, B035-1100. Teradata WebSphere MQ Access Module Teradata Data Connector API IBM WebSphere MQ 7.5 Note: To display the version of WebSphere that is installed on the system, run the dspmqver command from the command line. 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 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 Ynet or BYNET. No separate network controller board or network software is required; the client provides its own. 16 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD The appropriate Ethernet hardware and software supporting a TCP/IP-based network must be installed on every Teradata Database with which the client communicates. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 17 Chapter 1 Preparing for Installation About Installing Teradata Tools and Utilities from DVD 18 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 CHAPTER 2 Uninstalling Software About Retaining Existing Files for Teradata GSS Client Before you uninstall any older versions of the Teradata GSS Client package in preparation for installing a new version, determine whether to retain any of the files for the old version. You might need to retain existing files if you need to do either of the following: • Return to an older version of the client package later for client compatibility with an older version of the Teradata Database system: If you require such compatibility, you need to retain the entire set of client package files for the older version(s), rather than uninstall them. Then you can use the version switching tool (tdgssversion) to switch from the new version to an older version to allow access to a compatible older Teradata Database system. For information on using the tdgssversion tool, refer to Security Administration, B035-1100. • Retain custom configuration information in the TdgssUserConfigFile.xml file and transfer it to the new version of the client package: If you do not need the version compatibility mentioned above, simply copy the configuration file for the old version and make the corresponding changes to the configuration file for the new version. For information on accessing and making changes to the TdgssUserConfigFile.xml file, refer to Security Administration, B035-1100. Uninstallation Script Overview Before you install a new version of Teradata Tools and Utilities packages, you must use the uninstallation script, uninstall_ttu.sh, to uninstall previous versions of the packages. 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 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 19 Chapter 2 Uninstalling Software Uninstallation Script Overview Note: It is not necessary to uninstall previous versions of Teradata GSS Client package before you install another version. When you uninstall previous versions, configuration settings that you might want to reuse are deleted. 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 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: 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. 20 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 2 Uninstalling Software Uninstallation Script Overview Uninstallation Script Usage and Parameters Usage 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 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 15.00, and packages prior to this version (14.10, 14.00, 13.10, 13.0, or 12.00) need to be removed, enter priorto 15.00.00.00. The number parameter must contain all four version numbers, and can be specific enough to remove all packages before, for example, 15.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-debugprocessid.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. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 21 Chapter 2 Uninstalling Software Uninstallation Script Overview 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 JMS (jmsaxsmod) Teradata Archive/Recovery Utility (teradata_arc) Teradata Call-Level Interface version 2 (cliv2, cliv2_64, cliv2so, and so on) Teradata COBOL Preprocessor2 (cobpp) Teradata Data Connector API (piom) Teradata FastExport (fastexp) Teradata FastLoad (fastld) Teradata GSS Client (teragss) Teradata MultiLoad (mload) Teradata Named Pipes Access Module (npaxsmod) Teradata Parallel Data Pump (tpump) Teradata Query Director (qrydir and sockclient) All Teradata Parallel Transporter packages up to Teradata Tools and Utilities13.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 (TTU14.00) (tptbase) Teradata Parallel Transporter Stream (TTU14.00) (tptstream) Teradata Wallet (tdwallet) Teradata WebSphere MQ Access Module (mqaxsmod) This list is subject to change as future products are added to Teradata Tools and Utilities. On rare occasions files are left on systems after improper installations or uninstallations or if very old Teradata Tools and Utilities packages were installed by copying files to the /usr/bin or /usr/lib directories. The uninstallation script checks and displays a warning message that the files still exist and may cause problems. The script offers to rename the files and displays the command to remove them. The script does not delete the files automatically. If the files for the following products exist in the /usr/lib directory, the script renames them and adds the extension teradata-package-remove.old: • • • • • Open Database Connectivity (ODBC) Driver for Teradata Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector API Teradata GSS Client Typical Output Package Removal Type: rpm .............................................................. The following packages are installed: 22 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 2 Uninstalling Software Uninstallation Script Overview 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. f. a. h. q. bteq1410 fastexp1410 fastld1410 mload1400 mload1410 mqaxsmod1400 npaxsmod1400 npaxsmod1410 tdodbc1410 tdwallet1410 tptstream1410 tpump1400 tpump1410 tptbase1410 piom1410 cliv21400 cliv21400 tdicu1400 tdicu1410 TeraGSS TeraGSS32 - 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 15.00.00.00 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 cliv21400 - 15.00.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: … 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): Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 23 Chapter 2 Uninstalling Software Uninstallation Script Overview If you answer yes when asked if you would like to move these files, output similar to this appears: … Moving /usr/lib/libcliv2.so to /usr/lib/libcliv2.so-teradata-package-remove.old Moving /usr/lib/libtdusr.so to /usr/lib/libtdusr.so-teradata-package-remove.old Moving /usr/lib/libpm.so to /usr/lib/libpm.so-teradata-package-remove.old Moving /usr/lib/libicudatatd.so to /usr/lib/libicudatatd.so-teradata-package-remove.old Moving /usr/lib/libicui18ntd.so to /usr/lib/libicui18ntd.so-teradata-package-remove.old Moving /usr/lib/libicuiotd.so to /usr/lib/libicuiotd.so-teradata-package-remove.old Moving /usr/lib/libiculetd.so to /usr/lib/libiculetd.so-teradata-package-remove.old Moving /usr/lib/libiculxtd.so to /usr/lib/libiculxtd.so-teradata-package-remove.old Moving /usr/lib/libicuuctd.so to /usr/lib/libicuuctd.so-teradata-package-remove.old To permanently remove these files execute the command : $ rm /usr/lib/*-teradata-package-remove.old If you answer no when asked if you would like to move these files, output similar to this appears: … The following listed files have not been moved: /usr/lib/libcliv2.so /usr/lib/libtdusr.so /usr/lib/libpm.so /usr/lib/libicudatatd.so /usr/lib/libicui18ntd.so /usr/lib/libicuiotd.so /usr/lib/libiculetd.so /usr/lib/libiculxtd.so /usr/lib/libicuuctd.so These could cause problems later. It is recommended that these files be manually moved or removed before installing new Teradata Client Packages. Manually Uninstalling Packages Note: It is not necessary to uninstall previous versions of Teradata GSS Client package before you install another version. When you uninstall previous versions, configuration settings that you might want to reuse are deleted. If a package was not properly uninstalled by the uninstallation script, run the script again. To manually uninstall a package, 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 24 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.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 WebSphere MQ Access Module Note: To display the version of WebSphere that is installed on the system, run the dspmqver command from the command line. 1 Before you run Teradata WebSphere MQ Access Module, download IBM WebSphere MQ 7.5 and install it according to the instructions in the downloaded package. About Installing Teradata Tools and Utilities Before you install Teradata Tools and Utilities software, always compare the versions available from the following resources: • Teradata Software Server • Teradata Developer Exchange • installation media (DVD) In general, software on the Teradata Software Server will contain the most recent point release of a software product, followed by Teradata Developer Exchange, and finally the installation media. 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 from media (DVD) The initial distribution of software is on media (DVD) in the Teradata Tools and Utilities Installation Kit. Using the installation script, install products on a single computer from the media. The media contains installation packages for the current release. Installing from Teradata Developer Exchange The download center may contain more current software packages which should be installed instead of lower version software contained on the DVD media. Packages on the download center include drivers and connectivity software. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 25 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 DVD media include files that allow you to deploy Teradata Tools and Utilities products across your network using tar.gz files and tar. Installation Order The main installation procedure installs all products and their dependencies in the correct order. Using an alternative method to do the installation requires that the products be installed manually in the correct order. 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 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 Topics Ensuring You Are Prompted About Teradata Wallet Data, on page 26 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: # TDWALLET_INTERACTIVE_INSTALL=1 2 Export the environment variable: # export TDWALLET_INTERACTIVE_INSTALL 26 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities Related Topics About Retaining and Deleting Data in Teradata Wallet, on page 26 Installing Teradata Tools and Utilities 1 Log on as root (or change to root and enter the root password). 2 If a mount point directory does not exist, create one: mkdir /mnt where mnt is the name of the media mount point. 3 If the installation source files are not on the system disk, insert the appropriate media into the media drive. Note: For a list of products and the media each one resides on, see DVD Contents. 4 Mount the media device: mount /dev/media device name/mnt For example, if the media device name is c0t1d0, type: mount /dev/c0t1d0/mnt 5 Change directory to the media mount point: cd /mnt 6 Begin the installation process: ./setup.bat Note: ./setup.bat accepts command line options: ./setup.bat a installs all packages and any required dependencies ./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 to) ./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 to) 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 appears that: • 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 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 27 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities • Quitting the installation 7 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: 1. 2. 3. 4. 5. Teradata GSS Client (teragss) Shared ICU Libraries for Teradata (tdicu) Teradata Call-Level Interface version 2 (cliv2) Teradata Data Connector API (piom) Other Products Note: If Teradata Call-Level Interface version 2 (CLIv2) is installed before Teradata Wallet and if Teradata Wallet is installed using a different directory prefix than the default /opt, CLIv2 will not be able to use Teradata Wallet. • To avoid this situation, do either of the following: • Install Teradata Wallet before you install CLIv2 • Install Teradata Wallet using the default directory prefix • To rectify this situation, reinstall CLIv2. For Teradata Wallet help, at the command prompt enter tdwallet help. For more information about Teradata Wallet, see Security Administration, B035-1100. 8 After reviewing product dependencies, do one of the following: Command Action Install All Packages Type the letter a. The number of products selected appears in the bottom right corner of the screen. The packages selected for installation have an asterisk (*) beside them. Uninstall All Type the letter u. This removes previous versions of Teradata Tools and Utilities products. 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. Install Selected Packages Type the numbers of the desired products and dependencies, separated by spaces, and press the Enter key. • 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 Type the letter q to quit the installation. 9 If you are prompted about retaining Teradata Wallet data, choose whether you want the uninstallation process to retain data or delete it: 28 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities Option Description Y (Yes) Data will be retained during uninstallation. N (No) Data will be deleted during uninstallation (if this is the last remaining version of Teradata Wallet to be uninstalled). 10 Change back to the root directory. 11 Unmount the media drive. umount /mnt 12 Remove the installation media from the media drive. Related Topics DVD Contents, on page 9 Installing Missing Library Files, on page 29 Product Dependencies, on page 14 About Retaining and Deleting Data in Teradata Wallet, on page 26 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 Developer Exchange Some Teradata Tools and Utilities products can be downloaded from the Teradata Developer Exchange Downloads page. Note: Products downloaded from the Teradata Developer Exchange Downloads page are intended to be used only for connecting to Teradata Database via non-Teradata products. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 29 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities They are not intended to be used for updating the Teradata Tools and Utilities suite of products available on DVD. Products Available from Teradata Developer Exchange Note: Products and versions of them available from Teradata Developer Exchange Downloads are subject to change. This list is limited to Teradata Tools and Utilities applications. Connectivity • Teradata Call-Level Interface version 2 suite (includes Teradata GSS Client and Teradata International Components for Unicode) • Teradata JDBC Driver • Teradata JMS Universal Connector • .NET Data Provider for Teradata • Open Database Connectivity (ODBC) Driver for Teradata suite (includes Teradata GSS Client and Teradata International Components for Unicode) • OLE DB Provider for Teradata Note: Download and install the Teradata Call-Level Interface version 2 suite to obtain the dependent packages for OLE DB Provider for Teradata. Tools • Teradata Plug-in for Eclipse • Teradata Studio Express • Teradata Wallet Downloading a Product from the Teradata Developer Exchange 1 Go to Teradata Developer Exchange Downloads. The Teradata Developer Exchange Downloads page with a list of selectable products appears. 2 Click the product name or the platform next to the product name. The list of available downloads by software version and processor or platform appears. 3 Click the software package or text file to download. 4 You may be asked to enter a user name and password or to create a user name and password. 5 Read the License Agreement, then click I Agree. A page with a link to the Download file appears. 6 If a readme file is included, click on the readme file link and read and print any special download or installation instructions before continuing. 7 Return to the DOWNLOADS page. 8 Click the package to download. This is typically a .tar, .tar.gz, or .zip file. 9 Click Save. 30 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities 10 Select a location where to save the file and click Save. The file is saved to the location chosen. Installing Products Downloaded from Teradata Developer Exchange Note: [64-bit systems] When you install Teradata Tools and Utilities from media, the 32-bit version and the 64-bit version of the product is installed. However, when you install Teradata Tools and Utilities from packages that you downloaded from Teradata Software Server (the Patch Server) or from Teradata Developer Exchange, only the version of the product that you downloaded (32-bit or 64-bit) is installed. 1 Log on as root (or change to root and enter the root password). 2 Go to the location where you saved the compressed file. 3 Read the readme file to see if it contains additional installation instructions or a list of dependencies. 4 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: 1. 2. 3. 4. 5. Teradata GSS Client (teragss) Shared ICU Libraries for Teradata (tdicu) Teradata Call-Level Interface version 2 (cliv2) Teradata Data Connector API (piom) 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 from media, the 32-bit version and the 64-bit version of the product is installed. However, when you install Teradata Tools and Utilities from packages that you downloaded from Teradata Software Server (the Patch Server) or from Teradata Developer Exchange, only the version of the product that you downloaded (32-bit or 64-bit) is installed. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 31 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities Downloading Updated Software Packages To ensure the highest quality and best performance of Teradata Tools and Utilities products, you should download the most recently updated software packages from the Teradata Software Server. 1 Log on to Teradata @ Your Service at tays.teradata.com. 2 Click Software Downloads. 3 In the Home tab, click the Teradata Client button. 4 Click the platform. 5 In the Teradata Client Released Software pane, select the Software base. 6 Filter the list of available software. • Select Current to display the most recent release. • Select All to display all versions of the software. 7 Click Submit. 8 Select the suite you want to download. 9 Select the Download Type and the Download Readme Files if desired, enter your User Name and E-Mail, 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 Log on as root (or change to root and enter the root password). 2 Go to the location where you saved the compressed file. 3 Read the readme file to see if it contains additional installation instructions or a list of dependencies. 4 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: 1. 2. 3. 4. 32 Teradata GSS Client (teragss) Shared ICU Libraries for Teradata (tdicu) Teradata Call-Level Interface version 2 (cliv2) Teradata Data Connector API (piom) Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities 5. 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 userdefined processing to take place. 1 Change directories to the sample directory: cd /opt/teradata/client/15.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 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. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 33 Chapter 3 Installing New Software About Installing Teradata Tools and Utilities 34 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 CHAPTER 4 Configuring New Software Creating Environment Variables 1 Include the installation directory path where Teradata Call-Level Interface version 2 software files are located in the LD_LIBRARY_PATH environment variable. 2 Bash and Bourne shell users, use the following command to add the installation directory path to the LD_LIBRARY_PATH environment variable: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:installation directory export LD_LIBRARY_PATH 3 C shell users, use the following command to add the installation directory path to the LD_LIBRARY_PATH environment variable: setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH":installation directory" 4 Export the LD_LIBRARY_PATH environment variable for all Teradata Tools and Utilities products. 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. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 35 Chapter 4 Configuring New Software Configuring Teradata Parallel Transporter 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 Topics Setting Parameters for Shared Memory, on page 37 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. 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. 1 Edit the configuration file and specify the Teradata Parallel Transporter default directory and default log directory. 'CheckpointDirectory'/opt/teradata/client/short version/tbuild/ checkpoint' 36 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 4 Configuring New Software Configuring Teradata Parallel Transporter CheckpointDirectory refers to the directory that contains the checkpoint files for Teradata Parallel Transporter jobs and short version is the product version in short form (for example, 15.00). 'LogDirectory/opt/teradata/client/short version/tbuild/logs' LogDirectory refers to the directory that contains the binary logs for Teradata Parallel Transporter jobs and short version is the product version in short form (for example, 15.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: /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. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 37 Chapter 4 Configuring New Software Configuring Teradata Parallel Transporter 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 installation 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 installation directory 3 Create the mmap directory and set the permissions to 777: mkdir mmap 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. Switching From 64-bit to 32-bit Environment The default of TPT Base is set to 64-bit environment on the 64-bit systems. You can switch to the 32-bit environment. 38 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 4 Configuring New Software Configuring Teradata Parallel Transporter 1 Log on as the root user. 2 Switch from a command line mode: If you're using a Bash or Bourne shell, add the following from the command line: export PATH=/opt/teradata/client/15.00/tbuild/bin:${PATH} If you're using a C shell, add the following from the command line: setenv PATH /opt/teradata/client/15.00/tbuild/bin:${PATH} 3 Switch for a single user mode: If you're using a Bash or Bourne shell, add the following to the $HOME/.profile file: PATH=/opt/teradata/client/15.00/tbuild/bin:$PATH;export PATH If you're using a C shell, add the following to the $HOME/.login file: setenv PATH /opt/teradata/client/15.00/tbuild/bin:${PATH} 4 Run $HOME/.profile or $HOME/.login. 5 Switch for all users mode: If you're using a Bash or Bourne shell, replace PATH=/opt/teradata/client/ 15.00/tbuild/bin64 with PATH=/opt/teradata/client/15.00/tbuild/bin. If you're using a C shell, replace PATH /opt/teradata/client/15.00/tbuild/ bin64 with PATH /opt/teradata/client/15.00/tbuild/bin. 6 Log off. 7 Log on. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 39 Chapter 4 Configuring New Software Configuring Teradata Parallel Transporter 40 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.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: • Verify the installation using BTEQ • Verify the installation using the CLI Sample Program Verifying the Installation Using Basic Teradata Query Using Basic Teradata Query (BTEQ) is the simplest way to verify that Teradata Tools and Utilities has been installed properly because BTEQ files are part of the 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 15.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 If the logon is successful, output similar to the following appears: *** Logon successfully completed. *** Teradata Database Release is 15.00.00.00 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 41 Chapter 5 Verifying the Complete Installation About Verifying the Installation *** Teradata Database Version is 15.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: 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 Log off of the Teradata Database and exit BTEQ. Related Topics Client Computer Problem: Cannot Log On to Teradata Database, on page 48 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: • makesamp.lx [32-bit] • makesamp.lx64 [64-bit] 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: • chmod +x clisamp [32-bit] • chmod +x clisamp_lx64 [64-bit] 4 Run the sample program using one of the following commands: • Run the sample program using the default logon information (dbc/ systemfe,service): 42 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 5 Verifying the Complete Installation Setting the JDBC Driver Classpath • clisamp [32-bit] • clisamp_lx64 [64-bit] • Show help for the sample program: • clisamp -h [32-bit] • clisamp_lx64 -h [64-bit] • Run the sample program using a user-provided input string: • clisamp tdpid/user,password [32-bit] • clisamp_lx64 tdpid/user,password [64-bit] 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 15.00.00.00 MTDP version is 15.00.00.00 MOSIOS version is 15.00.00.00 MOSIDEP version is 15.00.00.00 OSERR version is 15.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. Related Topics Client Computer Problem: Cannot Log On to Teradata Database, on page 48 Setting the JDBC Driver Classpath The Teradata JDBC Driver is distributed as platform-independent jar files. 1 Copy the jar files into a directory. 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. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 43 Chapter 5 Verifying the Complete Installation Accessing Lists of Installed Files 1 Log into http://tays.teradata.com. 2 Click the Knowledge Search tab. 3 Enter the Knowledge Article Number in the search window. 44 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 Red Hat Enterprise Linux Installation Guide, Release 15.00 CHAPTER 6 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 COPLIB Check that the COPLIB environment variable has the correct path name to the CLI system parameter block file, clispb.dat. The COPLIB environment variable is set to /usr/lib in the /etc/profile file during the installation of the software. 1 Use one of the following commands to define the correct path name to the clispb.dat file in the COPLIB environment variable: • Bourne shell users, add the following to the .profile file: COPLIB=/sd;export COPLIB where sd (source directory) is the name of the directory you created to receive the object library, the system parameter block file, and the executable files. • C shell users, add the following to the .login file: setenv COPLIB /sd Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 45 Chapter 6 Troubleshooting the Installation Client Computer Problem: Incorrect Path Name in COPERR where sd (source directory) is the name of the directory you created to receive the object library, the system parameter block file, and the executable files. 2 Run the .profile or .login file. Client Computer Problem: Incorrect Path Name in COPERR If the No such error found message appears, check that the COPERR environment variable has the correct path name to the error message catalog file, errmsg.cat. 1 Use one of the following commands to define the correct path name to the errmsg.cat file in the COPERR environment variable: • Bourne shell users, add the following to the .profile file: COPERR=/ed; export COPERR where ed (error directory) is the name of the directory created to contain the error message catalog file. • C shell users, add the following to the .login file: setenv COPERR /ed where ed (error directory) is the name of the directory created to contain the error message catalog file. 2 Run the .profile or .login file. Client Computer Problem: errmsg.cat File Not Found If the CLI: Message catalog open failed! error message appears, the errmsg.cat file cannot be opened. This error is displayed when the errmsg.cat file is not found in the /usr/lib directory or in the directory specified in the COPERR environment variable. 1 Set the COPERR environment variable to the directory where the errmsg.cat file is located. Client Computer Problem: Incorrect Path Name in COPANOMLOG 1 To produce an anomaly log file, verify that the COPANOMLOG environment variable has the correct path name to the anomaly log file. 46 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 6 Troubleshooting the Installation Client Computer Problem: Missing hosts File Client Computer Problem: Missing hosts File 1 Verify that the /etc/hosts file exists on the client. Client Computer Problem: Incorrect Entries in the hosts File 1 Check the following entries in the /etc/hosts file or in the hosts file on the NIS master: • Check all entries for incorrect, missing, or duplicate network addresses of COPs, APs, or nodes. Remember that a TCP/IP (Internet) address is a 4-byte value in the form a.b.c.d. COPs, APs, or nodes on the same logical network must have the same network ID portion of the network address. • Check that COPs, APs, or nodes in the same group for a Teradata 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 1 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 1 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. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 47 Chapter 6 Troubleshooting the Installation Client Computer Problem: Cannot Log On from CLI Application 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 1 If you cannot log on to a Teradata Database, try logging on to a different database. 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 Verify that the transceiver is connected to the network, client, and Teradata Database. 2 Check for broken or disconnected network cables. 3 Verify that drop cables are not too long. The cables must comply with IEEE 802.3 standards. 4 Verify that all repeaters, bridges, routers, and gateways functioning properly. 5 Verify that all jumpers are setup correctly on the client's network controller board. 6 Verify that the network software is installed and running properly on the client. 7 Verify that the network software is compatible with the network controller board installed on the client. 8 Confirm that the network is operational using a network utility program. 9 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. 48 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 6 Troubleshooting the Installation Teradata Database Problem 10 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. 11 If a network controller board is replaced on the client, reboot Teradata Database so it can obtain the network address of the new board. 12 If the network configuration was changed, check that all network related files were changed accordingly. 13 Reboot the client to reset network hardware and reload network software. 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. 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. Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 49 Chapter 6 Troubleshooting the Installation Teradata Parallel Transporter Problem: Unable to Find tbuild 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 TPT_install_directory/bin path is in the PATH environment variable. 4 If the TPT_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. 3 If you are still unable to run the new installed version of Teradata Parallel Transporter, verify that the TPT_install_directory/bin path is in the PATH environment variable. 4 If the TPT_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. 50 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 6 Troubleshooting the Installation Teradata Parallel Transporter Problem: Failed to Load libpxcommon Library Teradata Parallel Transporter Problem: Failed to Load libpxcommon Library 1 If a message similar to the following error message appears when executing a Teradata Parallel Transporter job, log off of the system and log on again. ld.so.1: tbuild: fatal: libpxcommon.so: open failed: No such file or directory Killed 2 Run the Teradata Parallel Transporter job again. 3 If the error message still appears, verify that the TPT_install_directory/lib path is in the PATH environment variable. 4 If the TPT_install_directory/lib 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 TPT_install_directory/msg path is in the PATH environment variable. 4 If the TPT_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. Technical Assistance For more information, see Teradata Tools and Utilities Release Definition, B035-2029. If you need additional information or assistance, contact your Teradata Customer Service Representative. If you purchased an Enterprise System Support (ESS) contract, a customized support plan was created for you. For contact information, refer to your support plan. To learn more about Teradata Customer Services, go to Teradata @ Your Service at tays.teradata.com Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 51 Chapter 6 Troubleshooting the Installation Technical Assistance 52 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 CHAPTER 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR The tar_teradata_client_packages script is intended for use by system administrators. The script aids with deploying Teradata Tools and Utilities products across a network. About the TAR File A tar file is an archive of files that you typically create on a UNIX or Linux system. The folder and file structure in the archive mirrors the structure of the source files. You can use the tar_teradata_client_packages script on the Teradata Tools and Utilities installation media to create a compressed archive of Teradata Tools and Utilities client packages for a specific platform or operating system from the installation media. You can also compress the tar file. A compressed tar file is like a zip or 7z or rar or cab file on a Windows system. On a 32-bit Windows system, you can create a tar file for bundling individual UNIX or Linux packages and their dependencies or the entire set of Teradata Tools and Utilities packages for UNIX or Linux. The tar archive can be copied to a network machine and deployed to UNIX or Linux clients through FTP. Use this option if for example the target UNIX or Linux clients have a CD drive but not a DVD drive. You can build the tar file to contain all of the packages for a specified platform, or all the files for a specified package. It also includes all of the required dependencies for the selected packages. TAR Script Compatibility with Platform Operating Systems The tar_teradata_client_packages script provided on the installation media runs on 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 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 53 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR 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. 1 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 Displays the available commands or tar_teradata_client_packages help 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 • pa-risc • s390x • sparc The path for the output can be changed. The output filename is in the following format: teradata-client-platform-media-name.tar. If the archive is compressed with gzip.exe, the script appends .gz to the • tar_teradata_client_packages platform package filename. Run the script with platform as the second parameter after the list parameter to list the packages available for the specified platform. Creates a tar file for a specific platform and one package Add the name of a package after the platform parameter. For example, to archive the bteq package for the aix platform, type: 54 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR Command Description 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: • cliv2 • piom • tdicu • teragss If you specify package names after the platform parameter, the script includes the dependent packages if they are available on the media. If you specify individual packages, all of the dependendent packages are included in the archive. tar_teradata_client_packages platform package1 Creates a tar file for a specific platform and specific packages package2 etc. 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 dependendent 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 Dependent Packages If a single package or multiple packages are selected, all of the dependent products are included, even if the product selected is one of the single dependent packages. Dependent packages typically have mutual dependencies. For example, dependent package cliv2 depends on the dependent packages tdicu and TeraGSS. 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: • tar_teradata_client_packages Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 55 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR Subject Description • tar_teradata_client_packages help A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v.xx.xx.xx.xx * ************************************************************************ Tar Teradata Client Packages Usage: tar_teradata_client_packages list tar_teradata_client_packages list {platform} tar_teradata_client_packages {platform} [{package1} {package2} ...] Parameters: commands help list : 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, pa-risc, i386, s390x, opteron, sparc Create the tar file for the supplied platform and include all packages or individual packages. {package} : Specify the packages available on this media for the specific platform. The parameter "all" (or blank) will include all available packages. To specify individual packages, list the packages separated by a space. Example: ttcp.bat linux bteq fastld The dependencies will automatically be included and do not need to be listed individually. The following packages are included: ---TeraGSS cliv2 tdicu piom All of the platforms and packages contained on the installation media can be listed by running the Listing the Available Packages and Platforms tar_teradata_client_packages script with the list parameter, for example: tar_teradata_client_packages list To list all packages for a specific platform available on the installation media, run tar_teradata_client_packages list platform where platform is the value of one of the platforms, for example: tar_teradata_client_packages list hp-ux A screen similar to the following appears as a result. It lists all the platforms and packages on the current installation media: ************************************************************************ * Tar Teradata Client Packages v.xx.xx.xx.xx * ************************************************************************ TTU Foundation 56 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR Subject Description The available platforms are: HP-UX Linux The available packages are: --- HP-UX Products bteq fastexp mload npaxsmod 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 Red Hat Enterprise Linux Installation Guide, Release 15.00 57 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR If gzip.exe is not installed, a message similar to the following appears during the creation of the tar file: Notice: The executable gzip.exe is not found. Download from 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: ************************************************************************ * Tar Teradata Client Packages v.15.00.00.00 * ************************************************************************ 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 58 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR cliv21500 sqlpp1500 tdicu1500 TeraGSS TeraGSS32 --- Solaris Opteron Products cliv21500 sqlpp1500 tdicu1500 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.15.00.00.00 * ************************************************************************ TTU Foundation Platform: Solaris\Sparc Default Path and Output File: C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar Hit [Enter] to accept the path: "C:\Documents and Settings\<user>", or input a different save directory :Output File "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttu-foundation.tar" b Press Enter to accept the default path, copy the packages, and create the tar archive. A screen similar to the following appears: ---Archiving all packages for sparc. tar cvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar" Solaris\Sparc Solaris/Sparc/ Solaris/Sparc/TeraGSS/ Solaris/Sparc/TeraGSS/install/ Solaris/Sparc/TeraGSS/install/depend . . (more files) . Solaris/Sparc/tdicu1500/reloc/$LIBDIR64/libiculxtd.so.46.0 Solaris/Sparc/tdicu1500/reloc/$LIBDIR64/libicuuctd.so.46.0 tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar" .setup.sh .setup.sh tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar" setup.bat setup.bat tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar" MEDIALABEL MEDIALABEL tar rvf "C:\Documents and Settings\<user>\teradata-client-Solaris-Sparc-ttufoundation.tar" Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 59 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR tar_teradata_client_packages.* tar_teradata_client_packages.bat tar_teradata_client_packages.sh Notice: The executable gzip.exe is not found. Download from 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. 1 Run the script with linux as the value of the platform parameter: D:\tar_teradata_client_packages linux A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v.15.00.00.00 * ************************************************************************ 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-15.00.00.00-1.i386.rpm 118 blocks a Linux/mload/mload1500-15.00.00.00-1.i386.rpm 374 blocks a Linux/piom/piom1500-15.00.00.00-1.i386.rpm 79 blocks a Linux/tdicu/tdicu-15.00.00.00-1.noarch.rpm 20564 blocks a Linux/fastld/fastld1500-15.00.00.00-1.i386.rpm 189 blocks a Linux/TeraGSS/TeraGSS_redhatlinux-i386-15.00.00.00-1.i386.rpm 12240 blocks a Linux/fastexp/fastexp1500-15.00.00.00-1.i386.rpm 341 blocks a Linux/tpump/tpump1500-15.00.00.00-1.i386.rpm 478 blocks a Linux/npaxsmod/npaxsmod-15.00.00.00-1.i386.rpm 272 blocks a Linux/cliv2/cliv2-15.00.00.00-1.x86_64.rpm 766 blocks a Linux/bteq/bteq-15.00.00.00-1.i386.rpm 303 blocks tar rvf "C:\Documents and Settings\user\teradata-client-linux-ttufoundation.tar" .setup.sh tar: blocksize = 20 a .setup.sh 282 blocks tar rvf "C:\Documents and Settings\user\teradata-client-linux-ttu-foundation.tar" setup.bat tar: blocksize = 20 a setup.bat 1 block 60 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR 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 Red Hat Enterprise Linux Installation Guide, Release 15.00 61 Chapter 7 Deploying Teradata Tools and Utilities with TAR About Deploying Applications with TAR 62 Teradata Tools and Utilities for Red Hat Enterprise Linux Installation Guide, Release 15.00