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

(1)

Teradata Tools and Utilities for SUSE Linux

Installation Guide

Release 14.00 B035-3122-071A 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 e-mail: [email protected]

Any comments or materials (collectively referred to as “Feedback”) sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback.

(3)

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

(4)

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...43 Table of Contents

(5)

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 Table of Contents

(6)

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...81 Table of Contents

(7)

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 Table of Contents

(8)

(9)

Preface

Purpose

This book describes how to install and deploy Teradata Tools and Utilities Release 14.00 software on a computer that runs on a supported operating system. Teradata Tools and Utilities is a group of products designed to work with the Teradata Database.

Audience

This guide is intended for use by:

• Database administrators and relational database developers • System administrators

• System and application programmers

• System operators and other database specialists

Supported Releases

This book supports the following releases: • Teradata Database Release 14.0

• Teradata Tools and Utilities Release 14.00 To locate detailed supported-release information:

1 Go to http://www.info.teradata.com.

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.

(10)

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 Description

November 2011 14.00

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.

August 2011 14.00

Initial release

Preface Prerequisites

(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 14.00.01 DVD

• Teradata Tools and Utilities Tape Storage Management Enablers Linux & WINDOWS Release 14.00.01 DVD

• Teradata Tools and Utilities Meta Data Services Linux & WINDOWS Release 14.00.01 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 B035-2029-071C, Teradata Tools and Utilities Release Definition Release 14.00 .

DVD Contents

The following table shows the Teradata Tools and Utilities products and dependencies contained on the Installation Kit media.

(12)

Product Install From...

Basic Teradata Query Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Named Pipes Access Module Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

ODBC Driver for Teradata Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Shared Common Components for

Internationalization for Teradata Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release14.00.01 DVD

Teradata Archive/Recovery Utility Teradata Tools and Utilities Tape Storage Management Enablers Linux & WINDOWS Release 14.00.01 DVD

Teradata C Preprocessor2 Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata Call-Level Interface version 2 Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata COBOL Preprocessor2 Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata Data Connector Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata FastExport Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata FastLoad Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata Generic Security Services

Client Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release14.00.01 DVD

Teradata JDBC Driver Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata JMS Access Module Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata Meta Data Services Teradata Tools and Utilities Meta Data Services Linux & WINDOWS Release 14.00.01 DVD

Teradata MultiLoad Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata Parallel Data Pump Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata Parallel Transporter Base Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata Parallel Transporter Stream Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Teradata Wallet Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD

Chapter 1 Prepare for Installation

(13)

Product Install From...

Teradata WebSphere MQ Access

Module Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release14.00.01 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 Versions Chart

12.00.xx B035-3119-067K, Teradata Tools and Utilities 12.00.xx Supported Platforms and Product Versions

14.00 B035-3119-071K, Teradata Tools and Utilities 14.00 Supported Platforms and Product Versions

Product Descriptions

Product Description

Basic Teradata Query 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.

Named Pipes Access Module 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).

ODBC Driver for Teradata 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.

Shared Common Components for

Internationalization for Teradata A library of routines based on the IBM International Components for Unicodeversion 3.6. The library provides Unicode support. Teradata Archive/Recovery Utility 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.

Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD

(14)

Teradata C Preprocessor2 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.

Teradata Call-Level Interface version 2 A library of routines that enable an application program to access data on the Teradata Database.

Teradata COBOL Preprocessor2 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.

Teradata Data Connector Reads and writes flat files to provide the input/output interface for access modules.

Teradata FastExport 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.

Teradata FastLoad 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 Generic Security Services

Client Teradata implementation of industry-standard Generic Security Services APIs inC language. It provides enhanced security services interfaces between Teradata network clients and the Teradata Database.

Teradata JDBC Driver Provides access to the Teradata Database using Java applications.

Note: Can be downloaded and installed from the web.

Teradata JMS Access Module 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).

Teradata Meta Data Services 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.

Teradata MultiLoad 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. Teradata Parallel Data Pump 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.

Teradata Parallel Transporter Base Object-oriented client application that provides scalable, high-speed, parallel data extraction, loading, and updating.

(15)

Teradata Parallel Transporter Stream 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).

Teradata Wallet 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.

Teradata WebSphere MQ Access

Module Allows Teradata utilities to import data using IBM Teradata WebSphere MQAccess 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 Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector

Teradata Generic Security Services Client

None

Named Pipes Access

Module None None

ODBC Driver for

Teradata Shared Common Components forInternationalization for Teradata Teradata Generic Security Services Client

Microsoft Data Access Components (MDAC), version 2.8 SP1 (on distribution DVD)

Shared Common Components for Internationalization for Teradata None None Teradata Archive/

Recovery Utility Shared Common Components forInternationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector

None

Teradata C

Preprocessor2 Shared Common Components forInternationalization for Teradata Teradata Call-Level Interface version 2 Teradata Generic Security Services Client

None

(16)

Teradata Call-Level

Interface version 2 Shared Common Components forInternationalization for Teradata Teradata Generic Security Services Client

None

Teradata COBOL

Preprocessor2 Shared Common Components forInternationalization for Teradata Teradata Call-Level Interface version 2 Teradata Generic Security Services Client

None

Teradata Data

Connector None None

Teradata FastExport Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector

None

Teradata FastLoad Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector

None

Teradata Generic

Security Services Client None None

Teradata JDBC Driver None JDK 1.4 , JDK 5.0, or JDK 6.0

Note: The environment can be downloaded

from Java Downloads. Teradata JMS Access

Module None None

Teradata Meta Data

Services ODBC Driver for Teradata_{Shared Common Components for} Internationalization for Teradata Teradata Generic Security Services Client

JRE 5.0 or JRE 6.0 32-bit

from Java Downloads.

Teradata MultiLoad Shared Common Components for Internationalization for Teradata Teradata Call-Level Interface version 2 Teradata Data Connector

None

Teradata Parallel Data

Pump Shared Common Components forInternationalization for Teradata Teradata Call-Level Interface version 2

None

(17)

Teradata Data Connector

Teradata Generic Security Services Client Teradata Parallel

Transporter Base Shared Common Components forInternationalization for Teradata Teradata Call-Level Interface version 2 Teradata Generic Security Services Client

None

from Java Downloads.

Teradata Parallel

Transporter Stream Teradata Call-Level Interface version 2 Teradata Generic Security Services Client Teradata Parallel Transporter Base

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 14.00.01.00 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 14.00.00 is already installed. Do you want to overwrite it with version 14.00.01?

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.

(18)

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.

(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

(20)

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 Description

uninstall_ttu.sh Executes the script to remove packages uninstall_ttu.sh priorto xx.xx.xx.xx Removes all packages before a specific version

number

uninstall_ttu.sh noremove Executes the script, but does not remove any

packages

uninstall_ttu.sh nocheck Executes the script, but does not check against

known Teradata Tools and Utilities packages

Parameters

Parameter Description

priorto xx.xx.xx.xx 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 14.00.00.00. The number parameter must contain

all four version numbers, and can be specific enough to remove all packages before, for example, 14.00.00.01. Typically the last

two sets of digits would just be 00.00. noremove Executes the script without removing packages

This parameter can be used to test the script without removing the packages.

The package remove commands that would have been used to remove each package are displayed. This may be useful to do a test package remove without actually removing the packages, to see in what order the packages would have been removed, or to capture the commands used to remove the packages for use in another script.

nocheck Executes the script looking for packages with "Teradata" in the

package name, but skipping the check against the known list of Teradata Tools and Utilities packages

Chapter 2 Uninstall Previous Software Uninstall Script Overview

(21)

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-tcp-debug-<processid>.out

This may be useful for debugging purposes. It lists the known Teradata Tools and Utilities packages, the initial list of the packages selected, and the final ordered list, and could be helpful in determining why a package was not removed.

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/

(22)

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. bteq1400 - 14.00.00.00 2. fastexp1400 - 14.00.00.00 3. fastld1400 - 14.00.00.00 4. mload1310 - 13.10.00.02 5. mload1400 - 14.00.00.00 6. mqaxsmod1310 - 13.10.00.02 7. npaxsmod1310 - 13.10.00.02 8. npaxsmod1400 - 14.00.00.00 9. tdodbc1400 - 14.00.00.00 10. tdwallet1400 - 14.00.00.00 11. tptstream1400 - 14.00.00.03 12. tpump1310 - 13.10.00.01 13. tpump1400 - 14.00.00.00 14. tptbase1400 - 14.00.00.03 15. piom1400 - 14.00.00.00 16. cliv21310 - 13.10.00.08 17. cliv21400 - 14.00.00.00 18. tdicu1310 - 13.10.00.02 19. tdicu1400 - 14.00.00.00 20. TeraGSS - 14.00.00.00 21. TeraGSS32 - 14.00.00.00

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 cliv21310 - 13.10.00.08 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: Chapter 2 Uninstall Previous Software

(23)

…

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:

(24)

1 To see if a package is still installed, type: rpm –q <packagename>

2 To manually remove a package, type:

rpm –erase --ignoredeps <packagename> Chapter 2 Uninstall Previous Software

(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 Description

Installing from a Web URL Some Teradata Tools and Utilities have third-party dependencies. Install these dependencies from their respective URLs.

Installing from DVD 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.

Installing from the Teradata

Developer Exchange The download center may contain more current software packages which should be installedinstead of lower version software contained on the DVD media. Packages on the download center include drivers and connectivity software.

Installing from the Teradata

Software Server The server may contain updated software packages which should be installed in lieu of lowerversion software contained on the DVD media, or on the Teradata Developer Exchange. Installing from the Teradata

ESDM Server Teradata Electronic Software Distribution Management (ESDM) program allows users taxbenefits for some users that download software. Deploying using tar The DVD media include files that allow you to deploy Teradata Tools and Utilities products

across your network using tar.vbs scripts and tar. Installing Teradata Meta

(26)

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-32-bit versions of the ODBC Driver for Teradata, both the 32-32-bit and 64-32-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 14.00.01 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: Chapter 3 Install New Software

(27)

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 B035-1100-111A, Security Administration for more information about Teradata Wallet.

6 After reviewing product dependencies, do one of the following: Command Action

Install All Packages 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.

Uninstall All Type u. This removes previous versions of Teradata Tools and Utilities

products, except Teradata Generic Security Services Client (TeraGSS). Display installed

package sizes Type

s to display the size of each installed package.

Install Selected

Packages Type the numbers of the desired products and dependencies, separatedby 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

Chapter 3 Install New Software Installing Teradata Tools and Utilities

(28)

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

MDS Repository Teradata Server HTML Page Intranet or Internet HTTP Request HTML Page MDS Com Interface + Engine ASP Page Active Server Engine Metasurf

Client Web Browser

Workstation/Laptop/Etc. with Supported Browsers

3118B001 Windows Web Server ODBC ODBC Teradata Database MetaManager/ MetaBrowse (Windows PC) MDS Engine * * *MDS Installed

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.

(29)

Teradata Meta Data Services Prerequisites

The following table lists the software and hardware required before installing Teradata Meta Data Services (MDS).

Text Box Description

Teradata Database System 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.

Teradata User Account 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. ODBC Driver for Teradata

(ODBC) and Data Source Name (DSN)

All machines running Teradata MDS software must have the appropriate ODBC Driver for Teradata installed and configured. ODBC 12.00.00 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.

Windows-based Workstation 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

Active Server Pages (ASP)

Compliant Web Server If the Teradata MDS MetaSurf web application will be used, a Windows 2008 Server withMicrosoft 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.

DIM Update Server 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.

(30)

Text Box Description

MDS Core Files 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.

MDS Development Kit 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.

MDS MetaSurf Files _{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.

MDS DIM Update Files 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 .

(31)

• 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.

(32)

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-14.00.00.01-1.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=208.199.59.208 LastUser= Username= Password= Database= DefaultDatabase= [SYSTEM1DSN] Driver=/usr/odbc/drivers/tdata.so Description=Teradata V12.0 System DBCName=208.199.59.209 LastUser= Username= Password= Database= DefaultDatabase= [default] Driver=/usr/odbc/drivers/tdata.so

Description=NCR 5500 running Teradata V12.0 DBCName=208.199.59.209

LastUser= Username=

(33)

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.

(34)

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.

-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

(35)

-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 Create a backup of the Teradata Database containing the Teradata MDS repository, if

you have not already done so.

b 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.

(36)

The following figure shows the processes supporting Automatic DIM updates.

Feature Description

Relay Services Gateway 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);

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.

DDL Gateway 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.

MDS Action Processor 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