Teradata Tools and Utilities for SUSE Linux Installation Guide Release B A November 2011

Transcription

1 Teradata Tools and Utilities for SUSE Linux Installation Guide Release B A November 2011

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Active Enterprise Intelligence, Applications Within, Aprimo, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast, Gridscale, Managing the Business of Marketing, MyCommerce, Raising Intelligence, Smarter. Faster. Wins., SQL-MapReduce, Teradata Decision Experts, Teradata Labs Logo, Teradata Raising Intelligence Logo, 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. 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. 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 Quest Software, 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. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a registered trademark of Unicode, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. The information contained in this document is provided on an as-is basis, without warranty of any kind, either express or implied, including the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. In no event will Teradata Corporation be liable for any indirect, direct, special, incidental, or consequential damages, including lost profits or lost savings, even if expressly advised of the possibility of such damages. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please [email protected] Any comments or materials (collectively referred to as Feedback ) sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright by Teradata Corporation. All Rights Reserved.

3 Table of Contents Preface...9 Purpose...9 Audience...9 Supported Releases...9 Prerequisites...10 Changes to This Documentation...10 Chapter 1: Prepare for Installation...11 Introduction to Installing Teradata Tools and Utilities from DVD...11 Installation Kit Contents...11 DVD Contents...11 Supported Versions...13 Product Descriptions...13 Product Dependencies...15 Installing Dependencies...17 System Requirements...17 Chapter 2: Uninstall Previous Software...19 Uninstall Script Overview...19 Uninstall Script Operation...19 Uninstall Script Usage and Parameters...20 Usage...20 Parameters...20 Teradata Tools and Utilities Packages Removed...21 Typical Output...22 Library File Checking Output...22 Manually Removing Packages...23 Teradata Tools and Utilities for SUSE Linux Installation Guide 3

4 Table of Contents Chapter 3: Install New Software...25 Installing Third-Party Software...25 Teradata WebSphere MQ Access Module...25 Installing Teradata Tools and Utilities...25 Installation Order...26 Installing Teradata Tools and Utilities...26 Teradata Meta Data Services...27 Introduction to the Teradata Meta Data Services Installation...28 Teradata Meta Data Services Documentation...28 Teradata Meta Data Services Installation Options...28 Teradata Meta Data Services Prerequisites...29 Teradata Meta Data Services Software Components...29 Uninstalling Teradata Meta Data Services...30 Uninstalling the Teradata Meta Data Services Development Kit Files...31 Uninstalling Teradata Meta Data Services with Automatic DIM Update Enabled...31 Uninstalling the Relay Services Gateway...31 Installing Teradata Meta Data Services...32 Installing and Configuring the ODBC Driver for Teradata Package...32 Installing the Teradata Meta Data Services Core Files...33 Installing the Teradata Meta Data Services Development Kit Package...34 Configuring Linux Workstations or Servers...34 Creating a Teradata Meta Data Services Repository...35 Migrating a Teradata Meta Data Services Repository...35 Installing the Automatic Database Information Metamodel...35 Automatic DIM Update Processes...35 Out of Sync Recovery...37 Installing the DIM Update Server Software...38 Installing the Teradata Meta Data Services Action Processor...38 Installing the Teradata Meta Data Services Data Definition Language Gateway...39 Configuring the odbc.ini File...40 Relay Services Gateway Overview...40 Installing the Relay Services Gateway...41 Configuring the Relay Services Gateway...41 Starting and Stopping the Relay Services Gateway...42 Configuring the Automatic DIM Update with MetaManager...42 Adding a Teradata Database System...42 Adding Teradata Nodes...43 Editing a Teradata Node in MetaManager Teradata Tools and Utilities for SUSE Linux Installation Guide

5 Table of Contents Loading Databases...43 Enabling Automatic Database Information Metamodel Update...44 Checking DIM Status with MetaManager...44 Starting and Stopping the Data Definition Language Gateway...45 Starting and Stopping the Teradata Meta Data Services Action Processor...45 Teradata Developer Exchange...46 Products Available from Teradata Developer Exchange...46 Downloading a Product from the Teradata Developer Exchange...46 Installing Products Downloaded from Teradata Developer Exchange...47 Teradata Software Server...48 Downloading Patches...48 Installing Downloaded Patches...48 Adding CLI User Exit Functions...49 Chapter 4: Configure New Software...51 Creating Environment Variables...51 Overview of Configuring ODBC Driver for Teradata...51 About Configuring Teradata Parallel Transporter...51 Editing twbcfg.ini...52 Selecting Checkpoint and Log Directories in the Configuration File...52 Setting Shared Memory Parameters...52 Setting Semaphore Parameters...53 Updating Environment Variables...53 Switching IPC Memory to Shared Memory...54 Switching IPC Memory to Mapped Memory...54 Chapter 5: Restart the Client Computer...55 Restarting the Client Computer...55 Chapter 6: Verify the Complete Installation...57 About Verifying the Installation...57 Verifying the Installation Using Basic Teradata Query...57 Verifying the Installation Using CLI Sample Program...58 Basic Teradata Query Files and Directories...59 Named Pipe Access Module Files and Directories...59 Teradata Tools and Utilities for SUSE Linux Installation Guide 5

6 Table of Contents ODBC Driver for Teradata Files and Directories...59 Shared Common Components for Internationalization for Teradata Files and Directories...61 Teradata Archive/Recovery Utility Files and Directories...63 Teradata C Preprocessor2 Files and Directories...64 Teradata Call-Level Interface version 2 Files and Directories...64 Teradata Data Connector Files and Directories...66 Teradata FastExport Files and Directories...66 Teradata FastLoad Files and Directories...67 Teradata Generic Security Services Files and Directories...67 Teradata JDBC Driver Files and Directories...67 Teradata MultiLoad Files and Directories...68 Teradata Parallel Data Pump Files and Directories...68 Teradata Wallet Files and Directories...68 Teradata WebSphere MQ Access Module Files and Directories...69 Chapter 7: Security and Connecting to a Teradata Database...71 About Connecting to a Teradata Database...71 About Logon Procedures...71 Connecting to a Teradata Database from a GUI Application...71 Connecting to a Teradata Database from a Command Line Application...73 Kerberos Logon Examples...74 LDAP Logon Examples...75 Implicit Logon...75 Accounting Information...75 TD2 Logon Examples...76 TD2 Logon Mechanisms...76 TD2 Logon...76 Connecting to a Teradata Database Programmatically...76 Checking Logon Error Messages...77 Chapter 8: Troubleshooting the Installation...79 Client Computer Problem: Cannot Communicate Over the Network with Teradata Database...79 Client Computer Problem: Incorrect Path Name in COPLIB...79 Client Computer Problem: Incorrect Path Name in COPERR...80 Client Computer Problem: errmsg.cat File Not Found...80 Client Computer Problem: Incorrect Path Name in COPANOMLOG...80 Client Computer Problem: Missing Hosts File...81 Client Computer Problem: Incorrect Entries in the Hosts File Teradata Tools and Utilities for SUSE Linux Installation Guide

7 Table of Contents Client Computer Problem: Missing Entries in the /etc/services File...81 Client Computer Problem: Improper Linking...81 Client Computer Problem: Incorrect clispb.dat Parameters...81 Client Computer Problem: Cannot Log On from CLI Application...82 Client Computer Problem: Cannot Log On to Teradata Database...82 Network Problems...82 Teradata Database Problem...83 Teradata Parallel Transporter Problem: Unable to Find tbuild...84 Teradata Parallel Transporter Problem: Can Not Run New Version of Teradata Parallel Transporter...84 Teradata Parallel Transporter Problem: Failed to Load libpxcommon Library...85 Teradata Parallel Transporter Problem: Unable to Find Messages...85 Technical Assistance...85 Chapter 9: Deploy Teradata Tools and Utilities with TAR...87 Deploying Applications with TAR...87 TAR Script Information...87 TAR Script Compatibility with Platform Operating Systems...87 TAR File Contents...87 Verifying TAR Script Dependencies are Installed...88 TAR Script Commands and Their Functions...88 TAR Script Usage Considerations...90 Downloading Windows Utility Software for TAR Deployment...91 Overview of TAR Script Examples...92 Archiving SPARC Packages to Windows...92 Archiving Packages to Linux...94 Teradata Tools and Utilities for SUSE Linux Installation Guide 7

8 Table of Contents 8 Teradata Tools and Utilities for SUSE Linux Installation Guide

9 Preface Purpose This book describes how to install and deploy Teradata Tools and Utilities Release software on a computer that runs on a supported operating system. Teradata Tools and Utilities is a group of products designed to work with the Teradata Database. Audience This guide is intended for use by: Database administrators and relational database developers System administrators System and application programmers System operators and other database specialists Supported Releases This book supports the following releases: Teradata Database Release 14.0 Teradata Tools and Utilities Release To locate detailed supported-release information: 1 Go to 2 Under Online Publications, click General Search. 3 Type 3119 in the Publication Product ID box. 4 Under Sort By, select Date. 5 Click Search. 6 Open the version of the Teradata Tools and Utilities ##.##.## Supported Platforms and Product Versions spreadsheet associated with this release. The spreadsheet includes supported Teradata Database versions, platforms, and product release numbers. Teradata Tools and Utilities for SUSE Linux Installation Guide 9

10 Preface Prerequisites Prerequisites You should be familiar with: Computer technology and terminology Relational database management systems Utilities that load and retrieve data Changes to This Documentation Date November August Description The following changes were made to support the November release of Teradata Tools and Utilities: Teradata Archive/Recovery Utility was added. Teradata JDBC Driver was added. Teradata Meta Data Services was added. Teradata Wallet was added. The uninstall script, uninstall_ttu.sh, was added. Initial release 10 Teradata Tools and Utilities for SUSE Linux Installation Guide

11 CHAPTER 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Before performing the procedures in this document, you must have: Network access Administrative privileges on the target machine Knowledge of which Teradata Tools and Utilities are to be installed Familiarity with Linux file and path name conventions Access to a bill of materials or similar list of Teradata Tools and Utilities software that was ordered Familiarity with software installation Installation Kit Contents The installation kit contains the following documentation and application media: Teradata User Documentation CD (Teradata Database 14.0, Teradata Tools and Utilities 14.00) Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities Tape Storage Management Enablers Linux & WINDOWS Release DVD Teradata Tools and Utilities Meta Data Services Linux & WINDOWS Release DVD If you did not receive all the installation media ordered, contact the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC). For information on how to contact TSCS-RSC, see B C, Teradata Tools and Utilities Release Definition Release DVD Contents The following table shows the Teradata Tools and Utilities products and dependencies contained on the Installation Kit media. Teradata Tools and Utilities for SUSE Linux Installation Guide 11

12 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Basic Teradata Query Named Pipes Access Module ODBC Driver for Teradata Shared Common Components for Internationalization for Teradata Teradata Archive/Recovery Utility Teradata C Preprocessor2 Teradata Call-Level Interface version 2 Teradata COBOL Preprocessor2 Teradata Data Connector Teradata FastExport Teradata FastLoad Teradata Generic Security Services Client Teradata JDBC Driver Teradata JMS Access Module Teradata Meta Data Services Teradata MultiLoad Teradata Parallel Data Pump Teradata Parallel Transporter Base Teradata Parallel Transporter Stream Teradata Wallet Install From... Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities Tape Storage Management Enablers Linux & WINDOWS Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities Meta Data Services Linux & WINDOWS Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD 12 Teradata Tools and Utilities for SUSE Linux Installation Guide

13 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Teradata WebSphere MQ Access Module Install From... Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD For information on products that can or must be downloaded from Teradata Developer Exchange, see Products Available from Teradata Developer Exchange. Supported Versions Teradata Tools and Utilities Version xx xx xx Versions Chart B K, Teradata Tools and Utilities xx Supported Platforms and Product Versions B K, Teradata Tools and Utilities xx Supported Platforms and Product Versions B K, Teradata Tools and Utilities xx Supported Platforms and Product Versions B K, Teradata Tools and Utilities Supported Platforms and Product Versions Product Descriptions Product Basic Teradata Query Named Pipes Access Module ODBC Driver for Teradata Shared Common Components for Internationalization for Teradata Teradata Archive/Recovery Utility Description Provides workstation users with command-line-based communication with one or more Teradata Database systems and formatting of reports for both print and screen output. Provides an interprocess communication link between a writer process, such as Teradata FastExport, and a reader process, such as Teradata FastLoad. Named Pipes Access Module works for Teradata Parallel Transporter and the standalone utilities (Teradata FastExport, Teradata FastLoad, Teradata MultiLoad, and Teradata Parallel Data Pump). Enables operating systems to communicate with the Teradata Database across local area networks using the open standards ODBC interface. With ODBC Driver for Teradata, connects applications to the Teradata Database. A library of routines based on the IBM International Components for Unicode version 3.6. The library provides Unicode support. Writes and reads sequential files on a Teradata client system to archive, restore, recover, and copy Teradata Database table data. 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 Backup Applications. It is not sold as a standalone product. Teradata Tools and Utilities for SUSE Linux Installation Guide 13

14 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Teradata C Preprocessor2 Teradata Call-Level Interface version 2 Teradata COBOL Preprocessor2 Teradata Data Connector Teradata FastExport Teradata FastLoad Teradata Generic Security Services Client Teradata JDBC Driver Teradata JMS Access Module Teradata Meta Data Services Teradata MultiLoad Teradata Parallel Data Pump Teradata Parallel Transporter Base Description Provides the application programmer with a simplified method of reading and changing information stored in the Teradata Database by interpreting and expanding SQL statements that have been incorporated in an application program. A library of routines that enable an application program to access data on the Teradata Database. Provides the application programmer with a simplified method of reading and changing information stored in a Teradata Database by interpreting and expanding SQL statements that have been incorporated in an application program. Reads and writes flat files to provide the input/output interface for access modules. A command-driven utility that uses multiple sessions to quickly transfer large amounts of data from tables and views of the Teradata Database to a client based application. A command-driven utility that quickly loads large amounts of data to empty tables in the Teradata Database. Teradata FastLoad uses multiple sessions to load data; however, it loads data into only one table on the Teradata Database per job. Teradata implementation of industry-standard Generic Security Services APIs in C language. It provides enhanced security services interfaces between Teradata network clients and the Teradata Database. Provides access to the Teradata Database using Java applications. Note: Can be downloaded and installed from the web. A utility that provides a fast, reliable, asynchronous method to transfer data between any JMS-enabled messaging system and Teradata Database. Teradata JMS Access Module works for Teradata Parallel Transporter and the standalone utilities (Teradata FastExport, Teradata FastLoad, Teradata MultiLoad, and Teradata Parallel Data Pump). Provides an infrastructure for managing Teradata active data warehouse metadata and for creating tools to interchange metadata with external operational systems, Extraction Transformation and Load tools, Business Intelligence tools, Database Modeling tools, and any other metadata sources. Provides an efficient way to deal with batch maintenance of large databases. Teradata MultiLoad is a command-driven utility for fast, high-volume maintenance on multiple tables and views of the Teradata Database. A data loading utility that helps maintain the data in the Teradata Database. Teradata Parallel Data Pump uses standard Teradata SQL to achieve moderate to high data loading rates to the Teradata Database. Object-oriented client application that provides scalable, high-speed, parallel data extraction, loading, and updating. 14 Teradata Tools and Utilities for SUSE Linux Installation Guide

15 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Teradata Parallel Transporter Stream Teradata Wallet Teradata WebSphere MQ Access Module Description A consumer operator that emulates the Teradata Parallel Data Pump utility to perform high-speed DML transactions (SQL INSERT, UPDATE, DELETE, or UPSERT) in a near-real-time mode to a table (or tables) while queries are performed on the table (or tables). Enables users to securely store private information, such as Teradata Database passwords, on client computers. The stored information can then be used when logging in to the Teradata Database. Allows Teradata utilities to import data using IBM Teradata WebSphere MQ Access Module message queuing middleware. Teradata WebSphere MQ Access Module works for Teradata Parallel Transporter and the standalone utilities (Teradata FastExport, Teradata FastLoad, Teradata MultiLoad, and Teradata Parallel Data Pump). Product Dependencies Product Teradata Tools and Utilities Dependencies Third-party Dependencies Basic Teradata Query Named Pipes Access Module ODBC Driver for Teradata Shared Common Components for Internationalization for Teradata Teradata Archive/ Recovery Utility Teradata C Preprocessor2 Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client None Shared Common Components for Internationalization for Teradata Teradata Generic Security Services Client None Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Generic Security Services Client None None Microsoft Data Access Components (MDAC), version 2.8 SP1 (on distribution DVD) None None None Teradata Tools and Utilities for SUSE Linux Installation Guide 15

16 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata Call-Level Interface version 2 Teradata COBOL Preprocessor2 Teradata Data Connector Teradata FastExport Teradata FastLoad Teradata Generic Security Services Client Shared Common Components for Internationalization for Teradata Teradata Generic Security Services Client Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Generic Security Services Client None Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client None None None None None 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 JMS Access Module Teradata Meta Data Services Teradata MultiLoad Teradata Parallel Data Pump None ODBC Driver for Teradata Shared Common Components for Internationalization for Teradata Teradata Generic Security Services Client Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 None JRE 5.0 or JRE bit Note: The environment can be downloaded from Java Downloads. None None 16 Teradata Tools and Utilities for SUSE Linux Installation Guide

17 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata Parallel Transporter Base Teradata Parallel Transporter Stream Teradata Data Connector Teradata Generic Security Services Client Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Generic Security Services Client Teradata Call-Level Interface version 2 Teradata Generic Security Services Client Teradata Parallel Transporter Base None Note: The environment can be downloaded from Java Downloads. None Teradata Wallet None None Teradata WebSphere MQ Access Module Teradata Data Connector IBM WebSphere MQ V5.2 Installing Dependencies The Teradata Tools and Utilities installation automatically installs dependent products. A message appears if a dependent product already exists on the client system for one of the following products: ODBC Driver for Teradata Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client The installation displays one of these messages: 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 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 is already installed. Do you want to overwrite it with 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. Teradata Tools and Utilities for SUSE Linux Installation Guide 17

18 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD 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. The appropriate Ethernet hardware and software supporting a TCP/IP-based network must be installed on every Teradata Database with which the client communicates. 18 Teradata Tools and Utilities for SUSE Linux Installation Guide

19 CHAPTER 2 Uninstall Previous Software Uninstall Script Overview Before installing new Teradata Tools and Utilities software, previous versions of Teradata Tools and Utilities software must be removed. Use the uninstall script, uninstall_ttu.sh, located in the root directory on the media, to remove previous versions of Teradata Tools and Utilities software. It removes all Teradata Tools and Utilities packages, including dependency packages, in the correct order. When the uninstall script is executed from the main install script, it offers to remove packages from previous versions of TTU and leave any current versions installed. The uninstall script can be used before installing a new or a specific version of Teradata Tools and Utilities software or if decommissioning Teradata Tools and Utilities software from a particular system. The uninstall script can specify individual packages to be removed. Teradata recommends that you remove the dependency products (CLIv2, PIOM, TDICU, and TeraGSS) last; however they can be removed individually regardless of the order. Caution: If a dependency product is removed without reinstalling a new version, the products that depend on that product cease to function. For example, if CLIv2 is removed, all products that depend on CLIv2 fail. The uninstall script warns you if the product you have asked to remove is a dependency and asks if you are sure you want to remove it. The uninstall script does not require any parameters to execute and all information within the script is displayed. The uninstall script must be executed as root or with root privileges, as it uses system packaging commands to remove packages. Uninstall Script Operation The uninstall 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 Teradata Tools and Utilities for SUSE Linux Installation Guide 19

20 Chapter 2 Uninstall Previous Software Uninstall Script Overview After the package removal process is complete, the uninstall 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. Uninstall Script Usage and Parameters Usage Command uninstall_ttu.sh uninstall_ttu.sh priorto xx.xx.xx.xx uninstall_ttu.sh noremove uninstall_ttu.sh nocheck Description Executes the script to remove packages Removes all packages before a specific version number Executes the script, but does not remove any packages Executes the script, but does not check against known Teradata Tools and Utilities packages Parameters Parameter priorto xx.xx.xx.xx noremove nocheck Description Removes packages prior to a specified version If the packages to be installed on a system are from Teradata Tools and Utilities version 14.00, and packages prior to this version (for example, 13.10, 13.0, or 12.00) need to be removed, enter priorto The number parameter must contain all four version numbers, and can be specific enough to remove all packages before, for example, Typically the last two sets of digits would just be Executes the script without removing packages This parameter can be used to test the script without removing the packages. The package remove commands that would have been used to remove each package are displayed. This may be useful to do a test package remove without actually removing the packages, to see in what order the packages would have been removed, or to capture the commands used to remove the packages for use in another script. Executes the script looking for packages with "Teradata" in the package name, but skipping the check against the known list of Teradata Tools and Utilities packages 20 Teradata Tools and Utilities for SUSE Linux Installation Guide

21 Chapter 2 Uninstall Previous Software Uninstall Script Overview Parameter Description 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. Caution: 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-tcpdebug-<processid>.out This may be useful for debugging purposes. It lists the known Teradata Tools and Utilities packages, the initial list of the packages selected, and the final ordered list, and could be helpful in determining why a package was not removed. Teradata Tools and Utilities Packages Removed The uninstall script recognizes the following Teradata Tools and Utilities packages: Basic Teradata Query (bteq) DUL/Dultape (dul and dultape) Named Pipes Access Module (npaxsmod) ODBC Driver for Teradata (tdodbc and tdodbc64) Shared Common Components for Internationalization for Teradata (tdicu, tdicu_64, and so on) SQL C Preprocessor (sqlpp) Teradata Archive/Recovery Utility (arc) Teradata Call-Level Interface version 2 (cliv2, cliv2_64, cliv2so, and so on) Teradata COBOL Preprocessor2 (cobpp) Teradata Data Connector (piom) Teradata FastExport (fastexp) Teradata FastLoad (fastld) Teradata Generic Security Services Client (TeraGSS) Teradata JMS Access Module (jmsaxsmod) Teradata MultiLoad (mload) 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/ Teradata Tools and Utilities for SUSE Linux Installation Guide 21

22 Chapter 2 Uninstall Previous Software Uninstall Script Overview bin or /usr/lib directories. The uninstall 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 uninstall script renames them and adds the extension teradata-package-remove.old: ODBC Driver for Teradata Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client Typical Output Package Removal Type: rpm The following packages are installed: 1. bteq fastexp fastld mload mload mqaxsmod npaxsmod npaxsmod tdodbc tdwallet tptstream tpump tpump tptbase piom cliv cliv tdicu tdicu TeraGSS TeraGSS f. Display the full package information on the packages listed. a. Remove all of the above software. h. Display help information. q. Quit the package remove script. Enter one or more selections (separated by space): 16 cliv is a product dependency. Are you sure you wish to remove it? [Y/N] > Library File Checking Output If all files are not removed, output similar to this appears: 22 Teradata Tools and Utilities for SUSE Linux Installation Guide

23 Chapter 2 Uninstall Previous Software Uninstall Script Overview WARNING: Teradata Libraries were found after post package removal. /usr/lib/libcliv2.so /usr/lib/libtdusr.so /usr/lib/libpm.so /usr/lib/libicudatatd.so /usr/lib/libicui18ntd.so /usr/lib/libicuiotd.so /usr/lib/libiculetd.so /usr/lib/libiculxtd.so /usr/lib/libicuuctd.so These files/softlinks may be the result of broken package uninstall and may interfere with future Teradata Client installations. Would you like to move these files to <filename>.teradata-package-remove.old in order to prevent this conflict? [Y/N] (default N): If you answer yes when asked if you would like to move these files, output similar to this appears: Moving /usr/lib/libcliv2.so to /usr/lib/libcliv2.so-teradata-package-remove.old Moving /usr/lib/libtdusr.so to /usr/lib/libtdusr.so-teradata-package-remove.old Moving /usr/lib/libpm.so to /usr/lib/libpm.so-teradata-package-remove.old Moving /usr/lib/libicudatatd.so to /usr/lib/libicudatatd.so-teradata-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 Removing Packages If a package was not properly removed by the uninstall script, trying running the script a second time. To manually remove a package, follow these steps: Teradata Tools and Utilities for SUSE Linux Installation Guide 23

24 Chapter 2 Uninstall Previous Software Uninstall Script Overview 1 To see if a package is still installed, type: rpm q <packagename> 2 To manually remove a package, type: rpm erase --ignoredeps <packagename> 24 Teradata Tools and Utilities for SUSE Linux Installation Guide

25 CHAPTER 3 Install New Software Installing Third-Party Software Some Teradata Tools and Utilities products require the installation of third-party software. This third-party software can be downloaded and installed from the manufacturer's website. Teradata WebSphere MQ Access Module 1 Download and install IBM WebSphere MQ 5.2 before running Teradata WebSphere MQ Access Module. Installing Teradata Tools and Utilities Whenever installing Teradata Tools and Utilities software, always compare the versions available on the DVD installation media, the Teradata Developer Exchange and the Teradata Software Server. In general, the software server will contain the most recent point release of a software product, followed in turn by the download center, and finally the installation media. Installation Type Installing from a Web URL Installing from DVD Installing from the Teradata Developer Exchange Installing from the Teradata Software Server Installing from the Teradata ESDM Server Deploying using tar Installing Teradata Meta Data Services Description Some Teradata Tools and Utilities have third-party dependencies. Install these dependencies from their respective URLs. The initial distribution of software is on DVD media. Using the main install, install products on a single-user from the DVD media in the Teradata Tools and Utilities Installation Kit. The DVDs contain installation packages for the current release. 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. The server may contain updated software packages which should be installed in lieu of lower version software contained on the DVD media, or on the Teradata Developer Exchange. Teradata Electronic Software Distribution Management (ESDM) program allows users tax benefits for some users that download software. The DVD media include files that allow you to deploy Teradata Tools and Utilities products across your network using tar.vbs scripts and tar. Teradata Meta Data Services (MDS) is installed from DVD or the Teradata Software Server. Installation is generally limited to administrative users. Teradata Tools and Utilities for SUSE Linux Installation Guide 25

26 Chapter 3 Install New Software Installing Teradata Tools and Utilities 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. Teradata Generic Security Services Client (teragss) Shared Common Components for Internationalization for Teradata (tdicu) Teradata Call-Level Interface version 2 (cliv2) Teradata Data Connector (piom) Any other products Note: Because the installation procedure for the ODBC Driver for Teradata installs both 32- bit and 64-bit versions of the ODBC Driver for Teradata, both the 32-bit and 64-bit versions of Teradata Generic Security Services Client must be installed before installing ODBC Driver for Teradata. Installing Teradata Tools and Utilities 1 Log on as the root user. 2 If a /mnt directory does not exist, create one: mkdir /mnt 3 Insert the Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release DVD into the media drive and type: mount /dev/<media device name>/mnt For example, if the media device name is c0t1d0, type: mount /dev/c0t1d0/mnt where the media mount point is /mnt. 4 To begin the installation process, type: cd /mnt./setup.bat A screen appears that: Identifies the platform and media Lists numbered products that can be installed Provides options for: Installing all software Removing previously installed software Displaying the sizes of the installed package Quitting the installation 5 Select the packages to install. Software must be installed in the following order: 26 Teradata Tools and Utilities for SUSE Linux Installation Guide

27 Chapter 3 Install New Software Installing Teradata Tools and Utilities 1. Teradata Generic Security Services Client (teragss) 2. Shared ICU Libraries for Teradata (tdicu) 3. Teradata Call-Level Interface version 2 (cliv2) 4. Teradata Data Connector (piom) 5. Other Products Note: If Teradata Call-Level Interface version 2 is installed before Teradata Wallet and Teradata Wallet is installed using a different directory prefix than the default /opt, Teradata Call-Level Interface version 2 will not be able to use Teradata Wallet. To avoid this situation, either install Teradata Wallet before installing Teradata Call-Level Interface version 2 or install Teradata Wallet using the default directory prefix. To rectify this situation, reinstall Teradata Call-Level Interface version 2. For Teradata Wallet Help, enter tdwallet help at the command prompt. See B A, Security Administration for more information about Teradata Wallet. 6 After reviewing product dependencies, do one of the following: Command Install All Packages Uninstall All Display installed package sizes Install Selected Packages Action Type 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. Type u. This removes previous versions of Teradata Tools and Utilities products, except Teradata Generic Security Services Client (TeraGSS). Type s to display the size of each installed package. 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 Teradata Call-Level Interface version 2 (cliv2) or Teradata Data Connector (piom). Enter the numbers for the dependencies at the prompt, separated by spaces. For information on dependent products, see Product Dependencies. Products: Enter the numbers for the products at the prompt, separated by spaces. Quit Type q to quit the installation. 7 Change back to the root directory and unmount the DVD. umount /mnt 8 Remove the installation DVD from the media drive. 9 When you are finished installing products, remove the last installation DVD from the media drive. Teradata Meta Data Services Teradata Meta Data Services (MDS) provides an infrastructure for managing Teradata data warehouse metadata and creating tools to interchange metadata with external operational Teradata Tools and Utilities for SUSE Linux Installation Guide 27

28 Chapter 3 Install New Software Installing Teradata Tools and Utilities systems, Extraction Transformation and Load (ETL) tools, Business Intelligence tools, Database Modeling tools, and other metadata sources. The following figure shows a typical Teradata MDS configuration consisting of: A Teradata Database System containing a Teradata MDS repository One or more workstations accessing the Teradata MDS repository with a web browser An Active Server Pages (ASP)-compliant web server with MetaSurf installed A Windows-based workstation configured to administer the Teradata MDS repository Client Web Browser Workstation/Laptop/Etc. with Supported Browsers ASP Page Metasurf * MetaManager/ MetaBrowse (Windows PC) * HTML Page HTTP Request Intranet or Internet Active Server Engine MDS Com Interface + Engine MDS Engine HTML Page ODBC ODBC Teradata Database Windows Web Server MDS Repository *MDS Installed Teradata Server 3118B001 A system may also contain one or more workstations that will be used to develop or run Teradata MDS applications and, if the Teradata MDS Automatic DIM Update feature is to be installed, a designated DIM Update server. Introduction to the Teradata Meta Data Services Installation Teradata Meta Data Services Documentation Click the link to display a list of Teradata Meta Data Services documentation. Teradata Meta Data Services Installation Options Before you install Teradata Meta Data Services, compare the versions available on the DVD and those on the Teradata Software Server. The Teradata Software Server contains the most recent point release of a software product. Installing from DVD: Teradata Tools and Utilities installs on a single user from the DVD in the Teradata Tools and Utilities Installation Kit. The DVD contains installation packages for the current release. Installing from the Teradata Software Server: The Teradata Software Server contains updated software packages that should be installed instead of any lower version software on the DVD. 28 Teradata Tools and Utilities for SUSE Linux Installation Guide

29 Chapter 3 Install New Software Installing Teradata Tools and Utilities Teradata Meta Data Services Prerequisites The following table lists the software and hardware required before installing Teradata Meta Data Services (MDS). Text Box Teradata Database System Teradata User Account ODBC Driver for Teradata (ODBC) and Data Source Name (DSN) Windows-based Workstation Active Server Pages (ASP) Compliant Web Server DIM Update Server Description The Teradata MDS repository is stored in a Teradata Database system, V2R6.2.x or greater. The minimum size of the Teradata Database for a production Teradata MDS repository is 50 MB. Note: A versioned repository requires more space than a non-versioned repository. Because the Teradata MDS repository is stored in a Teradata Database system, a Teradata user account must connect to the Teradata Database system to access these tables. Note: A Teradata user account is required for each Teradata Database system to be loaded into the Teradata MDS repository. Unless the metaviews utility is used, these users must have SELECT privileges to the DBC tables. Note: If Teradata MDS is being installed on the workstation of the Teradata MDS administrator, grant the user all privileges to the Teradata Database system. All machines running Teradata MDS software must have the appropriate ODBC Driver for Teradata installed and configured. ODBC or later is required. For best results use the ODBC Driver for Teradata for the Teradata version that matches the Teradata MDS version being used. Compatible versions of Shared Common Components for Internationalization for Teradata and Teradata Generic Security Services Client must also be installed. Create a System DSN for the Teradata Database system that will contain the Teradata MDS repository. The odbc.ini file specifies the DSN information. The name and location of the odbc.ini file can be specified with the ODBCINI environment variable. Because the Teradata MDS administrative software is a Windows-based application, at least one Windows-based workstation is required. This can be a Windows XP, Windows Server 2008, Windows Server 2003, Windows Vista, or Windows 7 system. Hardware requirements are: Pentium PC or greater with at least 1 GB RAM Minimum of 50 MB disk space If the Teradata MDS MetaSurf web application will be used, a Windows 2008 Server with Microsoft IIS 7.0, a Windows 2003 Server with Microsoft IIS 6.0, or a Web Server that supports ASP and Microsoft COM components is required. If setting up and using the Teradata MDS Automatic DIM Update feature, a Linux, Windows XP, Windows Server 2003, or Windows Vista system is required to run the server processes. This can be an application node on the Teradata Database system or a separate host with a network connection to the Teradata Database system. Teradata Meta Data Services Software Components The following table shows the different types of Teradata Meta Data Services (MDS) software packages that perform different tasks and can be installed on different hardware and software environments. Teradata Tools and Utilities for SUSE Linux Installation Guide 29

30 Chapter 3 Install New Software Installing Teradata Tools and Utilities Text Box MDS Core Files MDS Development Kit MDS MetaSurf Files MDS DIM Update Files Description The core files are the Teradata MDS executables and DLLs and include the MDS MetaBrowse and MDS MetaManager programs. These files are required on all systems running a Teradata MDS application or developing Teradata MDS applications. The core files can be installed on Windows or Linux systems. The development kit contains additional files needed to develop Teradata MDS applications. Teradata MDS provides a set of application programming interfaces (APIs) for third-party applications to store, administer, and retrieve metadata from the Teradata MDS repository. The development kit also includes sample applications. The development kit must be installed on the workstation of any user who will be working with the Teradata MDS APIs. The development kit files can be installed on Windows or Linux systems. A directory of samples that show how to use the various APIs is part of the kit. MetaSurf provides HTML files and ASP scripts that enable users to browse and search the Teradata MDS repository using a Web application. The MetaSurf files must be installed on the ASP-compliant web server. If setting up and using the Teradata MDS Automatic DIM Update feature, install executable files for the Teradata MDS DDL Gateway and Teradata MDS Action Processor on the designated DIM Update Server. The Teradata MDS DIM Update files can be installed on Windows or Linux systems. Uninstalling Teradata Meta Data Services If an older version of the Teradata Meta Data Services software is installed, uninstall it before installing the new version. 1 Log on as the root user. 2 From the command line, type: metadelete superuser password [-F] -h where: superuser is the name of an Teradata Meta Data Services (MDS) administrator password is the password of an Teradata MDS administrator -F deletes the repository even if it is not the current release -h displays a message describing the metadelete parameters and then exits; no changes are made to the repository The metadelete program deletes all objects (tables, views, macros, and so on) that were created by Teradata MDS in the Teradata Database. 3 Do one of the following: If the Teradata MDS development kit and Teradata MDS DIM Update packages are not installed, remove the MDS base package to uninstall the MDS Core files: rpm -e mdsbase If the Teradata MDS development kit files are installed, see Uninstalling the Teradata Meta Data Services Development Kit Files. 30 Teradata Tools and Utilities for SUSE Linux Installation Guide

31 Chapter 3 Install New Software Installing Teradata Tools and Utilities If the Teradata MDS DIM Update files are installed, see Uninstalling Teradata Meta Data Services with Automatic DIM Update Enabled. Uninstalling the Teradata Meta Data Services Development Kit Files 1 Uninstall the Teradata Meta Data Services (MDS) development kit files: rpm -e mdssdk Uninstalling Teradata Meta Data Services with Automatic DIM Update Enabled 1 You must stop the DDL Gateway processes (gwclient, gwserver, and iserver) and Action Processor (metaaction) before uninstalling them. Note: You can stop the DDL Gateway and Action Processor without checking first to see if they are running. a Check whether the DDL Gateway is running: ps -elf grep server ps -elf grep gwclient b Stop the DDL Gateway: /etc/init.d/mdsgwy stop c Check whether the Action Processor is running: ps -elf grep metaaction d Stop the Action Processor: /etc/init.d/mdsap stop 2 Uninstall the DDL Gateway: rpm -e mdsgwy 3 Uninstall the Action Processor package: rpm -e mdsap 4 If the Teradata MDS development kit files are installed, uninstall them: rpm -e mdssdk 5 Uninstall the Teradata MDS base software: rpm -e mdsbase If the Automatic DIM Update feature will not be used in the future, see Uninstalling the Relay Services Gateway. Uninstalling the Relay Services Gateway 1 Perform a TPA shutdown, as a running Relay Services Gateway (RSG) cannot be removed: tpareset x stop 2 Remove the RSG package. Teradata Tools and Utilities for SUSE Linux Installation Guide 31

32 Chapter 3 Install New Software Installing Teradata Tools and Utilities It is strongly suggested that you use tdpkgrm because it allows selected versions of RSG to be removed from all nodes simultaneously. To remove the RSG package from a single node, use rpm -e rsg. The next time Teradata is reset, it stops logging to the Teradata Meta Data Services (MDS) Recovery Table and it does not start the Teradata MDS RSG program. Installing Teradata Meta Data Services Before installing the Teradata Meta Data Services (MDS) software, uninstall any Teradata MDS software currently installed on the machine. Installing and Configuring the ODBC Driver for Teradata Package 1 If the ODBC Driver for Teradata package (tdodbc) is not already installed, install it: rpm -i <RPM file name> where <RPM file name> is the name of the ODBC rpm file to install. For example: rpm -i tdodbc noarch.rpm The ODBC Driver for Teradata package installs a.odbc.ini file as shown in the following example: [ODBC] InstallDir=/usr/odbc Trace=0 TraceFile=/usr/joe/odbcusr/trace.log TraceAutoStop=0 [ODBC Data Sources] MDSDSN=tdata.so default=tdata.so SYSTEMIDSN=tdata.so [MDSDSN] Driver=/usr/odbc/drivers/tdata.so Description=MDS Repository DBCName= LastUser= Username= Password= Database= DefaultDatabase= [SYSTEM1DSN] Driver=/usr/odbc/drivers/tdata.so Description=Teradata V12.0 System DBCName= LastUser= Username= Password= Database= DefaultDatabase= [default] Driver=/usr/odbc/drivers/tdata.so Description=NCR 5500 running Teradata V12.0 DBCName= LastUser= Username= 32 Teradata Tools and Utilities for SUSE Linux Installation Guide

33 Chapter 3 Install New Software Installing Teradata Tools and Utilities Password= DefaultDatabase= 2 Edit the.odbc.ini file. There must be a.odbc.ini file everywhere that Teradata Meta Data Services (MDS) base files are (or will be) installed. The.odbc.ini file is usually in the /root directory, but the ODBCINI environment variable can be used to find the file if it is in another location. a In the [ODBC Data Sources] section, add a line with the DSN name as follows: There is only one Teradata MDS repository system, and its DSN will be supplied to the mdsconfig utility later. Enter that DSN information into the.odbc.ini file now. One or more Teradata Database systems will be tracked by Teradata MDS, and one of those systems might be the Teradata MDS repository system. Enter the DSN information for each of those systems if it is not already in the.odbc.ini file. The line has the form: <DSN name a>=tdata.so b For each DSN line added to the [ODBC Data Sources] section, add a new section with the following information: [<DSN name x>] Driver=/usr/odbc/drivers/tdata.so Description= DBCName=<system name> LastUser= Username= Password= Database= DefaultDatabase= Installing the Teradata Meta Data Services Core Files 1 After installing the Teradata ODBC package and editing the appropriate odbc.ini file, use one of the following to install the Teradata Meta Data Services (MDS) Core (mdsbase) package, which contains the executables and shared object libraries: PUT utility mdsbaseinstall command mdsbasenonstdinstall command If the mdsbaseinstall command is used, the Teradata MDS core files are installed in the /opt/teradata/mds directory. If the PUT utility or mdsbasenonstdinstall command is used, the Teradata MDS core files are installed in a nonstandard location. 2 Run the mdsconfig utility to configure the ODBC Data Source Name and Database User Name and Password for the Teradata MDS repository. Teradata Tools and Utilities for SUSE Linux Installation Guide 33

34 Chapter 3 Install New Software Installing Teradata Tools and Utilities If you will not be installing the Teradata MDS Development Kit Files, go to Configuring Linux Workstations or Servers. Installing the Teradata Meta Data Services Development Kit Package Prerequisite: Installing the Teradata Meta Data Services (MDS) development kit package is optional. The Teradata MDS Core (mdsbase) package must be installed before you install the Teradata MDS development kit package. 1 Use the PUT utility or mdssdkinstall command to install the Teradata MDS development kit package (mdssdk). The Teradata MDS development kit includes additional files, libraries, and source file examples on how to build Teradata MDS applications with the appropriate commands. The Teradata MDS development kit files are installed in the /opt/teradata/mds directory or a nonstandard location if that option was selected when the MDS base package was installed. Configuring Linux Workstations or Servers 1 Log on as the root user. 2 Run the mdsconfig utility to set the local configuration parameters. The Data Source Name (DSN) specified with mdsconfig for the location of the Teradata Meta Data Services (MDS) repository should have been added to the odbc.ini file on the Linux workstation or server. Use mdsconfig H to get help for the mdsconfig program. The following table shows the parameters for the mdsconfig utility. Parameter Description -h <metahome> Teradata MDS installation folder It is highly recommended that the default location of /opt/teradata/mds not be changed. -o <DSN> Default ODBC Data Source Name (DSN) that Teradata MDS uses to connect to the Teradata Database System containing the Teradata MDS repository -u <dbuser> Database User Name that Teradata MDS uses to log on to the Teradata Database System to access the Teradata MDS repository -p <dbpasswd> Database User Password that Teradata MDS uses to log on to the Teradata Database System to access the Teradata MDS repository -l <loglevel> Error Log level (0..5), where 0 is the least amount of logging and 5 is the greatest amount -t <tracelevel> Trace level (0..5) to be used for Application debugging, where 0 is the least amount of tracing and 5 is the greatest amount of tracing -s <numintsvr> Number of Integrity Servers for the Teradata MDS Data Definition Language (DDL) Gateway to start; default is 5 34 Teradata Tools and Utilities for SUSE Linux Installation Guide

35 Chapter 3 Install New Software Installing Teradata Tools and Utilities Parameter Description -H Displays option list Creating a Teradata Meta Data Services Repository If the system does not have an existing Teradata Meta Data Services (MDS) repository created from an earlier version of Teradata MDS, create one: 1 Log onto the workstation as the root user. 2 Run one of the following programs: To create a Teradata MDS repository without versioning support: /opt/teradata/mds/bin/metacreate To create a Teradata MDS repository with versioning support: /opt/teradata/mds/bin/metacreate -v Migrating a Teradata Meta Data Services Repository Prerequisite: The system must have an existing Teradata Meta Data Services (MDS) repository. 1 As a precaution, Teradata recommends that you create a backup of the Teradata Database containing the Teradata MDS repository before proceeding. If you are upgrading Teradata, you will create a backup in the next step. 2 If necessary, upgrade from an earlier version of the Teradata Database: a b Create a backup of the Teradata Database containing the Teradata MDS repository, if you have not already done so. Upgrade the Teradata Database. c Restore the Teradata MDS repository database. 3 Install the most recent Teradata MDS software components on a client that needs to access the MDS repository in that environment. 4 Use the metamigrate utility to migrate the Teradata MDS repository to the same version as the client. Migrating a Teradata MDS repository takes several minutes. 5 Install the most recent Teradata MDS software components on any additional clients that need to access the Teradata MDS repository. Installing the Automatic Database Information Metamodel Automatic DIM Update Processes Because Teradata Database metadata is a central part of the Teradata Meta Data Services (MDS) repository, it is vital to the use of Teradata MDS that the information be kept up to date and dynamically reflect any changes in the Teradata active data warehouse. The Automatic DIM Update feature dynamically keeps the Teradata MDS repository synchronized with the Teradata Database system it describes. Teradata Tools and Utilities for SUSE Linux Installation Guide 35

36 Chapter 3 Install New Software Installing Teradata Tools and Utilities The following figure shows the processes supporting Automatic DIM updates. Feature Relay Services Gateway Description The Relay Services Gateway (RSG) is a Teradata vproc that relays messages between Teradata and the Teradata MDS Data Definition Language (DDL) Gateway. Whenever a Teradata Database system processes a DDL statement, it sends the DDL to the RSG, which sends it on to the Teradata MDS DDL Gateway. The Teradata MDS DDL Gateway then updates the metadata in the Teradata MDS repository. An example of a DDL is: create table mytable (c1 int); DDL Gateway MDS Action Processor A RSG vproc must be running on every Teradata node of the Teradata Database system. The RSG communicates with the Teradata MDS DDL Gateway via TCP/IP. The Teradata MDS DDL Gateway consists of one client, one server, and one or more integrity server processes that keep the metadata in the Teradata MDS repository synchronized with Teradata. Teradata MDS can track changes to multiple Teradata systems. The Teradata MDS DDL Gateway is also responsible for maintaining the audit trail of the DIM changes for each processed DDL statement. If the Audit Log Flag is set to On, an entry is inserted into the audit trail for each update to the DIM. The Teradata MDS DDL Gateway can be installed on an application node of the Teradata Database system or on a separate Windows or Linux machine. Only one instance of the Teradata MDS DDL Gateway is allowed. The Teradata MDS Action Processor polls the Audit Log for expired entries and purges them. The Teradata MDS Action Processor also sends messages to the Teradata MDS DDL Gateway to initiate scheduled recovery. The Teradata MDS Action Processor runs on Windows or Linux. Only one Teradata MDS Action Processor can be run. The Action Poll Rate defined in the MetaManager System-Wide Parameters defines how often the Teradata MDS Action Processor rereads the Teradata Database system settings to pick up changes to the Audit Flag, Audit Trail Expiration Days, and DIM Update Recovery 36 Teradata Tools and Utilities for SUSE Linux Installation Guide

37 Chapter 3 Install New Software Installing Teradata Tools and Utilities Feature MDS Recovery Tables Database Connection Information DDL Gateway User Accounts Description Schedule for each Teradata Database system object. The default setting for the Action Poll Rate is 5 minutes. The Action Poll Rate can be increased to a maximum of 1440 minutes (24 hours). The Teradata MDS Action Processor polls the Teradata MDS Audit Trail every 24 hours at 1:30 a.m. local time to remove expired entries in the Audit Trail. A Recovery Schedule is configured in Teradata MDS for each Teradata Database system. The Teradata MDS Action Processor monitors the schedule times for each Teradata Database system and sends a message to the Teradata MDS DDL Gateway server when scheduled recovery is to be performed on each system. For the Automatic DIM update feature to be enabled on each Teradata Database system loaded into the Teradata MDS repository, a Teradata MDS Recovery Table must exist on each of the Teradata Database systems. Teradata Database systems automatically contain a Teradata MDS Gateway Recovery Table. The table has a fixed name (mdsrecoverytbl) and location (DBC). When creating a Teradata Database system with Automatic DIM Updates enabled, a DSN, user name, and password for the Teradata MDS DDL Gateway to use to connect to the system are specified in MetaManager. The Gateway Server process uses these settings to resynchronize a database during recovery and to access the Teradata MDS Recovery Table. The Gateway Integrity Servers use these settings to connect to the system to get information from the DBC tables. The Teradata MDS DDL Gateway uses the Teradata user name specified in mdsconfig to connect to the Teradata MDS repository. The Gateway uses the Teradata user name specified in the MetaManager system configuration to connect to other Teradata Database systems. Out of Sync Recovery The Teradata Meta Data Services (MDS) repository can be out of sync with a Teradata Database System for the following reasons: A Teradata Database System, Relay Services Gateway (RSG), and/or Teradata MDS Data Definition Language (DDL) Gateway reset occurs. An error occurs and an Integrity Server cannot commit a transaction to the repository. The Teradata MDS DDL Gateway goes down and does not come back up right away. In this case Teradata is processing DDLs and not forwarding them on to Teradata MDS, but is writing the database names to the Teradata MDS Recovery Table. The Integrity Servers have a backlog of transactions that have not yet been processed. When the Automatic DIM Update feature is enabled, the task of keeping track of the DDL Transactions is divided among the three components: Teradata Database System, RSG, and DDL Gateway Server. Feature Teradata Database System Description When the Teradata MDS DDL Gateway is down, the Teradata Database System processes DDL statements, but writes the names of all Affected databases to the Teradata MDS Recovery Table. There is one Teradata MDS Recovery Table for each Teradata Database System. Teradata Tools and Utilities for SUSE Linux Installation Guide 37

38 Chapter 3 Install New Software Installing Teradata Tools and Utilities Feature Description When the Teradata MDS DDL Gateway Server comes up, if the Recovery on Startup flag is checked, it reads the Teradata MDS Recovery Table and resynchronizes the repository for each database name listed in the table. RSG DDL Gateway Server The RSG keeps track of the in-progress Teradata DDL transactions. These are DDLs that the Gateway Server has not yet captured in its log and has not responded to Teradata to complete the transaction. When the RSG detects that the Teradata MDS DDL Gateway has gone down or receives a reset message from the Teradata MDS DDL Gateway Server, the RSG aborts the in-progress transactions with the Teradata Database System. The Teradata MDS DDL Gateway Server keeps track of the database names of all DDL transactions for which it has received messages. It tracks the transaction in a backlog list and in a log file. The log is combined with the Teradata MDS Recovery Table to resynchronize the repository. Only databases that are out of sync are resynchronized during recovery. The DDL Gateway Server performs recovery: On startup of the DDL Gateway On startup, the Gateway Server looks in the Teradata MDS Recovery Table and in its own log to determine which databases need recovery. If the Teradata Database System is configured in Teradata MDS to have the Recovery On Startup flag enabled, the Gateway begins recovery for that system. If the flag is not set, recovery is deferred until the scheduled time. When the DDL Gateway receives a Recover now message from the Teradata MDS Action Processor Scheduled recovery only occurs once per day for each Teradata Database System based on the schedule configured for that system in Teradata MDS. The schedule configuration also specifies the days of the week to perform scheduled recovery. When performing recover, the Gateway Server: 1. Sends a message to the Teradata Database to stop sending DDLs to RSG and to log Affected databases in the Teradata MDS Recovery Table 2. Reads and deletes Teradata MDS Recovery Table entries, reads the backlog list, and compiles a list of database names to resynchronize 3. Calls the metaload utility to resynchronize each database name 4. Reads and deletes the Teradata MDS Recovery Table again to resynchronize databases that may have been affected by DDLs during the resynchronization process 5. Sends a message to the Teradata Database to start sending DDLs to RSG Installing the DIM Update Server Software Installing the Teradata Meta Data Services Action Processor Prerequisite: The Teradata Meta Data Services (MDS) Core (mdsbase) package must be installed on the designated DIM Update Server before you install the Teradata MDS Action Processor package. 1 Use the PUT utility or mdsapinstall command to install the Teradata MDS Action Processor package (mdsap) on the DIM Update Server. 38 Teradata Tools and Utilities for SUSE Linux Installation Guide

39 Chapter 3 Install New Software Installing Teradata Tools and Utilities The Teradata MDS Action Processor software supports scheduled recovery and Audit logging. The Teradata MDS Action Processor files are installed in the <MDS installation directory>/bin directory. The <MDS installation directory> is /opt/teradata/ mds or a nonstandard location if that option was selected when the MDS base package was installed. The Teradata MDS Action Processor starts automatically at system startup. You can also start it with the /etc/init.d/mdsap start script. Installing the Teradata Meta Data Services Data Definition Language Gateway Prerequisite: The Teradata Meta Data Services (MDS) Core (mdsbase) package must be installed on the designated DIM Update Server before you install the Teradata MDS Data Definition Language (DDL) Gateway package. 1 Use the PUT utility or mdsgwyinstall command to install the Teradata MDS DDL Gateway package (mdsgwy) on the DIM Update Server. The Teradata MDS DDL Gateway software is installed in the <MDS installation directory>/gateway directory. The MDS installation directory is /opt/teradata/ mds or a nonstandard location if that option was selected when the MDS base package was installed. The Teradata MDS DDL Gateway is not started at installation. The next time the system is started, the DDL Gateway starts automatically. You can start it manually with the following command: /etc/init.d/mdsgwy start Note: On initial installation, the status of the system may be Down and a message similar to the following may be sent to the mds log: 09/18/11 15:31:43 PID CGwaySocket::Get HostByAddr( ) returns SMP001-4 The first name specified for a node in the /etc/hosts file is the primary node name for the node. This is the name that must be used for a node defined for a system in the MetaManager GUI. Correct the etc/hosts file or the MetaManager node names. The mdsgwy package automatically increases the following system tunable parameters in /etc/sysctl.conf to these values: kernel.msgmnb= kernel.msgmni=1000 kernel.msgmax=32767 The following services are added to the /etc/services file on your designated DIM Update Server. TxServer 56969/tcp # MDS Gateway Server RSiMsg 56970/tcp # RSG Server The services file changes are done as a consequence of installing mdsgwy. They may have been previously done as a consequence of installing mdsap or RSG. Teradata Tools and Utilities for SUSE Linux Installation Guide 39

40 Chapter 3 Install New Software Installing Teradata Tools and Utilities Configuring the odbc.ini File The Teradata Meta Data Services (MDS) Action Processor (mdsap) or Teradata MDS DDL Gateway (mdsgwy) package installs a default odbc.ini file in the <MDS installation directory>/msg_txt directory. The MDS installation directory is /opt/teradata/mds or a nonstandard location if that option was selected when the Teradata MDS base package was installed. If the ODBCINI environment variable is set, the package installation does not change the environment variable. The Teradata MDS Action Processor and Teradata MDS DDL Gateway use the odbc.ini file specified in the environment variable. If the ODBCINI environment variable is not set, the default odbc.ini file is used. 1 Edit the odbc.ini file. a In the [ODBC Data Sources] section, add a line with the DSN information for the Teradata MDS repository system and all other systems being tracked by Teradata MDS. The line has the form: <DSN name x>=tdata.so [ODBC Data Sources] MDSDSN=tdata.so default=tdata.so SYSTEMIDSN=tdata.so b For each DSN line added to the [ODBC Data Sources] section, add a new section with the following information: [ <DSN name x>] Driver=/usr/odbc/drivers/tdata.so Description= DBCName=<system name> LastUser= Username= Password= Database= DefaultDatabase= Relay Services Gateway Overview Every node of every Teradata Database System that is to be loaded into the Teradata Meta Data Services (MDS) repository and tracked with the Automatic DIM Update feature must have the Relay Services Gateway (RSG) installed and the RSG vprocs configured and running. The RSG package must be installed on the appropriate nodes. Edit the RSG configuration files to indicate where the Teradata MDS DDL Gateway is installed and which node is the RSG master node. Create and configure the RSG vprocs. 40 Teradata Tools and Utilities for SUSE Linux Installation Guide

41 Chapter 3 Install New Software Installing Teradata Tools and Utilities Installing the Relay Services Gateway 1 Before the initial installation of the Relay Services Gateway (RSG), use the PUT utility to add the RSG vprocs to the appropriate nodes. The RSG vproc on the RSG master node should have id Secondary RSG nodes should use smaller RSG vproc ids. Note: The vconfig.txt file created by PUT also contains RSG vproc information, including whether the vproc is movable or not. It should always say the vproc is not movable. The RSG vproc type is defined in the DBS startup.txt file and is 4. The RSG partition is It is strongly suggested that a TPA shutdown be done prior to installing RSG: tpareset x stop If a TPA shutdown is not done at this time, it must remain up throughout the RSG installation. If a TPA shutdown occurs during the RSG installation, and if the ctl utility shows that the Running RSG version is a version that is no longer on the system, ctl must be used to set the Desired RSG to the last installed RSG version or blank it out. The next time a TPA start or reset is done, the system automatically switches to the Desired RSG version or, if it is blank, the last installed RSG version. 3 Run rsginstall on each node or use the Additional Packages menu in the PUT utility to update all nodes simultaneously. The RSG package is installed in the following directory on each node: <Teradata installation directory>/rsg/<version> where <version> is the package version (for example, ). The following services are added to the /etc/services file on the node when the RSG packages are installed. TxServer 56969/tcp # MDS Gateway Server RSiMsg 56970/tcp # RSG Server The services file changes may or may not be done as a consequence of installing mdsgwy. The RSG package, if installed first, will make the changes. Configuring the Relay Services Gateway 1 Edit the Relay Services Gateway (RSG) configuration file, <tdconfig directory>/ rsg/rsg.cfg, of each node to indicate where the Teradata Meta Data Services (MDS) DDL Gateway is installed and which node is the RSG master node: MDSGWYNODE=<MDS Gateway node name> RSGMASTERNODE=<RSG master node name> DEBUGTRACE=<optional; can have value ON, OFF, or REPLACE> REPLACE indicates that the old RSG log file will be removed and a new log file created at the next TPA reset. If the MDSGWYNODE or the RSGMASTERNODE value is NULL, RSG keeps trying to read the RSG configuration file, sleeping between tries. Teradata Tools and Utilities for SUSE Linux Installation Guide 41

42 Chapter 3 Install New Software Installing Teradata Tools and Utilities 2 If the tdinfo utility indicates that the RSG vproc is not online, run the vprocmanager utility to set it offline and then online as follows: set xxxx offline set xxxx online where xxxx is the ID of the vproc. Repeat these steps for each RSG vproc. Note: The vprocmanager utility cannot be used to set the state for Hot Swap Nodes. 3 Run the dbscontrol utility and turn on the MDS is Enabled flag: modify general 38=TRUE write quit 4 Restart the Teradata Database. Starting and Stopping the Relay Services Gateway 1 Run the dbscontrol utility to verify that the MDS is Enabled flag is set. When the MDS is Enabled flag is set in dbscontrol, the Relay Services Gateway (RSG) starts automatically with the Teradata Database. 2 Display the MDS is Enabled flag: display general View /var/log/messages to see if RSG has been started. If DEBUGTRACE is set to ON, full RSG logging takes place. If DEBUGTRACE is set to OFF, minimal logging occurs. The REPLACE option indicates that the old RSG log file will be removed and a new log file created at the next TPA reset. The files are located in <tdconfig directory>/rsg. There is one set of files per node. 3 If the tdinfo utility indicates that the RSG vproc is not online, run the vprocmanager utility to set it online: set xxxx online where xxxx is the ID of the RSG vproc on one TPA node. Repeat these steps for the other TPA nodes. The RSG vproc IDs are 9215, 9214, 9213, and so on. The RSG is stopped when the Teradata Database is stopped. Configuring the Automatic DIM Update with MetaManager Adding a Teradata Database System 1 To add a Teradata Database System, see, Administer MDS with MetaManager in B A, Teradata Meta Data Services Administrator Guide. 42 Teradata Tools and Utilities for SUSE Linux Installation Guide

43 Chapter 3 Install New Software Installing Teradata Tools and Utilities Adding Teradata Nodes Nodes may be added to a system, edited, or deleted. A node definition consists of a name and the node status (Up or Down). 1 In MetaManager, select a system. 2 Go to System > Add Node. The Add Node dialog box appears. 3 In the Add Node dialog box, enter the node name, choose the node status, and click OK. Node names are not arbitrary. Each name must be the primary name (first name after the IP address in an /etc/hosts file) for its IP address and not an alias. Node names must be unique within the enterprise, not just within the Teradata Database System. 4 A dialog box asks if you want to add another node; click Yes or No. When you are finished adding nodes, they appear in MetaManager. The Automatic DIM Update feature requires that Teradata nodes on the Teradata Database System be configured. Editing a Teradata Node in MetaManager 1 In MetaManager, right-click the node to edit to display the shortcut menu. 2 Click Edit. 3 In the Edit node dialog box, set the Node Status to Up or Down, then click OK. If the node on the Teradata Database System is to be removed for an extended period, set the status of the node to Down. This prevents DDL Gateway from sending messages to the RSG on the node when it is unavailable. Loading Databases Teradata Meta Data Services (MDS) loads data dictionary information for each of the selected databases into the Teradata MDS repository. The actual data in the database tables is not loaded. The following table shows the options used to load databases into the Teradata MDS repository. These options determine which databases the DDL Gateway keeps in sync. The difference is in how the DDL Gateway handles newly created users and databases in the Teradata Database System. Load All Selected Description The DDL Gateway automatically adds new databases and users created in the Teradata Database System to the MDS repository. All indicates that the MDS repository contains all databases in the Teradata Database System. The DDL Gateway does not add new databases and users created in the Teradata Database System to the MDS repository. The DDL Gateway maintains only those databases selectively loaded into the Teradata MDS repository. If you use this option, and later use the Load All option, the Load flag is changed to Load All. Teradata Tools and Utilities for SUSE Linux Installation Guide 43

44 Chapter 3 Install New Software Installing Teradata Tools and Utilities Load All but Selected Description The DDL Gateway automatically adds new databases and users created in the Teradata Database System to the MDS repository. However, it maintains the list of those databases that were excluded on the initial load and ignores all DDLs for those databases. Databases that were originally loaded, but later unloaded are considered excluded databases. For all other DDLs, the DDL Gateway updates the repository for loaded databases and ignores DDL for databases that are not loaded into the repository. If databases are not loaded for a Teradata Database System, the DDL Gateway does not track that system even if Automatic DIM Update is enabled for the system. Before enabling Automatic DIM Update, load all databases to be maintained. If there is a long time between the initial load of the databases and when Automatic DIM Update is enabled, resynchronize all databases before enabling it. See Administer MDS with MetaManager in B A, Teradata Meta Data Services Administrator Guide. Enabling Automatic Database Information Metamodel Update 1 In MetaManager, right-click the system that will have Automatic DIM Update enabled. 2 Click DIM Update. 3 In the DIM Update dialog box, select the Enable DIM Update check box, then click OK. 4 In the Enable DIM Update dialog box, select the Recovery on Startup check box or define the recovery schedule by clicking Schedule, then click OK. The Teradata MDS Recovery Table keeps track of the database name for each DDL that occurs while the DDL Gateway is down. If RSG detects that the DDL Gateway is down, RSG notifies Teradata to begin writing to the Teradata MDS Recovery Table. When the DDL Gateway comes back up, it reads the Teradata MDS Recovery Table and marks each of the databases in the Teradata MDS Recovery Table as out of sync. The DDL Gateway resynchronizes each database if Recovery on Startup was selected or at a scheduled recovery time if that was selected. The recovery database is always DBC. The Teradata MDS Recovery Table is mdsrecoverytbl. The Teradata user specified in the System Object must have SELECT and DELETE privileges to the Teradata MDS Recovery Table. Checking DIM Status with MetaManager 1 From MetaManager, go to System > Database Systems. 2 In the Teradata Meta Data Services Administration window, highlight a system name and click Database Administration. The Teradata Meta Data Services Administration dialog box appears. To go directly to the Teradata Meta Data Services Administration dialog box, from the MetaManager main window, right-click on the system with database(s) to administer, and click Database Administration. 3 Click the Dim Update Status tab to determine if any databases are marked out of sync by the DDL Gateway. 44 Teradata Tools and Utilities for SUSE Linux Installation Guide

45 Chapter 3 Install New Software Installing Teradata Tools and Utilities The DIM Update Status tab is disabled if Automatic DIM Update has not been enabled for your system. The DIM Update Status window shows the following: Name System Name DIM Update Status Database Out of Sync Refresh List Sync Now Description System chosen DIM Update status of the system The status codes are: UP: DIM Update is up and tracking changes to the system DOWN: DDL Gateway has not yet notified the Teradata Database System to begin sending DDLs STOPPED: DIM Update is disabled and not tracking changes to the system RESYNC: Gateway is currently running recovery (scheduled or on startup) UNKNOWN: MetaManager could not contact the DDL Gateway to get the status or the DDL Gateway does not know about the system List of database names the DDL Gateway has marked out of sync, including those that were in the MDS Recovery Table Updates the display Sends a message to the DDL Gateway to immediately begin recovery to synchronize the out of sync databases Starting and Stopping the Data Definition Language Gateway The Data Definition Language (DDL) Gateway is automatically started as a service at system boot and stops at system shutdown. The following table shows the names of the DDL Gateway programs. Gateway Component Gateway Server Gateway Client Integrity Servers Linux Program Name gwserver gwclient iserver 1 To manually start the DDL Gateway, type: /etc/init.d/mdsgwy start 2 To manually stop the DDL Gateway, type: /etc/init.d/mdsgwy stop Starting and Stopping the Teradata Meta Data Services Action Processor The Teradata Meta Data Services (MDS) Action Processor is automatically started as a service at system boot and stops at system shutdown. The name of the Teradata MDS Action Processor program is metaaction. 1 To manually start the Teradata MDS Action Processor, type: Teradata Tools and Utilities for SUSE Linux Installation Guide 45

46 Chapter 3 Install New Software Installing Teradata Tools and Utilities /etc/init.d/mdsap start 2 To manually stop the Teradata MDS Action Processor, type: /etc/init.d/mdsap stop Teradata Developer Exchange The Teradata Developer Exchange Downloads page contains software that is not included on Teradata Tools and Utilities media or is released more frequently than the Teradata Tools and Utilities collection of applications. Products Available from Teradata Developer Exchange Note: Products and versions of them available from Teradata Developer Exchange are subject to change. This list is limited to Teradata Tools and Utilities applications. Table 1: Connectivity Product Teradata Call-Level Interface version 2 for IBM AIX Teradata Call-Level Interface version 2 for Windows Teradata Call-Level Interface version 2 for Solaris Teradata Call-Level Interface version 2 for Linux Teradata Call-Level Interface version 2 for HP-UX Teradata JDBC Driver Teradata JMS Universal Connector.NET Data Provider for Teradata ODBC Driver for Teradata for HP-UX ODBC Driver for Teradata for Linux ODBC Driver for Teradata for IBM AIX ODBC Driver for Teradata for Solaris ODBC Driver for Teradata for Windows OLE DB Provider for Teradata Table 2: Tools Product Teradata SQL Assistant Java Edition Teradata Plug-in for Eclipse Downloading a Product from the Teradata Developer Exchange 1 Go to Teradata Developer Exchange. 46 Teradata Tools and Utilities for SUSE Linux Installation Guide

47 Chapter 3 Install New Software Installing Teradata Tools and Utilities The Teradata Developer Exchange DOWNLOADS page with a list of selectable products appears. 2 Click the product name or the platform next to the product name. The list of available downloads by software version and processor or platform appears. 3 Click the software package or text file to download. 4 You may be asked to enter a user name and password or to create a user name and password. 5 Read the License Agreement, then click I Agree. A page with a link to the Download file appears. 6 If a readme file is included, click on the readme file link and read and print any special download or installation instructions before continuing. 7 Return to the DOWNLOADS page. 8 Click the package to download. This is typically a.tar,.tar.gz, or.zip file. 9 Click Save. 10 Select a location where to save the file and click Save. The file is saved to the location chosen. Installing Products Downloaded from Teradata Developer Exchange 1 Go to the location where the.zip file containing the required *.tar.gz files and associated files was saved. 2 Read the *.txt readme file to determine further installation instructions. 3 Uncompress and untar the files and dependent product packages into a folder for the setup packages. Typically the readme instructions describe how to uncompress and untar the files and dependent product packages into a folder for the setup packages. For example, uncompress and untar the cliv2 package with: gunzip cliv2_linux_x8664_ tar.gz tar xvf 4 Remove the previous software: rpm -e 5 Install the dependencies in order, and then install the product: rpm [INSERT Tdicu] rpm [INSERT TeradGSS] rpm -ivh --nodeps cliv2_ x86_64.rpm Teradata Tools and Utilities for SUSE Linux Installation Guide 47

48 Chapter 3 Install New Software Installing Teradata Tools and Utilities Teradata Software Server To ensure the highest quality and best performance of Teradata Tools and Utilities products, download the most recent critical post-production updates from Teradata Software Server. Downloading Patches To ensure the highest quality and best performance of Teradata Tools and Utilities products, the most recent critical post-production updates should be installed from the Teradata Software Server. 1 Log on to Teradata At Your Service. 2 Click Downloads. 3 In the Teradata Software Server dialog box, click Teradata Client. 4 In the Client Help dialog box, click the desired platform. 5 In the Teradata Client Released Software dialog box, select the software base and the platform base, then click Submit. 6 In the Client Patches dialog box, select the check boxes for the software patches to download. 7 Select the Download Type and the Download Readme Files (if desired), enter your User Name and , then click Submit. 8 Click Download. 9 Click Save. 10 Specify to save-to location and click Save to start the download. Installing Downloaded Patches 1 Go to the location where the *.zip file containing the required *.tar.gz files and associated files was saved. 2 Read the *.txt readme file to determine further installation instructions. 3 Uncompress and untar the files and dependent product packages into a folder for the setup packages. Typically the readme instructions describe how to uncompress and untar the files and dependent product packages into a folder for the setup packages. For example, uncompress and untar the cliv2 package with: gunzip cliv2_linux_x8664_ tar.gz tar xvf 4 Remove the previous software: rpm -e 5 Install the dependencies in order, and then install the product. rpm [INSERT Tdicu] rpm [INSERT TeradGSS] rpm -ivh --nodeps cliv2_ x86_64.rpm 48 Teradata Tools and Utilities for SUSE Linux Installation Guide

49 Chapter 3 Install New Software Installing Teradata Tools and Utilities 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 /opt/teradata/client/14.00/sample, using the following command: cd /opt/teradata/client/14.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 B A, Teradata Call- Level Interface Version 2 Reference for Network-Attached Systems, Appendix D. Teradata Tools and Utilities for SUSE Linux Installation Guide 49

50 Chapter 3 Install New Software Installing Teradata Tools and Utilities 50 Teradata Tools and Utilities for SUSE Linux Installation Guide

51 CHAPTER 4 Configure New Software Creating Environment Variables 1 Include the installation directory path where Teradata Call-Level Interface version 2 software files are located in LD_LIBRARY_PATH. 2 Bash and Bourne shell users, use the following command to add the installation directory path to the LD_LIBRARY_PATH: 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: setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH":<installation directory>" 4 Export the LD_LIBRARY_PATH environment variable for all Teradata Tools and Utilities products. Overview of Configuring ODBC Driver for Teradata After installing the ODBC Driver for Teradata, you may need to configure the following: Environment variables The odbc.ini template ODBC data sources For complete configuration information on the ODBC Driver for Teradata, see B A, ODBC Driver for Teradata User Guide. 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: Teradata Tools and Utilities for SUSE Linux Installation Guide 51

52 Chapter 4 Configure New Software About Configuring Teradata Parallel Transporter Shared memory parameters: shmmax and shmmni Semaphore parameters: semmni and semmns The following environment variables may also need to be modified: TWB_ROOT PATH LD_LIBRARY_PATH NLSPATH Editing twbcfg.ini After the Teradata Parallel Transporter Base package is installed, the configuration file, $TWB_ROOT/twbcfg.ini can be edited to change the default directory for checkpoint and logs. The $TWB_ROOT environment variable contains the installation directory for Teradata Parallel Transporter. 1 Log on as the root user. 2 Use a text editor to edit the configuration file to change the checkpoint or logs directory. For example, if the logs directory is full, then you should change the logs directory to another directory with free disk space. Note: No kernel rebuild or reboot is required after making the changes in the configuration file. Selecting Checkpoint and Log Directories in the Configuration File The configuration file contains parameters that determine the default behavior for Teradata Parallel Transporter Base, such as default checkpoint and log directories. These must be selected. 1 Edit the configuration file and specify the Teradata Parallel Transporter default directory and default log directory. 'CheckpointDirectory='/opt/teradata/client/14.00/tbuild/ checkpoint' CheckpointDirectory refers to the directory that contains the checkpoint files for Teradata Parallel Transporter jobs. 'LogDirectory='/opt/teradata/client/14.00/tbuild/logs' LogDirectory refers to the directory that contains the binary logs for Teradata Parallel Transporter jobs. Each Teradata Parallel Transporter job creates a job log in the jobs directory. Refer to B A, Teradata Parallel Transporter Reference on how to read the job log. Setting Shared Memory Parameters 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 52 Teradata Tools and Utilities for SUSE Linux Installation Guide

53 Chapter 4 Configure New Software About Configuring Teradata Parallel Transporter 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 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 The default semmns parameter value is 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 Updating Environment Variables Prerequisite: Note: You must have root access to execute the listed commands. Teradata Tools and Utilities for SUSE Linux Installation Guide 53

54 Chapter 4 Configure New Software About Configuring Teradata Parallel Transporter 1 If CLIv2 was installed on SUSE Linux, set up the environment variables for those products. Include the installation directory path where CLIv2 software files are located in LD_LIBRARY_PATH. Bash and Bourne shell users, use this command to add the installation directory path to the LD_LIBRARY_PATH: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<installation directory>; export LD_LIBRARY_PATH C shell users, use this command to add the installation directory path to the LD_LIBRARY_PATH: setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH":<installation directory>" 2 On SUSE Linux operating systems, export the LD_LIBARY_PATH environment variable for all Teradata Tools and Utilities products. export LD_LIBRARY_PATH=/<installation directory> 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 with "777" permissions: 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. 54 Teradata Tools and Utilities for SUSE Linux Installation Guide

55 CHAPTER 5 Restart the Client Computer Restarting the Client Computer 1 Reboot if the client installation requires it. In most cases, the client computer does not require a restart. Note: Teradata Parallel Transporter adds some kernel modifications that require a computer restart. Teradata Tools and Utilities for SUSE Linux Installation Guide 55

56 Chapter 5 Restart the Client Computer Restarting the Client Computer 56 Teradata Tools and Utilities for SUSE Linux Installation Guide

57 CHAPTER 6 Verify 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 Check that the product files were loaded in the proper folders 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 B A, Basic Teradata Query Reference 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 A screen similar to the following appears: Teradata BTEQ for UNIX5. Copyright , 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, a screen similar to the following appears: *** Logon successfully completed. *** Transaction Semantics are BTET. Teradata Tools and Utilities for SUSE Linux Installation Guide 57

58 Chapter 6 Verify the Complete Installation About Verifying the Installation *** Character Set Name is 'ASCII'. *** Total elapsed time was 1 second. BTEQ -- Enter your DBC/SQL request or BTEQ command: 6 Submit a sample Teradata SQL query: SELECT time; If the test passes, a screen similar to the following appears. BTEQ select time output: *** Query completed. One row found. One column returned. *** Total elapsed time was 1 second. Time :09:11 7 Log off the Teradata Database and exit BTEQ. 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 makesamp.3000 makefile with the correct directory paths to the include files. 2 Execute the makefile to create the executable module clisamp: make -f makesamp Change the mode of the executable to run: chmod +x clisamp 4 Run the sample program using one of the following commands: Run the sample program using the default logon information (dbc/ systemfe,service): clisamp Show help for the sample program: clisamp -h Run the sample program using a user-provided input string: clisamp slugger/dbc,dbc where TDPID= slugger, user=dbc, and password=dbc. 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 MTDP version is MOSIOS version is Teradata Tools and Utilities for SUSE Linux Installation Guide

59 Chapter 6 Verify the Complete Installation About Verifying the Installation MOSIDEP version is OSERR version is Logging on to --> dbc/systemfe,service writing out to --> CLISAMP.DAT submitting --> select* from dbc.sessioninfo; writing out to --> CLISAMP.DAT Logging off. Basic Teradata Query Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for a file that has been installed in the default directory /opt/teradata/client/<version>/ bin. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/bin /usr/include /opt/teradata/client/<version>/bin /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample Files bteq* btnfyext.h* bteq btnfyext.c mkbtnfyext.linux btnfyext.h Named Pipe Access Module Files and Directories An asterisk (*) after a name in the following table indicates that it is a "softlink" for files that have been moved to the /opt/teradata/client/<version>/lib directory. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/lib /opt/teradata/client/<version>/lib Files np_axsmod.so* np_axsmod.so ODBC Driver for Teradata Files and Directories The default directory for the ODBC Driver for Teradata is opt/teradata/client/ ODBC_32 opt/teradata/client/odbc_32 or /opt/teradata/client/odbc_64, depending on the platform. An asterisk (*) after a name in the following table indicates that it is a "softlink" for files that have been moved to the /opt/teradata/client/<version>/lib directory. Teradata Tools and Utilities for SUSE Linux Installation Guide 59

60 Chapter 6 Verify the Complete Installation About Verifying the Installation Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/lib /usr/lib /usr/lib /usr/lib <installation directory> <installation directory> <installation directory> /lib /bin /include /include /include /include /include /include /include /lib /<install dir>/lib /<install dir>/lib /<install dir>/lib /<install dir>/lib /<install dir>/lib /<install dir>/lib /<install dir>/lib /<install dir>/lib /opt/teradata/client/<version>/odbc_32/help/man/man5 or Files libivicu24.so* libtdsso.so* libodbcinst.so* libtdparse.so* README odbc.ini odbcinst.ini tdata.so tdxwinapp odbcinst.h sql.h sqlext.h sqltypes.h sqlucode.h sqlunx.h tdsql.h libodbc.so libivicu24.so libodbcinst.so libtdparse.so odbccurs.so odbctrac.so tdconndlg.so vscnctdlg.so tdata.so tdata.man /opt/teradata/client/<version>/odbc_64/msg/man/man5 /opt/teradata/client/odbc_32/locale/en_us/lc_messages or odbc.m /opt/teradata/client/odbc_64/locale/en_us/lc_messages 60 Teradata Tools and Utilities for SUSE Linux Installation Guide

61 Chapter 6 Verify the Complete Installation About Verifying the Installation Directory /<install dir>/samples/c /<install dir>/samples/c /<install dir>/samples/c /<install dir>/samples/c /<install dir>/samples/c /<install dir>/samples/c++ /<install dir>/samples/c++ /<install dir>/samples/c++ /<install dir>/samples/c++ /<install dir>/samples/c++ /opt/teradata/client/<version>/odbc_32/msg or Files Makefile adhoc adhoc.c common.includes error.c Makefile adhoc adhoc.cpp common.includes error.cpp tdodbc.cat /opt/teradata/client/<version>/odbc_64/msg Shared Common Components for Internationalization for Teradata Files and Directories Directory /usr/lib /usr/lib /usr/lib /usr/lib /usr/lib /usr/lib /usr/lib /usr/lib /usr/lib Files libicudatatd.so.46 -> /opt/teradata/client/<version>/tdicu/ lib/libicudatatd.so.46.0 libicui18ntd.so.46 -> /opt/teradata/client/<version>/tdicu/ lib/libicui18ntd.so.46.0 libicuuctd.so.46 -> /opt/teradata/client/<version>/tdicu/ lib/libicuuctd.so.46.0 libicuiotd.so.46 -> /opt/teradata/client/<version>/tdicu/ lib/libicuiotd.so.46.0 libiculxtd46.so -> /opt/teradata/client/<version>/tdicu/lib/ libiculxtd.so.46.0 libiculetd46.so -> /opt/teradata/client/<version>/tdicu/lib/ libiculetd.so.46.0 libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib/ libicudatatd.so.46.0 libicudatatd.so -> /opt/teradata/client/<version>/tdicu/lib/ libicudatatd.so.46.0 libicuuctd.so -> /opt/teradata/client/<version>/tdicu/lib/ libicuuctd.so.46.0 Teradata Tools and Utilities for SUSE Linux Installation Guide 61

62 Chapter 6 Verify the Complete Installation About Verifying the Installation Directory /usr/lib /usr/lib /usr/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib /opt/teradata/client/ <version>/tdicu/lib Files libicuiotd.so -> /opt/teradata/client/<version>/tdicu/lib/ libicuiotd.so.46.0 libiculxtd.so -> /opt/teradata/client/<version>/tdicu/lib/ libiculxtd.so.46.0 libiculetd.so -> /opt/teradata/client/<version>/tdicu/lib/ libiculetd.so.46.0 libicudatatd.so.46 -> libicudatatd.so.46.0 libicui18ntd.so.46 -> libicui18ntd.so.46.0 libicuuctd.so.46 -> libicuuctd.so.46.0 libicuiotd.so.46 -> libicuiotd.so.46.0 libicudatatd.so.46.0 libicui18ntd.so.46.0 libicuuctd.so.46.0 libicuiotd.so.46.0 libiculetd.so.46.0 libiculxtd.so.46.0 libiculetd.so.46 -> libiculetd.so.46.0 libiculxtd.so.46 -> libiculxtd.so.46.0 libicudatatd.so -> libicudatatd.so.46.0 libicui18ntd.so -> libicui18ntd.so.46.0 libicuiotd.so -> libicuiotd.so.46.0 libiculetd.so -> libiculetd.so.46.0 libiculxtd.so -> libiculxtd.so Teradata Tools and Utilities for SUSE Linux Installation Guide

63 Chapter 6 Verify the Complete Installation About Verifying the Installation Directory /opt/teradata/client/ <version>/tdicu/lib /usr/lib64 /usr/lib64 /usr/lib64 /usr/lib64 /usr/lib64 /usr/lib64 Files libicuuctd.so -> libicuuctd.so.46.0 libicudatatd.so -> /opt/teradata/client/<version>/tdicu/ lib_64/libicudatatd46.0.so libicuuctd.so -> /opt/teradata/client/<version>/tdicu/ lib_64/libicuuctd46.0.so libiculxtd46.so -> /opt/teradata/client/<version>/tdicu/ lib_64/libiculxtd46.0.so libiculetd46.so -> /opt/teradata/client/<version>/tdicu/ lib_64/libiculetd46.0.so libicuiotd46.so -> /opt/teradata/client/<version>/tdicu/ lib_64/libicuiotd46.0.so libicui18ntd46.so -> /opt/teradata/client/<version>/tdicu/ lib_64/libicui18ntd46.0.so Teradata Archive/Recovery Utility Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for files that have been moved to the /opt/teradata/client/<version>/bin and the /opt/ teradata/client/<version>/bin64 directories. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. The Teradata Archive/Recovery Utility.rpm install package will now install both 32-bit and 64-bit versions of Teradata Archive/Recovery Utility on a 64-bit SUSE Linux machine at the same time. Even though the 64-bit version of Teradata Archive/Recovery Utility will be installed on a 64-bit Linux machine, the 32-bit version of Teradata Archive/Recovery Utility will still be the default version. To use the 64-bit version of Teradata Archive/Recovery Utility, you will have to explicitly identify that version of Teradata Archive/Recovery Utility by either accessing it through the softlink at /usr/bin64/arcmain or by specifying the full path to the 64-bit executable, for example: /opt/teradata/client/<version>/bin64/arcmain. Directory /usr/bin /usr/bin64 /opt/teradata/client/<version>/bin /opt/teradata/client/<version>/bin64 Files arcmain.exe* arcmain.exe* arcmain.exe arcmain.exe Teradata Tools and Utilities for SUSE Linux Installation Guide 63

64 Chapter 6 Verify the Complete Installation About Verifying the Installation Teradata C Preprocessor2 Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for files that have been moved to the /opt/teradata/client/<version>/bin, /opt/ teradata/client/<version>/bin64, /opt/teradata/client/<version>/lib or the /opt/teradata/client/<version>/lib64 directories. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/bin64 /usr/lib64 /opt/teradata/client/<version>/bin64 /opt/teradata/client/<version>/lib64 /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample Files ppcmain* lippruntim.so* ppcmain lippruntim.so LABSBTEQ PPCLB1 PPCLB2 PPCLB3 PPCLB4 PPCLB5 PPCLB6 PPCLB7 PPCLB8 PPCLB9 Teradata Call-Level Interface version 2 Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for files that have been moved to either the /opt/teradata/client/<version>/include or the /opt/teradata/client/<version>/lib directory. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory SUSE Linux 32-bit Files SUSE Linux 64-bit Files /usr/lib clispb.dat* clispb.dat* /usr/lib errmsg.cat* errmsg.cat* /usr/lib errmsg.txt* errmsg.txt* /usr/lib libcliv2.so* libcliv2.so* /usr/lib libtdusr.so* libtdusr.so* 64 Teradata Tools and Utilities for SUSE Linux Installation Guide

65 Chapter 6 Verify the Complete Installation About Verifying the Installation Directory SUSE Linux 32-bit Files SUSE Linux 64-bit Files /usr/include cliv2if.h* cliv2if.h* /usr/include coptypes.h* coptypes.h* /usr/include coperr.h* coperr.h* /usr/include dbca2px.h* dbca2px.h* /usr/include dbcarea.h* dbcarea.h* /usr/include dbcerr.h* dbcerr.h* /usr/include dbchqep.h* dbchqep.h* /usr/include parcel.h* parcel.h* /usr/lib/lib-i386 mosiif.h* mosiif.h* /usr/lib/lib-i386 libcliv2.so* libcliv2.so* /usr/lib/lib-i386 libtdusr.so* libtdusr.so* /opt/teradata/client/<version>/lib64 libcliv2.so libcliv2.so /opt/teradata/client/<version>/lib64 libtdusr.so libtdusr.so /opt/teradata/client/<version>/lib64 errmsg.cat errmsg.cat /opt/teradata/client/<version>/lib64 errmsg.txt errmsg.txt /opt/teradata/client/<version>/lib64 clispb.dat clispb.dat /opt/teradata/client/<version>/include coptypes.h coptypes.h /opt/teradata/client/<version>/include dbchqep.h dbchqep.h /opt/teradata/client/<version>/include dbca2px.h dbca2px.h /opt/teradata/client/<version>/include cliv2if.h cliv2if.h /opt/teradata/client/<version>/include coperr.h coperr.h /opt/teradata/client/<version>/include dbcarea.h dbcarea.h /opt/teradata/client/<version>/include parcel.h parcel.h /opt/teradata/client/<version>/include dbcerr.h dbcerr.h /opt/teradata/client/<version>/include mosiff.h mosiff.h /opt/teradata/client/<version>/lib errmsg.cat errmsg.cat /opt/teradata/client/<version>/lib errmsg.txt errmsg.txt /opt/teradata/client/<version>/lib clispb.dat clispb.dat /opt/teradata/client/<version>/sample CliLgn.Ex.c CliLgn.Ex.c /opt/teradata/client/<version>/sample CliPPS.c CliPPS.c /opt/teradata/client/<version>/sample clisamp.c clisamp.c /opt/teradata/client/<version>/sample makesamp.lx makesamp.lx /opt/teradata/client/<version>/sample makerdusr.lx makerdusr.lx Teradata Tools and Utilities for SUSE Linux Installation Guide 65

66 Chapter 6 Verify the Complete Installation About Verifying the Installation Teradata Data Connector Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for files that have been moved to either the /opt/teradata/client/<version>/include or the /opt/teradata/client/<version>/lib directory. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/lib /usr/include /usr/include /usr/include /opt/teradata/client/<version>/lib /opt/teradata/client/<version>/include /opt/teradata/client/<version>/include /opt/teradata/client/<version>/include Files libpm.so* pmdcomt.h* pmddamt.h* pmtypes.h* libpm.so pmdcomt.h pmddamt.h pmtypes.h Teradata FastExport Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for files that have been moved to the /opt/teradata/client/<version>/bin, /opt/ teradata/client/<version>/include, or the /opt/teradata/client/ <version>/sample directories. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/bin /usr/include /usr/sample /usr/sample /opt/teradata/client/<version>/bin /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample Files fexp* expnfyxt.h* expnfyxt.c* mkexpext.linux* fexp expnfyxt.h expnfyxt.c mkexpext.linux 66 Teradata Tools and Utilities for SUSE Linux Installation Guide

67 Chapter 6 Verify the Complete Installation About Verifying the Installation Teradata FastLoad Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for files that have been moved to the /opt/teradata/client/<version>/bin or the /opt/ teradata/client/<version>/sample directories. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/bin /usr/sample /usr/sample /usr/sample /opt/teradata/client/<version>/bin /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample Files fastload* blkexit.c* blkexitr.c* flnfyext.c* fastload blkexit.c blkexitr.c flnfyext.c Teradata Generic Security Services Files and Directories The files included with the Teradata Generic Security Services Client package can change from package to package, so there is no definitive filename list to verify. To verify the installation of the Teradata Generic Security Services Client packages, verify the existence of a file named version in the /usr/teragss/<architecture>/<version> directory, where: <version> is the version of software being verified. Directory /usr/teragss/suselinux-i386/<version> /usr/teragss/suselinux-i64/<version> /usr/teragss/suselinux-ia64/<version> Files /usr/teragss/suselinuxia64/<version> /usr/teragss/suselinuxi64/<version> /usr/teragss/suselinuxia64/<version> Teradata JDBC Driver Files and Directories File Type File Name Default Folder Executable terajdbc4.jar user selectable Sample samples.jar user selectable Security tdgssconfig.jar user selectable Teradata Tools and Utilities for SUSE Linux Installation Guide 67

68 Chapter 6 Verify the Complete Installation About Verifying the Installation Teradata MultiLoad Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for files that have been moved to the /opt/teradata/client/<version>/bin, /opt/ teradata/client/<version>/include, or the /opt/teradata/client/ <version>/sample directories. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/bin* /usr/include* /usr/sample* /usr/sample* /opt/teradata/client/<version>/bin /opt/teradata/client/<version>/include /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample Files mload* mldnfyxt.h* mldnfyxt.c* mkmldext.linux* mload mldnfyxt.h mldnfyxt.c mkmldext.linux Teradata Parallel Data Pump Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for files that have been moved to the /opt/teradata/client/<version>/bin and /opt/ teradata/client/<version>/lib directories. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/bin /usr/lib /usr/lib /opt/teradata/client/<version>/bin /opt/teradata/client/<version>/lib /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample /opt/teradata/client/<version>/sample Files tpumpexe* tdatpump.cfg* tdatpump.cfg tpumpexe* tldnfyxt.c makinmod.3000 tpumpimd.c tpumpar.csql Teradata Wallet Files and Directories An asterisk (*) after a filename in the following table indicates that it is a symbolic link. 68 Teradata Tools and Utilities for SUSE Linux Installation Guide

69 Chapter 6 Verify the Complete Installation About Verifying the Installation Directory /usr/bin /opt/teradata/client/<version>/tdwallet /opt/teradata/client/<version>/tdwallet/redhatlinux-i386 /opt/teradata/client/<version>/tdwallet/redhatlinux-i386 /opt/teradata/client/<version>/tdwallet/redhatlinux-i386 /opt/teradata/client/<version>/tdwallet/redhatlinux-i386 /opt/teradata/client/<version>/tdwallet/redhatlinux-x8664 /opt/teradata/client/<version>/tdwallet/redhatlinux-x8664 /opt/teradata/client/<version>/tdwallet/redhatlinux-x8664 /opt/teradata/client/<version>/tdwallet/redhatlinux-x8664 /opt/teradata/client/tdwallet/wallets Files tdwallet* config.xml libtdwallet.so tdwallet tdwalletdir* tdwhelper.exe libtdwallet.so tdwallet tdwalletdir* tdwalletdir* initially empty Teradata WebSphere MQ Access Module Files and Directories An asterisk (*) after a filename in the following table indicates that it is a "softlink" for files that have been moved to the /opt/teradata/client/<version>/lib and the /opt/ teradata/client/<version>/opt directories. Note: The silent install method works only if the default installation path is /opt, as shown in the above example. Directory /usr/lib /opt/teradata/client/<version>/lib Files libmqsc.so* libmqsc.so Teradata Tools and Utilities for SUSE Linux Installation Guide 69

70 Chapter 6 Verify the Complete Installation About Verifying the Installation 70 Teradata Tools and Utilities for SUSE Linux Installation Guide

71 CHAPTER 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database You can establish a connection to a Teradata Database with any of the following methods: From a GUI application From a command line driven application Programmatically Regardless of the connection method, you must check logon error messages. About Logon Procedures The logon string can be provided while logging on to a Teradata Database if the application allows it. If the application does not provide all the logon information, a Connect to Teradata Database dialog appears that allows entry of the missing logon information. If the Connect to Teradata Database dialog appears, all application-provided parameters are automatically entered into the dialog fields. You can change the value in any field. After entering required and optional logon information press Enter or click OK to continue logging on. The user logon exit routine can also be used to manipulate the fields of the Connect to Teradata Database dialog. Connecting to a Teradata Database from a GUI Application This procedure describes how to use the Connect to Teradata Database dialog box from a Graphical User Interface (GUI) application to connect to a Teradata Database. This procedure is for a typical application. See the product's User or Reference guide for specific information about an individual product. 1 If the application connecting to the Teradata Database has a Connectivity tab in the Tools options menu, select CLI or ODBC depending on the desired method for connecting to the Teradata Database. 2 Click Connect. 3 In the Connect to Teradata Database dialog box, select or enter the appropriate values for the Teradata Database. Teradata Tools and Utilities for SUSE Linux Installation Guide 71

72 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database Database Name (Required) This is the name of the Teradata Database to connect to. Enter a valid Teradata Database name, or select a Teradata Database name that was previously entered from the drop-down list. Authentication Mechanism (Optional) The authentication mechanism identifies the mechanism used for connections to the data source. Select the authentication mechanism specified by the client system administrator from the list of authentication mechanisms provided in the drop down list. Valid authentication mechanism values are: Empty - If no authentication mechanism is listed in the drop down list, or if the authentication mechanism selected is not supported, the mechanism used is the system default TD2 - Teradata 2 mechanism ldap - ldap mechanism KRB5 - Kerberos mechanism Other - user-defined mechanism Authentication Parameter (Optional) Enter the parameters required by the selected authentication mechanism. See your system administrator for these values. User Name (Optional) Select your user name from the drop down list or enter a valid user name. Password (Optional) Enter the password for the user name you selected. Default Database (Optional) Select the default Teradata Database for the session. Account String (Optional) Enter a new account string or select an account string from the drop down list. The account string is used to create a user in a Teradata Database, instead of providing account information during configuration of ODBC. It allows Teradata to isolate users, to find out what applications users are running, or to restrict users trying to connect to the Teradata Database. Even though the User Name and Password parameters are required to log on to the Teradata Database, entry into the Connect to Teradata Database dialog box is not required because they may be filled in by the user logon exit routine or retrieved from another parameter or service. 4 Click OK. 72 Teradata Tools and Utilities for SUSE Linux Installation Guide

73 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database Connecting to a Teradata Database from a Command Line Application 1 Enter the.logmech command. The.logmech command identifies the desired logon authentication mechanism (logmech_name_string). The logmech_name_string is limited to eight bytes and is not case sensitive. The syntax for the.logmech command is:.logmech logmech_name_string where logmech_name_string can have any one of the following values: None - If no authentication mechanism is entered, or if the authentication mechanism selected is not supported, the system determines a default based on client and server settings TD2 - Teradata 2 mechanism LDAP - LDAP mechanism KRB5 - Kerberos mechanism 2 Enter the.logdata command. To successfully authenticate the user, the.logdata command provides all the parameters needed by the authentication mechanism other than a UserId and Password. The information is entered into and passed by the logdata_string. The logdata_string is limited to 64 KB. The syntax for the.logdata command is:.logdata logdata_string; If logdata_string has white space characters or other special characters embedded, the entire logdata_string must be delimited with single quotes:.logdata `logdata_string'; The exact contents of the logdata_string vary according to the selected authentication mechanism. The string is not displayed, parsed, or otherwise processed by the application. 3 Enter the.logon command. The syntax for the.logon command is:.logon DBCName/[UserId,Password][,AccountId] where The required DBCName is also referred to as the TDPID (Teradata Director Program ID). It identifies a particular Teradata Database. If no identifier is specified, the value of this field is copied from the clispb.dat field, i_dbcpat. DBCName is not case sensitive. The optional UserId or user name string can be up to 30 characters long. The first character cannot be a numeric character. UserId is not case sensitive. The optional Password string can be up to 30 characters long. The first character cannot be a numeric character. In the dialog box, each character of Password is displayed as an asterisk (*). Password is not case sensitive. Teradata Tools and Utilities for SUSE Linux Installation Guide 73

74 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database The AccountId is optional. If supplied, it must be separated from the Password by a comma, and if the Password is not supplied, by two commas. The first character cannot be a numeric character. Do not enter the single quote (') that normally surrounds an AccountId. AccountId is not case sensitive. Example Logons from the Command Line In general, mechanisms that perform authentication and validation do not require that a Teradata Database UserID and Password be included as part of the logon string. If these items are provided in conjunction with an authentication mechanism, they are ignored. Mechanism Mechanism Parameter UserID Password TD2 Never Must Must KRB5 Optional Optional Optional LDAP Optional Optional Optional Kerberos Logon Examples Implicit Logon In all environments that support Kerberos, a UserId, Password, and a Domain or a Realm can be provided. The Domain or Realm must be supplied separately as authentication mechanism data. After the user's identity has been verified by Kerberos, an implicit logon proceeds using the tendered UserId as the Teradata Database Username:.logmech KRB5.logdata joe@domain1@@mypassword.logon mydbs/ Single-Domain Environment Logon For single-domain environments, the gateway can be configured so that the Domain or Realm do not need to be supplied:.logmech KRB5.logdata joe@@mypassword.logon mydbs/ SSO Logon Alternatively, a Kerberos-mediated SSO-style logon can be used by omitting the UserId, Password and a Domain or a Realm. In this case, Kerberos uses the security credentials associated with the current client session:.logmech KRB5.logon mydbs/ Accounting Information 74 Teradata Tools and Utilities for SUSE Linux Installation Guide

75 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database If required, Teradata Database accounting information may be included as part of.logon command as follows:.logmech KRB5.logdata joe@domain1@@mypassword.logon mydbs/,, or.logmech KRB5.logdata joe@@mypassword.logon mydbs/,, or.logmech KRB5.logon mydbs/,, In all of these cases, a Teradata Database Username must be defined in the target Teradata Database that matches the actual or derived UserId. The Username must have previously been granted the "logon with null password privilege." Note: The special dbc username cannot be used with Kerberos authentication mechanism because "dbc" cannot be granted the "logon with null password privilege." If the "dbc" username is passed, the Teradata Database will return error LDAP Logon Examples Implicit Logon The LDAP authentication mechanism allows a user to be authenticated via LDAP and, optionally, to assume a role or user identity other than his or her own, as allowed by the appropriate directory settings. The user may supply a UserId, Password, and Domain or Realm. The exact contents of the LDAP.logdata information necessarily depends largely on how the site is using LDAP, and how LDAP has been configured. The samples below are generic examples. Once the user's identity has been verified by LDAP, an implicit logon will proceed using the UserId as the Teradata Database username:.logmech LDAP.logdata domain7authcid=joe password=password real=myrealm.logon mydbs/joe,password Accounting Information If required, Teradata Database accounting information may be included as part of.logon command as follows:.logmech LDAP.logdata authcid=joe password=password real=myrealm.logon mydbs/,, If the directory maps the UserId to a specific Teradata Database Username, that Username must be defined in the target Teradata Database and must have previously been granted the "logon with null password privilege." Once the user's identity has been verified by LDAP, an implicit logon will proceed using the tendered UserId as the Teradata Database Username. Teradata Tools and Utilities for SUSE Linux Installation Guide 75

76 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database Note: The special "dbc" username cannot be used with the LDAP authentication mechanism because "dbc" cannot be granted the "logon with null password privilege." If "dbc" is passed as the username, the Teradata Database will return error Note: If the directory does not map the UserId to a specific Teradata Database Username, a generic username will be used and a role assigned. The role will be derived from information contained in the directory. Logon will be by extended logon. Note:.logdata information must always be provided for the LDAP authentication mechanism. TD2 Logon Examples TD2 Logon Mechanisms TD2 represents the Teradata Database logon mechanism. It does not perform any authentication. It facilitates encryption/decryption for sessions connected without the mediation of extended security. A valid Teradata Database username and password are always required. TD2 is used by Teradata Tools and Utilities 8.0 and later for the V2R6.0 Teradata Database and later. There should be no.logdata parameter; if one is passed to CLIv2, it is ignored. TD2 Logon TD2 is the default mechanism for the server-based XML configuration file:.logmech TD2.logon mydbs/rhh,password Connecting to a Teradata Database Programmatically Product ODBC Driver for Teradata OLE DB Provider for Teradata Teradata Call-Level Interface version 2 Several Teradata Tools and Utilities products allow a programmatic connection to a Teradata Database using SQL and APIs. 1 Consult the manual for the specified connectivity product to learn how to programmatically connect to a Teradata Database. Document and Description B A, ODBC Driver for Teradata User Guide Describes SQLConnect, SQLDriverConnect, SQLBrowseConnect, and the parameters implemented for security, and includes information on configuring the ODBC Driver for Teradata B A, OLE DB Provider for Teradata User Guide Teradata JDBC Driver Teradata JDBC Driver Reference : Describes the security implemented for the OLE DB Provider for Teradata B A, Teradata Call-Level Interface Version 2 Reference for Network- Attached Systems Describes the security implemented for the Teradata Call-Level Interface version 2 76 Teradata Tools and Utilities for SUSE Linux Installation Guide

77 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database Product Document and Description Describes the security-related connection parameters of the Teradata JDBC Driver Checking Logon Error Messages Message Text Explanation Generated by Remedy UTY1652 Logon mechanism is not supported in the version of CLI. The user specified an option that needs to use the logon authentication mechanism feature but this feature is not supported in the version of CLI. UTYMSG Remove specified logon mechanism options. UTY6668 Invalid use of the.logmech statement. It is invalid to specify the.logmech statement after the.logon statement. UTYMSG Remove the invalid statement and resubmit the program. UTY6669 Invalid use of the.logdata statement. It is invalid to specify the.logdata statement after the.logon statement. UTYMSG Remove the invalid statement and resubmit the program. UTY6670 A.LOGMECH statement has been previously specified, terminating. A.LOGMECH statement has already been processed. UTYMSG Remove the extra statement and resubmit the program. UTY6671 A.LOGDATA statement has been previously specified, terminating. A.LOGDATA statement has already been processed. UTYMSG Remove the extra statement and resubmit the program. Teradata Tools and Utilities for SUSE Linux Installation Guide 77

78 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database 78 Teradata Tools and Utilities for SUSE Linux Installation Guide

79 CHAPTER 8 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 SUSE Linux Installation Guide 79

80 Chapter 8 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. 80 Teradata Tools and Utilities for SUSE Linux Installation Guide

81 Client Computer Problem: Missing Hosts File 1 Verify that the /etc/hosts file exists on the client. Chapter 8 Troubleshooting the Installation Client Computer Problem: Missing Hosts File 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 / etc/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 SUSE Linux Installation Guide 81

82 Chapter 8 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 Basic Teradata Query, 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 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. 82 Teradata Tools and Utilities for SUSE Linux Installation Guide

83 Chapter 8 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 SUSE Linux Installation Guide 83

84 Chapter 8 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 out from the system and log on again. 2 Rerun the Teradata Parallel Transporter job. 3 If you still cannot find tbuild, check that the $TWB_ROOT/bin path is in your PATH environment variable. The TWB_ROOT environment variable is set to the installation directory for Teradata Parallel Transporter. 4 If the $TWB_ROOT/bin path is not in the PATH environment variable, add the $TWB_ROOT/bin path to the front of the PATH environment variable. 5 Run the Teradata Parallel Transporter job again. Teradata Parallel Transporter Problem: Can Not Run New Version of Teradata Parallel Transporter If you cannot run the newly installed version of Teradata Parallel Transporter: 1 Log off from the system and 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 $TWB_ROOT/bin path is in the PATH environment variable. TWB_ROOT is the environment variable that is set to the installation directory for Teradata Parallel Transporter. 4 If the $TWB_ROOT/bin path is not in the PATH environment variable, add the $TWB_ROOT/bin path to the front of the PATH environment variable. 5 Run the Teradata Parallel Transporter job again. 84 Teradata Tools and Utilities for SUSE Linux Installation Guide

85 Chapter 8 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 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, check the $TWB_ROOT/lib path is in the LD_LIBRARY_PATH environment variable. TWB_ROOT is the environment variable that is set to the installation directory for Teradata Parallel Transporter. 4 If the $TWB_ROOT/lib path is not in the LD_LIBRARY_PATH environment variable, then add the $TWB_ROOT/lib path to the front of the LD_LIBRARY_PATH 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 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, check the $TWB_ROOT/msg/%N path is in the NLSPATH environment variable. TWB_ROOT is the environment variable that is set to the installation directory for Teradata Parallel Transporter. 4 If the $TWB_ROOT/msg/%N path is not in the NLSPATH environment variable, add the $TWB_ROOT/msg/%N path to the NLSPATH environment variable. 5 Rerun the Teradata Parallel Transporter job. Technical Assistance Technical assistance during installation of the Teradata Tools and Utilities software is available from the Teradata Solutions Customer Services Remote Services Center (TSCS- RSC). For more information, see B C, Teradata Tools and Utilities Release Definition Release Teradata Tools and Utilities for SUSE Linux Installation Guide 85

86 Chapter 8 Troubleshooting the Installation Technical Assistance 86 Teradata Tools and Utilities for SUSE Linux Installation Guide

87 CHAPTER 9 Deploy Teradata Tools and Utilities with TAR 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. TAR Script Information The tar_teradata_client_packages script downloads Teradata client packages from a disk mount and packages them in a tar file for distribution to other systems. If the gzip executable is installed, packages are compressed accordingly. The tar file can include specific packages or all packages depending on the command options selected. Dependent Teradata Tools and Utilities packages are automatically included in the tar file. The files are copied from the Teradata client media. Third-party software dependencies must be installed separately. TAR Script Compatibility with Platform Operating Systems The tar script provided on the installation media runs on all of the major Linux and UNIX platforms that Teradata client supports and can be run from the DOS prompt in a Windows command window: IBM AIX HP-UX SUSE Linux Red Hat Linux Sun Solaris SPARC Sun Solaris Opteron Executed within a Windows command window (DOS) On UNIX machine with the Korn shell (/bin/ksh) TAR File Contents The tar_teradata_client_packages script is contained on each of the Teradata Tools and Utilities UNIX installation media. It allows the creation of a subset of the Teradata client packages from the DVD media by simply copying a single tar file across the network. The tar file created: Contains all of the files for the specified platform, or all the files for a specified package Includes all of the dependent packages for the client packages in the file Teradata Tools and Utilities for SUSE Linux Installation Guide 87

88 Chapter 9 Deploy Teradata Tools and Utilities with TAR 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, the tar program is typically available in /bin. Note: Windows does not automatically include tar.exe or gzip.exe. They must be installed manually. 1 Ensure the tar executable is located in the PATH on the system running the script. If the tar.exe executable isn't located on the system, the script aborts and provides a suggested location for the user to download the GNU version of tar.exe from ftp:// ftp.gnu.org/pub/pub/gnu/tar/tar-1.12.msdos.exe. Note: On a UNIX system, the tar program is typically available in /bin. If the gzip executable on Windows is available in the PATH, the script attempts to compress the tar file, to make it faster to transfer across a network. Note: The Linux tar file only compresses a small amount, compared to the other platform's packages. TAR Script Commands and Their Functions Two versions of the script are provided: tar_teradata_client_packages.bat for Windows tar_teradata_client_packages.sh for UNIX and Linux Command tar_teradata_client_packages or Description Displays the available commands tar_teradata_client_packages help tar_teradata_client_packages list tar_teradata_client_packages list {platform} Displays the available platforms and packages on the DVD Lists the products available for a specific platform on the DVD Running the script with [platform] as the first parameter creates a tar file in the default target path. The resulting tar file contains all Teradata client packages on that media for that system. 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: 88 Teradata Tools and Utilities for SUSE Linux Installation Guide

89 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR Command Description teradata-client-{platform}-{media_name}.tar (.gz if compressed) Running the script with [platform] as the second parameter following the list parameter only lists the packages available for the specified platform. tar_teradata_client_packages {platform} tar_teradata_client_packages {platform} [{package1} {package2} ] Runs the script creating a tar file for a specific platform, including all packages Optional parameters following the [platform] parameter list specific packages, including: bteq cliv2 fastexp fastld mload If any packages other than the four dependent packages are specified, the dependent packages are all included: cliv2 piom tdicu teragss Adding package names (previously displayed by the list command) after the [platform] parameter always includes the dependent packages if they are available on the media. If any of these packages is individually specified, all of these dependencies are included in the archive. Runs the script creating a tar file for a specific platform and specific packages Optional parameters following the [platform] parameter list specific packages, including: bteq cliv2 fastexp fastld mload If any packages other than the four dependent packages are specified, the dependent packages are all included: cliv2 piom tdicu teragss Adding package names (previously displayed by the list command) after the [platform] parameter always includes the dependent packages if they are available on the media. If any of these packages is individually specified, all of these dependencies are included in the archive. Teradata Tools and Utilities for SUSE Linux Installation Guide 89

90 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR Note: The version of the package is not required with the package name; bteq works as well as bteq1400. TAR Script Usage Considerations Subject Default Directory Multiple and Dependent Packages Getting Help on the Script Description The tar script prompts for a directory to create the tar file, and accepts Enter for the default user directory. The default location is: C:\Documents and Settings\username is usually HOME for Windows UNIX user home directory for UNIX /tmp if the script is run as root on UNIX tar_teradata_client_packages attempts to create the directory if it does not exist. If the location is read-only or unable to be written, the script ends. If a single package or multiple packages are selected, all of the dependent products are included, even if the product selected is one of the single dependent packages. Typically, the dependent packages depend on each other; cliv2 depends on tdicu and TeraGSS. For tar_teradata_client_packages, the tar executable can run without parameters, or with the help parameter: D:\tar_teradata_client_packages D:\tar_teradata_client_packages help A screen similar to the following, listing the command usage and optional parameters, appears as a result of the command: ************************************************************************ * Tar Teradata Client Packages v * ************************************************************************ Tar Teradata Client Packages Usage: tar_teradata_client_packages list tar_teradata_client_packages list {platform} tar_teradata_client_packages {platform} [{package1} {package2}...] Parameters: commands : help, list, {platform} [{package1} {package2}...] help : Display this help message. list : List the available platforms and packages from the media. list {platform} : List the packages available for the specified platform. {platform} : Available platforms: aix, ia64, pa-risc, i386, s390x, opteron, sparc Create the tar file for the supplied platform and include all packages or individual packages. {package} : Specify the packages available on this media for the specific platform. The parameter "all" (or blank) will include all available packages. To specify individual packages, list the packages separated by a space. Example: ttcp.bat linux bteq fastld The dependencies will automatically be included and do not need to be listed individually. The following packages are included: ---TeraGSS cliv2 tdicu piom 90 Teradata Tools and Utilities for SUSE Linux Installation Guide

91 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR Subject Listing the Available Packages and Platforms Description All of the platforms and packages contained on the DVD can be listed by running the tar executable with the list parameter (platforms and packages vary), for example: /mount/loadunloadvol2> tar_teradata_client_packages.sh list To list all packages for a specific platform available on the DVD, run the tar executable with the list parameter followed by the platform parameter, for example: /mount/loadunloadvol2> tar_teradata_client_packages.sh list HP-UX A screen similar to the following appears as a result of the list command. It lists all the platforms and packages on the current DVD: ************************************************************************ * Tar Teradata Client Packages v * ************************************************************************ Load /Unload - Volume 2 The available platforms are: HP-UX Linux The available packages are: --- HP-UX Products bteq fastexp mload npaxsmod tdicu tpump cliv2 fastld mqaxsmod piom TeraGSS --- Linux Products bteq fastexp mload npaxsmod tdicu tpump cliv2 fastld mqaxsmod piom TeraGSS Downloading Windows Utility Software for TAR Deployment This task is necessary only if you are installing from a Windows platform. 1 Enter the following command to check if tar.exe is installed: D:\tar_teradata_client_packages A screen similar to the following appears, directing you to a location where the tar.exe file can be downloaded, if tar.exe is not installed, and the tar_teradata_client_packages executable is run on the initial skeleton system: ************************************************************************ * Tar Teradata Client Packages v * ************************************************************************ Load/Unload - Volume 2 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: Teradata Tools and Utilities for SUSE Linux Installation Guide 91

92 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR 2 If tar.exe is not installed, install tar.exe and save tar-1.12.msdos.exe as tar.exe in your windows directory: ftp://ftp.gnu.org/pub/pub/gnu/tar/tar-1.12.msdos.exe 3 Enter the following command to check if gzip.exe is installed: D:\tar_teradata_client_packages When the tar file is being created, and gzip.exe cannot be found a message similar to the following is displayed: Notice: The executable gzip.exe is not found. Download from for MSDOS to automatically compress the output tar file to a gzip file. To compress files, download gzip.exe 4 Unless gzip.exe was previously installed, gzip.exe does not exist in your C: \Windows directory. To install it, go to: gzip home page and download the MSDOS version to the C:\Windows directory. Overview of TAR Script Examples The file tar_teradata_client_packages is available on all installation media. The examples list packages available and create tar files that include all packages or individual packages and their dependent packages. Examples are provided that show: Archiving packages on Linux platforms Archiving SPARC Packages to Windows This example copies all Sun Solaris SPARC packages on the installation media to a Windows client. The resulting tar file can be copied to Sun Solaris SPARC machines, and the packages loaded there. The procedure includes the following steps 1. Listing available products 2. Downloading/archiving products Note: In this example, gzip.exe has not been installed and the files are not compressed. 1 Enter the tar executable on the Windows system with the list parameter to list 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 * ************************************************************************ Preprocessors - Volume 3 The available platforms are: AIX Solaris 92 Teradata Tools and Utilities for SUSE Linux Installation Guide

93 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR 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 cliv21400 sqlpp1400 tdicu1400 TeraGSS TeraGSS Solaris Opteron Products cliv21400 sqlpp1400 tdicu1400 TeraGSS_solaris-i386 TeraGSS_solaris-x Enter the following commands to download the Sun Solaris SPARC packages and dependencies on the Teradata Tools and Utilities media to the Windows client. a D:\tar_teradata_client_packages sparc A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v * ************************************************************************ Preprocessors - Volume 3 Platform: Solaris\Sparc Default Path and Output File: C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.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-sparc-preprocessors-volume-3.tar" b Press Enter to download the packages. A screen similar to the following appears: ---Archiving all packages for sparc. tar cvf "C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar" Solaris\Sparc Solaris/Sparc/ Solaris/Sparc/TeraGSS/ Solaris/Sparc/TeraGSS/install/ Solaris/Sparc/TeraGSS/install/depend.. (more files). Solaris/Sparc/tdicu1400/reloc/$LIBDIR64/libiculxtd.so.46.0 Solaris/Sparc/tdicu1400/reloc/$LIBDIR64/libicuuctd.so.46.0 Teradata Tools and Utilities for SUSE Linux Installation Guide 93

94 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR tar rvf "C:\Documents and Settings\<user>\teradata-client-sparcpreprocessorsvolume-3.tar".setup.sh.setup.sh tar rvf "C:\Documents and Settings\<user>\teradata-client-sparcpreprocessors-volume-3.tar" setup.bat setup.bat tar rvf "C:\Documents and Settings\<user>\teradata-client-sparcpreprocessors-volume-3.tar" MEDIALABEL MEDIALABEL tar rvf "C:\Documents and Settings\<user>\teradata-client-sparcpreprocessors-volume-3.tar" tar_teradata_client_packages.* tar_teradata_client_packages.bat tar_teradata_client_packages.sh Notice: The executable gzip.exe is not found. Download from for MSDOS to automatically compress the output tar file to a gzip file. The file has been saved at : C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar Archiving Packages to Linux This example copies all packages and dependencies on the installation CD for a SUSE Linux or Red Hat Linux client. The packages and dependencies are archived and then compressed. 1 Run the tar executable with linux as the platform: D:\tar_teradata_client_packages linux A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v * ************************************************************************ Load/Unload - Volume 2 Platform: Linux Default Path and Output File: C:\Documents and Settings\user\teradata-client-linux-load-unload-volume- 2.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-load unload-volume-2.tar" ---Archiving all packages for linux. tar cvf "C:\Documents and Settings\user\teradata-client-linux-loadunload-volume-2.tar" Linux a Linux/mqaxsmod/mqaxsmod i386.rpm 118 blocks a Linux/mload/mload i386.rpm 374 blocks a Linux/piom/piom i386.rpm 79 blocks a Linux/tdicu/tdicu noarch.rpm blocks a Linux/fastld/fastld i386.rpm 189 blocks a Linux/TeraGSS/TeraGSS_redhatlinux-i386-14i i386.rpm blocks a Linux/fastexp/fastexp i386.rpm 341 blocks a Linux/tpump/tpump i386.rpm 478 blocks a Linux/npaxsmod/npaxsmod i386.rpm 272 blocks a Linux/cliv2/cliv x86_64.rpm 766 blocks a Linux/bteq/bteq i386.rpm 303 blocks 94 Teradata Tools and Utilities for SUSE Linux Installation Guide

95 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR tar rvf "C:\Documents and Settings\user\teradata-client-linux-loadunload-volume-2.tar".setup.sh tar: blocksize = 20 a.setup.sh 282 blocks tar rvf "C:\Documents and Settings\user\teradata-client-linux-loadunload-volume-2.tar" setup.bat tar: blocksize = 20 a setup.bat 1 block tar rvf "C:\Documents and Settings\user\teradata-client-linux-loadunload-volume-2.tar" MEDIALABEL tar: blocksize = 20 a MEDIALABEL 1 block The file has been saved at : C:\Documents and Settings\user\teradata-client-linux-load-unloadvolume-2.tar.gz Teradata Tools and Utilities for SUSE Linux Installation Guide 95

96 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR 96 Teradata Tools and Utilities for SUSE Linux Installation Guide