Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Teradata Tools and Utilities for Microsoft Windows Installation Guide Release 14.00 B035-2407-071A March 2012 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. Copyright © 1996 - 2012 by Teradata Corporation. All Rights Reserved. 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..................................................................................................................................14 Product Dependencies................................................................................................................................17 Installing Dependencies......................................................................................................................20 System Requirements..................................................................................................................................21 Platform Requirements.......................................................................................................................21 Chapter 2: Uninstall Previous Software....................................................................................................23 About Uninstalling Previous Versions of Teradata Tools and Utilities Software.....................................23 Uninstall Script Overview..........................................................................................................................23 Uninstall Script Prerequisites.............................................................................................................24 Uninstall Script Usage and Parameters.............................................................................................24 Usage...............................................................................................................................................24 Parameters.....................................................................................................................................24 Manually Uninstalling Previously Installed Teradata Tools and Utilities..........................................26 Chapter 3: Install New Software......................................................................................................................29 Teradata Tools and Utilities for Microsoft Windows Installation Guide 3 Table of Contents Installing Third-Party Software.........................................................................................................................29 .NET Data Provider for Teradata...............................................................................................................29 Teradata Parallel Transporter Base............................................................................................................29 Teradata Parallel Transporter Wizard.......................................................................................................29 Teradata Query Scheduler Administrator................................................................................................30 Teradata SQL Assistant...............................................................................................................................30 Teradata WebSphere MQ Access Module................................................................................................30 Installing Teradata Tools and Utilities.............................................................................................................30 Installing Teradata Tools and Utilities......................................................................................................31 Silently Installing Teradata Tools and Utilities Products from DVD...................................................32 Installing .NET Data Provider for Teradata....................................................................................................32 About Installing .NET Data Provider for Teradata.................................................................................32 Understanding Security Requirements for .NET Data Provider for Teradata....................................33 Known Issues for .NET Data Provider for Teradata...............................................................................33 Uninstalling .NET Data Provider for Teradata........................................................................................34 Installing Third-Party Microsoft .NET Framework................................................................................34 Downloading .NET Data Provider for Teradata......................................................................................34 Installing .NET Data Provider for Teradata.............................................................................................35 Verifying Installation of the .NET Data Provider for Teradata.............................................................36 Installing Meta Data Services.............................................................................................................................37 Teradata Meta Data Services.......................................................................................................................37 Introduction to the Teradata Meta Data Services Installation...............................................................38 Teradata Meta Data Services Documentation...................................................................................38 Teradata Meta Data Services Installation Options...........................................................................38 Teradata Meta Data Services Prerequisites........................................................................................38 Teradata Meta Data Services Software Components.......................................................................39 Uninstalling Teradata Meta Data Services.........................................................................................40 Installing Teradata Meta Data Services..............................................................................................40 Teradata Meta Data Services Configuration......................................................................................43 Configuring the Windows Registry for Teradata Meta Data Services.............................43 Setting Database Connection Information.........................................................................43 Setting Logging and Tracing Levels.....................................................................................44 Creating a Teradata Meta Data Services Repository........................................................................45 Migrating a Teradata Meta Data Services Repository......................................................................45 Creating a Virtual Directory or Web Application............................................................................46 Installing the Automatic Database Information Metamodel.................................................................47 Automatic DIM Update Processes.....................................................................................................47 Out of Sync Recovery............................................................................................................................48 Relay Services Gateway Overview.......................................................................................................50 Adding the Relay Services Gateway vprocs ........................................................................50 Configuring the Relay Services Gateway.............................................................................50 Starting and Stopping the Relay Services Gateway............................................................51 Configuring the Automatic DIM Update with MetaManager........................................................51 4 Teradata Tools and Utilities for Microsoft Windows Installation Guide Table of Contents Adding a Teradata Database System..............................................................................................51 Adding Teradata Nodes...................................................................................................................51 Editing a Teradata Node in MetaManager....................................................................................52 Loading Databases............................................................................................................................52 Enabling Automatic Database Information Metamodel Update...............................................53 Checking DIM Status with MetaManager...................................................................................................53 Starting and Stopping the Data Definition Language Gateway................................................................54 Starting and Stopping the Teradata Meta Data Services Action Processor............................................54 Teradata Developer Exchange.....................................................................................................................................55 Products Available from Teradata Developer Exchange..................................................................................55 Downloading a Product from the Teradata Developer Exchange...................................................................56 Installing Products Downloaded from Teradata Developer Exchange..........................................................56 Teradata Software Server..............................................................................................................................................56 Downloading Patches............................................................................................................................................57 Installing Downloaded Patches............................................................................................................................57 Installing the Windows Help Program.......................................................................................................................57 Chapter 4: Configure New Software.........................................................................................................................59 About Setting Up Network Parameters......................................................................................................................59 About Configuring Teradata Call-Level Interface version 2...................................................................................59 Verifying the Existence of hosts File...........................................................................................................................59 Identifying a Teradata Database..................................................................................................................................60 Adding Entry to hosts File............................................................................................................................................60 About Setting Up Environment Parameters..............................................................................................................61 Defining Paths to System Files.....................................................................................................................................61 Setting Up Environment Variables.............................................................................................................................61 Speeding Up the Logon Process..................................................................................................................................62 Setting Up the Port Number, Netrace, and Threadlogging.....................................................................................62 Setting Up System Parameters.....................................................................................................................................63 clispb Data Information................................................................................................................................................63 Overview of Configuring ODBC Driver for Teradata..............................................................................................63 Configuring ODBC Driver for Teradata.............................................................................................................63 Configuring ODBC Driver for Teradata Data Source.......................................................................................64 About Configuring Teradata Query Scheduler Administrator...............................................................................65 Modifying the HOSTS File....................................................................................................................................65 Configuring Teradata Query Scheduler Client..........................................................................................................66 About Configuring Teradata Query Scheduler Server.............................................................................................66 Specifying a Default Teradata Query Scheduler Server ....................................................................................66 Changing Teradata Query Scheduler Server Configurations...........................................................................66 Configuring Teradata Administrator..........................................................................................................................67 Teradata Tools and Utilities for Microsoft Windows Installation Guide 5 Table of Contents Editing the Teradata Parallel Transporter Configuration File......................................................................68 Editing the Teradata Parallel Transporter Properties File.............................................................................68 Editing the Teradata Parallel Transporter Environment Variables.............................................................69 Configuring Teradata JMS Access Module......................................................................................................69 Chapter 5: Restart the Client Computer.....................................................................................................71 Restarting the Client Computer........................................................................................................................71 Chapter 6: Verify the Complete Installation..........................................................................................73 About Verifying the Installation........................................................................................................................73 Running clisamp...........................................................................................................................................73 Basic Teradata BTEQ Files and Folders....................................................................................................74 JMS Access Module Files and Folders.......................................................................................................74 Named Pipe Access Module Files and Folders.........................................................................................75 .NET Data Provider for Teradata Files and Folders................................................................................75 ODBC Driver for Teradata Files and Folders...........................................................................................77 OLE DB Provider for Teradata Files and Folders....................................................................................77 Shared ICU Libraries for Teradata Files and Folders..............................................................................78 Teradata Administrator Files and Folders................................................................................................78 Teradata Archive/Recovery Utility Files and Folders.............................................................................79 Teradata C Preprocessor2 Files and Folders............................................................................................79 Teradata Call-Level Interface version 2 Files and Folders......................................................................80 Teradata Data Connector Files and Folders.............................................................................................81 Teradata FastExport Files and Folders......................................................................................................81 Teradata FastLoad Files and Folders.........................................................................................................81 Teradata Generic Security Services Files and Folders.............................................................................82 Teradata Index Wizard Files and Folders.................................................................................................84 Teradata JDBC Driver Files and Folders...................................................................................................88 Teradata MultiLoad Files and Folders.......................................................................................................89 Teradata OLE DB Access Module Files and Folders...............................................................................89 Teradata Parallel Data Pump Files and Folders for 32-bit Platforms...................................................89 Teradata Performance Monitor Object Files and Folders......................................................................89 Teradata Query Scheduler Administrator Files and Folders..................................................................90 Teradata Query Scheduler Client Files and Folders................................................................................90 Teradata Query Scheduler Server Files and Folders................................................................................90 Teradata SQL Assistant Files and Folders.................................................................................................91 Teradata Statistics Wizard Files and Folders............................................................................................92 6 Teradata Tools and Utilities for Microsoft Windows Installation Guide Table of Contents Teradata System Emulation Tool Files and Folders..........................................................................................96 Teradata Visual Explain Files and Folders........................................................................................................101 Teradata Wallet Files and Directories...............................................................................................................105 Teradata WebSphere MQ Access Module Files and Folders.........................................................................105 Teradata Workload Analyzer Files and Folders...............................................................................................106 Chapter 7: Security and Connecting to a Teradata Database......................................................107 About Connecting to a Teradata Database..............................................................................................................107 About Logon Procedures.....................................................................................................................................107 Connecting to a Teradata Database from a GUI Application........................................................................107 Connecting to a Teradata Database from a Command Line Application....................................................109 Kerberos Logon Examples...........................................................................................................................111 SPNEGO Logon Examples...........................................................................................................................112 NTLM Logon Examples...............................................................................................................................112 LDAP Logon Examples................................................................................................................................113 Implicit Logon........................................................................................................................................113 Accounting Information.......................................................................................................................113 TD2 Logon Examples...................................................................................................................................114 TD2 Logon Mechanisms.......................................................................................................................114 TD2 Logon..............................................................................................................................................114 Connecting to a Teradata Database Programmatically..................................................................................114 Checking Logon Error Messages........................................................................................................................115 Chapter 8: Deploy Teradata Tools and Utilities with SMS...............................................................117 Introduction to SMS Deployment.............................................................................................................................117 Installation Package Sources......................................................................................................................................118 Introduction to Downloading Packages from DVD.......................................................................................118 Downloading Installation Packages from DVDs for SMS Deployment................................................118 Introduction to Downloading Packages from Teradata Developer Exchange............................................119 Products Available from Teradata Developer Exchange.........................................................................119 Downloading Installation Packages from Teradata Developer Exchange for SMS Deployment......120 Introduction to Downloading Packages from Patch Server...........................................................................121 Downloading Installation Packages from Patch Server for SMS Deployment.....................................121 Overview of Product Response Files.........................................................................................................................122 Installation Order and Dependencies................................................................................................................122 Creating Product Response Files for SMS Deployment..................................................................................128 Creating Basic MSI Files for SMS Deployment................................................................................................129 Copy Packages for SMS Deployment........................................................................................................................129 Teradata Tools and Utilities for Microsoft Windows Installation Guide 7 Table of Contents Creating VBS Script for SMS Deployment....................................................................................................130 Deploying with SMS..........................................................................................................................................130 Sample Uninstall Script....................................................................................................................................130 Chapter 9: Deploy Teradata Tools and Utilities with TAR......................................................169 Deploying Applications with TAR..................................................................................................................169 Understanding the TAR File.....................................................................................................................169 TAR Script Compatibility with Platform Operating Systems.......................................................169 Verifying TAR Script Dependencies are Installed..........................................................................169 TAR Script Commands and Their Functions.................................................................................170 TAR Script Usage Considerations....................................................................................................171 Downloading Windows Utility Software for TAR Deployment.........................................................173 Overview of TAR Script Examples..........................................................................................................173 Archiving Sun Solaris SPARC Packages..........................................................................................174 Archiving an HP-UX Package...........................................................................................................175 Archiving Linux Packages..................................................................................................................177 8 Teradata Tools and Utilities for Microsoft Windows Installation Guide 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. Teradata Tools and Utilities for Microsoft Windows Installation Guide 9 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 Description March 2012 This release makes the following changes: • Added installation procedures for .NET Data Provider for Teradata. 14.00 November 2011 14.00 • Updated dependencies and system requirements for Teradata SQL Assistant, Teradata Query Scheduler Administrator, and OLE DB Provider for Teradata. • Updated configuration details for Teradata Parallel Transporter. 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.vbs, was added. August 2011 Initial release 14.00 10 Teradata Tools and Utilities for Microsoft Windows Installation Guide CHAPTER 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Before performing the procedures in this document, you must have: • • • • Internet access Network access Administrative privileges on the target machine Knowledge of which Teradata Tools and Utilities are to be installed • Familiarity with Windows 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 Database Management 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 that you ordered, contact your Teradata Sales Representative. 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 Microsoft Windows Installation Guide 11 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD 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 .NET Data Provider for Teradata 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 ICU Libraries for Teradata Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD Teradata Administrator Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.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 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 Release 14.00.01 DVD Teradata Index Wizard Teradata Tools and Utilities Database Management WINDOWS Release 14.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 OLE DB Access Module 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 12 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Install From... 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 Performance Monitor Object Teradata Tools and Utilities Database Management WINDOWS Release 14.00.01 DVD Teradata Query Scheduler Administrator Teradata Tools and Utilities Database Management WINDOWS Release 14.00.01 DVD Teradata Query Scheduler Client Teradata Tools and Utilities Database Management WINDOWS Release 14.00.01 DVD Teradata Query Scheduler Server Teradata Tools and Utilities Database Management WINDOWS Release 14.00.01 DVD Teradata SQL Assistant Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD Teradata Statistics Wizard Teradata Tools and Utilities Database Management WINDOWS Release 14.00.01 DVD Teradata System Emulation Tool Teradata Tools and Utilities Database Management WINDOWS Release 14.00.01 DVD Teradata Visual Explain Teradata Tools and Utilities Database Management WINDOWS Release 14.00.01 DVD Teradata Wallet Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD Teradata WebSphere MQ Access Module Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD Teradata Workload Analyzer Teradata Tools and Utilities Database Management WINDOWS Release 14.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 13.00.xx B035-3119-088K, Teradata Tools and Utilities 13.00.xx Supported Platforms and Product Versions 13.10.xx B035-3119-050K, Teradata Tools and Utilities 13.10.xx Supported Platforms and Product Versions 14.00 B035-3119-071K, Teradata Tools and Utilities 14.00 Supported Platforms and Product Versions Teradata Tools and Utilities for Microsoft Windows Installation Guide 13 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD 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). .NET Data Provider for Teradata Microsoft .NET Framework applications use .NET Data Provider for Teradata for uniform and standard-based (ADO.NET) access to the Teradata Database. 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. OLE DB Provider for Teradata A set of Component Object Model interfaces and objects that provides applications with uniform, standard access to any data store. In this case, the data store is in the Teradata Database. OLE DB Provider for Teradata allows access to data stores that do not use Structured Query Language. Using this product, an application requests database information from an intermediate program, which in turn accesses the Teradata Database. The intermediate program receives the response from the Teradata Database and returns a copy of the desired data to the application. Shared ICU Libraries for Teradata A library of routines based on the IBM International Components for Unicode version 3.6. The library provides Unicode support. Teradata Administrator Provides graphical interface to the Teradata Database Data Dictionary for performing database administration tasks on the Teradata Database. 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. 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 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. 14 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Description 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 in C language. It provides enhanced security services interfaces between Teradata network clients and the Teradata Database. Teradata Index Wizard Allows a Teradata Database administrator to create or identify a workload, perform index analysis for a workload, and verify and apply index recommendations to increase efficiency and maximize system performance. 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 OLE DB Access Module Teradata FastLoad, Teradata FastExport, Teradata MultiLoad, Teradata Parallel Data Pump, Teradata Parallel Transporter, Basic Teradata Query), and data sources for which an OLE DB provider is available. The access module quickly moves data between an OLE DB data sources and the Teradata Database without the requirement for intermediate storage. 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. The following Teradata Parallel Transporter Operators are installed as part of the Teradata Parallel Transporter Base: • Data Connector Operator • DDL Operator • Export Operator • FastExport OUTMOD Adapter Operator • FastLoad INMOD Adapter Operator • Load Operator • MultiLoad INMOD Adapter Operator • ODBC Operator Teradata Tools and Utilities for Microsoft Windows Installation Guide 15 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Description • • • • • • • • • Operator Support Library OS Command Operator Schema Mapping Operator SQL Inserter Operator SQL Selector Operator Teradata Parallel Transporter API Teradata Parallel Transporter ICU Library Teradata Parallel Transporter Wizard Update Operator 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 Performance Monitor Object Presents a snapshot of the detail Session and Resource usage on the Teradata Database. Teradata Query Scheduler Administrator Enables the database administrator to manage workloads submitted to the Teradata Database. Teradata Query Scheduler Client Submit scheduled SQL requests to Teradata Query Scheduler Server and also view information about your scheduled jobs. Teradata Query Scheduler Server The Teradata QS server components save, process, and execute Teradata Query Scheduler Client requests that have been scheduled. Teradata SQL Assistant A Windows-based information discovery tool designed to retrieve, manipulate, and store data from ODBC-compliant database servers. Teradata Statistics Wizard A graphical tool that can improve the performance of queries and, as a result, the entire Teradata Database. It reduces the time to collect data and eliminates the need for constant customizing. Teradata System Emulation Tool Emulates the Optimizer-generated data from a target system, generates query plans, and then imports that information to a test system where queries can be run without impacting the production system. Teradata Visual Explain Adds another dimension to the EXPLAIN modifier by visually depicting the execution plan of complex SQL statements in a simplified manner. It presents a graphical view of the statement broken down into discrete steps that show the flow of data during execution. 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 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). Teradata Workload Analyzer 16 Analyzes and generates candidate workloads from a Windows PC. Teradata Workload Analyzer provides three major areas of guidance: Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Description • • • Recommends workload group definitions. The database administrator guides these based on business knowledge and existing workload mix and characteristics Recommends appropriate workload goals Recommends workload to allocation group mapping plus priority scheduler weights Product Dependencies Product Teradata Tools and Utilities Dependencies Third-party Dependencies Basic Teradata Query Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client Named Pipes Access Module None None .NET Data Provider for None Teradata Microsoft .NET Framework Version 3.5 SP1 Redistributable Package or Microsoft .NET Framework Version 4.0 Redistributable Package ODBC Driver for Teradata Shared ICU Libraries for Teradata None OLE DB Provider for Teradata Shared ICU Libraries for Teradata Shared ICU Libraries for Teradata None None Teradata Administrator ODBC Driver for Teradata None Teradata Generic Security Services Client Teradata Generic Security Services Client Note: During the silent installation of the OLE DB Provider for Teradata package, when the user is part of the administrator group, but not an inbuilt administrator on Windows 7, Windows 2008 R2, or Windows Vista, a User Account Control dialog box appears. The dialog prompts you to allow the program to make changes to the computer. Click OK. Shared ICU Libraries for Teradata Teradata Generic Security Services Client Teradata Archive/ Recovery Utility Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client Teradata C Preprocessor2 Shared ICU Libraries for Teradata Teradata Tools and Utilities for Microsoft Windows Installation Guide None 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 Call-Level Interface version 2 Teradata Generic Security Services Client Teradata Call-Level Interface version 2 Shared ICU Libraries for Teradata None Teradata Data Connector None None Teradata FastExport Shared ICU Libraries for Teradata None Teradata Generic Security Services Client Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client Teradata FastLoad Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client Teradata Generic None Security Services Client None Teradata Index Wizard Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 or ODBC Driver for Teradata Teradata Generic Security Services Client Teradata JDBC Driver None JDK 1.4 , JDK 5.0, or JDK 6.0 Note: • JDK 5.0 is certified for Windows 32-bit. • JDK 5.0 is certified for Windows XP Professional x64 using EM64T. • JDK 6.0 is certified for Windows 64-bit. Note: The environment can be downloaded from Java Downloads. Teradata JMS Access Module None None Teradata Meta Data Services ODBC Driver for Teradata JRE 5.0 or JRE 6.0 32-bit Shared ICU Libraries for Teradata Note: The environment can be downloaded from Java Downloads. Teradata Generic Security Services Client Teradata MultiLoad Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector 18 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Teradata Tools and Utilities Dependencies Third-party Dependencies Teradata Generic Security Services Client Teradata OLE DB Access Module ODBC Driver for Teradata None Shared ICU Libraries for Teradata Teradata Generic Security Services Client Teradata Parallel Data Pump Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Data Connector Teradata Generic Security Services Client Teradata Parallel Transporter Base Shared ICU Libraries for Teradata Java 2 Runtime Environment 1.4.2_06 or later Teradata Call-Level Interface version 2 Note: The environment can be downloaded from Java Downloads. Teradata Generic Security Services Client Teradata Parallel Transporter Stream Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Generic Security Services Client Teradata Parallel Transporter Base Teradata Performance Monitor Object Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Generic Security Services Client Teradata Query Scheduler Administrator Shared ICU Libraries for Teradata Teradata Query Scheduler Client Shared ICU Libraries for Teradata Teradata Call-Level Interface version 2 Teradata Generic Security Services Client Teradata Query Scheduler Administrator has dependencies on TCP/IP and Ethernet drivers. Although the standard networking-enabled Windows installation includes a TCP/IP driver with WinSock support for Windows version 2.0 or later and an Ethernet driver that is compatible with the TCP/IP driver, ensure that these drivers are also on the Windows client system. None Teradata Call-Level Interface version 2 Teradata Generic Security Services Client Teradata Query Scheduler Server Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Generic Security Services Client Teradata Query Scheduler Client Teradata SQL Assistant Install at least one of the following: • .NET Data Provider for Teradata version 13.11 or later Teradata Tools and Utilities for Microsoft Windows Installation Guide If you use .NET Data Provider for Teradata to connect Teradata SQL Assistant to the Teradata Database, install dependencies in the following order: 19 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Teradata Tools and Utilities Dependencies Third-party Dependencies • 1. Microsoft .NET Framework Version 3.5 SP1 Redistributable Package 2. .NET Data Provider for Teradata version 13.11 or later. The Install Policy Files must be selected during the installation ODBC Driver for Teradata Note: Teradata SQL Assistant uses ODBC Driver for Teradata or .NET Data Provider for Teradata to connect to the Teradata Database. You can have ODBC Driver for Teradata and .NET Data Provider for Teradata version 13.11 or later installed concurrently. If you use ODBC Driver for Teradata to connect Teradata SQL Assistant to the Teradata Database, install dependencies in the following order: 1. Shared ICU Libraries for Teradata 2. Teradata Generic Security Services Client 3. ODBC Driver for Teradata Teradata Statistics Wizard Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 or ODBC Driver for Teradata Teradata Generic Security Services Client Teradata System Emulation Tool Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 or ODBC Driver for Teradata Teradata Generic Security Services Client Teradata Visual Explain Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 or ODBC Driver for Teradata Teradata Generic Security Services Client Teradata Wallet None None Teradata WebSphere MQ Access Module Teradata Data Connector IBM WebSphere MQ V5.2 Teradata Workload Analyzer Shared ICU Libraries for Teradata None Teradata Call-Level Interface version 2 Teradata Generic Security Services Client 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 ICU Libraries for Teradata • Teradata Call-Level Interface version 2 20 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD • 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 Platform Requirements Teradata Tools and Utilities software runs on an i386-based or greater computer which includes: • A network card • 800 MB of free disk space for a full installation Specific operating systems supported are listed in the B035-3119-071K, Teradata Tools and Utilities 14.00 Supported Platforms and Product Versions. Note: You must have administrator privileges for the computer where the software is to be installed. Note: The client computer must be able to communicate with a network-attached Teradata Database that is using the TCP/IP protocol with Winsock version 2.0 support. For an up-to-date description of which software the Teradata Database must be running, refer to B035-2029-071C, Teradata Tools and Utilities Release Definition Release 14.00. Table 1: Minimum Hardware Configurations Product Client Servers Teradata Performance Monitor Object Teradata Administrator Teradata Statistics Wizard Teradata Query Scheduler Administrator 500 MHz Pentium III 256 MB RAM 10 GB Hard Drive Media Drive 1024x768 Display 1.2 GHz Pentium 4 512 MB RAM 2*18 GB Hard Drive Media Drive 1024x768 Display Modem (required to use the Send a Page action of the Alerts facility) Teradata SQL Assistant 1 GHz Pentium 4 512 MB RAM Media Drive 1024x768 Display 100 MB free disk space Teradata Tools and Utilities for Microsoft Windows Installation Guide 21 Chapter 1 Prepare for Installation Introduction to Installing Teradata Tools and Utilities from DVD Product Client Servers OLE DB Provider for Teradata Minimum free disk space 3 MB for OLE DB Provider for Teradata 14 MB in the TEMP folder for temporary installation files Teradata Databases supported Teradata Database V2R6.2.x Teradata Database 12.0 Teradata Database 13.0, 13.10 Teradata Database 14.00 Table 2: Recommended Hardware Configurations Product Client Server Teradata Performance Monitor Object Teradata Administrator Teradata Statistics Wizard Teradata Query Scheduler Administrator 1.2 GHz Pentium 4 512 MB RAM 40 GB Hard Drive Media Drive 1280x1024 Display 2 GHz Pentium 4 1 GB RAM 2*30 GB Hard Drive Media Drive 1280x1024 Display Modem (required to use the Send a Page action of the Alerts facility) Teradata SQL Assistant 1.5 GHz Pentium 4 1 GB RAM Media Drive 1024x768 Display 200 MB free disk space 22 Teradata Tools and Utilities for Microsoft Windows Installation Guide CHAPTER 2 Uninstall Previous Software About Uninstalling Previous Versions of Teradata Tools and Utilities Software Before installing new Teradata Tools and Utilities software, all existing Teradata Tools and Utilities software must be uninstalled. 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.vbs, located in the \Windows 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. The uninstall script creates a uninstall_script_<TIMESTAMP>.log log file in the %TEMP% directory. It contains all the steps taken during execution. msi logging is turned on during package installation from the media. The msi uninstallation logs are stored as uninstall_<packagename>_<packageversion>.log in the %TEMP% directory. These logs provide useful information to support personnel if any issues are observed in the uninstallation of Teradata Tools and Utilities packages. 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, TDODBC, 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 requires the product parameter to execute. Without a parameter the script displays usage information. The uninstall script has been enhanced to support new options called /PRIORTOVERSION and /FORCE:TRUE. A version can be specified using the /PRIORTOVERSION option, such as / PRIORTOVERSION:14.00.00.00, as an argument to the script. The uninstall script Teradata Tools and Utilities for Microsoft Windows Installation Guide 23 Chapter 2 Uninstall Previous Software About Uninstalling Previous Versions of Teradata Tools and Utilities Software only uninstalls versions of the specified packages less than the /PRIORTOVERSION specified. When /PRIORTOVERSION option is not specified the default value is / PRIORTOVERSION:13.00.00.00. The default behavior handles uninstallations of Teradata Tools and Utilities packages, except corrupted installations which are handled using the /FORCE option. When this option is used the uninstall script performs an extensive registry search for all versions and components installed by a particular Teradata Tools and Utilities package and deletes them if found. This option should be used with care because it takes time to search the registry for versions and components of a package and, if multiple packages are passed as arguments, the script can take a long time to complete. When both options are specified, the /FORCE:TRUE option uninstall script performs uninstallation and cleanup of only the versions of the packages specified less than the / PRIORTOVERSION. The uninstall script must be executed as admin or with admin privileges, as it uses system packaging commands to remove packages. Uninstall Script Prerequisites To run the uninstall_TTU.vbs script the following software is required on the target machine. • Windows installer version must be 3.0 or above. {Type msiexec at command prompt to retrieve the windows installer version on the machine.} • Windows Script Host (WSH) version must be 5.6 or above. {Type cscript at the command prompt to retrieve the windows script host version on the machine.} Uninstall Script Usage and Parameters Usage Command Description cscript uninstall_TTU.vbs Prints out usage information cscript uninstall_TTU.vbs [Product] Any or all of the specified Teradata Tools and Utilities products can be passed as arguments to the script. Parameters Parameter Description [ Product ] Teradata Tools and Utilities products Teradata Tools and Utilities packages should be listed in order of dependency. The package names to be passed as arguments to the uninstall script are case sensitive and need to be specified exactly as indicated in the usage output. The following examples list the dependency order for CLI-based and TDODBC-based products. 24 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 2 Uninstall Previous Software About Uninstalling Previous Versions of Teradata Tools and Utilities Software Parameter Description Uninstalling BTEQ and its dependencies: C:\cscript uninstall_TTU.vbs BTEQ PIOM CLIv2 TDICU TERAGSS Uninstalling SQLA and its dependencies: C:\ cscript uninstall_TTU.vbs SQLA TDODBC TDICU TERAGSS The product names along with their corresponding parameter name and the dependency order of the Teradata Tools and Utilities packages is listed in the table below. /PRIORTOVERSION: xx.xx.xx.xx /FORCE:TRUE 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 / PRIORTOVERSION:14.00.00.00. The number parameter must contain all four pairs of digits, and can be specific enough to remove all packages before, for example, 14.00.00.01. Typically the last two pair of digits would just be 00.00. The /FORCE option removes all traces of the product by force. The default is /FORCE:FALSE. Table 3: Teradata Tools and Utilities Parameter Names and Package Order for Uninstallation This is the reverse order from installation. Product Name Parameter Name Teradata SQL Assistant Web Edition TSAW Teradata Manager TMGR Teradata Dynamic Workload Manager TDWM Teradata Administrator TDADMIN Teradata Workload Analyzer TWA Teradata Query Scheduler Client TQSCLIENT Teradata Query Scheduler Server TQSSERVER Teradata Query Scheduler Administrator TQSADMIN Teradata Statistics Wizard TSWIZ Teradata Index Wizard TIWIZ Visual Explain VECOMP Teradata System Emulation Tool TSET Teradata SQL Assistant SQLA JMS Access Module JMSAXSMOD Teradata Tools and Utilities for Microsoft Windows Installation Guide 25 Chapter 2 Uninstall Previous Software About Uninstalling Previous Versions of Teradata Tools and Utilities Software Product Name Parameter Name OLE DB Access Module OLEDBAXSMOD WebSphere Access Module MQAXSMOD Named Pipes Access Module NPAXSMOD C Preprocessor2 SQLPP OLE DB Provider for Teradata TDOLEDB TPump TPUMP Teradata Performance Monitor PMON FastExport FASTEXP MultiLoad MLOAD FastLoad FASTLD BTEQ BTEQ Data Connector PIOM ODBC Driver for Teradata TDODBC CLIv2 CLIv2 Shared ICU Libraries for Teradata TDICU Teradata GSS Client TERAGSS Manually Uninstalling Previously Installed Teradata Tools and Utilities Prerequisite: Because of dependencies between Teradata Tools and Utilities products, you must manually uninstall products in a specific order. Always uninstall the following products after all others, and use the following sequence: 1. 2. 3. 4. 5. 6. 7. 8. Teradata Query Scheduler Server Teradata Query Scheduler Client Teradata Data Connector ODBC Driver for Teradata .NET Data Provider for Teradata Teradata Call-Level Interface version 2 Teradata Generic Security Services Client Shared ICU Libraries for Teradata All remaining Teradata Tools and Utilities products can be uninstalled in any order. 1 Open a command prompt and type APPWIZ.CPL. 2 Click the product to remove. 3 Click Change/Remove. 4 Do one of the following: a If prompted to confirm the uninstallation of the product, click OK. 26 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 2 Uninstall Previous Software About Uninstalling Previous Versions of Teradata Tools and Utilities Software b If prompted to Repair or Remove, click Remove and then Next. 5 Click OK. 6 In the InstallShield Wizard, click Finish. Teradata Tools and Utilities for Microsoft Windows Installation Guide 27 Chapter 2 Uninstall Previous Software About Uninstalling Previous Versions of Teradata Tools and Utilities Software 28 Teradata Tools and Utilities for Microsoft Windows Installation Guide 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. .NET Data Provider for Teradata Prerequisite: You must install Microsoft .NET Framework 3.5 SP1 or later before you install .NET Data Provider for Teradata. 1 Determine the current version of Microsoft .NET Framework installed on the system by doing one of the following: • Open a command prompt and type APPWIZ.CPL. The version of Microsoft .NET Framework is displayed in the list of installed programs. • See the article How to determine which versions and service pack levels of the Microsoft .NET Framework are installed. 2 If the system does not have the correct version installed, download the Microsoft .NET Framework Version 3.5 SP1 Redistributable Package or Microsoft .NET Framework Version 4.0 Redistributable Package. 3 Select the Microsoft .NET Framework Redistributable Package for your platform. 4 Follow recommendations on the installation page for installing Microsoft .NET Framework. Teradata Parallel Transporter Base 1 Download and install Java 2 Runtime Environment 1.4.2_06 or later from Java Downloads. Teradata Parallel Transporter Wizard The Teradata Parallel Transporter Wizard software must use the 32-bit Java SE Runtime Environment (JRE) version 1.4.2_06 or later on the 32-bit and 64-bit Windows platforms, but the PATH to the JRE is not added automatically. On the 64-bit Windows platform, the Teradata Parallel Transporter Wizard cannot use the 64-bit JRE version. Teradata Tools and Utilities for Microsoft Windows Installation Guide 29 Chapter 3 Install New Software Installing Teradata Tools and Utilities 1 Download and install the 32-bit JRE from Java SE Downloads on the 32-bit or 64-bit Windows platform. 2 On a 64-bit Windows platform, add the path to the 32-bit JRE java.exe command to the front of the system PATH environment variable. Teradata Query Scheduler Administrator The standard networking-enabled Windows installation includes TCP/IP and Ethernet drivers. 1 Ensure that a TCP/IP driver with WinSock support for Windows version 2.0 or later and a compatible Ethernet driver compatible with the TCP/IP driver are installed on the Windows client system. Teradata SQL Assistant Prerequisite: You must install Microsoft .NET Framework 3.5 SP1 or later before you install Teradata SQL Assistant. 1 Determine the current version of Microsoft .NET Framework installed on the system by doing one of the following: • Open a command prompt and type APPWIZ.CPL. The version of Microsoft .NET Framework is displayed in the list of installed programs. • See the article How to determine which versions and service pack levels of the Microsoft .NET Framework are installed. 2 If the system does not have the correct version installed, download the Microsoft .NET Framework Version 3.5 SP1 Redistributable Package . 3 Select the Microsoft .NET Framework Redistributable Package for your platform. 4 Follow recommendations on the installation page for installing Microsoft .NET Framework. 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 When installing Teradata Tools and Utilities products other than with the main install, products must be installed in the following order. Using the main install will install all products and their dependencies in the correct order. Using an alternative method to do the install requires that the products be installed manually in the correct order: • Shared ICU Libraries for Teradata (tdicu) • Teradata Generic Security Services Client (teragss) 30 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Teradata Tools and Utilities • Teradata Call-Level Interface version 2 (cliv2) • ODBC Driver for Teradata (tdodbc) • .NET Data Provider for Teradata • Teradata Data Connector (piom) • Any other products Note: Client applications can cause a Window's Path overrun if the PATH system environment variable or a user environment variable exceeds 1024 characters, causing programs not to run. If the problem is encountered, upgrade the system to the latest service pack for Windows XP or install the Microsoft hotfix to increase the PATH size to 2048 characters. Note: A command line window appears during the installation of Teradata SQL Assistant. Do not close the window during the installation, it is required by the installation. Note: For ODBC on all platforms, because the installation process now 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 Note: When installing Teradata Tools and Utilities products from the media, all dependent products for your selection install in silent mode as part of the product installation. On a 64bit system, both 32-bit and 64-bit versions of the dependencies are installed. 1 Close all active Windows programs and disable any virus protection software running on the client computer. 2 Insert the Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD into the media drive. 3 In the Welcome to Teradata Tools and Utilities dialog box, click Install Product. Note: If the Welcome dialog box does not appear shortly after the media is inserted, use Windows Explorer to navigate to the main folder of the DVD. Double-click setup.bat to start the installation process. 4 In the Choose Setup Language dialog box, select the desired language, then click OK. Note: English and Japanese are the only languages currently supported. 5 In the Welcome dialog box, click Next. 6 In the Software License Agreement dialog box, read the agreement, then click Yes to accept it. 7 In the Setup Type dialog box, click Typical, then click Next. Note: If a previous version of the dependent products was not uninstalled, the install asks to overwrite the software. Click Yes to overwrite the software. 8 In the Choose Destination Location dialog box, if the default path shown in the Destination Folder block is acceptable, click Next. (Recommended) Teradata Tools and Utilities for Microsoft Windows Installation Guide 31 Chapter 3 Install New Software Installing .NET Data Provider for Teradata Note: To use a destination location other than the default, click Browse, navigate to the location where the files are installed, click OK, then click Next to end the procedure. Note: You must have write access to the destination folder, the Windows root folder, and the Windows system folder. Progress monitors appear during the installation process. No action is required. 9 In the Select Install Method dialog box, select the products to install silently, or clear the products to interactively install and then click Next. The products not highlighted are installed interactively. The product setup sequences is activated to make adjustments during installation. 10 In the Setup Complete dialog box, choose whether to view B035-2029-071C, Teradata Tools and Utilities Release Definition Release 14.00, then click Finish. Silently Installing Teradata Tools and Utilities Products from DVD You can silently install all Teradata Tools and Utilities products on the DVD with a single DOS command, except Meta Data Services, which is on its own DVD. Perform a silent installation as follows: 1 Close all active Windows programs and disable any virus protection software running on the client computer. 2 Uninstall previous versions of the Teradata Tools and Utilities software. 3 Insert the Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD into the media drive. 4 From a DOS window, change directory to the media drive. 5 Change directory to the Windows\TTU directory. 6 Run the command: setup.exe /s /f1"./setup.iss" Installing .NET Data Provider for Teradata About Installing .NET Data Provider for Teradata When you install .NET Data Provider for Teradata, you must perform several tasks: 1. Review security requirements for using Microsoft .NET Framework. 2. Uninstall the old version of .NET Data Provider for Teradata if it exists on your computer. 3. Check that the required version of Microsoft .NET Framework is installed on your computer. 4. Download and install the most recent version of .NET Data Provider for Teradata. 5. Verify the installation. 32 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing .NET Data Provider for Teradata The .NET Data Provider for Teradata has no dependencies on other Teradata Tools and Utilities client products. Understanding Security Requirements for .NET Data Provider for Teradata The Microsoft Developer Network Library provides extensive documentation for Microsoft .NET Framework. The following topics are recommended reading before you start developing applications to access the Teradata Database with Microsoft .NET Framework, Microsoft Visual Studio, and .NET Data Provider for Teradata: • ADO.NET Specification and .NET Data Providers at ADO.NET Overview • FullTrust permission set at Security in the .NET Framework • Additional security information at Administering Security Policy Known Issues for .NET Data Provider for Teradata The following installation issues are recognized for .NET Data Provider for Teradata. Suggestions are provided for working around the installation issues. • Installing a newer version of .NET Data Provider for Teradata without first uninstalling the older version, a side-by-side installation, is not recommended. If you uninstall any version of .NET Data Provider for Teradata after a side-by-side installation, the registry key HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\.NETFramework \AssemblyFolders\Teradata Data Provider is removed. In addition, Microsoft Visual Studio no longer lists .NET Data Provider for Teradata in the AddReference dialog box. To resolve this uninstallation issue after a side-by-side installation, do the following: 1. Open a command prompt and type APPWIZ.CPL. 2. In the list of installed programs, do one of the following for .NET Data Provider for Teradata depending on the Windows version: • Click Change, select Repair, and click Next • Right-click the item and click Repair • Use the FullTrust permission set of Microsoft .NET Framework to run .NET Data Provider for Teradata. Security in the .NET Framework provides more information about the FullTrust permission set. • For Microsoft Visual Studio 2008, note the following integration issues: • TableAdapter Query Configuration Wizard does not generate correct parameters for the INSERT Query type. Visual Studio 2008 Dataset bug provides more information about this issue. • TdDataAdapter Configuration Wizard does not generate unique names for commands. The wizard always generates the names SelectCommand, InsertCommand, UpdateCommand, and DeleteCommand for the corresponding instances of the TdCommand class. To configure more than one TdDataAdapter, change the name of auto-generated commands to prevent conflict with the command names generated for the first Teradata Tools and Utilities for Microsoft Windows Installation Guide 33 Chapter 3 Install New Software Installing .NET Data Provider for Teradata instance of TdDataAdapter. For example, if the first instance of TdDataAdapter uses the name SelectCommand, rename the second instance to SelectCommand1. Uninstalling .NET Data Provider for Teradata It is recommended to uninstall previous versions of .NET Data Provider for Teradata before installing the most recent version. 1 Open a command prompt and type APPWIZ.CPL. 2 If .NET Data Provider for Teradata appears in the list of installed programs and is older than the version you are installing, right-click the entry and select Uninstall or Change/ Remove, depending on the Windows version. 3 In the .NET Data Provider for Teradata - InstallShield Wizard dialog box, select Remove and click Next. 4 In the Maintenance Complete dialog box, click Finish. Installing Third-Party Microsoft .NET Framework Prerequisite: You must install Microsoft .NET Framework 3.5 SP1 or later before you install .NET Data Provider for Teradata. 1 Determine the current version of Microsoft .NET Framework installed on the system by doing one of the following: • Open a command prompt and type APPWIZ.CPL. The version of Microsoft .NET Framework is displayed in the list of installed programs. • See the article How to determine which versions and service pack levels of the Microsoft .NET Framework are installed. 2 If the system does not have the correct version installed, download the Microsoft .NET Framework Version 3.5 SP1 Redistributable Package or Microsoft .NET Framework Version 4.0 Redistributable Package. 3 Select the Microsoft .NET Framework Redistributable Package for your platform. 4 Follow recommendations on the installation page for installing Microsoft .NET Framework. Downloading .NET Data Provider for Teradata Prerequisite: You must be a registered user of Teradata Developer Exchange before you can download installation files for .NET Data Provider for Teradata. The executable file for .NET Data Provider for Teradata, along with a README in text format and a .zip archive of help files in .chm format, are available for download from Teradata Developer Exchange. 1 Go to .NET Data Provider for Teradata download files. 2 Click Sign In to log on to Teradata Developer Exchange. If you are not a registered user for the site, click the create an account link and complete the forms to register. 34 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing .NET Data Provider for Teradata 3 Click the link to download the executable file tdnetdp__windows_indep.<version>.exe. 4 Accept the license agreement. 5 [Optional] Click the link to download a .zip archive of the help files. 6 Accept the license agreement. 7 [Optional] Click the link to view the README in the browser. The README provides detailed information about this version of .NET Data Provider for Teradata as well as information on security requirements, supported platforms, development environments, and versions of the Teradata Database. Installing .NET Data Provider for Teradata 1 Browse to the installation file tdnetdp__windows_indep.<version>.exe that you downloaded. 2 Double-click the executable to launch the installer. 3 If the User Account Control dialog box prompts you to allow the program to make changes to the computer, click Yes. 4 In the Choose Setup Language dialog box, select the desired language, then click OK. Note: English and Japanese are the only languages currently supported. 5 In the Welcome dialog box, click Next. 6 Accept the default Destination Folder or select a different destination folder and click Next. • On 32-bit systems, the default installation folder is %ProgramFiles%\Teradata \NET Data Provider for Teradata\<version>\. • On 64-bit systems, the folder is %ProgramFiles(x86)%\Teradata\NET Data Provider for Teradata\<version>\. 7 Select one of the following in the Setup Type dialog box: • Complete to install all program files for .NET Data Provider for Teradata. • Custom to install all program files for .NET Data Provider for Teradata and include the following optional features: Feature Description Notes Microsoft Visual Studio 2010 Integration If Microsoft Visual Studio 2010 is installed on the system, .NET Data Provider for Teradata is integrated into Microsoft Visual Studio. Microsoft Visual Studio 2008 Integration If Microsoft Visual Studio 2008 is installed on the system, .NET Data Provider for Teradata is integrated into Microsoft Visual Studio. If Microsoft SQL Server Business Intelligence Integration with Microsoft Visual Studio products is selected by default if the installer detects that they are on the system. You can clear the option to integrate .NET Data Provider for Teradata with Microsoft Visual Studio if integration is not required. When integration is not selected, the installation time is shortened. Teradata Tools and Utilities for Microsoft Windows Installation Guide 35 Chapter 3 Install New Software Installing .NET Data Provider for Teradata Feature Description Notes Development Studio is also installed on the system, .NET Data Provider for Teradata is also integrated into the Development Studio. Publisher Policy A publisher policy assembly configures the policy that is used when the Microsoft .NET Framework runtime binds to an assembly. The publisher policy assembly is installed into the Global Assembly Cache. The Publisher Policy feature is selected by default. • Leave Publisher Policy selected if you are upgrading a previous version of .NET Data Provider for Teradata or other applications are installed that are dependent on an earlier version of .NET Data Provider for Teradata. • Clear Publisher Policy if no previous installations of .NET Data Provider for Teradata exist on the system and no other applications are dependent on an earlier version of .NET Data Provider for Teradata. Suppose you upgrade from version 01.02.00 to version 14.00.00 of .NET Data Provider for Teradata and you bind all existing applications to the 14.00.00 version. You must place the publisher policy assembly policy. 1.2.Teradata.Client.Provider.dll in the Global Assembly Cache to redirect (bind) an existing application built with the 01.02.00 version of .NET Data Provider for Teradata to the 14.00.00 version. 8 Click Install in the Ready to Install the Program dialog box. 9 [Optional] To display the readme file, select Show the readme file in the InstallShield Wizard Complete dialog box. 10 Click Finish to complete the installation. Verifying Installation of the .NET Data Provider for Teradata The complete installation of .NET Data Provider for Teradata includes an unsupported adhoc query tool NQuery.exe. Use this tool to test successful installation of .NET Data Provider for Teradata and to verify connection to a Teradata Database. 1 Navigate to %ProgramFiles%\Teradata\NET Data Provider for Teradata \<version>\ Samples\Bin\ or %ProgramFiles(x86)%\Teradata\NET Data Provider for Teradata\<version>\ Samples\Bin\, depending on the Windows platform. 2 Double-click NQuery.exe. 3 Select Connection > Connect. 4 Select .NET Data Provider for Teradata for the Data Provider. 5 Enter values in the Connection String box. The connection string is a semicolon-separated list of name=value pairs. It uses the format Data Source = DBC ; User Id = username ; Password = password ; where: • Data Source = DBC, the Teradata Database system name • User Id = username, the user name for the Teradata Database system 36 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Meta Data Services • Password = password, the password for the username For example, to connect to database vixen with user name jackieo and password sVnglass3s, type: Data Source = vixen ; User Id = jackieo ; Password = sVnglass3s ; 6 Click Connect. 7 Type Select Date; in the SQL Command pane and click Execute. The Teradata Database that you connect to returns the current system date in the Command Result pane. 8 Click Connection > Disconnect. 9 Click File > Exit. Installing Meta Data Services 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 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 Teradata Tools and Utilities for Microsoft Windows Installation Guide 37 Chapter 3 Install New Software Installing Meta Data Services Client Web Browser ASP Page HTTP Request HTML Page MetaManager/ MetaBrowse * Workstation/Laptop/Etc. with Supported Browsers (Windows PC) * Metasurf Intranet or Internet Active Server Engine MDS Com Interface + Engine MDS Engine HTML Page ODBC ODBC Teradata Database Windows Web Server 3118B001 MDS Repository * MDS Installed Teradata Server 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. 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. 38 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Meta Data Services Text Box Description 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 ICU Libraries 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. When configuring the ODBC DSN: • Make sure the Do not resolve alias name to IP address check box is not selected. • Select the Run in Quiet Mode check box. • Increase the Maximum Response Buffer Size to 65,477. 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 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. 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. Teradata Tools and Utilities for Microsoft Windows Installation Guide 39 Chapter 3 Install New Software Installing Meta Data Services 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 It is not necessary to uninstall the existing version of the Teradata Meta Data Services (MDS) software before installing a new version. To uninstall an existing version of Teradata MDS, follow this procedure: 1 Open a command prompt and type APPWIZ.CPL. 2 Select the Teradata MDS program to remove, then click Remove. 3 Answer any prompts that appear, then click Finish in the Complete screen. Installing Teradata Meta Data Services 1 Close all Windows programs before installing Teradata Meta Data Services (MDS). 2 Use a standard Windows executable setup file (for example, setup.exe) to start the installation. The setup file can be found on the Teradata MDS installation DVD, or you may be directed to access the setup file from another location. The setup file may be automatically launched from the DVD, or you may have to double-click it. 3 In the Choose Setup Language dialog box, select the installation language, then click OK. The Teradata Meta Data Services splash screen appears briefly. 4 In the Welcome screen, click Next to continue the installation. 40 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Meta Data Services 5 An Important Virus Message appears; read it, then click OK to continue the installation. 6 In the Welcome screen, click Next to continue the installation. 7 In the Choose Destination Location dialog box, click Next to accept the default location or Browse, then Next to choose a different location. The default location provided is one of the following: • The location where Teradata MDS was previously installed • The Program Files folder on the boot drive. If the boot drive is C:, the location is: C:\Program Files\Teradata\Teradata Meta Data Services 8 In the Choose MDS Log File Location dialog box, click Next to accept the default location or Browse, then Next to choose a different location. The default location is C:\mdslog. 9 In the Select Features dialog box, select the components to install, then click Next. Note: MDS Core Files is required and cannot be cleared. When MDS Development Kit is highlighted, the Change button becomes active and subcomponents of the development kit can be selected or deselected. The development kit contains files needed to develop applications that exchange information with Teradata MDS. Note: To develop Unicode-based programs with Teradata MDS, the MDS Development Kit options must be changed. The Web application MetaSurf must be installed on a Windows Web server system. If this is a new MetaSurf installation, a MetaSurf directory with all associated files and subdirectories will be installed in the directory containing Teradata MDS. Caution: MetaSurf files can be customized. Therefore, subsequent installations of Teradata MDS will display a message indicating that the MetaSurf files will be replaced or removed depending on whether the MetaSurf feature is selected or not. If the existing MetaSurf files are to be kept, they must be copied to another directory before proceeding with the installation. C:\Program Files\Teradata\Teradata Meta Data Services\metasurf After MetaSurf has been installed, the administrator must designate the start point for MetaSurf on the Web server. This can be done using the IIS Manager to create a virtual directory or web application. Refer to the Microsoft Internet Information Services (IIS) documentation. If Teradata MDS is reinstalled on a system that is used as a Web Server for MetaSurf, the following error appears if Microsoft Internet Information Services (IIS) is not restarted before the installation. Restart IIS to clear the dlls from memory and reinstall MetaSurf software components. An error occurred during the datamove process - 115 Component: MDSCore FileGroups:basic Teradata Tools and Utilities for Microsoft Windows Installation Guide 41 Chapter 3 Install New Software Installing Meta Data Services File:<installdir>/metasurf During a reinstallation, if new MetaSurf files are not installed, it is because Teradata MDS does not overwrite existing MetaSurf files. The installation will display a warning message. Move the current MetaSurf folder to a different location or uninstall Teradata MDS before installing a new release. To enable the Automatic DIM Update feature, select and install the DIM Update files on your designated DIM Update Server. The DIM Update files should be installed on only one server in the network. 10 In the Meta Data Services Repository Connection Information dialog box, enter the information Teradata MDS will use to connect to the Teradata MDS repository, then click Next. The following information is saved in the Windows registry. Text Box Required/ Optional Description Data Source Name Required Enter the DSN to use to connect to the Teradata MDS repository. The DSN specified must be configured as a System DSN in ODBC Administrator. User Name Required Enter the user name Teradata MDS will use to log on to the Teradata Database. The User must have permissions to access the Teradata Database MDS tables. Database Password Required Enter the password Teradata MDS will use to log on to the Teradata Database. Database Name Optional Enter the name of the Teradata Database containing the Teradata MDS repository. If the Database Name is omitted, the database defaults to the default database specified in the DSN. If a default database is not specified in the DSN, the database defaults to the user’s default database in Teradata. 11 In the Select Program dialog box, choose the name of the Windows program folder in which to store the Teradata MDS start-up shortcuts, then click Next. The default folder is Teradata Meta Data Services. 12 In the Start Copying dialog box, review the summary of the installation selections, then click Back to change the selections or click Next to begin copying the installation files. When the files begin copying, an indication of the progress of the installation appears. 13 In the InstallShield Wizard Complete dialog box, select Yes, I want to view the readme file now to view the Readme.txt file before clicking Finish to complete the setup. 14 If performing additional Teradata MDS installations, repeat this process for each workstation or server. 42 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Meta Data Services Teradata Meta Data Services Configuration Configuring the Windows Registry for Teradata Meta Data Services The local Teradata Meta Data Services (MDS) configuration parameters are stored in the Windows Registry. 1 To change the Windows Registry settings, log onto the Windows system as a user who has permission to update the Windows Registry. Note: Users who are only members of the Guests group are not allowed to change the settings. 2 In the Windows Control Panel, click MDS Configuration. 3 In the Teradata Meta Data Services Configuration dialog box, MDS Configuration tab, go to Start > Programs > Teradata Meta Data Services > MetaManager. 4 In the Teradata Meta Data Services MetaManager Logon dialog box, click Configure. Note: If the default name was not selected during installation, find the specified name for the Teradata MDS program group to launch MetaManager. Setting Database Connection Information 1 In the Teradata Meta Data Services Configuration dialog box: a At Data Source Name, enter the ODBC system Data Source Name (DSN) to use to connect to the Teradata Database System containing the Teradata Meta Data Services (MDS) repository. b At Database User Name, enter the user name that Teradata MDS will use to log onto the Teradata Database System. The user must have specific permissions for various actions: • The user must have permission to access the Teradata MDS database tables. • To browse the Teradata MDS repository, SELECT privileges to the database containing the Teradata MDS repository are required. • To load or update the Teradata MDS repository, INSERT, UPDATE, and DELETE privileges are required. • To create an Application Information Metamodel, CREATE TABLE privileges are required. • To create the Teradata MDS repository, GRANT ALL PRIVILEGES privileges are required. c At Database User Password, enter the password that Teradata MDS will use to log onto the Teradata Database System. d At Database Name, enter the name of the Teradata Database within the Teradata Database System where the Teradata MDS repository is stored. This can be the same as the Database User Name. If omitted, the Database Name defaults to the default Database Name in the ODBC DSN for that Teradata Database System where the database is housed. Teradata Tools and Utilities for Microsoft Windows Installation Guide 43 Chapter 3 Install New Software Installing Meta Data Services Note: If the DSN does not have a default Database Name, the connection is made to the default database of the Database User. e Click Apply or OK to save your changes to the registry. Note: If you are connected to MetaManager when changes to these settings are made, they will not take effect until the next time MetaManager is run. Setting Logging and Tracing Levels The logging and tracing levels only apply to the local system, where a Teradata Meta Data Services (MDS) application is running. They can be changed at any time. Changes are immediately written to the registry of the local system. Teradata MDS applications only read the log and trace level settings on start up, so you must restart the application for the new settings to take effect. To change the settings for MetaSurf, restart the web server. 1 In the Teradata Meta Data Services Configuration dialog box, choose the Logging tab. • The following table shows the Logging Level options available. The Logging Level controls the log messages written to the Teradata MDS log file. The default is Warning. Table 4: Logging Level Options Level Description Critical Logs Critical messages Error Logs Error and Critical messages Warning (default) Logs Warning, Error and Critical messages. Warning is the default logging level Information Logs Information, Warning, Error and Critical messages All Logs Debug, Information, Warning, Error and Critical messages • The following table shows the Tracing Level options available. The Tracing Level controls the type of messages traced and written to the standard error output. The Tracing Level and error output are primarily used when writing an application using the Teradata MDS APIs. The default is Disable. Table 5: Tracing Level Options 44 Level Description Disable (default) No messages are traced Critical Traces Critical messages Error Traces Error and Critical messages Warning Traces Warning, Error and Critical messages Information Traces Information, Warning, Error and Critical messages All Traces Debug, Information, Warning, Error and Critical messages Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Meta Data Services • The read-only log file name is meta_yyyymmdd.txt (where yyyy = year, mm = month, dd = day). The date in the log file name is the date the log entries were written. Teradata MDS creates a new log file each day. The log does not wrap. Old log files should be deleted by the Teradata MDS Administrator. To see previously generated log files (names and file sizes in bytes), click Log Files Manager. View or delete the logs in this window. 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 Go to Start > Programs. 2 Click Teradata Meta Data Services (or the Program Group name specified during installation). 3 Click Create MDS Repository. 4 Choose one of the following: • Click Create without versioning, which is the default, to run the metacreate program and create a Teradata MDS repository without versioning support. • Click Create with versioning to run the metacreate program and create a Teradata MDS repository with versioning support. 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 Teradata MDS repository in that environment. 4 Migrate the Teradata MDS repository to the same version as the client. a Go to Start > Programs. b Click Teradata Meta Data Services (or the Program Group name specified during installation). c Click Migrate MDS Repository. Teradata Tools and Utilities for Microsoft Windows Installation Guide 45 Chapter 3 Install New Software Installing Meta Data Services • Click Migrate without versioning to invoke the metamigrate program in an MSDOS window and migrate a Teradata MDS repository without versioning enabled. This is the default. • Click Migrate with versioning to invoke the metamigrate program in an MS-DOS window and migrate a Teradata MDS repository with versioning enabled. Caution: If migrating a versioned repository to a non-versioned repository, only the latest version of each object is migrated. All previous versions are removed and cannot be recovered. d Enter the MDS Administrator username and password (unless changed, it is metasu). 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. Creating a Virtual Directory or Web Application After MetaSurf is installed, define a virtual directory or web application to MetaSurf on the web server. See the Teradata Meta Data Services (MDS) Readme.txt file for information on configuring the Web Server. 1 When creating a virtual directory or web application, select an alias name for MetaSurf such as: http://www.<yourhostname>/<mds> or http://<yourhostname>/<mds> where yourhostname is the name of the system and <mds> is the virtual name assigned for MetaSurf. Note: When changes are made to the Teradata ODBC DSN or Teradata MDS configuration, web services may need to be restarted before the changes to take effect. For complete information on setting up a web server, starting and stopping web services, and using IIS manager to create a virtual directory or web applications, refer to the web server documentation. See the Readme.txt file for more information. 2 Change the appearance of the MetaSurf web pages by modifying the style sheets used or defining new style sheets and incorporating them into MetaSurf. Style sheets, defined by the World Wide Web Consortium (W3C), allow you to describe the appearance of individual HTML tags. The style sheet tags describe the font, color, paragraph alignment, and other attributes for common HTML tags such as headings, paragraphs, lists, and tables. Style sheets separate the style and layout of HTML from the informational content. 46 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Meta Data Services 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. 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. Teradata Tools and Utilities for Microsoft Windows Installation Guide 47 Chapter 3 Install New Software Installing Meta Data Services Feature Description 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 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. MDS Recovery Tables 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). Database Connection Information 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. DDL Gateway User Accounts The Teradata MDS DDL Gateway uses the Teradata user names specified in the MetaManager system configuration to connect to Teradata Database systems. The Teradata MDS DDL Gateway runs as a service. A service can run as the LocalSystem Account or as a specified account name and password. If the Teradata MDS repository Database Configuration is configured for Teradata Single Sign On (SSO) where no username and password is specified, the Teradata MDS DDL Gateway Service must not be configured to run with the LocalSystem Account. If the Teradata MDS repository Database configuration is configured for SSO where no username and password is specified, there must be a Teradata user account with the same name as the user account in which the Gateway is run. 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. 48 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Meta Data Services • 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 Description Teradata Database System 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. 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 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. DDL Gateway Server 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 Teradata Tools and Utilities for Microsoft Windows Installation Guide 49 Chapter 3 Install New Software Installing Meta Data Services Feature Description 5. Sends a message to the Teradata Database to start sending DDLs to RSG 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 Teradata installation and version switch programs install the RSG component; there is no need to install the software. 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. Adding the Relay Services Gateway vprocs 1 Use the PUT utility to add the RSG vprocs to the appropriate nodes. The services file is automatically updated with the following values: TxServer 56969/tcp #MDS Gateway Server RSiMsg 56970/tcp #RSG Server The RSG vproc on the RSG master node should have id 9215. 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 RSG startup.txt file and is 4. The RSG partition is 19. 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. 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 50 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Meta Data Services 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 There is an Event Viewer log entry indicating that 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 B035-3118-071A, Teradata Meta Data Services Administrator Guide. 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. Teradata Tools and Utilities for Microsoft Windows Installation Guide 51 Chapter 3 Install New Software Installing Meta Data Services 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. 52 Load Description All 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. Selected 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. All but Selected 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. Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing Meta Data Services 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 B035-3118-071A, 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. 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: Teradata Tools and Utilities for Microsoft Windows Installation Guide 53 Chapter 3 Install New Software Installing Meta Data Services Name Description System Name System chosen DIM Update Status 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 Database Out of Sync List of database names the DDL Gateway has marked out of sync, including those that were in the MDS Recovery Table Refresh List Updates the display Sync Now 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 Teradata Meta Data Services (MDS) 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 Program Name Gateway Server gwserver.exe Gateway Client gwclient.exe Integrity Servers iserver.exe 1 To manually start or stop the DDL Gateway, use the Services Administrative Tool. Note: The DDL Gateway processes are not started at installation. Note: On initial installation of the DDL Gateway, 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-523|5|CGwaySocket::Get HostByAddr(153.64.14.126) 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. 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.exe. 54 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Teradata Developer Exchange 1 To manually start or stop the Teradata MDS Action Processor, use the Services Administrative Tool. 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 6: 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 7: Tools Product Teradata SQL Assistant Java Edition Teradata Plug-in for Eclipse Teradata Tools and Utilities for Microsoft Windows Installation Guide 55 Chapter 3 Install New Software Teradata Software Server Downloading a Product from the Teradata Developer Exchange 1 Go to Teradata Developer Exchange. 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 patch file was saved. The files are saved in .zip format on your client. 2 Read the *.txt readme file to determine further installation instructions. 3 Uninstall previous versions of the product. 4 Extract the package files to the folder. 5 Run the setup.exe file to install the software. Note: Install any dependencies listed first. 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. 56 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 3 Install New Software Installing the Windows Help Program 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 @ 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. 6 In the Client Patches dialog box, select the check boxes for the software patches to download. 7 Select Current to filter the list of available software for the most recent release or All to display all versions of the software for the software base. 8 Click Submit. 9 Select the Download Type and the Download Readme Files (if desired), enter your User Name and E-Mail, then click Submit. 10 Click Download. 11 Click Save. 12 Specify a save-to location and click Save to start the download. Installing Downloaded Patches 1 Go to the location where the patch file was saved. The files are saved in .zip format on your client. 2 Read the readme.txt file in the *.zip file to view further installation instructions. 3 Uninstall previous versions of the package. 4 Extract the package files to a folder. 5 Run the setup.exe file to install the software. Note: Dependencies are installed first. Installing the Windows Help Program This task must be performed for all clients that are running Windows 7, Windows Vista, or Windows Server 2008. The application is necessary to run online help files with a .HLP extension. 1 Install Teradata Tools and Utilities software before proceeding. Teradata Tools and Utilities for Microsoft Windows Installation Guide 57 Chapter 3 Install New Software Installing the Windows Help Program 2 Go to Microsoft Support (Windows Help). 3 In the Search box, type WinHlp32.exe to locate the WinHlp32.exe file. Note: Windows Vista users must pass a short validation process before downloading the file. Once validated, specific instructions are given for obtaining the download. 4 Run the executable. 58 Teradata Tools and Utilities for Microsoft Windows Installation Guide CHAPTER 4 Configure New Software About Setting Up Network Parameters The Internet address and the symbolic names for the Teradata Database are considered the network parameters. It is assumed that network software is installed correctly. About Configuring Teradata Call-Level Interface version 2 The following parameters must be set for Teradata Call-Level Interface version 2 to work properly: Network Parameters Setting the correct network parameters guarantees that Teradata Call-Level Interface version 2 communicates with the target Teradata Database. These parameters must be set correctly to use the software. Environment Parameters The environment parameters provide Teradata Call-Level Interface version 2 with parameter file location information, as well as the facility for enabling Teradata Call-Level Interface version 2 to run in parallel mode. Teradata strongly recommends that you set the environment parameters. System Parameters The Teradata Call-Level Interface version 2 system parameters are used internally by Teradata Call-Level Interface version 2 to customize services and features. Setting system parameters is only necessary if there are special requirements that the default setting cannot meet. Verifying the Existence of hosts File 1 Verify the hosts file is located in %Program Files%\Teradata\Client \<version>\Teradata Parallel Transporter. 2 If running a Name Server, verify the hosts file is on the Name Server and that network software is configured to access the Name Server. Teradata Tools and Utilities for Microsoft Windows Installation Guide 59 Chapter 4 Configure New Software Identifying a Teradata Database The Teradata Tools and Utilities software uses generic TCP/IP GetHostByName services. 3 If not running a Name Server, verify the hosts file contains a list of all systems on the LAN that can be accessed. The Teradata Database must be identified in this file if a system is going to communicate with it. A hosts file exists on each computer system in the network. Identifying a Teradata Database 1 Identify each TCP/IP Communications Processor (COP), Applications Processor (AP), or UNIX node running the Teradata Gateway that the client computer will be communicating to the Teradata Database. In the table below, AP refers to all of the following: • TCP/IP Communications Processor (COP) • Applications Processor (AP) • Node running the Teradata Gateway 2 Make an entry in the hosts file for each TCP/IP Communications Processor (COP), Applications Processor (AP), or UNIX node running the Teradata Gateway. The following table includes the entries to the hosts file. Platform hosts File Entries Teradata Database on an AP platform (System 3600) APs Teradata Database on a V2 computer (UNIX) nodes Adding Entry to hosts File 1 Once the Application Processor (APs) are identified, use a text editor to open the client hosts file and add or edit the AP entries. Use the following syntax when adding entries to the hosts file: <a.b.c.d> <dbcnameCOPn> [aliasCOPn] a.b.c.d The Internet address is a four-byte numeric value that identifies an AP and its location on the network. An Internet address is assigned to each AP when the Teradata Database is configured. dbcname The Teradata Database using the AP is 1 to 8 characters in length. The first character must be alphabetic; where the remaining characters can be alphanumeric. The System Parameter Block file, %Program Files%\Teradata\Client\<version>\clispb.dat, lists dbc as the default dbcname. dbc can be assigned as the dbcname of a Teradata Database with which the client computer communicates. This simplifies network debugging and avoids problems when name servers become available. If the client computer communicates with more than one Teradata Database on the same TCP/IP LAN, use dbc as the dbcname for the more heavily used Teradata Database. Any other names can be used for any remaining Teradata Databases. 60 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 4 Configure New Software About Setting Up Environment Parameters COPn The parameter that assigns a number to a particular AP that the Teradata Database uses. COP is a fixed string of characters that must always be specified. The value of n can range from 1 to the total number of "APs" in a COP group. A COP group is a set of "APs" that operates together for a particular Teradata Database. "APs" in the same COP group share session balancing and session recovery. Each AP within a COP group must be assigned a unique number starting with 1. aliasCOPn The alias name, specifies an alternate name for a Teradata Database AP. Its use is optional. More than one aliasname is permitted. An aliasname need not be unique across a network, but the hosts file for a computer must not contain the same aliasname for more than one AP. Suggestion: the n in each alias COPn equals n in the corresponding dbcname COPn. For example, a client computer accesses one Teradata Database (named dbc) through two TCP/IP APs with addresses 101.0.0.21 and 101.0.0.22 on the same logical TCP/IP LAN. Each AP is assigned two alias names. The following lines show example entries in the hosts file for the two APs: 101.0.0.21 dbcnode1 dbccop1 tdcop1 101.0.0.22 dbcnode2 dbccop2 tdcop2 About Setting Up Environment Parameters Environment parameters allow the runtime environment to be specified for each Teradata Tools and Utilities user. On Windows systems, if system environment parameters are changed, the client computer must be rebooted for the changes to take effect. It is not sufficient to restart the daemon, or to log off and log on again. Defining Paths to System Files 1 Define the path to the Teradata Call-Level Interface version 2 system parameter block file by setting the COPLIB environment parameter. COPLIB is the path to the Teradata Call-Level Interface version 2 system parameter block file, clispb.dat. 2 Define the path to the Teradata Call-Level Interface version 2 anomaly log file by setting the COPANOMLOG environment parameter. COPANOMLOG is the path to the anomaly log file, a trace log file displaying Teradata Call-Level Interface version 2 activities, including network-related error information. This environment variable should be defined only for debugging purposes. Setting Up Environment Variables 1 Open a command prompt and type SYSDM.CPL to open the System Properties dialog box. 2 Click the Advanced tab. Teradata Tools and Utilities for Microsoft Windows Installation Guide 61 Chapter 4 Configure New Software Speeding Up the Logon Process 3 Click Environment Variables to add a new variable or edit an existing variable. Speeding Up the Logon Process 1 Increase the speed of the logon process by limiting the number of host name resolution requests issued by the applications. This is done by setting an environment variable with the name equal to the machine name with a specified number of COPS available for it. set <machine_name>=<cops> <machine_name> name of the PC <cops> number of COPS 2 Open a command prompt and type SYSDM.CPL to open the System Properties dialog box. 3 Click the Advanced tab. 4 Click Environment Variables and add or edit the <machine_name> System variable. 5 Set the SHOGUN System variable to 3 as follows: set SHOGUN=3 Setting SHOGUN=3 causes CLIv2 to issue GetHostByName for SHOGUNCOP1, SHOGUNCOP2, and SHOGUNCOP3 only. If one of the GetHostByName requests fails, the successive requests are not issued. 6 Add or edit the SHOGUN System variable. Setting Up the Port Number, Netrace, and Threadlogging 1 Specify the port number (nnnn) used by the Teradata Tools and Utilities software by setting the System variable TDMSTPORT as follows: set TDMSTPORT=nnnn 2 Open a command prompt and type SYSDM.CPL to open the System Properties dialog box. 3 Click the Advanced tab. 4 Click Environment Variables and add or edit the TDMSTPORT System variable. 5 Enable Detailed COPANOMLOG Logging by setting up the System variable NETRACE as follows: set NETRACE=1 Setting NETRACE=1 enables detailed network information between the client computer and the Teradata Database server. This information is logged in to the file defined in the environmental setting COPANOMLOG. 62 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 4 Configure New Software Setting Up System Parameters 6 Add or edit the NETRACE System variable. 7 Enable Multiple COPANOMLOG File Creation by setting up the System variable THREADLOGGING as follows: set THREADLOGGING=1 Threadlogging supports multi-threaded Windows applications. Multi-threaded logging is enabled by setting THREADLOGGING=1. For example, if COPANOMLOG is c: \temp\coplog and THREADLOGGING is enabled, logs are created as c:\temp \coplog0.txt, c:\temp\coplog1.txt, and so on through c:\temp \coplogn.txt. Each thread that uses a CLI connection creates its own individual log file. 8 Add or edit the THREADLOGGING System variable. Setting Up System Parameters 1 Edit the clispb.dat file to meet system requirements. The clispb.dat file (the Teradata Call-Level Interface version 2 System Parameter Block) contains default values for variables used by CLI application programs. In the clispb.dat file, the Teradata Database sets the initial values to duplicate the Teradata Call-Level Interface version 2 internal defaults. 2 Refer to B035-2418-071A, Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems for more information. clispb Data Information The clispb.dat file (the Teradata Call-Level Interface version 2 System Parameter Block) contains default values for variables used by CLI application programs. In clispb.dat, the Teradata Database sets the initial values to duplicate the Teradata Call-Level Interface version 2 internal defaults. Overview of Configuring ODBC Driver for Teradata To use the ODBC Driver for Teradata, you must first configure the ODBC driver and an ODBC data source. Configuring ODBC Driver for Teradata 1 Complete procedures to configure the ODBC Driver for Teradata are included in B035-2509-071A, ODBC Driver for Teradata User Guide. Teradata Tools and Utilities for Microsoft Windows Installation Guide 63 Chapter 4 Configure New Software Overview of Configuring ODBC Driver for Teradata Configuring ODBC Driver for Teradata Data Source Use the Microsoft ODBC Data Source Administrator program installed on the workstation to define a data source for Teradata Administrator, Teradata SQL Assistant, Teradata Parallel Transporter, and any third-party or customer-developed applications that use ODBC Driver for Teradata to communicate with Teradata Database. 1 From the Windows desktop, select Start > Control Panel > Administrative Tools > Data Sources (ODBC). 2 In the ODBC Data Source Administrator dialog box, from the drop down, select the type of data source to create User DSN A data source name that is visible only to you. System DSN A data source name that is visible to any user on this machine. Either data source name type is usable only on the machine where it is created. 3 Click Add. 4 In the Create New Data Source dialog box, select Teradata and click Finish. 5 In the ODBC Driver Setup for Teradata Database dialog box, enter information on the location of the database and the connection parameters to be used when establishing a connection. a Data Source Group: for Name, enter any name you want to give to the data source being created. b Data Source Group: for Description, enter a description that describes the data source name used. c Teradata Server Info Group: For Name(s) or IP address(es), Enter the names or IP addresses of each LAN-connected node in your system, one per line. Entering only the first node name or IP address causes the client to communicate only with that node or IP address and can decrease system performance significantly. You must define any names entered here in either Domain Name Services (DNS) or the local hosts file. The hosts file is located in the system32\drivers\etc subdirectory of the directory in which Windows is installed. Never enter both a name and an IP address. d Authentication Group: For Use Integrated Security, ensure that this option is not selected. It refers to single sign-on. e Authentication Group: For Mechanism, choose TD2 unless otherwise mandated by your site. For more information, see B035-1100-111A, Security Administration. f Authentication Group: For Parameter, leave this blank. It is optional for the TD2 mechanism. g Authentication Group: For Username, enter a user name valid for the Teradata Database specified in the Data Source Name. 64 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 4 Configure New Software About Configuring Teradata Query Scheduler Administrator h Authentication Group: For Password, leave this field blank. The system will prompt you for a password. The only exception is if you need to run an application in batch mode that requires the ODBC Driver for Teradata (such as Teradata SQL Assistant). i Optional Group: For Default Database, enter the default database name. If the Default Database is not entered, the Username is used as the default. All tables, views, and macros are assumed to be in this default database unless explicitly prefixed by a database name in the query. j Optional Group: For Account String, enter one of the accounts that the DBA assigned to the Username when it was created. k Session Character Set Group: For Session Character Set, choose the character set. The default is ASCII. l Optionally, you can now configure ODBC Driver for Teradata Options or Teradata ODBC Driver Advanced Options. Teradata strongly recommends that you do not change the settings in the Teradata ODBC Driver Advanced Options dialog box. 6 Click OK to complete configuring ODBC. Note: If you need to change your ODBC connection later, you can enter the change in the configuration screen for any ODBC-enabled utility, such as Teradata Administrator by clicking File > Define Data Source > Configure, rather than in the ODBC Driver for Teradata. The change is automatically entered in the ODBC configuration and is in effect for all ODBC-enabled utilities installed on that machine. About Configuring Teradata Query Scheduler Administrator Starting with Teradata Tools and Utilities Release 13.10.00, before using Teradata Query Scheduler Administrator for the first time, you must run the tqssetup.bteq script included in the Teradata Query Scheduler Administrator package. This creates the required scheduling tables on the Teradata Database. Default Communications, as well as Client and Server configuration parameters are changeable within the program. For more information, refer to B035-2511-071A, Teradata Query Scheduler Administrator Guide and B035-2512-071A, Teradata Query Scheduler User Guide. Modifying the HOSTS File Prerequisite: If your site does not use DNS, you must define the IP address and the Teradata Database name to use in the system HOSTS file on your workstation. 1 Locate the file hosts on your computer. This file is typically located at %SystemRoot% \system32 \drivers\etc. 2 Open the file with a text editor, such as Notepad. 3 Add the following entry to the file: xxx.xx.xxx.xxx sssCOP1 where xxx.xx.xxx.xxx is the IP address and sss is the Teradata Database name. Teradata Tools and Utilities for Microsoft Windows Installation Guide 65 Chapter 4 Configure New Software Configuring Teradata Query Scheduler Client 4 Save the hosts file. Configuring Teradata Query Scheduler Client 1 Starting with Teradata Tools and Utilities Release 13.10.00, before using Teradata Query Scheduler Client for the first time, you must run the tqssetup.bteq script included in the Teradata Query Scheduler Administrator package. This creates the required scheduling tables on the Teradata Database. Default Communications, as well as Client and Server configuration parameters are changeable within the program. For more information, refer to B035-2511-071A, Teradata Query Scheduler Administrator Guide and B035-2512-071A, Teradata Query Scheduler User Guide. About Configuring Teradata Query Scheduler Server To start the Teradata Query Scheduler Server, you must first configure database logon credentials using the Teradata Query Scheduler Operations Utility. For more information, refer to B035-2512-071A, Teradata Query Scheduler User Guide. Specifying a Default Teradata Query Scheduler Server Teradata Query Scheduler Viewer temporarily establishes a Teradata Database session using Teradata Call-Level Interface version 2 to validate the logon parameters and find the location of an active Teradata Query Scheduler Server. If Teradata Call-Level Interface version 2 cannot establish a session, or if there is an application that accesses the Teradata Query Scheduler Client library functions directly, a default Teradata Query Scheduler Server location can be configured. 1 Use the Teradata Query Scheduler Client library functions to configure the location. See Changing Default Server Information in B035-2512-071A, Teradata Query Scheduler User Guide for instructions. After a default Teradata Query Scheduler Server is configured, begin using the Teradata Query Scheduler Viewer or the Teradata Query Scheduler Operations utility. If working with various character sets, continue with Working with Character Sets in B035-2512-071A, Teradata Query Scheduler User Guide. To learn how to start using the Teradata Query Scheduler Operations utility, see Working with the Teradata Query Scheduler Operation Utility in B035-2512-071A, Teradata Query Scheduler User Guide. See Getting Started in B035-2512-071A, Teradata Query Scheduler User Guide to learn more about the Teradata Query Scheduler Viewer. Changing Teradata Query Scheduler Server Configurations 1 Click Start > Programs > Teradata Query Scheduler Utilities > Scheduler to open the Teradata Query Scheduler Operations window. 66 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 4 Configure New Software Configuring Teradata Administrator 2 Click Configuration > Server. The Server Parameters dialog box displays. 3 Modify the fields as desired: Character Set Select the Teradata session character set to use. On a Kanji system (having KANJI1 database object names), select the KANJISJIS_0S character set. Shared Memory Size (KB) Specify the size of the memory area on this system used to store server information. This memory is shared among all the server processes. Request Processor Processes Specify the number of server processes created for handling client messages. Encrypt Client Data Specify whether client data is encrypted through CLIv2. If selected, encryption provides data security in communications between the Teradata Query Scheduler client and server components over network socket connections. The default setting is blank, meaning data is unencrypted. Select the check box to select encryption. Selecting the Encrypt Client Data option also causes encryption to be used for data passed between the Teradata Query Scheduler server and the Teradata Database. Note: After changing the encryption option, stop and restart both the Teradata Query Scheduler clients and server. Listener Address Select the IP address of the Teradata QS Listener to which remote client systems will connect. Tip: Teradata recommends that the default (topmost) address be selected. An administrator may need to change the selection if, for example, the server system is configured for both IPv4 (default) and IPv6 (non-default) networks, and clients are on the IPv6 network. 4 Click OK to close the Server Parameters dialog box and return to the Teradata Query Scheduler Operations tool. Configuring Teradata Administrator After installation, Teradata Administrator must be configured to include the Teradata user name. 1 Navigate to %Program Files%\Teradata\Client\<version>\Teradata Administrator\sql. 2 Edit setup.sql to replace all occurrences of the string <User> with the Teradata user name and save the file. 3 Execute the query setup.sql. Teradata Tools and Utilities for Microsoft Windows Installation Guide 67 Chapter 4 Configure New Software Editing the Teradata Parallel Transporter Configuration File Editing the Teradata Parallel Transporter Configuration File If you installed Teradata Parallel Transporter Base, the local configuration file twbcfg.ini can be modified to change the location of the checkpoint files. 1 Clear the read-only attribute for the configuration file %TWB_ROOT%\Teradata \Client\version\Teradata Parallel Transporter\twbcfg.ini. By default, an installation of Teradata Parallel Transporter sets this file to read-only. %TWB_ROOT% is the system environment variable that holds the value for the Teradata Parallel Transporter installation folder. 2 Use any text editor to edit the default log and checkpoint directories in the configuration file. No reboot is required after making the change in the configuration file. The following are sample default configuration files: • 32-bit CheckpointDirectory= 'C:\Program Files\Teradata\Client \14.00\Teradata Parallel Transporter/checkpoint' LogDirectory='C:\Program Files\Teradata\Client\14.00\Teradata Parallel Transporter/logs' • 64-bit CheckpointDirectory= 'C:\Program Files (x86)\Teradata\Client \14.00\Teradata Parallel Transporter/checkpoint' LogDirectory='C:\Program Files (x86)\Teradata\Client \14.00\Teradata Parallel Transporter/logs' CheckpointDirectory A folder that contains the checkpoint files for Teradata Parallel Transporter jobs. Teradata Parallel Transporter uses checkpoint files to store temporary information needed to restart a job that does not complete successfully. LogDirectory A folder that contains the binary logs for Teradata Parallel Transporter jobs. Each Teradata Parallel Transporter job writes a log in the jobs directory. Note: If a change is made to the folder for the log directory and the Teradata Parallel Transporter Wizard is installed, the LOG_DIRECTORY variable in the %TWB_ROOT% \tptwizard\config\tptwizard.properties file must be changed before running Teradata Parallel Transporter Wizard. Editing the Teradata Parallel Transporter Properties File If the folder for the Log Directory to C:\Logs\Teradata Parallel Transporter 14.0 is changed and the Teradata Parallel Transporter Wizard is installed, use the following 68 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 4 Configure New Software Editing the Teradata Parallel Transporter Environment Variables procedure to update the LOG_DIRECTORY entry in the %TWB_ROOT%\tptwizard \config\tptwizard.properties file. 1 Use any text editor to open tptwizard.properties in the %TWB_ROOT% \tptwizard\config folder 2 Update the LOG_DIRECTORY line to LOG_DIRECTORY=c:\Program Files \Teradata\Client\14.0\Teradata Parallel Transporter\logs\\ The C:\Logs\Teradata Parallel Transporter 14.00.00.00 folder is used as an example. A different folder can be used. Note: The folder for the LOG_DIRECTORY entry in the tptwizard.properties file must be separated by double backslash (\\) and must end with double backslash (\\). Note: Refer to B035-2436-071A, Teradata Parallel Transporter Reference on how to interpret the job log. Editing the Teradata Parallel Transporter Environment Variables By default, an installation of Teradata Parallel Transporter sets the system environment variable TWB_ROOT. Teradata Parallel Transporter uses this variable when running a job. If the user environment variable TWB_ROOT exists, delete or rename it before running a job. 1 Open a command prompt and type SYSDM.CPL to open the System Properties dialog box. 2 Click the Advanced tab. 3 Click Environment Variables. 4 Select the TWB_ROOT variable in the User variables section and click Delete. 5 Click OK. 6 Click OK again. 7 Set the ORACLE_HOME system environment variable to the folder where the Oracle client version of software used by the Teradata Parallel Transporter Wizard is located. Configuring Teradata JMS Access Module 1 After installing Teradata JMS Access Module see the readme file in the installation folder for Teradata JMS Access Module. The default installation folder is %Program Files%\Teradata\Client\<version>\AXSMOD. The readme file contains configuration instructions. Use a text editor, like Notepad, to open the readme file. Teradata Tools and Utilities for Microsoft Windows Installation Guide 69 Chapter 4 Configure New Software Configuring Teradata JMS Access Module 70 Teradata Tools and Utilities for Microsoft Windows Installation Guide 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 Microsoft Windows Installation Guide 71 Chapter 5 Restart the Client Computer Restarting the Client Computer 72 Teradata Tools and Utilities for Microsoft Windows Installation Guide CHAPTER 6 Verify the Complete Installation About Verifying the Installation You can verify successful installation of Teradata Tools and Utilities using either of the following methods: • Run clisamp. This sample CLI program and its makefile are copied to the PC during the installation. • Inspect folders to ensure that all required files are present. Running clisamp 1 Modify the makefile makesamp.win with the correct paths to the include files. By default the makesamp.win file is located in %Program Files%\Teradata \Client\<version>\cliv2\clisamp. 2 Run the makefile to create the executable module clisamp: # nmake -f makesamp.win The default configuration is CFG="clisamp - Win32 Debug" Also supported is: CFG="clisamp - Win32 Release" 3 Run the sample program by entering one of the following commands at the command prompt (change to the appropriate folder first): Release, Debug, IA64Release, or IA64Debug): • To run the sample program using the default logon information (dbc/ systemfe,service) enter: # clisamp • To show help for the sample program, use the -h option, enter: # clisamp -h • To run the sample program, using a user provided input string (TDPID= slugger, user=dbc, password=dbc ), enter:# clisamp slugger/ dbc,dbc The program logs on to the default dbccop1 (no user input supplied) specified in the hosts file and executes a simple query "SELECT * from dbc.sessioninfo;" and writes the output to DAT clisamp.dat file. A display similar to the following appears: # clisamp CLIv2 version is 14.00.00.00 MTDP version is 14.00.00.00 MOSIOS version is 14.00.00.00 MOSIDEP version is 14.00.00.00 OSERR version is 14.00.00.00 Teradata Tools and Utilities for Microsoft Windows Installation Guide 73 Chapter 6 Verify the Complete Installation About Verifying the Installation 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 BTEQ Files and Folders File Type File Name Executable bteq.exe Default Folder %ProgramFiles%\Teradata\Client\<version>\ bin bteqwin.exe Help bteqwin_enu.chm %ProgramFiles%\Teradata\Client\<version>\ bin bteqwin_jpn.chm Icon teqtalk.ico %ProgramFiles%\Teradata\Client\<version>\ bin Library bteqwin_jpn.dll %ProgramFiles%\Teradata\Client\<version>\ bin caputl.dll Sample btnfyext.c %ProgramFiles%\Teradata\Client\<version>\ btnfy btnfyext.def btnfyext.h btnfyext.mak Merge Modules Visual C++ 8.0 CRT (x86) C:\windows\WinSxS\ Visual C++ 8.0 MFC (x86) Visual C++ 8.0 MFCLOC (x86) JMS Access Module Files and Folders File Type File Name Default Folder Dynamic Link Library libjmsam.dll %ProgramFiles%\Teradata\Client\<version>\ AXSMOD Readme readme.txt %ProgramFiles%\Teradata\Client\<version>\ AXSMOD Jar jmsam.jar %ProgramFiles%\Teradata\Client\<version>\ AXSMOD Properties sam_charsets.properties 74 %ProgramFiles%\Teradata\Client\<version>\ AXSMOD Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation Named Pipe Access Module Files and Folders File Type File Name Default Folder Library np_AXSMOD.dll np_AXSMODenu.dll Windows 32-bit on 32-bit Windows platform: %ProgramFiles% \Teradata\Client\<version>\ AXSMOD Windows 32-bit on 64-bit Windows platform: %ProgramFiles(x86)% \Teradata\Client\<version>\ AXSMOD Windows 64-bit on 64-bit Windows platform: %ProgramFiles% \Teradata\Client\<version>\ AXSMOD .NET Data Provider for Teradata Files and Folders .NET Data Provider for Teradata uses the following folder as the default root folder, depending on platform: • For 32-bit platform %ProgramFiles%\Teradata\NET Data Provider for Teradata\<version>\ • For 64-bit platform %ProgramFiles(x86)%\Teradata\NET Data Provider for Teradata\<version>\ Table 8: .NET Data Provider for Teradata Files and Folders Folder File Root folder Readme.txt bin\ bin\ja\ config\ config\ja\ help\ PrivateAssemblies\ PrivateAssemblies\ja\ samples\ samples\Bin\ samples\LearningExamples\ TraceLog\ TraceLog\ja\ bin\ SchemaLoader.exe SetLogLevel.exe Teradata.Client.Provider.dll Teradata.Client.Provider.xml bin\ja\ Teradata.Client.Provider.resources.dll config\ LogAllDebug.config LogAllError.config LogAllInfo.config LogAllTraceExternal.config LogAllTraceInternal.config LogAllWarn.config LogOff.config Teradata Tools and Utilities for Microsoft Windows Installation Guide 75 Chapter 6 Verify the Complete Installation About Verifying the Installation Folder File SDKExtensions.xsd TdgssNetConfig.exe TdgssUserConfigFile.xml config\ja\ TdgssNetConfig.resources.dll help\ COL_TDNETDP.HxC COL_TDNETDP.hxt COL_TDNETDP_A.hxk COL_TDNETDP_D.hxk COL_TDNETDP_F.hxk COL_TDNETDP_K.hxk COL_TDNETDP_N.hxk helpcontentsetup.msha tdnetdp.cab tdnetdp.chm tdnetdp.hxs PrivateAssemblies\ policy.1.0.Teradata.Client.Provider.config policy.1.0.Teradata.Client.Provider.dll policy.1.1.Teradata.Client.Provider.config policy.1.1.Teradata.Client.Provider.dll policy.1.2.Teradata.Client.Provider.config policy.1.2.Teradata.Client.Provider.dll policy.12.0.Teradata.Client.Provider.config policy.12.0.Teradata.Client.Provider.dll policy.13.0.Teradata.Client.Provider.config policy.13.0.Teradata.Client.Provider.dll policy.13.1.Teradata.Client.Provider.config policy.13.1.Teradata.Client.Provider.dll policy.13.10.Teradata.Client.Provider.config policy.13.10.Teradata.Client.Provider.dll policy.13.11.Teradata.Client.Provider.config policy.13.11.Teradata.Client.Provider.dll Teradata.Client.Entity.dll Teradata.Client.VS.dll Teradata.Net.Security.Tdgss.dll PrivateAssemblies\ja\ Teradata.Client.VS.resources.dll Teradata.Net.Security.Tdgss.resources.dll samples\Bin\ NQuery.application NQuery.exe NQuery.exe.config NQuery.exe.maifest samples\LearningExamples\ readme.doc T20000DP.cs through T21300DP.cs TraceLog\ Teradata.Client.Entity.dll Teradata.Client.Provider.dll TraceLog\ja\ Teradata.Client.Provider.resources.dll 76 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation ODBC Driver for Teradata Files and Folders File Type File Name Default Folder vbs Pbocd0x0.txt 32-bit Windows platform: %ProgramFiles%\Teradata\Client Readme.txt tdodbcdsn.vbs \<version>\ ODBC Driver for Teradata 64-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ ODBC Driver for Teradata nt-x8664 tdsql.h Bin tdxodbc 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ ODBC Driver for Teradata\Bin 64-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ ODBC Driver for Teradata nt-x8664\Bin Help catalog.css document.css images (folder) 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ ODBC Driver for Teradata\Help 64-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ ODBC Driver for Teradata nt-x8664\Help odbc_help.htm odbc-1-01.html thru odbc-2-6.html scripts (folder) wwhdata (folder) wwhelp (folder) wwhelp4.jar Library _unodbc.dll tdata32.dll tdatas32.dll 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ ODBC Driver for Teradata\lib 64-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ ODBC Driver for Teradata nt-x8664\lib tdprsr32.dll terasso.dll Samples adhoc.c error.c getopt.c 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ ODBC Driver for Teradata\Samples\C 64-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ ODBC Driver for Teradata nt-x8664\Samples\C getopt.h OLE DB Provider for Teradata Files and Folders File Type File Name Default Folder DLL terasso.dll %ProgramFiles%\Teradata\Client\<version>\ OLE DB Provider for Teradata TDOLEDB.dll Teradata Tools and Utilities for Microsoft Windows Installation Guide 77 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder TDOLEDBR.dll TDOLEDB_TEST.udl tdoledb.h TD_TL.dll TD_RT.dll TD_OC.dll TD_OCPR.dll MSVCRT.DLL Shared ICU Libraries for Teradata Files and Folders File Type File Name Default Folder Dynamic Link Library icudttd46l.dll 32-bit: %ProgramFiles(x86)%\Teradata\Client\<version>\ Shared ICU Libraries for Teradata\lib icuintd46.dll icuiotd46.dll 64-bit: %ProgramFiles%\Teradata\Client\<version>\ Shared ICU Libraries for Teradata\lib iculetd46.dll iculxtd46.dll icuuctd46.dll Teradata Administrator Files and Folders File Type File Name Default Folder Executables STOLE2.TLB %ProgramFiles%\Teradata\Teradata Administrator 14.0\ bin teradata.syn teradata_sp.syn verify.dat Verify.exe winddi.exe Help winddird.txt %ProgramFiles%\Teradata\Teradata Administrator 14.0\ bin winddi_enu.chm DLLs asycfilt.dll %ProgramFiles%\Teradata\Teradata Administrator 14.0\ bin comcat.dll ctl3d32.dll history.txt mfc42u.dll 78 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder MSVBVM60.DLL mscr80.dll mscrt.dll oleaut32.dll olepro32.dll shfolder.dll tdtmgr.dll Winddi_enu.dll SQL setup.spl %ProgramFiles%\Teradata\Teradata Administrator 14.0\ sql udtistinct.txt udtstruct.txt winddi.def winddx.def XViews.sql Teradata Archive/Recovery Utility Files and Folders File Type File Name Executable arcmain.exe Default Folder Windows 32-bit on 32-bit Windows platform: %ProgramFiles% \Teradata\Client\<version>\ bin Windows 32-bit on 64-bit Windows platform: %ProgramFiles(x86)% \Teradata\Client\<version>\ bin Windows 64-bit on 64-bit Windows platform: %ProgramFiles% \Teradata\Client\<version>\ bin Teradata C Preprocessor2 Files and Folders File Type File Name Executable ppcmain.exe Default Folder 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ bin 64-bit Windows platform: %ProgramFiles%\Teradata\Client\<version>\ bin64 DLL ppruntim.dll 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ pp2 64-bit Windows platform: %ProgramFiles%\Teradata\Client\<version>\ pp2_64 Teradata Tools and Utilities for Microsoft Windows Installation Guide 79 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Library ppruntim.lib Default Folder 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ pp2 64-bit Windows platform: %ProgramFiles%\Teradata\Client\<version>\ pp2_64 Sample LABSBTEQ PPCLB1 PPCLB2 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ pp2 64-bit Windows platform: %ProgramFiles%\Teradata\Client\<version>\ pp2_64 PPCLB3 PPCLB4 PPCLB5 PPCLB6 PPCLB7 PPCLB8 PPCLB9 Teradata Call-Level Interface version 2 Files and Folders File Type File Name Default Folder CLI Data clispb.dat %ProgramFiles%\Teradata\Client\<version>\ cliv2 clisamp clisamp.c %ProgramFiles%\Teradata\Client\<version>\ cliv2 makesamp.win Include cliv2if.h %ProgramFiles%\Teradata\Client\<version>\ cliv2\inc coperr.h coptypes.h dbcacnx.h dbcarea.h dbcerr.h dbchqep.h mosiif.h nojunk.h parcel.h resource.h wincliv2.h Library 80 wincli32.lib %ProgramFiles%\Teradata\Client\<version>\ cliv2\lib Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder Dynamic Link Library wincli32.dll %ProgramFiles%\Teradata\Client\<version>\ cliv2 tdusr32.dll localisation.dll User Exit CliLgnEx.c CliPPS.c %ProgramFiles%\Teradata\Client\<version>\ cliv2\UserExit tdusr.def tdusr.rc userexit.mak Teradata Data Connector Files and Folders File Type File Name Default Folder Header pmdcomt.h %ProgramFiles%\Teradata\Client\<version>\ inc pmddamt.h DLLs libpm.dll %ProgramFiles%\Teradata\Client\<version>\ bin Teradata FastExport Files and Folders File Type File Name Default Folder Executable fexp.exe %ProgramFiles%\Teradata\Client\<version>\ bin Sample %ProgramFiles%\Teradata\Client\<version>\ fexp feimod.c fenotf.c feomod.c Teradata FastLoad Files and Folders File Type File Name Default Folder Executable fastload.exe %ProgramFiles%\Teradata\Client\<version>\ bin Sample %ProgramFiles%\Teradata\Client\<version>\ fastload blkexit.c blkexit.mak blkexitr.c flnfyext.c Teradata Tools and Utilities for Microsoft Windows Installation Guide 81 Chapter 6 Verify the Complete Installation About Verifying the Installation Teradata Generic Security Services Files and Folders File Type File Name Default Folder Version version %ProgramFiles%\Teradata\Teradata GSS\ nti386\<version>\ Executables dumpcfg.exe %ProgramFiles%\Teradata\Teradata GSS\ nti386\<version>\ bin gethost.exe ldapcompare.exe ldapdelete.exe ldap.exe ldapmodify.exe ldapmodrdn.exe ldappassword.exe ldapwhoami.exe run_tdgssconfig.bat tdgss.dll tdgssconfig.exe gdgssversion.exe tdlink.exe tdsbind.exe tdssearch.exe tdstcl.exe tests.exe tfclient.exe tfserver.exe DLLs gssp2ldap.dll %ProgramFiles%\Teradata\Teradata GSS\ nti386\<version>\ bin gssp2sspi.dll gssp2td1.dll gssp2tdl2.dll ldap.dll DLLs Microsoft.VC80.CRT.manifest msccm80.dll %ProgramFiles%\Teradata\Teradata GSS\ nti386\<version>\ bin\Microsoft.VC80.CRT mdvcp80.dll msvcr80.dll Help dumpcfg.html gethost.html 82 %ProgramFiles%\Teradata\Teradata GSS\ nti386\<version>\ doc\html Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder ldap_license.html regex_license.html sasl_license.html tdgssconfig.html tdgssversion.html tdlink.html tdsbind.html toc.html xerces_license.html Pod dumpcfg.pod gethost.pod %ProgramFiles%\Teradata\Teradata GSS\ nti386\<version>\ doc\pod ldap_license.pod regex_license.pod sasl_license.pod tdgssconfig.pod tdgssversion.pod tdlink.pod tdsbind.pod toc.pod xerces_license.pod Schema and GlobalTypes.xsd Configuration ipfilter.actdir.schema %Program Files%\Teradata\Teradata GSS\nti386\LCLIENT\etc ipfilter.edir.schema ipfilter.openldap.schema ipfilter.sunone.schema SDKExtensions.xsd systemdlls.txt tdat.actdir.schema tdat.edir.schema tdat.openldap.schema tdat.sunone.schema TdgssConfigFile.xsd TdgssLibraryConfigFile.xml TdgssUserConfigFile.xml Teradata Tools and Utilities for Microsoft Windows Installation Guide 83 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder Header Files algerrors.h %Program Files%\Teradata\Teradata GSS\nti386\LCLIENT\etc ldaperrors.h loadtdgsserrors.h spnegoerrors.h sspierrors.h td1errors.h td2errors.h tdgssapi.h tdgssdefines.h tdgsserrors.h Library loadtgss.lib %Program Files%\Teradata\Teradata GSS\nti386\LCLIENT\lib Java/Jar jtests.jar %Program Files%\Teradata\Teradata GSS\nti386\LCLIENT\lib\java Login.config tdgssdefines.java tdgsstf.jar tcl dntest.tcl pkgIndex.tcl XML TdgssUserConfigFile.xml %Program Files%\Teradata\Teradata GSS\nti386\LCLIENT\lib\tcl\Tds %Program Files%\Teradata\Teradata GSS\Site Teradata Index Wizard Files and Folders File Type File Name Executable DBCVXViews120.bteq Default Folder %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ DBCVXViews62.bteq qcfsetup.def verify.dat Verify.exe DLL Files mgrcli.dll %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ monpm.dll msvcr80.dll tdapp.dll tddaw.dll tdis.dll tdmfcis.dll 84 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder tdtmgr.dll tdwmutil.dll tiwapiw.dll Tiwiz.exe tm_dialogs.dll tseapiw.dll tvecapiw.dll Help catalog.ccc document.css %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu tiwiz-01-01.html thru tiwiz-14-01.html tiwiz_help.htm wwhelp4.jar Graphics numerous *.gif and *.ico files %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\images Script expand.js %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\scripts Common ailinks.js %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\wwhdata\common context.js files.js popups.js synomyms.xml title.js towwhdir.js wwhpagef.js XML files.xml ix.xml %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\wwhdata\java search.xml toc.xml java index.js search.js %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\wwhdata\js toc.js Search rch0.js search1.js %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\wwhdata\js\search Teradata Tools and Utilities for Microsoft Windows Installation Guide 85 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder Help books.xml %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp messages.xml settings.xml splash.jpg Help Graphics altclose.gif altopen.gif %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp\images splash.jpg Help api.htm version.htm Help alinks.htm blank.htm %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp\wwhimpl %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp\wwhimpl\common\html bookmark.htm content.htm controll.htm controlr.htm default.htm document.htm first.htm frameset.htm int0.htm int1.htm int2.htm int3.htm pagenav.htm popup.htm reset.htm switch.htm title.htm wwhelp.htm Help numerous *.gif %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp\wwhimplcommon\images Help java books.js %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp\wwhimpl\common\private locale.js options.js popupf.js 86 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder title.js Help java bklst1s bookgrps.js %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp\wwhimpl\common\scripts booklist.js browser.js control.js documt1.js filelist.js handler.js help.js highlit.js pophash.js popup.js related.js strutils.js switch.js Help java explore6.htm explorer.htm %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp\wwhimpl\java\html javainfo.htm javainfo.jar mozzila.htm mozzillau.htm netscape.htm winhelp.htm Help java books.xml locale.xml %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp\wwhimpl\java\private options.js options.xml Help java handler.js java.js %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\winhelp\wwhimpl\java\scripts javainfo.js Help indexsel.htm navigate.htm %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\wwhdata\java panelfni.htm Teradata Tools and Utilities for Microsoft Windows Installation Guide 87 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder panelfns.htm panelfsi.htm panelfss.htm panelini.htm panelmsg.htm panelnav.htm panelvie.htm tabs.htm wwhelp.htm Help tabsbg.gif %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\wwhelp\wwhimpl\js\images Help java locale.js %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\wwhelp\wwhimpl\js\private options.js Help java handler.js index1s.js %ProgramFiles%\Teradata\Teradata Index Wizard 14.0\ Help\enu\wwhelp\wwhimpl\js\scripts index.js javascript.js outfast.js outlin1s.js outline.js outsafe.js panels.js search1s.js search 2s.js search3s.js search4s.js search.js tabs.js Teradata JDBC Driver Files and Folders File Type File Name Default Folder Executable terajdbc4.jar user selectable Sample samples.jar user selectable Security tdgssconfig.jar user selectable 88 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation Teradata MultiLoad Files and Folders File Type File Name Default Folder Executable mload.exe %ProgramFiles%\Teradata\Client\<version>\ bin Sample %ProgramFiles%\Teradata\Client\<version>\ mload mlimod.c mlnotf.c Teradata OLE DB Access Module Files and Folders File Type File Name Default Folder Executable oleload.exe %ProgramFiles%\Teradata\Client\<version>\ bin Library %ProgramFiles%\Teradata\Client\<version>\ AXSMOD OLEDB_AXSMOD.dll OLEDB_AXSMODenu.dll OLEDB_AXSMODjpn.dll Uninst.dll Online Help Online Help files %ProgramFiles%\Teradata\Client\<version>\ AXSMOD \Teradata OLE DB Access Module Help Icon program.ico %ProgramFiles%\Teradata\Client\<version>\ AXSMOD Merge Modules MSVC80.dll C:\windows\WinSxS\ C:\windows\WinSxS MFC80.dll Teradata Parallel Data Pump Files and Folders for 32-bit Platforms File Type File Name Default Folder Executable tpump.exe %ProgramFiles%\Teradata\Client\<version>\ bin Sample %ProgramFiles%\Teradata\Client\<version>\ tpump tdatpump.cfg tldnfyxt.c tpumpar.csql tpumpimd.c Teradata Performance Monitor Object Files and Folders File Type File Name Default Folder Executables Verify.dat %ProgramFiles%\Teradata\Teradata Performance Monitor Object Verify.exe DLLs Msvcrt.dll Mfc42u.dll %ProgramFiles%\Teradata\Teradata Performance Monitor Object Teradata Tools and Utilities for Microsoft Windows Installation Guide 89 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder Monitor.dll TDMon8.dll PDF MonitorUserGuide.pdf %ProgramFiles%\Teradata\Teradata Performance Monitor Object Teradata Query Scheduler Administrator Files and Folders File Type File Name Executable tqsadm.exe tdqmdb.exe Default Folder %Program Files%\Teradata\Teradata Query Scheduler Admin <version> Note: Program Files can be configured by the system administrator to be on a drive other than the boot drive. Readme readme.txt %Program Files%\Teradata\Teradata Query Scheduler Admin <version> Teradata Query Scheduler Client Files and Folders File Type File Name Executable tdqmcomm.exe tdqmops.exe Default Folder %ProgramFiles%\Teradata\Teradata Query Scheduler <version>\ \client tdqmview.exe Library tdqmcomm.dll %SystemRoot%\system32 tdqmsr.dll tdqmsubm.dll Readme readme.txt %ProgramFiles%\Teradata\Teradata Query Scheduler <version>\ Teradata Query Scheduler Server Files and Folders File Type File Name Executable tdqmjob.exe tdqmlsnr.exe Default Folder %ProgramFiles%\Teradata\Teradata Query Scheduler <version>\ server tdqmreqp.exe tdqmserv.exe Library tdqmserv.dll %SystemRoot%\system32 tdsqlprsu.dll bignumu.dll 90 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder Parser sqlprs.dfa %ProgramFiles%\Teradata\Teradata Query Scheduler <version>\ server sqlprs.llr Teradata SQL Assistant Files and Folders Teradata SQL Assistant uses the following folder as the default root folder, depending on platform: • For 32-bit platform %ProgramFiles%\Teradata\Client\<version>\Teradata SQL Assistant\ • For 64-bit platform %ProgramFiles(x86)%\Teradata\Client\<version> \Teradata SQL Assistant\ Table 9: Teradata SQL Assistant Files and Folders Folder Root folder File access.lng ansi.lng AxInterop.CodeMax4.dll base.lng db2.lng explain.lng FarPoint.CalcEngine.dll FarPoint.Excel.dll FarPoint.PDF.dll FarPoint.PluginCalendar.WinForms.dll FarPoint.Win.dll FarPoint.Win.Chart.dll FarPoint.Win.Spread.dll FarPoint.Win.Spread.Html.dll informix.lng Infragistics2.Shared.v11.2.dll Infragistics2.Win.Misc.v11.2.dll Infragistics2.Win.UltraWinDock.v11.2.dll Infragistics2.Win.UltraWinEditors.v11.2.dll Infragistics2.Win.UltraWinGrid.v11.2.dll Infragistics2.Win.UltraWinListView.v11.2.dll Infragistics2.Win.UltraWinMaskedEdit.v11.2.dll Infragistics2.Win.UltraWinStatusBar.v11.2.dll Infragistics2.Win.UltraWinTabbedMdi.v11.2.dll Infragistics2.Win.UltraWinTabControl.v11.2.dll Infragistics2.Win.UltraWinToolbars.v11.2.dll Infragistics2.Win.UltraWinTree.v11.2.dll Infragistics2.Win.v11.2.dll ingres.lng Interop.CodeMax4.dll Interop.DAO.dll mysql.lng neoview.lng Netezza.lng Teradata Tools and Utilities for Microsoft Windows Installation Guide 91 Chapter 6 Verify the Complete Installation About Verifying the Installation Folder File Office2000.isl Office2003.isl Office2007Black.isl Office2007Blue.isl Office2007Silver.isl oracle.lng outmsg.lng Pink.isl postgresql.lng ReleaseNotes.htm report.lng soliddb.lng SQLA.exe SQLA.exe.config SQLA.pdb SQLA.XmlSerializers.dll sqlacm_en.dll sqla_enu.chm sqlserver.lng startup.exe stdole.dll sybase.lng teradata.lng verify.dat verify.exe Windows7.isl WindowsVista.isl Teradata Statistics Wizard Files and Folders File Type File Name Default Folder Executables DBCVXViews120.bteq %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ DBCVXViews62.bteq qcfsetup.def tswiz.exe verify.dat Verify.exe DLLs mgrcli.dll msvcr80.dll %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ tdapp.dll tddaw.dll tdis.dll tdmfcis.dll 92 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder tdtmgr.dll tdwmutil.dll tiwapiw.dll tm_dialogs.dll tm_stats.dll TSEAPIw.dll tvecapiw.dll Help catalog.ccc document.css %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu tswiz-01-01.html through tswiz-14-01.html tswiz_help.htm wwhelp4.jar Images and icons numerous *.gif and *.ico files %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\images Scripts expand.js %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\scripts Help ailinks.js %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhdata\common context.js files.js popups.js synomyms.xml title.js towwhdir.js wwhpagef.js Java Help files.xml ix.xml %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhdata\java search.xml toc.xml Java Script index.js search.js %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhdata\js toc.js Java Script search0.js %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhdata\js\search Teradata Tools and Utilities for Microsoft Windows Installation Guide 93 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder Help books.xml %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp messages.html settings.html Help Graphics altclose.gif altopen.gif %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\images splash.jpg Help api.htm version.htm Help alinks.htm blank.htm %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\common\html bookmark.htm content.htm controll.htm controlr.htm default.htm document.htm first.htm frameset.htm int0.htm int1.htm int2.htm int3.htm pagenav.htm popup.htm reset.htm switch.htm title.htm wwhelp.htm Help Graphics numerous *.gif %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\common\images Java Script books.js %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\common\private locale.js options.js popupf.js title.js 94 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder Java Script bklst1s %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\common\scripts bookgrps.js booklist.js browser.js controls.js documt1.js filelist.js handler.js help.js highlt.js pophash.js popup.js related.js strutils.js switch.js Help explore6.htm explorer.htm %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\java\html javainfo.htm javainfo.jar mozzila.htm mozzillau.htm netscape.htm wwhelp.htm XML books.xml locale.xml %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\java\private options.js options.xml Java Script handler.js java.js %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\java\scripts javainfo.js Help indexsel.htm navigate.htm %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\js\html panelfni.htm panelfns.htm Teradata Tools and Utilities for Microsoft Windows Installation Guide 95 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder panelfsi.htm panelfss.htm panelini.htm panelmsg.htm panelnav.htm panelvie.htm tabs.htm wwhelp.htm Graphics tabsbg.gif %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\js\images Help locale.js %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\js\private options.js Java Scripts handler.js index1s.js %ProgramFiles%\Teradata\Teradata Statistics Wizard 14.0\ Help\enu\wwhelp\wwhimpl\js\scripts index.js javascript.js outfast.js outlin1s.js outline.js outsafe.js panels.js search1s.js search 2s.js search3s.js search4s.js search.js tabs.js Teradata System Emulation Tool Files and Folders File Type File Name Executables DBCVXViews120.bteq Default Folder %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ DBCVXViews62.bteq mgrcli.dll monpm.dll 96 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder msvcr80.dll qcfsetup.def tdapp.dll tddaw.dll tdis.dll tdmfcis.dll tdtmgr.dll tdwmutil.dll tm_dialogs.dll tseapiw.dll TSET.exe tvecapiw.dl verify.dat Verify.exe Help Files catalog.ccc document.css %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU tset-01-01.html thru tset-14-01.html tset_help.htm wwhelp4.jar Graphics numerous *.gif and *.ico files %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\images Script expand.js %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\scripts Scripts ailinks.js %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhdata\common context.js files.js popups.js synomyms.xml title.js topics.js towwhdir.js wwhpagef.js Teradata Tools and Utilities for Microsoft Windows Installation Guide 97 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder XML files.xml %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhdata\java ix.xml search.xml toc.xml Scripts index.js search.js %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhdata\js toc.js Scripts search0.js search1.js Help books.xml messages.html %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhdata\js\search %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp settings.html Help Images altclose.gif altopen.gif %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\images splash.jpg Help api.htm version.htm Help alinks.htm blank.htm %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\common\html bookmark.htm content.htm controll.htm controlr.htm default.htm document.htm first.htm frameset.htm int0.htm int1.htm int2.htm int3.htm pagenav.htm popup.htm reset.htm 98 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder switch.htm title.htm wwhelp.htm Graphics numerous *.gif %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\common\images Scripts books.js %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\common\private locale.js options.js popupf.js title.js Scripts bklst1s bookgrps.js %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\common\scripts booklist.js browser.js controls.js documt1.js filelist.js handler.js help.js highlt.js pophash.js popup.js related.js strutils.js switch.js Help explore6.htm explorer.htm %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\java\html javainfo.htm javainfo.jar mozzila.htm mozzillau.htm netscape.htm wwhelp.htm XML books.xml %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\java\private Teradata Tools and Utilities for Microsoft Windows Installation Guide 99 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder locale.xml options.js options.xml Scripts handler.js java.js %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\java\scripts javainfo.js Help indexsel.htm navigate.htm %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\js\html panelfni.htm panelfns.htm panelfsi.htm panelfss.htm panelini.htm panelmsg.htm panelnav.htm panelvie.htm tabs.htm wwhelp.htm Help Images tabsbg.gif %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\js\images Scripts locale.js %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\js\private options.js Scripts handler.js index1s.js %ProgramFiles%\Teradata\Teradata System Emulation Tool 14.0\ Help\ENU\wwhelp\wwhimpl\js\scripts index.js javascript.js outfast.js outlin1s.js outline.js outsafe.js panels.js search1s.js search2s.js search3s.js 100 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder search4s.js search.js tabs.js Teradata Visual Explain Files and Folders File Type File Name Executable DBCVXViews120.bteq Default Folder %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ DBCVXViews62.bteq mgrcli.dll monpm.dll msvcr80.dll qcdapiw.dll qcfsetup.def tdapp.dll tddaw.dll tdis.dll tdmfcis.dll tdtmgr.dll tdwmutil.dll tiwapiw.dll dialogs.dll tseapiw.dll tvecapiw.dll Vecomp.exe verify.dat Verify.exe Help Files catalog.ccc document.css %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU ve-01-01.html thru ve-14-01.html ve_help.htm wwhelp4.jar Teradata Tools and Utilities for Microsoft Windows Installation Guide 101 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder Graphics numerous *.gif and *.ico files %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\images Script expand.js %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\scripts Script ailinks.js %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhdata\common context.js files.js popups.js synomyms.xml title.js topics.js towwhdir.js wwhpagef.js XML files.xml ix.xml %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhdata\java search.xml toc.xml Script index.js search.js %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhdata\js toc.js Script search0.js search1.js Help books.xml messages.html %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhdata\js\search %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp settings.html Help Images altclose.gif altopen.gif %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\images splash.jpg Help api.htm version.htm Help alinks.htm blank.htm %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\common\html bookmark.htm content.htm controll.htm 102 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder controlr.htm default.htm document.htm first.htm frameset.htm int0.htm int1.htm int2.htm int3.htm pagenav.htm popup.htm reset.htm switch.htm title.htm wwhelp.htm Graphics numerous *.gif %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\common\images Script books.js %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\common\private locale.js options.js popupf.js title.js Script bklst1s bookgrps.js %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\common\scripts booklist.js browser.js controls.js documt1.js filelist.js handler.js help.js highlt.js pophash.js popup.js related.js Teradata Tools and Utilities for Microsoft Windows Installation Guide 103 Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder strutils.js switch.js Help explore6.htm explorer.htm %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\java\html javainfo.htm javainfo.jar mozzila.htm mozzillau.htm netscape.htm wwhelp.htm XML books.xml locale.xml %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\java\private options.js options.xml Script handler.js java.js %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\java\scripts javainfo.js Help indexsel.htm navigate.htm %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\js\html panelfni.htm panelfns.htm panelfsi.htm panelfss.htm panelini.htm panelmsg.htm panelnav.htm panelvie.htm tabs.htm wwhelp.htm Graphics tabsbg.gif %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\js\images Script locale.js %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\js\private options.js Script 104 handler.js %ProgramFiles%\Teradata\Teradata Visual Explain 14.0\ Help\ENU\wwhelp\wwhimpl\js\scripts Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 6 Verify the Complete Installation About Verifying the Installation File Type File Name Default Folder index1s.js index.js javascript.js outfast.js outlin1s.js outline.js outsafe.js panels.js search1s.js search 2s.js search3s.js search4s.js search.js tabs.js Teradata Wallet Files and Directories File Type File Name Default Folder Executable tdwallet.exe 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ \tdwallet\nt-i386 tdlink.exe 64-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ \tdwallet\nt-x8664 Library tdwallet.dll 32-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ \tdwallet\nt-i386 64-bit Windows platform: %ProgramFiles%\Teradata\Client \<version>\ \tdwallet\nt-x8664 Configuration Language Help config.xml %ProgramFiles%\Teradata\Client\<version>\ tdwallet Teradata WebSphere MQ Access Module Files and Folders File Type File Name Default Folder Library libmqs.dll %ProgramFiles%\Teradata\Client\<version>\ AXSMOD libmqsc.dll Teradata Tools and Utilities for Microsoft Windows Installation Guide 105 Chapter 6 Verify the Complete Installation About Verifying the Installation Teradata Workload Analyzer Files and Folders File Type File Name Executable twa.exe Verify.exe Default Folder %ProgramFiles%\Teradata\Client\<version>\ Teradata Workload Analyzer verify.dat Library fspread.dll mgrcli.dll %ProgramFiles%\Teradata\Client\<version>\ Teradata Workload Analyzer monpm.dll tdtmgr.dll psaload.dll tdapp.dll tdis.dll tdmfcis.dll tdwmutil.dll tm_dialogs.dll Library 106 msvcr80.dll %SystemRoot%\System32 Teradata Tools and Utilities for Microsoft Windows Installation Guide 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. Note: If the environment variable GUILOGON is set to NO, the Connect to Teradata Database dialog box does not open, allowing the application to log on to the Teradata Database without prompting for the password. 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. Teradata Tools and Utilities for Microsoft Windows Installation Guide 107 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database 3 In the Connect to Teradata Database dialog box, select or enter the appropriate values for the 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 • SPNEGO - Simple and protected GSSAPI Negotiation mechanism • NTLM - NT LAN Manager mechanism • Other - user-defined mechanism Note: For new installations, the NTLM mechanisms was disabled as of Teradata Tools and Utilities 14.00.00 in the following files: • TdgssLibraryConfigFile.xml • TdgssUserLibraryConfigFile.xml Users with existing versions of these files are not affected. New installations must explicitly enable the NTLM mechanism to use it. For more information, see B035-1100-111A, Security Administration. 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. 108 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database 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. 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 • SPNEGO - Simple and Protected GSSAPI Negotiation mechanism • NTLM - NT LAN Manager mechanism Note: For new installations, the NTLM mechanisms was disabled as of Teradata Tools and Utilities 14.00.00 in the following files: • TdgssLibraryConfigFile.xml • TdgssUserLibraryConfigFile.xml Users with existing versions of these files are not affected. New installations must explicitly enable the NTLM mechanism to use it. For more information, see B035-1100-111A, Security Administration. 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 Teradata Tools and Utilities for Microsoft Windows Installation Guide 109 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database 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. • 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. 110 Mechanism Mechanism Parameter UserID Password TD2 Never Must Must KRB5 Optional Optional Optional SPNEGO Optional Optional Optional LDAP Optional Optional Optional Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database 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 If required, Teradata Database accounting information may be included as part of .logon command as follows: .logmech KRB5 .logdata joe@domain1@@mypassword .logon mydbs/,,2345889909 or .logmech KRB5 .logdata joe@@mypassword .logon mydbs/,,2345889909 or .logmech KRB5 .logon mydbs/,,2345889909 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." Teradata Tools and Utilities for Microsoft Windows Installation Guide 111 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database 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 3790. SPNEGO Logon Examples SPNEGO Logon Mechanism Teradata Database employs the Simple and Protected GSSAPI Negotiation (SPNEGO) mechanism to provide confidentiality and integrity while supporting non-LDAP external authentication for users logging on to Teradata Database through Windows .NET applications. The SPNEGO mechanism functions almost identically to the KRB5 mechanism, except that KRB5 cannot be used in a Windows .NET environment. See the Kerberos Logon Examples . NTLM Logon Examples Implicit Logon The NTLM authentication mechanism should be used in Windows-to-Windows environments only. A UserId, Password, and Domain can be provided. Once the user's identity has been verified by NTLM, an implicit logon proceeds using the tendered UserId as the Teradata Database Username. .logmech NTLM .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 need not be indicated: .logmech NTLM .logdata joe@@mypassword .logon mydbs/ SSO Logon Alternatively, an NTLM-mediated SSO-style logon can be used by omitting the UserId, Domain, and Password, or omitting the UserId, Password, and either the Domain or the Realm. In this second case, NTLM uses the security credentials associated with the current client session: .logmech NTLM .logon mydbs/ Accounting Information If required, Teradata Database accounting information can be included as part of .logon command as follows: 112 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database .logmech NTLM .logdata joe@domain1@@mypassword .logon mydbs/,,2345889909 or .logmech NTLM .logdata joe@@mypassword .logon mydbs/,,2345889909 or .logmech NTLM .logon mydbs/,,2345889909 In all of the above cases, a Teradata Database Username defined in the target Teradata Database must exist. The Username must match the actual or derived UserId and must have previously been granted the "logon with null password privilege." Note: The special dbc Username cannot be used with the NTLM authentication mechanism since dbc cannot be granted the "logon with null password privilege." If dbc is passed as the username, the Teradata Database will return error 3790. Note: For compatibility purposes, this is equivalent to the existing SSO feature. The existing third-party sign-on variant of SSO (NTLM only) is supported for compatibility purposes. However, Teradata recommends that new applications use the logmech_name, logmech_data_ptr, and logmech_data_len fields in DBCAREA instead. 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/,,2345889909 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 Microsoft Windows Installation Guide 113 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 3790. 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 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. Product Document and Description ODBC Driver for Teradata B035-2509-071A, 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 OLE DB Provider for Teradata B035-2498-020A, OLE DB Provider for Teradata User Guide Describes the security implemented for the OLE DB Provider for Teradata Teradata Call-Level Interface version 2 B035-2418-071A, Teradata Call-Level Interface Version 2 Reference for NetworkAttached Systems Describes the security implemented for the Teradata Call-Level Interface version 2 Teradata JDBC Driver 114 Teradata JDBC Driver Reference : Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database Product Document and Description http://developer.teradata.com/connectivity/reference/jdbc-driver Describes the security-related connection parameters of the Teradata JDBC Driver Checking Logon Error Messages Message Text Explanation Generated by Remedy UTY1652 Logon mechanism 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 is not supported in the version of CLI. 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 It is invalid to specify the .LOGDATA statement after the .LOGON statement. UTYMSG Remove the invalid statement and resubmit the program. A .LOGMECH statement has already been UTYMSG processed. Remove the extra statement and resubmit the program. A .LOGDATA statement has already been UTYMSG processed. Remove the extra statement and resubmit the program. the .LOGDATA statement. UTY6670 A .LOGMECH statement has been previously specified, terminating. UTY6671 A .LOGDATA statement has been previously specified, terminating. Teradata Tools and Utilities for Microsoft Windows Installation Guide 115 Chapter 7 Security and Connecting to a Teradata Database About Connecting to a Teradata Database 116 Teradata Tools and Utilities for Microsoft Windows Installation Guide CHAPTER 8 Deploy Teradata Tools and Utilities with SMS Introduction to SMS Deployment The basic tasks required before deploying using SMS are: • Gather packages by downloading the Teradata Tools and Utilities setup packages and dependencies from the installation media in one or more of the following ways: • Use a network installation. • Use the Teradata Developer Exchange. • Apply patches from the Teradata Software Server. Download third-party installation packages from their corporate URL. Note: Patches on the Teradata Software Server are complete packages. Note: Performing a network installation from the installation media also copies the default response files to the specified folders for products that use install scripts. • Determine which products are InstallScript MSI packages or Basic MSI packages. Note: Include third-party products in your determination. • Create product response files for products that require them. Note: Third-party packages are usually downloaded and deployed using SMS in the same manner as Teradata Tools and Utilities packages. Some may require creation of product response files. • Copy all folders for the installation packages being deployed to the Microsoft SMS server. Only 32-bit packages are deployed to 32-bit machines. Both 32-bit and 64-bit packages must be deployed to 64-bit machines. • Create vbs scripts to install third-party products and Teradata Tools and Utilities products and their dependencies. The process can include the following: • Stop programs that may be running. • Determine if previous versions of the software exist. • Uninstalling if required. • Install third-party dependencies. • Install Teradata Tools and Utilities products and dependencies. • Use SMS to set up and deploy installation packages to client systems. Teradata Tools and Utilities for Microsoft Windows Installation Guide 117 Chapter 8 Deploy Teradata Tools and Utilities with SMS Installation Package Sources Installation Package Sources The SMS deployment procedures can download installation packages from the following sources: • Web URL: Some Teradata Tools and Utilities have third-party dependencies. Download these dependencies from their respective URLs. • DVD: Download product installation packages to a single user from the DVD provided in the Teradata Tools and Utilities Installation Kit. The DVD contains the initial release version of the Teradata Tools and Utilities installation packages. • Teradata Developer Exchange: Download Teradata Tools and Utilities device drivers and communications packages available on the Teradata Developer Exchange. The Teradata Developer Exchange may contain more current software installation packages that should be downloaded instead of initial release version software contained on the media. • Teradata Software Server, accessible from the Downloads link on Teradata @ Your Service: The server contains the latest updated software packages that should be downloaded in lieu of earlier version software contained on the media or on the Teradata Developer Exchange. The Teradata Electronic Software Distribution Management (ESDM) program is not available for Windows. Introduction to Downloading Packages from DVD On a 32-bit or 64-bit machine, download the Teradata Tools and Utilities installation packages from the DVD. Perform a Network Installation of the 32-bit and 64-bit packages to the TTU14.x directory. The packages and any required response files are copied to individual subfolders in that directory. Downloading Installation Packages from DVDs for SMS Deployment When downloading packages, both 32-bit and 64-bit packages are put in the correct corresponding folder. 1 Close all active Windows programs and disable any virus protection software running on the client computer. 2 Insert the Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD into the media drive. 3 In the Welcome to Teradata Tools and Utilities dialog box, click Install Product. 4 In the Choose Setup Language dialog box, select the desired language, then click OK. Note: English and Japanese are the only languages currently supported. 5 In the Welcome dialog box, click Next. 6 In the Software License Agreement dialog box, read the agreement, then click Yes to accept it. 7 In the Setup Type dialog box , click Network. 118 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Installation Package Sources 8 In the Select Components dialog box: a Select the boxes for the products to be downloaded. b Clear the boxes for the products not being downloaded. c Click Next. 9 In the Choose Destination Location dialog box, if the default path shown in the Destination Folder block is acceptable, click Next. (Recommended) Note: To use a destination location other than the default, click Browse, navigate to the location where the files are installed, click OK, then click Next to end the procedure. Note: You must have write access to the destination folder, the Windows root folder, and the Windows system folder. Progress monitors appear during the installation process. No action is required. 10 In the Setup Complete dialog box, choose whether to view the B035-2029-071C, Teradata Tools and Utilities Release Definition Release 14.00, then click Finish. All the packages and dependency packages required for the example SMS deployment of BTEQ and SQLA Assistant are located on the Teradata Tools and Utilities AIX - HP-UX - LINUX - Solaris - Windows Release 14.00.01 DVD. Introduction to Downloading Packages from Teradata Developer Exchange Download installation packages from the Teradata Developer Exchange. Each installation package on the Teradata Developer Exchange contains a procedure that may have been customized for the individual package or release. For both 32-bit and 64-bit packages, download the corresponding package to the directory TTU14.x. The package is copied to the appropriate subfolders in the TTU1x.x directory. 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 10: 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 Teradata Tools and Utilities for Microsoft Windows Installation Guide 119 Chapter 8 Deploy Teradata Tools and Utilities with SMS Installation Package Sources Product .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 11: Tools Product Teradata SQL Assistant Java Edition Teradata Plug-in for Eclipse Downloading Installation Packages from Teradata Developer Exchange for SMS Deployment 1 If downloading 64-bit packages, you must download them to a 64-bit PC. 2 Close all active Windows programs and disable any virus protection software running on the client computer. 3 Go to Teradata Support & Downloads. 4 Click Drivers and Connectivity Software. The Teradata Download Center screen with a list of selectable products appears. 5 Click Windows NT/2000/XP/Vista. A list of available downloads appears. 6 Click the appropriate software package to download. A description of the package appears. 7 Click Download Files. 8 Read the License Agreement, then click I Accept. A screen with a link to the download file appears. 9 Click Download..., then Open. A WinZip or similar window appears containing the Zip file for the download. 10 Create a folder for the package and move the Zip file to that folder. 11 Unzip the file using one of the following methods: • WinZip or similar tool • Right click on the zipped file and select Explore • Right click on the zipped file and select Open With -> Compressed (zipped) Folders 120 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Installation Package Sources 12 Repeat steps 2 through 11 for each package being downloaded from Teradata Developer Exchange. Introduction to Downloading Packages from Patch Server Download Teradata Tools and Utilities installation packages from the Teradata Software Server. Each downloadable package on the Teradata Software Server contains a procedure that may be customized for the individual package or release. For all packages, download to the directory TTU14.x on your machine. The packages are copied to the correct 32-bit or 64-bit individual subfolders in the TTU14.x directory. The Teradata Software Server contains patches to software that were made since the software was released. Perform the following procedure to download installation packages from the Teradata Software Server. For products that have a more recent release located on the Teradata Software Server, download the file to the corresponding products directory created by the Network install. Unzip the file to replace the original installation files. Downloading Installation Packages from Patch Server for SMS Deployment When downloading packages, both 32-bit and 64-bit packages are put in the correct corresponding folder. 1 Close all active Windows programs and disable any virus protection software running on the client computer. 2 Log on to Teradata @ Your Service. 3 Click Downloads. 4 Click Teradata Client . The Client Help screen appears. 5 Click on Windows. The Teradata Client Released Software screen appears. 6 Select the Software Base and Platform Base, then click on Submit. The Client Patches available screen appears. 7 For 32-bit packages, click in the check boxes to select the 32-bit software patches to download. 8 For 64-bit packages, click in the check boxes to select the 64-bit software patches to download. 9 Enter your User Name and E-Mail Address and then click Submit. 10 Click Download. A WinZip window appears containing the Zip file for the download. 11 Create a folder for the package, and move the Zip file to the folder. 12 Unzip the file using one of the following methods: Teradata Tools and Utilities for Microsoft Windows Installation Guide 121 Chapter 8 Deploy Teradata Tools and Utilities with SMS Overview of Product Response Files • WinZip or similar tool • Right-click on the zipped file and select Explore • Right-click on the zipped file and select Open With > Compressed (zipped) Folders 13 Repeat steps 6 through 12 for each 32-bit and 64-bit package being downloaded from the Teradata Software Server. Overview of Product Response Files Response files must be created for both 32-bit and 64-bit installation packages that use them. Performing a Network installation copies the corresponding packages and any default response files to the user-specified installation directory for that product. Note: All Teradata Tools and Utilities client installation packages include an MSI file. On both 32-bit and 64-bit systems, 32-bit and 64-bit installation directories are created for products that have both. The following products require a response file for silent installation: • Teradata Archive/Recovery Utility • Teradata Meta Data Services Installation Order and Dependencies Order Product Install Script Basic MSI 0 1 Shared ICU Libraries for Teradata Dependencies • Windows Installer 3.0 • Determine required dependencies from third-party URL X None X None X None X Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata 32-bit package 2 Shared ICU Libraries for Teradata 64-bit package 3 Teradata Generic Security Services Client 32-bit package 4 ODBC Driver for Teradata 32-bit package 5 ODBC Driver for Teradata 64-bit package 122 • X Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Generic Security Services Client Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Overview of Product Response Files Order Product Install Script 6 OLE DB Provider for Teradata X Basic MSI Dependencies Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata 32-bit package • Teradata Generic Security Services Client Note: During the silent installation of the OLE DB Provider for Teradata package, when the user is part of the administrator group, but not an inbuilt administrator on Windows 7, Windows 2008 R2, or Windows Vista, a User Account Control dialog box appears. The dialog prompts you to allow the program to make changes to the computer. Click OK. 7 Teradata JDBC Driver X 32-bit package Third-party dependencies: • JDK 1.4 , JDK 5.0, or JDK 6.0 Note: • JDK 5.0 is certified for Windows 32-bit. • JDK 5.0 is certified for Windows XP Professional x64 using EM64T. • JDK 6.0 is certified for Windows 64-bit Note: The environment can be downloaded from Java Downloads. 8 Teradata JDBC Driver X 64-bit package Third-party dependencies: • JDK 1.4 , JDK 5.0, or JDK 6.0 Note: • JDK 5.0 is certified for Windows 32-bit. • JDK 5.0 is certified for Windows XP Professional x64 using EM64T. • JDK 6.0 is certified for Windows 64-bit Note: The environment can be downloaded from Java Downloads. 9 Teradata Call-Level Interface version 2 X 32-bit package 10 Teradata Call-Level Interface version 2 • X 64-bit package 11 Teradata Data Connector Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Generic Security Services Client X None X None 32-bit package 12 Teradata Data Connector 64-bit package Teradata Tools and Utilities for Microsoft Windows Installation Guide 123 Chapter 8 Deploy Teradata Tools and Utilities with SMS Overview of Product Response Files Order Product 13 .NET Data Provider for Teradata Install Script Basic MSI Dependencies X Third-party dependency: • Microsoft .NET Framework Version 3.5 SP1 Redistributable Package or Microsoft .NET Framework Version 4.0 Redistributable Package Note: The installation package is 32bit. .NET Data Provider for Teradata supports and runs 32-bit or 64-bit processes. 14 Teradata Archive/Recovery Utility X Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata 32-bit package 15 Teradata Archive/Recovery Utility X Basic Teradata Query X 32-bit package 17 Teradata Query Scheduler Administrator Teradata Call-Level Interface version 2 • Teradata Data Connector • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata 64-bit package 16 • X 32-bit package • Teradata Call-Level Interface version 2 • Teradata Data Connector • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Data Connector • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Generic Security Services Client Teradata Query Scheduler Administrator has dependencies on TCP/IP and Ethernet drivers. Although the standard networking-enabled Windows installation includes a TCP/IP driver with WinSock support for Windows version 2.0 or later and an Ethernet driver that is compatible with the TCP/IP driver, ensure that these drivers are also on the Windows client system. 18 Teradata Query Scheduler Client X 32-bit package 19 Teradata Query Scheduler Server 32-bit package 124 X Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Overview of Product Response Files Order 20 Product Teradata FastExport Install Script Basic MSI X 32-bit package 21 Teradata FastLoad X 32-bit package 22 Teradata MultiLoad X 32-bit package 23 Teradata Parallel Data Pump X 32-bit package 24 Named Pipes Access Module Dependencies • Teradata Generic Security Services Client • Teradata Query Scheduler Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Data Connector • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Data Connector • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Data Connector • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Data Connector • Teradata Generic Security Services Client X None X None X Teradata Tools and Utilities dependencies: • ODBC Driver for Teradata 32-bit package 25 Named Pipes Access Module 64-bit package 26 Teradata OLE DB Access Module 32-bit package 27 Teradata C Preprocessor2 X 32-bit package 28 Teradata C Preprocessor2 X • Shared ICU Libraries for Teradata • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: Teradata Tools and Utilities for Microsoft Windows Installation Guide 125 Chapter 8 Deploy Teradata Tools and Utilities with SMS Overview of Product Response Files Order Product Install Script Basic MSI 64-bit package 29 Teradata SQL Assistant X 32-bit package Dependencies • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Generic Security Services Client Teradata SQL Assistant uses ODBC Driver for Teradata or .NET Data Provider for Teradata to connect to the Teradata Database. You can have ODBC Driver for Teradata and .NET Data Provider for Teradata version 13.11 or later installed concurrently. If you use .NET Data Provider for Teradata to connect Teradata SQL Assistant to the Teradata Database, install dependencies in the following order: 1. Microsoft .NET Framework Version 3.5 SP1 Redistributable Package 2. .NET Data Provider for Teradata version 13.11 or later. The Install Policy Files must be selected during the installation If you use ODBC Driver for Teradata to connect Teradata SQL Assistant to the Teradata Database, install dependencies in the following order: 1. Shared ICU Libraries for Teradata 2. Teradata Generic Security Services Client 3. ODBC Driver for Teradata 30 Teradata Administrator X 32-bit package 31 Teradata Visual Explain X 32-bit package 32 Teradata System Emulation Tool X 32-bit package 33 Teradata Parallel Transporter Base 32-bit package 126 X Teradata Tools and Utilities dependencies: • ODBC Driver for Teradata • Shared ICU Libraries for Teradata • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 or ODBC Driver for Teradata • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 or ODBC Driver for Teradata • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Overview of Product Response Files Order Product Install Script Basic MSI Dependencies • Teradata Generic Security Services Client Third-party dependencies: • Java 2 Runtime Environment 1.4.2_06 or later Note: The environment can be downloaded from Java Downloads. 34 Teradata Parallel Transporter Base X 64-bit package Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Generic Security Services Client Third-party dependencies: • Java 2 Runtime Environment 1.4.2_06 or later Note: The environment can be downloaded from Java Downloads. 35 Teradata Parallel Transporter Stream X 32-bit package 36 Teradata Parallel Transporter Stream X 64-bit package 37 Teradata Index Wizard X 32-bit package 38 Teradata Statistics Wizard X 32-bit package 39 Teradata WebSphere MQ Access Module 32-bit package X Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Generic Security Services Client • Teradata Parallel Transporter Base Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Generic Security Services Client • Teradata Parallel Transporter Base Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 or ODBC Driver for Teradata • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 or ODBC Driver for Teradata • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • Teradata Data Connector Third-party dependencies: • IBM WebSphere MQ V5.2 Teradata Tools and Utilities for Microsoft Windows Installation Guide 127 Chapter 8 Deploy Teradata Tools and Utilities with SMS Overview of Product Response Files Order Product Install Script 40 Teradata Workload Analyzer Basic MSI Dependencies X Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata 32-bit package 41 Teradata Meta Data Services X • Teradata Call-Level Interface version 2 • Teradata Generic Security Services Client Teradata Tools and Utilities dependencies: • ODBC Driver for Teradata 32-bit package • Shared ICU Libraries for Teradata • Teradata Generic Security Services Client Third-party dependencies: • JRE 5.0 or JRE 6.0 32-bit Note: The environment can be downloaded from Java Downloads. 42 Teradata Performance Monitor Object 32-bit package X Teradata Tools and Utilities dependencies: • Shared ICU Libraries for Teradata • Teradata Call-Level Interface version 2 • Teradata Generic Security Services Client Creating Product Response Files for SMS Deployment Some products require product response files ( setup.iss). See the list of products and determine which products you are installing require the product response files. To create a product response file, use a command similar to the following for each package directory that uses a response file: setup.exe /r /f1"<response_file>" Example: setup.exe /r /f1"c:\temp\TDOLEDB.iss" To install products using a product response file, use a command similar to the following for each package directory that uses a response file: setup.exe /s /f1"<response_file>" /f2"<setup_log_file>" /w Example: setup.exe /s /f1"c:\temp\TDOLEDB.iss" /f2"c:\temp\TDOLEDB.log" /w setup.exe /s /f1"c:\temp\TDOLEDB.iss" /f2"c:\temp\TDOLEDB.log" /w The parameters shown in the following table are used with setup.exe and response files. 128 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Copy Packages for SMS Deployment Parameter Description /r (Record Mode) Enables creation of a response file; when a response file is recorded, all options selected are recorded /s (Silent Mode) Plays the recorded response back with all options selected /f1"<response_file>" (Response File Name) By default, the response file is named setup.iss and is created in the Windows system folder. Use the /f1 option to specify a different response file name and absolute path. /f2"<setup_log_file>" (Setup Log File Name) The default log file is created in the same directory as the response file. It has the same file name as the corresponding response file, with a different extension. Use the /f2 option to specify an alternative log file name and absolute path. /w (Wait) The setup.exe process exits upon completion. 1 Change directories to a package folder that requires a product response file. 2 From the command line, execute the following: setup.exe /r /f1"<response filename>" The splash and then Welcome screens appear. 3 Click Next and continue with the installation dialog as though running the interactive installation. When finished, a response file with the name setup.iss is created in the same folder. 4 Repeat the procedure for each of the packages requiring product response files. Creating Basic MSI Files for SMS Deployment Most products come with MSI files. See the list of products to determine which products you are installing have basic MSI files. 1 To install products using a Basic MSI file, set up the script file to run a command similar to the following for each package directory that uses a Basic MSI file: setup.exe /s/v/qn/w where: • /s is silent mode. The recorded response is played back with all options selected. • /v is pass arguments. Arguments are passed to Msiexec. • /qn is set installation user interface level. Using the /q or /qn options initiates a silent install with no user interaction required. • /w is wait. The setup.exe execution exits when the installation is complete. Copy Packages for SMS Deployment After product response files have been created for the installation packages that require them, copy all installation package folders to the SMS server. Teradata Tools and Utilities for Microsoft Windows Installation Guide 129 Chapter 8 Deploy Teradata Tools and Utilities with SMS Creating VBS Script for SMS Deployment 1 Copy the TTU14.00 directory containing both the 32-bit and 64-bit installation packages to the Microsoft SMS server. Creating VBS Script for SMS Deployment 1 Create a vbs script file that uninstalls existing versions of Teradata Tools and Utilities products; installs third-party dependencies; and then installs Teradata Tools and Utilities products. Deploying with SMS To deploy Teradata Tools and Utilities use the vbs script you created and the features of the Microsoft SMS server. 1 Follow your normal deployment procedures using SMS. Sample Uninstall Script ‘==================================================================================================== ‘ Copyright 2007-2011 by Teradata Corporation. ‘ All Rights Reserved. ‘ TERADATA CONFIDENTIAL AND TRADE SECRET ‘ ‘ Description : ‘ uninstall_TTU.vbs script is used to uninstall previous versions of a TTU product. ‘ This script can be executed from a command prompt by passing the product name as arguments. ‘ The script handles uninstallation of previous versions for the following TTU products ‘ TERAGSS ‘ TDICU ‘ TDODBC ‘ CLIv2 ‘ PIOM ‘ BTEQ ‘ FASTLD ‘ MLOAD ‘ FASTEXP ‘ TPUMP ‘ TDOLEDB ‘ SQLPP ‘ NPAXSMOD ‘ MQAXSMOD ‘ OLEDBAXSMOD ‘ JMSAXSMOD ‘ SQLA ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ This script does not require any arguments to be passed. The script creates temporary files in %SYSTEMROOT%\temp folder. The script execution is logged into a file called %SYSTEMROOT%\temp\uninstall_script.log. The information logged in the file can be used for troubleshooting errors in the script. This script uses IDriver.exe to uninstall Installscript MSI packages installed on the machine. Msiexec.exe to uninstall Basic MSI packages installed on the machine. Note : 130 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ ‘ 1) This script assumes IDriver.exe file exists under the following folders on 32-bit machines:e C:\Program Files\Common Files\InstallShield\Driver\7\Intel 32\ & C:\Program Files\Common Files\InstallShield\Driver\9\Intel 32\ on 64-bit machines:e C:\Program Files (x86)\Common Files\InstallShield\Driver\7\Intel 32\ & C:\Program Files (x86)\Common Files\InstallShield\Driver\9\Intel 32\ The uninstall_TTU script is enhanced to handle uninstallation of products provided as arguments. The following command can be used to execute the script Usage: cscript uninstall_TTU.vbs [TERAGSS TDICU CLIv2 TDODBC PIOM BTEQ FASTLD MLOAD FASTEXP TPUMP TDOLEDB SQLPP NPAXSMOD MQAXSMOD OLEDBAXSMOD JMSAXSMOD SQLA] Revision History: 14.00.00.00 2011Feb01 14.00.00.00 2011Feb01 14.00.00.00 2011Feb01 14.00.00.00 2011Feb01 14.00.00.00 2011Feb01 14.00.00.00 2011Feb12 14.00.00.00 2011Feb12 14.00.00.00 2011Feb12 14.00.00.00 2011Feb12 14.00.00.00 2011Mar15 14.00.00.00 2011Mar15 14.00.00.00 2011Mar16 14.00.00.00 2011Mar16 14.00.00.00 2011Mar16 14.00.00.00 2011Mar16 14.00.00.00 2011Mar16 14.00.00.00 2011Jun19 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 pk185011 DR117520 DR117517 DR117527 DR117516 DR116126 DR117519 DR117525 DR117518 DR117528 DRxxxxxx DRxxxxxx DRxxxxxx DRxxxxxx DRxxxxxx DRxxxxxx DRxxxxxx DR123218 TDICU CLIv2 TDODBC PIOM BTEQ FASTLD MLOAD FASTEXP TPUMP TERAGSS TDOLEDB SQLPP NPAXSMOD MQAXSMOD OLEDBAXSMOD JMSAXSMOD TDOLEDB : : : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Uninstallation of previous version : Enhanced the script to uninstall corrupted installations or left over files and registry entries. ‘==================================================================================================== Dim objWshNetwork Dim objWshShell Dim objFile Dim Dim Dim Dim ComputerName CurrentUserName UserDomain CompleteUserName Dim Dim Dim Dim Dim Dim position output winroot program_files_dir program_files_x86_dir allusers_dir Dim Dim Dim Dim Dim Dim Dim Dim Dim Dim product_name product_code product_ver Wow6432Node Hex_Version Disp_Name alpha_product_ver saved_product_ver saved_product_code alpha_char Dim Dim Dim Dim Dim Dim Dim txtfile txtfile1 txtfile2 lf outputfile outputfile1 outputfile2 Teradata Tools and Utilities for Microsoft Windows Installation Guide 131 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script Dim Dim Dim Dim Dim Dim Dim Dim Dim Dim Dim Dim Dim Dim Dim ScriptLog ISSFileName LogFileName InstallPath TIMESTAMP Package_64bit strcomputer objCtx objLocator objServices objStdProv Inparams Outparams Proc_Arch RegValue Dim TTUProds(20) Dim TTUProducts(20) Dim TTUProduct_cntrs(20) TTUProds(0) = “TERAGSS” TTUProds(1) = “TDICU” TTUProds(2) = “CLIv2” TTUProds(3) = “TDODBC” TTUProds(4) = “PIOM” TTUProds(5) = “BTEQ” TTUProds(6) = “FASTLD” TTUProds(7) = “MLOAD” TTUProds(8) = “FASTEXP” TTUProds(9) = “TPUMP” TTUProds(10) = “TDOLEDB” TTUProds(11) = “SQLPP” TTUProds(12) = “NPAXSMOD” TTUProds(13) = “MQAXSMOD” TTUProds(14) = “OLEDBAXSMOD” TTUProds(15) = “JMSAXSMOD” TTUProds(16) = “SQLA” TTUProds(17) = Empty TTUProducts(0) = “Teradata GSS” TTUProducts(1) = “Shared ICU Libraries for Teradata” TTUProducts(2) = “Teradata CLIv2” TTUProducts(3) = “ODBC Driver for Teradata” TTUProducts(4) = “Teradata Data Connector” TTUProducts(5) = “Teradata BTEQ” TTUProducts(6) = “Teradata FastLoad” TTUProducts(7) = “Teradata MultiLoad” TTUProducts(8) = “Teradata FastExport” TTUProducts(9) = “Teradata TPump” TTUProducts(10) = “OLE DB Provider for Teradata” TTUProducts(11) = “Teradata C PP2” TTUProducts(12) = “Teradata Named Pipes Access Module” TTUProducts(13) = “WebSphere Access Module for Teradata” TTUProducts(14) = “Teradata OLE DB Access Module” TTUProducts(15) = “Teradata Access Module For JMS” TTUProducts(16) = “Teradata SQL Assistant” TTUProducts(17) = Empty const ForReading=1, ForWriting=2 Const HKEY_LOCAL_MACHINE = &H80000002 Const HKLM = &h80000002 strComputer = “.” ‘Check if required arguments are provided set args = WScript.Arguments.Unnamed if (args.count < 1) then WSCript.Echo “Usage: “ WScript.Echo “cscript uninstall_TTU.vbs [TERAGSS TDICU CLIv2 TDODBC PIOM BTEQ “ 132 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script WScript.Echo “ FASTLD MLOAD FASTEXP TPUMP TDOLEDB “ WScript.Echo “ SQLPP NPAXSMOD MQAXSMOD OLEDBAXSMOD “ WScript.Echo “ JMSAXSMOD SQLA] “ WSCript.Echo “Any or all of the products specified above can be passed as arguments” WScript.Echo “to the script.” WScript.Echo “eg: cscript uninstall_TTU.vbs TDODBC” WScript.Echo “eg: cscript uninstall_TTU.vbs TDODBC CLIv2” WScript.Echo “eg: cscript uninstall_TTU.vbs TDODBC CLIv2 TDICU TERAGSS” WScript.Quit() else for i = 1 to args.count ‘Get the Product_name from based on the arguments. Select case args(i-1) case TTUProds(0) case TTUProds(1) case TTUProds(2) case TTUProds(3) case TTUProds(4) case TTUProds(5) case TTUProds(6) case TTUProds(7) case TTUProds(8) case TTUProds(9) case TTUProds(10) case TTUProds(11) case TTUProds(12) case TTUProds(13) case TTUProds(14) case TTUProds(15) case TTUProds(16) case else WSCript.Echo “Invalid Product specified : “ & args(i-1) WSCript.Echo “Usage: “ WScript.Echo “cscript uninstall_TTU.vbs [TERAGSS TDICU CLIv2 TDODBC PIOM BTEQ “ WScript.Echo “ FASTLD MLOAD FASTEXP TPUMP TDOLEDB “ WScript.Echo “ SQLPP NPAXSMOD MQAXSMOD OLEDBAXSMOD “ WScript.Echo “ JMSAXSMOD SQLA] “ WSCript.Echo “Any or all of the products specified above can be passed as arguments” WScript.Echo “to the script.” WScript.Echo “eg: cscript uninstall_TTU.vbs TDODBC” WScript.Echo “eg: cscript uninstall_TTU.vbs TDODBC CLIv2” WScript.Echo “eg: cscript uninstall_TTU.vbs TDODBC CLIv2 TDICU TERAGSS” WScript.Quit() end select next end if TIMESTAMP = Year(Now) & Month(Now) & Day(Now) & Hour(Now) & Minute(Now) & Second(Now) set objWshShell = CreateObject(“WScript.Shell”) Set objFile = CreateObject(“Scripting.FileSystemObject”) ‘Get Windows systemroot on the machine set output = objWshShell.Exec(“cmd /C echo %SYSTEMROOT%”) winroot = output.StdOut.ReadLine ‘Get Windows Program Files folder on the machine set output = objWshShell.Exec(“cmd /C echo %PROGRAMFILES%”) program_files_dir = output.StdOut.ReadLine ‘Get Windows All Users folder on the machine set output = objWshShell.Exec(“cmd /C echo %ALLUSERSPROFILE%”) allusers_dir = output.StdOut.ReadLine ‘Define the temporary files and the log file. outputfile = winroot & “\temp\output.txt” outputfile1 = winroot & “\temp\output1.txt” outputfile2 = winroot & “\temp\output2.txt” Teradata Tools and Utilities for Microsoft Windows Installation Guide 133 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script ScriptLog = winroot & “\temp\uninstall_script_” & TIMESTAMP & “.log” Set lf = objFile.CreateTextFile(ScriptLog, True) lf.WriteLine “====================Uninstall_prev_ver script being execution========================” ‘Obtain User Name of the current user rc = objWshShell.Run(“cmd /C echo %USERNAME%> “ & outputfile,0,true) set txtfile = objFile.OpenTextFile(outputfile, ForReading, False) CurrentUserName = txtfile.ReadLine txtfile.close ‘Obtain Domain Name of the current user rc = objWshShell.Run(“cmd /C echo %USERDOMAIN%> “ & outputfile,0,true) set txtfile = objFile.OpenTextFile(outputfile, ForReading, False) UserDomain = txtfile.ReadLine txtfile.close ‘Obtain Computer Name of the current user rc = objWshShell.Run(“cmd /C echo %COMPUTERNAME%> “ & outputfile,0,true) set txtfile = objFile.OpenTextFile(outputfile, ForReading, False) ComputerName = txtfile.ReadLine txtfile.close ‘Check if the ComputerName and UserDomain are same then the user is ‘not logged onto a domain. if (LCase(ComputerName) = LCase(UserDomain)) then CompleteUserName = CurrentUserName elseif (LCase(CurrentUserName) = “administrator”) then CompleteUserName = CurrentUserName else CompleteUserName = UserDomain & “\” & CurrentUserName end if ‘Retrieve the administrators on the machine rc = objWshShell.Run(“cmd /C net localgroup administrators > “ & outputfile,0,true) set txtfile = objFile.OpenTextFile(outputfile, ForReading, False) content=”” Do While txtfile.AtEndOfStream <> True content = content & txtfile.ReadLine loop txtfile.close ‘Search for the current user in the if instr(content, CompleteUserName) lf.WriteLine CompleteUserName else lf.WriteLine CompleteUserName & end if list of administrators on the machine. <> 0 then & “ is an administrator.” “ is not an administrator.” RegValue = “PROCESSOR_ARCHITECTURE” ‘Obtain Processor Architecture. rc = objWshShell.Run(“cmd /C reg query “ & chr(34) & “HKLM\SYSTEM\CurrentControlSet\Control\Session Manager \Environment” & chr(34) & “ /V “ & RegValue & “ > “ & outputfile,0,true) set txtfile = objFile.OpenTextFile(outputfile, ForReading, False) if (txtfile.AtEndOfStream = False) then content = ““ Do While txtfile.AtEndOfStream <> True content = txtfile.ReadLine if instr(1,content, RegValue) <> 0 then strlen = len(content) pos = InStr(1,content,”REG_SZ”) Proc_Arch = Right(content,(strlen-pos)-6) exit do end if loop end if 134 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script txtfile.close Proc_Arch = trim(Proc_Arch) lf.WriteLine “Proc Arch : “ & Proc_Arch if (Proc_Arch = “AMD64”) then ‘Get Windows Program Files(x86) folder on the machine set output = objWshShell.Exec(“cmd /C echo %PROGRAMFILES(x86)%”) program_files_x86_dir = output.StdOut.ReadLine else program_files_x86_dir = ““ end if ‘Product_ver is fixed for a release product_ver=”13.00.00.00” ‘Iterate the uninstallation process for all the arguments. for iter = 1 to args.Count ‘Assign the actual Product Name by searching through the TTUProducts array. Select case args(iter-1) case TTUProds(0) ‘TERAGSS product_name = TTUProducts(0) case TTUProds(1) ‘TDICU product_name = TTUProducts(1) case TTUProds(2) ‘CLIv2 product_name = TTUProducts(2) case TTUProds(3) ‘TDODBC product_name = TTUProducts(3) case TTUProds(4) ‘PIOM product_name = TTUProducts(4) case TTUProds(5) ‘BTEQ product_name = TTUProducts(5) case TTUProds(6) ‘FASTLD product_name = TTUProducts(6) case TTUProds(7) ‘MLOAD product_name = TTUProducts(7) case TTUProds(8) ‘FASTEXP product_name = TTUProducts(8) case TTUProds(9) ‘TPUMP product_name = TTUProducts(9) case TTUProds(10) ‘TDOLEDB product_name = TTUProducts(10) case TTUProds(11) ‘SQLPP product_name = TTUProducts(11) case TTUProds(12) ‘NPAXSMOD product_name = TTUProducts(12) case TTUProds(13) ‘MQAXSMOD product_name = TTUProducts(13) case TTUProds(14) ‘OLEDBAXSMOD product_name = TTUProducts(14) case TTUProds(15) ‘JMSAXSMOD product_name = TTUProducts(15) case TTUProds(16) ‘SQLA product_name = TTUProducts(16) end select lf.WriteLine “==============================” & product_name & “======================================” Set objCtx = CreateObject(“WbemScripting.SWbemNamedValueSet”) objCtx.Add “__ProviderArchitecture”, 64 objCtx.Add “__RequiredArchitecture”, TRUE Set objLocator = CreateObject(“Wbemscripting.SWbemLocator”) Set objServices = objLocator.ConnectServer(““,”root\default”,””,””,,,,objCtx) Set objStdRegProv = objServices.Get(“StdRegProv”) Wow6432Node=False GetInstalledProducts() lf.WriteLine “Completed searching the registry for “ & product_name lf.WriteLine “-----------------------------------------------------------------------------------------” Teradata Tools and Utilities for Microsoft Windows Installation Guide 135 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script ‘Search the Wow6432Node registry section only on a 64-bit machine for 32-bit packages installed on the machine. if (Proc_Arch = “AMD64”) then objCtx.Add “__ProviderArchitecture”, 32 objCtx.Add “__RequiredArchitecture”, TRUE Set objLocator = CreateObject(“Wbemscripting.SWbemLocator”) Set objServices = objLocator.ConnectServer(““,”root\default”,””,””,,,,objCtx) Set objStdRegProv = objServices.Get(“StdRegProv”) Wow6432Node=True GetInstalledProducts() lf.WriteLine “Completed searching the Wow6432Node registry for “ & product_name end if lf.WriteLine “=================================================================================” Next lf.WriteLine “===================Uninstall_prev_ver script end execution===========================” lf.close ‘============================================================================================================ ========================================= ‘Check the DisplayName key in the uninstall registry entry to match the product name of the TTU product Function GetInstalledProducts() ‘ Use ExecMethod to call the GetStringValue method Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\Microsoft\Windows\CurrentVersion\Uninstall\” Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) For Each strSubKey In Outparams.snames if (instr(1,strSubKey,”{“) <> 0 ) then pos = instr(1,strSubKey,”{“) if (pos = 1) then product_code = strSubKey call FindTTUProduct(“SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\” & strSubKey,product_name) end if end if Next ‘Uninstall the active TeraGSS version at the end. if (saved_product_ver <> ““) then Call Initiate_Product_Uninstall(product_name, saved_product_code,saved_product_ver) saved_product_ver = ““ end if End Function ‘============================================================================================================ ========================================= ‘Check the DisplayName key in the uninstall registry entry to match the product name of the TTU product Function FindTTUProduct(ByVal uninst_key, Byval ProductName) Dim shellobj Dim outputobj Dim content Dim ExePath Dim vcompare set shellobj = CreateObject(“WScript.Shell”) ‘Get the DisplayName of the product from the uninstall key to filter out the matched products. Set Inparams = objStdRegProv.Methods_(“GetStringValue”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = uninst_key Inparams.Svaluename = “DisplayName” set Outparams = objStdRegProv.ExecMethod_(“GetStringValue”, Inparams,,objCtx) ‘If the DisplayName matches the ProductName we further extract the productcode, product version to verify that the product ‘entry matches the criteria for uninstallation. if instr(1,Outparams.SValue, ProductName) <> 0 then 136 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script if instr(1,Outparams.SValue, “x8664”) <> 0 then Package_64bit=true else Package_64bit=false end if product_version = ExtractProductVersion(uninst_key,ProductName) ExtractUnInstallInfo uninst_key, ProductName lf.WriteLine “Product installation Found. Product Name = “ & ProductName & “ = “ & product_version | Product Version ‘TeraGSS does not allow the uninstallation of the TeraGSS version that is active if there are other versions ‘of TeraGSS already installed on the machine. The active TeraGSS version has to be the last version that ‘should be uninstalled. Hence identifying the currently active TeraGSS version by running tdgssversion and ‘saving the product version and product code, so that they can be used to uninstall the active version later. if (ProductName = TTUProducts(0)) then ‘TERAGSS if (saved_product_ver = ““) then ‘Get the InstallPath of the product. GetInstallPath ProductName,ProductVersion if (Package_64bit = true) then ‘ Looking for 64-bit TeraGSS ExePath=”nt-x8664\LCLIENT\bin\tdgssversion.exe” else ExePath=”nt-i386\LCLIENT\bin\tdgssversion.exe” end if rc = shellobj.Run(“cmd /C “ & chr(34) & InstallPath & ExePath & chr(34) & “ >” & outputfile1,0,true) set txtfile1 = objFile.OpenTextFile(outputfile1, ForReading, False) content = ““ Do While txtfile1.AtEndOfStream <> True content = rtrim(txtfile1.ReadLine) strlen = len(content) if (InStr(1,content,”*”)) then pos = InStr(1,content,”*”) if ( pos = strlen) then lf.WriteLine “* Found : “ & content pos = InStr(1,content,”.”) pos = Instr(pos+1,content,”.”) pos = Instr(pos+1,content,”.”) saved_product_ver=Left(content,pos+2) if (alpha_product_ver <> ““) then if (Instr(1,saved_product_ver,alpha_product_ver) <> 0) then saved_product_ver = product_version saved_product_code = product_code else saved_product_ver=”” end if else if (Instr(1,saved_product_ver,product_version) <> 0) then saved_product_ver = product_version saved_product_code = product_code else saved_product_ver=”” end if end if lf.WriteLine “Saved Product Version : “ & saved_product_ver & “ “Saved Product Code : “ & saved_product_code end if end if loop txtfile1.close end if | “ & ‘If this version is not the currently active version then initiate uninstallation Teradata Tools and Utilities for Microsoft Windows Installation Guide 137 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script if (saved_product_ver <> product_version) then Call Initiate_Product_Uninstall(ProductName, product_code,product_version) end if else ‘For all other products ‘Initiate uninstallation Call Initiate_Product_Uninstall(ProductName, product_code,product_version) end if end if End Function ‘============================================================================================================ ========================================= Function Initiate_Product_Uninstall(ByVal ProductName, ByVal ProductCode, ByVal ProductVersion) Dim shellobj Dim vcompare Dim ExePath Dim ExeArgs set shellobj = CreateObject(“WScript.Shell”) lf.WriteLine “Initating Product uninstallation...” ‘Compare the product version with the currently installed product version vcompare = VersionCompare(ProductVersion, product_ver) ‘Uninstall currently installed version only if it is less than the product installed. if (vcompare = -1) then lf.WriteLine “Currently installed product version(“ & ProductVersion & version being installed(“ & product_ver & “)” lf.WriteLine “Proceed with uninstallation...” Call UninstallTTUProduct(ProductName, ProductCode, ProductVersion) elseif (vcompare = 1) then lf.WriteLine “Currently installed product version(“ & ProductVersion & version being installed(“ & product_ver & “)” lf.WriteLine “Uninstallation not required...” else lf.WriteLine “Currently installed product version(“ & ProductVersion & version being installed(“ & product_ver & “)” lf.WriteLine “Uninstallation not required...” end if version being “)” & “ < “ & “product “)” & “ > “ & “product “)” & “ = “ & “product ‘If uninstallation is not required for this version of the product and if it is not the current active TeraGSS version ‘then switch to this version so that uninstallation of other TeraGSS versions goes on smoothly. if (ProductName = TTUProducts(0)) then ‘TERAGSS if (vcompare = 0) and (ProductVersion <> saved_product_ver) then if (alpha_product_ver <> ““) then ‘If the version contains alpha character if (Package_64bit = true) then ‘ Looking for 64-bit TeraGSS ExePath=”nt-x8664\” & alpha_product_ver & “\bin\tdgssversion.exe” else ExePath=”nt-i386\” & alpha_product_ver & “\bin\tdgssversion.exe” end if ExeArgs=” -switch “ & alpha_product_ver else if (Package_64bit = true) then ‘ Looking for 64-bit TeraGSS ExePath=”nt-x8664\” & ProductVersion & “\bin\tdgssversion.exe” else ExePath=”nt-i386\” & ProductVersion & “\bin\tdgssversion.exe” end if ExeArgs=” -switch “ & ProductVersion end if lf.WriteLine “cmd /C “ & chr(34) & InstallPath & ExePath & chr(34) & ExeArgs rc = shellobj.Run(“cmd /C “ & chr(34) & InstallPath & ExePath & chr(34) & ExeArgs & “ >” & outputfile1,0,true) set txtfile1 = objFile.OpenTextFile(outputfile1, ForReading, False) content=”” do while txtfile1.AtEndOfStream <> True content = txtfile1.ReadLine if (Instr(1,content,”switch”) <> 0) then lf.WriteLine content 138 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script end if loop txtfile1.close end if end if End Function ‘============================================================================================================ ========================================= ‘Extract the Product Code from the uninstall registry key Function ExtractProductCode ( ByVal uninst_keyname ) Dim pos Dim strlen strlen = len(uninst_keyname) pos = InStr(1,uninst_keyname,”{“) ExtractProductCode = Right(uninst_keyname,(strlen-pos)+1) Exit Function End Function ‘============================================================================================================ ========================================= ‘Extract the Product Version from the uninstall registry key Function ExtractProductVersion ( ByVal uninst_keyname, ByVal ProductName ) Dim outputobj Dim content Dim pos Dim strlen Dim part Dim lpart Dim rpart Dim strComments ‘For TeraGSS the DisplayVersion is not populated. Instead the Comments Registry value contains the actual product version. ‘So the comments registry value in the uninstall registry key is read for TeraGSS to get the product version. if (ProductName = TTUProducts(0)) then ‘TERAGSS Set Inparams = objStdRegProv.Methods_(“GetStringValue”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = uninst_keyname Inparams.Svaluename = “Comments” set Outparams = objStdRegProv.ExecMethod_(“GetStringValue”, Inparams,,objCtx) strComments = Outparams.SValue strlen = len(strComments) pos = InStr(1,strComments,”Version”) if (pos > 1 ) then ‘Extract the version only if “Version” is found, otherwise set the product_version blank. product_version = Right(strComments,(strlen-(pos+7))) else product_version=”01.00” end if ‘Format the product_version as xx.xx or xx.xx.xx or xx.xx.xx.xx strlen = len(product_version) pos = InStr(1,product_version,”.”) lpart=Left(product_version,pos-1) rpart=Right(product_version,len(product_version)-pos) if (len(lpart) = 1) then lpart=”0” & lpart end if do while (pos > 1) pos = InStr(1,rpart,”.”) if (pos > 1) then part=left(rpart,pos-1) rpart=Right(rpart,len(rpart)-pos) if (len(part) = 1) then part=”0” & part end if Teradata Tools and Utilities for Microsoft Windows Installation Guide 139 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script lpart = lpart & “.” & part else if (len(rpart) = 1) then rpart=”0” & rpart end if exit do end if loop product_version = lpart & “.” & rpart do while (len(product_version) < 11) product_version = product_version & “.00” loop ‘If the product_version contains an alpha character, removing it. pos = InStr(1,product_version,”.”) alpha_char=Mid(product_version,pos-1,1) if (IsNumeric(alpha_char)) then alpha_product_ver=”” alpha_char=”” else alpha_product_ver=product_version lpart = Left(product_version,pos-2) rpart = Right(product_version,len(product_version)-pos) product_version = lpart & “.” & rpart end if lf.WriteLine “Product Version : “ & product_version & “ | Alpha Product Version : “ & alpha_product_ver else ‘For other products Set Inparams = objStdRegProv.Methods_(“GetStringValue”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = uninst_keyname Inparams.Svaluename = “DisplayVersion” set Outparams = objStdRegProv.ExecMethod_(“GetStringValue”, Inparams,,objCtx) product_version = Outparams.SValue ‘wscript.Echo “DisplayVersion : “ & Outparams.SValue end if ExtractProductVersion = product_version Exit Function End Function ‘============================================================================================================ ========================================= ‘Some useful information like the DisplayName and Hex_Version from the uninstall registry key is stored so that it can be used to identify the ‘product’s registry entries in HKLM\Software\Classes\Installer\Products registry entries. Function ExtractUninstallInfo(ByVal uninst_keyname, ByVal ProductName) Dim shellobj Dim outputobj Dim content Dim pos Dim temp_ver Dim temp_name Dim strlen Dim strComments ‘Get DisplayName for the product. This will be used while deleting the HKLM\Software\Classes\Installer \Products registry entry. Set Inparams = objStdRegProv.Methods_(“GetStringValue”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = uninst_keyname Inparams.Svaluename = “DisplayName” set Outparams = objStdRegProv.ExecMethod_(“GetStringValue”, Inparams,,objCtx) temp_name = Outparams.SValue 140 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script ‘Get comments for the product. This will be used while deleting the HKLM\Software\Classes\Installer \Products registry entry. Set Inparams = objStdRegProv.Methods_(“GetStringValue”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = uninst_keyname Inparams.Svaluename = “Comments” set Outparams = objStdRegProv.ExecMethod_(“GetStringValue”, Inparams,,objCtx) strComments = Outparams.SValue strlen = len(strComments) pos = InStr(1,strComments,”Version”) if (pos > 1 ) then ‘Extract the version only if “Version” is found, otherwise set the product_version blank. temp_ver = Right(strComments,(strlen-(pos+7))) else temp_ver=”” end if ‘Store DisplayName. It will be used to search the product in HKLM\Software\Classes\Installer\Products. Disp_Name = temp_name ‘Get HexVersion for the product. This will be used while deleting the HKLM\Software\Classes\Installer \Products registry entry. Set Inparams = objStdRegProv.Methods_(“GetDWORDValue”).Inparameters Inparams.Hdefkey = HKLM Inparams.sSubkeyname = uninst_keyname Inparams.sValuename = “Version” set Outparams = objStdRegProv.ExecMethod_(“GetDWORDValue”, Inparams,,objCtx) Hex_Version = Outparams.uValue lf.WriteLine “UninstallInfo : DisplayName = “ & Disp_Name & “\t Hex_Version = “ & Hex_Version End Function ‘============================================================================================================ ========================================= ‘Compare the version of the installed product with ‘the version of the product being installed Function VersionCompare(Byval product_ver, Byval product_version) Dim strlen Dim pos, pos1 Dim first_ver_1, first_ver_2 Dim second_ver_1, second_ver_2 Dim result ‘Get xx.yy(Major Release number) from the version string xx.yy.zz.kk strlen = len(product_ver) pos = instr(1,product_ver, “.”) first_ver_1=Mid(product_ver,1,pos-1) ‘Get yy from the version string xx.yy.zz.kk pos1 = instr(pos+1, product_ver, “.”) if (pos1 = 0) then pos1=strlen+1 end if first_ver_2=Mid(product_ver,pos+1,pos1-pos-1) ‘Get xx from the version string xx.yy.zz.kk strlen = len(product_version) pos = instr(1,product_version, “.”) second_ver_1=Mid(product_version,1,pos-1) ‘Get yy from the version string pos1 = instr(pos+1, product_version, “.”) if (pos1 = 0) then pos1=strlen+1 end if second_ver_2=Mid(product_version,pos+1,pos1-pos-1) ‘Compare the first two parts of the version string. if CInt(first_ver_1) < CInt(second_ver_1) then Teradata Tools and Utilities for Microsoft Windows Installation Guide 141 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script result=-1 elseif CInt(first_ver_1) > CInt(second_ver_1) then result=1 else if CInt(first_ver_2) < CInt(second_ver_2) then result=-1 elseif CInt(first_ver_2) > CInt(second_ver_2) then result=1 else result=0 End if End if VersionCompare=result End Function ‘============================================================================================================ ========================================= ‘Generates the uninstall ISS file for InstallScript MSI products using the productcode supplied. Function GenerateISSFile ( ByVal ProductName, ByVal ProductCode, ByVal ProductVersion ) Dim shellobj Dim outputobj Dim content Dim pos1 Dim pos2 Dim f_product_code Dim TempFolder Dim ISSFile Dim LogFile Dim tf Dim pkg_64 if (Package_64bit = True) then pkg_64 = “x8664_” else pkg_64 = ““ end if TempFolder = winroot & “\temp” Select case ProductName case TTUProducts(1) ‘TDICU ISSFile = “uninstall_tdicu_” & pkg_64 & ProductVersion & “.iss” LogFile = “uninstall_tdicu_” & pkg_64 & ProductVersion & “.log” case TTUProducts(2) ‘CLIv2 ISSFile = “uninstall_cliv2_” & pkg_64 & ProductVersion & “.iss” LogFile = “uninstall_cliv2_” & pkg_64 & ProductVersion & “.log” case TTUProducts(3) ‘TDODBC ISSFile = “uninstall_tdodbc_” & pkg_64 & ProductVersion & “.iss” LogFile = “uninstall_tdodbc_” & pkg_64 & ProductVersion & “.log” case TTUProducts(4) ‘PIOM ISSFile = “uninstall_piom_” & ProductVersion & “.iss” LogFile = “uninstall_piom_” & ProductVersion & “.log” case TTUProducts(5) ‘BTEQ ISSFile = “uninstall_bteq_” & ProductVersion & “.iss” LogFile = “uninstall_bteq_” & ProductVersion & “.log” case TTUProducts(6) ‘FASTLD ISSFile = “uninstall_fastld_” & ProductVersion & “.iss” LogFile = “uninstall_fastld_” & ProductVersion & “.log” case TTUProducts(7) ‘MLOAD ISSFile = “uninstall_mload_” & ProductVersion & “.iss” LogFile = “uninstall_mload_” & ProductVersion & “.log” case TTUProducts(8) ‘FASTEXP ISSFile = “uninstall_fastexp_” & ProductVersion & “.iss” LogFile = “uninstall_fastexp_” & ProductVersion & “.log” case TTUProducts(9) ‘TPUMP ISSFile = “uninstall_tpump_” & ProductVersion & “.iss” LogFile = “uninstall_tpump_” & ProductVersion & “.log” case TTUProducts(10) ‘TDOLEDB ISSFile = “uninstall_tdoledb_” & ProductVersion & “.iss” 142 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script LogFile = “uninstall_tdoledb_” & ProductVersion & “.log” case TTUProducts(11) ‘SQLPP ISSFile = “uninstall_sqlpp_” & pkg_64 & ProductVersion & “.iss” LogFile = “uninstall_sqlpp_” & pkg_64 & ProductVersion & “.log” case TTUProducts(12) ‘NPAXSMOD ISSFile = “uninstall_npaxsmod_” & ProductVersion & “.iss” LogFile = “uninstall_npaxsmod_” & ProductVersion & “.log” case TTUProducts(13) ‘MQAXSMOD ISSFile = “uninstall_mqaxsmod_” & ProductVersion & “.iss” LogFile = “uninstall_mqaxsmod_” & ProductVersion & “.log” case TTUProducts(14) ‘OLEDBAXSMOD ISSFile = “uninstall_oledbaxsmod_” & ProductVersion & “.iss” LogFile = “uninstall_oledbaxsmod_” & ProductVersion & “.log” case TTUProducts(15) ‘JMSAXSMOD ISSFile = “uninstall_jmsaxsmod_” & ProductVersion & “.iss” LogFile = “uninstall_jmsaxsmod_” & ProductVersion & “.log” end select ISSFileName=TempFolder & “\” & ISSFile LogFileName=TempFolder & “\” & LogFile Set tf = objFile.CreateTextFile(ISSFileName, True) ‘Generate the .iss file. Some products have special handling. Select case ProductName case TTUProducts(1) ‘TDICU. An extra entry is needed in the .iss file for TDICU. tf.WriteLine (“[“ & ProductCode & “-DlgOrder]”) tf.WriteLine (“Dlg0=” & ProductCode & “-AskYesNo-0”) tf.WriteLine (“Count=3”) tf.WriteLine (“Dlg1=” & ProductCode & “-SprintfBox-0”) tf.WriteLine (“Dlg2=” & ProductCode & “-SdFinish-0”) tf.WriteLine (“[“ & ProductCode & “-AskYesNo-0]”) tf.WriteLine (“Result=1”) tf.WriteLine (“[“ & ProductCode & “-SprintfBox-0]”) tf.WriteLine (“Result=1”) tf.WriteLine (“[“ & ProductCode & “-SdFinish-0]”) tf.WriteLine (“Result=1”) tf.close ‘CLiv2, TDODBC, PIOM, BTEQ, FASTLD, MLOAD, FASTEXP, TPUMP, SQLPP, ‘NPAXSMOD, MQAXSMOD, OLEDBAXSMOD, JMSAXSMOD case TTUProducts(2), _ TTUProducts(3), _ TTUProducts(4), _ TTUProducts(5), _ TTUProducts(6), _ TTUProducts(7), _ TTUProducts(8), _ TTUProducts(9), _ TTUProducts(11), _ TTUProducts(12), _ TTUProducts(13), _ TTUProducts(14), _ TTUProducts(15) tf.WriteLine (“[“ & ProductCode & “-DlgOrder]”) tf.WriteLine (“Dlg0=” & ProductCode & “-SprintfBox-0”) tf.WriteLine (“Count=2”) tf.WriteLine (“Dlg1=” & ProductCode & “-SdFinish-0”) tf.WriteLine (“[“ & ProductCode & “-SprintfBox-0]”) tf.WriteLine (“Result=1”) tf.WriteLine (“[“ & ProductCode & “-SdFinish-0]”) tf.WriteLine (“Result=1”) tf.close case TTUProducts(10) ‘TDOLEDB. Need to handle the Welcome maintenance dialog during uninstallation. tf.WriteLine (“[“ & ProductCode & “-DlgOrder]”) tf.WriteLine (“Dlg0=” & ProductCode & “-SdWelcomeMaint-0”) tf.WriteLine (“Count=3”) tf.WriteLine (“Dlg1=” & ProductCode & “-SprintfBox-0”) tf.WriteLine (“Dlg2=” & ProductCode & “-SdFinish-0”) tf.WriteLine (“[“ & ProductCode & “-SdWelcomeMaint-0]”) tf.WriteLine (“Result=303”) tf.WriteLine (“[“ & ProductCode & “-SprintfBox-0]”) Teradata Tools and Utilities for Microsoft Windows Installation Guide 143 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script tf.WriteLine (“Result=1”) tf.WriteLine (“[“ & ProductCode & “-SdFinish-0]”) tf.WriteLine (“Result=1”) tf.close end select lf.WriteLine “ISS File generated for the product. ISSFileName = “ & ISSFileName & “ LogFileName = “ & LogFileName End Function ‘============================================================================================================ ========================================= ‘Uninstall the product using one of the uninstallation methods based on the product. ‘Using IDriver.exe to uninstall the product if the package is installscript MSI. ‘Using MSIExec.exe to uninstall the product if the package is Basic MSI. Function UninstallTTUProduct(ByVal ProductName, ByVal ProductCode, ByVal ProductVersion) Dim shellobj Dim outputobj Dim content Dim rc Dim IDriver9Path, IDriver7Path set shellobj = CreateObject(“WScript.Shell”) ‘Set the IDriver.exe path based on the processor architecture. Since IDriver.exe is a 32-bit program ‘it resides in Program Files (x86) folder on 64-bit machines. if (Proc_Arch = “AMD64”) then IDriver7Path = Mid(program_files_x86_dir,1,3) & chr(34) & Mid(program_files_x86_dir, 4,len(program_files_x86_dir)-3)& chr(34) & “\””Common Files””\InstallShield\Driver\7\””Intel 32”” \IDriver.exe” IDriver9Path = Mid(program_files_x86_dir,1,3) & chr(34) & Mid(program_files_x86_dir, 4,len(program_files_x86_dir)-3)& chr(34) & “\””Common Files””\InstallShield\Driver\9\””Intel 32”” \IDriver.exe” else IDriver7Path = Mid(program_files_dir,1,3) & chr(34) & Mid(program_files_dir, 4,len(program_files_dir)-3)& chr(34) & “\””Common Files””\InstallShield\Driver\7\””Intel 32””\IDriver.exe” IDriver9Path = Mid(program_files_dir,1,3) & chr(34) & Mid(program_files_dir, 4,len(program_files_dir)-3)& chr(34) & “\””Common Files””\InstallShield\Driver\9\””Intel 32””\IDriver.exe” end if lf.WriteLine “Uninstalling “ & ProductName & “ : “ & ProductVersion & “ : “ & ProductCode select case ProductName case TTUProducts(0) ‘TeraGSS if (Package_64bit = True) then LogFileName= winroot & “\temp\uninstall_teragss_x8664_” & ProductVersion & “.log” else LogFileName= winroot & “\temp\uninstall_teragss_” & ProductVersion & “.log” end if ‘Copy the TdgssUserConfigFile.xml from NCR location to a temporary location so that it can be copied to the Teradata location rc = shellobj.Run(“cmd /C copy “ & chr(34) & InstallPath & “Site\TdgssUserConfigFile.xml” & chr(34) & “ “ & winroot & “\temp”,0,true) ‘Run the command to uninstall the product. lf.WriteLine “cmd /C MsiExec.exe /qn /X” & ProductCode & _ “ /LV! “ & chr(34) & LogFileName & chr(34) rc = shellobj.Run(“cmd /C MsiExec.exe /qn /X” & ProductCode & _ “ /LV! “ & chr(34) & LogFileName & chr(34), 0, true) ‘TDICU, CLiv2, TDODBC, PIOM, BTEQ, FASTLD, MLOAD, FASTEXP, TPUMP, TDOLEDB, SQLPP, ‘NPAXSMOD, MQAXSMOD, OLEDBAXSMOD, JMSAXSMOD case TTUProducts(1), _ TTUProducts(2), _ TTUProducts(3), _ TTUProducts(4), _ TTUProducts(5), _ 144 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script TTUProducts(6), _ TTUProducts(7), _ TTUProducts(8), _ TTUProducts(9), _ TTUProducts(10), _ TTUProducts(11), _ TTUProducts(12), _ TTUProducts(13), _ TTUProducts(14), _ TTUProducts(15) ‘Generate the response file(.iss) for uninstallation GenerateISSFile ProductName,ProductCode,ProductVersion ‘Get the InstallPath of the product. This is used for cleanup of left over remnants of the installation. GetInstallPath ProductName,ProductVersion ‘Run the command to uninstall the product. ‘For earlier versions of TDODBC and SQLPP IDriver.exe from Installshield version 7.0 is required. if ((ProductName = TTUProducts(3)) OR (ProductName = TTUProducts(11))) then lf.WriteLine “cmd /C “ & IDriver7Path & “ /M” & ProductCode & _ “ /verbose” & chr(34) & LogFileName & chr(34) & _ “ /s /f1” & chr(34) & ISSFileName & chr(34) rc = shellobj.Run(“cmd /C “ & IDriver7Path & “ /M” & ProductCode & _ “ /verbose” & chr(34) & LogFileName & chr(34) & _ “ /s /f1” & chr(34) & ISSFileName & chr(34), 0, true) end if ‘For all other products including newer ‘Installshield version 9.0 is required. lf.WriteLine “cmd /C “ & IDriver9Path & “ /verbose” “ /s /f1” & versions of TDODBC & SQLPP IDriver.exe from “ /M” & ProductCode & _ & chr(34) & LogFileName & chr(34) & _ chr(34) & ISSFileName & chr(34) rc = shellobj.Run(“cmd /C “ & IDriver9Path & “ /M” & ProductCode & _ “ /verbose” & chr(34) & LogFileName & chr(34) & _ “ /s /f1” & chr(34) & ISSFileName & chr(34), 0, true) case TTUProducts(16) ‘SQLA LogFileName= winroot & “\temp\uninstall_sqla_” & ProductVersion & “.log” ‘Run the command to uninstall the product. lf.WriteLine “cmd /C MsiExec.exe /qn /X” & ProductCode & _ “ /LV! “ & chr(34) & LogFileName & chr(34) rc = shellobj.Run(“cmd /C MsiExec.exe /qn /X” & ProductCode & _ “ /LV! “ & chr(34) & LogFileName & chr(34), 0, true) end select if (rc = 0) then ‘Upon successful uninstallation verify that no remnants of the product are left over. lf.WriteLine ProductName & “ uninstallation successful....” Verify_Uninstallation ProductName,ProductCode,ProductVersion else ‘Incase of an uninstallation failure also verify that no remnants of the product are left over. lf.WriteLine ProductName & “ uninstallation failed. rc = “ & rc Verify_Uninstallation ProductName,ProductCode,ProductVersion end if End Function ‘============================================================================================================ ========================================= ‘Get the install path for the product from the registry. Function GetInstallPath(ByVal ProductName, ByVal ProductVersion) Dim content Dim strlen Dim pos Dim RegPath Dim RegValue Teradata Tools and Utilities for Microsoft Windows Installation Guide 145 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script lf.WriteLine “Get InstallPath for “ & ProductName & “ : “ & ProductVersion if (Wow6432Node = False) then RegPath = “HKLM\SOFTWARE\NCR\” & ProductName else RegPath = “HKLM\SOFTWARE\Wow6432Node\NCR\” & ProductName end if Select case ProductName Case TTUProducts(0) ‘TeraGSS if (Wow6432Node = False) then InstallPath = “C:\Program Files\NCR\Teradata GSS\” else InstallPath = “C:\Program Files (x86)\NCR\Teradata GSS\” end if RegValue=”InstallDir” Case TTUProducts(1) ‘TDICU if (Wow6432Node = False) then InstallPath = “C:\Program Files\NCR\Common Files\Shared ICU Libraries for Teradata\lib” else InstallPath = “C:\Program Files (x86)\NCR\Common Files\Shared ICU Libraries for Teradata\lib” end if RegValue=”InstallDLLPath” Case TTUProducts(2) ‘CLIv2 if (Wow6432Node = False) then RegPath = RegPath & “\” & ProductVersion InstallPath = “C:\Program Files\NCR\Teradata Client\cliv2\” else RegPath = RegPath & “\” & ProductVersion InstallPath = “C:\Program Files (x86)\NCR\Teradata Client\cliv2\” end if RegValue=”InstallDLLsPath” Case TTUProducts(3) ‘TDODBC if (Wow6432Node = False) then InstallPath = “C:\Program Files\NCR\ODBC Driver for Teradata\” else InstallPath = “C:\Program Files (x86)\NCR\ODBC Driver for Teradata\” end if RegValue=”InstallPath” Case TTUProducts(4) ‘PIOM if (Wow6432Node = False) then InstallPath = “C:\Program Files\NCR\Teradata Client\bin\” else InstallPath = “C:\Program Files (x86)\NCR\Teradata Client\bin\” end if RegValue=”InstallDLLPath” Case TTUProducts(5) ‘BTEQ if (Wow6432Node = False) then InstallPath = “C:\Program Files\NCR\Teradata Client\” else InstallPath = “C:\Program Files (x86)\NCR\Teradata Client\” end if RegValue=”InstallPath” Case TTUProducts(6) ‘FASTLD if (Wow6432Node = False) then RegPath = “HKLM\SOFTWARE\NCR\Teradata Client” InstallPath = “C:\Program Files\NCR\Teradata Client\” else RegPath = “HKLM\SOFTWARE\Wow6432Node\NCR\Teradata Client” InstallPath = “C:\Program Files (x86)\NCR\Teradata Client\” end if RegValue=”DestPath” Case TTUProducts(7) ‘MLOAD if (Wow6432Node = False) then InstallPath = “C:\Program Files\NCR\Teradata Client\” else InstallPath = “C:\Program Files (x86)\NCR\Teradata Client\” end if RegValue=”InstallBasePath” Case TTUProducts(8) ‘FASTEXP 146 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script if (Wow6432Node = False) then InstallPath = “C:\Program Files\NCR\Teradata Client\” else InstallPath = “C:\Program Files (x86)\NCR\Teradata Client\” end if RegValue=”InstallBasePath” Case TTUProducts(9) ‘TPUMP if (Wow6432Node = False) then InstallPath = “C:\Program Files\NCR\Teradata Client\” else InstallPath = “C:\Program Files (x86)\NCR\Teradata Client\” end if RegValue=”InstallBasePath” Case TTUProducts(10) ‘TDOLEDB if (Wow6432Node = False) then RegPath = RegPath & “\” & ProductVersion InstallPath = “C:\Program Files\NCR\Teradata Client\OLE DB Provider for Teradata\” else RegPath = RegPath & “\” & ProductVersion InstallPath = “C:\Program Files (x86)\NCR\Teradata Client\OLE DB Provider for Teradata\” end if RegValue=”InstallDir” Case TTUProducts(11) ‘SQLPP if (Wow6432Node = False) then RegPath = RegPath & “\” & ProductVersion InstallPath = “C:\Program Files\NCR\Teradata Client\pp2” else RegPath = RegPath & “\” & ProductVersion InstallPath = “C:\Program Files (x86)\NCR\Teradata Client\pp2” end if RegValue=”InstallPP2RuntimePath” Case TTUProducts(12) ‘NPAXSMOD if (Wow6432Node = False) then InstallPath = “C:\Program Files\Common Files\NCR\AXSMOD\” else InstallPath = “C:\Program Files (x86)\Common Files\NCR\AXSMOD\” end if RegValue=”InstallPath” Case TTUProducts(13) ‘MQAXSMOD if (Wow6432Node = False) then InstallPath = “C:\Program Files\Common Files\NCR\AXSMOD\” else InstallPath = “C:\Program Files (x86)\Common Files\NCR\AXSMOD\” end if RegValue=”InstallPath” Case TTUProducts(14) ‘OLEDBAXSMOD if (Wow6432Node = False) then InstallPath = “C:\Program Files\Common Files\NCR\AXSMOD\” else InstallPath = “C:\Program Files (x86)\Common Files\NCR\AXSMOD\” end if RegValue=”InstallPath” Case TTUProducts(15) ‘JMSAXSMOD if (Wow6432Node = False) then InstallPath = “C:\Program Files\Common Files\NCR\JMSAXSMOD\” else InstallPath = “C:\Program Files (x86)\Common Files\NCR\JMSAXSMOD\” end if RegValue=”InstallDir” end select ‘Check for registry entries in HKLM\Software\NCR rc = objWshShell.Run(“cmd /C reg query “ & chr(34) & RegPath & chr(34) & “ /v “ & RegValue & “ > “ & outputfile1,0,true) set txtfile1 = objFile.OpenTextFile(outputfile1, ForReading, False) if (txtfile1.AtEndOfStream = False) then content = ““ Do While txtfile1.AtEndOfStream <> True Teradata Tools and Utilities for Microsoft Windows Installation Guide 147 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script content = ltrim(txtfile1.ReadLine) if instr(1,content, RegValue) <> 0 then strlen = len(content) pos = InStr(1,content,”:\”) InstallPath = Right(content,(strlen-pos)+2) lf.WriteLine “Product Install Path from registry : “ & InstallPath exit do end if loop else lf.WriteLine “No output for reg query “ & chr(34) & RegPath & ProductName & chr(34) & “ /v “ & RegValue end if txtfile1.close lf.WriteLine “Product Install Path : “ & InstallPath End Function ‘============================================================================================================ ========================================= ‘Verifies whether the product uninstallation was successful and if any remnants(Files, registry entries, PATH entries) of the product are left over on the machine. Function Verify_Uninstallation(ByVal ProductName, ByVal ProductCode, ByVal ProductVersion) Dim TempInstallPath lf.WriteLine “Verifying uninstallation of “ & ProductName & “ : “ & ProductVersion & “ : “ & ProductCode VerifyProductFiles ProductName,ProductVersion, InstallPath VerifyRegistryEntries ProductName, ProductCode, ProductVersion ‘Since the InstallPath only points to the top installation folder. The exact entry for the product in the PATH variable ‘is passed to PATHCleanup, so that the entry can be removed from PATH if not already done. select case ProductName case TTUProducts(5) ‘BTEQ PATHCleanup InstallPath & “Bin” case TTUProducts(6) ‘FASTLD PATHCleanup InstallPath & “Bin” case TTUProducts(7) ‘MLOAD PATHCleanup InstallPath & “Bin” case TTUProducts(8) ‘FASTEXP PATHCleanup InstallPath & “Bin” case TTUProducts(9) ‘TPUMP PATHCleanup InstallPath & “Bin” case TTUProducts(11) ‘SQLPP TempInstallPath=replace(InstallPath,”\pp2”,”\\pp2”) InstallPath=TempInstallPath TempInstallPath=replace(InstallPath,”pp2”,”Bin”) PATHCleanup TempInstallPath PATHCleanup InstallPath case else PATHCleanup InstallPath end select lf.WriteLine “Verification successful... “ End Function ‘============================================================================================================ ========================================= ‘Verifies that the files installed by the products are removed during the uninstallation. ‘Removes the left over files forcibly. Function VerifyProductFiles(ByVal ProductName, ByVal ProductVersion, ByVal InstallPath) Dim objFilesys Dim TempInstallPath Dim rc Set objFilesys = CreateObject(“Scripting.FilesystemObject”) select case ProductName case TTUProducts(0) ‘TERAGSS if (alpha_product_ver <> ““) then temp_product_ver = alpha_product_ver else 148 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script temp_product_ver = ProductVersion end if if (Package_64bit = true) then folderpath=InstallPath & “nt-x8664\” & temp_product_ver else folderpath=InstallPath & “nt-i386\” & temp_product_ver end if if objFilesys.FolderExists(folderpath) then lf.WriteLine “Folder found : “ & folderpath rc = objFilesys.DeleteFolder(folderpath,true) else lf.WriteLine “Folder not found : “ & folderpath end if case TTUProducts(1) ‘TDICU ‘Check if ICU3.4 files exist on the machine if objFilesys.FileExists(InstallPath & “\icudttd34l.dll”) then lf.WriteLine “File found : “ & InstallPath & “\icudttd34l.dll” rc = objFilesys.DeleteFile(InstallPath & “\icudttd34l.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\icudttd34l.dll” end if if objFilesys.FileExists(InstallPath & “\icuintd34.dll”) then lf.WriteLine “File found : “ & InstallPath & “\icuintd34.dll” rc = objFilesys.DeleteFile(InstallPath & “\icuintd34.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\icuintd34.dll” end if if objFilesys.FileExists(InstallPath & “\icuiotd34.dll”) then lf.WriteLine “File found : “ & InstallPath & “\icuiotd34.dll” rc = objFilesys.DeleteFile(InstallPath & “\icuiotd34.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\icuiotd34.dll” end if if objFilesys.FileExists(InstallPath & “\iculetd34.dll”) then lf.WriteLine “File found : “ & InstallPath & “\iculetd34.dll” rc = objFilesys.DeleteFile(InstallPath & “\iculetd34.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\iculetd34.dll” end if if objFilesys.FileExists(InstallPath & “\iculxtd34.dll”) then lf.WriteLine “File found : “ & InstallPath & “\iculxtd34.dll” rc = objFilesys.DeleteFile(InstallPath & “\iculxtd34.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\iculxtd34.dll” end if if objFilesys.FileExists(InstallPath & “\icuuctd34.dll”) then lf.WriteLine “File found : “ & InstallPath & “\icuuctd34.dll” rc = objFilesys.DeleteFile(InstallPath & “\icuuctd34.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\icuuctd34.dll” end if ‘Check if ICU 2.8 files exist on the machine. if objFilesys.FileExists(InstallPath & “\icudttd28l.dll”) then lf.WriteLine “File found : “ & InstallPath & “\icudttd28l.dll” rc = objFilesys.DeleteFile(InstallPath & “\icudttd28l.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\icudttd28l.dll” end if if objFilesys.FileExists(InstallPath & “\icuintd28.dll”) then lf.WriteLine “File found : “ & InstallPath & “\icuintd28.dll” rc = objFilesys.DeleteFile(InstallPath & “\icuintd28.dll”,true) Teradata Tools and Utilities for Microsoft Windows Installation Guide 149 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script else lf.WriteLine “File not found : “ & InstallPath & “\icuintd28.dll” end if if objFilesys.FileExists(InstallPath & “\icuiotd28.dll”) then lf.WriteLine “File found : “ & InstallPath & “\icuiotd28.dll” rc = objFilesys.DeleteFile(InstallPath & “\icuiotd28.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\icuiotd28.dll” end if if objFilesys.FileExists(InstallPath & “\iculetd28.dll”) then lf.WriteLine “File found : “ & InstallPath & “\iculetd28.dll” rc = objFilesys.DeleteFile(InstallPath & “\iculetd28.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\iculetd28.dll” end if if objFilesys.FileExists(InstallPath & “\iculxtd28.dll”) then lf.WriteLine “File found : “ & InstallPath & “\iculxtd28.dll” rc = objFilesys.DeleteFile(InstallPath & “\iculxtd28.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\iculxtd28.dll” end if if objFilesys.FileExists(InstallPath & “\icuuctd28.dll”) then lf.WriteLine “File found : “ & InstallPath & “\icuuctd28.dll” rc = objFilesys.DeleteFile(InstallPath & “\icuuctd28.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “\icuuctd28.dll” end if if objFilesys.FileExists(InstallPath & “\MSVCP71.DLL”) then lf.WriteLine “File found : “ & InstallPath & “\MSVCP71.DLL” rc = objFilesys.DeleteFile(InstallPath & “\MSVCP71.DLL”,true) else lf.WriteLine “File not found : “ & InstallPath & “\MSVCP71.DLL” end if if objFilesys.FileExists(InstallPath & “\MSVCR71.DLL”) then lf.WriteLine “File found : “ & InstallPath & “\MSVCR71.DLL” rc = objFilesys.DeleteFile(InstallPath & “\MSVCR71.DLL”,true) else lf.WriteLine “File not found : “ & InstallPath & “\MSVCR71.DLL” end if case TTUProducts(2) ‘CLIv2 ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “wincli32.dll”) then lf.WriteLine “File found : “ & InstallPath & “wincli32.dll” rc = objFilesys.DeleteFile(InstallPath & “wincli32.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “wincli32.dll” end if ‘terasso.dll is not shipped with CLIv2 if objFilesys.FileExists(InstallPath & “terasso.dll”) then lf.WriteLine “File found : “ & InstallPath & “terasso.dll” rc = objFilesys.DeleteFile(InstallPath & “terasso.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “terasso.dll” end if if objFilesys.FileExists(InstallPath & “tdusr32.dll”) then lf.WriteLine “File found : “ & InstallPath & “tdusr32.dll” rc = objFilesys.DeleteFile(InstallPath & “tdusr32.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “tdusr32.dll” end if if objFilesys.FileExists(InstallPath & “localisation.dll”) then 150 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script lf.WriteLine “File found : “ & InstallPath & “localisation.dll” rc = objFilesys.DeleteFile(InstallPath & “localisation.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “localisation.dll” end if if objFilesys.FileExists(InstallPath & “clispb.dat”) then lf.WriteLine “File found : “ & InstallPath & “clispb.dat” rc = objFilesys.DeleteFile(InstallPath & “clispb.dat”,true) else lf.WriteLine “File not found : “ & InstallPath & “clispb.dat” end if if objFilesys.FileExists(InstallPath & “\lib\tdusr32.lib”) then lf.WriteLine “File found : “ & InstallPath & “\lib\tdusr32.lib” rc = objFilesys.DeleteFile(InstallPath & “\lib\tdusr32.lib”,true) else lf.WriteLine “File not found : “ & InstallPath & “\lib\tdusr32.lib” end if if objFilesys.FileExists(InstallPath & “\lib\wincli32.lib”) then lf.WriteLine “File found : “ & InstallPath & “\lib\wincli32.lib” rc = objFilesys.DeleteFile(InstallPath & “\lib\wincli32.lib”,true) else lf.WriteLine “File not found : “ & InstallPath & “\lib\wincli32.lib” end if if objFilesys.FileExists(InstallPath & “\inc\cliv2if.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\cliv2if.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\cliv2if.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\cliv2if.h” end if if objFilesys.FileExists(InstallPath & “\inc\coperr.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\coperr.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\coperr.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\coperr.h” end if if objFilesys.FileExists(InstallPath & “\inc\coptypes.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\coptypes.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\coptypes.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\coptypes.h” end if if objFilesys.FileExists(InstallPath & “\inc\dbcacnx.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\dbcacnx.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\dbcacnx.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\dbcacnx.h” end if if objFilesys.FileExists(InstallPath & “\inc\dbcarea.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\dbcarea.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\dbcarea.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\dbcarea.h” end if if objFilesys.FileExists(InstallPath & “\inc\dbcerr.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\dbcerr.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\dbcerr.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\dbcerr.h” end if if objFilesys.FileExists(InstallPath & “\inc\dbchqep.h”) then Teradata Tools and Utilities for Microsoft Windows Installation Guide 151 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script lf.WriteLine “File found : “ & InstallPath & “\inc\dbchqep.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\dbchqep.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\dbchqep.h” end if if objFilesys.FileExists(InstallPath & “\inc\mosiif.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\mosiif.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\mosiif.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\mosiif.h” end if if objFilesys.FileExists(InstallPath & “\inc\nojunk.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\nojunk.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\nojunk.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\nojunk.h” end if if objFilesys.FileExists(InstallPath & “\inc\parcel.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\parcel.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\parcel.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\parcel.h” end if if objFilesys.FileExists(InstallPath & “\inc\resource.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\resource.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\resource.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\resource.h” end if if objFilesys.FileExists(InstallPath & “\inc\wincliv2.h”) then lf.WriteLine “File found : “ & InstallPath & “\inc\wincliv2.h” rc = objFilesys.DeleteFile(InstallPath & “\inc\wincliv2.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “\inc\wincliv2.h” end if if objFilesys.FileExists(InstallPath & “\clisamp\clisamp.c”) then lf.WriteLine “File found : “ & InstallPath & “\clisamp\clisamp.c” rc = objFilesys.DeleteFile(InstallPath & “\clisamp\clisamp.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “\clisamp\clisamp.c” end if if objFilesys.FileExists(InstallPath & “\clisamp\makesamp.win”) then lf.WriteLine “File found : “ & InstallPath & “\clisamp\makesamp.win” rc = objFilesys.DeleteFile(InstallPath & “\clisamp\makesamp.win”,true) else lf.WriteLine “File not found : “ & InstallPath & “\clisamp\makesamp.win” end if if objFilesys.FileExists(InstallPath & “\UserExit\CliLgnEx.c”) then lf.WriteLine “File found : “ & InstallPath & “\UserExit\CliLgnEx.c” rc = objFilesys.DeleteFile(InstallPath & “\UserExit\CliLgnEx.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “\UserExit\CliLgnEx.c” end if if objFilesys.FileExists(InstallPath & “\UserExit\CliPPS.c”) then lf.WriteLine “File found : “ & InstallPath & “\UserExit\CliPPS.c” rc = objFilesys.DeleteFile(InstallPath & “\UserExit\CliPPS.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “\UserExit\CliPPS.c” end if if objFilesys.FileExists(InstallPath & “\UserExit\tdusr.def”) then 152 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script lf.WriteLine “File found : “ & InstallPath & “\UserExit\tdusr.def” rc = objFilesys.DeleteFile(InstallPath & “\UserExit\tdusr.def”,true) else lf.WriteLine “File not found : “ & InstallPath & “\UserExit\tdusr.def” end if if objFilesys.FileExists(InstallPath & “\UserExit\tdusr.rc”) then lf.WriteLine “File found : “ & InstallPath & “\UserExit\tdusr.rc” rc = objFilesys.DeleteFile(InstallPath & “\UserExit\tdusr.rc”,true) else lf.WriteLine “File not found : “ & InstallPath & “\UserExit\tdusr.rc” end if if objFilesys.FileExists(InstallPath & “\UserExit\userexit.mak”) then lf.WriteLine “File found : “ & InstallPath & “\UserExit\userexit.mak” rc = objFilesys.DeleteFile(InstallPath & “\UserExit\userexit.mak”,true) else lf.WriteLine “File not found : “ & InstallPath & “\UserExit\userexit.mak” end if ‘Removing CLIv2 libraries from system32 if objFilesys.FileExists(winroot & “\system32\wincli32.dll”) then lf.WriteLine “File found : “ & winroot & “\system32\wincli32.dll” rc = objFilesys.DeleteFile(winroot & “\system32\wincli32.dll”,true) else lf.WriteLine “File not found : “ & winroot & “\system32\wincli32.dll” end if if objFilesys.FileExists(winroot & “\system32\tdusr32.dll”) then lf.WriteLine “File found : “ & winroot & “\system32\tdusr32.dll” rc = objFilesys.DeleteFile(winroot & “\system32\tdusr32.dll”,true) else lf.WriteLine “File not found : “ & winroot & “\system32\tdusr32.dll” end if if objFilesys.FileExists(winroot & “\system32\terasso.dll”) then lf.WriteLine “File found : “ & winroot & “\system32\terasso.dll” rc = objFilesys.DeleteFile(winroot & “\system32\terasso.dll”,true) else lf.WriteLine “File not found : “ & winroot & “\system32\terasso.dll” end if if objFilesys.FileExists(winroot & “\system32\localisation.dll”) then lf.WriteLine “File found : “ & winroot & “\system32\localisation.dll” rc = objFilesys.DeleteFile(winroot & “\system32\localisation.dll”,true) else lf.WriteLine “File not found : “ & winroot & “\system32\localisation.dll” end if case TTUProducts(3) ‘TDODBC ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “_unodbc.dll”) then lf.WriteLine “File found : “ & InstallPath & “_unodbc.dll” rc = objFilesys.DeleteFile(InstallPath & “_unodbc.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “_unodbc.dll” end if if objFilesys.FileExists(InstallPath & “Pbodb0x0.txt”) then lf.WriteLine “File found : “ & InstallPath & “Pbodb0x0.txt” rc = objFilesys.DeleteFile(InstallPath & “Pbodb0x0.txt”,true) else lf.WriteLine “File not found : “ & InstallPath & “Pbodb0x0.txt” end if if objFilesys.FileExists(InstallPath & “Readme.txt”) then lf.WriteLine “File found : “ & InstallPath & “Readme.txt” rc = objFilesys.DeleteFile(InstallPath & “Readme.txt”,true) else lf.WriteLine “File not found : “ & InstallPath & “Readme.txt” Teradata Tools and Utilities for Microsoft Windows Installation Guide 153 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script end if if objFilesys.FileExists(InstallPath & “tdata32.dll”) then lf.WriteLine “File found : “ & InstallPath & “tdata32.dll” rc = objFilesys.DeleteFile(InstallPath & “tdata32.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “tdata32.dll” end if if objFilesys.FileExists(InstallPath & “tdatas32.dll”) then lf.WriteLine “File found : “ & InstallPath & “tdatas32.dll” rc = objFilesys.DeleteFile(InstallPath & “tdatas32.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “tdatas32.dll” end if if objFilesys.FileExists(InstallPath & “tdprsr32.dll”) then lf.WriteLine “File found : “ & InstallPath & “tdprsr32.dll” rc = objFilesys.DeleteFile(InstallPath & “tdprsr32.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “tdprsr32.dll” end if if objFilesys.FileExists(InstallPath & “terasso.dll”) then lf.WriteLine “File found : “ & InstallPath & “terasso.dll” rc = objFilesys.DeleteFile(InstallPath & “terasso.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “terasso.dll” end if ‘Deleting the ODBC Libraries from system32 if objFilesys.FileExists(winroot & “\system32\tdata32.dll”) then lf.WriteLine “File found : “ & winroot & “\system32\tdata32.dll” rc = objFilesys.DeleteFile(winroot & “\system32\tdata32.dll”,true) else lf.WriteLine “File not found : “ & winroot & “\system32\tdata32.dll” end if if objFilesys.FileExists(winroot & “\system32\tdatas32.dll”) then lf.WriteLine “File found : “ & winroot & “\system32\tdatas32.dll” rc = objFilesys.DeleteFile(winroot & “\system32\tdatas32.dll”,true) else lf.WriteLine “File not found : “ & winroot & “\system32\tdatas32.dll” end if if objFilesys.FileExists(winroot & “\system32\tdprsr32.dll”) then lf.WriteLine “File found : “ & winroot & “\system32\tdprsr32.dll” rc = objFilesys.DeleteFile(winroot & “\system32\tdprsr32.dll”,true) else lf.WriteLine “File not found : “ & winroot & “\system32\tdprsr32.dll” end if if objFilesys.FileExists(winroot & “\system32\terasso.dll”) then lf.WriteLine “File found : “ & winroot & “\system32\terasso.dll” rc = objFilesys.DeleteFile(winroot & “\system32\terasso.dll”,true) else lf.WriteLine “File not found : “ & winroot & “\system32\terasso.dll” end if ‘Remove left over Start Menu entries if objFilesys.FolderExists(allusers_dir & “\Start Menu\Programs\ODBC Driver for Teradata”) then lf.WriteLine “Folder found : “ & allusers_dir & “\Start Menu\Programs\ODBC Driver for Teradata” rc = objFilesys.DeleteFolder(allusers_dir & “\Start Menu\Programs\ODBC Driver for Teradata”,true) else lf.WriteLine “Folder not found : “ & allusers_dir & “\Start Menu\Programs\ODBC Driver for Teradata” end if case TTUProducts(4) ‘PIOM ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “libpm.dll”) then lf.WriteLine “File found : “ & InstallPath & “libpm.dll” 154 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script rc = objFilesys.DeleteFile(InstallPath & “libpm.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “libpm.dll” end if if objFilesys.FileExists(InstallPath & “pmddamt.h”) then lf.WriteLine “File found : “ & InstallPath & “pmddamt.h” rc = objFilesys.DeleteFile(InstallPath & “pmddamt.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “pmddamt.h” end if if objFilesys.FileExists(InstallPath & “pmdcomt.h”) then lf.WriteLine “File found : “ & InstallPath & “pmdcomt.h” rc = objFilesys.DeleteFile(InstallPath & “pmdcomt.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “pmdcomt.h” end if case TTUProducts(5) ‘BTEQ ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “bin\bteq.exe”) then lf.WriteLine “File found : “ & InstallPath & “bin\bteq.exe” rc = objFilesys.DeleteFile(InstallPath & “bin\bteq.exe”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\bteq.exe” end if if objFilesys.FileExists(InstallPath & “bin\bteqwin.exe”) then lf.WriteLine “File found : “ & InstallPath & “bin\bteqwin.exe” rc = objFilesys.DeleteFile(InstallPath & “bin\bteqwin.exe”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\bteqwin.exe” end if if objFilesys.FileExists(InstallPath & “bin\mgrcli.dll”) then lf.WriteLine “File found : “ & InstallPath & “bin\mgrcli.dll” rc = objFilesys.DeleteFile(InstallPath & “bin\mgrcli.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\mgrcli.dll” end if if objFilesys.FileExists(InstallPath & “bin\ncrtmgr.dll”) then lf.WriteLine “File found : “ & InstallPath & “bin\ncrtmgr.dll” rc = objFilesys.DeleteFile(InstallPath & “bin\ncrtmgr.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\ncrtmgr.dll” end if if objFilesys.FileExists(InstallPath & “bin\printman.dll”) then lf.WriteLine “File found : “ & InstallPath & “bin\printman.dll” rc = objFilesys.DeleteFile(InstallPath & “bin\printman.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\printman.dll” end if if objFilesys.FileExists(InstallPath & “bin\tdis.dll”) then lf.WriteLine “File found : “ & InstallPath & “bin\tdis.dll” rc = objFilesys.DeleteFile(InstallPath & “bin\tdis.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\tdis.dll” end if if objFilesys.FileExists(InstallPath & “bin\tm_dialogs.dll”) then lf.WriteLine “File found : “ & InstallPath & “bin\tm_dialogs.dll” rc = objFilesys.DeleteFile(InstallPath & “bin\tm_dialogs.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\tm_dialogs.dll” end if if objFilesys.FileExists(InstallPath & “bin\tm_stat.dll”) then Teradata Tools and Utilities for Microsoft Windows Installation Guide 155 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script lf.WriteLine “File found : “ & InstallPath & “bin\tm_stat.dll” rc = objFilesys.DeleteFile(InstallPath & “bin\tm_stat.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\tm_stat.dll” end if if objFilesys.FileExists(InstallPath & “bin\bteqwin_enu.cnt”) then lf.WriteLine “File found : “ & InstallPath & “bin\bteqwin_enu.cnt” rc = objFilesys.DeleteFile(InstallPath & “bin\bteqwin_enu.cnt”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\bteqwin_enu.cnt” end if if objFilesys.FileExists(InstallPath & “bin\BTEQWIN_ENU.HLP”) then lf.WriteLine “File found : “ & InstallPath & “bin\BTEQWIN_ENU.HLP” rc = objFilesys.DeleteFile(InstallPath & “bin\BTEQWIN_ENU.HLP”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\BTEQWIN_ENU.HLP” end if if objFilesys.FileExists(InstallPath & “bin\teqtalk.ico”) then lf.WriteLine “File found : “ & InstallPath & “bin\teqtalk.ico” rc = objFilesys.DeleteFile(InstallPath & “bin\teqtalk.ico”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\teqtalk.ico” end if if objFilesys.FileExists(InstallPath & “btnfy\btnfyext.c”) then lf.WriteLine “File found : “ & InstallPath & “btnfy\btnfyext.c” rc = objFilesys.DeleteFile(InstallPath & “btnfy\btnfyext.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “btnfy\btnfyext.c” end if if objFilesys.FileExists(InstallPath & “btnfy\btnfyext.def”) then lf.WriteLine “File found : “ & InstallPath & “btnfy\btnfyext.def” rc = objFilesys.DeleteFile(InstallPath & “btnfy\btnfyext.def”,true) else lf.WriteLine “File not found : “ & InstallPath & “btnfy\btnfyext.def” end if if objFilesys.FileExists(InstallPath & “btnfy\btnfyext.h”) then lf.WriteLine “File found : “ & InstallPath & “btnfy\btnfyext.h” rc = objFilesys.DeleteFile(InstallPath & “btnfy\btnfyext.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “btnfy\btnfyext.h” end if if objFilesys.FileExists(InstallPath & “btnfy\btnfyext.mak”) then lf.WriteLine “File found : “ & InstallPath & “btnfy\btnfyext.mak” rc = objFilesys.DeleteFile(InstallPath & “btnfy\btnfyext.mak”,true) else lf.WriteLine “File not found : “ & InstallPath & “btnfy\btnfyext.mak” end if if objFilesys.FileExists(winroot & “\system32\caputl.dll”) then lf.WriteLine “File found : “ & winroot & “\system32\caputl.dll” rc = objFilesys.DeleteFile(winroot & “\system32\caputl.dll”,true) else lf.WriteLine “File not found : “ & winroot & “\system32\caputl.dll” end if ‘Remove left over Start Menu entries if objFilesys.FileExists(allusers_dir & “\Start Menu\Programs\Teradata Client\Teradata BTEQ”) then lf.WriteLine “File found : “ & allusers_dir & “\Start Menu\Programs\Teradata Client\Teradata BTEQ” rc = objFilesys.DeleteFile(allusers_dir & “\Start Menu\Programs\Teradata Client\Teradata BTEQ”,true) else lf.WriteLine “File not found : “ & allusers_dir & “\Start Menu\Programs\Teradata Client\Teradata BTEQ” end if 156 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script if objFilesys.FileExists(allusers_dir & “\Start Menu\Programs\Teradata Client\Teradata BTEQWin”) then lf.WriteLine “File found : “ & allusers_dir & “\Start Menu\Programs\Teradata Client\Teradata BTEQWin” rc = objFilesys.DeleteFile(allusers_dir & “\Start Menu\Programs\Teradata Client\Teradata BTEQWin”,true) else lf.WriteLine “File not found : “ & allusers_dir & “\Start Menu\Programs\Teradata Client\Teradata BTEQWin” end if case TTUProducts(6) ‘FASTLD ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “\bin\fastload.exe”) then lf.WriteLine “File found : “ & InstallPath & “\bin\fastload.exe” rc = objFilesys.DeleteFile(InstallPath & “\bin\fastload.exe”,true) else lf.WriteLine “File not found : “ & InstallPath & “\bin\fastload.exe” end if if objFilesys.FileExists(InstallPath & “\fastload\blkexit.c”) then lf.WriteLine “File found : “ & InstallPath & “\fastload\blkexit.c” rc = objFilesys.DeleteFile(InstallPath & “\fastload\blkexit.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “\fastload\blkexit.c” end if if objFilesys.FileExists(InstallPath & “\fastload\blkexit.mak”) then lf.WriteLine “File found : “ & InstallPath & “\fastload\blkexit.mak” rc = objFilesys.DeleteFile(InstallPath & “\fastload\blkexit.mak”,true) else lf.WriteLine “File not found : “ & InstallPath & “\fastload\blkexit.mak” end if if objFilesys.FileExists(InstallPath & “\fastload\blkexitr.c”) then lf.WriteLine “File found : “ & InstallPath & “\fastload\blkexitr.c” rc = objFilesys.DeleteFile(InstallPath & “\fastload\blkexitr.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “\fastload\blkexitr.c” end if if objFilesys.FileExists(InstallPath & “\fastload\flnfyext.c”) then lf.WriteLine “File found : “ & InstallPath & “\fastload\flnfyext.c” rc = objFilesys.DeleteFile(InstallPath & “\fastload\flnfyext.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “\fastload\flnfyext.c” end if case TTUProducts(7) ‘MLOAD ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “bin\mload.exe”) then lf.WriteLine “File found : “ & InstallPath & “bin\mload.exe” rc = objFilesys.DeleteFile(InstallPath & “bin\mload.exe”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\mload.exe” end if if objFilesys.FileExists(InstallPath & “mload\mlimod.c”) then lf.WriteLine “File found : “ & InstallPath & “mload\mlimod.c” rc = objFilesys.DeleteFile(InstallPath & “mload\mlimod.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “mload\mlimod.c” end if if objFilesys.FileExists(InstallPath & “mload\mlnotf.c”) then lf.WriteLine “File found : “ & InstallPath & “mload\mlnotf.c” rc = objFilesys.DeleteFile(InstallPath & “mload\mlnotf.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “mload\mlnotf.c” end if case TTUProducts(8) ‘FASTEXP ‘Check if files exist on the machine Teradata Tools and Utilities for Microsoft Windows Installation Guide 157 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script if objFilesys.FileExists(InstallPath & “bin\fexp.exe”) then lf.WriteLine “File found : “ & InstallPath & “bin\fexp.exe” rc = objFilesys.DeleteFile(InstallPath & “bin\fexp.exe”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\fexp.exe” end if if objFilesys.FileExists(InstallPath & “fexp\feimod.c”) then lf.WriteLine “File found : “ & InstallPath & “fexp\feimod.c” rc = objFilesys.DeleteFile(InstallPath & “fexp\feimod.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “fexp\feimod.c” end if if objFilesys.FileExists(InstallPath & “fexp\fenotf.c”) then lf.WriteLine “File found : “ & InstallPath & “fexp\fenotf.c” rc = objFilesys.DeleteFile(InstallPath & “fexp\fenotf.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “fexp\fenotf.c” end if if objFilesys.FileExists(InstallPath & “fexp\feomod.c”) then lf.WriteLine “File found : “ & InstallPath & “fexp\feomod.c” rc = objFilesys.DeleteFile(InstallPath & “fexp\feomod.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “fexp\feomod.c” end if case TTUProducts(9) ‘TPUMP ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “bin\tpump.exe”) then lf.WriteLine “File found : “ & InstallPath & “bin\tpump.exe” rc = objFilesys.DeleteFile(InstallPath & “bin\tpump.exe”,true) else lf.WriteLine “File not found : “ & InstallPath & “bin\tpump.exe” end if if objFilesys.FileExists(InstallPath & “tpump\tdatpump.cfg”) then lf.WriteLine “File found : “ & InstallPath & “tpump\tdatpump.cfg” rc = objFilesys.DeleteFile(InstallPath & “tpump\tdatpump.cfg”,true) else lf.WriteLine “File not found : “ & InstallPath & “tpump\tdatpump.cfg” end if if objFilesys.FileExists(InstallPath & “tpump\tldnfyxt.c”) then lf.WriteLine “File found : “ & InstallPath & “tpump\tldnfyxt.c” rc = objFilesys.DeleteFile(InstallPath & “tpump\tldnfyxt.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “tpump\tldnfyxt.c” end if if objFilesys.FileExists(InstallPath & “tpump\tpumpar.csql”) then lf.WriteLine “File found : “ & InstallPath & “tpump\tpumpar.csql” rc = objFilesys.DeleteFile(InstallPath & “tpump\tpumpar.csql”,true) else lf.WriteLine “File not found : “ & InstallPath & “tpump\tpumpar.csql” end if if objFilesys.FileExists(InstallPath & “tpump\tpumpimd.c”) then lf.WriteLine “File found : “ & InstallPath & “tpump\tpumpimd.c” rc = objFilesys.DeleteFile(InstallPath & “tpump\tpumpimd.c”,true) else lf.WriteLine “File not found : “ & InstallPath & “tpump\tpumpimd.c” end if case TTUProducts(10) ‘TDOLEDB ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “msvcp71.dll”) then lf.WriteLine “File found : “ & InstallPath & “msvcp71.dll” rc = objFilesys.DeleteFile(InstallPath & “msvcp71.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “msvcp71.dll” 158 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script end if if objFilesys.FileExists(InstallPath & “msvcr71.dll”) then lf.WriteLine “File found : “ & InstallPath & “msvcr71.dll” rc = objFilesys.DeleteFile(InstallPath & “msvcr71.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “msvcr71.dll” end if if objFilesys.FileExists(InstallPath & “TD_OC.dll”) then lf.WriteLine “File found : “ & InstallPath & “TD_OC.dll” rc = objFilesys.DeleteFile(InstallPath & “TD_OC.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “TD_OC.dll” end if if objFilesys.FileExists(InstallPath & “TD_OCPR.dll”) then lf.WriteLine “File found : “ & InstallPath & “TD_OCPR.dll” rc = objFilesys.DeleteFile(InstallPath & “TD_OCPR.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “TD_OCPR.dll” end if if objFilesys.FileExists(InstallPath & “TD_OCPR.dll”) then lf.WriteLine “File found : “ & InstallPath & “TD_OCPR.dll” rc = objFilesys.DeleteFile(InstallPath & “TD_OCPR.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “TD_OCPR.dll” end if if objFilesys.FileExists(InstallPath & “TD_RT.dll”) then lf.WriteLine “File found : “ & InstallPath & “TD_RT.dll” rc = objFilesys.DeleteFile(InstallPath & “TD_RT.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “TD_RT.dll” end if if objFilesys.FileExists(InstallPath & “TD_TL.dll”) then lf.WriteLine “File found : “ & InstallPath & “TD_TL.dll” rc = objFilesys.DeleteFile(InstallPath & “TD_TL.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “TD_TL.dll” end if if objFilesys.FileExists(InstallPath & “TDOLEDB.dll”) then lf.WriteLine “File found : “ & InstallPath & “TDOLEDB.dll” rc = objFilesys.DeleteFile(InstallPath & “TDOLEDB.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “TDOLEDB.dll” end if if objFilesys.FileExists(InstallPath & “tdoledb.h”) then lf.WriteLine “File found : “ & InstallPath & “tdoledb.h” rc = objFilesys.DeleteFile(InstallPath & “tdoledb.h”,true) else lf.WriteLine “File not found : “ & InstallPath & “tdoledb.h” end if if objFilesys.FileExists(InstallPath & “TDOLEDB_TEST.udl”) then lf.WriteLine “File found : “ & InstallPath & “TDOLEDB_TEST.udl” rc = objFilesys.DeleteFile(InstallPath & “TDOLEDB_TEST.udl”,true) else lf.WriteLine “File not found : “ & InstallPath & “TDOLEDB_TEST.udl” end if if objFilesys.FileExists(InstallPath & “TDOLEDBR.dll”) then lf.WriteLine “File found : “ & InstallPath & “TDOLEDBR.dll” rc = objFilesys.DeleteFile(InstallPath & “TDOLEDBR.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “TDOLEDBR.dll” Teradata Tools and Utilities for Microsoft Windows Installation Guide 159 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script end if case TTUProducts(11) ‘SQLPP ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “LABSBTEQ”) then lf.WriteLine “File found : “ & InstallPath & “LABSBTEQ” rc = objFilesys.DeleteFile(InstallPath & “LABSBTEQ”,true) else lf.WriteLine “File not found : “ & InstallPath & “LABSBTEQ” end if if objFilesys.FileExists(InstallPath & “PPCLB1”) then lf.WriteLine “File found : “ & InstallPath & “PPCLB1” rc = objFilesys.DeleteFile(InstallPath & “PPCLB1”,true) else lf.WriteLine “File not found : “ & InstallPath & “PPCLB1” end if if objFilesys.FileExists(InstallPath & “PPCLB2”) then lf.WriteLine “File found : “ & InstallPath & “PPCLB2” rc = objFilesys.DeleteFile(InstallPath & “PPCLB2”,true) else lf.WriteLine “File not found : “ & InstallPath & “PPCLB2” end if if objFilesys.FileExists(InstallPath & “PPCLB3”) then lf.WriteLine “File found : “ & InstallPath & “PPCLB3” rc = objFilesys.DeleteFile(InstallPath & “PPCLB3”,true) else lf.WriteLine “File not found : “ & InstallPath & “PPCLB3” end if if objFilesys.FileExists(InstallPath & “PPCLB4”) then lf.WriteLine “File found : “ & InstallPath & “PPCLB4” rc = objFilesys.DeleteFile(InstallPath & “PPCLB4”,true) else lf.WriteLine “File not found : “ & InstallPath & “PPCLB4” end if if objFilesys.FileExists(InstallPath & “PPCLB5”) then lf.WriteLine “File found : “ & InstallPath & “PPCLB5” rc = objFilesys.DeleteFile(InstallPath & “PPCLB5”,true) else lf.WriteLine “File not found : “ & InstallPath & “PPCLB5” end if if objFilesys.FileExists(InstallPath & “PPCLB6”) then lf.WriteLine “File found : “ & InstallPath & “PPCLB6” rc = objFilesys.DeleteFile(InstallPath & “PPCLB6”,true) else lf.WriteLine “File not found : “ & InstallPath & “PPCLB6” end if if objFilesys.FileExists(InstallPath & “PPCLB7”) then lf.WriteLine “File found : “ & InstallPath & “PPCLB7” rc = objFilesys.DeleteFile(InstallPath & “PPCLB7”,true) else lf.WriteLine “File not found : “ & InstallPath & “PPCLB7” end if if objFilesys.FileExists(InstallPath & “PPCLB8”) then lf.WriteLine “File found : “ & InstallPath & “PPCLB8” rc = objFilesys.DeleteFile(InstallPath & “PPCLB8”,true) else lf.WriteLine “File not found : “ & InstallPath & “PPCLB8” end if if objFilesys.FileExists(InstallPath & “PPCLB9”) then lf.WriteLine “File found : “ & InstallPath & “PPCLB9” rc = objFilesys.DeleteFile(InstallPath & “PPCLB9”,true) else 160 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script lf.WriteLine “File not found : “ & InstallPath & “PPCLB9” end if if objFilesys.FileExists(InstallPath & “ppruntim.dll”) then lf.WriteLine “File found : “ & InstallPath & “ppruntim.dll” rc = objFilesys.DeleteFile(InstallPath & “ppruntim.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “ppruntim.dll” end if if objFilesys.FileExists(InstallPath & “ppruntim.lib”) then lf.WriteLine “File found : “ & InstallPath & “ppruntim.lib” rc = objFilesys.DeleteFile(InstallPath & “ppruntim.lib”,true) else lf.WriteLine “File not found : “ & InstallPath & “ppruntim.lib” end if TempInstallPath=replace(InstallPath,”pp2”,”bin”) if objFilesys.FileExists(TempInstallPath & “ppcmain.exe”) then lf.WriteLine “File found : “ & TempInstallPath & “ppcmain.exe” rc = objFilesys.DeleteFile(TempInstallPath & “ppcmain.exe”,true) else lf.WriteLine “File not found : “ & TempInstallPath & “ppcmain.exe” end if case TTUProducts(12) ‘NPAXSMOD ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “np_AXSMOD.dll”) then lf.WriteLine “File found : “ & InstallPath & “np_AXSMOD.dll” rc = objFilesys.DeleteFile(InstallPath & “np_AXSMOD.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “np_AXSMOD.dll” end if if objFilesys.FileExists(InstallPath & “np_AXSMODenu.dll”) then lf.WriteLine “File found : “ & InstallPath & “np_AXSMODenu.dll” rc = objFilesys.DeleteFile(InstallPath & “np_AXSMODenu.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “np_AXSMODenu.dll” end if if objFilesys.FileExists(InstallPath & “np_AXSMODenuTWB.dll”) then lf.WriteLine “File found : “ & InstallPath & “np_AXSMODenuTWB.dll” rc = objFilesys.DeleteFile(InstallPath & “np_AXSMODenuTWB.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “np_AXSMODenuTWB.dll” end if if objFilesys.FileExists(InstallPath & “np_AXSMODTWB.dll”) then lf.WriteLine “File found : “ & InstallPath & “np_AXSMODTWB.dll” rc = objFilesys.DeleteFile(InstallPath & “np_AXSMODTWB.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “np_AXSMODTWB.dll” end if case TTUProducts(13) ‘MQAXSMOD ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “libmqs.dll”) then lf.WriteLine “File found : “ & InstallPath & “libmqs.dll” rc = objFilesys.DeleteFile(InstallPath & “libmqs.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “libmqs.dll” end if if objFilesys.FileExists(InstallPath & “libmqsc.dll”) then lf.WriteLine “File found : “ & InstallPath & “libmqsc.dll” rc = objFilesys.DeleteFile(InstallPath & “libmqsc.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “libmqsc.dll” end if if objFilesys.FileExists(InstallPath & “libmqscTWB.dll”) then Teradata Tools and Utilities for Microsoft Windows Installation Guide 161 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script lf.WriteLine “File found : “ & InstallPath & “libmqscTWB.dll” rc = objFilesys.DeleteFile(InstallPath & “libmqscTWB.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “libmqscTWB.dll” end if if objFilesys.FileExists(InstallPath & “libmqsTWB.dll”) then lf.WriteLine “File found : “ & InstallPath & “libmqsTWB.dll” rc = objFilesys.DeleteFile(InstallPath & “libmqsTWB.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “libmqsTWB.dll” end if case TTUProducts(14) ‘OLEDBAXSMOD ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “msvcr71.dll”) then lf.WriteLine “File found : “ & InstallPath & “msvcr71.dll” rc = objFilesys.DeleteFile(InstallPath & “msvcr71.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “msvcr71.dll” end if if objFilesys.FileExists(InstallPath & “OLEDB_AXSMOD.dll”) then lf.WriteLine “File found : “ & InstallPath & “OLEDB_AXSMOD.dll” rc = objFilesys.DeleteFile(InstallPath & “OLEDB_AXSMOD.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “OLEDB_AXSMOD.dll” end if if objFilesys.FileExists(InstallPath & “OLEDB_AXSMODenu.cnt”) then lf.WriteLine “File found : “ & InstallPath & “OLEDB_AXSMODenu.cnt” rc = objFilesys.DeleteFile(InstallPath & “OLEDB_AXSMODenu.cnt”,true) else lf.WriteLine “File not found : “ & InstallPath & “OLEDB_AXSMODenu.cnt” end if if objFilesys.FileExists(InstallPath & “OLEDB_AXSMODenu.dll”) then lf.WriteLine “File found : “ & InstallPath & “OLEDB_AXSMODenu.dll” rc = objFilesys.DeleteFile(InstallPath & “OLEDB_AXSMODenu.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “OLEDB_AXSMODenu.dll” end if if objFilesys.FileExists(InstallPath & “OLEDB_AXSMODENU.HLP”) then lf.WriteLine “File found : “ & InstallPath & “OLEDB_AXSMODENU.HLP” rc = objFilesys.DeleteFile(InstallPath & “OLEDB_AXSMODENU.HLP”,true) else lf.WriteLine “File not found : “ & InstallPath & “OLEDB_AXSMODENU.HLP” end if if objFilesys.FileExists(InstallPath & “OLEDB_AXSMODjpn.cnt”) then lf.WriteLine “File found : “ & InstallPath & “OLEDB_AXSMODjpn.cnt” rc = objFilesys.DeleteFile(InstallPath & “OLEDB_AXSMODjpn.cnt”,true) else lf.WriteLine “File not found : “ & InstallPath & “OLEDB_AXSMODjpn.cnt” end if if objFilesys.FileExists(InstallPath & “OLEDB_AXSMODjpn.dll”) then lf.WriteLine “File found : “ & InstallPath & “OLEDB_AXSMODjpn.dll” rc = objFilesys.DeleteFile(InstallPath & “OLEDB_AXSMODjpn.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “OLEDB_AXSMODjpn.dll” end if if objFilesys.FileExists(InstallPath & “OLEDB_AXSMODJPN.HLP”) then lf.WriteLine “File found : “ & InstallPath & “OLEDB_AXSMODJPN.HLP” rc = objFilesys.DeleteFile(InstallPath & “OLEDB_AXSMODJPN.HLP”,true) else lf.WriteLine “File not found : “ & InstallPath & “OLEDB_AXSMODJPN.HLP” end if 162 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script if objFilesys.FileExists(InstallPath & “program.ico”) then lf.WriteLine “File found : “ & InstallPath & “program.ico” rc = objFilesys.DeleteFile(InstallPath & “program.ico”,true) else lf.WriteLine “File not found : “ & InstallPath & “program.ico” end if if objFilesys.FileExists(InstallPath & “Uninst.dll”) then lf.WriteLine “File found : “ & InstallPath & “Uninst.dll” rc = objFilesys.DeleteFile(InstallPath & “Uninst.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “Uninst.dll” end if if objFilesys.FolderExists(InstallPath & “Teradata OLE DB Access Module Help”) then lf.WriteLine “Folder found : “ & InstallPath & “Teradata OLE DB Access Module Help” rc = objFilesys.DeleteFolder(InstallPath & “Teradata OLE DB Access Module Help”,true) else lf.WriteLine “Folder not found : “ & InstallPath & “Teradata OLE DB Access Module Help” end if TempInstallPath=”C:\Program Files\NCR\Teradata Client\Bin” if objFilesys.FileExists(TempInstallPath & “OleLoad.exe”) then lf.WriteLine “File found : “ & TempInstallPath & “OleLoad.exe” rc = objFilesys.DeleteFile(TempInstallPath & “OleLoad.exe”,true) else lf.WriteLine “File not found : “ & TempInstallPath & “OleLoad.exe” end if if objFilesys.FileExists(TempInstallPath & “OleLoadKeyFile.txt”) then lf.WriteLine “File found : “ & TempInstallPath & “OleLoadKeyFile.txt” rc = objFilesys.DeleteFile(TempInstallPath & “OleLoadKeyFile.txt”,true) else lf.WriteLine “File not found : “ & TempInstallPath & “OleLoadKeyFile.txt” end if case TTUProducts(15) ‘JMSAXSMOD ‘Check if files exist on the machine if objFilesys.FileExists(InstallPath & “libjmsam.dll”) then lf.WriteLine “File found : “ & InstallPath & “libjmsam.dll” rc = objFilesys.DeleteFile(InstallPath & “libjmsam.dll”,true) else lf.WriteLine “File not found : “ & InstallPath & “libjmsam.dll” end if if objFilesys.FileExists(InstallPath & “readme”) then lf.WriteLine “File found : “ & InstallPath & “readme” rc = objFilesys.DeleteFile(InstallPath & “readme”,true) else lf.WriteLine “File not found : “ & InstallPath & “readme” end if if objFilesys.FileExists(InstallPath & “Receiver.class”) then lf.WriteLine “File found : “ & InstallPath & “Receiver.class” rc = objFilesys.DeleteFile(InstallPath & “Receiver.class”,true) else lf.WriteLine “File not found : “ & InstallPath & “Receiver.class” end if end select End Function ‘============================================================================================================ ========================================= ‘Verifies that all the registry entries for a product are deleted. If any registry entry is found, it is deleted forcibly. Function VerifyRegistryEntries(ByVal ProductName, ByVal ProductCode, ByVal ProductVersion) Dim Check_Name ‘Check for registry entries in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall Teradata Tools and Utilities for Microsoft Windows Installation Guide 163 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\Microsoft\Windows\CurrentVersion\Uninstall\” & ProductCode Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion \Uninstall\” & ProductCode & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\” & ProductCode & “ entry found and deleted...” else lf.WriteLine “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\” & ProductCode & “ entry not found...” end if ‘Check for registry entries in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall \InstallShield_{Product_Code} Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\Microsoft\Windows\CurrentVersion\Uninstall\Installshield_” & ProductCode Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion \Uninstall\Installshield_” & ProductCode & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Installsheild_” & ProductCode & “ entry found and deleted...” else lf.WriteLine “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Installsheild_” & ProductCode & “ entry not found...” end if ‘Check for registry entries in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield Uninstall Information Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield Uninstall Information\” & ProductCode Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion \Uninstall\InstallShield Uninstall Information\” & ProductCode & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield Uninstall Information\” & ProductCode & “ entry found and deleted...” else lf.WriteLine “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield Uninstall Information\” & ProductCode & “ entry not found...” end if ‘Check for registry entries in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\Microsoft\Windows\CurrentVersion\Uninstall\” & ProductName Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion \Uninstall\” & ProductName & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\” & ProductName & “ entry found and deleted...” else lf.WriteLine “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\” & ProductName & “ entry not found...” end if if (ProductName = TTUProducts(0)) then Check_Name = Disp_Name else Check_Name = ProductName end if ‘TERAGSS ‘Retrieve information about the products installed on the machine by inspecting the HKLM\SOFTWARE\Classes \Installer\Products keys in the registry 164 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script ‘Searching the HKLM\Software\Classes\Installer\Products Keys is only possible in 64-bit mode, so switching the context to 64-bit mode temporarily. if (Wow6432Node = True) then objCtx.Add “__ProviderArchitecture”, 64 objCtx.Add “__RequiredArchitecture”, TRUE Set objLocator = CreateObject(“Wbemscripting.SWbemLocator”) Set objServices = objLocator.ConnectServer(““,”root\default”,””,””,,,,objCtx) Set objStdRegProv = objServices.Get(“StdRegProv”) end if Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\Classes\Installer\Products” Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) For Each strSubKey In Outparams.snames Set Inparams = objStdRegProv.Methods_(“GetStringValue”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\Classes\Installer\Products\” & strSubKey Inparams.Svaluename = “ProductName” set Outparams = objStdRegProv.ExecMethod_(“GetStringValue”, Inparams,,objCtx) if (““ & Outparams.sValue) = ““ then ‘wscript.echo strSubKey Else if (instr(1, Outparams.SValue,Check_Name) > 0) then lf.WriteLine Check_Name & “ found in the entry : “ & strSubKey Set Inparams = objStdRegProv.Methods_(“GetDWORDValue”).Inparameters Inparams.Hdefkey = HKLM Inparams.sSubkeyname = “Software\Classes\Installer\Products\” & strSubKey Inparams.sValuename = “Version” set Outparams = objStdRegProv.ExecMethod_(“GetDWORDValue”, Inparams,,objCtx) if (Hex_Version = Outparams.uValue) then lf.WriteLine “Matching Product Version found in entry and deleted the entry : “ & strSubKey rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\Software\Classes\Installer \Products\” & strSubKey & chr(34) & “ /f”,0,true) else lf.WriteLine “Matching Product Version not found in the entry : “ & strSubKey end if else lf.WriteLine Check_Name & “ not found in the entry : “ & strSubKey end if End iF Next ‘Switch back the context to 32-bit mode. Since we want to search the 32-bit products. if (Wow6432Node = True) then objCtx.Add “__ProviderArchitecture”, 32 objCtx.Add “__RequiredArchitecture”, TRUE Set objLocator = CreateObject(“Wbemscripting.SWbemLocator”) Set objServices = objLocator.ConnectServer(““,”root\default”,””,””,,,,objCtx) Set objStdRegProv = objServices.Get(“StdRegProv”) end if Select case ProductName case TTUProducts(0) ‘TERAGSS ‘For TeraGSS the Product entry under HKLM\Software\NCR is removed only if the version uninstalled is the last/active version ‘of TeraGSS. if (ProductVersion = saved_product_ver) then ‘Check for registry entries in HKLM\Software\NCR Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\NCR\” & ProductName Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\NCR\” & ProductName & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\NCR\” & ProductName & “ entry found and deleted...” Teradata Tools and Utilities for Microsoft Windows Installation Guide 165 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script else lf.WriteLine “HKLM\SOFTWARE\NCR\” & ProductName & “ entry not found...” end if end if case TTUProducts(2) ‘CLIv2 ‘Check for registry entries in HKLM\Software\NCR Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\NCR\” & ProductName Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\NCR\” & ProductName & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\NCR\” & ProductName & “ entry found and deleted...” else lf.WriteLine “HKLM\SOFTWARE\NCR\” & ProductName & “ entry not found...” end if ‘Check for registry entries in HKLM\Software\NCR\Teradata CLI2. Earlier versions of CLIv2 created two entries. Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\NCR\Teradata CLI2” Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\NCR\Teradata CLI2” & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\NCR\Teradata CLI2” & “ entry found and deleted...” else lf.WriteLine “HKLM\SOFTWARE\NCR\Teradata CLI2” & “ entry not found...” end if case TTUProducts(16) ‘SQLA ‘Check for registry entries in HKLM\Software\NCR Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\NCR\” & ProductName Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\NCR\” & ProductName & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\NCR\” & ProductName & “ entry found and deleted...” else lf.WriteLine “HKLM\SOFTWARE\NCR\” & ProductName & “ entry not found...” end if ‘Check for registry entries in HKLM\Software\NCR\SQLAssistant. Older versions have this entry. Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\NCR\SQLAssistant” Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\NCR\SQLAssistant” & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\NCR\SQLAssistant” & “ entry found and deleted...” else lf.WriteLine “HKLM\SOFTWARE\NCR\SQLAssistant” & “ entry not found...” end if case else ‘For all other products ‘Check for registry entries in HKLM\Software\NCR Set Inparams = objStdRegProv.Methods_(“EnumKey”).Inparameters Inparams.Hdefkey = HKLM Inparams.Ssubkeyname = “Software\NCR\” & ProductName Set Outparams = objStdRegProv.ExecMethod_(“EnumKey”, Inparams,,objCtx) if (Outparams.ReturnValue = 0) then rc = objWshShell.Run(“cmd /C reg delete “ & chr(34) & “HKLM\SOFTWARE\NCR\” & ProductName & chr(34) & “ /f”,0,true) lf.WriteLine “HKLM\SOFTWARE\NCR\” & ProductName & “ entry found and deleted...” else lf.WriteLine “HKLM\SOFTWARE\NCR\” & ProductName & “ entry not found...” end if End Select End Function 166 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script ‘============================================================================================================ ========================================= ‘Compare the Major release of the installed product with ‘the Major release of the product being installed Function PATHCleanup(Byval InstallPath) Dim strlen Dim TotalStr Dim FirstPart, LastPart Dim pos, pos1, pos2 Dim objEnv Dim fldr Dim fls Dim Path_modified lf.WriteLine “Inside PATHCleanup : Searching for “ & InstallPath Path_Modified=false Set objEnv = objWshShell.Environment(“SYSTEM”) TotalStr=objEnv(“PATH”) pos=1 pos1=1 pos2=1 pos = instr(1,TotalStr,InstallPath) if (pos > 0) then strlen = len(TotalStr) do while (strlen > 0 ) pos2=instr(pos1,TotalStr,”;”) if (pos2 > 0) then if (InstallPath = Left(TotalStr,pos2-1)) then ‘Path Matches PATH entry lf.WriteLine “PATH Entry Found...” if (objFile.FolderExists(InstallPath) = True) then ‘ Check if the folder exists set fldr = objFile.GetFolder(InstallPath) set fls = fldr.Files if (fls.count = 0) then ‘If the folder is empty remove the PATH entry lf.WriteLine “Removing “ & InstallPath & “ entry from PATH.” Path_Modified=True else lf.WriteLine “Not removing “ & InstallPath & “ entry from PATH, because the folder is not empty.” FirstPart = FirstPart & Left(TotalStr,pos2) end if else lf.WriteLine “Folder doesn’t exist : Removing “ & InstallPath & “ entry from PATH..” Path_Modified=True end if else FirstPart = FirstPart & Left(TotalStr,pos2) end if TotalStr=Right(TotalStr,(strlen-pos2)) strlen = len (TotalStr) else ‘When no semicolon in the string, usually the last entry in PATH if (InstallPath = TotalStr) then lf.WriteLine “PATH Entry Found...” if (objFile.FolderExists(InstallPath) = True) then ‘ Check if the folder exists set fldr = objFile.GetFolder(InstallPath) set fls = fldr.Files if (fls.count = 0) then ‘If the folder is empty remove the PATH entry lf.WriteLine “Removing “ & InstallPath & “ entry from PATH.” Path_Modified=True else lf.WriteLine “Not removing “ & InstallPath & “ entry from PATH, because the folder is not empty.” FirstPart = FirstPart & Left(TotalStr,pos2) end if Teradata Tools and Utilities for Microsoft Windows Installation Guide 167 Chapter 8 Deploy Teradata Tools and Utilities with SMS Sample Uninstall Script else lf.WriteLine “Folder doesn’t exist : Removing “ & InstallPath & “ entry from PATH..” Path_Modified=True end if else FirstPart = FirstPart & TotalStr end if strlen=0 end if loop else lf.WriteLine “PATH entry not found...” end if if (Path_Modified = True) then objEnv(“PATH”)=FirstPart lf.WriteLine “PATH modified...” else lf.WriteLine “PATH not modified...” end if End Function ‘============================================================================================================ ========================================= 168 Teradata Tools and Utilities for Microsoft Windows Installation Guide 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. Understanding the TAR File A tar file is an archive of files that you typically create on a UNIX or Linux system. The folder and file structure in the archive mirrors the structure of the source files. You can use the tar_teradata_client_packages script on the Teradata Tools and Utilities installation media to create a compressed archive of Teradata Tools and Utilities client packages for a specific platform or operating system from the installation media. You can also compress the tar file. A compressed tar file is like a zip or 7z or rar or cab file on a Windows system. On a 32-bit Windows system, you can create a tar file for bundling individual UNIX or Linux packages and their dependencies or the entire set of Teradata Tools and Utilities packages for UNIX or Linux. The tar archive can be copied to a network machine and deployed to UNIX or Linux clients through FTP. Use this option if for example the target UNIX or Linux clients have a CD drive but not a DVD drive. You can build the tar file to contain all of the packages for a specified platform, or all the files for a specified package. It also includes all of the required dependencies for the selected packages. TAR Script Compatibility with Platform Operating Systems The tar_teradata_client_packages script provided on the installation media runs on 32-bit Windows using the DOS command prompt. Verifying TAR Script Dependencies are Installed The tar executable must be located in the PATH on the system running the script. A standard Windows installation does not include tar.exe or gzip.exe. These utilities must be installed manually. 1 Ensure that the tar executable is located in the PATH on the system by running the script. If the tar.exe executable is not found on the system, the script aborts. The script displays a download location for the GNU version of tar.exe at ftp://ftp.gnu.org/pub/ pub/gnu/tar/tar-1.12.msdos.exe. Teradata Tools and Utilities for Microsoft Windows Installation Guide 169 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR This version of tar.exe works on 32-bit Windows only. If the gzip.exe compression utility is in the PATH, the script uses the utility to compress the tar file. TAR Script Commands and Their Functions Launch the script with tar_teradata_client_packages.bat. Command Description tar_teradata_client_packages Displays the available commands or tar_teradata_client_packages help tar_teradata_client_packages list Displays the available platforms and packages on the installation media tar_teradata_client_packages list platform Lists the products available for a specific platform on the installation media • Run the script with platform as the first parameter to create a tar file in the default target path. The resulting archive contains all Teradata client packages on the media for that platform. The value of the platform parameter can be one of the following: • aix • i386 • ia64 • opteron • pa-risc • s390x • sparc The path for the output can be changed. The output filename is in the following format: teradata-client-platform-media-name.tar. The scripts appends .gz if the archive is compressed with gzip.exe. • tar_teradata_client_packages platform package Run the script with platform as the second parameter after the list parameter to list the packages available for the specified platform. Runs the script creating a tar file for a specific platform, including all packages You can add the name of a package after the platform parameter to list specific packages. For example, to list the bteq packages for the aix platform, type: tar_teradata_client_packages aix bteq If any packages other than the four dependent packages are specified, the dependent packages are all included: • cliv2 • piom • tdicu • teragss 170 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR Command Description If you add package names after the platform parameter, the script always includes the dependent packages if they are available on the media. If you specify individual packages, all package dependencies are included in the archive. tar_teradata_client_packages platform [package1] [package2]... Runs the script creating a tar file for a specific platform and specific packages You can add the name of a package after the platform parameter to list specific packages. For example, to list the bteq packages for the aix platform, type: tar_teradata_client_packages aix bteq If any packages other than the four dependent packages are specified, the dependent packages are all included: • cliv2 • piom • tdicu • teragss If you add package names after the platform parameter, the script always includes the dependent packages if they are available on the media. If you specify individual packages, all package dependencies are included in the archive. Note: The package-version identifier is not required. For example, the package names bteq and bteq1400 are equivalent when running the script. TAR Script Usage Considerations Subject Description Default Directory The tar_teradata_client_packages script prompts for a directory to create the tar file. To use the default user directory, press Enter. By convention, the default home directory is %USERPROFILE%. The script attempts to create the directory if it does not exist. If the location is read-only or unable to be written, the script ends. Multiple and Dependent Packages If a single package or multiple packages are selected, all of the dependent products are included, even if the product selected is one of the single dependent packages. Dependent packages typically have mutual dependencies. For example, dependent package cliv2 depends on the dependent packages tdicu and TeraGSS. Getting Help on the Script To view command usage and optional command parameters, run tar_teradata_client_packages by itself or with the optional help parameter: • tar_teradata_client_packages • tar_teradata_client_packages help A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v.14.00.00.00 * ************************************************************************ Tar Teradata Client Packages Teradata Tools and Utilities for Microsoft Windows Installation Guide 171 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR Subject Description Usage: tar_teradata_client_packages list tar_teradata_client_packages list {platform} tar_teradata_client_packages {platform} [{package1} {package2} ...] Parameters: commands help list : help, list, {platform} [{package1} {package2} ...] : Display this help message. : List the available platforms and packages from the media. list {platform} : List the packages available for the specified platform. {platform} : Available platforms: aix, ia64, pa-risc, i386, s390x, opteron, sparc Create the tar file for the supplied platform and include all packages or individual packages. {package} : Specify the packages available on this media for the specific platform. The parameter "all" (or blank) will include all available packages. To specify individual packages, list the packages separated by a space. Example: ttcp.bat linux bteq fastld The dependencies will automatically be included and do not need to be listed individually. The following packages are included: ---TeraGSS cliv2 tdicu piom Listing the Available Packages and Platforms All of the platforms and packages contained on the installation media can be listed by running the tar_teradata_client_packages script with the list parameter, for example: tar_teradata_client_packages list To list all packages for a specific platform available on the installation media, run tar_teradata_client_packages list platform where platform is the value of one of the platforms, for example: tar_teradata_client_packages list hp-ux A screen similar to the following appears as a result. It lists all the platforms and packages on the current installation media: ************************************************************************ * Tar Teradata Client Packages v.14.00.00.00 * ************************************************************************ Load /Unload - Volume 2 The available platforms are: HP-UX Linux 172 The available packages are: --- HP-UX Products bteq fastexp mload npaxsmod cliv2 fastld mqaxsmod piom tdicu TeraGSS tpump --- Linux Products bteq fastexp mload cliv2 fastld mqaxsmod tdicu TeraGSS tpump npaxsmod piom Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR Downloading Windows Utility Software for TAR Deployment To create a compressed tar archive of Linux or UNIX packages for Teradata Tools and Utilities products on a 32-bit Windows platform from the installation media, the tar.exe and gzip.exe archiving and compression utilities must be installed. 1 Enter the following command to verify if tar.exe is installed: D:\tar_teradata_client_packages If tar.exe is not installed, a message similar to the following appears, directing you to a location where the tar.exe archiving utility is available for download: ************************************************************************ * Tar Teradata Client Packages v.14.00.00.00 * ************************************************************************ 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: http://www.gnu.org/software/tar/ 2 If tar.exe is not installed, download tar-1.12.msdos.exe from ftp:// ftp.gnu.org/pub/pub/gnu/tar/tar-1.12.msdos.exe. This version of tar.exe works on 32-bit Windows only. 3 Save the download to the C:\Windows directory and rename the file to tar.exe. 4 Enter the following command to verify if gzip.exe is installed: D:\tar_teradata_client_packages If gzip.exe is not installed, a message similar to the following appears during the creation of the tar file: Notice: The executable gzip.exe is not found. Download from www.gzip.org for MSDOS to automatically compress the output tar file to a gzip file. 5 If gzip.exe is not installed, download the MSDOS version of gzip.exe from gzip home page. The MSDOS version of gzip.exe works on 32-bit Windows only. 6 Save the download to the C:\Windows directory. Overview of TAR Script Examples The file tar_teradata_client_packages is available on all installation media. The examples list available packages and create tar files that include all packages or individual Teradata Tools and Utilities for Microsoft Windows Installation Guide 173 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR packages and their dependent packages. Examples also show the commands for creating tar package archives for UNIX and Linux platforms on Windows. Archiving Sun Solaris SPARC Packages This example archives packages and dependencies that are required for the deployment of Teradata Tools and Utilities products to Sun Solaris SPARC clients. The packages and dependencies are copied from the installation media and archived as a tar file. The archive can be copied to Sun Solaris SPARC machines and expanded. The example assumes that you run the archiving script on a 32-bit Windows system on which tar.exe is installed but gzip.exe is not installed. The procedure involves the following steps: 1. Listing available products 2. Copying and archiving products 1 Run the script with the list parameter to display a list of the products available for each product and platform: D:\tar_teradata_client_packages list A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v.14.00.00.00 * ************************************************************************ Preprocessors - Volume 3 The available platforms are: AIX Solaris For Solaris Sparc use "sparc" for the platform parameter. For Solaris Opteron use "opteron" for the platform parameter. The available packages are: --- AIX Products cliv2 cobpp sqlpp tdicu TeraGSS --- Solaris Sparc Products cliv21400 sqlpp1400 tdicu1400 TeraGSS TeraGSS32 --- Solaris Opteron Products cliv21400 sqlpp1400 tdicu1400 TeraGSS_solaris-i386 TeraGSS_solaris-x8664 2 Enter the following commands to create an archive of the Sun Solaris SPARC packages and dependencies. a D:\tar_teradata_client_packages sparc 174 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v.14.00.00.00 * ************************************************************************ 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 accept the default path, copy the packages, and create the tar archive. A screen similar to the following appears: ---Archiving all packages for sparc. tar cvf "C:\Documents and Settings\<user>\teradata-client-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 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 www.gzip.org for MSDOS to automatically compress the output tar file to a gzip file. The file has been saved at : C:\Documents and Settings\<user>\teradata-client-sparc-preprocessors-volume-3.tar Archiving an HP-UX Package This example archives the bteq package and its dependencies that are required for the deployment of bteq to HP-UX clients. The package and dependencies are copied from the installation media, archived as a tar file, and compressed. The compressed archive can be copied to HP-UX machines and expanded. The example assumes that you run the archiving script on a 32-bit Windows system on which tar.exe and gzip.exe are installed. Teradata Tools and Utilities for Microsoft Windows Installation Guide 175 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR 1 Run the script with hp-ux as the value of the platform parameter and bteq as the product name: D:\tar_teradata_client_packages hp-ux bteq A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v.14.00.00.00 * ************************************************************************ Load/Unload - Volume 2 Platform: HP-UX Default Path and Output File: C:\Documents and Settings\user\teradata-client-hp-ux-load-unload-volume-2.tar Hit [Enter] to accept the path: "C:\Documents and Settings\username", or input a different save directory : "C:\Documents and Settings\username" Output File "C:\Documents and Settings\username\teradata-client-hp-ux-load-unload-volume-2.tar" ---Archiving setup files and dependency packages for hp-ux tar cvf "C:\Documents and Settings\username\teradata-client-hp-ux-load-unload-volume-2.tar" HPUX \TeraGSS* a HP-UX/TeraGSS/ia64/pkginfo.txt 1 block a HP-UX/TeraGSS/ia64/TeraGSS_hpux-ia64_14.00.00.00.depot 164540 blocks a HP-UX/TeraGSS/ia64/TeraGSS_hpux-ia64_14.00.00.00.psf 3 blocks a HP-UX/TeraGSS/pa32/pkginfo.txt 1 block a HP-UX/TeraGSS/pa32/TeraGSS_hpux-pa32_14.00.00.00.depot 114340 blocks a HP-UX/TeraGSS/pa32/TeraGSS_hpux-pa32_14.00.00.00.psf 3 blocks tar rvf "C:\Documents and Settings\username\teradata-client-hp-ux-load-unload-volume-2.tar" HPUX\tdicu* tar: blocksize = 20 a HP-UX/tdicu/ia64/swagent.log 3 blocks a HP-UX/tdicu/ia64/tdicu1400/tdicu1400/opt/teradata/client/14.00/tdicu/ lib/libicudatatd.so.46.0 16206 blocks a HP-UX/tdicu/ia64/tdicu1400/tdicu1400/opt/teradata/client/14.00/tdicu/ lib/libicui18ntd.so.46.0 24941 blocks a HP-UX/tdicu/ia64/tdicu1400/tdicu1400/opt/teradata/client/14.00/tdicu/ lib/libicuiotd.so.46.0 773 blocks … a HP-UX/bteq/pa32/catalog/swlock 0 blocks a HP-UX/bteq/pa32/catalog/INDEX 9 blocks a HP-UX/bteq/pa32/catalog/bteq1400/bteq1400/INFO 4 blocks a HP-UX/bteq/pa32/catalog/bteq1400/bteq1400/INDEX 1 block a HP-UX/bteq/pa32/catalog/bteq1400/bteq1400/postinstall 10 blocks a HP-UX/bteq/pa32/catalog/bteq1400/bteq1400/postremove 5 blocks a HP-UX/bteq/pa32/catalog/bteq1400/bteq1400/preinstall 11 blocks a HP-UX/bteq/pa32/catalog/bteq1400/pfiles/INFO 1 block a HP-UX/bteq/pa32/catalog/bteq1400/pfiles/INDEX 8 blocks a HP-UX/bteq/pa32/catalog/bteq1400/pfiles/README 1 block a HP-UX/bteq/pa32/catalog/bteq1400/pfiles/_ACL 1 block a HP-UX/bteq/pa32/catalog/bteq1400/pfiles/_LOCK_FILE 0 blocks a HP-UX/bteq/pa32/catalog/bteq1400/pfiles/_OWNER 1 block a HP-UX/bteq/pa32/catalog/dfiles/INFO 1 block a HP-UX/bteq/pa32/catalog/dfiles/INDEX 1 block a HP-UX/bteq/pa32/catalog/dfiles/_ACL 1 block a HP-UX/bteq/pa32/catalog/dfiles/_PROD_DFLT_ACL 1 block a HP-UX/bteq/pa32/catalog/dfiles/_LOCK_FILE 0 blocks a HP-UX/bteq/pa32/catalog/dfiles/_OWNER 1 block 176 Teradata Tools and Utilities for Microsoft Windows Installation Guide Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR The file has been saved at : C:\Documents and Settings\username\teradata-client-hp-ux-load-unload-volume-2.tar.gz Archiving Linux Packages This example archives packages and dependencies that are required for the deployment of Teradata Tools and Utilities products to SUSE Linux or Red Hat Linux clients. The packages and dependencies are copied from the installation media, archived as a tar file, and compressed. The compressed archive can be copied to SUSE Linux or Red Hat Linux machines and expanded. The example assumes that you run the archiving script on a 32-bit Windows system on which tar.exe and gzip.exe are installed. 1 Run the script with linux as the value of the platform parameter: D:\tar_teradata_client_packages linux A screen similar to the following appears: ************************************************************************ * Tar Teradata Client Packages v.14.00.00.00 * ************************************************************************ Load/Unload - Volume 2 Platform: Linux Default Path and Output File: C:\Documents and Settings\user\teradata-client-linux-load-unload-volume2.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-14.00.00.00-1.i386.rpm 118 blocks a Linux/mload/mload140-14.00.00.00-1.i386.rpm 374 blocks a Linux/piom/piom140-14.00.00.00-1.i386.rpm 79 blocks a Linux/tdicu/tdicu-14.00.00.00-1.noarch.rpm 20564 blocks a Linux/fastld/fastld140-14.00.00.00-1.i386.rpm 189 blocks a Linux/TeraGSS/TeraGSS_redhatlinux-i386-14i.00.00.00-1.i386.rpm 12240 blocks a Linux/fastexp/fastexp140-14.00.00.00-1.i386.rpm 341 blocks a Linux/tpump/tpump140-14.00.00.00-1.i386.rpm 478 blocks a Linux/npaxsmod/npaxsmod-14.00.00.00-1.i386.rpm 272 blocks a Linux/cliv2/cliv2-14.00.00.00-1.x86_64.rpm 766 blocks a Linux/bteq/bteq-14.00.00.00-1.i386.rpm 303 blocks 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 Teradata Tools and Utilities for Microsoft Windows Installation Guide 177 Chapter 9 Deploy Teradata Tools and Utilities with TAR Deploying Applications with TAR The file has been saved at : C:\Documents and Settings\user\teradata-client-linux-load-unloadvolume-2.tar.gz 178 Teradata Tools and Utilities for Microsoft Windows Installation Guide