Teradata Tools and Utilities
Installation Guide for Microsoft Windows
Release 13.10.00
B035-2407-020A
August 2010
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce,
SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You’ve Never Seen Your Business Like
This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates.
Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc.
EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.
GoldenGate is a trademark of GoldenGate Software, Inc.
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 and Engenio are registered trademarks 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.
Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.
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.
Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other
countries.
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 collective membership mark and a service mark of Unicode, Inc.
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-2010 by Teradata Corporation. All Rights Reserved.
Preface
Purpose
This book provides information about installing the Teradata Tools and Utilities Release
13.10.00 software on a computer that runs on a Windows operating system. Teradata Tools
and Utilities is a group of products designed to work with Teradata Database.
Audience
This book is intended for use by:
•
System and application programmers
•
System administrators
•
Database administrators and relational database developers
•
System operators and other database specialists
Supported Releases
This book supports the following releases:
•
Teradata Database 13.10.00
•
Teradata Tools and Utilities 13.10.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 Installation Guide for Microsoft Windows
3
Preface
Prerequisites
Prerequisites
The following prerequisite knowledge is required for this product:
•
Computer technology and terminology
•
Relational database management systems
•
Utilities that load and retrieve data
Changes to This Book
The following changes were made to this book in support of the current release. Changes are
marked with change bars. For a complete list of changes to the product, see the Teradata Tools
and Utilities Release Definition associated with this release.
Date and Release
Description
August 2010
The following changes were made to support Teradata Tools and Utilities
13.10 installation:
13.10
• Added ARC 64-bit info to SMS table.
February 2010
13.10
The following changes were made to support Teradata Tools and Utilities
13.10 installation:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
4
Total Manual redesign.
Added fix for Windows path overrun.
Added SMS Deployment section to the documentation.
Added information on migrating to VS8.0.
Added information for Teradata Tools and Utilities upgrades to Release
13.10.
Moved installation procedures from several stand alone documents to
main install document.
Optimized the SQLA startup performance.
TDICU 12.00.00.00 requires Windows Installer 3.0.
Created 64-bit installation packages for Data Connector.
Created Basic MSI packages for most products. See the section on
Deploying Using SMS.
Added ARC installation information. Required for BAR.
Updated Minimum Configuration section.
Included .NET Data Provider installation instructions.
Removed ODBC Driver for Teradata from Tape Storage Management
Enablers CD.
Created a Windows 64-bit directory in Tape Storage Management
Enablers CD.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Preface
Changes to This Book
Date and Release
Description
February 2010
• Added information about Teradata Parallel Transporter Wizard
requiring 32-bit Java.
• Installer must be administrator to install products on WS 8 and
Windows 7.
• Made changes to version scheme.
• Added information on SPNEGO.
• Added Teradata Monitor Object.
• Delivering both VC 7.1 and VC 8.0 compilers in 32-bit Teradata Parallel
Transporter API package.
• Discontinued BTEQWIN DLLs.
• Discontinued support for z/VM.
• Discontinued support for MP-RAS.
• Discontinued Teradata MultiTool.
13.10 (continued)
August 2008
13.00
The following changes were made to support Teradata Tools and Utilities
13.00 installation:
• Reduced the number of Teradata Parallel Transport products from 15 to
6.
• The Tivoli Access Module is no longer included on the Tape Storage
Management Enabler CD.
• ODBC, CLIv2, and Shared ICU Libraries for Teradata are now Basic MSI
Installation packages.
• For those Client products that have both a 32-bit and a 64-bit
installation package, both versions can co-exist on an EM64T system.
• When a Client product that has both a 32-bit and a 64-bit installation
package and is installed silently on an EM64T system, both the 32-bit
and the 64-bit versions will be installed. If the Client product is installed
interactively, only the 64-bit version is installed.
• Earlier versions of installed Client products are now automatically
uninstalled as part of the installation.
• Changes to support the new Teradata Corporation branding that
include a new splash screen, copyright, license text, and logo.
• A new directory structure for the Teradata Tools and Utilities 13.00
client products where the default location is now:
%ProgramFiles%\Teradata\Client\13.0\<product>
Teradata Tools and Utilities Installation Guide for Microsoft Windows
5
Preface
Additional Information
Additional Information
Additional information that supports this product and Teradata Tools and Utilities is available
at the web sites listed in the table that follows. In the table, mmyx represents the publication
date of a manual, where mm is the month, y is the last digit of the year, and x is an internal
publication code. Match the mmy of a related publication to the date on the cover of this book.
This ensures that the publication selected supports the same release.
Type of Information
Description
Access to Information
Release overview
Use the Release Definition for the following
information:
1 Go to http://www.info.teradata.com/.
• Overview of all of the products in the
release
• Information received too late to be
included in the manuals
• Operating systems and Teradata
Database versions that are certified to
work with each product
• Version numbers of each product and
the documentation for each product
• Information about available training
and the support center
3 Type 2029 in the Publication Product ID box.
Use the Teradata Information Products web
site to view or download specific manuals
that supply related or additional
information to this manual.
1 Go to http://www.info.teradata.com/.
Late information
Additional product
information
2 Under Online Publications, click General Search.
4 Click Search.
5 Select the appropriate Release Definition from
the search results.
2 Under the Online Publications subcategory,
Browse by Category, click Data Warehousing.
3 Do one of the following:
• For a list of Teradata Tools and Utilities
documents, click Teradata Tools and Utilities,
and then select an item under Releases or
Products.
• Select a link to any of the data warehousing
publications categories listed.
Specific books related to Teradata Call-Level
Interface Version 2 for Channel-Attached Systems
are as follows:
• Messages
B035-1096-mmyA
• Teradata Tools and Utilities Command Summary
B035-2401-mmyA
• Teradata JDBC Driver User Guide
B035-2403-mmyA
• Teradata Tools and Utilities Installation Guide for
Microsoft Windows
B035-2407-mmyA
• Teradata MultiLoad Reference
B035-2409-mmyA
6
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Preface
Additional Information
Type of Information
Description
Access to Information
• (Continued from the bulleted list above) in the
Publication Product ID field, enter one of the
following book numbers:
• Teradata FastExport Reference
B035-2410-mmyA
• Teradata FastLoad Reference
B035-2411-mmyA
• Teradata Archive/Recovery Utility Reference
B035-2412-mmyA
• Basic Teradata Query Reference
B035-2414-mmyA
• Teradata Director Program Reference
B035-2416-mmyA
• Teradata Call-Level Interface Version 2 Reference
for Channel-Attached Systems
B035-2417-mmyA
• Teradata Call-Level Interface Version 2 Reference
for Network-Attached Systems
B035-2418-mmyA
• Teradata Transparency Series/ Application
Programming Interface User Guide
B035-2419-mmyA
• Teradata Tools and Utilities Access Module
Programmer Guide
B035-2424-mmyA
• Teradata Tools and Utilities Access Module
Reference
B035-2425-mmyA
• Teradata SQL Assistant for Microsoft Windows
User Guide
B035-2430-mmyA
• Teradata Parallel Transporter Reference
B035-2436-mmyA
• Teradata Access Module for Tivoli Installation and
User Guide
B035-2444-mmyA
• Teradata Parallel Transporter User Guide
B035-2445-mmyA
• Teradata Preprocessor2 for Embedded SQL
Programmer Guide
B035-2446-mmyA
• IBM IMS/DC Interface for Teradata Reference
B035-2447-mmyA
• IBM CICS Interface for Teradata Reference
B035-2448-mmyA
• Interactive Teradata Query Reference
B035-2451-mmyA
Teradata Tools and Utilities Installation Guide for Microsoft Windows
7
Preface
Additional Information
Type of Information
Description
Access to Information
• (Continued from the bulleted list above) in the
Publication Product ID field, enter one of the
following book numbers:
• Interactive Teradata Query User Guide
B035-2452-mmyA
• Teradata Tools and Utilities Installation Guide for
IBM z/OS
B035-2458-mmyA
• Teradata Tools and Utilities Installation Guide for
UNIX and Linux
B035-2459-mmyA
• Teradata System Emulation Tool User Guide
B035-2492-mmyA
• OLE DB Provider for Teradata Installation and
User Guide
B035-2498-mmyA
• Teradata Administrator User Guide
B035-2502-mmyA
• Teradata Statistics Wizard User Guide
B035-2503-mmyA
• Teradata Visual Explain User Guide
B035-2504-mmyA
• Teradata Index Wizard User Guide
B035-2506-mmyA
• ODBC Driver for Teradata User Guide
B035-2509-mmyA
• Teradata Query Director User Guide
B035-2510-mmyA
• Teradata Query Scheduler Administrator Guide
B035-2511-mmyA
• Teradata Query Scheduler User Guide
B035-2512-mmyA
• Teradata Workload Analyzer User Guide
B035-2514-mmyA
• Teradata Parallel Transporter Application
Programming Interface Programmer Guide
B035-2516-mmyA
• Teradata Parallel Data Pump Reference
B035-3021-mmyA
• Teradata Meta Data Services Installation and
Administration Guide
B035-3118-mmyA
• Teradata Meta Data Services Programmer Guide
B035-3047-mmyA
8
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Preface
Additional Information
Type of Information
Description
Access to Information
CD-ROM images
Access a link to a downloadable CD-ROM
image of all customer documentation for
this release. Customers are authorized to
create CD-ROMs for their use from this
image.
1 Go to http://www.info.teradata.com/.
2 Under the Online Publications subcategory,
Browse by Category, click Data Warehousing.
3 Click CD-ROM List and Images.
4 Follow the ordering instructions.
Ordering
information for
manuals
Use the Teradata Information Products web
site to order printed versions of manuals.
1 Go to http://www.info.teradata.com/.
2 Under Print & CD Publications, click How to
Order.
3 Follow the ordering instructions.
General information
about Teradata
The Teradata home page provides links to
numerous sources of information about
Teradata. Links include:
1 Go to Teradata.com.
2 Select a link.
• Executive reports, case studies of
customer experiences with Teradata,
and thought leadership
• Technical information, solutions, and
expert advice
• Press releases, mentions, and media
resources
Teradata Tools and Utilities Installation Guide for Microsoft Windows
9
Preface
Additional Information
10
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Changes to This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Chapter 1:
Windows General Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
General Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Instructions for Installing Across a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Instructions for Installing Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Chapter 2:
Installing from CD Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Step 1: Inspect the Installation Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Inspect the Installation Kit CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Step 2: Review Platforms, Products, Dependencies, and Requirements . . . . . . . . . . . . . . . . .
Determine if Platforms and Products are Compatible . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Read Product Descriptions and Determine Product Dependencies . . . . . . . . . . . . . . . . .
Determine if System Requirements have been Met . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Determine if the Installer has Administrative Privileges . . . . . . . . . . . . . . . . . . . . . . . . . .
23
23
23
24
24
Step 3: Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . . . . . . . 24
Manually Uninstall Previous Versions of Teradata Tools and Utilities . . . . . . . . . . . . . . 24
Step 4: Install Third-Party Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Teradata Parallel Transporter Wizard Special Considerations . . . . . . . . . . . . . . . . . . . . . 25
Install Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Step 5: Install Teradata Tools and Utilities from the CD Media . . . . . . . . . . . . . . . . . . . . . . . 27
Alternate Method of Installing Teradata Tools and Utilities on Windows . . . . . . . . . . . 27
Teradata Tools and Utilities Installation Guide for Microsoft Windows
11
Table of Contents
Install Teradata Tools and Utilities on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Step 6: Install Drivers from the Teradata Download Center . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Step 7: Install Patches from the Teradata Software Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Step 8: Add CLI User Exit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Step 9: Install Teradata Meta Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Step 10: Install Asynchronous Release Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Step 11: Install the Windows Help Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Step 12: Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Step 13: Restart the Client Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Step 14: Verify the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Step 15: Deploying Using SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Security and Connecting to a Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Troubleshooting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Chapter 3:
Installing from the
Teradata Software Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Task 1: Install Patches on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Step 1: Identify the Patches Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Step 2: Download the Setup Package from the Teradata Software Server . . . . . . . . . . . . .35
Step 3: Install the Downloaded Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Chapter 4:
Installing from
the Teradata Download Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Products Available on the Download Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Task 1: Install on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Step 1: Identify the Package to Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Step 2: Download Packages from the Teradata Download Center . . . . . . . . . . . . . . . . . . .39
Step 3: Install the Downloaded Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Chapter 5:
Installing the Windows Help Program . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Task 1: Install the Windows Help Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
12
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Table of Contents
Chapter 6:
Adding CLI User Exit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Task 1: Add CLI User Exit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Chapter 7:
Installing .NET Data Provider
for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Task 1: Install .NET Data Provider for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.NET Data Provider for Teradata Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 1: Review Product Description, Dependencies and Restrictions. . . . . . . . . . . . . . . .
Step 2: Uninstall .NET Data Provider for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 3: Install Third-Party Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 4: Download .NET Data Provider for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 5: Install .NET Data Provider for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 6: Configure .NETteragss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 7: Verify Installation and Connectivity to the Teradata Database . . . . . . . . . . . . . .
45
45
45
46
47
48
49
51
51
Chapter 8:
Installing Teradata Meta Data Services
on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Task 1: Review MDS Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 1: Review Teradata Meta Data Services Documentation . . . . . . . . . . . . . . . . . . . . . .
Step 2: Review Teradata Meta Data Services Product Description . . . . . . . . . . . . . . . . . .
Step 3: Review Teradata MDS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 4: Review Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 5: Review Software Components to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
53
53
53
54
56
Task 2: Uninstall Teradata MDS on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Task 3: Install Teradata MDS on Windows Workstations and Servers . . . . . . . . . . . . . . . . . . 57
Task 4: Set the MDS Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Step 1: Configure Windows Workstations or Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Task 5: Create the Meta Data Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Step 1: Create the Repository from a Windows Workstation . . . . . . . . . . . . . . . . . . . . . . 69
Task 6: Migrate the Meta Data Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Step 1: Migrate the MDS Repository on a Windows Workstation . . . . . . . . . . . . . . . . . . 70
Task 7: Create A Virtual Directory or Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Teradata Tools and Utilities Installation Guide for Microsoft Windows
13
Table of Contents
Chapter 9:
Installing Automatic DIM Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Task 1: Review Automatic DIM Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Step 1: Review the Automatic DIM Update Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Step 2: Review Out of Sync Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Task 2: Configure Automatic DIM Update Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Step 1: Configure Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Task 3: Install DIM Update Server Software (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Task 4: Install and Configure RSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Step 1: Install and Configure RSG on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Step 2: Start/Stop the RSG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Task 5: Configure Automatic DIM Update in MetaManager. . . . . . . . . . . . . . . . . . . . . . . . . . .80
Step 1: Add a Teradata Database System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Step 2: Add Teradata Nodes to a Teradata Database System . . . . . . . . . . . . . . . . . . . . . . . .81
Step 3: Load Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Step 4: Enable Automatic DIM Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Task 6: Check DIM Update Status with MetaManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Task 7: Start/Stop the DDL Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Task 8: Start/Stop the MDS Action Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
Chapter 10: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deploying Using SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Tasks to Deploy Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Task 1: Gather Installation Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Step 1: Determine Versions to Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Step 2: Download Installation Packages from the CD Media . . . . . . . . . . . . . . . . . . . . . . .88
Step 3: Download Installation Packages from the Teradata Download Center . . . . . . . . .90
Step 4: Download Installation Packages from the Teradata Software Server . . . . . . . . . . .91
Step 5: Download Third-Party Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Task 2: Create Response Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Step 1: Installing with InstallScripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Step 2: Installing Using Basic MSI Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Task 3: Copy Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Step 1: Copy Installation Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Task 4: Create a Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Task 5: Deploy Products Using SMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Step 1: Deploying Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
14
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Table of Contents
Chapter 11:
Example Uninstall Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Chapter 12:
Configuring Teradata Tools and Utilities. . . . . . . . . . . . . . . . . . . . . . . . 139
Task 1: Configure Teradata Call-Level Interface version 2 (CLIv2). . . . . . . . . . . . . . . . . . . .
Step 1: Setup Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 2: Setup Environment Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 3: Setup System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
139
139
141
144
Task 2: Configure ODBC Driver for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Step 1: Configure an ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Task 3: Configure Teradata Query Scheduler Administrator . . . . . . . . . . . . . . . . . . . . . . . . . 146
Step 1: Modify the HOSTS File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Task 4: Configure Teradata Query Scheduler Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Task 5: Configure Teradata Query Scheduler Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Step 1: Specify a Default Teradata Query Scheduler Server . . . . . . . . . . . . . . . . . . . . . . . 147
Step 2: Change Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Task 6: Configure Teradata Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Task 7: Configure Teradata Parallel Transporter for Windows . . . . . . . . . . . . . . . . . . . . . . .
Step 1: Edit the Configuration File (twbcfg.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 2: Edit the Properties File (tptwizard.properties) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 3: Setup User Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 4: Setup System Environment Variable ORACLE_HOME . . . . . . . . . . . . . . . . . . .
149
149
150
150
151
Task 8: Configure Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Chapter 13:
Verifying the Installation
Using the CLI Sample Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Task 1: Run clisamp to Verify the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Chapter 14:
Verifying the OLE DB Provider for Teradata Installation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Task 1: Verify the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Teradata Tools and Utilities Installation Guide for Microsoft Windows
15
Table of Contents
Chapter 15:
Checking Files and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Step 1: Verifying Installation of Individual Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Basic Teradata Query (BTEQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
Named Pipes Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
.NET Data Provider for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
ODBC Driver for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
OLE DB Provider for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
Shared ICU Libraries for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
Teradata Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Teradata Archive/Recovery Utility (ARC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Teradata C Preprocessor2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Teradata Call-Level Interface version 2 (CLIv2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Teradata Data Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
Teradata FastExport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
Teradata FastLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
Teradata Generic Security Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Teradata Index Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
Teradata Meta Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
Teradata MultiLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Teradata OLE DB Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Teradata Parallel Data Pump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Teradata Parallel Transporter API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Teradata Parallel Transporter Export Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
Teradata Parallel Transporter Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
Teradata Parallel Transporter Load Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
Teradata Parallel Transporter Stream Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
Teradata Parallel Transporter Update Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
Teradata Performance Monitor Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Teradata Query Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Teradata Query Scheduler Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Teradata Query Scheduler Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
Teradata Query Scheduler Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
Teradata SQL Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
Teradata Statistics Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
Teradata System Emulation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
Teradata Visual Explain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225
Teradata WebSphere MQ Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231
Teradata Workload Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231
16
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Table of Contents
Chapter 16:
Uninstalling Previous Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Task 1: Uninstall Previous Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Step 1: Observe the Uninstallation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Step 2: Uninstall Individual Products - Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Chapter 17:
Installation Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Task 1: Inspect the Installation Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Task 2: Determine the CD Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Chapter 18:
Product Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Task 1: Review Product Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Chapter 19:
Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Task 1: Review Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Task 2: Installing Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Chapter 20:
Windows System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Task 1: Determine System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 1: Determine Platform Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 2: Determine Privilege Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 3: Determine Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 4: Determine Teradata Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 5: Determine Minimum Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 6: Determine Recommended Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teradata Tools and Utilities Installation Guide for Microsoft Windows
255
255
255
255
255
256
256
17
Table of Contents
Chapter 21:
Windows Installation Recommendations . . . . . . . . . . . . . . . . . . . . . . . .259
Task 1: Determine Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
Recommendation 1: Typical, Custom, and Network Installations . . . . . . . . . . . . . . . . . .259
Recommendation 2: Command Line Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
Task 2: Operating System Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
Recommendation 1: Installing on Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . .259
Recommendation 2: Installing on EM64T Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
Task 3: Product Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
Recommendation 1: Installation of Dependent Products . . . . . . . . . . . . . . . . . . . . . . . . .260
Chapter 22:
Security and Connecting to a
Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
Task 1: Make the Database Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
Step 1: Review Logon Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
Step 2: Connect To a Teradata Database from a GUI Application . . . . . . . . . . . . . . . . . .261
Step 2: Connect to a Teradata Database from Command Line Driven Applications . . .263
Step 3: Connect to a Teradata Database Programmatically . . . . . . . . . . . . . . . . . . . . . . . .270
Step 4: Check Logon Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271
Step 5: Reselect Authentication Mechanism on Connection Error. . . . . . . . . . . . . . . . . .272
Chapter 23:
Troubleshooting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
Task 1: Troubleshoot Client Computer Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
Problem 1: Path Overrun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
Problem 2: Cannot Communicate Over the Network with Teradata Database . . . . . . .274
Problem 3: Incorrect Path Name in COPLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274
Problem 4: File localisation.dll Could Not Be Opened. . . . . . . . . . . . . . . . . . . . . . . . . . . .274
Problem 5: File icuuctd36.dll Could Not Be Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Problem 6: Incorrect Path Name in COPANOMLOG. . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Problem 7: Incorrect CLIv2 Libraries Referenced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Problem 8: CLIv2 DLLs Load Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Problem 9: Incorrect Entries in the hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Problem 10: Missing Entries in the services File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Problem 11: Incorrect clispb.dat Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276
Problem 12: Cannot Log On from CLI Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276
18
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Table of Contents
Problem 13: Cannot Log On to the Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Problem 14: MSVCR80.DLL not found Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Problem 15: Troubleshooting OLE DB Provider for Teradata Installation . . . . . . . . . . 276
Task 2: Troubleshoot Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Problem 1: Troubleshooting Network Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Task 3: Troubleshoot Software Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem 1: Error Running ttu.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem 2: Install Button Does Not Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem 3: InstallShield 1603 Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem 4: InstallShield 1607 Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem 5: InstallShield 432 Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
283
283
283
283
284
286
Task 4: Troubleshoot Teradata Database Hardware Problems . . . . . . . . . . . . . . . . . . . . . . . 286
Chapter 24:
Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Teradata Tools and Utilities Installation Guide for Microsoft Windows
19
Table of Contents
20
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 1
Windows General Install
This document describes the general installation of Teradata Tools and Utilities products from
CD-ROM, Teradata Download Center, and Teradata Software Server. It contains specific
instructions for installing Teradata Meta Data Services and asynchronous product .Net Data
Provider for Teradata.
A section is included that describes how to deploy products across the web using an SMS
Server.
General Installation Instructions
Whenever installing Teradata Tools and Utilities software, always compare the versions
available on the CD media, the Teradata Download Center and the Teradata Software Server.
In general, the software server will contain the most recent point release of a software product,
followed in turn by the download center and finally the CD media.
•
Installing from a Web URL - Some Teradata Tools and Utilities have third-party
dependencies. Install these dependencies from these respective URLs.
•
Installing from CD Media - Describes how to install products on a single-user from the
CD media in the Teradata Tools and Utilities Installation Kit. The CDs contain installation
packages for the current release.
•
Installing from the Teradata Download Center - Describes how to install Teradata Tools
and Utilities communications packages and other software available on the Teradata
Download Center. The download center may contain more current software packages
which should be installed instead of lower version software contained on the CD media.
•
Installing from the Teradata Software Server - This document describes how to install
Teradata Tools and Utilities packages from the Teradata Software Server. The server may
contain updated software packages which should be installed in lieu of lower version
software contained on the CD media, or on the Teradata Download Center.
•
Installing from the ESDM Server - Teradata's Electronic Software Distribution
Management (ESDM) program is not currently available for Windows.
Instructions for Installing Across a Network
•
Deploying Using SMS - This document describes how to deploy one or more Teradata
Tools and Utilities products across your network using vbs scripts and SMS. It includes
Teradata Tools and Utilities Installation Guide for Microsoft Windows
21
Chapter 1: Windows General Install
Instructions for Installing Individual Products
how to download software packages to an SMS server or client, and create response files
required for installation for each package.
Instructions for Installing Individual Products
22
•
Installing Teradata Meta Data Services - Teradata Meta Data Services (MDS) is installed
from CD media or the Teradata Software Server. Installation is generally limited to
administrative users. This section details the installation of Teradata Meta Data Services.
•
Installing .NET Data Provider for Teradata - .NET Data Provider for Teradata has
recently been included as part of the Teradata Tools and Utilities CDs. Although it is not
overtly complex to install, it is presented as a “stand-alone” procedure since it includes
installing third-party software, and contains options and configuration beyond what
might be considered a “normal” installation. .NET Data Provider for Teradata can be
installed from the CD media or the download center.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 2
Installing from CD Media
Follow these steps to Install one or more Teradata Tools and Utilities products from the
Teradata Tools and Utilities installation Kit CD Media to Windows clients.
Step 1: Inspect the Installation Kit
Inspect the Installation Kit CDs
•
Installation Kit - Lists the Installation Kit CDs and indicates the CDs where products and
their dependencies are located. Inspect the Teradata Tools and Utilities Installation Kit for
completeness, and determine which CDs contain the products and the dependencies being
installed. Because of space limitations, products on some installation CDs are segregated
by platform.
Step 2: Review Platforms, Products,
Dependencies, and Requirements
Determine if the products being installed are compatible with and supported by the client.
Then determine if the minimum system requirements have been met, and which products
have dependencies which have to be installed.
Determine if Platforms and Products are Compatible
Links to a spreadsheet which lists the UNIX, Linux, Windows and mainframe platforms and
the products supported by each release of Teradata Tools and Utilities are located at:
•
http://www.info.teradata.com
Links to the current and last two major releases are included below:
•
Teradata Tools and Utilities 12.00.xx Supported Versions - [12.00.xx]
•
Teradata Tools and Utilities 13.00.xx Supported Versions - [13.00.xx]
•
Teradata Tools and Utilities 13.10.xx Supported Versions - [13.10.xx]
Read Product Descriptions and Determine Product Dependencies
•
Product Descriptions - Lists a synopsis of each of the products available.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
23
Chapter 2: Installing from CD Media
Step 3: Uninstall Previous Versions of Teradata Tools and Utilities
•
Product Dependencies - Lists the Teradata Tools and Utilities dependencies. When
installing from the main install, all Teradata Tools and Utilities product dependencies are
verified, and if not available, are installed automatically.
•
Third-Party Dependencies - Third-party products must be installed before installing any
Teradata Tools and Utilities Products. This software is not contained on the installation
CDs. Most are available from the manufacturer’s website.
Determine if System Requirements have been Met
•
Windows System Requirements - Lists minimum system and server requirements to install
Teradata Tools and Utilities
Determine if the Installer has Administrative Privileges
On Microsoft Windows Vista, Windows Server 2008, and Windows 7 operating systems User
Account Control (UAC) and other security infrastructure has been introduced to thwart
malware from accessing and possibly damaging the operating system.
If the operating system is one of the three previously mentioned, you must have administrator
privileges to install Teradata Tools and Utilities. If you do not possess the appropriate
administrative level, UAC messages may appear during the installation, including during a
silent installation.
Step 3: Uninstall Previous Versions of Teradata
Tools and Utilities
On Windows, previous versions of Teradata Tools and Utilities are automatically uninstalled
or upgraded by the Teradata Tools and Utilities installation.
24
•
All Release 13.10 Packages Uninstall pre-13.00 Releases of Teradata Tools and Utilities
Products Automatically - If versions of Teradata Tools and Utilities products earlier than
Release 13.00 exist on a machine, each Release 13.10 package being installed will
automatically uninstall all pre-Teradata Tools and Utilities 13.00 versions of the package,
before installing the Release 13.10 version of the product.
•
Release 13.10 Packages Upgrade Release 13.00 Products Automatically - If Release 13.00
Teradata Tools and Utilities products exist on the machine, each Release 13.10 package
upgrades the 13.00 package to 13.10, except for the following packages which support
side-by-side installations and multiple versions coexistence:
•
TeraGSS
•
SQLA
•
TPT packages
•
DBM packages
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 2: Installing from CD Media
Step 4: Install Third-Party Software Dependencies
Manually Uninstall Previous Versions of Teradata Tools and Utilities
•
Uninstalling Previous Versions - Follow the Uninstall Order. If you’ve decided to manually
uninstall Teradata Tools and Utilities products, use Add or Remove Programs in the
Control Panel to uninstall them in the following order:
1
All products other than the following 6 products
2
Teradata Data Connector (piom)
3
ODBC Driver for Teradata (tdodbc)
4
.NET Data Provider for Teradata
5
Call-Level Interface version 2 (cliv2)
6
Teradata Generic Security Services (teragss)
7
Shared ICU Libraries for Teradata (tdicu)
Note: Additionally, TQS Server must be uninstalled before TQS Client.
Step 4: Install Third-Party Software
Dependencies
Some Teradata Tools and Utilities products require the installation of third-party software.
Most third-party dependency software can be installed from the manufacturer’s website. Links
are provided where known.
Teradata Parallel Transporter Wizard Special Considerations
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 64bit JRE version.
If installing the TPT Wizard, use the following procedure to add the PATH to the JRE.
Procedure - Adding 32-bit JRE Path for Teradata Parallel Transporter Wizard
1
Install the 32-bit JRE version 1.4.2_06 or later on the 64-bit Windows platform. To install
the JRE, visit the website at:
http://java.sun.com/javase/downloads
2
Add the path to the 32-bit JRE java.exe command to the front of the system PATH
environment variable.
3
Run the Teradata Parallel Transporter Wizard.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
25
Chapter 2: Installing from CD Media
Step 4: Install Third-Party Software Dependencies
Install Third-Party Software
Install the third-party software listed for each product being installed. Where available, the
download site or product information site is shown.
.NET Data Provider for Teradata
•
Microsoft .NET Framework Redistributable Package, version 2.0 or later
http://msdn.microsoft.com/downloads
•
(Optional) Microsoft Visual Studio 2005 or Microsoft Visual 2008 Integration Feature
http://www.microsoft.com/eXPress/download/
•
(Optional) Microsoft SQL Server Business Intelligence Development Studio, is delivered
SQL Server Reporting Services. The following is the link to “Introducing Business
Intelligence Development Studio”.
http://msdn.microsoft.com/en-us/library/ms173767.aspx
ODBC Driver for Teradata
•
Microsoft Data Access Components (MDAC), version 2.8 SP1 (on distribution CD)
(required for Windows 2000 only)
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037185d0506396c&DisplayLang=en
OLE DB Provider for Teradata
•
Microsoft Data Access Components (MDAC), version 2.8 SP1 (on distribution CD)
(required for Windows 2000 only)
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037185d0506396c&DisplayLang=en
Teradata JDBC Driver
•
JDK 1.4, JDK 5.0, or JDK 6.0 from Sun
http://java.sun.com/javase/downloads/index_jdk5.jsp
http://java.sun.com/javase/downloads/index.jsp
•
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
Teradata Parallel Transporter Infrastructure
•
Java 2 Runtime Environment 1.4.2_06 or later
http://java.sun.com/products/archive
Teradata Query Scheduler Administrator
26
•
TCP/IP driver with WinSock support for Windows version 1.1 or later
•
Ethernet or Token Ring packet driver compatible with the above
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 2: Installing from CD Media
Step 5: Install Teradata Tools and Utilities from the CD Media
Teradata SQL Assistant
•
Microsoft .NET Framework, version 2.0 or later
http://msdn.microsoft.com/downloads
Teradata WebSphere MQ Access Module
•
IBM® WebSphere® MQ 5.2
http://www-01.ibm.com/software/data/masterdata/product-info/library/
documentation.html
Step 5: Install Teradata Tools and Utilities from
the CD Media
•
Follow the Install Order - When installing Teradata Tools and Utilities products other
than with a Main Install, products must be installed in the following order.
1
Shared ICU Libraries for Teradata (tdicu)
2
Teradata Generic Security Services (teragss)
3
Call-Level Interface version 2 (cliv2)
4
ODBC Driver for Teradata (tdodbc)
5
.NET Data Provider for Teradata
6
Teradata Data Connector (piom)
7
Any other products
Note: Additionally, TQS Client must be installed before TQS Server.
Warning:
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 XP or install the
Microsoft hotfix to increase the PATH size to 2048 characters.
Warning:
A command line window appears during the installation of Teradata SQLA Assistant. Do not
close the window during the installation, it is required by the installation. Ignore any error
messages that appear in the window.
Warning:
For ODBC on all platforms, since the installation process now installs both 32-bit and 64-bit
versions of the ODBC driver in silent mode, both the 32-bit and 64-bit versions of TeraGSS must
be installed before installing ODBC.
Note: 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.
Alternate Method of Installing Teradata Tools and Utilities on Windows
Several products can be installed using Teradata Parallel Upgrade Tool (PUT). PUT automates
and makes parallel the upgrade process. Products which can be installed using PUT include:
Teradata Tools and Utilities Installation Guide for Microsoft Windows
27
Chapter 2: Installing from CD Media
Step 5: Install Teradata Tools and Utilities from the CD Media
•
Basic Teradata Query
•
FastExport
•
FastLoad
•
MultiLoad
•
Named Pipes Access Module
•
OLE DB Provider for Teradata
•
Shared ICU Libraries for Teradata
•
Teradata Archive/Recovery Utility
•
Teradata Data Connector
•
Teradata Generic Security Services - Client
•
Teradata Meta Data Services and MDS Relay Services Gateway
•
Teradata Parallel Data Pump
•
Teradata WebSphere® MQ Access Module
For information about using PUT to install these products, see the Parallel Upgrade Tool
(PUT) for Microsoft Windows User Guide, B035-5710-mmyA.
Install Teradata Tools and Utilities on Windows
The following procedure installs Teradata Tools and Utilities on Windows.
Procedure - Install Teradata Tools and Utilities - Typical Installation
Follow these steps to begin an installation:
1
Close all active Windows programs and disable any virus protection software running on
the client computer.
2
Insert the Teradata Utility Pack - Vol 1 of 3 (Windows) CD into the CD drive.
3
In the Welcome to Teradata Tools and Utilities dialog, click Install Product.
Note: If the Welcome dialog does not appear shortly after the CD is inserted, use Windows
Explorer to navigate to the main folder of the CD. Then double-click the setup.bat file to
start the installation process.
4
In the Choose Setup Language dialog, select the desired language, then click OK.
Note: English and Japanese are the only languages currently supported
5
In the Welcome dialog, click Next.
6
In the Software License Agreement dialog, read the agreement, then click Yes to accept it.
7
In the Setup Type dialog, 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
28
To use a destination location other than the default, click Browse, navigate to the location
where the files will be installed, click OK, then click Next. Write access to the destination
folder, the Windows root folder, and the Windows system folder is required.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 2: Installing from CD Media
Step 6: Install Drivers from the Teradata Download Center
9
In the Choose Destination Location dialog, if the default path shown in the Destination
Folder block is acceptable, click Next. (This is recommended.)
10 In the Select Install Method dialog, select the products to install silently, or clear the
products to interactively install. Then click Next.
Those products not highlighted are installed interactively, the product setup sequence is
activated to make adjustments during installation.
11 In the Install Wizard Completion screen, click Finish to complete the installation.
Note: The ODBC Driver for Teradata Setup may take several minutes.
12 Repeat the previous steps for each Windows CD in the installation kit.
•
Preprocessors for Windows Vol. 1 of 3
•
Query Director Linux-Windows Vol. 1 of 1
•
Load/Unload for Windows Vol 1 of 3
•
Parallel Transporter for Windows Vol. 1 of 3
•
Tape Storage Management Enablers Linux - Windows Vol. 1 of 1
•
Database Management Vol. 1 of 1
•
Teradata Meta Data Services Linux - MPRAS(RSG) - Windows Vol. 1 of 1
13 Choose whether or not to view the Release Definition, then click Finish.
Step 6: Install Drivers from the Teradata
Download Center
•
Installing from the Teradata Download Center - Install products from the Teradata
Download Center. All products are not available.
Step 7: Install Patches from the Teradata
Software Server
•
Installing from the Teradata Software Server - Install the most recent critical postproduction product updates from the Teradata Software Server.
Step 8: Add CLI User Exit Functions
•
Adding CLI User Exit Functions - [Optional] CLI User Exit functions are general purpose
facilities that can be added to the CLI workstation architecture on client systems after the
products have been installed. These functions allow user-defined processing to take place.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
29
Chapter 2: Installing from CD Media
Step 9: Install Teradata Meta Data Services
Step 9: Install Teradata Meta Data Services
To install the latest version of Teradata Meta Data Services and its associated products, go to:
•
Installing Teradata Meta Data Services on Windows
•
Installing Automatic DIM Update
Step 10: Install Asynchronous Release
Products
Install asynchronously released Teradata Tools and Utilities. The latest versions should be
installed from the Teradata Download Center.
Links to the .NET Data Provider for Teradata Release Definition, B035-2032-mmyC for the
latest releases of .NET Data Provider for Teradata. [Optional]:
•
.NET Data Provider for Teradata Release Definition - [Release 12.00.00]
•
.NET Data Provider for Teradata Release Definition - [Release 12.00.01]
•
.NET Data Provider for Teradata Release Definition - [Release 13.00]
•
.NET Data Provider for Teradata Release Definition - [Release 13.01]
Note: .NET Data Provider for Teradata installation is only included on the Teradata Utility
Pak CD.
To install the latest version of .NET Data Provider for Teradata, go to:
•
Installing .NET Data Provider for Teradata
Step 11: Install the Windows Help Program
This task should be performed for all clients that are running Windows 7, Windows Vista or
Windows Server 2008. If not running Windows 7, Windows Vista or Windows Server 2008,
skip to the next task.
This task installs the Windows Help Program to Windows Vista or Windows Server 2008 after
installing Teradata Tools and Utilities.
Procedure - Installing the Windows Help Program
Install the Windows Help Program on Windows 7, Windows Vista and Windows Server 2008.
30
1
Install the Teradata Tools and Utilities software before proceeding.
2
Go to http://www.microsoft.com/downloads/details.aspx?familyid=6EBCFAD9-D3F54365-8070-334CD175D4BB&displaylang=en
3
Click Continue.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 2: Installing from CD Media
Step 12: Configure Products
Note: Windows Vista users must pass a short validation process before installing the file.
Once validated, specific instructions are given for obtaining the download.
4
Run the executable.
Step 12: Configure Products
After the installation is complete, edit environment variable names, and configure products.
•
Configuring Teradata Tools and Utilities
Step 13: Restart the Client Computer
After editing environment variables and configuring products, always restart the client
computer to ensure that environment variables are set correctly, and to allow file upgrades to
complete.
Step 14: Verify the Installation
Verify the installation of individual Teradata Tools and Utilities products using one of the
following methods:
•
Verifying the Installation Using the CLI Sample Program - Verify the installation using the
CLI Sample program on the installed files.
•
Verifying the OLE DB Provider for Teradata Installation - If installed, verify the
installation of OLE DB Provider for Teradata.
•
Checking Files and Folders - Verify the installation by comparing a list of folder and file
names for each product.
Step 15: Deploying Using SMS
If you decide to deploy using SMS, go to the following chapters:
•
Deploying Using SMS
•
Example Uninstall Script
Reference Material
The information in this section is provided as additional reference material useful in logging
onto the database, and troubleshooting a Teradata Tools and Utilities installation
Teradata Tools and Utilities Installation Guide for Microsoft Windows
31
Chapter 2: Installing from CD Media
Reference Material
Security and Connecting to a Teradata Database
Security and Connecting to a Teradata Database contains information helpful in
understanding the security schemes used in Teradata and making a successful connection to a
Teradata Database.
Troubleshooting the Installation
Troubleshooting the Installation - Contains information helpful in troubleshooting problems
that may arise while installing Teradata Tools and Utilities products.
32
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 3
Installing from the
Teradata Software Server
To ensure the highest quality and best performance of Teradata Tools and Utilities products,
the most recent critical post-production updates can be installed from the Teradata Software
Server at:
http://tssprod.teradata.com:8080/TSFS/home.do
Task 1: Install Patches on Windows
Step 1: Identify the Patches Available
The following procedure shows how to download patches available on the Teradata Software
Server.
Procedure - Identifying Patches on the Teradata Software Server
The following steps illustrate how to identify patches on the Teradata Software Server.
1
Go to http://tssprod.teradata.com:8080/TSFS/home.do.
2
Click on Teradata Client. The Client Help screen appears.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
33
Chapter 3: Installing from the Teradata Software Server
Task 1: Install Patches on Windows
34
3
Click on Windows. The Teradata Client Released Software screen appears.
4
Select the Software Base and Platform Base, then click on Submit. The Client Patches
available screen appears.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 3: Installing from the Teradata Software Server
Task 1: Install Patches on Windows
Step 2: Download the Setup Package from the Teradata Software Server
The following procedure continues by downloading the selected product setup packages from
the Teradata Software Server.
Procedure - Downloading the Setup Package
1
Click in the check box(es) to select the software patch(es) to download
2
Enter your User Name and E-Mail Address, then click Submit.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
35
Chapter 3: Installing from the Teradata Software Server
Task 1: Install Patches on Windows
3
Click Download.
4
Then click Save and select the location to download the package.
5
Click Save to start the download.
Step 3: Install the Downloaded Package
The following steps continue with the installation of the downloaded product.
Procedure - Installing the Downloaded Package
1
Go to the location where the .zip file was saved.
2
Read the .txt readme file to determine further installation instructions.
3
Remove previous versions of the package.
4
Extract the package files to the folder.
5
Typically, install all the software, with dependencies preceding the package, by running
setup.exe in the unzipped folders.
36
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 4
Installing from
the Teradata Download Center
This document describes the general procedures for installing Teradata Tools and Utilities
from the Teradata Download Center on Windows.
Products Available on the Download Center
The following is a list of the Teradata Tools and Utilities products that can be installed from
the center.
Drivers and Connectivity Software:
•
ODBC Driver for Teradata
•
OLE DB Provider for Teradata
•
.NET Data Provider for Teradata
•
Teradata Call-Level Interface version 2
•
Teradata JDBC Driver
Task 1: Install on Windows
Perform the steps in this section to download and install products from the Teradata
Download Center on a Windows operating system.
Step 1: Identify the Package to Download
The following procedure illustrates how to identify which package are available to download
from the Teradata Download Center.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
37
Chapter 4: Installing from the Teradata Download Center
Task 1: Install on Windows
Procedure - Identifying Setup Packages Available on the Download Center
38
1
Go to http://www.teradata.com/downloadcenter/. The Teradata Download Center screen
with a list of selectable products appears.
2
Click on the product name. The list expands to list the operating systems which can be
chosen.
3
Click on Windows NT/2000/XP/Vista. A list of the windows downloads available appears.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 4: Installing from the Teradata Download Center
Task 1: Install on Windows
Step 2: Download Packages from the Teradata Download Center
The following steps illustrate how to download a typical setup package from the Teradata
Download Center.
Procedure - Downloading the Selected Setup Package from the Download Center
1
Click on the software package to download. A description of the package appears along
with a list of Download Files. If there are unique download procedures for a product or a
specific release, the link to a file containing the procedures also appears with the download
.zip file link.
2
If a readme file is included, click on the readme file link and determine any special
download or installation instructions before continuing.
3
Return to the Download screen.
4
Click on the Download Files package (typically a .zip file).
Teradata Tools and Utilities Installation Guide for Microsoft Windows
39
Chapter 4: Installing from the Teradata Download Center
Task 1: Install on Windows
5
Read the License Agreement, then click I Accept. A screen with a link to the Download file
appears.
6
Click Download..., and select the location where to save the .zip file.
7
Click SAVE to save the .zip file is saved to the location chosen.
Step 3: Install the Downloaded Product
The following steps continue with the installation of the downloaded product.
Procedure - Installing the Downloaded Product
1
Go to the location where the .zip file was saved.
2
Read the .txt readme file to determine further installation instructions.
3
Remove previous versions of the package.
4
Extract the package files to the folder.
5
Typically, install all the software, with dependencies preceding the package, by running
setup.exe in the unzipped folders.
40
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 5
Installing the Windows Help Program
This task should be performed for all clients that are running Windows Vista, Windows Server
2008, or Windows 7. If not running Windows Vista or Windows Server 2008, skip this section.
This task installs the Windows Help Program to Windows Vista or Windows Server 2008 after
installing Teradata Tools and Utilities.
Task 1: Install the Windows Help Program
Procedure - Installing the Windows Help Program
Install the Windows Help Program on Windows Vista, Windows Server 2008, and Windows 7.
1
Install the Teradata Tools and Utilities software before proceeding.
2
Go to http://www.microsoft.com/downloads/
3
In the Search box, type WinHlp32 Vista 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.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
41
Chapter 5: Installing the Windows Help Program
Task 1: Install the Windows Help Program
42
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 6
Adding CLI User Exit Functions
CLI User Exit functions are general-purpose facilities that are added to the CLI workstation
architecture on Windows systems. CLI User Exit functions are general purpose facilities that
can be added to the CLI workstation architecture on the selected operating system. These
functions allow user-defined processing to take place.
Task 1: Add CLI User Exit Functions
Procedure - Adding CLI User Exit Functions
Follow these steps to install CLI User Exit functions to a Window’s client.
1
Change Directories to the folder where the tdusr32.mak file was installed. The default
folder is %Program Files\Teradata\Client\<version>\cliv2\UserExit.
cd "%ProgramFiles%\Teradata\Client\<version>\cliv2\UserExit"
2
Modify the CliLgnEx.c or CliPPS.c file in the UserExit folder.
3
Compile and link using the make facility:
nmake -f userexit.mak CFG="tdusr32 - Win32 Release"
The following configurations are supported:
•
tdusr32 - Win32 Release
•
tdusr32 - Win32 Debug
The 64-bit configurations must use the correct environment for 64-bit development.
4
Move the tdusr32.dll file into the appropriate folder. By default this library is installed into
the %ProgramFiles%\Teradata\Client\<version>\cliv2\lib folder.
For more information on CLI User Exit Functions, see the Teradata Call-Level Interface
Version 2 Reference for Network-Attached Systems, Appendix D.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
43
Chapter 6: Adding CLI User Exit Functions
Task 1: Add CLI User Exit Functions
44
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 7
Installing .NET Data Provider
for Teradata
This section describes how to install .NET Data Provider for Teradata.
Task 1: Install .NET Data Provider for Teradata
.NET Data Provider for Teradata Documentation
Click on the following link to display a list of all .NET Data Provider for Teradata
documentation:
.NET Data Provider for Teradata documentation
Links to the .NET Data Provider Release Definition, B035-2032-mmyC for the latest releases of
.NET Data Provider for Teradata. [Optional]:
•
.NET Data Provider for Teradata Release Definition - [Release 12.00]
•
.NET Data Provider for Teradata Release Definition - [Release 12.00.01]
•
.NET Data Provider for Teradata Release Definition - [Release 13.00]
•
.NET Data Provider for Teradata Release Definition - [Release 13.01]
Note: .NET Data Provider for Teradata installation procedures have been included in this
document starting with release Teradata Tools and Utilities 13.00.
Step 1: Review Product Description, Dependencies and Restrictions
Review .Net Data Provider for Teradata Product Description
Microsoft® .NET Framework applications utilize .NET Data Providers for uniform and
standard access to data sources such as Teradata®. The .NET Data Provider for Teradata is the
data access component of the .NET Framework Class Library (FCL).
Review .Net Data Provider for Teradata Product Dependencies
.NET Data Provider for Teradata has no Teradata Tools and Utilities dependencies.
Review .Net Data Provider for Teradata Restrictions
The following restrictions apply to .NET Data Provider for Teradata. These restrictions are
also listed in the .NET Data Provider for Teradata Readme.txt file.
•
To run .NET Data Provider for Teradata requires the Full Trust permission set.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
45
Chapter 7: Installing .NET Data Provider for Teradata
Task 1: Install .NET Data Provider for Teradata
For additional information, refer to the articles on “Security in the .NET Framework” at
http://msdn2.microsoft.com/en-us/library/fkytk30f.aspx in MSDN.
Also, refer to “Administering Security Policy” at http://msdn2.microsoft.com/en-us/
library/wztcyd2e.aspx in MSDN.
•
There are outstanding side-by-side install and uninstall issues related to version 01.00.00,
01.01.00 and 01.02.00. The uninstall does not update the following registry key to the last
available version (for example version 01.01.00.00 after 01.02.00.00 is uninstalled):
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\.NETFramework\AssemblyFolders\
Teradata Data Provider
Therefore, .NET Data Provider for Teradata is not listed in the Add Reference dialog box.
•
The installation adds/creates a directory in Program Files on 32-bit systems, or in Program
Files (x86) on 64-bit operating systems.
•
The TdDataAdapter Configuration Wizard, in Microsoft Visual Studio 2005, does not
generate unique names for the Commands. It always generates SelectCommand,
InsertCommand, UpdateCommand and DeleteCommand names for the corresponding
instances of TdCommand class. In order to configure a second or subsequent
TdDataAdapter, the existing generated commands must be renamed to a different name
which does not conflict with the default generated command names. For instance
SelectCommand may be renamed to SelectCommand1.
•
TableAdapter Query Configuration Wizard, in Microsoft Visual Studio 2008, does not
generate correct Parameters for INSERT Query Type. This is a known Visual Studio 2008
limitation. See incident number 331845 at http://connect.microsoft.com/VisualStudio.
Step 2: Uninstall .NET Data Provider for Teradata
This section contains the procedure to uninstall a previous version of .NET Data Provider for
Teradata.
Procedure - Uninstall .NET Data Provider for Teradata
Follow this procedure to uninstall .NET Data Provider for Teradata:
46
1
Open Control Panel.
2
Start Add or Remove Programs.
3
In Add or Remove Programs, find .NET Data Provider for Teradata xx.xx.xx.xx and click
Change/Remove.
4
In the .NET Data Provider for Teradata - InstallShield Wizard, choose Remove and click
Next>.
5
In the Maintenance Complete dialog, click Finish.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 7: Installing .NET Data Provider for Teradata
Task 1: Install .NET Data Provider for Teradata
Step 3: Install Third-Party Dependencies
Product
Required Third-Party Software Installations
.NET Data Provider for Teradata 13.00.00
• Microsoft .NET Framework
Redistributable Package, version 2.0
Service Pack 1, or later
• (Optional feature) Microsoft Visual Studio
2005
• (Optional feature) Microsoft Visual Studio
2008
• (Optional feature) Microsoft SQL Server
Business Intelligence Development Studio
The following third-party dependencies must be installed for .NET Data Provider for
Teradata.
•
Microsoft .NET Framework Redistributable Package, version 2.0 Service Pack 1, or later
•
(Optional) Microsoft Visual Studio 2005 or Microsoft Visual Studio 2008 Integration
Feature
•
(Optional) Microsoft SQL Server Business Intelligence Development Studio
.Install Microsoft NET Framework 2.0
.NET Data Provider for Teradata 13.00.00 is dependent on Microsoft .NET Framework, which
must be installed on all computers running .NET Data Provider for Teradata.
Note: If .NET Framework is not installed prior to attempting to install .NET Data Provider
for Teradata, the .NET Data Provider for Teradata installation will abort and request that
.NET Framework be installed first, before continuing.
Procedure - Installing Microsoft .NET Framework Redistributable
Follow these steps to install the Microsoft .NET Framework Redistributable:
1
Go to http://msdn.microsoft.com/en-us/netframework/aa569263.aspx.
2
Select the .NET Framework Runtime Package for your client.
3
Download and Install the Microsoft .NET Framework runtime by following the Microsoft
recommended procedures.
Install Visual Studio 2005 or 2008 Integration Feature
Select the Visual Studio 2005 or 2008 Integration feature during the interactive installation of
.NET Data Provider for Teradata.
The Integration feature integrates:
Teradata Tools and Utilities Installation Guide for Microsoft Windows
47
Chapter 7: Installing .NET Data Provider for Teradata
Task 1: Install .NET Data Provider for Teradata
•
.NET Data Provider for Teradata schema collection into the Microsoft Visual Studio Server
Explorer. It provides access to Teradata Data Dictionary including Databases, Tables,
Views and Stored Procedures.
•
.NET Data Provider for Teradata help files into the Microsoft Visual Studio help
collections. It enables context sensitive help for all classes in Teradata.Client.Provider
namespace.
Install Publisher Policy
Select the Publisher Policy during the interactive installation of .NET Data Provider for
Teradata.
A publisher policy assembly configures the policy used when the .NET Framework runtime
binds to an assembly. The publisher policy assembly is installed into the GAC and is named
using the following naming convention:
policy.major_ver.minor_ver.Teradata.Client.Provider.dll
where: major_ver and minor_ver refer to the major and minor version of the previous version
of the .NET Data Provider for Teradata.
Therefore, if upgrading from .NET Data Provider for Teradata 01.02.00 to .NET Data Provider
for Teradata 13.00.00, and binding all existing applications to the 13.xx.xx version, the
publisher policy assembly policy.1.2.Teradata.Client.Provider.dll must be placed in the Global
Assembly Cache to redirect existing application built against .NET Data Provider for Teradata
01.02.00 to .NET Data Provider for Teradata 13.xx.xx.
•
If this is a new installation of .NET Data Provider for Teradata, and there are no other
applications installed or being installed which are dependent on an earlier version of .NET
Data Provider, uncheck Publisher Policy. (The default is Publisher Policy checked.)
•
If this is an upgrade of a previous installation of .NET Data Provider for Teradata, or there
are other applications installed or being installed which are dependent on an earlier
version of .NET Data Provider, leave Publisher Policy checked. (The default is Publisher
Policy checked.)
Step 4: Download .NET Data Provider for Teradata
.NET Data Provider for Teradata 13.xx.xx installation package is located on the Teradata
Download Center located at:
http://www.teradata.com
Procedure - Downloading .NET Data Provider from the Teradata Download Center
Follow this procedure to download .NET Data Provider for Teradata 13.xx.xx from the
Teradata Download Center.
48
1
Create a “temporary” folder where the .NET Data Provider for Teradata EXE file can be
downloaded.
2
Go to: http://www.teradata.com.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 7: Installing .NET Data Provider for Teradata
Task 1: Install .NET Data Provider for Teradata
3
Choose Downloads in the Support & Downloads menu.
4
Choose .NET Data Provider.
5
Click the “.NET Data Provider for Teradata” version that is correct for the client system.
6
Click the filename to download. A description of the software appears.
Note: The following steps download the readme.txt file.
7
Click on the download .txt file in Download Files.
8
Click on Download tdnetdp__windows_indep.13.xx.xx.xx.txt in Download Files.
9
Click Save.
10 Navigate to the “temporary” folder created in step 1, then click Save to download the
.NET Data Provider for Teradata .txt file.
tdnetdp__windows_indep.13.xx.xx.xx.txt - the .NET Data Provider for Teradata readme file
Note: The following steps download the zipped executable files.
11 Click on the download ZIP file in Download Files.
12 Read the License Agreement and click I Accept.
13 Click on Download tdnetdp__windows_indep.13.xx.xx.xx.zip in Download Files.
14 Click Save.
15 Navigate to the “temporary” folder created in step 1, then click Save to download the
.NET Data Provider for Teradata ZIP file.
16 Extract files from the ZIP file to the folder. The files must be a minimum of the version
number shown:
•
tdnetdp__windows_indep.13.xx.xx.xx.exe - the .NET Data Provider for Teradata
executable file
Step 5: Install .NET Data Provider for Teradata
Previously, the .NET Data Provider for Teradata installation package must have been
downloaded. This procedure installs the .NET Data Provider for Teradata that was
downloaded.
Procedure - Installing .NET Data Provider for Teradata Interactively
Follow this procedure to install .NET Data Provider for Teradata interactively.
1
Navigate to the “temporary” folder created in Step 4: Download .NET Data Provider for
Teradata and locate the tdnetdp__windows_indep.13.xx.xx.xx.exe executable file.
2
Run the tdnetdp__windows_indep.13.xx.xx.xx.exe executable file.
3
If installing on Windows Vista, the User Account Control dialog appears when the
tdnetdp__windows_indep.13.00.00.00.exe executable file is run. If it does, click Allow: I
trust this program. I know where it's from or I've used it before.
4
In the Choose Setup Language dialog, select the Language to use, then click OK.
5
When the Welcome screen appears, click Next>.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
49
Chapter 7: Installing .NET Data Provider for Teradata
Task 1: Install .NET Data Provider for Teradata
6
In the Select Features dialog, select the features to install, then click Next>.
The Select Features dialog box allows selection or unselection of:
•
Microsoft Visual Studio 2005 Integration feature
Note: If Microsoft Visual Studio 2005 or Microsoft SQL Server 2005 is installed on the
system, and the Visual Studio 2005 Integration feature is selected, then the .NET Data
Provider for Teradata product is integrated into Microsoft Visual Studio 2005, or
Microsoft SQL Server Business Intelligence Development Studio, or both.
By default, this feature is selected for installation. If the Visual Studios 2005 Integration
is not required, unselect this feature to reduce the installation time.
•
Microsoft Visual Studio 2008 Integration feature
Note: If Microsoft Visual Studio 2008 or Microsoft SQL Server 2008 is installed on the
system, and the Visual Studio 2008 Integration feature is selected, then the .NET Data
Provider for Teradata product is integrated into Microsoft Visual Studio 2008, or
Microsoft SQL Server Business Intelligence Development Studio, or both.
By default, this feature is selected for installation. If the Visual Studios 2008 Integration
is not required, unselect this feature to reduce the installation time.
•
Publisher Policy feature
Note: A publisher policy assembly configures the policy used when the .NET
Framework runtime binds to an assembly. The publisher policy assembly is installed
into the GAC. If upgrading from .NET Data Provider for Teradata version 01.02.00 to
.NET Data Provider for Teradata 13.xx.xx, and binding all existing applications to the
13.00.00 version, the publisher policy assembly policy.1.2.Teradata.Client.Provider.dll
must be placed in the Global Assembly Cache to redirect an existing application built
against .NET Data Provider for Teradata 01.02.00 to .NET Data Provider for Teradata
13.00.00.
•
If this is a new installation of .NET Data Provider for Teradata, and there are no
other applications installed or being installed which are dependent on an earlier
version of .NET Data Provider, uncheck Publisher Policy. (The default is Publisher
Policy checked.)
•
If this is an upgrade of a previous installation of .NET Data Provider for Teradata,
or there are other applications installed or being installed which are dependent on
an earlier version of .NET Data Provider, leave Publisher Policy checked. (The
default is Publisher Policy checked.)
7
In the Choose Destination Location screen, choose a destination folder and click Next>.
8
In the Select Program Folder dialog, click Next>.
9
In the Start Copying Files dialog, click Next> to start copying files.
10 If installing Visual Studio 2005 Integration on Windows Vista, and the Program
Compatibility Assistant dialog appears, click Run program to continue the installation.
11 In the InstallShield Wizard Complete screen, select “Yes, I want to view the readme file now.”
to display the readme file.
12 Click Finish to complete the installation.
50
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 7: Installing .NET Data Provider for Teradata
Task 1: Install .NET Data Provider for Teradata
Step 6: Configure .NETteragss
.NETteragss is installed with .NET Data Provider for Teradata. For information on configuring
.NETteragss, see “Configuring .NETteragss” in the .NET Data Provider for Teradata Help file.
Also, see the Teradata Database Security Administration manual.
Step 7: Verify Installation and Connectivity to the Teradata Database
.NET Data Provider for Teradata installs an unsupported ad-hoc query tool named
NQUERY.exe. It can be used to verify installation and connectivity to Teradata Database.
Procedure - Verify the Installation of .NET Data Provider for Teradata and Connectivity to
the Teradata Database
Follow this procedure to verify the installation of .NET Data Provider for Teradata and the
connectivity to the Teradata Database.
1
Run <Installation Directory>\13.xx.xx.xx\Samples\Bin\NQuery.exe.
2
From the menu bar, select Connection followed by Connect… to display the Connect
dialog.
3
Select .NET Data Provider for Teradata for the Data Provider.
4
Enter the connection string as:
Data Source = DbcName;User Id = X;Password=Y;
where:
•
DbcName is the Teradata system name
•
X is the user name/ID
•
Y is the password
5
Click Connect.
6
Enter Select Date in the SQL Command box and click Execute to display the Teradata
Database system date in the Result window.
7
From the menu bar, select Connection followed by Disconnect.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
51
Chapter 7: Installing .NET Data Provider for Teradata
Task 1: Install .NET Data Provider for Teradata
52
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 8
Installing Teradata Meta Data Services
on Windows
Installation, configuration, dependencies and reference information for Teradata Meta Data
Services on Windows operating systems are described in this section.
Distribution Media
Whenever installing Teradata Meta Data Services, always compare the versions available on
the CD media and the Teradata Software Server. The software server will contain the most
recent point release of a software product.
•
“Installing from CD Media” - Teradata Tools and Utilities installs on a single-user from
the CD media in the Teradata Tools and Utilities Installation Kit. The CDs contain
installation packages for the current release.
•
“Installing from the Teradata Software Server” - The server contains updated software
packages which should be installed in lieu of lower version software contained on the CD
media.
Task 1: Review MDS Product Information
Step 1: Review Teradata Meta Data Services Documentation
Click on the following link to display a list of archived Teradata Meta Data Services
documentation:
Teradata Meta Data Services documentation
Step 2: Review Teradata Meta Data Services Product Description
Teradata Meta Data Services (MDS) provides an infrastructure for managing Teradata data
warehouse metadata and for creating tools to interchange metadata with external operational
systems, Extraction Transformation and Load (ETL) tools, Business Intelligence tools,
Database Modeling tools, and any other metadata sources.
Step 3: Review Teradata MDS Overview
The following figure illustrates a typical Teradata MDS configuration consisting of:
Teradata Tools and Utilities Installation Guide for Microsoft Windows
53
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 1: Review MDS Product Information
•
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 MDS repository
Client Web Browser
*
Workstation/Laptop/Etc
with Supported Browsers
ASP
Page
HTML
Page
HTTP
Request
MetaManager/
MetaBrowse
(Windows PC)
*
Metasurf
Intranet
or
Internet
Active
Server
Engine
MDS
Com
Interface
+
Engine
MDS
Engine
HTML
Page
ODBC
ODBC
Teradata
Database
MDS
Repository
3118B001
Windows
Web
Server
* MDS Installed
Teradata Server
A system may also contain one or more workstations that will be used to develop or run MDS
applications and, if the Teradata MDS Automatic DIM Update feature is to be installed, a
designated DIM Update server.
Step 4: Review Installation Prerequisites
The following table lists software and hardware required before installing Teradata Meta Data
Services:
54
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 1: Review MDS Product Information
Text Box
Description
Teradata Database System
The MDS repository is stored in a Teradata Database
System V2R6.1.x or greater.
The minimum size of the database for a production
MDS repository is 50MB.
Note: A versioned repository will require more space
than a non-versioned repository.
Teradata User Account
Because the MDS repository is stored in a Teradata
Database, a Teradata user account is required to
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 MDS
repository. Unless the metaviews utility is used, these
users must have SELECT privileges to the DBC
tables.
Note: If Teradata Meta Data Services is being
installed on the MDS administrator’s workstation,
grant the user all privileges to the MDS database.
ODBC Driver for Teradata (ODBC) and
Data Source Name (DSN)
All of the machines running Teradata MDS software
must have the appropriate Teradata ODBC driver
installed and configured. ODBC 12.00.00 and above
is required. For best results use the ODBC driver for
Teradata version that matches the Teradata Meta
Data Services version being used. Compatible
versions of Shared ICU Libraries for Teradata and
Teradata Generic Security Services must also be
installed.
Create a System DSN for the Teradata Database
Systems that will contain the MDS repository.
Take the following actions when configuring the
ODBC DSN on Windows machines:
• 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 either a
Windows XP, Windows Server 2008, Windows Server
2003, Windows 2000, Windows Vista, or Windows 7
system.
Hardware requirements are:
• Pentium PC or greater with at least 256 MB RAM
• Minimum of 50 MB disk space
Teradata Tools and Utilities Installation Guide for Microsoft Windows
55
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 1: Review MDS Product Information
Text Box
Description
An 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, Windows 2000/2003 Server with Microsoft IIS
5.0, 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, Windows 2000, 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.
Step 5: Review Software Components to Install
There are four different types of Teradata MDS software packages that perform different tasks
and install on different hardware and software environments.
Text Box
Description
MDS Core Files
The core files are the MDS executables and DLLs. The
core files include the MDS MetaBrowse and MDS
MetaManager programs. These files are required on
all systems running an MDS application or
developing MDS applications.
Installed: The MDS core files can be installed on
either Windows or Linux based systems.
MDS Development Kit
The MDS development kit contains additional files
needed to develop MDS applications. MDS provides
a set of application programming interfaces (APIs)
for third-party applications to store, administer, and
retrieve metadata from the MDS repository. The
development kit also includes sample applications.
Installed: The MDS development kit is installed on
the workstation of any user who will be working with
the MDS APIs. The MDS development kit files can be
installed on either Windows or Linux based systems.
MDS MetaSurf Files
MetaSurf provides HTML files and ASP scripts that
enable users to browse and search the MDS
repository using a Web application.
Installed: The MetaSurf files are installed on the ASP
compliant web server.
56
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 2: Uninstall Teradata MDS on Windows
Text Box
Description
MDS DIM Update Files
Installed: If setting up and using the Teradata MDS
Automatic DIM Update feature, install executable
files for the MDS DDL Gateway and the MDS Action
Processor on the designated DIM Update Server.
The MDS DIM Update files can be installed on either
Windows, or Linux based systems.
Task 2: Uninstall Teradata MDS on Windows
[OPTIONAL] Decide whether to uninstall an existing version of MDS. If an older version of
the MDS software already exists on a machine running Windows, it is not required to
uninstall the older version before installing the new version of MDS.
Perform the following procedure if you decide to uninstall an existing version of Teradata
MDS from a Windows client.
Procedure - Uninstalling Teradata MDS
1
To remove the software, in Start, select Control Panel and then Add or Remove Programs.
2
Select the Teradata Meta Data Services program to remove, then click Remove.
3
Answer any prompts that appear and then click Finish in the Complete screen.
Task 3: Install Teradata MDS on Windows
Workstations and Servers
Use this procedure for each Windows workstation or server where MDS software is to be
installed.
Procedure - To install Teradata MDS on Windows Workstations and Servers
1
Close all Windows programs before installing MDS.
2
Start the installation using a standard Windows executable setup file (setup.exe). This can
be found on the Teradata Meta Data Services Installation CD, or you may be directed to
access the setup from another location.
The setup may be automatically launched from the CD, or you may have to double-click
on the setup.exe file.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
57
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 3: Install Teradata MDS on Windows Workstations and Servers
3
In the Choose Setup Language dialog, select the installation language.
4
Click OK to accept the default language, or select another language.
The Teradata Meta Data Services splash screen appears briefly and then the Welcome
screen appears.
58
5
Click Next to continue the installation, an Important Virus Message appears.
6
Read the Important Virus Message message, then click OK to continue the installation. The
Welcome screen appears.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 3: Install Teradata MDS on Windows Workstations and Servers
7
Click Next to continue the installation, and the Choose Destination Location window
appears.
This dialog prompts for the destination location, where to install the MDS files.
The default location provided is either:
8
•
Location where MDS was previously installed
•
Program Files folder on the boot drive. If the boot drive is C: the location will be
C:\Program Files\Teradata\Teradata Meta Data Services.
Click Browse to choose a different location, and then click Next to accept the new or
default location.
The Choose MDS Log File Location dialog appears, it asks where to store the MDS log files.
The default location is: C:\mdslog.
9
Click Next to accept the default location, or Browse to choose a different location.
The Select Features dialog appears.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
59
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 3: Install Teradata MDS on Windows Workstations and Servers
10 From this dialog select the components to install.
Note: Teradata Meta Data Services Core Files component is required and cannot be
cleared.
11 Choose whether to install the Development Kit, the MetaSurf Web application, or DIM
Update files.
When Meta Data 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 will exchange information with MDS.
Note: To develop Unicode based programs with MDS, the options of the Meta Data
Development Kit must be changed.
60
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 3: Install Teradata MDS on Windows Workstations and Servers
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 MDS 13.10.
Warning:
MetaSurf files can be customized. Therefore, subsequent installations of 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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
61
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 3: Install Teradata MDS on Windows Workstations and Servers
Warning:
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.
Warning:
If 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 occured during the datamove process - 115
Component: MDSCore
FileGroups:basic
File:<installdir>/metasurf
Warning:
During a reinstallation, if new MetaSurf files are not installed, it is because 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 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. For more information on the Automatic DIM Update feature
refer to “Chapter 9 Installing Automatic DIM Update” on page 73.
12 Click Next to continue the installation.
Whether using an existing repository or creating one, the Meta Data Services Repository
Connection Information dialog asks for details about the database connection.
62
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 3: Install Teradata MDS on Windows Workstations and Servers
13 Enter the information MDS will use to connect to the MDS repository. This information is
saved in the Windows registry.
Text Box
Required/
Optional
Description
Data Source Name
Required
Enter the DSN to use to connect to MDS repository.
Note: The DSN specified must be configured as a System DSN in ODBC Administrator.
User Name
Required
Enter the user name MDS will use to log on to the Teradata Database. The User must
have permissions to access the MDS database tables.
Database Password
Required
Enter the password that MDS will use to log on to the Teradata Database.
Database Name
Optional
Enter the name of the Teradata Database containing the MDS repository
Note: 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.
14 Click Next to continue, the Select Program dialog appears.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
63
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 3: Install Teradata MDS on Windows Workstations and Servers
15 Choose the name of the Windows program folder to store the Teradata Meta Data Services
start-up shortcuts, click Next.
Note: The default folder is Teradata Meta Data Services.
The Start Copying dialog containing a summary of the installation selections appears.
16 Review the summary of the installation selections. Then click Back and change the
selections, or click Next to begin copying the installation files.
An indication of the progress of the installation appears when the files begin copying.
When the Setup program has finished installing Teradata Meta Data Services, the
InstallShield Wizard Complete dialog appears.
64
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 4: Set the MDS Configuration Parameters
17 Select the Yes, I want to view the readme file now check box to view the Readme.txt file
before clicking Finish to complete the setup on this workstation or server.
18 If performing additional MDS installations, repeat this process for each workstation or
server.
19 If not using the Automatic DIM Update feature, continue to post installation tasks.
20 If using the Automatic DIM Update feature, refer to “Chapter 9 Installing Automatic DIM
Update” on page 73 to perform additional installation tasks.
21 If you have installed MetaSurf, refer to “Task 7: Create A Virtual Directory or Web
Application.”
Task 4: Set the MDS Configuration Parameters
After installing the appropriate software on a workstation or server, set the MDS configuration
parameters for each workstation or server.
Step 1: Configure Windows Workstations or Servers
On Windows, the local MDS configuration parameters are stored in the Windows Registry.
Procedure - Configure Windows Workstations or Servers
1
To change the settings, log onto the Windows system as a user who has permission to
update the Windows Registry.
Note: On Windows, users who are only members of the Guests group will not be able to
change the settings.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
65
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 4: Set the MDS Configuration Parameters
2
Click MDS Configuration from the Windows Control Panel to display the MDS Configuration
tab of the Teradata Meta Data Services Configuration dialog.
3
Click Start>Programs>Teradata Meta Data Services>MetaManager to display The Teradata
Meta Data Services MetaManager Logon dialog.
4
Then click Configure.
Note: If the default name was not selected as during installation, find the specified name
for the MDS program group to launch MetaManager.
For more information, see the following:
•
Set the Database Connection Information
•
Setting Logging and Trace Levels
•
Log Files Manager
Set the Database Connection Information
During installation, a prompt to specify the MDS Database connection information was
made. This information resides in the local client system registry files, not in the repository.
The MDS engine uses this information to connect to the MDS repository.
The settings can be changed before making the connection.
66
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 4: Set the MDS Configuration Parameters
Procedure - Set the Database Connection Information
1
In the Teradata Meta Data Services Configuration dialog Data Source Name box, enter the
ODBC system Data Source Name (DSN) to use to connect to the Teradata Database
System containing the MDS repository.
2
In the Database User Name box enter the user name that MDS will use to log onto the
Teradata Database System. The user must have permissions to access the MDS database
tables.
3
If the MDS users on the local system are browsing the MDS repository, the user needs
SELECT privileges to the database containing the MDS repository.
4
If any user loads or updates the MDS repository, INSERT, UPDATE and DELETE
privileges are also required.
5
To create an Application Information Metamodel, CREATE TABLE privileges are needed.
6
If this user will be creating the MDS repository, GRANT ALL PRIVILEGES to the user on
the database.
7
In the Database User Password box enter the password that MDS will use to log onto the
Teradata Database System.
8
In the Database Name box enter the name of the Teradata Database within the Teradata
Database System where the MDS repository is stored. This can be the same as the Database
User Name.
If omitted, the Database Name will default to the default Database Name in the ODBC
DSN for that Teradata Database System where the database is housed.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
67
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 4: Set the MDS Configuration Parameters
Note: If the DSN does not have a default Database Name, the connection will be made to the
default database of the Database User.
Changes to these settings are saved in the registry when by clicking Apply or OK after making
changes.
Note: If 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 Trace Levels
From the Teradata Meta Data Services Configuration dialog box, choose the Logging tab to see
the log options.
The logging and tracing levels only apply to the local system, where an MDS application is
running. They can be changed at any time and changes are written to the local system’s
registry immediately.
MDS applications only read the log and trace level settings on start up, therefore restart the
application for the new settings to take effect. To change the settings for MetaSurf, restart the
web server.
Logging Level
This choice controls the amount of log messages written to the MDS log file. The default is
Warning.
Level
Description
Critical
Logs Critical messages
Error
Logs Error and Critical messages
Warning
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
Tracing Level
This choice controls the type of messages traced and written to the standard error output. The
Tracing Level and error output are used primarily when writing an application using the MDS
APIs. The default is Disable.
68
Level
Description
Disable
No messages are traced.
Critical
Traces Critical messages
Error
Traces Error and Critical messages
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 5: Create the Meta Data Repository
Level
Description
Warning
Traces Warning, Error and Critical messages
Information
Traces Information, Warning, Error and Critical messages
All
Traces Debug, Information, Warning, Error and Critical messages
Log Filename
The Log filename is read-only. The filename is meta_yyyymmdd.txt (where yyyy = year, mm =
month, dd = day). The date contained in the log filename indicates the date the log entries
were written.
MDS creates a new log file each day. The log does not wrap. Old log files should be deleted by
the MDS Administrator.
Log Files Manager
Click Log Files Manager to see previously generated log files - their names, and file sizes in
bytes.
View or delete the logs in this window.
Task 5: Create the Meta Data Repository
The following instructions assume that the system does not have an existing MDS repository
created from an earlier version of MDS. If you have such a repository refer to “Task 6: Migrate
the Meta Data Repository” for information on migrating the existing MDS repository to the
current software version.
After installing the MDS software, the next step is to create the MDS repository.
Step 1: Create the Repository from a Windows Workstation
Use this procedures to create the MDS Repository from a Windows workstation.
Procedure - Creating the MDS Repository
1
Click Start>Programs.
2
Click Teradata Meta Data Services (or the Program Group name specified during
installation).
3
Click Create MDS Repository.
•
Click Create without versioning to create a repository without versioning enabled. This
is the default choice. This runs the metacreate program and creates an MDS repository
without versioning support.
•
Click Create with versioning to create a repository with versioning enabled. This runs
the metacreate program and creates an MDS repository with versioning support.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
69
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 6: Migrate the Meta Data Repository
Task 6: Migrate the Meta Data Repository
The following procedure assumes that the system has an existing MDS repository created
from an earlier version of MDS. If the system does not have such a repository refer to “Task 5:
Create the Meta Data Repository” for information on creating an MDS repository.
Procedure - Upgrading from an Earlier Version of Teradata
If also upgrading from an earlier version of Teradata, complete the following tasks before
upgrading and migrating the MDS repository:
1
Save the database containing the MDS repository.
2
Upgrade the Teradata Database version.
3
Restore the MDS repository.
4
Install MDS 13.10 software components.
After installing the MDS software, migrate the existing MDS repository to the current
software version.
Step 1: Migrate the MDS Repository on a Windows Workstation
Perform the following steps to migrate the MDS Repository from a Windows workstation.
Procedure - To migrate the MDS Repository
1
Click Start>Programs.
2
Click Teradata Meta Data Services (or the Program Group name specified during
installation).
3
Click Migrate MDS Repository.
Click Migrate without versioning to invoke the metamigrate program in an MS-DOS
window and migrate without versioning enabled. This is the default choice.
Click Migrate with versioning to invoke the metamigrate program in an MS-DOS window
and migrate a repository with versioning enabled.
Warning:
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.
4
Enter the MDS Administrator username and password (unless changed, it is metasu).
Migrating a repository takes several minutes.
70
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 7: Create A Virtual Directory or Web Application
Task 7: Create A Virtual Directory or Web
Application
After installation of MetaSurf, a virtual directory or web application to MetaSurf on the web
server should be defined. See section 9.0 of the Teradata Meta Data Services Readme.txt file for
Web Server configuration information.
Procedure - Creating a Virtual Directory
1
When creating the virtual directory or web application, select an alias name for MetaSurf
for example:
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 MDS configuration, web
services may need to be restarted for the change to take effect.
2
For complete information on setting up the 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.
3
Alter the appearance of the MetaSurf Web pages by:
•
modifying the style sheets used
•
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.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
71
Chapter 8: Installing Teradata Meta Data Services on Windows
Task 7: Create A Virtual Directory or Web Application
72
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 9
Installing Automatic DIM Update
This section describes the Automatic DIM Update feature for Teradata Meta Data Services.
Task 1: Review Automatic DIM Update
This section contains general information on the Automatic DIM Update feature, information
on software installation, configuration tasks required to implement and administer the
feature.
Because the Teradata Database metadata is a central part of the Teradata MDS repository, it is
vital to the use of 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 will
dynamically keep the MDS repository synchronized with the Teradata Database Systems it
describes.
Step 1: Review the Automatic DIM Update Process
The following figure illustrates the processes supporting Automatic DIM updates.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
73
Chapter 9: Installing Automatic DIM Update
Task 1: Review Automatic DIM Update
Feature
Description
Relay Services Gateway (RSG)
The RSG is a Teradata VPROC that relays messages
between Teradata and the MDS DDL Gateway.
Whenever a Teradata Database System processes a Data
Definition Language (DDL) statement, it sends the DDL
to the RSG, which sends it on to the MDS DDL Gateway.
The DDL Gateway then updates the metadata in the
MDS repository. An example of a DDL is:
create table mytable (c1 int);
Every Teradata node of the Teradata Database System
must have an RSG VPROC running.
The RSG communicates via TCP/IP with the MDS DDL
Gateway.
DDL Gateway
The DDL Gateway consists of one client, one server, and
one or more integrity server processes that keep the
metadata in the MDS repository synchronized with
Teradata. MDS can track changes to multiple Teradata
systems. The 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 DDL Gateway can be installed on an application
node of the Teradata system or on a separate Windows
or Linux box. Only one instance of the DDL Gateway is
allowed.
74
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 9: Installing Automatic DIM Update
Task 1: Review Automatic DIM Update
Feature
Description
MDS Action Processor
The MDS Action Processor is responsible for polling the
Audit Log for expired entries and purging the expired
entries. The MDS Action Processor is also responsible
for sending messages to the MDS DDL Gateway to
initiate scheduled recovery.
The MDS Action Processor runs on Windows or Linux
and only one MDS Action Processor can be run.
The Action Poll Rate defined in the MetaManager
System-Wide Parameters defines the frequency that the
MDS Action Processor will reread the MDS system
settings to pick up changes to the Audit Flag, Audit Trail
Expiration Days, and DIM Update Recovery Schedule
for each Teradata 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 MDS Action Processor will poll the 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 MDS for each
Teradata Database System. The MDS Action Processor
will monitor the schedule times for each Teradata system
and send a message to the 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 MDS
repository, an MDS Recovery Table must exist on each of
the Teradata Database Systems.
Teradata Database Systems automatically contain an
MDS Gateway MDS Recovery Table. The table has a
fixed name (mdsrecoverytbl) and location (DBC).
Database Connection Information
When creating a System with Automatic DIM Updates
enabled, a DSN, user name and password for the DDL
Gateway to use to connect to the system are specified in
MetaManager.
The Gateway Server process uses these settings to resync
a database during recovery and to access the MDS
Recovery Table. The Gateway Integrity Servers use these
settings to connect to the system to get information
from the DBC tables.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
75
Chapter 9: Installing Automatic DIM Update
Task 1: Review Automatic DIM Update
Feature
Description
DDL Gateway User Accounts
The DDL Gateway uses the Teradata user names
specified in MetaManager's system configuration to
connect to Teradata systems.
The DDL Gateway on Windows systems runs as a
service. A service can run as the LocalSystem Account or
as a specified account name and password. If the MDS
repository Database Configuration is configured for
Teradata Single Sign On (SSO) where no username and
password is specified, then the DDL Gateway Service
MUST NOT be configured to run with the LocalSystem
Account. If the 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.
Step 2: Review Out of Sync Recovery
The MDS repository can be out of sync with a Teradata Database System for a number of
reasons:
•
A Teradata Database System, RSG and/or MDS DDL Gateway reset occurs.
•
An error occurs and an Integrity Server cannot commit a transaction to the repository.
•
The 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 MDS but is writing the
database names to the 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.
76
Feature
Description
Teradata Database System
When the MDS DDL Gateway is down, the Teradata
Database System will process DDL statements but will
write the names of all “Affected” databases to the MDS
Recovery Table. There is one MDS Recovery Table per
Teradata Database System. When the MDS DDL
Gateway Server comes up, if the Recovery on Startup
flag is checked, it will read the MDS Recovery Table and
resynchronize the repository for each database name
listed in the table.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 9: Installing Automatic DIM Update
Task 1: Review Automatic DIM Update
Feature
Description
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 MDS DDL Gateway has gone down or
receives a reset message from the MDS DDL Gateway
Server, the RSG will abort the in-progress transactions
with the Teradata Database System.
DDL Gateway Server
DDL Gateway Server
The MDS DDL Gateway Server will keep track of the
database names of all DDL transactions that it has
received messages for. It will track the transaction in a
backlog list and in a log file. The log will be combined
with the MDS Recovery Table to resync the repository.
Only databases that are out-of-sync will be resynced
during recovery.
The DDL Gateway Server performs recovery:
• On startup of the DDL Gateway. On startup, the
Gateway Server looks in the MDS Recovery Table and
in its own log to determine which databases need
recovery. If the Teradata Database System is
configured in MDS to have the “Recovery On
Startup” flag enabled, the Gateway will begin
recovery for that system. If the flag is not set, recovery
will be deferred until the scheduled time.
• When the DDL Gateway receives a “Recover now”
message from the MDS Action Processor. Scheduled
recovery will only occur once per day for each
Teradata Database System based on the schedule
configured for that system in MDS. The schedule
configuration also specifies the days of the week to
perform scheduled recovery.
The Gateway Server performs the following steps
when performing recovery:
• The Gateway Server sends a message to the
Teradata Database to stop sending DDLs to RSG
and to log “Affected” databases in the MDS
Recovery Table.
• The Gateway Server reads and deletes MDS
Recovery Table entries, reads the backlog list and
compiles a list of database names to resync.
• Calls the metaload utility to resync each database
name.
• Reads and deletes the MDS Recovery Table again
to resync databases that may have been affected by
DDLs during the resync process.
• Sends a message to the Teradata Database to start
sending DDLs to RSG.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
77
Chapter 9: Installing Automatic DIM Update
Task 2: Configure Automatic DIM Update Software
Task 2: Configure Automatic DIM Update
Software
If the Automatic DIM Update feature is desired, there are additional configuration tasks that
must be performed before using this feature.
You will need to install and configure software on your designated Automatic DIM Update
Server. In addition software must be installed or configured on TPA nodes.
Step 1: Configure Windows Servers
If the designated DIM Update Server is a Windows machine, the configuration tasks are as
follows:
•
Install DIM Update Files on the DIM Update Server
•
Configure the RSG VProcs on TPA nodes
When the DIM Update files are installed on the DIM Update Server, proceed to Task 4: Install
and Configure RSG.
Task 3: Install DIM Update Server Software
(Windows)
The designated DIM Update Server must already have the MDS Core software files installed
before continuing.
If the DIM Update files are installed on a Windows system which doesn't also have Teradata/
RSG installed, update the services file manually. The services file is found in
C:\WINDOWS\system32\drivers\etc. The following two lines must be added:
RSiMsg
TxServer
56970/tcp
56969/tcp
# RSG Server
# MDS Gateway Server
Their order or position in the file doesn't matter.
Note: If these lines are not added, the MDS 13.10 DDL Gateway may continuously recycle
itself. The DDL Gateway will rapidly open and close virtual circuits each time it recycles.
Teradata Gateway keeps its end of the virtual circuits (sessions) open for a user specified time.
Eventually all Teradata virtual circuits may be exhausted.
Note: The Teradata Meta Data Services MDS installation code is fixed in MDS 13.10.01.
When MDS is installed on Windows, these lines are now automatically added to the services
file. When MDS is installed on Linux, these lines are already automatically added to the
services file.
78
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 9: Installing Automatic DIM Update
Task 4: Install and Configure RSG
Task 4: Install and Configure RSG
Every node of every Teradata Database System that is to be loaded into the MDS repository
and tracked with the Automatic DIM Update feature must have RSG installed and RSG vprocs
configured and running.
Under Windows, 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 MDS DDL Gateway is installed and
•
which node is the RSG master node
Creating and configuring RSG vprocs is required.
Step 1: Install and Configure RSG on Windows
Procedure - Install and Configure RSG on Windows
1
Use the PUT utility to add the RSG vprocs. The services file will be 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
partition 19.
2
Edit each node’s RSG configuration file, <tdconfig directory>\RSG\rsg.cfg, to indicate
where the 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 at the next TPA reset, the old RSG log file will be removed and a
new log file created.
If the MDSGWYNODE or the RSGMASTERNODE value is NULL, RSG will keep trying
to read the RSG configuration file. It will sleep between tries.
3
If the Teradata tdinfo utility indicates that the RSG vproc is not online, run the Teradata
vprocmanager utility to set it offline and then online as follows:
set xxxx offline
set xxxx online
Where xxxx is the ID of the vproc.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
79
Chapter 9: Installing Automatic DIM Update
Task 5: Configure Automatic DIM Update in MetaManager
Repeat these steps for each RSG vproc.
4
Run the dbscontrol utility and turn on the “MDS is Enabled” flag:
modify general 38=TRUE
write
quit
5
Restart the Teradata Database.
Step 2: Start/Stop the RSG
RSG starts automatically with the Teradata Database if the “MDS is Enabled” flag is set in
dbscontrol.
To validate that the “MDS is Enabled” flag is set, run the dbscontrol utility. Display the “MDS
is Enabled” flag with:
display general
If DEBUGTRACE is set to ON in the RSG configuration file, full RSG logging will take place.
If it is set to OFF, then minimal logging occurs. The REPLACE option will replace the old log
file and start a new one. On Windows, the RSG error log files are located in <tdconfig
directory>\RSG. There is one set of files per node.
Procedure - Putting the RSG vproc online Windows
1
If the tdinfo utility on Windows indicates that the RSG vproc is not online, run the
vprocmanager utility to set it online as follows:
set xxxx online
where xxxx is the ID of the RSG vproc on one TPA node. Repeat for the other TPA nodes.
The RSG vproc IDs are 9215, 9214, 9213, and so forth.
The RSG will be stopped when the Teradata Database is stopped.
Task 5: Configure Automatic DIM Update in
MetaManager
Use MetaManager to enable Automatic DIM Update. The steps to be performed are:
80
1
Add a Teradata Database System.
2
Add all Teradata nodes to the Teradata Database System.
3
Load databases.
4
Enable DIM Update and optionally setting the Recovery on Startup flag, and recovery
schedule.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 9: Installing Automatic DIM Update
Task 5: Configure Automatic DIM Update in MetaManager
Step 1: Add a Teradata Database System
For details on this, see, “Administer MDS with MetaManager” of the Teradata Meta Data
Administration Guide.
Step 2: Add Teradata Nodes to a Teradata Database System
Configure Nodes
The Automatic DIM Update feature requires that Teradata nodes on the Teradata Database
System be configured.
Add a Node
Procedure - Adding a Node
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. In the example shown, the system’s name is “simca.”
2
Click System>Add Node. The Add Node dialog appears.
3
Type in the node name, choose the node status, and click OK.
The 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. The node names must
be unique within the enterprise, not just within the Teradata Database System.
4
A request is made to add another node. When you are finished adding nodes, they will
appear in MetaManager.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
81
Chapter 9: Installing Automatic DIM Update
Task 5: Configure Automatic DIM Update in MetaManager
Edit a Node in MetaManager
Procedure - Editing a Node in MetaManager
1
In MetaManager, choose the node to edit, then right-click on it to display the shortcut
menu.
2
Click Edit, and an Edit node dialog box will appear.
3
The node status can be changed to Up or Down.
The status of the node should be set Down if the node on the Teradata Database System is to
be removed for an extended period. This will prevent the MDS DDL Gateway from sending
messages to the RSG on the node when it is unavailable.
Step 3: Load Databases
MDS loads data dictionary information for each of the selected databases into the MDS
repository. The actual data in the databases’ tables is not loaded.
The option used to load databases into the MDS repository determines what 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.
82
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 9: Installing Automatic DIM Update
Task 5: Configure Automatic DIM Update in MetaManager
Load...
Description
All Databases
If “All” databases is chosen, the DDL Gateway will
automatically add new databases and users that are
created in the Teradata Database System to the MDS
repository. In other words, “All” indicates that the MDS
repository will contain all databases in the Teradata
Database System.
Selected Databases
If “Selected” databases is chosen, the DDL Gateway will
NOT add new databases and users that are created in the
Teradata Database System to the MDS repository. The
DDL Gateway will maintain only those databases
selectively loaded into the 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
If “All but Selected” databases is chosen – the DDL
Gateway will automatically add new databases and users
that are created in the Teradata Database System to the
MDS repository. It, however, 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 are later unloaded are
considered to be databases that are excluded.
For all other DDLs, the DDL Gateway will update the repository for loaded databases and will
ignore DDL for databases that are not loaded into the repository.
If databases are not loaded for a Teradata Database System, the MDS DDL Gateway will not
track that system even if Automatic DIM Update is enabled for the system.
Before enabling DIM Update, load all databases to be maintained. If there is a lengthy time
between the initial load of the databases and when DIM Update is enabled, resync all
databases before enabling DIM Update.
For details on this, see “Resynchronize Databases” in “Administer MDS with MetaManager”
in the Teradata Meta Data Services Administrator Guide.
Step 4: Enable Automatic DIM Update
Procedure - Enabling the Automatic DIM Update
1
In MetaManager, choose the system which will have Automatic DIM Update enabled, then
right-click it.
2
Click DIM Update, and the DIM Update dialog appears.
3
Select the Enable DIM Update check box.
4
Click OK to exit the dialog. From this dialog select the Recovery on Startup check box or
define the recovery schedule by clicking Schedule (both are optional).
Teradata Tools and Utilities Installation Guide for Microsoft Windows
83
Chapter 9: Installing Automatic DIM Update
Task 6: Check DIM Update Status with MetaManager
The 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 Gateway is down, RSG notifies Teradata to
begin writing to the MDS Recovery Table. When the Gateway comes back up, it reads the
MDS Recovery Table and marks each of the databases in the MDS Recovery Table as “out of
sync.” The Gateway will resync each database if Recovery on Startup is selected or at a
scheduled recovery time.
The recovery database is always DBC and the MDS Recovery Table is mdsrecoverytbl.
The Teradata user specified in the System Object must have SELECT and DELETE privileges
to the MDS Recovery Table.
Task 6: Check DIM Update Status with
MetaManager
Procedure - Checking DIM Update Status with MetaManager
1
From MetaManager, click System>Database Systems.
2
In the Teradata Meta Data Services Administration window, highlight a system name, click
Database Administration. The Teradata Meta Data Services Administration dialog appears.
To go directly to the Teradata Meta Data Services Administration dialog, 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. Refer to “Step 4: Enable Automatic DIM Update” on page 83 for additional
information.
The DIM Update Status window shows:
84
Name
Description
System Name
Displays the system chosen
DIM Update Status
Displays the 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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 9: Installing Automatic DIM Update
Task 7: Start/Stop the DDL Gateway
Name
Description
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
Displays the list of database names that 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.
Task 7: Start/Stop the DDL Gateway
The DDL Gateway is automatically started at system boot and stops at system shutdown. The
DDL Gateway starts as a service on Windows. The names of the DDL Gateway programs are:
Gateway Component
Windows Program Name
Gateway Server
gwserver.exe
Gateway Client
gwclient.exe
Integrity Servers
iserver.exe
Procedure - To Manually Start or Stop the DDL Gateway on Windows
1
To manually start or stop the DDL Gateway on Windows, use the Services Administrative
Tool. The DDL Gateway service is called Meta Data Services DDL Gateway.
Note: The DDL Gateway processes are not started at installation.
Note: On the initial installation of the Meta Data Services DDL Gateway, the status of the
system is “Down” and a message similar to the following is sent to the mds log:
10/18/02 15:31:43|PID52.3|5|CGwySocket::GetHostByAddr(153.64.14.126) returns ‘SMP0014’
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.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
85
Chapter 9: Installing Automatic DIM Update
Task 8: Start/Stop the MDS Action Processor
Task 8: Start/Stop the MDS Action Processor
The MDS Action Processor is automatically started at system boot and stops at system
shutdown. The MDS Action Processor starts as a service on Windows.
The name of the MDS Action Processor program is metaaction.exe on Windows.
Procedure - Manually Start or Stop the MDS Action Processor on Windows
1
86
To manually start or stop the MDS Action Processor in Windows, use the Services
Administrative Tool. The MDS Action Processor service is called Meta Data Services
Action Processor.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 10
Deploying Using SMS
This section provides guided upgrade practices for deploying by means of Microsoft SMS and
SCCM. Follow the procedures in this section and the guidelines provided to deploy Teradata
Tools and Utilities products from a Microsoft SMS Server.
It’s assumed that the SMS developer is familiar with deploying products using vbs scripts and
Microsoft SMS Server.
Tasks to Deploy Packages
The basic tasks to deploy using SMS are:
•
Gathering setup packages - Download the Teradata Tools and Utilities setup packages and
dependencies you wish to deploy with SMS from CD media using a Network installation,
or from the Teradata Download Center, or “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 CD media also copies default response
files for products that install using install scripts to the specified folders.
•
Determine products that install using:
•
Install scripts and product response files
•
Basic MSI files
Note: Include third-party products in your determination.
•
Create product response files - Create product response files for those products that
require them.
Note: Third-party packages are normally downloaded and deployed using SMS in the
same manner as Teradata Tools and Utilities packages. Some may require creation of
product response files.
•
Copy installation packages to the SMS Server - Copy all of the 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 script files - Create vbs scripts to install third-party products, and Teradata
products and their dependencies. The process can include: stopping programs that may be
running, determining if previous versions of the software exist, uninstalling it if required,
installing third-party dependencies, and installing Teradata Tools and Utilities products
and dependencies.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
87
Chapter 10: Deploying Using SMS
Task 1: Gather Installation Packages
•
Setup and deploy installation packages using SMS - Setup and deploy installation
packages to client systems using SMS.
Task 1: Gather Installation Packages
Step 1: Determine Versions to Download
The first task to perform to deploy using SMS is to determine which Teradata Tools and
Utilities installation packages contain the version of software you want to download and then
download the installation packages to a common folder. For purposes of explanation in this
section, call the folder “TTU13.x”, where “x” is the revision number.
Installation Package Sources
The SMS deployment procedures can download installation packages from these sources.
•
Web URL - Some Teradata Tools and Utilities have third-party dependencies. Download
these dependencies from their respective URLs.
•
CD Media - Download product installation packages to a single-user from the CD media
provided in the Teradata Tools and Utilities Installation Kit. The CDs contain the initial
release version of Teradata Tools and Utilities installation packages.
•
Teradata Download Center - Download Teradata Tools and Utilities device drivers and
communications packages available on the Teradata Download Center. The download
center may contain more current software installation packages which should be
downloaded instead of initial release version software contained on the CD media.
•
Teradata Software Server - Download Teradata Tools and Utilities packages from the
Teradata Software Server. The server contains the latest updated software packages which
should be download in lieu of earlier version software contained on the CD media, or on
the Teradata Download Center.
•
ESDM Server - Teradata's Electronic Software Distribution Management (ESDM)
program is not currently available for Windows.
The first source to check is the Teradata Software Server. It contains the most recent packages,
typically “point” releases of the original software, which contain fixes and updates. The
current release of each of the available software drivers is normally found on the Teradata
Download Center. The original release is located on the CD media. In some cases the CD
media is re-released containing point releases as needed.
Step 2: Download Installation Packages from the CD Media
Download Teradata Tools and Utilities installation packages from the CD media on either a
32-bit or 64-bit machine. Perform a “Network Installation” of packages to the directory
“TTU13.x”. Both the 32-bit and 64-bit packages and any required response files are copied to
the individual subfolders in the TTU13.x directory.
88
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 10: Deploying Using SMS
Task 1: Gather Installation Packages
Procedure - Downloading Installation Packages From CD Media
Perform this procedure to download the Teradata Tools and Utilities installation packages
from Teradata Tools and Utilities CDs using the main install “Network Install”.
1
Close all active windows programs and disable any virus protection software running on
the client computer.
2
Insert the Teradata Utility Pack for Windows Vol. 1 of 3 CD into the CD drive.
3
In the Welcome to Teradata Tools and Utilities dialog, click Install Product.
Note: If the Welcome dialog does not appear shortly after the CD is inserted, use Windows
Explorer to navigate to the main folder of the CD. Double-click the setup.bat file to start
the installation process.
4
In the Choose Setup Language dialog, click the drop-down arrow and select the desired
language from the list that appears, then click OK.
Note: English and Japanese are the only setup languages currently supported.
5
In the Welcome dialog, click Next.
6
In the Software License Agreement dialog, read the agreement, then click Yes to accept it.
7
In the Setup Type dialog, click Network. The Select Components dialog appears.
8
Do the following:
9
a
Select the boxes for the products whose installation files will be copied.
b
Clear the boxes for the products not being downloaded.
c
Click Next.
In the Choose Destination Location dialog box, if the default path shown in the Destination
Folder block is acceptable, click Next. (This is recommended.)
To use a destination location other than the default, click Browse, and navigate to the
folder where the files will be installed. Then click Next.
Note: Write access to the destination folder is required.
10 As files are copied to the Destination Folder, progress monitors appear during the process.
No action is required.
11 After the installation packages are copied to the Destination Folder, the Setup Complete
dialog appears. Choose whether or not to view the Teradata Tools and Utilities Release
Definition, then click Finish.
Note: All the packages and dependency packages required for the example SMS
deployment of BTEQ and SQLA Assistant are located on Teradata Utility Pack for Windows
Vol. 1 of 3 CD. If other packages are to be downloaded, repeat steps 2 through 11 for each
of the Windows installation disks in the Teradata Tools and Utilities Installation Kit
containing packages to be installed.
•
Preprocessors for Windows Vol. 1 of 3
•
Query Director Linux-Windows Vol. 1 of 1
•
Load/Unload for Windows Vol. 1 of 3
Teradata Tools and Utilities Installation Guide for Microsoft Windows
89
Chapter 10: Deploying Using SMS
Task 1: Gather Installation Packages
•
Parallel Transporter for Windows Vol. 1 of 3
•
Tape Storage Management Enablers Linux - Windows Vol. 1 of 1
•
Database Management Vol. 1 of 1
•
Teradata Meta Data Services Linux - MPRAS(RSG) - Windows Vol. 1 of 1
Step 3: Download Installation Packages from the Teradata Download
Center
Download installation packages from the Teradata Download Center. Each installation
package on the Teradata Download Center contains a procedure which may have been
customized for the individual package or release.
For 32-bit packages, download the 32-bit packages to the directory “TTU13.x”. The packages
are copied to the individual subfolders in the TTU13.x directory.
For 64-bit packages, download the installation packages to a 64-bit system. This allows you to
create 64-bit response files for those installation packages that require them. Then copy the
64-bit installation packages to the “TTU13.x” location on the 32-bit system, place them in
uniquely named directories.
The following steps illustrate a typical download from the Teradata Download Center. Each
downloadable package on the download center contains a procedure which may be
customized for the individual package or release.
Procedure - Downloading Installation Packages From the Teradata Download Center
1
Close all active windows programs and disable any virus protection software running on
the client computer.
Go to http://www.teradata.com/resources/drivers-udfs-and-toolbox
2
Click Drivers and Connectivity Software. The Teradata Download Center screen with a list of
selectable products appears.
3
Click the name of the product you want to download. The list expands to list the operating
systems which can be chosen.
4
Click Windows NT/2000/XP/Vista. A list of downloads available appears.
5
Click the appropriate software package to download. A description of the package appears.
6
Click Download Files package.
7
Read the License Agreement, then click I Accept. A screen with a link to the Download file
appears.
8
Click Download..., then Open.
9
A WinZip 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:
•
90
WinZip tool
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 10: Deploying Using SMS
Task 1: Gather Installation Packages
•
Right click on the zipped file and select Explore
•
Right click on the zipped file and select Open With -> Compressed (zipped) Folders
12 Repeat steps 2 through 11 for each package being downloaded from the Teradata
Download Center.
Step 4: Download Installation Packages from the Teradata Software
Server
Download Teradata Tools and Utilities installation packages from the Teradata Software
Server. Each downloadable package on the Teradata Software Server contains a procedure
which may be customized for the individual package or release.
For 32-bit packages, download the 32-bit packages to the directory “TTU13.x” on your PC.
The packages are copied to the individual subfolders in the TTU13.x directory.
For 64-bit packages, download the installation packages to a 64-bit system. Then copy the 64bit installation packages to the “TTU13.x” location on the 32-bit system, place them in
uniquely named directories.
The Teradata Software Server contains “patches” to software that have been made since the
software was released. Perform the following procedure to download installation packages
from the Teradata Software Server.
For those 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.
Download latest versions of required TTU Client products from patch server.
Procedure - Downloading Installation Packages from the Teradata Software Server
Follow these steps to download an installation package from the Teradata Software Server.
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 http://tssprod.teradata.com:8080/TSFS/home.do
4
Click on 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 box(es) to select the 32-bit software patch(es) to
download.
8
For 64-bit packages, click in the check box(es) to select the 64-bit software patch(es) to
download.
9
Enter your User Name and E-Mail Address, then click Submit.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
91
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
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:
•
WinZip 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 2 through 12 for each 32-bit and 64-bit package being downloaded from the
Teradata Software Server.
Step 5: Download Third-Party Dependencies
Procedure - Download Third-Party Dependencies
Perform the following steps to download .NET Framework. It is required for our example
SMS deployment.
1
Download the dependency to a folder. For our example deployment, download .NET
Framework from the Microsoft website to a subdirectory on your client PC. The
minimum version required is 2.0 SP2. Both 32-bit and 64-bit versions of the .NET
Framework must be deployed:
32-bit .NET Framework 2.0 redistributable
64-bit .NET Framework 2.0 redistributable
Task 2: Create Response Files
Response files must be created for both 32-bit and 64-bit packages. Performing a Network
installation copies the corresponding packages and any default response files to the product’s
user-specified installation directory.
Note: All Teradata Tools and Utilities client installation packages (except .NET Data Provider
for Teradata) include an MSI file.
On a 64-bit system, both a 32-bit and a 64-bit installation directory is created for those
products that have both. The following products require a response file for silent installation:
•
Teradata Archive/Recovery Utility
•
Teradata Meta Data Services
•
Teradata Query Director
Create 32-bit and 64-bit response files for those packages which require them.
The following table lists the products in the installation order that must be followed to insure
that dependencies are installed in the proper order, which products have 32-bit or 64-bit
installation packages, which products are installed using basic MSI, which products require a
response file, and their dependencies.
92
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Order
Product
0
Third-Party Dependencies
Install
Script
Basic
MSI
• Windows Installer 3.0
Windows Installer 3.0 Redistributable
Determine from the list of
dependencies in the right-hand
column.
1
Dependencies
• Determine required dependencies from thirdparty URL
Shared ICU Libraries for Teradata
X
None
X
None
X
None
X
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
TeraGSS - Client package
• Microsoft Data Access Components (MDAC),
version 2.8 SP1
Note: Required for Windows 2000 only.
32-bit package
2
Shared ICU Libraries for Teradata
64-bit package
3
Teradata Generic Security Services
Client
32-bit package only
4
ODBC Driver for Teradata
32-bit package
Note: On distribution CD.
5
X
ODBC Driver for Teradata
64-bit package
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
TeraGSS - Client package
• Microsoft Data Access Components (MDAC),
version 2.8 SP1
Note: Required for Windows 2000 only.
Note: On distribution CD.
6
OLE DB Provider for Teradata
X
32-bit package
• Shared ICU Libraries for Teradata
• Teradata GSS Client
• Microsoft Data Access Components (MDAC),
version 2.8 sp1
Note: Required for Windows 2000 only.
Note: On distribution CD.
Note: During silent installation of OLEDB
Provider for Teradata package when the user is
a part of administrator group but not an
inbuilt administrator on Windows 7,
Windows Server 2008 R2 and Windows Vista,
a UAC window will pop up. The user needs to
respond to continue with the installation of
the package.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
93
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Order
Product
7
Teradata JDBC Driver
Install
Script
Basic
MSI
• JDK 1.4, JDK 5.0, or JDK 6.0 from Sun
• 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
the Sun website at: http://java.sun.com/products/
archive
32-bit package
8
Teradata JDBC Driver
• JDK 1.4, JDK 5.0, or JDK 6.0 from Sun
• 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
the Sun website at: http://java.sun.com/products/
archive
64-bit package
9
Teradata Call-Level Interface version 2
X
• Teradata Generic Security Services
• Shared ICU Libraries for Teradata
X
• Teradata Generic Security Services
• Shared ICU Libraries for Teradata
X
None
X
None
X
• .NET Framework 2.0
32-bit redistributable
32-bit package
10
Teradata Call-Level Interface version 2
64-bit package
11
Dependencies
Teradata Data Connector
32-bit package
12
Teradata Data Connector
64-bit package
13
.NET Data Provider for Teradata
32-bit package only
64-bit redistributable
• (Optional) Microsoft Visual Studio 2005 or
Microsoft Visual 2008 Integration Feature
• (Optional) Microsoft SQL Server Business
Intelligence Development Studio
14
Teradata Archive/Recovery Utility
X
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Generic Security Services
Teradata Call-Level Interface version 2
Teradata Data Connector
X
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Generic Security Services
Teradata Call-Level Interface version 2
Teradata Data Connector
32-bit package
15
Teradata Archive/Recovery Utility
64-bit package
94
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Order
Product
16
Basic Teradata Query
Install
Script
Basic
MSI
X
•
•
•
•
Teradata Call-Level Interface version 2
Teradata Data Connector
Teradata Generic Security Services
Shared ICU Libraries for Teradata
X
•
•
•
•
Teradata Call-Level Interface version 2
Teradata Data Connector
Teradata Generic Security Services
Shared ICU Libraries for Teradata
X
•
•
•
•
X
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services
X
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
Teradata Query Scheduler Client
X
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Generic Security Services
Teradata Call-Level Interface version 2
Teradata Data Connector
X
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Generic Security Services
Teradata Call-Level Interface version 2
Teradata Data Connector
X
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Generic Security Services
Teradata Call-Level Interface version 2
Teradata Data Connector
X
•
•
•
•
Teradata Call-Level Interface version 2
Teradata Data Connector
Teradata Generic Security Services
Shared ICU Libraries for Teradata
32-bit package
17
Basic Teradata Query
64-bit package
18
Teradata Query Scheduler
Administrator
32-bit package only
19
Teradata Query Scheduler Client
32-bit package only
20
Teradata Query Scheduler Server
32-bit package only
21
Teradata FastExport
32-bit package only
22
Teradata FastLoad
32-bit package only
23
Teradata MultiLoad
32-bit package only
24
Teradata Parallel Data Pump
32-bit package only
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Dependencies
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
TCP/IP driver with WinSock support for
Windows version 1.1 or later
• Ethernet or Token Ring packet driver
compatible with the above
95
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Order
Product
25
Named Pipes Access Module
Install
Script
Basic
MSI
Dependencies
X
None
X
None
X
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
• ODBC Driver for Teradata
X
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services
• Shared ICU Libraries for Teradata
X
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services
• Shared ICU Libraries for Teradata
X
The ODBC Driver for Teradata can be used, in
addition to, or as an alternative to, the .Net Data
Provider for Teradata,.
32-bit package
26
Named Pipes Access Module
64-bit package
27
Teradata OLE DB Access Module
32-bit package only
28
Teradata C Preprocessor2
32-bit package
29
Teradata C Preprocessor2
64-bit package
30
Teradata SQL Assistant
32-bit package only
Teradata SQL Assistant dependencies must be
installed in the following order:
• Microsoft .NET Framework, version 2.0 or
later
32-bit redistributable
64-bit redistributable
• .NET Data Provider for Teradata, version 12.0
or later. Install Policy Files must be selected
during the installation.
http://www.teradata.com
• ODBC Driver for Teradata (optional)
Note: The ODBC Driver for Teradata can be
installed at any time before or after installing
Teradata SQL Assistant.
31
Teradata Administrator
X
• ODBC Driver for Teradata
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
X
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
• Teradata Call-Level Interface version 2
or
32-bit package only
32
Teradata Visual Explain
32-bit package only
• ODBC Driver for Teradata
96
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Order
Product
33
Teradata System Emulation Tool
Install
Script
Basic
MSI
X
32-bit package only
Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
• Teradata Call-Level Interface version 2
or
• ODBC Driver for Teradata
34
Teradata Parallel Transporter
Infrastructure
X
•
•
•
•
X
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services
X
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services
X
•
•
•
•
32-bit package only
35
Teradata Parallel Transporter API
32-bit package
36
Teradata Parallel Transporter API
64-bit package
37
Teradata Parallel Transporter Export
Operator
32-bit package
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
Java 2 Runtime Environment 1.4.2_06 or later
Note: The environment can be downloaded
from the Sun website at: http://java.sun.com/
products/archive
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
(Optional) Teradata Parallel Transporter
Infrastructure
Note: For Teradata Parallel Transporter job
script users.
• (Optional) Teradata Parallel Transporter API
Note: For Teradata Parallel Transporter API
users.
38
Teradata Parallel Transporter Export
Operator
64-bit package
X
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
(Optional) Teradata Parallel Transporter
Infrastructure
Note: For Teradata Parallel Transporter job
script users.
• (Optional) Teradata Parallel Transporter API
Note: For Teradata Parallel Transporter API
users.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
97
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Order
Product
39
Teradata Parallel Transporter Load
Operator
Install
Script
Basic
MSI
X
32-bit package
Dependencies
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
(Optional) Teradata Parallel Transporter
Infrastructure
Note: For Teradata Parallel Transporter job
script users.
• (Optional) Teradata Parallel Transporter API
Note: For Teradata Parallel Transporter API
users.
40
Teradata Parallel Transporter Load
Operator
X
64-bit package
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
(Optional) Teradata Parallel Transporter
Infrastructure
Note: For Teradata Parallel Transporter job
script users.
• (Optional) Teradata Parallel Transporter API
Note: For Teradata Parallel Transporter API
users.
41
Teradata Parallel Transporter Update
Operator
X
32-bit package
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
(Optional) Teradata Parallel Transporter
Infrastructure
Note: For Teradata Parallel Transporter job
script users.
• (Optional) Teradata Parallel Transporter API
Note: For Teradata Parallel Transporter API
users.
42
Teradata Parallel Transporter Update
Operator
64-bit package
X
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
(Optional) Teradata Parallel Transporter
Infrastructure
Note: For Teradata Parallel Transporter job
script users.
• (Optional) Teradata Parallel Transporter API
Note: For Teradata Parallel Transporter API
users.
98
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Order
Product
43
Teradata Parallel Transporter Stream
Operator
Install
Script
Basic
MSI
X
32-bit package
Dependencies
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
(Optional) Teradata Parallel Transporter
Infrastructure
Note: For Teradata Parallel Transporter job
script users.
• (Optional) Teradata Parallel Transporter API
Note: For Teradata Parallel Transporter API
users.
44
X
Teradata Parallel Transporter Stream
Operator
64-bit package
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
(Optional) Teradata Parallel Transporter
Infrastructure
Note: For Teradata Parallel Transporter job
script users.
• (Optional) Teradata Parallel Transporter API
Note: For Teradata Parallel Transporter API
users.
45
Teradata Index Wizard
X
32-bit package only
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
• Teradata Call-Level Interface version 2
or
• ODBC Driver for Teradata
46
Teradata Statistics Wizard
X
•
•
•
•
X
• Teradata Data Connector
• IBM WebSphere MQ V5.2
32-bit package only
47
Teradata WebSphere MQ Access
Module
Shared ICU Libraries for Teradata
Teradata Call-Level Interface version 2
Teradata Generic Security Services
ODBC Driver for Teradata
32-bit package only
48
Teradata Query Director
X
•
•
•
•
32-bit package only
49
Teradata Workload Analyzer
32-bit package only
Teradata Tools and Utilities Installation Guide for Microsoft Windows
X
Teradata Call-Level Interface version 2
Shared ICU Libraries for Teradata
Teradata Generic Security Services
No dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
• Teradata Call-Level Interface version 2
99
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Order
Product
Install
Script
50
Teradata Meta Data Services
X
Basic
MSI
•
•
•
•
Shared ICU Libraries for Teradata
Teradata Generic Security Services
ODBC Driver for Teradata
Java Runtime Environment 1.5.0 or later
• JDK 1.5, JDK 5.0, or JDK 6.0 from Sun
• 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
the Sun website at: http://java.sun.com/products/
archive
32-bit package only
51
Teradata Performance Monitor Object
Dependencies
X
32-bit package only
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
• Teradata Call-Level Interface version 2
Step 1: Installing with InstallScripts
Determine which Products Use InstallScripts
From the previous table, determine which packages you intend to deploy. Make note of their
•
Prerequisite dependencies
•
Order in which they need to be installed
•
Packages that require you to create a product response file
Creating 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>”
This is an example of the command to create a response file:
setup.exe /r /f1"c:\temp\TDOLEDB.iss"
The following commands and parameters refer to response files:
100
Command/Parameter
Description
setup.exe
Command - Setup command
/r
Record Mode - enables creation of a response file. When
a response file is recorded all the options selected are
recorded.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Command/Parameter
Description
/s
Silent Mode - plays the recorded response back with all
the options selected.
/f1”<response_file>”
Response File Name - By default, the response file is
named setup.iss and is created in the system’s
Windows folder. Use /f1 to specify an alternative
response file name and absolute path.
/f2”<setup_log_file>”
Setup Log File Name - The default logfile is created in
the same directory as the response file. It has the same
name, except for the extension, as the response file. Use /
f2 to specify an alternative log file name and absolute
path.
/w
Wait - setup.exe will not exit until the installation is
complete
This procedure creates product response files named setup.iss for packages which require them
for SMS deployment.
Note: 64-bit installation packages must be downloaded to 64-bit machines and their response
files created there. Both 32-bit and 64-bit packages must be “pushed” to 64-bit machines.
Procedure - Creating Product Response Files
1
Change directories to a 32-bit or 64-bit <package> folder which requires a product
response file.
2
Then, from the command line, execute the following:
setup.exe /r /f1”<response filename>”
The splash screen appears and Welcome screen appear.
3
Click Next and continue as though you were 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.
Installing with Product Response Files
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
This is an example of the command used to silently install using a response file:
setup.exe /s /f1"c:\temp\TDOLEDB.iss" /f2”c:\temp\TDOLEDB.log” /w
where the following commands and parameters refer to response files:
Teradata Tools and Utilities Installation Guide for Microsoft Windows
101
Chapter 10: Deploying Using SMS
Task 2: Create Response Files
Command/Parameter
Description
setup.exe
Command - Setup command
/r
Record Mode - enables creation of a response file. When
a response file is recorded all the options selected are
recorded.
/s
Silent Mode - plays the recorded response back with all
the options selected.
/f1”<response_file>”
Response File Name - By default, the response file is
named setup.iss and is created in the system’s
Windows folder. Use /f1 to specify an alternative
response file name and absolute path.
/f2”<setup_log_file>”
Setup Log File Name - The default logfile is created in
the same directory as the response file. It has the same
name, except for the extension, as the response file. Use /
f2 to specify an alternative log file name and absolute
path.
/w
Wait - setup.exe will not exit until the installation is
complete
Step 2: Installing Using Basic MSI Files
Determine which Products Use Basic MSI Files
From the previous table, determine which packages you intend to deploy using Basic MSI
files. Make note of their prerequisite dependencies, the order in which they need to be
installed.
Installing Using Basic MSI FIles
To install products using a Basic MSI file, the script file runs a command similar to the
following for each package directory that uses a Basic MSI file:
setup.exe /s /v”/qn” /w
where the following commands and parameters refer to response files and Basic MSI files:
102
Command/Parameter
Description
setup.exe
Command - Setup command
/s
Silent Mode - plays the recorded response back with all
the options selected.
/v
Pass Arguments - Pass arguments to Msiexec
/qn
Set Installation User Interface Level - Specifying /q or
/qn causes the installation to be silent with no user
interface.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 10: Deploying Using SMS
Task 3: Copy Packages
Command/Parameter
Description
/w
Wait - setup.exe will not exit until the installation is
complete
Task 3: Copy Packages
After product response files have been created for those installation packages that require
them, copy all the installation package folders to the SMS server.
Step 1: Copy Installation Packages
Procedure - Copy Installation Packages
Perform the following steps to get ready to create an SMS file.
1
Copy the “TTU13.10” directory containing 32-bit and 64-bit installation packages to the
Microsoft SMS server.
Task 4: Create a Script File
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.
Note: See “Chapter 11 Example Uninstall Script” on page 105 for an example of how to
uninstall products.
Task 5: Deploy Products Using SMS
To deploy Teradata Tools and Utilities use the vbs script you created and the features of the
Microsoft SMS server.
Step 1: Deploying Products
Procedure - Deploying Products
1
Follow your normal deployment procedures using SMS.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
103
Chapter 10: Deploying Using SMS
Task 5: Deploy Products Using SMS
104
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 11
Example Uninstall Script
This section contains the example Uninstall Script.
Example 1- Example Uninstall Script
‘====================================================================================================
‘ Copyright 2007-2009 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 searches the registry for the 32-bit and 64-bit variants of the product
‘ and uninstalls if the installed version is less than the version of the product that is
‘ being installed. The product name and product version is picked up from the Property Manager.
‘ 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 :
‘
1) This script assumes IDriver.exe file exists under the following folders
‘
on 32-bit machines:
‘
C:\Program Files\Common Files\InstallShield\Driver\7\Intel 32\ &
‘
C:\Program Files\Common Files\InstallShield\Driver\9\Intel 32\
‘
‘
on 64-bit machines:
‘
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:
‘ 13.00.00.002008Feb01pk185011DR117520TDICU: Uninstallation of previous version
‘ 13.00.00.002008Feb01pk185011DR117517CLIv2: Uninstallation of previous version
‘ 13.00.00.002008Feb01pk185011DR117527TDODBC: Uninstallation of previous version
‘ 13.00.00.002008Feb01pk185011DR117516PIOM: Uninstallation of previous version
‘ 13.00.00.002008Feb01pk185011DR116126BTEQ: Uninstallation of previous version
Teradata Tools and Utilities Installation Guide for Microsoft Windows
105
Chapter 11: Example Uninstall Script
‘ 13.00.00.002008Feb12pk185011DR117519FASTLD: Uninstallation of previous version
‘ 13.00.00.002008Feb12pk185011DR117525MLOAD: Uninstallation of previous version
‘ 13.00.00.002008Feb12pk185011DR117518FASTEXP: Uninstallation of previous version
‘ 13.00.00.002008Feb12pk185011DR117528TPUMP: Uninstallation of previous version
‘ 13.00.00.002008Mar15pk185011DRxxxxxxTERAGSS: Uninstallation of previous version
‘ 13.00.00.002008Mar15pk185011DRxxxxxxTDOLEDB: Uninstallation of previous version
‘ 13.00.00.002008Mar16pk185011DRxxxxxxSQLPP: Uninstallation of previous version
‘ 13.00.00.002008Mar16pk185011DRxxxxxxNPAXSMOD: Uninstallation of previous version
‘ 13.00.00.002008Mar16pk185011DRxxxxxxMQAXSMOD: Uninstallation of previous version
‘ 13.00.00.002008Mar16pk185011DRxxxxxxOLEDBAXSMOD: Uninstallation of previous version
‘ 13.00.00.002008Mar16pk185011DRxxxxxxJMSAXSMOD: Uninstallation of previous version
‘ 13.00.00.002008Jun19pk185011DR123218TDOLEDB: Enhanced the script to uninstall
‘
: corrupted installations or left over
‘
: files and registry entries.
‘ 13.00.00.002008Jul23pk185011DR123999ALL Products: Uninstallation of the previous versions
‘
DR124001
: was not working for silent installation
‘
DR124002
: of Basic MSI packages even though the
‘
: uninstall_prev_ver custom action was
‘
: sequenced in the Execute Sequence.
‘
: Hence the script was enhanced to execute
‘
: it from command prompt and uninstall
‘
: the previous versions of TTU products
‘
: that are passed to the script as arguments.
‘13.00.00.002008Aug29pk185011DR123999ALL Products: Uninstallation of 64-bit TTU products
‘
: was not happening because the 64-bit
‘
: registry was not accessed. Modified
‘
: the script to handle reading both the
‘
: 32-bit & 64-bit sections of the registry.
‘
: Added support for SQLA uninstall.
‘ 13.00.00.012008Oct15pk185011DR125893TDOLEDB: Added code to remove terasso.dll from
‘
: system folders during uninstallation.
‘ 13.00.00.012009Mar12pk185011DR125893TDOLEDB: Backing out the changes for DR125893 as the
‘
: changes are done in the TDOLEDB product to
handle the scenario.
‘ 13.00.00.01
2009Apr01
pk185011
DR129226
CLNINST
: Fixing issues in the script identified
during
‘
: testing through SMS at EBay.
‘====================================================================================================
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
Dim
Dim
Dim
Dim
Dim
Dim
Dim
Dim
Dim
txtfile
txtfile1
txtfile2
lf
outputfile
outputfile1
outputfile2
ScriptLog
ISSFileName
LogFileName
InstallPath
TIMESTAMP
Package_64bit
strcomputer
objCtx
objLocator
106
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
Dim
Dim
Dim
Dim
Dim
Dim
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 “
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)
Teradata Tools and Utilities Installation Guide for Microsoft Windows
107
Chapter 11: Example Uninstall Script
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”
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
108
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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
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)
Teradata Tools and Utilities Installation Guide for Microsoft Windows
109
Chapter 11: Example Uninstall Script
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 “---------------------------------------------------------------------------------------
‘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)
110
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
Dim
Dim
Dim
Dim
Dim
shellobj
outputobj
content
ExePath
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
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 & “
Version = “ & product_version
|
Product
‘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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
111
Chapter 11: Example Uninstall Script
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
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
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 installed.
“)” & “ < “ & “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
end if
loop
txtfile1.close
112
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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
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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
113
Chapter 11: Example Uninstall Script
‘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
‘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
114
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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
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 = ““
Teradata Tools and Utilities Installation Guide for Microsoft Windows
115
Chapter 11: Example Uninstall Script
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”
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),_
116
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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]”)
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)
Teradata Tools and Utilities Installation Guide for Microsoft Windows
117
Chapter 11: Example Uninstall Script
‘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),_
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
required.
‘Run the command to uninstall the product.
‘For earlier versions of TDODBC and SQLPP IDriver.exe from Installshield version 7.0 is
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 versions of TDODBC & SQLPP IDriver.exe from
‘Installshield version 9.0 is required.
lf.WriteLine “cmd /C “ & IDriver9Path & “ /M” & ProductCode & _
“ /verbose” & chr(34) & LogFileName & chr(34) & _
“ /s /f1” & 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
118
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
Dim pos
Dim RegPath
Dim RegValue
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
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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
119
Chapter 11: Example 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(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
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
‘========================================================================================================
=============================================
120
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
‘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
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”
Teradata Tools and Utilities Installation Guide for Microsoft Windows
121
Chapter 11: Example Uninstall Script
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)
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
122
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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
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)
Teradata Tools and Utilities Installation Guide for Microsoft Windows
123
Chapter 11: Example Uninstall Script
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
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
124
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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
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”
end if
if objFilesys.FileExists(InstallPath & “tdata32.dll”) then
Teradata Tools and Utilities Installation Guide for Microsoft Windows
125
Chapter 11: Example Uninstall Script
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”
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
126
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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
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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
127
Chapter 11: Example Uninstall Script
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
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
128
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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
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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
129
Chapter 11: Example Uninstall Script
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”
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
130
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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”
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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
131
Chapter 11: Example Uninstall Script
if objFilesys.FileExists(InstallPath & “PPCLB9”) then
lf.WriteLine “File found : “ & InstallPath & “PPCLB9”
rc = objFilesys.DeleteFile(InstallPath & “PPCLB9”,true)
else
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
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
132
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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
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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
133
Chapter 11: Example Uninstall Script
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
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
134
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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‘TERAGSS
Check_Name = Disp_Name
else
Check_Name = ProductName
end if
‘Retrieve information about the products installed on the machine by inspecting the
HKLM\SOFTWARE\Classes\Installer\Products keys in the registry
‘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)
strSubKey
if (Hex_Version = Outparams.uValue) then
lf.WriteLine “Matching Product Version found in entry and deleted the entry : “ &
Teradata Tools and Utilities Installation Guide for Microsoft Windows
135
Chapter 11: Example Uninstall Script
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...”
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
136
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 11: Example Uninstall Script
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
‘========================================================================================================
=============================================
‘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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
137
Chapter 11: Example Uninstall Script
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
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
‘========================================================================================================
=============================================
138
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 12
Configuring Teradata Tools and Utilities
This section contains procedures to configure the following Teradata Tools and Utilities
software.
Task 1: Configure Teradata Call-Level Interface
version 2 (CLIv2)
The following sections contain the steps required for setting the Teradata Call-Level Interface
version 2 for Windows network, environment, and system parameters:
•
Network Parameters - Setting the correct network parameters guarantees that the
Teradata Call-Level Interface version 2 for Windows will communicate with the target
Teradata Database. These parameters must be set correctly to use the software.
•
Environment Parameters - The environment parameters provide the Teradata Call-Level
Interface version 2 for Windows with parameter file location information, as well as the
facility for enabling CLIv2 to run in parallel mode. Setting the environment parameters is
highly recommended.
•
System Parameters - The CLIv2 system parameters are used internally by the Call-Level
Interface to customize services and features. Setting system parameters is necessary only if
there are special requirements that the default setting cannot meet.
Step 1: Setup Network Parameters
The Internet address and the symbolic names for the Teradata Database are considered the
network parameters. This section assumes that network software is installed correctly.
Verify the hosts File Exists
If not running a Name Server, 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 individual computer system in the network.
If running a Name Server, make sure the hosts file is on the Name Server and that network
software is configured to access the Name Server. The Teradata Tools and Utilities software
uses generic TCP/IP GetHostByName services.
The hosts file is in the %SystemRoot%\WINDOWS\system32\drivers\etc\hosts folder.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
139
Chapter 12: Configuring Teradata Tools and Utilities
Task 1: Configure Teradata Call-Level Interface version 2 (CLIv2)
Identify a Teradata Database
To identify the Teradata Database, add an entry to the hosts file for each TCP/IP
Communications Processor (COP), Applications Processor (AP), or UNIX node running the
Teradata Gateway that the client computer will be communicating. The following table
includes the entries to the hosts file.
Platform
Entries to the Hosts file
Teradata Database on an AP platform (System 3600)
APs
Teradata Database on a V2 Computer (UNIX)
nodes
Note: Throughout this manual, “AP” refers to the following: TCP/IP Communications
Processor (COP), Applications Processor (AP), and the node running the Teradata Gateway.
Syntax to Add an Entry to the hosts File
Use the following syntax when adding entries to the hosts file:
<a.b.c.d > <dbcnameCOPn> [aliasCOPn]
The following table describes the hosts file syntax.
Parameter
Description
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,
%ProgramFiles%\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 name(s) can be used for the remaining Teradata
Database(s).
140
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 12: Configuring Teradata Tools and Utilities
Task 1: Configure Teradata Call-Level Interface version 2 (CLIv2)
Parameter
Description
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 equal n in the
corresponding dbcname COPn.
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.
In this case, add these lines to the hosts file:
101.0.0.21 dbcnode1 dbccop1 ncrcop1
101.0.0.22 dbcnode2 dbccop2 ncrcop2
Step 2: Setup Environment Parameters
The environment parameters allow the runtime environment for each user who will be using
the Teradata Tools and Utilities software to be specified.
On Windows systems, if system environment parameters are changed, the client computer
must be rebooted for the changes to take effect. It is not enough to restart the daemon, nor
logoff and log on again.
Define Paths to System Files
Define the path to the CLIv2 system parameter block file and the anomaly log file by setting
the following environment parameters. The following table shows how to setup Environment
Parameters.
Parameters
Definition
COPLIB
COBLIB is the path to the CLIv2 system parameter block
file, clispb.dat.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
141
Chapter 12: Configuring Teradata Tools and Utilities
Task 1: Configure Teradata Call-Level Interface version 2 (CLIv2)
Parameters
Definition
COPANOMLOG
COPANOMLOG is the path to the anomaly log file, a trace
log file displaying CLIv2 activities, including networkrelated error information. This environment variable
should be defined only for debugging purposes.
Setup the Environment Variables on Windows XP, 2000 and 2003
Use the information in the following table to setup the Environment Parameters.
Note: If COPLIB is not specified when the Teradata Tools and Utilities applications are
started, the current working folder finds the system parameter block file (.\clispb.dat). If
COPANOMLOG is not specified, no anomaly log file created.
The following table shows how to setup Environment Parameters.
Platform
Action
Windows 2000
Start > Control Panel > System, then
select the Advanced tab, then click on
Environment Variables.
Windows XP or Windows Server 2003
Start > Control Panel > System, then
select the Advanced tab, then click on
Environment Variables.
Speed Up the Logon Process
The speed of the logon process can be increased by limiting the number of host name
resolution requests issued by the Teradata Tools and Utilities 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>
The following table lists the login parameter definitions.
Parameter
Definition
machine_name
The name of the machine
cops
The number of COPS
For example:
set 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.
The following table describes how to setup <machine name>.
142
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 12: Configuring Teradata Tools and Utilities
Task 1: Configure Teradata Call-Level Interface version 2 (CLIv2)
Platform
Setup
Windows 2000
Start > Control Panel > System, then
select the Advanced tab, then click on
Environment Variables.
Windows XP or Windows Server 2003
Start > Control Panel > System, then
select the Advanced tab, then click on
Environment Variables.
Setup the Port Number
Specify the port number used by the Teradata Tools and Utilities software by setting the
environment variable TDMSTPORT as follows:
set TDMSTPORT=<nnnn>
The following table provides definitions for the port number parameters.
Parameter
Definition
nnnn
The port number
The following table provides how to setup TDMSTPORT
Platform
How to Setup TDMSTPORT
Windows 2000
Start > Control Panel > System, then
select the Advanced tab, then click on
Environment Variables.
Windows XP or Windows Server 2003
Start > Control Panel > System, then
select the Advanced tab, then click on
Environment Variables.
NETRACE - Enable Detailed COPANOMLOG Logging
Setting NETRACE=1 enables detailed network information between the client computer and
the Teradata Database server. This information is logged into the file defined in the
environmental setting COPANOMLOG.
THREADLOGGING - Enable Multiple COPANOMLOG File Creation
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.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
143
Chapter 12: Configuring Teradata Tools and Utilities
Task 2: Configure ODBC Driver for Teradata
Step 3: Setup System Parameters
The clispb.dat file (the CLIv2 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 CLIv2 internal defaults.
Edit the clispb.dat file to meet the system’s most common requirements. Refer to the Teradata
Call-Level Interface Version 2 Reference for Network-Attached Systems for more information.
Task 2: Configure ODBC Driver for Teradata
The following table contains configuration information for products installed:
Product
Configuration Information
ODBC Driver for Teradata
Use the ODBC Administrator to configure the driver.
For more information, refer to the:
ODBC Driver for Teradata User Guide
Step 1: Configure an ODBC Data Source
This section describes how to configure the ODBC Driver for Teradata for Windows clients.
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 to
communicate with Teradata Database.
Procedure - Configuring an ODBC Data Source
1
From the Windows desktop, select Start > Control Panel > Administrative Tools > Data
Sources (ODBC).
2
In the ODBC Data Source Administrator dialog, from the drop down, decide what type of
data source to create:
Data Source Name
Explanation
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
After selecting the DSN type, click Add.
For example: In the ODBC Data Source Administrator dialog, click the System DSN tab to
bring it to the front. Click Add.
144
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 12: Configuring Teradata Tools and Utilities
Task 2: Configure ODBC Driver for Teradata
4
In the Create New Data Source dialog, select Teradata and click Finish.
5
In the ODBC Driver Setup for Teradata Database dialog, enter information on the location
of the database and the connection parameters to be used when establishing a connection.
These are described in the following table.
Field Description
Recommended Action
In the Data Source Group....
Name
Enter any name you want to give to the data source being created.
Description
Enter a description. This is a comment to describe the data source
name used.
In the Teradata Server Info Group...
Name(s) or IP address(es)
Enter the name(s) or IP address(es) 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.
Note: Never enter both a name and an IP address.
See the “DBCName=<IP-addr-or-alias> DBCName2=<IP-addror-alias> DBCNamen=<IP-addr-or-alias>” option in the “Data
Source Specification Section” in Chapter 2.
Do not resolve alias name
to IP address
Check this box because you are entering the names or IP addresses
of each node manually, which is recommended.
In the Authentication Group...
Use Integrated Security
This is single sign-on. Do not check this.
Mechanism
Choose TD2 unless otherwise mandated by your site. For more
information, see Security Administration.
Parameter
Leave this blank. It is optional for the TD2 mechanism.
Username
Enter a user name valid for the Teradata Database specified in the
Data Source Name.
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 Teradata ODBC Driver (such as SQL
Assistant).
In the Optional Group...
Teradata Tools and Utilities Installation Guide for Microsoft Windows
145
Chapter 12: Configuring Teradata Tools and Utilities
Task 3: Configure Teradata Query Scheduler Administrator
Field Description
Recommended Action
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.
Account String
Enter one of the accounts that the DBA assigned to the Username
when it was created.
In the Session Character Set Group...
Session Character Set
Choose the character set. The default is ASCII.
Optionally, you can now configure:
•
ODBC Driver for Teradata Options
•
Teradata ODBC Driver Advanced Options
Note: Teradata strongly recommends that you do not change the settings in the Teradata
ODBC Driver Advanced Options dialog.
6
Click OK. Your ODBC configuration is now complete.
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
File>Define Data Source>Configure, rather than in the Teradata ODBC Driver. The change is
automatically entered in the ODBC configuration and is in effect for all ODBC-enabled
utilities installed on that machine.
Task 3: Configure Teradata Query Scheduler
Administrator
Starting with Teradata Tools and Utilities Release 13.10, 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, Client and Server configuration
parameters are changeable within the program.
For more information, refer to the Teradata Query Scheduler Administrator Guide.
Step 1: Modify the HOSTS File
If your site does not use a DNS, define the IP address and the Teradata Database name to use
in the system HOSTS file on your workstation.
146
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 12: Configuring Teradata Tools and Utilities
Task 4: Configure Teradata Query Scheduler Client
To Define the System IP Address and Teradata Database Name
1
Open Windows Explorer and navigate to the HOSTS file in the subdirectory of the
directory in which Windows is installed, for example WINNT\system32\drivers\etc.
2
Double-click the HOSTS file.
If this file is not already mapped to an application, an Open With dialog box appears.
3
Select NOTEPAD from the Program list.
4
Click OK.
The HOSTS file opens in a Notepad window.
5
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.
6
Click File>Save.
7
Click File>Exit to close Notepad and return to your desktop.
Task 4: Configure Teradata Query Scheduler
Client
Starting with Teradata Tools and Utilities Release 13.10, 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, Client and Server configuration
parameters are changeable within the program.
For more information, refer to the Teradata Query Scheduler User Guide.
Task 5: Configure Teradata Query Scheduler
Server
To start the Teradata Query Scheduler Server, first configure database logon credentials using
the Teradata Query Scheduler Operations Utility.
For more information, refer to the Teradata Query Scheduler User Guide.
Step 1: Specify a Default Teradata Query Scheduler Server
Usually the Query Scheduler Viewer temporarily establishes a Teradata Database session using
CLIv2 (Call-Level Interface version 2) to validate the logon parameters and find the location
of an active Teradata Query Scheduler server. However, if CLIv2 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. To do this, use
Teradata Tools and Utilities Installation Guide for Microsoft Windows
147
Chapter 12: Configuring Teradata Tools and Utilities
Task 5: Configure Teradata Query Scheduler Server
the Teradata Query Scheduler client library functions. See “Changing Default Server
Information” 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.” To learn
how to start using the Teradata Query Scheduler Operations utility, go to: “Working with the
Teradata Query Scheduler Operation Utility”. See “Getting Started”. to find out more about
the Teradata Query Scheduler Viewer.
Step 2: Change Server Configurations
General Teradata Query Scheduler server configurations are specified using the Server
Parameters dialog box.
Procedure - Changing Server Parameters
1
From the Teradata Query Scheduler Operations window, click Configuration>Server.
The Server Parameters dialog box appears.
2
Change the following fields as desired:
Field/Control
Description
Character Set box
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)
text box
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 box
Specify the number of server processes created for handling client
messages.
Encrypt Client Data check
box
Define if 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. Click
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.
3
148
Click OK to close the Server Parameters dialog box and return to the Teradata Query
Scheduler Operations tool.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 12: Configuring Teradata Tools and Utilities
Task 6: Configure Teradata Administrator
Task 6: Configure Teradata Administrator
After installation, the Teradata Administrator should be configured to include the Teradata
user name.
Procedure - Configuring the Teradata Administrator
Follow these steps to configure the Teradata Administrator.
1
Go to: %ProgramFiles%\Teradata\Client\<version>\Teradata Administrator\sql
2
Open setup.sql
3
Use the Edit/Replace menu to change all occurrences of the string <User> to the Teradata
user name.
4
Execute the query.
Task 7: Configure Teradata Parallel
Transporter for Windows
After Teradata Parallel Transporter Infrastructure has been installed, the local configuration
file: twbcfg.ini requires modification to change the Checkpoint
Step 1: Edit the Configuration File (twbcfg.ini)
Edit the configuration file, %ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\twbcfg.ini. It contains the default directory for checkpoint and logs.
A text editor can be used to modify the configuration file.
Change the Checkpoint and Log Directories
For example, modify the Teradata Parallel Transporter configuration file, to change the
checkpoint or log directories.
No reboot is required after making the change in the configuration file.
An example of the Teradata Parallel Transporter configuration file is shown here:
CheckpointDirectory= 'c:\Program Files\Teradata\Client\13.10\Teradata
Parallel Transporter\checkpoint'
LogDirectory='c:\Program Files\Teradata\Client\13.10\Teradata Parallel
Transporter\logs'
CheckpointDirectory refers to the folder that contains the checkpoint files for Teradata Parallel
Transporter jobs.
LogDirectory refers to the folder that contains the binary logs for Teradata Parallel Transporter
jobs. Each Teradata Parallel Transporter job creates a job log in the jobs directory.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
149
Chapter 12: Configuring Teradata Tools and Utilities
Task 7: Configure Teradata Parallel Transporter for Windows
Note: If a change is made to the folder for the LogDirectory and the Teradata Parallel
Transporter Wizard is installed, the LOG_DIRECTORY entry in the
%TWB_ROOT%\tptwizard\config\tptwizard.properties file must be changed before running
Teradata Parallel Transporter Wizard. %TWB_ROOT% is the system environment variable
that holds the value for the Teradata Parallel Transporter installation folder.
Step 2: Edit the Properties File (tptwizard.properties)
For example, if the folder for the LogDirectory to C:\Logs\Teradata Parallel Transporter 13.10 is
changed and the Teradata Parallel Transporter Wizard is installed, use the following
procedures to update the LOG_DIRECTORY entry in the
%TWB_ROOT%\tptwizard\config\tptwizard.properties file.
Procedure - Updating the LOG_DIRECTORY
Use the following steps to update the LOG_DIRECTORY.
1
Use a text editor (for example, NOTEPAD) to open the tptwizard.properties file in the
%TWB_ROOT%\tptwizard\config folder.
2
Update the LOG_DIRECTORY line to this:
LOG_DIRECTORY=c:\Program Files\Teradata\Client\13.1\Teradata Parallel
Transporter\logs\\
3
Save the change.
4
Quit the editor.
The C:\Logs\Teradata Parallel Transporter 13.10.00.00 folder is used as an example. A different
folder can be used.
The folder for the LOG_DIRECTORY entry in the tptwizard.properties file must be separated
by double backslash “\\” and must end with double backslash “\\”.
Refer to the Teradata Parallel Transporter Reference manual on how to read the job log.
Step 3: Setup User Environment Variables
If the TWB_ROOT user environment variable is used, it is recommended to delete it before
running a Teradata Parallel Transporter job.
Procedure - Deleting the TWB_ROOT Variable
Follow these steps to delete the TWB_ROOT user variable.
150
1
Go to Start > Settings > Control Panel > System
2
In the System Properties dialog box, click on the Advanced tab.
3
In the Advanced tab, click on the Environment Variables button.
4
Highlight the TWB_ROOT variable in the User variables section and click on the Delete
button.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 12: Configuring Teradata Tools and Utilities
Task 8: Configure Teradata JDBC Driver
5
Click on the OK button.
6
Click on the OK button again.
Step 4: Setup System Environment Variable ORACLE_HOME
The Teradata Parallel Transporter Wizard requires that the ORACLE_HOME system
environment variable point to folder where the Oracle client version of software used by the
Teradata Parallel Transporter Wizard is located.
Task 8: Configure Teradata JDBC Driver
For configuration instructions, see “Importing the SQL Package and Loading the Teradata
JDBC Driver” in chapter 2 of the Teradata JDBC Driver User Guide.
Note: It is recommended, but not required, that previous releases of the Teradata JDBC Driver
be uninstalled prior to downloading and installing this release of the Teradata JDBC Driver.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
151
Chapter 12: Configuring Teradata Tools and Utilities
Task 8: Configure Teradata JDBC Driver
152
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 13
Verifying the Installation
Using the CLI Sample Program
There are a number of ways to verify that Teradata Tools and Utilities have been properly
installed including: checking the files and folders for a product; and using the CLI Sample
program.
Task 1: Run clisamp to Verify the Installation
One way to verify that Teradata Tools and Utilities software has been properly installed is to
run the sample CLI application, clisamp. The program and its makefile were copied over
during the installation.
Procedure - Running clisamp to Verify the Installation
Perform the following steps to verify the installation:
1
Modify the makefile makesamp.win with the correct paths to the include files. By default
the makesamp.win file is located in:
%ProgramFiles%\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.”
“clisamp - Win32 Release” is also supported.
3
Run the sample program by entering one of the following commands at the command
prompt (change to the appropriate folder first: Release, Debug, x8664Release, or
x8664Debug):
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
Teradata Tools and Utilities Installation Guide for Microsoft Windows
153
Chapter 13: Verifying the Installation Using the CLI Sample Program
Task 1: Run clisamp to Verify the Installation
4
The program logs on to the default dbccop1 (no user input supplied) specified in the hosts
file and execute a simple query - “SELECT * from dbc.sessioninfo;” and write the output
to DAT clisamp.dat file. A display similar to the following appears:
# clisamp
CLIv2 version is 13.10.00.24
MTDP version is 13.10.00.20
MOSIOS version is 13.10.00.05
MOSIDEP version is 13.10.00.05
OSERR version is 13.10.00.01
Logging on to --->dbc/systemfe,service
writing out to--> CLISAMP.DAT
submitting -->select* from dbc.sessioninfo;
writing out to --> CLISAMP.DAT
Logging off.
154
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 14
Verifying the OLE DB Provider for
Teradata Installation
On 32-bit systems verify the installation of OLE DB Provider for Teradata.
Task 1: Verify the Installation
To verify the installation of OLD DB Provider for Teradata, perform the following procedure.
Note: The procedure only works on 32-bit systems.
Procedure - Verify the Installation
Perform the following steps to verify the installation:
1
Open Windows Explorer.
2
Navigate to the directory where OLE DB Provider for Teradata was installed.
3
Verify the TDOLEDB_TEST.udl file is in the destination folder.
Note: The presence of this file in the destination folder verifies that the rest of the OLE DB
Provider for Teradata files are also installed in the correct directory.
4
Double-click the TDOLEDB_TEST.udl file to display the Data Link Properties dialog.
5
In the dialog, do the following:
•
Select the Connection tab.
•
In the Data Source field, type the Teradata Database name or IP address.
•
Select Use a specific user name and password.
•
In the User name field, enter the name of the Teradata user.
•
In the Password field, enter the Teradata User password.
•
Click Test Connection.
6
If a Test Connection succeeded message appears, the software installation is successful and
an OLE DB session is established. If an error message appears, the connection attempt
failed.
7
In Data Link Properties, click Cancel.
8
Close the Windows Explorer file utility
Teradata Tools and Utilities Installation Guide for Microsoft Windows
155
Chapter 14: Verifying the OLE DB Provider for Teradata Installation
Task 1: Verify the Installation
9
156
Close Windows Find utility if open.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 15
Checking Files and Folders
This section describes how to verify that Teradata Tools and Utilities software has been
installed properly. This chapter includes the following topics:
Step 1: Verifying Installation of Individual
Products
Procedure - Verifying Installation of Individual Products
Follow these steps to verify the installation of individual Teradata Tools and Utilities products
and their dependencies.
1
Check that the directories specified in the tables below have been installed.
2
Check that the files specified in the tables below have been installed.
•
Step 1: Verifying Installation of Individual Products
•
Basic Teradata Query (BTEQ)
•
Named Pipes Access Module
•
.NET Data Provider for Teradata
•
ODBC Driver for Teradata
•
OLE DB Provider for Teradata
•
Shared ICU Libraries for Teradata
•
Teradata Administrator
•
Teradata Archive/Recovery Utility (ARC)
•
Teradata C Preprocessor2
•
Teradata Call-Level Interface version 2 (CLIv2)
•
Teradata Data Connector
•
Teradata FastExport
•
Teradata FastLoad
•
Teradata Generic Security Services
•
Teradata Index Wizard
•
Teradata JDBC Driver
•
Teradata Meta Data Services
•
Teradata MultiLoad
Teradata Tools and Utilities Installation Guide for Microsoft Windows
157
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
•
Teradata OLE DB Access Module
•
Teradata Parallel Data Pump
•
Teradata Parallel Transporter API
•
Teradata Parallel Transporter Export Operator
•
Teradata Parallel Transporter Infrastructure
•
Teradata Parallel Transporter Load Operator
•
Teradata Parallel Transporter Stream Operator
•
Teradata Parallel Transporter Update Operator
•
Teradata Performance Monitor Object
•
Teradata Query Director
•
Teradata Query Scheduler Administrator
•
Teradata Query Scheduler Client
•
Teradata Query Scheduler Server
•
Teradata SQL Assistant
•
Teradata System Emulation Tool
•
Teradata Visual Explain
•
Teradata WebSphere MQ Access Module
•
Teradata Workload Analyzer
Basic Teradata Query (BTEQ)
The following table lists BTEQ files installed for 32-bit platforms.
BTEQ for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
bteq.exe
%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
158
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
BTEQ for Windows 32-bit platforms
Merge Modules
Visual C++ 8.0 CRT
(x86)
C:\windows\WinSxS
Visual C++ 8.0 MFC
(x86)
Visual C++ 8.0
MFCLOC (x86)
Named Pipes Access Module
The following table lists Named Pipes Access Module files installed for 32-bit platforms.
Named Pipes Access Module for Windows 32-bit platforms
File Type
File Name
Default Folder
Library
np_AXSMOD.dll
%ProgramFiles%\Teradata\Client\<version>\AXSMOD
np_AXSMODenu.dll
The following table lists Named Pipes Access Module files installed for 32-bit on a 64-bit
platform.
Named Pipes Access Module for Windows 32-bit on 64-bit platforms
File Type
File Name
Default Folder
Library
np_AXSMOD.dll
%ProgramFiles(x86)%
\Teradata\Client\<version>\AXSMOD
np_AXSMODenu.dll
The following table lists Named Pipes Access Module files installed for 64-bit platforms.
Named Pipes Access Module for Windows 64-bit platforms
File Type
File Name
Default Folder
Library
np_AXSMOD.dll
%ProgramFiles%\Teradata\Client\<version>\AXSMOD
np_AXSMODenu.dll
.NET Data Provider for Teradata
The following table lists .NET Data Provider for Teradata files installed for 32-bit platforms.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
159
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata .NET Data Provider for Teradata for Windows 32-bit platforms
File Type
File Name
Default Folder
bin
%ProgramFiles%\Teradata\NET
Data Provider for Teradata\<version>
config
help
PrivateAssemblies
samples
TraceLog
Readme.txt
Executables
SetLogLevel.exe
Teradata.Client.Provider.dll
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>\bin
Teradata.Client.Provider.xml
Configuration
Teradata.Client.Provider.resources.dll
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>\bin\ja
ja
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>\config
LogAllDebug.config
LogAllError.config
LogAllInfo.config
LogAllTraceExternal.config
LogAllTraceInternal.config
LogAllWarn.config
LogOff.config
SDKExtensions.xsd
TdgssNetConfig.exe
TdgssUserConfigFile.xml
Configuration
160
TdgssNetConfig.resources.dll
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>\config\ja
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata .NET Data Provider for Teradata for Windows 32-bit platforms
Help
COL_TDNETDP.HxC
COL_TDNETDP.hxt
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>\help
COL_TDNETDP_A.hxk
COL_TDNETDP_D.hxk
COL_TDNETDP_F.hxk
COL_TDNETDP_K.hxk
COL_TDNETDP_N.hxk
tdnetdp.chm
tdnetdp.hxs
Private
Assemblies
ja
policy.1.0.Teradata.Client.Provider.config
policy.1.0.Teradata.Client.Provider.dll
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>\PrivateAssemblie
s
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
Teradata.Client.VS.dll
Teradata.Net.Security.Tdgss.dll
Private
Assemblies
Teradata.Client.VS.resources.dll
Samples
NQuery.application
Teradata.Net.Security.Tdgss.resources.dll
NQuery.exe
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>\PrivateAssemblie
s\ja
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>\samples\Bin
NQuery.exe.config
NQuery.exe.maifest
Samples
readme.doc
T20000DP.cs
thru
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>\samples\Learnin
gExamples
T21300DP.cs
Teradata Tools and Utilities Installation Guide for Microsoft Windows
161
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata .NET Data Provider for Teradata for Windows 32-bit platforms
Trace Log
Teradata.Client.Provider.dll
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>TraceLog
Trace Log
Teradata.Client.Provider.resources.dll
%ProgramFiles%\Teradata\NET
Data Provider for
Teradata\<version>TraceLog\ja
ODBC Driver for Teradata
The following table lists ODBC Driver for Teradata files installed for 32-bit platforms.
ODBC Driver for Teradata for Windows 32-bit platforms
File Type
File Name
Default Folder
Pbocd0x0.txt
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradata
Readme.txt
tdodbcdsn.vbs
tdsql.h
Bin
tdxodbc
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradata\Bin
Help
catalog.css
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradata\Help
document.css
images (folder)
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
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradata\Lib
tdatas32.dll
tdprsr32.dll
terasso.dll
162
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
ODBC Driver for Teradata for Windows 32-bit platforms
Samples
adhoc.c
error.c
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradata\Samples\C
getopt.c
getopt.h
The following table lists ODBC Driver for Teradata files installed for 64-bit platforms.
ODBC Driver for Teradata for Windows 64-bit platforms
File Type
File Name
Default Folder
Pbodb0x0.txt
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradata nt-x8664
Readme.txt
tdodbcdsn.vbs
tdsql.h
Bin
tdxodbc
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradata nt-x8664\Bin
Help
catalog.css
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradata nt-x8664\Help
document.css
images (folder)
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
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradata nt-x8664\Lib
Tdatas32.dll
tdprsr32.dll
terasso.dll
Samples
adhoc.c
error.c
%ProgramFiles%\Teradata\Client\<version>\ODBC Driver for
Teradatant-x8664\Samples\C
getopt.c
getopt.h
Teradata Tools and Utilities Installation Guide for Microsoft Windows
163
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
OLE DB Provider for Teradata
The following table lists OLE DB Provider for Teradata files installed for 32-bit platforms.
Teradata OLE DB Provider for Teradata for Windows 32-bit platforms
File Type
File Name
Default Folder
terasso.dll
%ProgramFiles%\Teradata\Client\<version>\OLE
DB Provider for Teradata
TDOLEDB.dll
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
The following table lists Shared ICU Libraries for Teradata installed for 32-bit platforms.
Shared ICU Libraries for Teradata for Windows 32-bit platforms
File Type
File Name
Default Folder
Dynamic Link Library
icudttd361.dll
%ProgramFiles%\Teradata\Client\<version>\Shared
ICU Libraries for Teradata\lib
icuintd36.dll
icuiotd36.dll
iculetd36.dll
iculxtd36.dll
icuuctd36.dll
The following table lists Shared ICU Libraries for Teradata installed for 32-bit package on 64bit platforms.
Shared ICU Libraries for Teradata for Windows 32-bit package on 64-bit platforms
File Type
164
File Name
Default Folder
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Shared ICU Libraries for Teradata for Windows 32-bit package on 64-bit platforms
Dynamic Link Library
icudttd361.dll
icuintd36.dll
%ProgramFiles(x86)%\Teradata\Client\<version>\S
hared ICU Libraries for Teradata\lib
icuiotd36.dll
iculetd36.dll
iculxtd36.dll
icuuctd36.dll
The following table lists Shared ICU Libraries for Teradata installed for 64-bit platforms.
Shared ICU Libraries for Teradata for Windows 64-bit platforms
File Type
File Name
Default Folder
Dynamic Link Library
icudttd361.dll
%ProgramFiles(x86)%\Teradata\Client\
<version>\Shared ICU Libraries for Teradata\lib
icuintd36.dll
icuiotd36.dll
iculetd36.dll
iculxtd36.dll
icuuctd36.dll
Teradata Tools and Utilities Installation Guide for Microsoft Windows
165
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Administrator
The following table lists Teradata Administrator folders and files installed for 32-bit platforms.
Teradata Administrator for Windows 32-bit platforms
File Type
File Name
Default Folder
asycfilt.dll
%ProgramFiles%\Teradata\Teradata Administrator
13.1\bin
comcat.dll
ctl3d32.dll
history.txt
mfc42u.dll
MSVBVM60.DLL
msvcr80.dll
msvcrt.dll
oleaut32.dll
olepro32.dll
shfolder.dll
STOLE2.TLB
tdtmgr.dll
teradata.syn
teradata_sp.syn
verify.dat
Verify.exe
winddi.exe
winddi_enu.chm
Winddi_enu.dll
winddird.txt
setup.sql
udtdistinct.txt
%ProgramFiles%\Teradata\Teradata Administrator
13.1\sql
udtstruct.txt
winddi.def
winddix.def
XViews.sql
166
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Archive/Recovery Utility (ARC)
The following table lists Teradata Archive/Recovery Utility (ARC) installed for 32-bit
platforms.
Teradata Archive/Recovery Utility (ARC) for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
arcmain.exe
%ProgramFiles%\Teradata\Client\<version>\bin
The following table lists Teradata Archive/Recovery Utility (ARC) installed for Windows 32bit on 64-bit platforms.
Teradata Archive/Recovery Utility (ARC) for Windows 32-bit on a 64-bit platforms
File Type
File Name
Default Folder
Executable
arcmain.exe
%ProgramFiles(x86)%\Teradata\Client\<version>\bin
The following table lists Teradata Archive/Recovery Utility (ARC) installed for Windows 64bit on a 64-bit platforms.
Teradata Archive/Recovery Utility (ARC) for Windows 64-bit on a 64-bit platforms
File Type
File Name
Default Folder
Executable
arcmain.exe
%ProgramFiles%\Teradata\Client\<version>\bin
Teradata C Preprocessor2
The following table lists C Preprocessor installed for the 32-bit platform.
Teradata C Preprocessor2 for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
ppcmain.exe
%ProgramFiles%\Teradata\Client\<version>\bin
Library
ppruntim.dll
%ProgramFiles%\Teradata\Client\<version>\pp2
Library
ppruntim.lib
%ProgramFiles%\Teradata\Client\<version>\pp2
Teradata Tools and Utilities Installation Guide for Microsoft Windows
167
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata C Preprocessor2 for Windows 32-bit platforms
Sample
LABSBTEQ
%ProgramFiles%\Teradata\Client\<version>\pp2
PPCLB1
PPCLB2
PPCLB3
PPCLB4
PPCLB5
PPCLB6
PPCLB7
PPCLB8
PPCLB9
The following table lists C Preprocessor files installed for the 64-bit platform.
Teradata C Preprocessor2 for Windows 64-bit platform
File Type
File Name
Default Folder
Executable
ppcmain.exe
%ProgramFiles%\Teradata\Client\<version>\bin64
Library
ppruntim.dll
%ProgramFiles%\Teradata\Client\<version>\pp2_64
Library
ppruntim.lib
%ProgramFiles%\Teradata\Client\<version>\pp2_64
Sample
LABSBTEQ
%ProgramFiles%\Teradata\Client\<version>\pp2_64
PPCLB1
PPCLB2
PPCLB3
PPCLB4
PPCLB5
PPCLB6
PPCLB7
PPCLB8
PPCLB9
Teradata Call-Level Interface version 2 (CLIv2)
The following table lists Teradata Call-Level Interface version 2 (CLIv2) installed for 32-bit
platforms.
168
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
CLIv2 for Windows 32-bit platforms
File Type
File Name
Default Folder
CLI Data
clispb.dat
%ProgramFiles%\Teradata\Client\<version>\cliv2
clisamp
clisamp.c
%ProgramFiles%\Teradata\Client\<version>\cliv2\clisamp
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
wincli32.lib
%ProgramFiles%\Teradata\Client\<version>\cliv2\lib
User Exit
CliLgnEx.c
%ProgramFiles%\Teradata\Client\<version>\cliv2\UserExit
CliPPS.c
tdusr.def
tdusr.rc
userexit.mak
Dynamic
Link
Library
wincli32.dll
%ProgramFiles%\Teradata\Client\<version>\cliv2
tdusr32.dll
terasso.dll
localisation.dll
The following table lists Teradata Call-Level Interface version 2 (CLIv2) installed for 64-bit
platforms.
CLIv2 for Windows 64-bit platforms
File Type
File Name
Default Folder
CLI Data
clispb.dat
%ProgramFiles%\Teradata\Client\<version>\cliv2
Teradata Tools and Utilities Installation Guide for Microsoft Windows
169
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
CLIv2 for Windows 64-bit platforms
clisamp
clisamp.c
%ProgramFiles%\Teradata\Client\<version>\cliv2\clisamp
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
wincli32.lib
%ProgramFiles%\Teradata\Client\<version>\cliv2\lib
User Exit
CliLgnEx.c
%ProgramFiles%\Teradata\Client\<version>\cliv2\UserExit
CliPPS.c
tdusr.def
tdusr.rc
userexit.mak
Dynamic
Link Library
wincli32.dll
%ProgramFiles%\Teradata\Client\<version>\cliv2
tdusr32.dll
terasso.dll
localisation.dll
Teradata Data Connector
The following table lists Teradata Data Connector installed for 32-bit platforms.
Teradata Data Connector for Windows 32-bit and 64-bit platforms
File Type
File Name
Default Folder
Header
pmdcomt.h
%ProgramFiles%\Teradata\Client\<version>\inc
pmddamt.h
Library
libpm.dll
%ProgramFiles%\Teradata\Client\<version>\bin
The following table lists Teradata Data Connector installed for 64-bit platforms.
170
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Data Connector for Windows 64-bit platforms
File Type
File Name
Default Folder
Header
pmdcomt.h
%ProgramFiles%\Teradata\Client\<version>\inc
pmddamt.h
Library
libpm.dll
%ProgramFiles%\Teradata\Client\<version>\bin
Teradata FastExport
The following table lists Teradata FastExport installed for 32-bit platforms.
Teradata FastExport for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
fexp.exe
%ProgramFiles%\Teradata\Client\<version>\bin
Sample
feimod.c
%ProgramFiles%\Teradata\Client\<version>\fexp
fenotf.c
feomod.c
Teradata FastLoad
The following table lists Teradata FastLoad installed for 32-bit platforms.
Teradata FastLoad for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
fastload.exe
%ProgramFiles%\Teradata\Client\<version>\bin
Sample
blkexit.c
%ProgramFiles%\Teradata\Client\<version>\fastload
blkexit.mak
blkexitr.c
flnfyext.c
Teradata Tools and Utilities Installation Guide for Microsoft Windows
171
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Generic Security Services
The following table lists Teradata Generic Security Services folders and files installed for 32-bit
platforms.
Teradata Generic Security Services for Windows 32-bit platforms
File Type
File Name
Default Folder
version
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\<version>
dumpcfg.exe
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\<version>\bin
gethost.exe
gssp2ldap.dll
gssp2sspi.dll
gssp2td1.dll
gssp2tdl2.dll
ldap.dll
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
Microsoft.VC80.CRT.manif
est
%ProgramFiles%\Teradata\Teradata GSS\nti386\<version>\bin\Microsoft.VC80.CRT
msccm80.dll
mdvcp80.dll
msvcr80.dll
172
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Generic Security Services for Windows 32-bit platforms
help
dumpcfg.html
gethost.html
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\<version>\doc\html
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\
nt-i386\<version>\doc\pod
ldap_license.pod
regex_license.pod
sasl_license.pod
tdgssconfig.pod
tdgssversion.pod
tdlink.podl
tdsbind.pod
toc.pod
xerces_license.pod
GlobalTypes.xsd
ipfilter.actdir.schema
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\<version>\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 Installation Guide for Microsoft Windows
173
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Generic Security Services for Windows 32-bit platforms
algerrors.h
ldaperrors.h
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\<version>\inc
loadtdgsserrors.h
spnegoerrors.h
sspierrors.h
td1errors.h
td2errors.h
tdgssapi.h
tdgssdefines.h
tdgsserrors.h
loadtgss.lib
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\<version>\lib
jtests.jar
%ProgramFiles%\Teradata\Teradata GSS
\nt-i386\<version>\lib\java
Login.config
tdgssdefines.java
tdgsstf.jar
dntest.tcl
pkgIndex.tcl
version
174
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\<version>\lib\tcl\Tds
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\LCLIENT
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Generic Security Services for Windows 32-bit platforms
dumpcfg.exe
gethost.exe
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\LCLIENT\bin
gssp2ldap.dll
gssp2sspi.dll
gssp2td1.dll
gssp2tdl2.dll
ldap.dll
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
Microsoft.VC80.CRT.manif
est
%ProgramFiles%\Teradata\Teradata GSS
\nt-i386\LCLIENT\bin\Microsoft.VC80.CRT
msccm80.dll
mdvcp80.dll
msvcr80.dll
Teradata Tools and Utilities Installation Guide for Microsoft Windows
175
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Generic Security Services for Windows 32-bit platforms
help
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\LCLIENT\doc\html
dumpcfg.html
gethost.html
ldap_license.html
regex_license.html
sasl_license.html
tdgssconfig.html
tdgssversion.html
tdlink.html
tdsbind.html
toc.html
xerces_license.html
pod
%ProgramFiles%\Teradata\Teradata GSS
\nt-i386\LCLIENT\doc\pod
dumpcfg.pod
gethost.pod
ldap_license.pod
regex_license.pod
sasl_license.pod
tdgssconfig.pod
tdgssversion.pod
tdlink.podl
tdsbind.pod
toc.pod
xerces_license.pod
%ProgramFiles%\Teradata\Teradata GSS
\nt-i386\LCLIENT\etc
GlobalTypes.xsd
ipfilter.actdir.schema
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
176
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Generic Security Services for Windows 32-bit platforms
algerrors.h
ldaperrors.h
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\LCLIENT\inc
loadtdgsserrors.h
spnegoerrors.h
sspierrors.h
td1errors.h
td2errors.h
tdgssapi.h
tdgssdefines.h
tdgsserrors.h
loadtgss.lib
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\LCLIENT\lib
jtests.jar
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\LCLIENT\lib\java
Login.config
tdgssdefines.java
tdgsstf.jar
dntest.tcl
pkgIndex.tcl
TdgssUserConfigFile.xml
Teradata Tools and Utilities Installation Guide for Microsoft Windows
%ProgramFiles%\Teradata\Teradata GSS\
nt-i386\LCLIENT\lib\tcl\Tds
%ProgramFiles%\Teradata\Teradata GSS\Site
177
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Index Wizard
The following table lists Teradata Index Wizard folders and files installed for 32-bit platforms.
Teradata Index Wizard for Windows 32-bit platforms
File Type
File Name
Default Folder
Executables
DBCVXViews120.bteq
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1
DBCVXViews62.bteq
mgrcli.dll
monpm.dll
msvcr80.dll
qcfsetup.def
tdapp.dll
tddaw.dll
tdis.dll
tdmfcis.dll
tdtmgr.dll
tdwmutil.dll
tiwapiw.dll
Tiwiz.exe
tm_dialogs.dll
tseapiw.dll
tvecapiw.dll
verify.dat
Verify.exe
Help Files
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu
catalog.ccc
document.css
tiwiz-01-01.html
thru
tiwiz-14-01.html
tiwiz_help.htm
wwhelp4.jar
178
numerous *.gif and *.ico
files
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\images
expand.js
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\scripts
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Index Wizard for Windows 32-bit platforms
ailinks.js
context.js
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhdata\common
files.js
popups.js
synomyms.xml
title.js
towwhdir.js
wwhpagef.js
files.xml
ix.xml
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhdata\java
search.xml
toc.xml
index.js
search.js
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhdata\js
toc.js
search0.js
search1.js
books.xml
messages.xml
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhdata\js\search
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp
settings.xml
splash.jpg
altclose.gif
altopen.gif
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\images
splash.jpg
api.htm
version.htm
Teradata Tools and Utilities Installation Guide for Microsoft Windows
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\wwhimpl
179
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Index Wizard for Windows 32-bit platforms
alinks.htm
blank.htm
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\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
numerous *.gif
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\wwhimpl\common\images
books.js
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\wwhimpl\common\private
locale.js
options.js
popupf.js
title.js
180
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Index Wizard for Windows 32-bit platforms
bklst1s
bookgrps.js
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\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
explore6.htm
explorer.htm
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\wwhimpl\java\html
javainfo.htm
javainfo.jar
mozzila.htm
mozzillau.htm
netscape.htm
winhelp.htm
books.xml
locale.xml
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\wwhimpl\java\private
options.js
options.xml
handler.js
java.js
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\wwhimpl\java\scripts
javainfo.js
Teradata Tools and Utilities Installation Guide for Microsoft Windows
181
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Index Wizard for Windows 32-bit platforms
indexsel.htm
navigate.htm
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\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
tabsbg.gif
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\wwhimpl\js\images
locale.js
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\Help\enu\wwhelp\wwhimpl\js\private
options.js
handler.js
index1s.js
%ProgramFiles%\Teradata\Teradata Index Wizard
13.1\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
182
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata JDBC Driver
The following table lists Teradata JDBC Driver installed for 32-bit and 64-bit platforms.
Teradata JDBC Driver for Windows 32-bit and 64-bit platforms
File Type
File Name
Default Folder
Executable
terajdbc4.jar
user selectable
Sample
samples.jar
user selectable
Security
tdgssconfig.jar
user selectable
Teradata Meta Data Services
The following table lists Teradata Meta Data Services folders and files installed for 32-bit
platforms.
Teradata Meta Data Services for Windows 32-bit platforms
File Type
File Name
Default Folder
Text
Readme.txt
%ProgramFiles%\Teradata\Teradata Meta Data
Services
Binary
bignumd.dll
%ProgramFiles%\Teradata\Teradata Meta Data
Services\bin
bignumu.dll
createnoversionshortcut.bat
createversionshortcut.bat
MDS.chm
mdsBIN.txt
mdsviews.dat
metaadm.dll
metaadmd.dll
metaauditlog.dll
metaauditlogd.dll
metaauditlogu.dll
metabteqrdr.jar
metabridge.dll
metabrowse.exe
metaclient.exe
Teradata Tools and Utilities Installation Guide for Microsoft Windows
183
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
metacmn.dll
metacmnd.dll
metacmnu.dll
metacom21.tlb
metacom22.tlb
metacom23.tlb
metacom24.tlb
metacom25.tlb
metacomexport21.dll
metaconf.cpl
metacreate.dat
metacreate.exe
metacreatefb.dat
metacreatenofb.dat
metacreatepost.dat
metacreate_versions.dat
metaddl.dll
metaddld.dll
metaddlu.dll
metaddlud.pdb
metaddlud.dll
metadelete.exe
MetaDesigner.dll
metadk.dll
metadkd.dll
metadku.dll
metaexp.dll
metaextern.dll
metaexternd.dll
metaexternu.dll
metajni.dll
metajniparse.dll
metald.dll
metaldd.dll
metaldu.dll
metalib.dll
metalibd.dll
metalibu.dll
184
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
metaload.exe
metamgr.exe
metamigr1.1.dat
metamigr12.0.dat
metamigr13.0.1.dat
metamigr13.0.2.dat
metamigr13.0.dat
metamigr13.10.dat
metamigr2.0.dat
metamigr2.1.dat
metamigr5.0.dat
metamigr5.1.dat
metamigr6.0.dat
metamigr6.1.dat
metamigr6.2.dat
metamigr7.0.dat
metamigrate.exe
metamigrate_versions_off.dat
metamigrate_versions_on.dat
metaosc.dll
metaoscd.dll
metaoscu.dll
metaprs.dll
metaprsd.dll
metaprsu.dll
metasockets.dll
metasocketsd.dll
metasocketsu.dll
metaviews.exe
metaw2k.dll
metaxml.exe
metaxml21.dtd
metaxml21.xsd
MetaXMLCOM.dll
migratenoversionshortcut.bat
migrateversionshortcut.bat
sqlprs.dfa
sqlprs.llr
Teradata Tools and Utilities Installation Guide for Microsoft Windows
185
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
types21.xsd
viewshortcut.bat
Include
dbaim.h
dbaim_h.bas
%ProgramFiles%\Teradata\Teradata Meta Data
Services\include
meta.h
metaaim.h
metaaimarray.h
metaappgroup.h
metabuild.h
metaclassdesc.h
metaerr.h
metaerror_h.bas
metaextern.h
metaextern_.h
metafilterinfo.h
metaglobals.h
MetaGlobals_h.bas
metaincludes.h
metalabel.h
metalabeledobjectkey.h
metalog.h
metaobjclasskey.h
metaobject.h
metaobjectkey.h
metapersist.h
metaproperty.h
metapropertydesc.h
metarelationship.h
metarelationshipdesc.h
metarepository.h
metasecprof.h
metatypes.h
metauser.h
metavariant.h
metaverobjclasskey.h
metaversionobjectkey.h
sactivitylog.h
186
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
JDK
docs
samples
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk
metacwm.jar
metaexport.jar
metajava.jar
metaparser.jar
JDK
api
copyright.html
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\docs
index.html
tdlogo.bmp
JDK
allclasses-frame.html
allclasses-noframe.html
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\docs\api
com
constant-values.html
deprecated-list.html
help-doc.html
index-all.html
index.html
overview-frame.html
overview-summary.html
overview-tree.html
package-list
resources
serialized-form.html
stylesheet.css
Teradata Tools and Utilities Installation Guide for Microsoft Windows
187
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
JDK
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\docs\api\com\teradata\mds
doc-files
MetaBinaryArray.html
MetaClassInfo.html
MetaConstants.html
MetaDataObject.html
MetaDIMConstants.html
MetaDormantObject.html
MetaException.html
MetaFilter.FilterItem.html
MetaFilter.html
MetaFilter.MetaCompOperator.
html
MetaFilter.MetaLogicalOperato
r.html
MetaLabelObjectKey.html
metamodel
MetaObject.html
MetaObject.MetaDateStruct.ht
ml
MetaObject.MetaTimeStruct.ht
ml
MetaObjectClassKey.html
MetaObjectCollection.html
MetaObjectCollection.Inheritan
ceInfo.html
MetaObjectKey.html
MetaPropertyItem.html
MetaPublishedState.html
MetaRange.html
MetaRepository.html
MetaVersionedObject.html
MetaVersionedObjectClassKey.h
tml
MetaVersionedObjectKey.html
package-frame.html
package-summary.html
package-tree.html
security
188
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
JDK
samplecode.html
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\docs\api\com\teradata\mds\doc-files
JDK
doc-files
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\docs\api\com\teradata\mds\metamodel
MetaCommonProperties.html
MetaLabel.html
MetaModelAIM.html
MetaModelClass.html
MetaModelObject.html
MetaModelProperty.html
MetaModelProperty.SQLType.ht
ml
MetaModelProperty.Variant.ht
ml
MetaModelRelationship.html
MetaPropertyBinaryType.html
MetaPropertyBooleanType.html
MetaPropertyByteType.html
MetaPropertyDateType.html
MetaPropertyDecimalType.html
MetaPropertyDoubleType.html
MetaPropertyIntType.html
MetaPropertyShortType.html
MetaPropertyStringType.html
MetaPropertyTimeStampType.h
tml
MetaPropertyTimeType.html
MetaPropertyType.html
MetaPropertyVarBinaryType.ht
ml
MetaPropertyVarStringType.ht
ml
MetaVersioningLevel.html
package-frame.html
package-summary.html
package-tree.html
JDK
samplecode.html
Teradata Tools and Utilities Installation Guide for Microsoft Windows
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\docs\api\com\teradata\mds\metamodel
\doc-files
189
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
JDK
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\docs\api\com\teradata\mds\security
doc-files
MetaGroup.html
MetaSecurityObject.html
MetaSecurityProfile.Access.html
MetaSecurityProfile.html
MetaSecurityProfile.SecProfEntr
y.html
MetaUser.html
package-frame.html
package-summary.html
package-tree.html
JDK
samplecode.html
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\docs\api\com\teradata\mds\security\do
c-files
JDK
inherit.gif
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\docs\api\resources
JDK
src
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\samples\general
manifest
readme.txt
JDK
SampleCleanup.java
SampleModel.java
%ProgramFiles%\Teradata\Teradata Meta Data
Services\jdk\samples\general\src\mds\samples
SampleObjects.java
SampleSearch.java
Library
metadk.lib
metadkd.lib
%ProgramFiles%\Teradata\Teradata Meta Data
Services\lib
metaextern.lib
metaexternd.lib
metaosc.lib
metaoscd.lib
190
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
Sample
addcoll.cpp
apimain.cpp
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\c++
autoaim.cpp
autoaim.h
autoconst.h
createaim.cpp
delete.cpp
extdim.cpp
getclass.cpp
getcoll.cpp
getcollkeys.cpp
getprop.cpp
Makefile
Makefile.linux
mdsapi.dsp
read.cpp
readme.txt
removecoll.cpp
rewrite.cpp
sample.dsw
write.cpp
Sample
AddDIMFields.vbp
ColumnForm.frm
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\macro\example2
ColumnForm.frx
Ex2readme.txt
Ex2SampleData.txt
metacol
Module1.bas
Sample
collog.cpp
collog.h
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\macro\example2\metacol
metacol.cpp
metacol.dsp
metacol.h
Teradata Tools and Utilities Installation Guide for Microsoft Windows
191
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
GlobalData.bas
LoadForm.frm
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\macro\example3
LoadForm.frx
MainForm.frm
MainForm.frx
MetaObject.bas
readme.txt
StartModule.bas
ErrorsForm.frm
ExcelBIZMacro.vbp
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\macro\example4
GlobalData.bas
LoadForm.frm
LoadForm.frx
MainForm.frm
MainForm.frx
MetaObject.bas
readme.txt
StartModule.bas
ErrorsForm.frx
dbanalysisMDS13.asp
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\metasurf\Shortcut
ADOConnect.asp
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\metasurf\TableData
ADOLogonInfo.asp
readme.txt
table.asp
192
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
aim.ico
DatabaseForm.frm
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\vb\MetaBizExport
DatabaseForm.frx
ExportForm.frm
ExportForm.frx
GlobalData.bas
MainForm.frm
MainForm.frx
MetaBizExport.vbp
MetaBizExport.vbw
MetaObject.bas
readme.txt
SaveForm.frm
SaveForm.frx
aim.ico
ClassForm.frm
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\vb\MetaExport
ClassForm.frx
DatabaseForm.frm
DatabaseForm.frx
ExportForm.frm
ExportForm.frx
GlobalData.bas
LoginForm.frm
LoginForm.frx
MetaExport.vbp
MetaExport.vbw
MetaObject.bas
readme.txt
aim.ico
dbaim_h.bas
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\vb\VBBrowse
Form1.frm
Form1.frx
frmLogin.frm
frmLogin.frx
MetaGlobals_h.bas
Project1.vbp
readme.txt
Teradata Tools and Utilities Installation Guide for Microsoft Windows
193
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\vb\VBModel
aim.ico
dbaim_h.bas
Form1.frm
Form1.frx
MetaData.bas
MetaGlobals_h.bas
MetaModel.bas
readme.txt
SecProfs.bas
Users.bas
VBModelTest.vbp
VBModelTest.vbw
Sample
%ProgramFiles%\Teradata\Teradata Meta Data
Services\sample\xml
AutoWorldDesc.xml
AutoWorldObjects.xml
AutoWorld_I Desc.xml
AutoWorld_I Objects.xml
AutoWorld_IA Desc.xml
AutoWorld_IA Objects.xml
deleteobject1.xml
deleteobject2.xml
metabusdesc.xml
metabusobjects.xml
metaclass.xml
metadiminstances.xml
metadimobjects.xml
metadimremove.xml
metadimtypes.xml
metagroup.xml
metagroup_user.xml
metamodel.xml
metaobject.xml
metaobject1.xml
metaproperty.xml
metarelationship.xml
metarptdata.xml
metauser.xml
rm_metabusobjects.xml
194
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Meta Data Services for Windows 32-bit platforms
Tools
%ProgramFiles%\Teradata\Teradata Meta Data
Services\tools
bridge.vbs
cfg_updt.vbs
ConvertNonMDSProps.exe
ConvertNonMDSPropsReadme.
txt
CWM_Metamodel.xml
CWM_Metamodel_Updt.xml
CWM_MetaXML.xslt
metabridge.xsd
metatools_cfg.xml
MetaXML_CWM.xslt
MetaJavaWS.war
%ProgramFiles%\Teradata\Teradata Meta Data
Services\ws\gf
MetaJavaWS.war
%ProgramFiles%\Teradata\Teradata Meta Data
Services\ws\tc
Teradata MultiLoad
The following table lists Teradata MultiLoad installed for 32-bit platforms.
Teradata MultiLoad for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
mload.exe
%ProgramFiles%\Teradata\Client\<version>\bin
Sample
mlimod.c
%ProgramFiles%\Teradata\Client\<version>\mload
mlnotf.c
Teradata Tools and Utilities Installation Guide for Microsoft Windows
195
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata OLE DB Access Module
The following table lists Teradata OLE DB Access Module installed for 32-bit platforms.
Teradata OLE DB Access Module for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
oleload.exe
%ProgramFiles%\Teradata\Client\<version>\bin
Library
OLEDB_AXSMOD.dll
<%ProgramFiles%\Teradata\Client\<version>\AX
SMOD
OLEDB_AXSMODenu.dll
OLEDB_AXSMODjpn.dll
Uninst.dll
Icon
program.ico
%ProgramFiles%\Teradata\Client\<version>\AXS
MOD
Online Help
Online Help files
%ProgramFiles%\Teradata\Client\<version>\AXS
MOD\ Teradata OLE DB Access Module Help
Merge Modules
MSVC80.dll
C:\windows\WinSxS
MFC80.dll
Teradata Parallel Data Pump
The following table lists Teradata Parallel Data Pump files installed for 32-bit platforms.
Teradata Parallel Data Pump for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
tpump.exe
%ProgramFiles%\Teradata\Client\<version>\bin
Sample
tdatpump.cfg
%ProgramFiles%\Teradata\Client\<version>\tpump
tldnfyxt.c
tpumpar.csql
tpumpimd.c
Teradata Parallel Transporter API
On a 64-bit PC, both 32-bit and 64-bit Teradata Parallel Transporter ICU Library and
Teradata Parallel Transporter Operator Support Library are loaded.
On a 32-bit PC, only 32-bit Teradata Parallel Transporter ICU Library and Teradata Parallel
Transporter Operator Support Library are loaded.
The following table lists Teradata Parallel Transporter API files installed for 32-bit platforms.
196
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
API: Windows 32-bit platforms
File Type
File Name
Default Folder
Library
opcommon.dll
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel Transporter\bin
pxicu.dll
telapi.dll
telapi.lib
Library
msvcp71.dll
msvcr.71.dll
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel Transporter\bin\vc7
telapi.dll
telapi.lib
Message Catalog
opermsgs.dll
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel Transporter\msg
Header
DMLGroup.h
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel Transporter\tptapi\inc
Schema.h
Connection.h
Header
Genericdriver.h
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\generic\inc
Header
BlockLoad.h
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\blockloading\inc
Header
MultipleOperators.h
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\multiple\inc
Header
fileio.h
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\multi_node\inc
multitest.h
synchronize.h
Header
checkpoint.h
Teradata Tools and Utilities Installation Guide for Microsoft Windows
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\checkpoint\inc
197
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
API: Windows 32-bit platforms
Header
%ProgramFiles%\Teradata\Client\<version
>Teradata Parallel
Transporter\tptapi\sample\threads\inc
common.h
Mutex.h
PerfTestMessage.h
TestBase.h
TestExport.h
TestLoad.h
TestSim.h
TestStream.h
TestUpdate.h
ThreadTest.h
ThreadTestParameters.h
Header
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\inc
DMLGroup.h
Schema.h
Connection.h
Header
OptionsManager.cpp
OptionsManager.h
Header
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\common
%ProgramFiles%\Teradata\Client\<version
>Teradata Parallel
Transporter\tptapi\sample\checkpoint
checkpoint.cpp
main.cpp
input.txt
infile.littleEndian
checkpoint.vcproj
checkpoint.sln
checkpoint_vc7.vcproj
checkpoint_vc7t.vcproj
cleanupTables.bteq
setupTables.bteq
Header
GenericDriver.cpp
main.cpp
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\generic
input.txt
infile.littleEndian
generic.vcproj
generic.sln
generic_vc7.vcproj
generic_vc7t.vcproj
cleanupTables.bteq
setupTables.bteq
198
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
API: Windows 32-bit platforms
Header
BlockLoad.cpp
main.cpp
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\blockloading
input.txt
infile.littleEndian
blockload.vcproj
blockload.sln
blockload_vc7.vcproj
blockload_vc7.sln
cleanupTables.bteq
setupTables.bteq
Header
multitest.cpp
synchronize.cpp
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\multi_node
fileio.cpp
master.cpp
slave.cpp
master_input.txt
slave_input.txt
infilemaster.littleEndian
infileslave.littleEndian.1
multinode.sln
masternode.vcproj
slavenode.vcproj
multinode_vc7.sln
masternode_vc7.vcproj
slavenode_vc7.vcproj
cleanupTables.bteq
setupTables.bteq
Teradata Tools and Utilities Installation Guide for Microsoft Windows
199
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
API: Windows 32-bit platforms
Header
PerfTestMessage.cpp
TelapiThreadTest.cpp
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\threads
PerfTestMessage.cpp
TelapiThreadTest.sln
TelapiThreadTest.vcproj
TelapiThreadTest_vc7.sln
TelapiThreadTest_vc7.vcproj
TestBase.cpp
TestExport.cpp
TestLoad.cpp
TestSim.cpp
TestStream.cpp
TestUpdate.cpp
ThreadTest.cpp
ThreadTestParameters.cpp
Synchronizer.cpp
input.txt
loadData.littleEndian
cleanupTables.bteq
setupTables.bteq
Get Buffer
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel
Transporter\tptapi\sample\getbuffer
GetBuffer.cpp
main.cpp
cleanupTables.bteq
setupTables.bteq
getbuffer.sln
getbuffer.vcproj
getbuffer_vc7.sln
getbuffer_vc7.vcproj
input.txt
Include
200
GetBuffer.h
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel Transporter/tptapi/
sample/getbuffer/inc
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
API: Windows 32-bit platforms
XSP
GenericDriver.cpp
GenericDriver.h
%ProgramFiles%\Teradata\Client\<version
>\Teradata Parallel Transporter/tptapi/
sample/xsp
OptionsReader.cpp
OptionsReader.h
xsp.cpp
xsp.sln
xsp.vcproj
xsp_vc7.sln
xsp_vc7.vcproj
input.exp
input.lod
input.stm
input.upd
infile.littleEndian
The following table lists Teradata Parallel Transporter API files installed for 64-bit platforms.
API: Windows 64-bit platforms
File Type
File Name
Default Folder
Library
telapi.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin64
telapi.lib
Library
pxicu.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin64
Library
opcommon.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin64
Message
Catalog
opermsgs.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\msg64
Header
DMLGroup.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\inc
Schema.h
Connection.h
Header
generic.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\generic\inc
Header
BlockLoad.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\blockloading\inc
Header
MultipleOperators.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\multiple\inc
Teradata Tools and Utilities Installation Guide for Microsoft Windows
201
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
API: Windows 64-bit platforms
Header
fileio.h
multitest.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\multi_node\inc
synchronize.h
Header
checkpoint.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\checkpoint\inc
Header
common.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\threads\inc
Mutex.h
PerfTestMessage.h
TestBase.h
TestExport.h
TestLoad.h
TestSim.h
TestStream.h
TestUpdate.h
ThreadTest.h
ThreadTestParamet
ers.h
Header
DMLGroup.h
Schema.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\inc
Connection.h
Header
OptionsManager.cp
p
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\common
OptionsManager.h
Header
checkpoint.cpp
main.cpp
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\checkpoint
input.txt
infile.littleEndian
checkpoint64.vcproj
checkpoint64.sln
cleanupTables.bteq
setupTables.bteq
202
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
API: Windows 64-bit platforms
Header
GenericDriver.cpp
main.cpp
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\generic
input.txt
infile.littleEndian
generic64.vcproj
generic64.sln
cleanupTables.bteq
setupTables.bteq
Header
BlockLoad.cpp
main.cpp
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\blockloading
input.txt
infile.littleEndian
blockload64.vcproj
blockload64.sln
cleanupTables.bteq
setupTables.bteq
Header
multitest.cpp
synchronize.cpp
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\multi_node
fileio.cpp
master.cpp
slave.cpp
master_input.txt
slave_input.txt
infilemaster.littleEn
dian
infileslave.littleEndi
an.1
multinode64.sln
masternode64.vcpro
j
slavenode64.vcproj
cleanupTables.bteq
setupTables.bteq
Teradata Tools and Utilities Installation Guide for Microsoft Windows
203
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
API: Windows 64-bit platforms
Header
PerfTestMessage.cpp
TelapiThreadTest.cp
p
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptapi\sample\threads
PerfTestMessage.cpp
TelapiThreadTest64.
sln
TelapiThreadTest64.
vcproj
TestBase.cpp
TestExport.cpp
TestLoad.cpp
TestSim.cpp
TestStream.cpp
TestUpdate.cpp
ThreadTest.cpp
ThreadTestParamet
ers.cpp
Synchronizer.cpp
input.txt
loadData.littleEndia
n
cleanupTables.bteq
setupTables.bteq
Get Buffer
GetBuffer.cpp
main.cpp
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter/tptapi/sample/getbuffer
cleanupTables.bteq
setupTables.bteq
getbuffer64.sln
getbuffer.64vcproj
input.txt
Include
204
GetBuffer.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter/tptapi/sample/getbuffer/inc
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
API: Windows 64-bit platforms
XSP
GenericDriver.cpp
GenericDriver.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter/tptapi/sample/xsp
OptionsReader.cpp
OptionsReader.h
xsp.cpp
xsp64.sln
xsp64.vcproj
input.exp
input.lod
input.stm
input.upd
infile.littleEndian
Teradata Parallel Transporter Export Operator
The following table lists Teradata Parallel Transporter Export Operator files installed for 32bit platforms.
Export Operator: Windows 32-bit platforms
File Type
File Name
Default Folder
Library
exportop.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\bin
Sample
expnfyxt.c
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\sample
The following table lists Teradata Parallel Transporter Export Operator files installed for 64bit platforms.
Export Operator: Windows 64-bit platforms
File Type
File Name
Default Folder
Library
exportop.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\bin64
Sample
expnfyxt.c
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\sample
Teradata Tools and Utilities Installation Guide for Microsoft Windows
205
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Parallel Transporter Infrastructure
The following table lists Teradata Parallel Transporter Infrastructure files installed for 32-bit
platforms.
Teradata Parallel Transporter Infrastructure: Windows 32-bit platforms
File Type
File Name
Default Folder
Configuration
twbcfg.ini
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter
twboper.ini
Folder
checkpoint
logs
Executable
coordinator.exe
executor.exe
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin
planexecutor.exe
tbuild.exe
ptmcmd.exe
ptmgts.exe
ptmjlgr.exe
ptmlvs.exe
ptmexec.exe
ptmtims.exe
tdload.exe
tlogview.exe
twbstat.exe
twbkill.exe
twbmdlgr.exe
tbuildexe.exe
tlogviewexe.exe
twbcmdexe.exe
twbkillexe.exe
twbstatexe.exe
Executable
twbrmcpexe.exe
twbpathexe.exe
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin
tptlaunch.exe
twbpath.exe
twbrmcp.exe
206
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Parallel Transporter Infrastructure: Windows 32-bit platforms
Header
pxdtypes.h
pxtypes.h
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\sdk\inc
pxmacros.h
pxoper.h
pxos.h
pxstc.h
pxdef.h
pxlogdef.h
pxutypes.h
pxversion.h
Library
feomop.dll
flimop.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin
logview.dll
mlimop.dll
MSVCIRT.DLL
MSVCIRTD.DLL
MSVCP60.DLL
MSVCP60D.DLL
MSCVCRT.DLL
MSCVCRTD.DLL
Library
oncrpc.dll
pxcommon.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin
ptmin.dll
ptmos.dll
ptmpi.dll
ptmpo.dll
pxicu.dll
dataconop.dll
ddlop.dll
odbcop.dll
opcommon.dll
oscmdop.dll
insertop.dll
selectop.dll
tableqry.dll
guisrv.dll
wwhelp.dll
Teradata Tools and Utilities Installation Guide for Microsoft Windows
207
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Parallel Transporter Infrastructure: Windows 32-bit platforms
Message
Catalog
opermsgs.dll
Configuration
tptwizard.properties
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptwizard\config
Directory
help
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptwizard
Java Binary
tdgssjava.jar
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptwizard\jars
twbmsgs.dll
terajdbc4.jar
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\msg
tptwizard.jar
tdgssconfig.jar
Icon
tptwizard.ico
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptwizard
Startup
runtbuild.cmd
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptwizard
tptwizard.cmd
Transformation
attributes.twb.xsl
base.twb.xsl
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\tptwizard\transformation
columns.twb.xsl
dbms.twb.xsl
file.twb.xsl
job.twb.xsl
jobstep.twb.xsl
logger.twb.xsl
logview.twb.xsl
objects.twb.xsl
operation.twb.xsl
operator.twb.xsl
schema.twb.xsl
table.twb.xsl
tableset.twb.xsl
208
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Parallel Transporter Infrastructure: Windows 32-bit platforms
Sample
GT11.txt
GT44.txt
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\sample\etl
GT62.txt
GT93.txt
GT94.txt
GT95.txt
GT96.txt
GT97.txt
jobvars.txt
Sample
sampleoperator.dsw
sampleoperator.dsp
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\sdk\src
samplefilter.cpp
Sample
data.in
samplescript.txt
Sample
sql1.txt
sql2.txt
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\sdk\sample
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\sample\metadata
twb_status.txt
twb_targets.txt
Version Text
version
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter
Template File
$DATACONNECTO
R_PRODUCER.txt
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\template
$DDL.txt
$EXPORT.txt
$FILE_READER.txt
$FILE_WRITER.txt
$INSERTER.txt
$LOAD.txt
$SELECTOR.txt
$STREAM.txt
$UPDATE.txt
Batch File
tdlog.bat
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin
Word
Document
readme.doc
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\sdk
Teradata Tools and Utilities Installation Guide for Microsoft Windows
209
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Parallel Transporter Load Operator
The following table lists Teradata Parallel Transporter Load Operator files installed for 32-bit
platforms.
Load Operator: Windows 32-bit platforms
File Type
File Name
Default Folder
Library
loadop.dll
<Boot Drive>:\Program Files\Teradata\Teradata Parallel
Transporter\<version>\bin
Sample
ldnfyext.c
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\samples
The following table lists Teradata Parallel Transporter Load Operator files installed for 64-bit
platforms.
Load Operator: Windows 64-bit platforms
File Type
File Name
Default Folder
Library
loadop.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin64
Sample
ldnfyext.c
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\samples
Teradata Parallel Transporter Stream Operator
The following table lists Teradata Parallel Transporter Stream Operator installed for 32-bit
platforms.
Stream Operator: Windows 32-bit platforms
File Type
File Name
Default Folder
Library
streamop.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin
Sample
stmnfyxt.c
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\samples
The following table lists Teradata Parallel Transporter Stream Operator installed for 64-bit
platforms.
210
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Stream Operator: Windows 64-bit platforms
File Type
File Name
Default Folder
Library
streamop.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\bin64
Sample
stmnfyxt.c
%ProgramFiles%\Teradata\Client\<version>\Teradata
Parallel Transporter\samples
Teradata Parallel Transporter Update Operator
The following table lists Teradata Parallel Transporter Update Operator installed for 32-bit
platforms.
Update Operator: Windows 32-bit platforms
File Type
File Name
Default Folder
Library
updateop.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\bin
Sample
updnfyxt.c
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\samples
The following table lists Teradata Parallel Transporter Update Operator files installed for 64bit platforms.
Update Operator: Windows 64-bit platforms
File Type
File Name
Default Folder
Library
updateop.dll
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\bin64
Sample
updnfyxt.c
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel
Transporter\samples
Teradata Tools and Utilities Installation Guide for Microsoft Windows
211
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Performance Monitor Object
The following table lists Teradata Performance Monitor Object folders and files installed for
32-bit platforms.
Teradata Performance Monitor for Windows 32-bit platforms
File Type
File Name
Default Folder
Executables
Mfc42u.dll
%ProgramFiles%\Teradata\Teradata Performance
Monitor Object
Monitor.dll
MonitorUserGuide.pdf
Msvcrt.dll
TDMon8.dll
Verify.dat
Verify.exe
Teradata Query Director
The following table lists Teradata Query Director folders and files installed for 32-bit
platforms.
Teradata Query Director for Windows 32-bit platforms
File Type
File Name
Default Folder
QD.exe
%Program File%s\Teradata\Teradata Query Director
qdmsg409.dll
sockclient.exe
tqdrsrvport.exe
Teradata Query Scheduler Administrator
The following table lists Teradata Query Scheduler Administrator files installed for 32-bit
platforms.
Teradata Query Scheduler Administrator for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
tqsadm.exe
%ProgramFiles%\Teradata\Teradata Query Scheduler
Admin <version>
(Program Files can be configured by the system
administrator to be on a drive other than the boot drive.)
tdqmdb.exe
212
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Query Scheduler Administrator for Windows 32-bit platforms
Readme
readme.txt
%ProgramFiles%\Teradata\Teradata Query Scheduler
Admin <version>
Teradata Query Scheduler Client
The following table lists Teradata Query Scheduler Client files installed for 32-bit platforms.
Teradata Query Scheduler Client for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
tdqmcomm.exe
%ProgramFiles%\Teradata\Teradata Query Scheduler
<version>\client
tdqmops.exe
tdqmview.exe
Library
tdqmcomm.dll
%SystemRoot%\system32
tdqmsr.dll
tdqmsubm.dll
Readme
readme.txt
%ProgramFiles%\Teradata\Teradata Query Scheduler
<version>
Teradata Query Scheduler Server
The following table lists Teradata Query Scheduler Server files installed for 32-bit platforms.
Teradata Query Scheduler Server for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
tdqmjob.exe
%ProgramFiles%\Teradata\Teradata Query Scheduler
<version>\server
tdqmlsnr.exe
tdqmreqp.exe
tdqmserv.exe
Library
tdqmserv.dll
%SystemRoot%\system32
tdsqlprsu.dll
bignumu.dll
Parser
sqlprs.dfa
sqlprs.llr
Teradata Tools and Utilities Installation Guide for Microsoft Windows
%ProgramFiles%\Teradata\Client\<version>\Teradata Query
Scheduler\server
213
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata SQL Assistant
The following table lists Teradata SQL Assistant folders and files installed for 32-bit platforms.
Teradata SQL Assistant for Windows 32-bit platforms
File Type
File Name
Default Folder
accsess.lng
ansi.lng
accsess.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.Spread.dll
informix.lng
Infragistics2.Shared.v9.1.dll
Infragistics2.Win.Misc.v9.1.dll
Infragistics2.Win.UltraWinDock.v9.1.dll
Infragistics2.Win.UltraWinEditors.v9.1.dll
Infragistics2.Win.UltraWinListView.v9.1.dll
Infragistics2.Win.UltraWinMaskedEditv9.1.
dll
214
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata SQL Assistant for Windows 32-bit platforms
Executables
Infragistics2.Win.UltraWinStatusBar.v9.1.d
ll
%ProgramFiles%\Teradata\Client\13.
1\Teradata SQL Assistant
Infragistics2.Win.UltraWinTabbedMdi.v9.1.
dll
Infragistics2.Win.UltraWinTabControl.v9.1.
dll
Infragistics2.Win.UltraWinToolbars.v9.1.dll
Infragistics2.Win.UltraWinTreek.v9.1.dll
Infragistics2.Win.v9.1.dll
ingres.lng
Interop.CodeMax4.dll
mysql.lng
neoview.lng
Office2000.isl
Office2003.isl
Office2007.isl
oracle.lng
outmsg.lng
postgresql.lng
ReleaseNotes.htm
report.lng
SQLA.exe
SQLA.exe.config
SQLA.pdb
SQLA.XmlSeralizers.dll
sqla_enu.chm
sqlacm_en.dll
sqlserver.lng
startup.exe
stdole.dll
sybase.lng
teradata.lng
verify.dat
verify.exe
Windows7.isl
WindowsVista.isl
Teradata Tools and Utilities Installation Guide for Microsoft Windows
215
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Statistics Wizard
The following table lists Teradata Statistics Wizard folders and files installed for 32-bit
platforms.
Teradata Statistics Wizard for Windows 32-bit platforms
File Type
File Name
Default Folder
Executables
DBCVXViews120.bteq
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1
DBCVXViews62.bteq
mgrcli.dll
msvcr80.dll
qcfsetup.def
tdapp.dll
tddaw.dll
tdis.dll
tdmfcis.dll
tdtmgr.dll
tdwmutil.dll
tiwapiw.dll
tm_dialogs.dll
tm_stats.dll
TSEAPIw.dll
tswiz.exe
tvecapiw.dll
verify.dat
Verify.exe
Help Files
catalog.ccc
document.css
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu
tswiz-01-01.html
thru
tswiz-14-01.html
tswiz_help.htm
wwhelp4.jar
216
numerous *.gif and
*.ico files
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\images
expand.js
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\scripts
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Statistics Wizard for Windows 32-bit platforms
ailinks.js
context.js
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhdata\common
files.js
popups.js
synomyms.xml
title.js
towwhdir.js
wwhpagef.js
files.xml
ix.xml
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhdata\java
search.xml
toc.xml
index.js
search.js
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhdata\js
toc.js
search0.js
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhdata\js\search
books.xml
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhelp
messages.html
settings.html
altclose.gif
altopen.gif
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhelp\images
splash.jpg
api.htm
version.htm
Teradata Tools and Utilities Installation Guide for Microsoft Windows
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhelp\wwhimpl
217
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Statistics Wizard for Windows 32-bit platforms
alinks.htm
blank.htm
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\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
numerous *.gif
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhelp\wwhimpl\common\images
books.js
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhelp\wwhimpl\common\private
locale.js
options.js
popupf.js
title.js
218
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Statistics Wizard for Windows 32-bit platforms
bklst1s
bookgrps.js
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\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 Statistics Wizard
13.1\Help\enu\wwhelp\wwhimpl\java\html
javainfo.htm
javainfo.jar
mozzila.htm
mozzillau.htm
netscape.htm
wwhelp.htm
books.xml
locale.xml
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhelp\wwhimpl\java\private
options.js
options.xml
handler.js
java.js
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhelp\wwhimpl\java\scripts
javainfo.js
Teradata Tools and Utilities Installation Guide for Microsoft Windows
219
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Statistics Wizard for Windows 32-bit platforms
indexsel.htm
navigate.htm
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\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
tabsbg.gif
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhelp\wwhimpl\js\images
locale.js
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\Help\enu\wwhelp\wwhimpl\js\private
options.js
handler.js
index1s.js
%ProgramFiles%\Teradata\Teradata Statistics Wizard
13.1\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
The following table lists Teradata System Emulator folders and files installed for 32-bit
platforms.
220
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata System Emulator for Windows 32-bit platforms
File Type
File Name
Default Folder
Executables
DBCVXViews120.bteq
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1
DBCVXViews62.bteq
mgrcli.dll
monpm.dll
msvcr80.dll
qcfsetup.def
tdapp.dll
tddaw.dll
tdis.dll
tdmfcis.dll
tdtmgr.dll
tdwmutil.dll
tm_dialogs.dll
tseapiw.dll
TSET.exe
tvecapiw.dll
verify.dat
Verify.exe
Help Files
catalog.ccc
document.css
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU
tset-01-01.html
thru
tset-14-01.html
tset_help.htm
wwhelp4.jar
numerous *.gif and *.ico
files
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\images
expand.js
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\scripts
Teradata Tools and Utilities Installation Guide for Microsoft Windows
221
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata System Emulator for Windows 32-bit platforms
ailinks.js
context.js
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhdata\common
files.js
popups.js
synomyms.xml
title.js
topics.js
towwhdir.js
wwhpagef.js
files.xml
ix.xml
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhdata\java
search.xml
toc.xml
index.js
search.js
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhdata\js
toc.js
search0.js
search1.js
books.xml
messages.html
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhdata\js\search
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhelp
settings.html
altclose.gif
altopen.gif
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhelp\images
splash.jpg
api.htm
version.htm
222
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhelp\wwhimpl
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata System Emulator for Windows 32-bit platforms
alinks.htm
blank.htm
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\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
numerous *.gif
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhelp\wwhimpl\common\images
books.js
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhelp\wwhimpl\common\private
locale.js
options.js
popupf.js
title.js
Teradata Tools and Utilities Installation Guide for Microsoft Windows
223
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata System Emulator for Windows 32-bit platforms
bklst1s
bookgrps.js
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\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 13.1\Help\ENU\wwhelp\wwhimpl\java\html
javainfo.htm
javainfo.jar
mozzila.htm
mozzillau.htm
netscape.htm
wwhelp.htm
books.xml
locale.xml
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhelp\wwhimpl\java\private
options.js
options.xml
handler.js
java.js
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhelp\wwhimpl\java\scripts
javainfo.js
224
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata System Emulator for Windows 32-bit platforms
indexsel.htm
navigate.htm
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\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
tabsbg.gif
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhelp\wwhimpl\js\images
locale.js
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\Help\ENU\wwhelp\wwhimpl\js\private
options.js
handler.js
index1s.js
%ProgramFiles%\Teradata\Teradata System Emulation
Tool 13.1\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 Visual Explain
The following table lists Teradata Visual Explain folders and files installed for 32-bit
platforms.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
225
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Visual Explain for Windows 32-bit platforms
File Type
File Name
Default Folder
Executables
DBCVXViews12
0.bteq
%ProgramFiles%\Teradata\Teradata Visual Explain 13.1
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
tm_dialogs.dll
tseapiw.dll
tvecapiw.dll
Vecomp.exe
verify.dat
Verify.exe
Help Files
catalog.ccc
document.css
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU
ve-01-01.html
thru
ve-14-01.html
ve_help.htm
wwhelp4.jar
226
numerous *.gif
and *.ico files
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\images
expand.js
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\scripts
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Visual Explain for Windows 32-bit platforms
ailinks.js
context.js
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhdata\common
files.js
popups.js
synomyms.xml
title.js
topics.js
towwhdir.js
wwhpagef.js
files.xml
ix.xml
%ProgramFiles%\TeradataTeradata Visual Explain
13.1\Help\ENU\wwhdata\java
search.xml
toc.xml
index.js
search.js
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhdata\js
toc.js
search0.js
search1.js
books.xml
messages.html
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhdata\js\search
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhelp
settings.html
altclose.gif
altopen.gif
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhelp\images
splash.jpg
api.htm
version.htm
Teradata Tools and Utilities Installation Guide for Microsoft Windows
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhelp\wwhimpl
227
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Visual Explain for Windows 32-bit platforms
alinks.htm
blank.htm
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\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
numerous *.gif
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhelp\wwhimpl\common\images
books.js
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhelp\wwhimpl\common\private
locale.js
options.js
popupf.js
title.js
228
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Visual Explain for Windows 32-bit platforms
bklst1s
bookgrps.js
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\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%\TeradataTeradata Visual Explain
13.1\Help\ENU\wwhelp\wwhimpl\java\html
javainfo.htm
javainfo.jar
mozzila.htm
mozzillau.htm
netscape.htm
wwhelp.htm
books.xml
locale.xml
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhelp\wwhimpl\java\private
options.js
options.xml
handler.js
java.js
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhelp\wwhimpl\java\scripts
javainfo.js
Teradata Tools and Utilities Installation Guide for Microsoft Windows
229
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata Visual Explain for Windows 32-bit platforms
indexsel.htm
navigate.htm
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\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
tabsbg.gif
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhelp\wwhimpl\js\images
locale.js
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\Help\ENU\wwhelp\wwhimpl\js\private
options.js
handler.js
index1s.js
%ProgramFiles%\Teradata\Teradata Visual Explain
13.1\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
230
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
Teradata WebSphere MQ Access Module
The following table lists Teradata Websphere MQ Access Module files installed for 32-bit
platforms.
Teradata WebSphere MQ Access Module for Windows 32-bit platforms
File Type
File Name
Default Folder
Library
libmqs.dll
%ProgramFiles%\Teradata\Client\<version>\AXSMOD
libmqsc.dll
Teradata Workload Analyzer
The following table lists Teradata Workload Manager files installed for 32-bit platforms.
Teradata Workload Analyzer for Windows 32-bit platforms
File Type
File Name
Default Folder
Executable
twa.exe
%ProgramFiles%\Teradata\Client\<version>\Teradata
Workload Analyzer
Verify.exe
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
msvcr80.dll
Teradata Tools and Utilities Installation Guide for Microsoft Windows
%SystemRoot%\System32
231
Chapter 15: Checking Files and Folders
Step 1: Verifying Installation of Individual Products
232
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 16
Uninstalling Previous Versions
Teradata Tools and Utilities Release 13.00.00 required that all products except for Teradata
Generic Security Services (TeraGSS) be uninstalled before installing the new release. This is
not required for Teradata Tools and Utilities Release 13.10.00.
Task 1: Uninstall Previous Versions
On Windows, previous versions of Teradata Tools and Utilities are automatically uninstalled
or upgraded by the Teradata Tools and Utilities installation.
•
All Release 13.10 Packages Uninstall pre-13.00 Releases of Teradata Tools and Utilities
Products Automatically - If versions of Teradata Tools and Utilities products earlier than
Release 13.00 exist on a machine, each Release 13.10 package being installed will
automatically uninstall all pre-Teradata Tools and Utilities 13.00 versions of the package,
before installing the Release 13.10 version of the product.
•
Release 13.10 Packages Upgrade Release 13.00 Products Automatically - If Release 13.00
Teradata Tools and Utilities products exist on the machine, each Release 13.10 package
upgrades the 13.00 package to 13.10, except for the following packages which support
side-by-side installations and multiple versions coexistence:
•
TeraGSS
•
SQLA
•
TPT packages
•
DBM packages
Step 1: Observe the Uninstallation Order
Follow the Uninstall Order. If you’ve decided to manually uninstall Teradata Tools and
Utilities products, use Add or Remove Programs in the Control Panel to uninstall them in the
following order:
1
Any Teradata Tools and Utilities products other than the following 6
2
Teradata Data Connector (piom)
3
ODBC Driver for Teradata (tdodbc)
4
.NET Data Provider for Teradata
5
Call-Level Interface version 2 (cliv2)
6
Teradata Generic Security Services (teragss)
Teradata Tools and Utilities Installation Guide for Microsoft Windows
233
Chapter 16: Uninstalling Previous Versions
Task 1: Uninstall Previous Versions
7
Shared ICU Libraries for Teradata (tdicu)
Note: Additionally, TQS Server must be uninstalled before TQS Client.
Step 2: Uninstall Individual Products - Windows
On Windows, all Teradata Tools and Utilities products are uninstalled individually, there is no
way to uninstall all products at one time. Use the following procedure to uninstall individual
Teradata Tools and Utilities products.
Procedure - Uninstalling Individual Teradata Tools and Utilities Products
Follow these steps to uninstall Teradata Tools and Utilities products.
234
1
Go to the Control Panel.
2
Click Add or Remove Programs.
3
In Change or Remove Programs, find and then click on the product to be removed
4
Click Change/Remove.
5
If prompted, click OK to confirm the uninstallation of the product, or if prompted to
Repair or Remove, click Remove and then Next>, then click OK to confirm the
uninstallation of the product.
6
In the InstallShield Wizard, click Finish.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 17
Installation Kit
The Teradata Tools and Utilities 13.10 installation kit contains the documentation and CD
media for Teradata Tools and Utilities.
Task 1: Inspect the Installation Kit
The kit includes the following documentation:
•
Teradata Tools and Utilities Release Definition, Release 13.10
•
Teradata Tools and Utilities Documentation CD
Also included are one or more of the following purchased CDs. Each CD contains product
versions for one or more network-attached platforms.
•
CD#1 - Teradata Utility Pack for Windows - Vol 1 of 3
•
CD#2 - Teradata Utility Pack for HP-UX-Linux - Vol 2 of 3
•
CD#3 - Teradata Utility Pack for AIX-Solaris - Vol 3 of 3
•
CD#4 - Database Management (Windows)
•
CD#5 - Preprocessors for Windows - Vol 1 of 3
•
CD#6 - Preprocessors for HP-UX-Linux - Vol 2 of 3
•
CD#7 - Preprocessors for AIX-Solaris - Vol 3 of 3
•
CD#8 - Load/Unload for Windows - Vol 1 of 3
•
CD#9 - Load/Unload for HP-UX-Linux - Vol 2 of 3
•
CD#10 - Load/Unload for AIX-Solaris - Vol 3 of 3
•
CD#11 - Parallel Transporter for Windows - Vol 1 of 3
•
CD#12 - Parallel Transporter for HP-UX-Linux - Vol 2 of 3
•
CD#13 - Parallel Transporter for AIX-Solaris - Vol 3 of 3
•
CD#14 - Query Director Linux-Windows
•
CD#15 - Tape Storage Management Enablers (Linux-Windows)
•
CD#16 - Teradata Meta Data Services (Linux-MPRAS (RSG)-Windows)
If all of the CDs ordered were not received, contact the Teradata Solutions Customer Services
Remote Services Center (TSCS-RSC). For information on how to contact TSCS-RSC, refer to
the Teradata Tools and Utilities Release Definition, Release 13.10.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
235
Chapter 17: Installation Kit
Task 2: Determine the CD Contents
Task 2: Determine the CD Contents
The following table lists the Teradata Tools and Utilities products and dependencies contained
on the Installation Kit CDs. Products indicated in the “W” column can be downloaded from
the Teradata Download Center.
Teradata Tools and Utilities CDs
Product
W
Basic Teradata Query
1
2
3
4
x
x
x
x
5
6
7
8
9
1
0
x
x
x
1
1
1
2
1
3
1
4
1
5
1
6
Teradata Meta Data Services Core
Files
x
• Meta Data Development Kit
x
• Meta Surf Files
x
• Dim Update Files
x
Named Pipes Access Module
x
x
x
x
x
x
x
Shared ICU Libraries for Teradata
x
x
x
x
Teradata Administrator
x
.NET Data Provider for Teradata
x
ODBC Driver for Teradata
OLE DB Provider for Teradata
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Teradata Archive/Recovery Utility
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Teradata FastExport
x
x
x
Teradata FastLoad
x
x
x
x
x
x
Teradata MultiLoad
x
x
x
Teradata OLE DB Access Module
x
Teradata COBOL Preprocessor2
Teradata Data Connector
x
Teradata Generic Security Services
x
x
x
x
x
Teradata Index Wizard
Teradata JDBC Driver
236
x
x
Teradata C Preprocessor2
Teradata Call-Level Interface version
2
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 17: Installation Kit
Task 2: Determine the CD Contents
Teradata Tools and Utilities CDs
1
1
1
2
1
3
Teradata Parallel Transporter
(Infrastructure)
x
x
x
• API
x
x
x
• Export Operator
x
x
x
• Load Operator
x
x
x
• Stream Operator
x
x
x
• Update Operator
x
x
x
Product
W
1
2
3
4
Teradata Parallel Data Pump
Teradata Performance Monitor
Object
5
6
7
8
9
1
0
x
x
x
1
5
1
6
x
Teradata Query Director
x
Teradata Query Scheduler
Administrator
x
Teradata Query Scheduler Client
x
Teradata Query Scheduler Server
x
Teradata SQL Assistant
1
4
x
Teradata Statistics Wizard
x
Teradata System Emulation Tool
x
Teradata Visual Explain
x
Teradata Workload Analyzer
x
Teradata WebSphere MQ Access
Module
x
x
x
x
x
x
Note: Products that can be Installed from the Teradata Download Center - See Installing from
the Teradata Download Center for information on products that can be installed from the
Teradata Download Center.
Note: Named Pipes Access Module - The installation of Named Pipes Access Module installs a
single version of Named Pipes Access Module that works for both the standalone utilities and
Teradata Parallel Transporter.
Note: Teradata WebSphere MQ Access Module - The installation of Teradata WebSphere MQ
Access Module installs a single version of Teradata WebSphere MQ Access Module that works
for both the standalone utilities and Teradata Parallel Transporter.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
237
Chapter 17: Installation Kit
Task 2: Determine the CD Contents
Note: Teradata Archive and Recovery Utility - Teradata Archive and Recovery Utility is
included to support Teradata’s Backup Applications. Teradata ARC is not sold as an individual
standalone product for Windows, or SUSE Linux, although it is available as a standalone
application on mainframes supported by Teradata.
Note: Teradata Parallel Transporter Wizard - Teradata Parallel Transporter Wizard is only
supported on Windows.
Note: Teradata Parallel Transporter Operators - Teradata Parallel Transporter ICU Library,
Operator Support Library, Data Connector Operator, FastExport OUTMOD Adapter
Operator, FastLoad INMOD Adapter Operator, the MultiLoad INMOD Adapter Operator,
SQL Inserter Operator, SQL Selector Operator, ODBC Operator, OS Command Operator,
DDL Operator, and the Teradata Parallel Transporter Wizard are installed as part of the
Teradata Parallel Transporter Infrastructure on Windows.
238
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 18
Product Descriptions
Teradata Tools and Utilities is a set of integrated warehouse management and utility software
products designed to operate with the Teradata Database. The utilities enable users to get data
from any source; extract and load the data quickly; then analyze the data.
Task 1: Review Product Descriptions
The following table lists descriptions of Teradata Tools and Utilities.
Products
Description
Basic Teradata Query
A general-purpose, command-based program that allows
users on a workstation to communicate with one or more
Teradata Database systems, and to format 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.
.NET Data Provider for Teradata
Microsoft® .NET Framework applications utilize .NET
Data Providers for uniform and standard access to data
sources such as Teradata®. The .NET Data Provider for
Teradata is the data access component of the .NET
Framework Class Library (FCL).
ODBC Driver for Teradata
Enables UNIX®, Linux® and Microsoft® Windows®
operating systems to communicate with the Teradata
Database across local area networks (LAN) using the open
standards ODBC interface. With the ODBC Driver for
Teradata, connect Microsoft Windows, Linux, and UNIX
applications to the Teradata Database.
Note: Can be downloaded and installed from the web.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
239
Chapter 18: Product Descriptions
Task 1: Review Product Descriptions
Products
Description
OLE DB Provider for Teradata
The OLE DB database is a set of Component Object Model
(COM) interfaces and objects that provide applications
with uniform, standard access to any data store. In this
case, the data store is in Teradata Database. OLE DB
Provider for Teradata specifically allows access to data
stores that do not use Structured Query Language (SQL).
Using this product, an application requests database
information from an intermediate program, which in turn
accesses Teradata Database. The intermediate program
receives the response from 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 an easy-to-use Windows-based graphical
interface to the Teradata Database Data Dictionary for
performing a multitude of 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 Teradata’s Backup
Applications solutions and the Teradata Database.
Note: Teradata Archive and Recovery Utility (ARC) is
included to support Teradata’s Backup Applications.
Teradata ARC is not sold as an individual standalone
product for Windows, or Linux, although it is available as a
standalone application on mainframes supported by
Teradata.
Teradata C Preprocessor2
Provides the application programmer with a simplified
method of reading and changing information stored in a
Teradata Database by interpreting and expanding SQL
statements that have been incorporated in an application
program.
Teradata Call-Level Interface version 2
A library of routines that enable an application program to
access data on a Teradata Database.
Note: Can be downloaded and installed from the web.
240
Teradata Data Connector
Reads and writes flat files, to provide the input/output
interface for access modules.
Teradata FastExport
A command-driven utility that uses multiple sessions to
quickly transfer large amounts of data from tables and
views of the Teradata Database to a client based
application.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 18: Product Descriptions
Task 1: Review Product Descriptions
Products
Description
Teradata FastLoad
A command-driven utility that quickly loads large
amounts of data to empty tables in a Teradata Database.
FastLoad uses multiple sessions to load data; however, it
loads data into only one table on a Teradata Database per
job.
Teradata Generic Security Services
Client
Teradata's implementation of industry-standard Generic
Security Services APIs in C language. It provides enhanced
security services interfaces between Teradata network
clients and Teradata Database.
Teradata Generic Security Services
Client Java
Teradata's implementation of industry-standard Generic
Security Services APIs in Java language. It provides
enhanced security services interfaces between Teradata
network clients and 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: Downloaded and installed from the web.
Teradata Meta Data Services
Teradata Meta Data Services (MDS) 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 (ETL) 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. MultiLoad is a command-driven utility for
fast, high-volume maintenance on multiple tables and
views of a Teradata Database.
Teradata OLE DB Access Module
A dynamic link library (DLL) that acts as an interface
between Teradata load and export utilities (Teradata
FastLoad, Teradata FastExport, Teradata MultiLoad,
TPump, Teradata Parallel Transporter [PT], and BTEQ)
and data sources for which an OLE DB provider is
available. The access module quickly moves data between a
OLE DB data sources and Teradata Database without
requiring intermediate storage.
Teradata Parallel Data Pump
A data loading utility that helps maintain (update, delete,
insert, and atomic upsert) the data in a Teradata Database.
TPump uses standard Teradata SQL to achieve moderate to
high data loading rates to the Teradata Database. Multiple
sessions and multi-statement requests are typically used to
increase throughput.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
241
Chapter 18: Product Descriptions
Task 1: Review Product Descriptions
Products
Description
Teradata Parallel Transporter API
Teradata Parallel Transporter API is a set of
application programming interfaces used to load and
export data to and from Teradata Database systems.
Teradata Parallel Transporter Export
Operator
Teradata Parallel Transporter Export Operator is a
producer operator that emulates the Teradata FastExport
utility. It exports large volumes of data at high speed from
the Teradata Database to a client by outputting the data to
a consumer operator, such as a Load, Update, Stream, or
SQL Inserter Operator to load data to a Teradata Database
table.
Using the DataConnector Operator as a consumer
operator, the data can be written to a flat file, passed to an
access module provided by Teradata, or passed to a custom
access module created by an end user.
Teradata Parallel Transporter
Infrastructure
Teradata Parallel Transporter Infrastructure is an
object-oriented client application that provides
scalable, high-speed, parallel data extraction, loading,
and updating.
Teradata Parallel Transporter Load
Operator
Teradata Parallel Transporter Load Operator is a consumer
operator which functions similar to Teradata FastLoad to
load a large volume of data at high speed into an empty
table on the Teradata Database.
The operator loads tables into the Teradata Warehouse.
Multiple parallel instances can be used to improve the
performance of the load.
Teradata Parallel Transporter Stream
Operator
Teradata Parallel Transporter Stream Operator is 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 Parallel Transporter Update
Operator
Teradata Parallel Transporter Update Operator is a
consumer operator that emulates the Teradata MultiLoad
utility to load a large volume of data at high speed into up
to five tables on the Teradata Database. Use this operator to
maintain tables in the Teradata Warehouse.
Teradata Performance Monitor
Object
Teradata Performance Monitor Object presents a snapshot
of the detail Session, and Resource, usage on a Teradata
Database.
The Session screen allows sorts on sessions by the amount
processing is skewed across the AMPs, in addition to the
previous sort orders. It also allows selection of a “hot”
AMP in order to see which sessions are currently skewed
towards that AMP.
Teradata Query Director
242
Increases database availability and efficiency by routing
sessions between two or more Teradata Databases.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 18: Product Descriptions
Task 1: Review Product Descriptions
Products
Description
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 a Teradata QS server
and also view information about your scheduled jobs.
Teradata Query Scheduler Server
The Teradata QS server components save, process, and
execute Teradata QS client requests that have been
scheduled.
Teradata SQL Assistant
A Windows-based information discovery tool designed to
retrieve, manipulate, and store data from ODBCcompliant 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
Imitates (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 WebSphere® MQ Access
Module
Allows Teradata utilities to import data using IBM®
WebSphere MQ message queuing middleware.
Teradata Workload Analyzer
A tool that analyzes and generates candidate workloads
from a Windows PC. Teradata WA provides three major
areas of guidance:
• Recommending workload group definitions. The DBA
(database administrator) guides these based on business
knowledge and Analyzer-assisted based on existing
workload mix and characteristics
• Recommending appropriate workload goals
• Recommending workload to AG (allocation group)
mapping plus priority scheduler weights
Teradata Tools and Utilities Installation Guide for Microsoft Windows
243
Chapter 18: Product Descriptions
Task 1: Review Product Descriptions
244
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 19
Product Dependencies
The following table lists the dependent products which must be installed to support Teradata
Tools and Utilities products installed. Unless otherwise specified, all Teradata Tools and
Utilities products and dependencies are version 13.10 or later.
Task 1: Review Product Dependencies
The following table lists dependencies of Teradata Tools and Utilities.
Products
Dependent Products
Basic Teradata Query
Teradata Tools and Utilities Dependencies
• Teradata Call-Level Interface version 2
• Teradata Data Connector
• Teradata Generic Security Services (teragss)
• Shared ICU Libraries for Teradata
Third-party Dependencies
• No third-party dependencies
Named Pipes Access Module
Teradata Tools and Utilities Dependencies
• No Teradata Tools and Utilities dependencies
Third-party Dependencies
• No third-party dependencies
.NET Data Provider for Teradata
Teradata Tools and Utilities Dependencies
• No Teradata Tools and Utilities dependencies
Third-party Dependencies
• .NET Framework 2.0
32-bit redistributable
64-bit redistributable
• (Optional) Microsoft Visual Studio 2005 or Microsoft
Visual 2008 Integration Feature
• (Optional) Microsoft SQL Server Business Intelligence
Development Studio
Teradata Tools and Utilities Installation Guide for Microsoft Windows
245
Chapter 19: Product Dependencies
Task 1: Review Product Dependencies
Products
Dependent Products
ODBC Driver for Teradata
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
TeraGSS - Client package
Third-party Dependencies
• Microsoft Data Access Components (MDAC), version
2.8 SP1 (on distribution CD)
Note: Required for Windows 2000 only.
OLE DB Provider for Teradata
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata GSS Client
Third-party Dependencies
• Microsoft Data Access Components (MDAC), version
2.8 sp1 (on distribution CD)
Note: Required for Windows 2000 only.
Shared ICU Libraries for Teradata
Teradata Tools and Utilities Dependencies
• No dependencies
Third-party Dependencies
• No dependencies
Teradata Administrator
Teradata Tools and Utilities Dependencies
• ODBC Driver for Teradata
• Shared ICU Libraries for Teradata (tdicu)
• Teradata Generic Security Services (teragss)
Third-party Dependencies
• No dependencies
Teradata Archive/Recovery Utility
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services
TeraGSS - Client package
• Teradata Call-Level Interface version 2
• Teradata Data Connector
Third-party Dependencies
• No dependencies
Teradata C Preprocessor2
Teradata Tools and Utilities Dependencies
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services
TeraGSS - Client package
• Shared ICU Libraries for Teradata
Third-party Dependencies
• No dependencies
246
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 19: Product Dependencies
Task 1: Review Product Dependencies
Products
Dependent Products
Teradata Call-Level Interface version 2
Teradata Tools and Utilities Dependencies
• Teradata Generic Security Services (TeraGSS - Client
package)
• Shared ICU Libraries for Teradata
Third-party Dependencies
• No dependencies
Teradata Data Connector
Teradata Tools and Utilities Dependencies
• No dependencies
Third-party Dependencies
• No dependencies
Teradata FastExport
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services (TeraGSS - Client
package)
• Teradata Call-Level Interface version 2
• Teradata Data Connector
Third-party Dependencies
• No dependencies
Teradata FastLoad
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services (TeraGSS - Client
package)
• Teradata Call-Level Interface version 2
• Teradata Data Connector
Third-party Dependencies
• No dependencies
Teradata Generic Security Services
Client
Teradata Tools and Utilities Dependencies
• No dependencies
Third-party Dependencies
• No dependencies
Teradata Generic Security Services
Client Java
Teradata Tools and Utilities Dependencies
• No dependencies
Third-party Dependencies
• No dependencies
Teradata Tools and Utilities Installation Guide for Microsoft Windows
247
Chapter 19: Product Dependencies
Task 1: Review Product Dependencies
Products
Dependent Products
Teradata Index Wizard
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services (TeraGSS - Client
package)
• Teradata Call-Level Interface version 2
or
• ODBC Driver for Teradata
Third-party Dependencies
• No dependencies
Teradata JDBC Driver
Teradata Tools and Utilities Dependencies
• No dependencies
Third-party Dependencies
• JDK 1.4, JDK 5.0, or JDK 6.0 from Sun
• 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
Teradata Meta Data Services
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services (TeraGSS - Client
package)
• ODBC Driver for Teradata
Third-party Dependencies
• See Teradata Meta Data Services documentation
• Java Runtime Environment 1.5.0 or later (32-bit)
Teradata MultiLoad
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services (TeraGSS - Client
package)
• Teradata Call-Level Interface version 2
• Teradata Data Connector
Third-party Dependencies
• No dependencies
Teradata OLE DB Access Module
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services (TeraGSS - Client
package)
• ODBC Driver for Teradata
Third-party Dependencies
• No dependencies
248
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 19: Product Dependencies
Task 1: Review Product Dependencies
Products
Dependent Products
Teradata Parallel Data Pump
Teradata Tools and Utilities Dependencies
• Teradata Call-Level Interface version 2
• Teradata Data Connector
• Teradata Generic Security Services (TeraGSS - Client
package)
• Shared ICU Libraries for Teradata
Third-party Dependencies
• No dependencies
Teradata Parallel Transporter API
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
Third-party Dependencies
• No dependencies
Teradata Parallel Transporter Export
Operator
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
• (Optional) Teradata Parallel Transporter Infrastructure
(for Teradata Parallel Transporter job script users.)
• (Optional) Teradata Parallel Transporter API
(for Teradata Parallel Transporter API users.)
Third-party Dependencies
• No dependencies
Teradata Parallel Transporter
Infrastructure
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
Third-party Dependencies
• Java 2 Runtime Environment 1.4.2_06 or later
Note: The environment can be downloaded from the
Sun website at: http://java.sun.com/products/archive
Teradata Tools and Utilities Installation Guide for Microsoft Windows
249
Chapter 19: Product Dependencies
Task 1: Review Product Dependencies
Products
Dependent Products
Teradata Parallel Transporter Load
Operator
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
• (Optional) Teradata Parallel Transporter Infrastructure
(for Teradata Parallel Transporter job script users.)
• (Optional) Teradata Parallel Transporter API
(for Teradata Parallel Transporter API users.)
Third-party Dependencies
• No dependencies
Teradata Parallel Transporter Stream
Operator
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
• (Optional) Teradata Parallel Transporter Infrastructure
(for Teradata Parallel Transporter job script users.)
• (Optional) Teradata Parallel Transporter API
(for Teradata Parallel Transporter API users.)
Third-party Dependencies
• No dependencies
Teradata Parallel Transporter Update
Operator
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
• (Optional) Teradata Parallel Transporter Infrastructure
(for Teradata Parallel Transporter job script users.)
• (Optional) Teradata Parallel Transporter API
(for Teradata Parallel Transporter API users.)
Third-party Dependencies
• No dependencies
Teradata Performance Monitor
Object
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
Third-party Dependencies
• No dependencies
250
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 19: Product Dependencies
Task 1: Review Product Dependencies
Products
Dependent Products
Teradata Query Director
Teradata Tools and Utilities Dependencies
• Teradata Call-Level Interface version 2
• Shared ICU Libraries for Teradata
• Teradata_GSS_Client
Third-party Dependencies
• No dependencies
Teradata Query Scheduler
Administrator
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
Third-party Dependencies
• TCP/IP driver with WinSock support for Windows
version 1.1 or later
• Ethernet or Token Ring packet driver compatible with
the above
Teradata Query Scheduler Client
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
Third-party Dependencies
• No dependencies
Teradata Query Scheduler Server
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
• Teradata Query Scheduler Client
Third-party Dependencies
• No dependencies
Teradata Tools and Utilities Installation Guide for Microsoft Windows
251
Chapter 19: Product Dependencies
Task 1: Review Product Dependencies
Products
Dependent Products
Teradata SQL Assistant
Teradata Tools and Utilities Dependencies and Third-party
Dependencies
The ODBC Driver for Teradata can be used, in addition to,
or as an alternative to, the .Net Data Provider for Teradata,.
Teradata SQL Assistant dependencies must be installed in
the following order:
• Microsoft .NET Framework, version 2.0 or later
32-bit redistributable
64-bit redistributable
• .NET Data Provider for Teradata, version 12.0 or later.
Install Policy Files must be selected during the
installation.
http://www.teradata.com
• ODBC Driver for Teradata (optional)
Note: The ODBC Driver for Teradata can be installed at
any time before or after installing Teradata SQL
Assistant.
• If ODBC installed, install Shared ICU Libraries for
Teradata
• If ODBC is installed, install Teradata Generic Security
Services (TeraGSS - Client package)
Teradata Statistics Wizard
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Call-Level Interface version 2
• Teradata Generic Security Services (TeraGSS - Client
package)
• ODBC Driver for Teradata
Third-party Dependencies
• No dependencies
Teradata System Emulation Tool
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services (TeraGSS - Client
package)
• Teradata Call-Level Interface version 2
or
• ODBC Driver for Teradata
Third-party Dependencies
• No dependencies
252
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 19: Product Dependencies
Task 1: Review Product Dependencies
Products
Dependent Products
Teradata Visual Explain
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services (TeraGSS - Client
package)
• Teradata Call-Level Interface version 2
or
• ODBC Driver for Teradata
Third-party Dependencies
• No dependencies
Teradata WebSphere® MQ Access
Module
Teradata Tools and Utilities Dependencies
• Teradata Data Connector
Third-party Dependencies
• IBM WebSphere MQ V5.2
Teradata Workload Analyzer
Teradata Tools and Utilities Dependencies
• Shared ICU Libraries for Teradata
• Teradata Generic Security Services (TeraGSS - Client
package)
• Teradata Call-Level Interface version 2
Third-party Dependencies
• No dependencies
Note: Teradata Parallel Transporter version 13.10 is certified with Teradata Call-Level
Interface version 2 release 13.10.
Note: The installation of Teradata Parallel Transporter Infrastructure installs the following
software:
•
Teradata Parallel Transporter Infrastructure
•
Teradata Parallel Transporter ICU Library
•
Teradata Parallel Transporter Operator Support Library
•
Teradata Parallel Transporter Data Connector Operator
•
Teradata Parallel Transporter DDL Operator
•
Teradata Parallel Transporter FastExport OUTMOD Adapter Operator
•
Teradata Parallel Transporter FastLoad INMOD Adapter Operator
•
Teradata Parallel Transporter MultiLoad INMOD Adapter Operator
•
Teradata Parallel Transporter ODBC Operator
•
Teradata Parallel Transporter OS Command Operator
•
Teradata Parallel Transporter SQL Inserter Operator
•
Teradata Parallel Transporter SQL Selector Operator
•
Teradata Parallel Transporter Wizard
Teradata Tools and Utilities Installation Guide for Microsoft Windows
253
Chapter 19: Product Dependencies
Task 2: Installing Dependencies
Note: The installation of Teradata Parallel Transporter API installs the following software:
•
Teradata Parallel Transporter API
•
Teradata Parallel Transporter ICU Library
•
Teradata Parallel Transporter Operator Support Library
Task 2: Installing Dependencies
The Teradata Tools and Utilities installation can automatically install dependent products. If a
dependent product already exists on the client system for one of the following products,
•
Shared ICU Libraries for Teradata
•
Teradata_GSS_Client
•
Teradata Call-Level Interface version 2
•
ODBC Driver for Teradata
•
Teradata Data Connector
the installation will display one of two messages.
•
Product Already Installed, Version the Same - The first message appears if a product is
already installed, and its version is the same as the product being installed. For example,
the following message is for the ODBC Driver for Teradata:
"ODBC Driver for Teradata 13.10.00.00 is already installed.
Do you want to reinstall it?"
•
Product Already Installed, Version Different - The second message appears if a product is
already installed and its version is not equal to the product being installed. For example,
the following message is for the ODBC Driver for Teradata:
"ODBC Driver for Teradata 13.00.00 is already installed.
Do you want to overwrite it with version 13.10.00?"
254
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 20
Windows System Requirements
The following sections contain information on platform requirements, administrator
privileges required, minimum and recommended configurations for Windows systems where
Teradata Tools and Utilities products are installed.
Task 1: Determine System Requirements
Step 1: Determine Platform Requirements
Teradata Tools and Utilities software runs on an i386-based or greater computer which
includes:
•
An appropriate network card
•
Ethernet or Token Ring LAN cards
•
345.9MB of free disk space for a full installation
•
FAT or NTFS for Teradata Generic Security Services (TeraGSS) Client
Specific operating systems supported are listed in the Teradata Tools and Utilities 13.10
Supported Platforms and Product Versions spreadsheet associated with this release.
Step 2: Determine Privilege Requirements
To install Teradata Tools and Utilities requires administrator privileges for the computer on
which they are being installed.
Step 3: Determine Network Requirements
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 the Teradata Tools and Utilities Release Definition, Release 13.1.
Step 4: Determine Teradata Database Requirements
The appropriate Ethernet hardware and software, supporting a TCP/IP-based network, must
be installed on every Teradata Database with which the client computer will communicate.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
255
Chapter 20: Windows System Requirements
Task 1: Determine System Requirements
Step 5: Determine Minimum Configurations
The following table lists the minimum hardware configurations for Teradata Tools and
Utilities products.
Product
Client
Server
Teradata Performance Monitor
Teradata Administrator
Teradata Statistics Wizard
Teradata Query Scheduler
500 MHz Pentium III
256 MB RAM
10 GB Hard Drive (100 MB for TMGR)
CD ROM Drive
1024x768 Display
1.2 GHz Pentium 4
512 MB RAM
18 GB Hard Drive (100 MB for TMGR)
CD ROM Drive
1024x768 Display
Modem (required to use the Send a Page
action of the Alerts facility)
Teradata SQL Assistant
500 MHz Pentium III
64 MB RAM
CD ROM Drive
800x600 Display
Minimum 50 MB free disk space
OLE DB Provider for Teradata
Minimum Disk Space
• 3 MB available disk space for OLE DB
Provider for Teradata files
• 27 MB available disk space on the
system drive for MDAC (required
only for Windows 2000)
• 14 MB available disk space on the
TEMP drive for temporary
installation files
Teradata Databases Supported:
• Teradata Database V2R6.x
• Teradata Database 12.00.xx
• Teradata Database 13.00.xx
Operating Systems Supported:
• Microsoft® Windows 2000
• Microsoft Windows XP Professional
(32-bit)
• Microsoft Windows Server 2003
• Microsoft Windows Vista
• Windows Server 2008
Step 6: Determine Recommended Configurations
The following table lists the recommended hardware configurations for Teradata Tools and
Utilities products.
256
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 20: Windows System Requirements
Task 1: Determine System Requirements
Product
Client
Server
Teradata Performance Monitor
Teradata Administrator
Teradata Statistics Wizard
Teradata Query Scheduler
1.2 GHz Pentium 4
512 MB RAM
40 GB Hard Drive (200 MB for TMGR)
CD ROM Drive
1280x1024 Display
2 GHz Pentium 4
1 GB RAM
30 GB Hard Drive (200 MB for TMGR)
CD ROM Drive
1280x1024 Display
Modem (required to use the Send a Page
action of the Alerts facility)
Teradata SQL Assistant
1.2 GHz Pentium 4
256 MB RAM
CD ROM Drive
1024x768 Display
Minimum 100 MB free disk space
Teradata Tools and Utilities Installation Guide for Microsoft Windows
257
Chapter 20: Windows System Requirements
Task 1: Determine System Requirements
258
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 21
Windows Installation Recommendations
Before beginning the installation of Teradata Tools and Utilities software on a Windows client
system, verify that the software package ordered is complete (see Installation Kit) and that the
client systems where the software will be installed are set up with the required software and
hardware. If the correct disks were not received, contact the TSCS-RSC.
Task 1: Determine Installation Type
Recommendation 1: Typical, Custom, and Network Installations
The following packages can be installed:
•
All of the Teradata Tools and Utilities products on the current CD (Typical installation)
•
Some of the products on the current CD (Custom installation)
•
It allows the product’s setup files to be copied to a specified folder (Network installation)
For a list of product dependencies, refer to Product Dependencies.
Recommendation 2: Command Line Installations
An installation can be “silent”. Windows packages are installed from the command prompt:
•
Download packages from the Teradata Software Server
•
Copy packages using a Network Setup Type, then copy them to the target machine
For a list of product dependencies, refer to Product Dependencies.
Task 2: Operating System Recommendations
Recommendation 1: Installing on Windows Server 2003
When installing Teradata Tools and Utilities software on a Windows Server 2003 system using
a terminal session opened with “mstsc”, open the session in console mode: “mstsc /console”.
Otherwise, the Windows Server 2003 system will have to be rebooted after installing the
software.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
259
Chapter 21: Windows Installation Recommendations
Task 3: Product Recommendations
Recommendation 2: Installing on EM64T Systems
When a Client product that has both a 32-bit and a 64-bit installation package is installed
silently on an EM64T system, both the 32-bit and the 64-bit versions will be installed. If the
Client product is installed interactively, only the 64-bit version is installed.
Task 3: Product Recommendations
Recommendation 1: Installation of Dependent Products
The Teradata Tools and Utilities installation can automatically install dependent products. If a
dependent product already exists on the system for one of the following products:
•
Shared Common Components for Internationalization for Teradata
•
Teradata Call-Level Interface version 2 (CLIv2)
•
Teradata Data Connector
•
ODBC Driver for Teradata
•
Teradata Generic Security Services
The installation displays one of two messages. The first message appears if a dependent
product already exists and its version is the same as the dependent product being installed. It
asks permission to reinstall the existing installed product.
For example, the following message is for Teradata Call-Level Interface version 2 (CLIv2):
"Teradata Call-Level Interface version 2 (CLIv2) 13.10.00.00 is already
installed.
Do you want to reinstall it?"
The second message that appears if a dependent product already exists and its version is not
equal to the dependent product being installed. It asks permission to overwrite the existing
installed product.
For example, the following message is for the Teradata Call-Level Interface version 2 (CLIv2):
"Teradata Call-Level Interface version 2 (CLIv2) 13.00.00 is already
installed.
Do you want to overwrite it with version 13.10.00.00?"
260
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 22
Security and Connecting to a
Teradata Database
This section contains procedures and describes how to connect to a Teradata Database.
Note: The figures shown in this document are examples only. Depending on the Teradata
Tools and Utilities products used in your installation, some dialogs might vary from those
shown in this guide.
Task 1: Make the Database Connection
This section describes:
•
How to connect to a Teradata Database from a GUI application.
•
How to connect to a Teradata Database from a command line application.
•
Where to find the information to programmatically connect to a Teradata Database.
For programmatic interfaces, the User or Reference guide for the specific product provides
information about the product interface.
Step 1: Review 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. If the information is incorrect, you can change the
value entered 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 be used to manipulate the fields of the Connect to Teradata
Database dialog.
Step 2: Connect To a Teradata Database from a GUI Application
This section contains the procedure to connect to a Teradata Database using the Connect to
Teradata Database dialog from a Graphical User Interface (GUI) application. The procedure is
Teradata Tools and Utilities Installation Guide for Microsoft Windows
261
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
for a typical application. The dialog for each product may and do vary in appearance and the
fields that it requires. See the product User or Reference guide for specific information about
an individual product.
Procedure - Connecting to a Teradata Database
To connect to a Teradata Database, perform the following procedure:
1
If the application connecting to the database has a Connectivity tab in the Tools options
menu, select WinCLI or ODBC.
2
Click the Connect button. The Connect to Teradata Database dialog appears.
3
Select or enter the appropriate values for the database.
4
Click OK.
Connect to Teradata Database Dialog
The following figure shows the Connect to Teradata Database dialog:
The following table describes the fields in the Connect to Teradata Database dialog:
262
Field Name
Definition
Database Name
(Required) Enter a valid Teradata Database name, or select a Teradata
Database Name that was previously entered from the drop down list. This is
the name of the database to connect.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
Field Name
Definition
Authentication
Mechanism
(Required) Select the authentication mechanism specified by the client system
administrator from the list of authentication mechanisms provided in the
drop down list. The Authentication Mechanism identifies the mechanism used
for connections to the data source.
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
• TD1 - Teradata 1 mechanism
• TD2 - Teradata 2 mechanism
• ldap - ldap mechanism
• KRB5 - Kerberos mechanism
• KRB5C - Kerberos Compatibility mechanism
• SPNEGO - Simple and Protected GSSAPI Negotiation Mechanism
• NTLM - NT LAN Manager mechanism
• NTLMC - NT LAN Manager Compatibility mechanism
• Other - user-defined mechanism
Authentication
Parameter
(Optional) Enter the parameters required by the selected authentication
mechanism. See your System Administrator.
User Name
(Required) Select your user name from the drop down list, or enter a valid user
name.
Password
(Required) Enter your Password for the user name you entered.
Default Database
(Optional) Select the default database for the session.
Account String
(Optional) Enter a new Account String or select an account string from the
drop down list.
The Account String is used to create a user in a Teradata Database, instead of
providing account information during configuration of ODBC. It allows
Teradata to isolate users, to find out what applications users are running, or to
restrict users trying to connect to the database.
Note: Even though the UserId and Password parameters are required to log on to the Teradata
Database, entry into the Connect to Teradata Database dialog is not required since they will be
filled in by the user logon exit routine.
Step 2: Connect to a Teradata Database from Command Line Driven
Applications
This section contains procedures and describes how to connect to a Teradata Database from
the command line.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
263
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
Procedure - Connecting from Command Line Driven Applications
Follow these steps to connect to a Teradata Database from the command line.
1
Enter the .logmech command.
2
Enter the .logdata command.
3
Enter the .logon command.
Use the .logmech Command
The .logmech command identifies the desired logon authentication mechanism
(logmech_name_string). The logmech_name_string is limited to 8 bytes and is not casesensitive.
The syntax for the .logmech command is:
.logmech logmech_name_string
The logmech_name_string supports the following values
•
None - If no Authentication Mechanism is entered, or if the Authentication Mechanism
selected is not supported, the system will default to TD2
•
TD1 - Teradata 1 mechanism
•
TD2 - Teradata 2 mechanism
•
LDAP - ldap mechanism
•
KRB5 - Kerberos mechanism
•
KRB5C - Kerberos Compatibility mechanism
•
SPNEGO - Simple and Protected GSSAPI Negotiation Mechanism
•
NTLM - NT LAN Manager mechanism
•
NTLMC - NT LAN Manager Compatibility mechanism
Use the .logdata Command
To successfully authenticate the user, the .logdata command provides all the parameters
needed by the authentication mechanism, other than a UserId and Password. The information
is entered into and passed by the logdata_string. The logdata_string is limited to 64K bytes.
The syntax for the .logdata command is:
.logdata logdata_string;
If the logdata_string has white space characters or the other special characters embedded, the
entire logdata string must be delimited with single quotes:
.logdata ‘logdata_string’;
The exact contents of the logdata_string will vary according to the selected authentication
mechanism. The string is not displayed, parsed, nor otherwise processed by the application.
Use the .logon Command
The syntax for the .logon command is:
264
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
.logon <DBCName></><UserId><,><Password><,><AccountId>
where:
Parameter
Definition
DBCName
(Required) The DBCName is also referred to as the TDIPD (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.
UserId
(Required) The UserId or user name string can be up to 30 characters
long. The first character cannot be a numeric character. The UserId is
not case sensitive.
Password
(Required) The Password string can be up to 30 characters long. The
first character cannot be a numeric character. In the dialog box, each
character of the Password is displayed with an asterisk (*). The
Password is not case sensitive.
AccountId
(Optional) - The AccountId is required only if there is a comma after
the Password field. The first character cannot be a numeric character.
Do not enter the single quote (') that normally surrounds an
AccountId. The AccountId is not case sensitive.
Example 1: Example Logons from the Command Line
Supported Mechanisms
In general, mechanisms which perform authentication and validation do not require that a
Teradata Database Username and Password be included as part of the logon string. If these
items are provided in conjunction with an authentication mechanism, they are ignored.
The following authentication mechanisms are supported:
Kerberos Examples
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.
Once the user’s identity has been verified by Kerberos, an implicit logon proceeds using the
tendered UserId as the Teradata Username:
.logmech KRB5
.logdata joe@domain1@@mypassword
.logon mydbs/
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/
Teradata Tools and Utilities Installation Guide for Microsoft Windows
265
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
Alternatively, a Kerberos-mediated SSO-style logon can be used by omitting either 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/
If required, Teradata 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 the cases above, a Teradata Username must be defined in the target Teradata Database
that matches the actual or derived UserId. Further, the Username must have previously been
granted the “logon with null password privilege.”
Note: The special “dbc” username cannot be used with Kerberos authentication mechanism
since “dbc” cannot be granted the “logon with null password privilege.” If the “dbc” username
is passed, the Teradata Database will return error 3790.
KRB5C Examples
The KRB5C mechanism is maintained for compatibility purposes with Teradata Tools and
Utilities 8.1 communicating with a pre-V2R6 Teradata Database that supports SSO and logon
encryption. It should not generally be specified.
The teraSSO library will automatically determine the appropriate authentication mechanism
when interfacing to such a Teradata Database using the same logic as employed in Teradata
Tools and Utilities 7.1.
•
Windows clients should use NTLMC or KRB5C for SSO
•
For non-SSO, Windows clients use TD1
•
Non-Windows clients should use TD1
In the event a user manually selects an incompatible mechanism,
TERASSO_SECPKGMATCH_FAIL is returned.
SPNEGO
Teradata Database employs the Simple and Protected GSSAPI Negotiation Mechanism
(SPNEGO) 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,
266
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
except that KRB5 cannot be used in a Windows .Net environment. See “Kerberos Examples”
on page 265.
The KRB5 and NTLM mechanisms should be used for legacy installations prior to Release
13.00.00.
Note: SPNEGO requires the download of .NET Framework.
NTLM Examples
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 will proceed using the tendered UserId
as the Teradata Username.
.logmech NTLM
.logdata joe@domain1@@mypasswordjoe
.logon mydbs/
For single-Domain environments, the gateway can be configured so that the Domain or
Realm need not be indicated:
.logmech NTLM
.logdata joe@@mypasswordjoe
.logon mydbs/
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/
If required, Teradata accounting information can be provided as part of .logon command as
follows:
.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 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. “
Teradata Tools and Utilities Installation Guide for Microsoft Windows
267
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
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.
For compatibility purposes, this is equivalent to the existing SSO feature. The existing thirdparty sign-on variant of SSO (NTLM only) is supported for compatibility purposes. However,
it is recommended that new applications should use the logmech_name, logmech_data_ptr,
and logmech_data_len fields in DBCAREA instead.
NTLMC Examples
The NTLMC authentication mechanism is maintained for compatibility purposes only for
Teradata Tools and Utilities 8.1 communication with a pre-V2R6 Teradata Database that
supports SSO and logon encryption. Generally, do not specify the NTLMC authentication
mechanism.
The teraSSO library automatically determines the appropriate mechanism when interfacing to
a Teradata Database, and uses the same logic as employed in Teradata Tools and Utilities 7.1.
•
Windows clients should use NTLMC or KRB5C for SSO.
•
For non-SSO, Windows clients should use TD1.
•
Non-Windows clients should use TD1.
In the event a user manually selects an incompatible mechanism,
TERASSO_SECPKGMATCH_FAIL will be returned.
LDAP Examples
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 upon 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 username:
.logmech LDAP
.logdata domain7authcid=joe password=password real=myrealm
.logon mydbs/joe,password
If required, Teradata 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 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 Username.
268
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
Note: The special “dbc” Username cannot be used with the LDAP authentication mechanism
since “dbc” cannot be granted the “logon with null password privilege.” If “dbc” is used as the
username, the Teradata Database will return error 3790.
If the directory does not map the UserId to a specific Teradata 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.
.logdata information must always be provided for the LDAP authentication mechanism.
TD1 and TD2 Examples
TD1 and TD2 represent the Teradata mechanisms. They do not perform any authentication.
Rather, they facilitate encryption/decryption for sessions connected absent the mediation of
extended security. Therefore, a valid Teradata Username and Password are always required.
•
Only TD1 is used by Teradata Tools and Utilities 7.1.
•
TD2 is used by Teradata Tools and Utilities 8.0 and later for the V2R6.0 Teradata Database
and later.
•
TD1 is used by Teradata Tools and Utilities 8.0 and above for the V2R5.1 Teradata
Database.
The difference between the two mechanisms is that the encryption key for TD2 is longer and,
therefore, offers a higher degree of security than that of TD1. For TD2, there should be no
.logdata parameter; if one is passed to CLIv2, it will be ignored.
TD2 is the default mechanism for the server-based XML configuration file:
.logmech TD2
.logon mydbs/rhh,password
TD1 Examples
TD1 is a deprecated mechanism used by Teradata Tools and Utilities 7.1. It is also used by
Teradata Tools and Utilities 8.0 when communicating with a V2R5.x Teradata Database. The
difference between the two mechanisms is that the encryption key for TD2 is longer and,
therefore, offers a higher degree of security than that of TD1.
The TD1 authentication mechanism is maintained for compatibility purposes only for
Teradata Tools and Utilities 8.0 communication with a V2R5.x Teradata Database. Generally,
it should not be specified.
The teraSSO library automatically determines the appropriate mechanism when interfacing to
a V2R5.x Teradata Database, using the same logic as used in Teradata Tools and Utilities 7.1.
•
Windows clients should use NTLMC or KRB5C for SSO
•
For non-SSO, Windows clients should use TD1
In the event a user manually selects an incompatible mechanism,
TERASSO_SECPKGMATCH_FAIL will be returned.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
269
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
Review Single Sign-On Legacy Considerations
The following table lists single sign-on legacy considerations in order to provide backward
compatibility with pre-Teradata Tools and Utilities 8.0 applications which use SSO, the
following items apply.
Type
Description
Direct sign-on
If a Username and Password are not supplied as part of the Teradata
logon string,
AND
no authentication mechanism name is specified in .logmech, the client
interface will not use the default mechanism.
Rather, it will first determine if the Kerberos mechanism is available. If
the Kerberos authentication mechanism is available, the client
interface will use it.
If the Kerberos interface is not available, the client interface will next
determine if the NTLM authentication mechanism is available. If the
NTLM authentication mechanism is available, it will use it.
If neither the NTLM nor the Kerberos authentication mechanism is
available, the logon attempt will fail.
If .logmech is specified, and the authentication mechanism turns out
to be different from the one automatically determined by the client
interface, an error will be returned.
Third-party sign-on
If an application uses the programmatic third-party sign-on capability
using the CLIv2 DBCAREA extension
AND
no authentication mechanism name is specified in logmech_name, the
client interface will not use the default authentication mechanism.
Rather, the client interface will first determine if the Kerberos
authentication mechanism is available. If the Kerberos authentication
mechanism is available, the client interface will use it.
If the Kerberos authentication mechanism is not available, the client
interface will next determine if the NTLM authentication mechanism
is available. If the NTLM authentication mechanism is available, it will
use it.
If neither the NTLM nor the Kerberos authentication method is
available, the logon attempt will fail.
If .logmech is specified, and the authentication mechanism turns out
to be different from the one automatically determined by the client
interface, an error will be returned.
Step 3: Connect to a Teradata Database Programmatically
Several Teradata Tools and Utilities products that allow a programmatic connection to the
Teradata Database using SQL and APIs.
270
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
The following table lists products that allow a programmatic connection to the Teradata
Database using SQL and APIs.
Product
Document
ODBC Driver for Teradata
ODBC Driver for Teradata User Guide.
Describes SQL Connect, SQLDriverConnect, and
SQLBrowseConnect and the parameters implemented for
security. Includes information on configuring the ODBC
Driver for Teradata.
OLE DB Provider for Teradata
OLE DB Provider for Teradata Installation and User Guide.
Describes the security implemented for the OLE DB
Provider for Teradata.
Teradata Call-Level Interface version
2 (CLIv2)
Teradata Call-Level Interface Version 2 Reference for
Network-Attached Systems.
Describes the CLI APIs implemented for security.
Teradata JDBC Driver
Teradata JDBC Driver User Guide.
Describes the security methods implemented for the type 4
driver and illustrates how to connect to the Teradata
Database using the Teradata JDBC Driver.
Step 4: Check Logon Error Messages
The following table lists error messages which apply to the logon and database connection
function.
Error Message
UTY1652 Logon mechanism is not supported in the version of CLI.
Explanation: 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.
Generated by: UTYMSG
Remedy: Remove specified logon mechanism options.
UTY6668 Invalid use of the .LOGMECH statement.
Explanation: It is invalid to specify the .LOGMECH statement after the .LOGON statement.
Generated by: UTYMSG
Remedy: Remove the invalid statement and resubmit the program.
UTY6669 Invalid use of the .LOGDATA statement.
Explanation: It is invalid to specify the .LOGDATA statement after the .LOGON statement.
Generated by: UTYMSG
Remedy: Remove the invalid statement and resubmit the program.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
271
Chapter 22: Security and Connecting to a Teradata Database
Task 1: Make the Database Connection
Error Message
UTY6670 A .LOGMECH statement has been previously specified, terminating.
Explanation: A .LOGMECH statement has already been processed.
Generated by: UTYMSG
Remedy: Remove the extra statement and resubmit the program.
UTY6671 A .LOGDATA statement has been previously specified, terminating.
Explanation: A .LOGDATA statement has already been processed.
Generated by: UTYMSG
Remedy: Remove the extra statement and resubmit the program.
Step 5: Reselect Authentication Mechanism on Connection Error
If there is an error in the authentication mechanism selected, “External authentication is not
currently allowed” may appear.
If this message, is received an incorrect authentication mechanism has been selected. Reselect
it using the authentication mechanism provided by the database administrator and try to
connect again.
272
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 23
Troubleshooting the Installation
This section includes tips on troubleshooting the Teradata Tools and Utilities installation.
Task 1: Troubleshoot Client Computer
Problems
To troubleshoot problems with a client computer, perform the following checks.
Problem 1: Path Overrun
When a program on a Microsoft Windows 2000-based computer or a Microsoft Windows NTbased computer, the program may not run. Additionally, when a new environment variable is
added manually that contains a path value, the path may be truncated.
This problem occurs because a system environment variable or a user environment variable
contains a path that exceeds the maximum character length. The maximum length of the
combined system and user-defined path for an environment variable is 1,023 characters,
excluding the "path=" part of either. The system path is limited to a maximum length of 1,023
characters.
If a system environment variable contains a path that exceeds the maximum character length,
the path is truncated when a program is started. This truncated version of the path is then
written back to the registry. When this occurs, the operating system may not be able to find
the executable files or the DLL files for the program. In this case, the program may not run.
The user-defined path is limited to a maximum length of 511 characters. When a user-defined
path is combined with a system path, the user-defined path is limited to 1,023 characters
minus the system path. If the system path uses the total allocated environment space, the userdefined path may be truncated. In this case, you may experience the problem that is
mentioned in the “Symptoms” section.
Note: These path length limits for environment variables are also true for Microsoft Windows
XP and Microsoft Windows Server 2003.
Resolution
A supported hotfix is now available from Microsoft, but it is only intended to correct the
problem that this article describes. Apply it only to systems that are experiencing this specific
problem. After applying this hotfix, the path length limit for environment variables is
increased to 2,048 characters. Refer to Teradata Tech Alert NTA 1455 for more information.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
273
Chapter 23: Troubleshooting the Installation
Task 1: Troubleshoot Client Computer Problems
Problem 2: Cannot Communicate Over the Network with Teradata
Database
To confirm that a client computer can communicate over the network to the Teradata
Database, ping the Teradata Database by opening a command window and typing:
ping dbcnameCOPn
A response similar to the following appears:
Pinging cs5100s.sandiegoca.ncr.com [153.64.116.94] with 32 bytes of
data:
Reply from 153.64.116.94: bytes=32 time=60ms TTL=60
Reply from 153.64.116.94: bytes=32 time=40ms TTL=60
Reply from 153.64.116.94: bytes=32 time=30ms TTL=60
Reply from 153.64.116.94: bytes=32 time=50ms TTL=60
Ping statistics for 153.64.116.94:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 60ms, Average = 45ms
Run a second test to verify communication to the Teradata Database by entering the following
at the command prompt:
telnet dbcnameCOPn
If the telnet service is disabled, you should receive the following response appears:
telnet: connect: Connection refused
If the connection is successful, a response similar to the following appears:
Welcome to the NCR MP-RAS SVR4 UNIX System
UNIX System V Release 4.0 (cs5100s) (pts/0)
login:
If one of these responses is not received, consult the next section, Task 2: Troubleshoot
Network Problems.
Note: dbcnameCOPn should be upper or lower case.
Problem 3: Incorrect Path Name in COPLIB
Verify that the environment variable COPLIB has the correct path name to the CLI system
parameter block file, clispb.dat.
COPLIB is not setup during installation.
Problem 4: File localisation.dll Could Not Be Opened
If the localisation.dll file is missing, this message appears:
"File "localisation.dll" could not be opened.
There may be problems with your installation.
Exiting..."
Check that the environmental variable PATH contains the folder where the localisation.dll file
resides.
274
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 23: Troubleshooting the Installation
Task 1: Troubleshoot Client Computer Problems
Problem 5: File icuuctd36.dll Could Not Be Found
If the icuuctd36.dll file is missing, this message appears:
The dynamic link library icuuctd36.dll could not be found in the
sprecified path.
Make sure the environment variable PATH contains the folder where icuuctd36.dll is located.
Problem 6: Incorrect Path Name in COPANOMLOG
To produce an anomaly log file, check that the environment variable COPANOMLOG has the
correct path name to the anomaly log file.
Problem 7: Incorrect CLIv2 Libraries Referenced
CLIv2 installs CLIv2 DLLs in different directories under Teradata Client. During the
installation, the system PATH environment variable is pre-pended with the directory of where
the CLIv2 DLLs are located. Where the DLLs are first found in the system PATH determines
how an application accesses the CLIv2 DLLs. The system PATH must be modified to access the
correct version of the CLIv2 DLLs.
Problem 8: CLIv2 DLLs Load Error
CLIv2 libraries are no longer installed in the %System32% directory. The libraries are now
installed under \Teradata\Client. The system PATH environment variable is pre-pended with
proper installed directories during installation. In order for the system PATH to take effect,
reboot the system or restart the command shell. Also, remove the old CLIv2 libraries from
%system32% directory.
Problem 9: Incorrect Entries in the hosts File
Perform the following checks in the %SystemRoot%\system32\drivers\etc\hosts file on the
client computer, or in the hosts file on the NIS master:
•
Check all entries for incorrect, missing, or duplicate network addresses of COPs, APs, or
nodes. A TCP/IP (Internet) address is a 4-byte value in the form a.b.c.d. COPs, APs, or
nodes on the same logical network must have the same network ID portion of the network
address.
•
Check that COPs, APs, or nodes in the same group for a Teradata have the same dbcname,
and that they are numbered sequentially, starting with 1. The format of a COP name is
dbcnameCOPn, where dbcname must begin with an alphabetic character.
Problem 10: Missing Entries in the services File
Check for the following lines in the %SystemRoot%\system32\drivers\etc\ services file, or in the
services file on the NIS master:
tdmst 1025/udp
tdses 1025/tcp
Teradata Tools and Utilities Installation Guide for Microsoft Windows
275
Chapter 23: Troubleshooting the Installation
Task 1: Troubleshoot Client Computer Problems
Problem 11: Incorrect clispb.dat Parameters
Check the parameter values in the system parameter block file, clispb.dat.
The default i_dbcpath must correspond to the dbcnames in the
%SystemRoot%\system32\drivers\etc\hosts file on the client computer or in the hosts file on the
NIS master.
Problem 12: Cannot Log On from CLI Application
If an old application cannot logon to the Teradata Database from the CLI application, try
logging on from BTEQ.
If BTEQ works, then check the application for errors.
Problem 13: Cannot Log On to the Teradata Database
If a logon to a Teradata Database is not successful, try logging on to a different Teradata
Database.
If the logon to a different Teradata Database is successful, there may be something wrong with
the first Teradata Database, or something wrong with the address of the first Teradata
Database in the local hosts file or in the hosts file on the NIS master.
Problem 14: MSVCR80.DLL not found Message
If a “MSVCR80.DLL not found” message appears when trying to start a CLIv2-based
application, reboot the system.
Problem 15: Troubleshooting OLE DB Provider for Teradata Installation
Use the following procedures to troubleshoot OLD DB Provider for Teradata Problems.
Administrator Privileges
To install OLE DB Provider for Teradata, you must log on to the system as a user with
administrator privileges. The installation fails if you are not logged on with administrative
privileges.
Installation Failure - Custom Setup
If a custom installation fails when MDAC is not installed, a message similar to the following
message appears. To resolve MDAC runtime issues for a custom setup, use the following
remedy.
276
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 23: Troubleshooting the Installation
Task 1: Troubleshoot Client Computer Problems
Remedy
To resolve MDAC runtime issues for a custom setup
1
Click Finish to end the installation program.
2
Using Windows Explorer, find the drive containing the TEMP directory.
3
Use Notepad to view the log file found in \TEMP\TDOLEDB.log.
4
In the log file, find the ERROR line that describes the error and shows the activities that
took place just before the error happened.
5
Reinstall OLE DB Provider. Select the Typical setup type to install the MDAC utility.
Installation Failure - Typical Setup
If a typical installation fails, a message similar to the following message appears. To resolve
MDAC runtime issues for a typical setup, use the following remedy.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
277
Chapter 23: Troubleshooting the Installation
Task 1: Troubleshoot Client Computer Problems
Remedy
To resolve MDAC runtime issues for a typical setup
1
Click Finish to end the installation program.
2
Using Windows Explorer, find the drive containing the TEMP directory.
3
Use Notepad to view the log file at \TEMP\TDOLEDB.log.
In the log file, find the ERROR line that describes the error and shows the activities that
took place just before the error happened. Following is an example of the ERROR line:
ERROR: MDAC installation failed. Please see C:\WINDOWSDASETUP.LOG
Notice that the ERROR line indicates that a failure occurred during the Microsoft Data
Access Components installation. The ERROR line also contains an instruction to inspect
the MDAC setup log.
4
Using Windows Explorer, locate the DASETUP.log setup log file in the system directory of
your system drive.
5
Use Notepad to open the DASETUP.log setup log file.
6
Correct the failing condition. For example, in the following log excerpt, the Missing
Dependency lines indicate that an error occurred because the version of Internet Explorer
is out of date.
Missing Dependency: This product required Microsoft Internet Explorer
4.01 sp2 or greater. Please exit setup and install the latest
Microsoft Internet Explorer.
7
Reinstall OLE DB Provider for Teradata. Select the Typical setup type.
MDAC Installation Failure
If the following message appears when using setup.exe to install MDAC, use the following
remedy.
Remedy
To resolve an installation failure
1
Click Yes.
Notepad displays the log file \DASETUP.log:
278
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 23: Troubleshooting the Installation
Task 1: Troubleshoot Client Computer Problems
2
The most common types of MDAC installation failures are due to missing dependencies
resulting from unsupported configurations of hardware or software, as shown in the
following log excerpt:
Missing Dependency: This product required Microsoft Internet Explorer
4.01 sp2 or greater. Please exit setup and install the latest
Microsoft Internet Explorer.
3
Install the resources that match the minimum supported configuration of hardware and
software. See “Step 5: Determine Minimum Configurations.”
4
Reinstall OLE DB Provider for Teradata. Select the Typical setup type.
Microsoft Data Link Error
If the following warning appears when trying to connect to Teradata Database, use the
following remedy.
Remedy
To resolve a connection error
1
Click OK.
2
Verify that the Teradata Server Name, User name, and password are correct.
Refer to Verifying the OLE DB Provider for Teradata Installation where you entered this
information.
3
Verify that Teradata Database is up and functioning properly by trying to establish a
connection to the database using BTEQ.
4
Contact the Teradata Support Center if you need more assistance.
User is Not a Member of Administrators Group
If the following warning appears when using setup.exe to install software, use the following
remedy.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
279
Chapter 23: Troubleshooting the Installation
Task 1: Troubleshoot Client Computer Problems
Remedy
You must be logged on to the system as a user with administrative privileges to install the
software.
To resolve an Administrators group error
1
Click OK.
2
Log off the system.
3
Ensure your system meets the requirements in Step 5: Determine Minimum
Configurations. Pay special attention to the requirement for administrative privileges.
4
Reinstall OLE DB Provider for Teradata.
Wrong Operating System or Internet Explorer
If a warning similar to the following example appears when using the setup.exe to install
software, use the following remedy.
Remedy
Your operating system and version of Internet Explorer must meet the requirements given in
Step 5: Determine Minimum Configurations.
To resolve a service pack error
1
Click OK.
2
Referring to Step 5: Determine Minimum Configurations, install the correct operating
system and Internet Explorer to meet the minimum requirements.
3
Reinstall OLE DB Provider for Teradata.
Not Enough Space on System Disk
If the following warning appears when using setup.exe, use the following remedy.
280
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 23: Troubleshooting the Installation
Task 2: Troubleshoot Network Problems
Remedy
MDAC installs on the drive that contains the operating system. You must increase the free
space on your system drive.
To resolve a disk space error
1
Click OK.
2
Read Step 5: Determine Minimum Configurations to find out how much space must be
available on your system drive.
3
Increase the available space on the system drive to at least the required amount.
4
Reinstall OLE DB Provider for Teradata.
Not Enough Space on Destination Disk
If the following warning appears when using setup.exe to install software, use the following
remedy.
Remedy
MDAC installs on the drive that contains the operating system. OLE DB Provider for Teradata
installs on the destination disk you chose during the installation. The destination disk might
be the system disk, or it might be a different disk. You must have enough storage space on the
required disks to accommodate the new software components, as well as the temporary
installation files.
To free up disk space
1
Click OK.
2
Read Step 5: Determine Minimum Configurations to find out how much space must be
available on your system drive and your destination drive.
3
Increase the available space on the appropriate drives to at least the required amounts.
4
Reinstall OLE DB Provider for Teradata.
Task 2: Troubleshoot Network Problems
Network problems can be due to network hardware or software.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
281
Chapter 23: Troubleshooting the Installation
Task 2: Troubleshoot Network Problems
Procedure - Troubleshooting Network Problems
Follow these steps to determine whether a network problem is due to network hardware, or
software.
1
Verify that the transceiver is connected to the network, the computer, and the Teradata
Database. (Completing all steps may not be necessary.)
2
Check for broken or disconnected network cables.
3
Check for excess lengths of all drop cables (they should follow the IEEE 802.3 standards).
4
Check all repeaters, bridges, routers, and gateways for correct operation.
5
Check the network controller board to verify that all jumpers are setup correctly.
6
Verify that the network software is installed and running correctly on the computer.
7
Verify that the network software is compatible with the network controller board installed
on the computer.
8
Use a network utility program to confirm that the network is operational.
9
Use a network utility program from another computer on the same network segment as
the first computer to confirm that the network is operational. If this works, there may be a
problem with the first computer.
10 Use a network utility program from another computer on a different network segment
than the first computer to confirm that the network is operational. If this works, there may
be a problem with the first network segment.
11 If a network controller board was replaced in the computer, restart the Teradata Database
so it can obtain the network address of the new board.
12 If the network configuration was changed, check that all network-related files were
changed accordingly (refer to the previous section, Task 1: Troubleshoot Client Computer
Problems).
13 Restart the computer to reset network hardware and reload network software.
Problem 1: Troubleshooting Network Installations
Silent Installation Result Codes
Silent installation creates a product setup log file, <product-release>.log. If failure occurs, refer
to the log for debug information.
Location of the Setup Log
The product setup log file is in the %TEMP%\ClientISS folder. The name of the product setup
log file is <product-release>.log. For example, MultiLoad’s setup log file would be MultiLoad13.10.log.
282
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 23: Troubleshooting the Installation
Task 3: Troubleshoot Software Problems
Task 3: Troubleshoot Software Problems
This section contains solutions to software problems that can be encountered.
Problem 1: Error Running ttu.exe
The following error message can appear while installing a package copied to a network drive:
The parameter is incorrect
This error can occur if the path to the setup.exe file is too long. To resolve the problem, shorten
the path to the setup.exe file. One way to do this is to move the file up in the directory
structure.
Map a network drive letter to the Disk1 or other folder further down the pathname to produce
a new shorter pathname.
If the Install button does not work, see “Problem 2: Install Button Does Not Work.”
Problem 2: Install Button Does Not Work
If the contents of a CD are copied to a network drive and the path to the ttu.exe file is too long,
clicking on the Install button after the DemoShield displays will have no effect.
To resolve the problem, shorten the path to the ttu.exe file. One way to do this is to move the
file up in the directory structure.
Problem 3: InstallShield 1603 Error
The following error message can appear during the installation:
1603: Fatal Error During Installation
Or the following message can appear:
Error 1603: General Windows Installer engine error. Increase
DiskSpace requirement in Setup.ini and try again.
Some known causes for this error are as follows:
•
The computer does not have enough disk space for the installation.
Solution: Increase the disk space.
•
The Temp directory is not clean.
Solution: Find the Temp directory and delete its contents.
•
A file on the installation Computer is locked.
Solution: Close all running applications and reboot the computer. Then run the
installation again.
•
The Windows Installer is not be properly installed.
Solution: Update the installation computer with the latest Windows Installer Service.
•
Improper or incorrect Administrative privileges.
Solution: Confirm the proper privileges.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
283
Chapter 23: Troubleshooting the Installation
Task 3: Troubleshoot Software Problems
•
The installation computer may have traces of a previous installation present.
Solution: Use Microsoft’s Windows Installer Clean Up utility to remove the previous
install. Also, manually remove files that may have been installed.
Problem 4: InstallShield 1607 Error
The following error message can appear:
1607: Unable to install InstallShield Scripting Runtime
Little information is known at this time about the specific cause of this initialization error, as
it rarely occurs and is typically encountered on an intermittent or machine-specific basis.
Some known causes for this error are as follows:
•
There is a special character in the directory path containing the installation files.
If the installation files have been copied to a folder on a hard drive, and the full path
contains special characters, such as “&”, “-”, “.”, etc., move the installation files to a path
which does not contain special characters.
Example of bad path:
C:\tmp\downloads & packages\PMon\setup.exe
Example without the special character:
C:\tmp\downloads\PMon\setup.exe
•
On Windows XP, there is a known issue with the Microsoft Windows Installer Service that
affects all MSI-based setups. This error results when an MSI-based setup is run from a
virtual drive created by the “subst” command.
If running on a Windows XP machine, make sure the setup is not running from a virtual
drive created by the “subst” command.
•
The file “IDriver.exe” is not registered properly.
Register the file “IDriver.exe” by using the command line below:
<ProgramFiles>\Common Files\InstallShield\Developer\9\Intel
32\IDriver.exe /REGSERVER
This command line can be entered in the Windows Start | Run dialog, after replacing
<ProgramFiles> with the location of the Program Files directory.
•
Permissions on the <Temp> folder are insufficient.
Verify that the SYSTEM has full permission on the UserID %TEMP% folder. For example,
on a computer running the Windows 2000 operating system, if UserID is fsk, the UserID
%TEMP% folder may be <Boot Drive>:\Documents and Settings\fsk\Local Settings\Temp.
•
Permissions on the <WindowsFolder>\Installer folder are insufficient.
Follow the steps below to setup the proper permissions:
<WindowsFolder>\Installer folder:
Procedure - Setting Permissions to the Installer Folder
Follow these steps to setup permissions to the Installer Folder.
284
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 23: Troubleshooting the Installation
Task 3: Troubleshoot Software Problems
1
Locate the folder <WindowsFolder>\Installer. (For example, on Windows 2000 this folder
would be “C:\WINNT\Installer”)*
2
Right-click the Installer folder, and choose “Properties.”
3
Select the “Security” tab.
4
Verify the system, as well as the specific user, has full control of this folder.
Note: This folder is hidden by default in the Windows environment. Therefore it may be
necessary to enter this path directly in the Windows Start | Run dialog to access this folder.
•
The file “msiexec.exe” is not registered properly.
Register the file “msiexec.exe” by using the command line below:
<WindowsFolder>\System32\msiexec.exe /REGSERVER
This command line can be entered in the Windows Start | Run dialog, after replacing
<WindowsFolder> with the location of the Windows folder.
•
There are insufficient privileges in Windows.
Verify the user has full administrative permissions for this Windows machine.
•
Another instance of the file “msiexec.exe” is running.
Kill unproductive copies of msiexec.exe using the Task Manager Processes tab.
•
Another MSI-based setup is running simultaneously.
Make sure no other MSI-based installations are running simultaneously.
•
DCOM impersonation level is set incorrectly.
The solution for the Windows 2000 Professional is to change the value for the “Default
Impersonation Level” from “Anonymous” to “Identify” using the “dcomcnfg” utility.
Procedure - Changing the Default Impersonation Level on Windows 2000
For Windows 2000, follow these steps to change the Default Impersonation Level from
“Anonymous” to “Identify.”
1
Click Start->Run and type dcomcnfg in the Open field.
2
Click OK.
3
Select “Default Properties” tab.
4
In the “Default Impersonation Level” list, select “Identify.”
5
Click OK.
The following procedure changes the “Default Impersonation Level” to “Identify” using the
“dcomcnfg” utility on Windows XP Professional:
Procedure - Changing the Default Impersonation Level on Windows XP
For Windows XP, follow these steps to change the Default Impersonation Level from
“Anonymous” to “Identify.”
Teradata Tools and Utilities Installation Guide for Microsoft Windows
285
Chapter 23: Troubleshooting the Installation
Task 4: Troubleshoot Teradata Database Hardware Problems
1
Click Start->Run and type dcomcnfg in the Open field.
2
Click OK.
3
In the console tree of the Component Services administrative tool, right-click the
computer whose machine-wide impersonation level you want to modify and then click
“Properties.”
4
Select the “Default Properties” tab.
5
Ensure that “Enable Distributed COM on this computer” is checked.
6
In the “Default Impersonation Level” box, select “Identify.”
7
Click OK.
Problem 5: InstallShield 432 Error
If installing from the CD to a computer that runs on the Windows 2000, or Windows XP
operating system, you can receive an error indicating that UnInstallShield is running
(InstallShield Error 432).
Procedure - Deleting ISUnist.exe
Follow these steps if you receive an InstallShield 432 error.
1
Verify that the logon has administrative privileges.
2
Delete all instances of IsUninst.exe from the Windows folder and run setup again.
3
If IsUninst.exe cannot be deleted because it is in use, reboot the machine and run setup
again.
Task 4: Troubleshoot Teradata Database
Hardware Problems
Teradata Database hardware problems should be diagnosed with the assistance of a Teradata
field service representative.
The following procedure helps determine if there is a database hardware problem, and if the is,
where it is located.
Procedure - Determine whether Database Hardware is Working Properly
Follow these steps to determine whether Database hardware is working properly. Steps 2
through 7 apply to the Teradata Database only.
286
1
Logon to the Teradata Database from the operator console, another network-attached
host, or a mainframe. If you are able to logon, the hardware is operational. If you are
unable to logon, contact your Teradata field service representative.
2
Have a field service representative verify that the adapter cable is connected.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Chapter 23: Troubleshooting the Installation
Task 4: Troubleshoot Teradata Database Hardware Problems
3
Have a field service representative check the Multibus Adapter Board (MAB).
4
Check for the following characteristics in all entries of the CopInfoTbl file on the Teradata
Database:
5
•
Incorrect, missing, or duplicate cabinet and processor numbers (ccc_p) for
applications processors (APs)
•
Incorrect, missing, or duplicate network addresses
•
Correct network protocol type (CopKind) for each AP
•
Correct host number for each AP
•
Entries in the CopInfoTbl file match the entries in the
%ProgramFiles%\Teradata\Client\<version>\Teradata Parallel Transporter\hosts file
(on the computer) or in the hosts file on the NIS master; use the CopUpdate macro to
change the CopInfoTbl file.
If necessary, run the CopUpdate macro.
If an AP is added or removed from the Teradata Database or if an AP’s network address is
changed, the CopUpdate macro must be executed so the Teradata Database can determine
changes to network addresses. (The Teradata Database must be restarted before the
changes can take effect.)
6
7
If using Internet routing (routers), check the CopRoutesTbl file for the following:
•
Incorrect or missing network addresses of destinations
•
Incorrect or missing network addresses of routes
•
Each router is identified by two (or more) Internet addresses, one for each network on
which it resides
•
Use the TcpRoute macro to change the CopRoutesTbl file
If using subnet routing (subnetting), check the CopOptionsTbl file for incorrect or missing
subnet masks.
(To change the CopOptionsTbl file, use the AddOption macro.)
8
If the Teradata Database goes down and then comes back up, its sessions table still contains
information generated by the hosts that were connected when it went down.
The Teradata Database expects to receive reconnect messages from those hosts. If it does
not receive a reconnect message within 20 minutes after it comes back up, it will remove
the sessions generated by hosts that have not reconnected.
Therefore, for 20 minutes after the Teradata Database comes back up, some sessions are
being kept that may not be used. If use of the Teradata Database is heavy, users unable to
log on during that 20-minute period (because the maximum number of sessions has been
reached) can try again after the unclaimed sessions are cleared.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
287
Chapter 23: Troubleshooting the Installation
Task 4: Troubleshoot Teradata Database Hardware Problems
288
Teradata Tools and Utilities Installation Guide for Microsoft Windows
CHAPTER 24
Technical Assistance
This section provides information on how to get technical assistance if you have a problem
with the installation you cannot resolve.
Technical Assistance
Technical assistance during installation of the Teradata Tools and Utilities software is available
from the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC).
For more information, refer to the Teradata Tools and Utilities Release Definition, Release 13.1.
Teradata Tools and Utilities Installation Guide for Microsoft Windows
289
Chapter 24: Technical Assistance
Technical Assistance
290
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Index
Index
Symbols
.NET Framework 47
.NETteragss
configure 51
_unodbc.dll 162
A
application, cannot log on 276
ARC
default destination folder 94
default program folder 94
dependencies 240, 246
product response file name 94
arcmain.exe 167
attributes.twb.xsl 208
authentication mechanism 263
Automatic DIM Update
action processor
starting/stopping 86
and RSG 74, 76
DDL Gateway 57, 74
database connection information 75
server 77
starting/stopping 85
user accounts 76
installing update files 62
MDS Action Processor 57, 75
MDS Recovery Table 76
nodes
configuring 81
processes 74, 76
RSG
starting/stopping 80
B
base.twb.xsl 208
bignumu.dll 213
blkexit.c 171
blkexit.mak 171
blkexitr.c 171
BlockLoad.h 197
BTEQ
default destination folder 95
default program folder 95
dependencies 239, 245
Teradata Tools and Utilities Installation Guide for Microsoft Windows
bteq.exe 158
bteqwin.exe 158
bteqwin_enu.chm 158
bteqwin_jpn.chm 158
bteqwin_jpn.dll 158
btnfyext.c 158
btnfyext.def 158
btnfyext.h 158
btnfyext.mak 158
C
cannot communicate over network 274
cannot log on from CLI application
CLI 276
cannot log on to database 276
caputl.dll 158
Character Set box 148
checkpoint 206
cleanupTables.bteq 200, 204
clisamp.c 169, 170
clispb.dat 169
clispb.dat, incorrect parameters 276
CLIv2
defining the system address 147
cliv2if.h 169, 170
columns.twb.xsl 208
computer problems
troubleshooting 273
configure
.NETteragss 51
Connection.h 197
coordinator.exe 206
COPANOMLOG 142
incorrect path name 275
coperr.h 169, 170
COPLIB 141
incorrect path name 274
coptypes.h 169, 170
D
DASETUP.log 278
Data Definition Language See DDL
data source name See DSN
data.in 209
database information metamodel SeeDIM
database name, specifying 146
291
Index
DataConnector Operator
dependencies 242
dataconop.dll 207
dbcacnx.h 169, 170
dbcarea.h 169, 170
dbcerr.h 169, 170
dbms.twb.xsl 208
DDL Gateway
Automatic DIM Update 57
ddlop.dll 207
dependencies 47
dependencies, missing during installation 278
DMLGroup.h 197
Domain Name Services (DNS) 145
download
.NET Data Provider for Teradata 48
drivers
TCP/IP 26, 95, 251
Token Ring packet 26, 95, 251
E
environment parameters
setting 141
ERROR line, tdoledb.log 278
executor.exe 206
expnfyxt.c 205
Export Operator
default destination folder 97
default program folder 97
product response file name 97
exportop.dll 205
F
fastload.exe 171
feimod.c 171
fenotf.c 171
feomod.c 171
feomop.dll 207
fexp.exe 171
file.twb.xsl 208
flimop.dll 207
flnfyext.c 171
fspread.dll 231
G
generic.h 197
GenericDriver.cpp 201, 205
GenericDriver.h 201, 205
GetBuffer.h 200, 204
getbuffer.sln 200
getbuffer.vcproj 200
getbuffer64.sln 204
292
getbuffer64.vcproj 204
GetHostByName
limiting requests 142
GT11.txt 209
GT44.txt 209
GT62.txt 209
GT93.txt 209
GT94.txt 209
GT95.txt 209
GT96.txt 209
GT97.txt 209
guisrv.dll 207
H
hardware problems
troubleshooting 286
help 208
hosts file 139, 145
adding entries to 140
incorrect entries 275
HOSTS file, modifying 146
I
icudttd361.dll 164, 165
icuintd36.dll 164, 165
icuiotd36.dll 164, 165
iculetd36.dll 164, 165
iculxtd36.dll 164, 165
icuuctd36.dll 164, 165
incorrect
clispb.dat parameters 276
incorrect entries in hosts file 275
incorrect path name in COPANOMLOG 275
incorrect path name in COPLIB 274
parameter is incorrect 283
infile.littleEndian 201, 205
input.exp 201, 205
input.lod 201, 205
input.stm 201, 205
input.txt 200, 204
input.upd 201, 205
insertop.dll 207
install
.NET Data Provider for Teradata 49
dependent products 48
verify the installation 51
Internet Explorer, required version 256
IP address, specifying 146
J
job.twb.xsl 208
jobstep.twb.xsl 208
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Index
jobvars.txt 209
L
LABSBTEQ 168
ldnfyext.c 210
libmqs.dll 231
libmqsc.dll 231
libpm.dll 170, 171
limiting GetHostByName requests 142
Load Operator
default destination folder 98
default program folder 98
loadop.dll 210
local hosts file 145
localisation.dll 169, 170
file could not be opened 274
logger.twb.xsl 208
logon
dialog box 261
procedures 261
logs 206
logview.dll 207
logview.twb.xsl 208
M
main.cpp 200, 204
makesamp.win 169, 170
MDAC runtime issues 276
MDS
core files
MetaBrowse 56
MetaManager 56
developer’s kit
installing
on Windows 60
Unicode 60
development kit 56
installation prerequisites 54
ASP compliant server 56
database size 55
Teradata database 55
Teradata user account 55
Windows workstation 55
installing
on Windows 57
repository
creating
on Windows 69
migrating
on Windows 70
MDS Action Processor
Automatic DIM Update 57
mechanism 145
Teradata Tools and Utilities Installation Guide for Microsoft Windows
MetaManager
nodes
adding 81
MetaSurf
ASP compliant web server 54
installing 61
virtual directory 71
metaviews 55
MFC80.dll 196
mgrcli.dll 231
missing entries in services file 275
mlimod.c 195
mlimop.dll 207
mlnotf.c 195
mload.exe 195
modifying
HOSTS file 146
monpm.dll 231
mosiif.h 169, 170
MSVC80.dll 196
MSVCIRT.DLL 207
MSVCIRTD.DLL 207
MSVCP60.DLL 207
MSVCP60D.DLL 207
msvcp71.dll 197
msvcr.71.dll 197
msvcr80.dll 231
N
Named Pipes Access Module
default destination folder 96
default program folder 96
dependencies 239, 245
network
parameters, setting 139
troubleshooting 281
nodes
adding 81
configuring for Automatic DIM Update 81
nojunk.h 169, 170
np_AXSMOD.dll 159
np_AXSMODenu.dll 159
O
objects.twb.xsl 208
ODBC
data source administrator 144
ODBC Driver for Teradata
configuring 144
default destination folder 93
default program folder 93
dependencies 239, 246
ODBC DSN
293
Index
configuring
on Windows 55
odbcop.dll 207
OLEDB_AXSMOD.dll 196
OLEDB_AXSMODenu.dll 196
OLEDB_AXSMODjpn.dll 196
oleload.exe 196
opcommon.dll 197, 201, 207
operation.twb.xsl 208
operator.twb.xsl 208
opermsgs.dll 197, 201, 208
OptionsReader.cpp 201, 205
OptionsReader.h 201, 205
oscmdop.dll 207
P
parameters 145
setting environment 141
setting network 139
setting system 144
parcel.h 169, 170
Pbocd0x0.txt 162
planexecutor.exe 206
pmdcomt.h 170, 171
pmddamt.h 170, 171
port number
setting using TDMSTPORT 143
PPCLB1 168
PPCLB2 168
PPCLB3 168
PPCLB4 168
PPCLB5 168
PPCLB6 168
PPCLB7 168
PPCLB8 168
PPCLB9 168
ppcmain.exe 167, 168
ppruntim.dll 167, 168
ppruntim.lib 167, 168
Preprocessor
default destination folder 96
default program folder 96
dependencies 240, 246
product response file name 96
product version numbers 3
program.ico 196
psaload.dll 231
ptmexec.exe 206
ptmgts.exe 206
ptmjlgr.exe 206
ptmlvs.exe 206
ptmtims.exe 206
publisher policy 48
294
pxdef.h 207
pxdtypes.h 207
pxicu.dll 197, 201, 207
pxlogdef.h 207
pxmacros.h 207
pxoper.h 207
pxos.h 207
pxstc.h 207
pxtypes.h 207
pxutypes.h 207
pxversion.h 207
R
readme.doc 209
Readme.txt 162
readme.txt 213
Relay Services Gateway See RSG
Request Processor Processes box 148
requests
GetHostByName 142
resource.h 169, 170
RSG
stopping 80
runtbuild.cmd 208
S
samplefilter.cpp 209
sampleoperator.dsp 209
sampleoperator.dsw 209
samples.jar 183
samplescript.txt 209
Schema.h 197
schema.twb.xsl 208
SELECT privileges
Teradata user account 55
selectop.dll 207
server name
configuration entry 145
Server Parameters dialog box 148
services file
missing entries 275
session limits
bteq 25
setup.log 282
setupTables.bteq 200, 204
Shared ICU Libraries for Teradata 93, 240, 246
Shared Memory Size (KB) text box 148
silent installation
troubleshooting 282
software problems
troubleshooting 283
sql1.txt 209
sql2.txt 209
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Index
sqlprs.dfa 213
sqlprs.llr 213
stmnfyxt.c 210, 211
Stream Operator
default destination folder 99
default program folder 99
streamop.dll 210, 211
support 289
supported software releases 3
syntax
for hosts file entries 140
T
table.twb.xsl 208
tables
accessing 55
permissions 63
tableset.twb.xsl 208
tbuild.exe 206
tbuildexe.exe 206
TCP/IP driver 26, 95, 251
tdapp.dll 231
tdata32.dll 162
tdatas32.dll 162
tdatpump.cfg 196
tdgssconfig.jar 183, 208
tdgssjava.jar 208
tdis.dll 231
tdmfcis.dll 231
TDMSTPORT
setting the port number 143
tdodbcdsn.vbs 162
TDOLEDB.log 277, 278
tdprsr32.dll 162
tdqmcomm.dll 213
tdqmcomm.exe 213
tdqmdb.exe 212
tdqmjob.exe 213
tdqmlsnr.exe 213
tdqmops.exe 213
tdqmreqp.exe 213
tdqmserv.dll 213
tdqmserv.exe 213
tdqmsr.dll 213
tdqmsubm.dll 213
tdqmview.exe 213
tdqsadm.exe 212
tdsql.h 162
tdsqlprs.dll 213
tdtmgr.dll 231
tdusr32.dll 169, 170
tdwmutil.dll 231
tdxodbc 162, 163
Teradata Tools and Utilities Installation Guide for Microsoft Windows
technical support 289
telapi.dll 197
telapi.lib 197
teqtalk.ico 158
Teradata Administrator
configuring 149
default destination folder 96
default program folder 96
dependencies 240, 246
Teradata Archive/Recovery Utility (ARC) 94
Teradata Call-Level Interface version 2 (CLIv2)
default destination folder 94
default program folder 94
dependencies 240, 247
Teradata Data Connector
default destination folder 94
default program folder 94
dependencies 240, 247
Teradata Database
cannot log on to 276
identifying 140
required versions 256
Teradata FastExport
default destination folder 95
default program folder 95
dependencies 240, 247
product response file name 95
Teradata FastLoad
dependencies 241, 247
Teradata Generic Security Services 93
Teradata Generic Security Services Client
dependencies 241, 247
platforms supported 255
Teradata Index Wizard
default destination folder 99
default program folder 99
dependencies 241, 248
Teradata JDBC Driver 271
supported on 241, 248
Teradata MultiLoad
default destination folder 95
default program folder 95
dependencies 241, 248
product response file name 95
Teradata OLE DB Access Module
default destination folder 96
default program folder 96
dependencies 241, 248
product response file name 96
Teradata Parallel Transporter
configuring 149
Teradata Parallel Transporter Infrastructure
default destination folder 97
default program folder 97
295
Index
version 242
Teradata Performance Monitor
dependencies 242, 250
Teradata QS server
configuration, changing 148
default 147
parameters, changing 148
Teradata Query Director
dependencies 242, 251
Teradata Query Scheduler Administrator 243, 251
Teradata Query Scheduler Client 243, 251
default destination folder 95
default program folder 95
Teradata Query Scheduler Server 243, 251
default destination folder 95
default program folder 95
Teradata SQL Assistant
default destination folder 96
default program folder 96
dependencies 243, 252
Teradata Statistics Wizard
default destination folder 99
default program folder 99
dependencies 243, 252
Teradata System Emulation Tool
default destination folder 97
default program folder 97
dependencies 243, 252
product response file name 97
Teradata Tools and Utilities 239
Teradata TPump
default destination folder 95
default program folder 95
dependencies 241, 249
Teradata user account
SELECT privileges 55
Teradata Visual Explain
default destination folder 96
default program folder 96
dependencies 243, 253
product response file name 96
Teradata WebSphere MQ Access Module 243, 253
default destination folder 99
default program folder 99
Teradata Workload Analyzer 243, 253
default destination folder 99
default program folder 99
terajdbc4.jar 183, 208
terasso.dll 162, 169, 170
tldnfyxt.c 196
tlogview.exe 206
tlogviewexe.exe 206
tm_dialogs.dll 231
tptlaunch.exe 206
296
tptwizard.cmd 208
tptwizard.ico 208
tptwizard.jar 208
tpump.exe 196
tpumpar.csql 196
tpumpimd.c 196
troubleshooting
client computer problems 273
client problems 273
hardware problems 286
network problems 281
silent installation 282
Teradata Database problems 286
troubleshooting, installation 277
TSCS-RSC 289
twa.exe 231
twb_status.txt 209
twb_targets.txt 209
twbcfg.ini 206
twbcmdexe.exe 206
twbkill.exe 206
twbkillexe.exe 206
twbmsgs.dll 208
twboper.ini 206
twbpath.exe 206
twbpathexe.exe 206
twbrmcp.exe 206
twbrmcpexe.exe 206
twbstat.exe 206
twbstatexe.exe 206
twbwizard.properties 208
U
Uninst.dll 196
uninstall
.NET Data Provider for Teradata 51
Update Operator
default destination folder 98
default program folder 98
updateop.dll 211
updnfyxt.c 211
user
DSN 144
User Exit functions 43
CLI 43
V
verify
installation 51
verify.dat 231
Verify.exe 231
verifying installation 157
version 209
Teradata Tools and Utilities Installation Guide for Microsoft Windows
Index
.NET Data Provider for Teradata 47
Microsoft .NET Framework 47
version numbers 3
Visual C++ 8.0 CRT (x86) 159
Visual C++ 8.0 MFC (x86) 159
Visual C++ 8.0 MFCLOC (x86) 159
Visual Studio 2005 47
Visual Studio 2008 47
W
wincli32.dll 169, 170
wincli32.lib 169, 170
wincliv2.h 169, 170
wwhelp.dll 207
X
xsp.cpp 201
xsp.sln 201
xsp.vcproj 201
xsp64.sln 205
xsp64.vcproj 205
Teradata Tools and Utilities Installation Guide for Microsoft Windows
297
Index
298
Teradata Tools and Utilities Installation Guide for Microsoft Windows