Download Teradata Tools and Utilities Release Definition

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Document related concepts

IMDb wikipedia, lookup

Microsoft Access wikipedia, lookup

Entity–attribute–value model wikipedia, lookup

Oracle Database wikipedia, lookup

Concurrency control wikipedia, lookup

Microsoft SQL Server wikipedia, lookup

SQL wikipedia, lookup

Functional Database Model wikipedia, lookup

PL/SQL wikipedia, lookup

Extensible Storage Engine wikipedia, lookup

Database wikipedia, lookup

Ingres (database) wikipedia, lookup

Microsoft Jet Database Engine wikipedia, lookup

Clusterpoint wikipedia, lookup

Relational model wikipedia, lookup

ContactPoint wikipedia, lookup

Database model wikipedia, lookup

Open Database Connectivity wikipedia, lookup

Transcript
Teradata Tools and Utilities
Release Definition
Release 13.00.01
B035-2029-110C
November 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 © 1994-2010 by Teradata Corporation. All Rights Reserved.
Preface
Purpose
Teradata® Tools and Utilities 13.00.01 is a Teradata Tools and Utilities maintenance media
release containing the most recent product efixes available for the Teradata Tools and Utilities
13.00 release. Teradata Tools and Utilities 13.00 information is available in Teradata Tools
and Utilities 13.00 publications and manuals. Fixes included in Teradata Tools and Utilities
13.00 products in this maintenance release are listed in this document.
Teradata Tools and Utilities is a group of products designed to work with Teradata Database.
Teradata Tools and Utilities Release Definition provides an overview of the products and
programs in Teradata Tools and Utilities 13.00.01. It contains important information received
late in the release not included in other documentation associated with this release. Teradata
Tools and Utilities Release Definition also contains lists of:
•
Teradata Database versions with which Teradata Tools and Utilities 13.00.01 are certified
•
Product release version information
•
Technical changes for each product in this release
•
Documentation that supports this release
•
Training and support centers
Audience
Teradata Tools and Utilities Release Definition is intended for system administrators, analysts,
engineers, and other database specialists who perform product installations or use Teradata
Tools and Utilities products.
Supported Releases
Teradata Tools and Utilities Release Definition supports Teradata Tools and Utilities 13.00.01.
Unless otherwise specified in this document, “this release” refers to Teradata Tools and
Utilities 13.00.01.
For release information on Teradata Database 13.00, see Base System Release Definition,
B035-1725-098K.
Teradata Tools and Utilities Release Definition
3
Preface
Additional Information
Additional Information
Additional information that supports 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
Source
Additional product
information
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/.
2 Click Data Warehousing under Online
Publications, Browse by Category.
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.
CD-ROM images
Ordering
information for
manuals
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/.
Use the Teradata Information Products web
site to order printed versions of manuals.
1 Go to http://www.info.teradata.com/.
2 Click Data Warehousing under Online
Publications, Browse by Category.
3 Click CD-ROM Images.
2 Click How to Order under Print & CD
Publications.
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
4
Teradata Tools and Utilities Release Definition
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Chapter 1:
Release Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Key Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Support Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Product Bundling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CDs and Magnetic Tape Cartridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teradata Utility Pack—Utilities (BCD0-1190-0000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Management (BCD0-1195-0000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load/Unload (BCD0-1192-0000). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teradata Parallel Transporter (BCD0-1193-0000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Meta Data Services (BCD0-1242-0000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preprocessors (BCD0-1191-0000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Query Director (BCD0-1255-0000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tape Storage Management Enablers (BCD0-1194-0000) . . . . . . . . . . . . . . . . . . . . . . . . .
Magnetic Tape Cartridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
14
15
15
16
16
17
17
18
18
18
Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
E-Fix Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 2:
Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Product Discontinuances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Product Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Product Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Teradata Tools and Utilities Release Definition
5
Table of Contents
Basic Teradata Query Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
IBM CICS Interface for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
IBM IMS Interface for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Interactive Teradata Query Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
.NET Data Provider for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Supported Versions of Teradata Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Requests for Change (RFCs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Discrepancy Reports (DRs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
ODBC Driver for Teradata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
OLE DB Provider for Teradata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Teradata Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Teradata Access Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Teradata Archive/Recovery Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Teradata Call-Level Interface version 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Teradata Director Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Teradata Dynamic Workload Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Teradata FastExport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Teradata FastLoad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Teradata Generic Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Teradata Index Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Teradata International Components for Unicode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Teradata JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Teradata Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Teradata Meta Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Teradata MultiLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
Teradata Parallel Data Pump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Teradata Parallel Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Teradata Preprocessor2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
6
Teradata Tools and Utilities Release Definition
Table of Contents
Teradata Query Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Teradata Query Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Teradata SQL Assistant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Teradata SQL Assistant/Web Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Teradata Statistics Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Teradata System Emulation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Teradata Visual Explain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Teradata Workload Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Teradata Access Module for Tivoli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Transparency Series/Application Programming Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Chapter 3:
Teradata Tools and Utilities Documentation . . . . . . . . . . . . . . . . . . . 151
Software Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Downloadable Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
151
152
152
Print Documentation and CD-ROMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Orange Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Publication Titles and IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Chapter 4:
Customer Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Customer Education. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Teradata Tools and Utilities Release Definition
7
Table of Contents
8
Teradata Tools and Utilities Release Definition
List of Tables
Table 1: Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 2: Unsupported Teradata 13.0 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 3: Teradata WebSphere MQ Access Module Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 4: Teradata CLIv2 for NAS Sun Solaris Makefiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 5: Installation RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 6: Installation DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 7: BTEQ RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 8: BTEQ DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 9: .NET Data Provider for Teradata RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 10: .NET Data Provider for Teradata DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 11: ODBC Driver for Teradata RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 12: ODBC Driver for Teradata DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 13: OLE DB Provider for Teradata RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 14: OLE DB Provider for Teradata DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 15: Teradata Administrator RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 16: Teradata Administrator DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 17: Teradata Access Module RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 18: Teradata Access Module DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 19: Teradata ARC RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 20: Teradata ARC DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 21: Teradata CLIv2 RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 22: Teradata CLIv2 DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Table 23: TDP RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 24: TDP DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 25: Teradata DWM RFCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 26: Teradata DWM DRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 27: Teradata FastExport RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 28: Teradata FastExport DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 29: Teradata FastLoad RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Table 30: Teradata FastLoad DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Table 31: Teradata Index Wizard RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Table 32: Teradata Index Wizard DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Teradata Tools and Utilities Release Definition
9
List of Tables
Table 33: Teradata ICU RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Table 34: Teradata ICU DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Table 35: Teradata JDBC Driver RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Table 36: Teradata JDBC Driver DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Table 37: Teradata Manager RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Table 38: Teradata Manager DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Table 39: Teradata MDS RFCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Table 40: Teradata MDS DRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Table 41: Teradata MultiLoad RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Table 42: Teradata MultiLoad DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Table 43: Teradata TPump RFCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Table 44: Teradata TPump DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Table 45: Teradata PT RFCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Table 46: Teradata PT API RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Table 47: Teradata PT DRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Table 48: Teradata PT API DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Table 49: Teradata Preprocessor2 for Embedded SQL RFCs . . . . . . . . . . . . . . . . . . . . . . . . . .124
Table 50: Teradata PP2 DRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
Table 51: Teradata QD RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Table 52: Teradata QD DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Table 53: Teradata QS RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Table 54: Teradata QS DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
Table 55: Teradata SQL Assistant RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Table 56: Teradata SQL Assistant DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Table 57: Teradata SQL Assistant/Web Edition DRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Table 58: Teradata Statistics Wizard RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140
Table 59: Teradata Statistics Wizard DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
Table 60: Teradata SET RFCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
Table 61: Teradata SET DRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Table 62: Teradata VE RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Table 63: Teradata VE DRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Table 64: Teradata WA RFCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Table 65: Teradata WA DRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
Table 66: Teradata Tools and Utilities 13.0 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . .154
10
Teradata Tools and Utilities Release Definition
CHAPTER 1
Release Information
This chapter provides an overview of the products and features in the Teradata Tools and
Utilities 13.00.01 and the latest release of Teradata Database, which compose Teradata 13.00.
Key Features
Table 1 lists major enhancements made to the Teradata Tools and Utilities suite of products
in support of Teradata 13.00 features. The enhancements include support for Teradata
Database 13.00 features and Teradata Tools and Utilities-specific improvements.
Note: Not all of the enhancements in this release were made to all of the products in the
Teradata Tools and Utilities suite. The Request for Changes sections in Chapter 2: “Product
Information” list abstracts of enhancements for each product.
Table 1: Key Features
Supported Feature
Teradata Tools and Utilities Product
October 1, 2007, marked the official launch of Teradata
Corporation. All references to NCR in Teradata Tools and
Utilities software and documentation were changed to Teradata.
All Teradata Tools and Utilities products, except Host
Utility Consoles (HUTCNS) and Interactive Teradata
Query (ITEQ).
Additional operating system support.
For details, see Teradata Tools and Utilities 13.0
Supported Platforms and Product Versions, B035-3119.
Access modules built for Teradata load and unload utilities also
work with Teradata Parallel Transporter without any
recompiling or relinking.
•
•
•
•
•
Data Definition Language (DDL) replication allows utility type
names and escape sequences to be expanded in SQL statements
containing the AS USER prefix.
• Basic Teradata Query (BTEQ)
• ODBC Driver for Teradata
• Teradata Call-Level Interface version 2 (CLIv2) for
Network-Attached Systems (NAS)
• Teradata Preprocessor (PP2)
Geospatial data types allow customers to store, manage, and
retrieve information based on aspects of spatial data, such as
geometry, location, and topology.
•
•
•
•
Teradata Tools and Utilities Release Definition
Named Pipes Access Module
OLE DB Access Module
Teradata Data Connector
Teradata WebSphere MQ Access Module
Teradata Parallel Transporter (PT)
ODBC Driver for Teradata
Teradata Administrator
Teradata Archive/Recovery Utility (ARC)
Teradata PP2
11
Chapter 1: Release Information
Key Features
Table 1: Key Features (continued)
Supported Feature
Teradata Tools and Utilities Product
Large Query Support. Queries larger than 10 KB can now be
imported using the SQL table for workload definitions.
• Teradata Index Wizard
• Teradata Statistics Wizard
No Primary Index (NoPI) tables load data faster and more
efficiently. After data is received by Teradata Database and
converted into the proper internal format, all rows in a data
parcel can be appended to a NoPI table without being
redistributed to the corresponding hash-owning AMPs. Because
unhashed tables don’t require rows to be in any particular order,
sorting work is also avoided.
•
•
•
•
•
•
•
•
•
Open Standards Compliance
• ODBC Driver for Teradata
• Teradata JDBC Driver
Ordered analytics allow dynamic partitions based on some
condition; for example:
• ODBC Driver for Teradata
• Teradata Administrator
ODBC Driver for Teradata
Teradata ARC
Teradata Index Wizard
Teradata JDBC Driver
Teradata MDS
Teradata SET
Teradata Statistics Wizard
Teradata TPump
Teradata VE
SUM( x ) OVER (ORDER BY time ROWS UNBOUNDED
PRECEDING RESET WHEN x IS NOT NULL)
PERIOD data types support the following element types:
•
•
•
•
•
PERIOD(DATE)
PERIOD(TIME(n))
PERIOD(TIME(n) WITH TIME ZONE)
PERIOD(TIMESTAMP(n))
PERIOD(TIMESTAMP(n) WITH TIME ZONE)
Scalar sub-queries are supported everywhere a value expression is
allowed compliant to ANSI syntax. Enhances application
migration from other database sources to Teradata Database.
12
•
•
•
•
•
•
•
•
•
•
•
•
•
BTEQ
ODBC Driver for Teradata
Teradata Administrator
Teradata ARC
Teradata CLIv2
Teradata Director Program (TDP)
Teradata FastExport
Teradata FastLoad
Teradata MultiLoad
Teradata OLE DB Access Module
Teradata Parallel Data Pump (TPump)
Teradata PT
Teradata PT Application Programming Interface
(API)
• Teradata PP2
• Teradata Query Scheduler (QS)
• ODBC Driver for Teradata
• Teradata PP2
Teradata Tools and Utilities Release Definition
Chapter 1: Release Information
Key Features
Table 1: Key Features (continued)
Supported Feature
Teradata Tools and Utilities Product
Teradata trusted sessions enables middle-tier applications to
assert user identities and roles for privilege checking and query
logging without establishing a logon session for the middle-tier
application end user.
•
•
•
•
•
•
•
Teradata trusted sessions, or user impersonation with query
banding, provides a mechanism to communicate an alternative
user ID to Teradata Database.
Teradata Active Systems Management Enhancements. See
“Teradata Dynamic Workload Manager” and “Teradata
Workload Analyzer” for details.
ODBC Driver for Teradata
Teradata ARC
Teradata JDBC Driver
Teradata CLIv2 for NAS
TDP
Teradata PP2
Teradata Query Director (QD)
• Teradata Dynamic Workload Manager (DWM)
• Teradata Workload Analyzer (WA)
Support Limitations
Not all of the enhancements in this release were made to all of the products in the Teradata
Tools and Utilities suite. The following major enhancements are not supported by the
Teradata Tools and Utilities suite of products listed in Table 2.
Table 2: Unsupported Teradata 13.0 Features
Unsupported Teradata Database Features
Teradata Tools and Utilities Product
Geospatial data types
Teradata JDBC Driver
PERIOD data types
•
•
•
•
•
•
•
•
•
•
•
Teradata JDBC Driver
Teradata DWM
Teradata Index Wizard
Teradata Manager
OLE DB Provider for Teradata
Teradata SQL Assistant for Microsoft Windows
Teradata SQL Assistant/Web Edition
Teradata Statistics Wizard
Teradata System Emulation Tool (SET)
Teradata Visual Explain (VE)
Teradata WA
User impersonation with query banding
•
•
•
•
•
•
•
•
•
Teradata DWM
Teradata Index Wizard
Teradata Manager
Teradata SQL Assistant for Microsoft Windows
Teradata SQL Assistant/Web Edition
Teradata Statistics Wizard
Teradata SET
Teradata VE
Teradata WA
Teradata Tools and Utilities Release Definition
13
Chapter 1: Release Information
Supported Operating Systems
Supported Operating Systems
Supported operating systems and product version numbers for all Teradata Tools and
Utilities are available in a single spreadsheet titled Teradata Tools and Utilities 13.0 Supported
Platforms and Product Versions, at www.info.teradata.com.
To view product version numbers and platform information
1
Go to http://www.info.teradata.com/.
2
Click General Search under Online Publications.
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, supported platforms, and
product version numbers.
Product Bundling
The majority of Teradata Tools and Utilities 13.00.01 programs are packaged and distributed
on CDs and/or magnetic tape cartridges. However, OLE DB Provider is available only from
the Download Center and is not available on CD or on magnetic tape cartridge.
The following products are available from the Download Center at Teradata.com. Click
Support and Downloads>Downloads.
•
.NET Data Provider for Teradata (new to the CD this release)
•
ODBC Driver for Teradata
•
OLE DB Provider for Teradata
•
Teradata Access Modules
•
Teradata CLIv2 for NAS
•
Teradata Generic Security Services (GSS) for Java
•
Teradata GSS
•
Teradata International Components for Unicode (ICU)
•
Teradata JDBC Driver
CDs and Magnetic Tape Cartridges
In the following sections, headings show the name and number of the product CD or
magnetic tape cartridge. The section lists the contents of the CD.
14
Teradata Tools and Utilities Release Definition
Chapter 1: Release Information
Product Bundling
Some CDs contain dependency products required by one or more of the primary products on
that CD. Products included as a dependency may be limited to specific operating systems on
that CD. To install A product on all supported operating systems, use the CD on which the
product is listed as a primary product.
Teradata Utility Pack—Utilities (BCD0-1190-0000)
Teradata Utility Pack tool are distributed on a three-CD set:
•
CD1 is for Microsoft® Windows® operating systems
•
CD2 is for Hewlett-Packard® HP-UX and Linux operating systems
•
CD3 is for IBM® AIX® and Sun® Solaris® operating systems
The Teradata Utility Pack—Utilities CD provides a wide base of user tools to connect
network-attached applications to Teradata Database:
•
Teradata Data Connector 13.00
•
Named Pipes Access Module 13.00
•
.NET Data Provider for Teradata 13.00
•
ODBC Driver for Teradata 13.00
•
Teradata CLIv2 13.00
•
Teradata GSS 13.00
•
Teradata ICU 13.00
•
Teradata JDBC Driver 13.00.00.27
The Teradata Utility Pack—Utilities CD also provides some database and query management
tools:
•
BTEQ 13.00
•
Teradata Administrator 13.00
•
Teradata SQL Assistant 13.00
•
Teradata SQL Assistant/Web Edition 13.00
Database Management (BCD0-1195-0000)
The Database Management CD provides database and query management tools you can use
to control access to, analyze the performance of, and improve the efficiency of the queries run
against your Teradata Database. These tools also feature online help systems.
•
Teradata DWM 13.00
•
Teradata Index Wizard 13.00
•
Teradata Manager 13.00
•
Teradata Performance Monitor 13.00
•
Teradata QS 13.00
•
Teradata Statistics Wizard 13.00
•
Teradata SET 13.00
Teradata Tools and Utilities Release Definition
15
Chapter 1: Release Information
Product Bundling
•
Teradata VE 13.00
•
Teradata WA 13.00
Dependencies:
•
BTEQ 13.00
•
Teradata Data Connector 13.00
•
ODBC Driver for Teradata 13.00
•
Teradata CLIv2 13.00
•
Teradata GSS 13.00
•
Teradata ICU 13.00
Load/Unload (BCD0-1192-0000)
Teradata load and unload utilities are distributed on a three-CD set:
•
CD1 is for Microsoft Windows operating systems
•
CD2 is for Hewlett-Packard HP-UX and Linux operating systems
•
CD3 is for IBM AIX and Sun Solaris operating systems
The Load/Unload CD provides the following Teradata products used to load and unload data
on your Teradata Database:
•
Named Pipes Access Module 13.00
•
OLE DB Access Module 13.00
•
Teradata Data Connector 13.00
•
Teradata FastExport 13.00
•
Teradata FastLoad 13.00
•
Teradata MultiLoad 13.00
•
Teradata TPump 13.00
•
Teradata WebSphere MQ Access Module 13.00
Dependencies:
•
BTEQ 13.00
•
ODBC Driver for Teradata 13.00
•
Teradata CLIv2 13.00
•
Teradata GSS 13.00
•
Teradata ICU 13.00
Note: Teradata Access Module for JMS is not included on the product installation CDs.
Teradata Access Module for JMS 13.00 will be available from the Download Center at
Teradata.com in Q4 2009.
Teradata Parallel Transporter (BCD0-1193-0000)
Teradata PT and Teradata PT API are distributed on a three-CD set:
16
Teradata Tools and Utilities Release Definition
Chapter 1: Release Information
Product Bundling
•
CD1 is for Microsoft Windows operating systems
•
CD2 is for Hewlett-Packard HP-UX and Linux operating systems
•
CD3 is for IBM AIX and Sun Solaris operating systems
The Teradata PT CD contains the entire Teradata PT suite of products used to load and
unload data on your Teradata Database in the following six packages:
•
Teradata PT API 13.00
•
Teradata PT Infrastructure 13.00
•
Teradata PT Export Operator 13.00
•
Teradata PT Load Operator 13.00
•
Teradata PT Stream Operator 13.00
•
Teradata PT Update Operator 13.00
Dependencies:
•
Named Pipes Access Module 13.00
•
Teradata WebSphere MQ Access Module 13.00
•
Teradata CLIv2 13.00
•
Teradata GSS 13.00
•
Teradata ICU 13.00
Meta Data Services (BCD0-1242-0000)
This CD contains Teradata Meta Data Services (MDS) 13.00, which provides a set of
object-oriented Application Programming Interfaces (APIs) that can be used to:
•
Create application information metamodels (AIMs) that define how metadata is stored in
an MDS repository.
•
Add, update, and delete metadata objects and collections in an MDS repository.
Teradata MDS also includes a set of utilities and GUIs that provide the infrastructure for a
metadata repository.
Preprocessors (BCD0-1191-0000)
Teradata Preprocessors are distributed on a three-CD set:
•
CD1 is for Microsoft Windows operating systems
•
CD2 is for Hewlett-Packard HP-UX and Linux operating systems
•
CD3 is for IBM AIX and Sun Solaris
The Preprocessors CD provides the Teradata tools needed for accessing your Teradata
Database with Teradata SQL statements in C or COBOL programs.
•
Teradata COBOL PP2 13.00
•
Teradata SQL C PP2 13.00
Dependencies:
Teradata Tools and Utilities Release Definition
17
Chapter 1: Release Information
Product Bundling
•
Teradata CLIv2 13.00
•
Teradata GSS 13.00
•
Teradata ICU 13.00
Query Director (BCD0-1255-0000)
This CD contains Teradata QD, a program used to route sessions for high availability
purposes.
Dependencies:
•
Teradata CLIv2 13.00
•
Teradata GSS 13.00
•
Teradata ICU 13.00
Tape Storage Management Enablers (BCD0-1194-0000)
Beginning with this release, Teradata Access Module for Tivoli® has been renamed Tivoli
Storage Manager Teradata Extension, and the product is not included on the Tape Storage
Management Enablers CD. It was released with the Teradata Tiered Archive and Restore
Architecture (TARA) 13.00.
This CD contains Teradata ARC 13.00, which provides Teradata backup and restore
functions.
Dependencies:
•
Teradata Data Connector 13.00
•
ODBC Driver for Teradata 13.00
•
Teradata SQL C PP2 13.00
•
Teradata CLIv2 13.00
•
Teradata GSS 13.00
•
Teradata ICU 13.00
Magnetic Tape Cartridges
Magnetic tape cartridges are released in two formats with different BCD numbers:
IBM z/OS® and z/VM®.
Teradata Tools and Utilities 13.0 for IBM z/OS (MVS)
•
3480 format: BCD0-1070-0000
•
3590 format: BCD0-1071-0000
•
9840 format: BCD0-1072-0000
Teradata Tools and Utilities 13.0 for IBM z/VM
18
•
3480 format: BCD0-1068-0000
•
3590 format: BCD0-1069-0000
Teradata Tools and Utilities Release Definition
Chapter 1: Release Information
Product Installation
Product Installation
This section provides installation notes for Teradata Tools and Utilities products. All Teradata
Tools and Utilities installation packages were updated to support the current release.
E-Fix Updates
To ensure the highest quality and best performance of Teradata Tools and Utilities products,
the most recent, critical, post-production updates can be downloaded from the Teradata
Software Server at: http://tssprod.teradata.com:8080/TSFS/home.do.
Release Notes
Documentation Updates
Last-minute changes were added to Teradata Tools and Utilities Installation Guide for UNIX
and Linux. An updated version is available at http://www.info.teradata.com/.
SCEERUN Library on IBM z/OS
Teradata Tools and Utilities applications running on IBM z/OS require the IBM Language
Environment SCEERUN library. If that library is not available in the MVS linklist, it must be
included in the JOBLIB concatenation for any job or in the STEPLIB concatenation for any
job step running a Teradata Tools and Utilities application.
Manual Install for Teradata WebSphere MQ Access Module
On Hewlett-Packard HP-UX 11i v2 (11.23) and 11i v3 (11.31) with Intel® Itanium®, Teradata
WebSphere MQ Access Module cannot be automatically installed using the Load/Unload
installation CD. Several libraries must be manually copied to your PC from the /HP-UX/
mqaxsmod/ia64 directory on the Load/Unload installation CD.
Before copying the libraries, ensure the following Teradata WebSphere MQ Access Module
product dependencies have been installed in the correct order.
•
Teradata Data Connector 13.00
•
IBM WebSphere® MQ 5.2 (HP-UX)
Table 3 lists the libraries and the corresponding directories where the library must be copied.
An asterisk (*) after a file name indicates a “softlink” for files located in this directory:
/opt/teradata/client/<version>/hpux64.
Table 3: Teradata WebSphere MQ Access Module Libraries
Copy this library...
To this directory...
libmqs.so*
/usr/lib/hpux64
libmqsc.so*
/usr/lib/hpux64
libmqs.so
/opt/teradata/client/<version>/hpux64
Teradata Tools and Utilities Release Definition
19
Chapter 1: Release Information
Product Installation
Table 3: Teradata WebSphere MQ Access Module Libraries (continued)
Copy this library...
To this directory...
libmqsc.so
/opt/teradata/client/<version>/hpux64
Teradata CLIv2 for NAS Sun Solaris Makefiles
When Teradata CLIv2 for NAS is installed on Sun Solaris with AMD® Opteron™, Solaris
SPARC makefiles are incorrectly copied to the /opt/teradata/client/13.0/sample directory. They
must be replaced with the Solaris Opteron makefiles listed in Table 4.
Table 4: Teradata CLIv2 for NAS Sun Solaris Makefiles
Replace this Solaris SPARC makefile...
With this Solaris Opteron makefile...
makesamp.sols
makesamp.soli386
makesamp.sols64
makesamp.solx8664
maketdusr.sols
maketdusr.soli386
maketdusr.sols64
maketdusr.solx8664
Note: The Solaris Opteron e-fixes can be downloaded from the Teradata Software Server at:
http://tssprod.teradata.com:8080/TSFS/home.do.
General Enhancements
•
Teradata Tools and Utilities are now installed in the following new default directories:
•
On UNIX operating systems:
/opt/teradata/client/<version>
•
On Windows operating systems:
C:\ProgramFiles\Teradata\Client\<version>
This new tree structure brings all Teradata Tools and Utilities for 13.00.01 under a single
sub-directory.
•
In path and file locations, references to “NCR” were changed to “Teradata.”
•
Teradata PT installation packages were reduced to six to streamline installation.
Enhancements for UNIX Operating Systems
20
•
Except for Teradata ARC, Teradata DUL, and Teradata DUL/T, Teradata Tools and
Utilities installation package names now include the version number; for example,
bteq130, cliv2130, and piom130.
•
To avoid a name conflict on Novell® SUSE® Linux Enterprise 9, the Teradata ARC install
package was renamed teradata_arc.
•
Except on systems where the microprocessor is different (Hewlett-Packard PA-RISC
compared to Intel Itanium), both 32-bit and 64-bit versions of Teradata Tools and
Utilities are included in a single installation package.
Teradata Tools and Utilities Release Definition
Chapter 1: Release Information
Product Installation
Note: 32-bit and 64-bit versions of Teradata GSS are still deployed in separate installation
packages. Both versions must be installed before installing a Teradata Tools and Utilities
application.
Enhancements for Microsoft Windows Operating Systems
•
Earlier versions of Teradata Tools and Utilities are now automatically removed before a
new version is installed.
•
ODBC Driver for Teradata, Teradata CLIv2, and shared Teradata ICU libraries are now
basic Microsoft Installer (.msi) installation packages.
•
32-bit and 64-bit Teradata Tools and Utilities applications can coexist on systems with
Intel EM64T.
•
When the silent install process is used on systems with Intel EM64T, both the 32-bit and
the 64-bit versions of a Teradata Tools and Utilities application are installed. When the
interactive install process is used, only the 64-bit version of a Teradata Tools and Utilities
application is installed.
Tar Teradata Client Packages
System administrators can now create a single tar file that can transfer UNIX Teradata Client
packages and dependencies from a Teradata Client Utilities UNIX media disk mounted on
Windows or UNIX across the network. For full detail and script samples, see Teradata Tools
and Utilities Installation Guide for UNIX and Linux, B035-2459-088A.
Silent Installation and Upgrades of ODBC Driver for Teradata
On Windows, the standard way to do silent installation of ODBC Driver for Teradata (and
other basic Microsoft Installer packages, such as Teradata Call-Level Interface v2 and Teradata
ICU) is:
Setup /S /v"/qn"
However, some environments restrict the execution of standard setup.exe files. Such a
scenario requires alternate installation methods. Therefore, if you cannot run the standard
setup.exe to install or upgrade ODBC Driver for Teradata, do the following:
•
New installation - For a new silent installation, use the following command:
Msiexec /I "ODBC Driver for Teradata.msi" /qn
•
Upgrade - To do a silent install that upgrades ODBC Driver for Teradata 13.00.01 from a
previous version, use the following command:
Msiexec /I "ODBC Driver for Teradata.msi" /qn REINSTALL=ALL
REINSTALLMODE=voums
Windows Interactive and Silent Installs
The following TTU packages on the TTU 13.00.01 Windows media have been converted from
Installscript to basic MSI packages. This provides consistency across TTU packages and easy
deployment through system management software.
•
TeraGSS
•
TDICU
Teradata Tools and Utilities Release Definition
21
Chapter 1: Release Information
Product Installation
•
TDODBC
•
CLIv2
•
PIOM
•
FASTLD
•
FASTEXP
•
MLOAD
•
TPUMP
•
NPAM
•
MQAM
•
OLEDBAM
•
SQLPP
•
TDOLEDB
•
SQLA
•
VECOMP
•
TSET
•
TIWIZ
•
TSWIZ
•
TQSClient
•
TQSServer
•
TQSAdmin
•
TWA
•
TDADMIN
•
PMON
•
TMGR
•
TDWM
•
TSAW
Use the following procedures to deploy the TTU Basic MSI packages through SMS or to
install the TTU packages individually.
•
To install the packages interactively, use the following command:
setup
•
To install the packages silently, use the following command:
setup /s /v"/qn"
•
To silently install the package to a user specified location, use the following command:
setup /s /v"/qn INSTALLDIR=<user_specified_folder>"
Documentation
Teradata Tools and Utilities Installation Guide for IBM z/OS,
B035-2458-088A
22
Teradata Tools and Utilities Release Definition
Chapter 1: Release Information
Product Installation
Teradata Tools and Utilities Installation Guide for IBM z/VM,
B035-2422-088A
Teradata Tools and Utilities Installation Guide for Microsoft Windows,
B035-2407-088A
Teradata Tools and Utilities Installation Guide for UNIX and Linux,
B035-2459-088A
Requests for Change
Requests for Change (RFCs) introduce new features and track changes that enhance the
operation of Teradata Tools and Utilities software. Product installation changes and RFCs
indicating support for new operating systems are listed in the individual product sections in
Chapter 2: “Product Information.”
Table 5: Installation RFCs
RFC
Description
103564
Network Install now extracts both 32 bit and 64 bit packages on a 32 bit
system.
138516
Windows Main Install now versioned in rd.txt file.
144065
Windows Main Install now automatically uninstalls pre-13.0 versions of DBM
products.
100701
The 32-bit version and the 64-bit version of ODBC Driver for Teradata can be installed
and used on the same system.
115012
Documentation Only
Improved instructions for silent installation were added to Teradata Tools and Utilities
Installation Guide for Microsoft Windows.
117885
117886
118876
On Microsoft Windows and UNIX operating systems, separate Teradata PT versions of
the Teradata WebSphere MQ Access Module and the Named Pipes Access Module are
no longer installed or required.
Documentation Only
The sequence for removing Teradata Tools and Utilities packages was added to
Teradata Tools and Utilities Installation Guide for UNIX and Linux.
119854
As of this release, Teradata ARC is installed in a new directory:
• On Windows: C:\ProgramFiles\Teradata\Client\<version>\bin
• On UNIX operating systems: /opt/teradata/client/<version>/bin
121109
UNIX packages can now be easily transferred from Teradata Client Media to a specific
UNIX platform by invoking a script to create a single tar file that includes all of the
dependent packages and installation files that are necessary.
For full detail and script samples, see Teradata Tools and Utilities Installation Guide for
UNIX and Linux, B035-2459-088A.
Teradata Tools and Utilities Release Definition
23
Chapter 1: Release Information
Product Installation
Table 5: Installation RFCs (continued)
RFC
Description
122435
Documentation Only
Information about using the SCEERUN library was added to Teradata Tools and
Utilities Installation Guide for IBM z/OS.
129225
.NET Data Provider for Teradata support was added to the Teradata Tools and
Utilities 13.00.01 Windows main install
Discrepancy Reports
Discrepancy Reports (DRs) track corrections and updates to Teradata Tools and Utilities
software and to documentation affected by the updates.
Table 6: Installation DRs
DR
Description
113827
Documentation Only
Installing Teradata Tools and Utilities applications can cause the Microsoft Windows
path to overrun if the system PATH environment variable exceeds 1024 characters. A
hotfix is available from Microsoft; see Tech Alert 1455 for details.
115305
Documentation Only
TeraGSS was changed to teragss in directory paths for commands in Teradata Tools and
Utilities Installation Guide for UNIX and Linux.
115983
32-bit and 64-bit ODBC Driver for Teradata can now be silently installed on IBM AIX.
117853
Documentation Only
Teradata Tools and Utilities Installation Guide for UNIX and Linux incorrectly stated
that the swap space needed to be equal to the memory size plus 2 G on Linux operating
systems.
Teradata Tools and Utilities Installation Guide for UNIX and Linux was corrected to
indicate that the swap space needs to be equal to only the memory size on Linux
operating systems.
117962
Documentation Only
A typographical error in a command to TRDTMTDP was corrected in Teradata Tools
and Utilities Installation Guide for IBM z/OS.
118343
Documentation Only
The LANG and LC__FASTMSG environment variables are now documented in
Teradata Tools and Utilities Installation Guide for UNIX and Linux.
118793
Documentation Only
To match standard IBM nomenclature, applicable references to MVS were changed to
z/OS and references to VM to were changed z/VM in Teradata Tools and Utilities
Installation Guide for IBM z/OS.
24
Teradata Tools and Utilities Release Definition
Chapter 1: Release Information
Product Installation
Table 6: Installation DRs (continued)
DR
Description
118926
Documentation Only
Use of the NOSWAP and NOPREF parameters was clarified in Teradata Tools and
Utilities Installation Guide for IBM z/OS.
122111
Documentation Only
Instructions for installing the Teradata Manager Server and Teradata Manager Client
components were updated in Teradata Manager Installation Guide.
122470
Windows Server 2003 operating systems must be shut down and restarted to apply
Teradata Tools and Utilities 13.00.01 upgrades.
126152
Teradata FastLoad was not using the main install directory path when it was installed
from the Teradata for Windows Load and Unload CD. This error no longer occurs.
126914
Teradata Tools and Utilities setup scripts for Linux were failing with a “unable to
execute./.setup.sh: No such file or directory” error message. This error no longer occurs.
128225
An InstallShield bug caused entries in the silent response file to be ignored, resulting in
the selection of all defined features, which caused .NET Data Provider for Teradata to
try to run utilities that might not be present.
The silent install process now works as expected.
128351
A subdirectory for Teradata Named Pipes Access Module is now correctly added to the
SOFTWARE\Teradata\Certlist directory at installation.
128388
A subdirectory for Teradata FastExport is now added to the
SOFTWARE\Teradata\Certlist directory at installation.
128389
A subdirectory for Teradata FastLoad is now added to the
SOFTWARE\Teradata\Certlist directory at installation.
128350
A subdirectory for Teradata Websphere MQ Access Module is now correctly added to
the SOFTWARE\Teradata\Certlist directory at installation.
128860
The installation of Teradata PT does not add curly braces around the PATH,
NLSPATH, or library path environment variables in the system login files, which broke
the shell on the AIX operating system. The installation process now adds curly braces, as
needed.
130398
During installation, the list of dependent applications was incomplete. The list is now
complete.
130470
BTEQ was unnecessarily removing the entire CertList key in the Registry during an
upgrade or uninstall. The error no longer occurs.
130492
A subdirectory for Teradata OLE DB Access Module is now added to the
SOFTWARE\Teradata\Certlist directory at installation.
130558
Teradata DataConnector was unnecessarily removing the entire CertList key in the
Registry during an upgrade or uninstall. The error no longer occurs.
130647
A subdirectory for Teradata MultiLoad is now correctly added to the
SOFTWARE\Teradata\Certlist directory at installation.
Teradata Tools and Utilities Release Definition
25
Chapter 1: Release Information
Product Installation
Table 6: Installation DRs (continued)
DR
Description
130802
A subdirectory for Teradata MultiLoad is now correctly added to the
SOFTWARE\Teradata\Certlist directory at installation.
132103
The installation of Teradata TPump removed registry entries under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninst
all key, which prevented the ability to uninstall packages after installing TPump. The
problem no longer occurs.
131753
26
Teradata TPump sometimes mishandled VARGRAPHIC FIELDs in unformatted files,
which caused the application to terminate. The problem no longer occurs.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Product Discontinuances
CHAPTER 2
Product Information
This chapter provides the following information about each of the products, database tools,
and utilities included in Teradata Tools and Utilities Release 13.00.01:
•
Product versions certified with this release
•
Supported versions of Teradata Database
•
Documentation associated with the product
•
Miscellaneous release notes
•
Requests for change (RFCs) and discrepancy reports (DRs) associated with each product
for this release
To ensure the highest quality and best performance of Teradata Tools and Utilities products,
the most recent, critical post-production updates can be downloaded from the Teradata
Software Server at: http://tssprod.teradata.com:8080/TSFS/home.do
Product Discontinuances
As of this release, Teradata Tools and Utilities are no longer supported on NCR® MP-RAS.
Support for Teradata Dump Load/Unload (DUL) on IBM z/OS (MVS) and z/VM operating
systems is being discontinued effective with this release.
Teradata MultiTool is being discontinued effective with this release.
Product Versions
Product version numbers for Teradata Tools and Utilities were changed to 13.00.01, except
for the following:
•
Basic Teradata Query Utility (BTEQ)
•
Host Utility Consoles (HUTCNS)
•
Interactive Teradata Query (ITEQ)
•
Symantec™ Netbackup™ Extension for Teradata
Teradata Tools and Utilities Release Definition
27
Chapter 2: Product Information
Basic Teradata Query Utility
Product Compatibility
You cannot mix multiple releases of any Teradata Tools and Utilities applications on the same
client PC. For example, you cannot run OLE DB Provider 13.00 with Teradata CLIv2 12.0 on
the same client PC.
All Teradata Tools and Utilities products invoked on a system must be from the same base
release. For example, if you upgrade to Teradata MultiLoad 13.00, you must also upgrade the
product dependencies (such as Teradata CLIv2, Teradata GSS, and Teradata ICU) to the
Teradata Tools and Utilities 13.00.01 version.
See Teradata Tools and Utilities 13.00.01 Supported Platforms and Product Versions to identify
compatible products.
Basic Teradata Query Utility
BTEQ utility is a general-purpose, command-based program that allows workstation users to
communicate with one or more Teradata Database systems and format reports for print and
monitor output.
Product Version Number
BTEQ 13.00.00.10
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Basic Teradata Query Reference,
B035-2414-088A
Release Notes
ActivityCount Variable and Notify Exit Routines
The data type for the ActivityCount returned by BTEQ was changed from Int32 (signed 32-bit
integer) to UInt32 (unsigned 32-bit integer). If you are using the ActivityCount variable in a
notify exit routine, you must change the print specifier for the ActivityCount variable to %u,
and then recompile the routine.
28
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Basic Teradata Query Utility
Unicode Support Limitations
Expression substitutions (&n) within a HEADING, FOOTING, or RTITLE command are
restricted to LATIN1 characters when using UTF8 and UTF16 session character sets with
BTEQ on IBM z/OS.
Note: UTF8 and UTF16 session character sets are not supported with BTEQ on IBM z/VM.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 7: BTEQ RFCs
RFC
Description
58020
Documentation Only
The examples for using the LOGON command in interactive mode were expanded to
improve usability. See Examples 1 and 2 in the “Using the Optional acctid Identifier”
section under the LOGON command in Basic Teradata Query Reference.
69180
Documentation Only
Obsolete information and AXSMOD examples for the Tape Access Module were
removed from Basic Teradata Query Reference.
87376
Documentation Only
Basic Teradata Query Reference was updated to more accurately describe initial and
assumed defaults in BTEQ commands.
93225
Documentation Only
Basic Teradata Query Reference incorrectly stated that the ERRORLEVEL is reset to zero
after a successful request. The information on ERRORLEVEL handling was corrected in
Basic Teradata Query Reference.
90037
See “ActivityCount Variable and Notify Exit Routines” on page 28.
98374
UTF16 scripts without a Byte Order Mark (BOM) can be used for workstation BTEQ
input. BTEQ checks the input file for a UTF16 or UTF8 BOM and automatically
changes the session character set to the appropriate Unicode encoding.
102430
Previously, when the BOM and NOBOM options were used with a MESSAGEOUT
command from BTEQ running on a mainframe operating system, a syntax error was
generated. Now, BTEQ prints a warning message indicating that the BOM/NOBOM
options are not supported for MESSAGEOUT on mainframe operating systems.
Note: The BOM and NOBOM options are valid for UNICODE character sets only.
Because EBCDIC is the default character set for mainframe operating systems, the BOM
and NOBOM options are invalid.
See Basic Teradata Query Reference for details.
102433
Previously on IBM z/OS, a BOM was not inserted at the beginning of a REPORT export
file. Now, a BOM is inserted at the beginning of REPORT and DIF export files
produced from UTF8 and UTF16 sessions. For more information, see Basic Teradata
Query Reference.
Teradata Tools and Utilities Release Definition
29
Chapter 2: Product Information
Basic Teradata Query Utility
Table 7: BTEQ RFCs (continued)
RFC
Description
102473
Previously, BTEQ did not display SHOW and COMMENT results correctly for UTF8
and UTF16 session character sets. BTEQ was modified and now correctly displays
SHOW and COMMENT results for UTF8 and UTF16 session character sets.
102477
On IBM z/OS, BTEQ supports using DIF (Data Interchange Format) with the EXPORT
command and UTF16 session character sets.
102478
See “Unicode Support Limitations” on page 29.
102484
On IBM z/OS, BTEQ supports creating stored procedures using the COMPILE
command with UTF8 and UTF16 session character sets.
104659
The formatting of field mode reports is no longer based on bytes for UTF8 sessions. A
new REPORTALIGN command is used to control UTF8 alignment. For example,
spacing between columns and WIDTH truncation may not be the same as past releases.
See Basic Teradata Query Reference for more information.
109593
Documentation Only
Usage Note were added to the RETRY command regarding the Error 2631 failure code.
For details, see Basic Teradata Query Reference.
111025
BTEQ running on mainframe operating systems does not support carriage control
characters in Unicode REPORT and DIF export files. BTEQ was modified so that an
EXPORT command fails when parsed instead of causing an Open failed on
file error when a subsequent SELECT command is executed. For more information,
see the EXPORT command in Basic Teradata Query Reference.
111088
BTEQ does not support embedded control characters within quoted strings for SQL
requests. Examples of unsupported control characters include a null, carriage return, or
line feed character. See Basic Teradata Query Reference for details.
114222
The SHOW VERSIONS command was updated to exclude output for the revision
levels for BTEQ/CAP source files (.C and .H) and CLI/PIOM source files (.C). For more
information, see Basic Teradata Query Reference.
114483
Documentation Only
Instructions for using the REPEAT command to establish the same query band for
multiple sessions were added to Basic Teradata Query Reference.
30
114709
The Teradata Database table header size was expanded to 1 MB. The BTEQ RETLIMIT
command was enhanced to allow more than 2048 columns to be selected. See Basic
Teradata Query Reference for details.
114700
When a Large Object (LOB) column is associated with an AS DEFERRED BY NAME
qualifier in the USING clause of an IMPORT command, Teradata Database solicits the
value using ElicitDataByName protocol. In deferred-mode, BTEQ supports loading of
LOB values using the ElicitDataByName Protocol.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Basic Teradata Query Utility
Table 7: BTEQ RFCs (continued)
RFC
Description
114986
BTEQ supports the Teradata Database replication group rule set feature. BTEQ
recognizes SQL activities associated with the use of DDL for this feature. BTEQ displays
a meaningful result message when users have successfully created, replaced, or dropped
replication rule sets.
DDL replication allows utility type names and escape sequences to be expanded in SQL
statements containing the AS USER prefix.
115382
LOBCOLS and TOTCOLS options were added to the IMPORT command to support
loading of LOB values using the ElicitData protocol on non-Unicode sessions.
In deferred-mode, BTEQ does not support LOB loading using Unicode session
character sets on mainframe operating systems.
See Basic Teradata Query Reference for details.
119025
BTEQWIN now uses HTML Compile help rather than WinHelp for online
documentation.
119494
BTEQ now displays a confirmation or failure message in response to Java XSP
statements related to class dependencies on other jar classes.
119535
Documentation Only
Users are responsible for correctly describing the input data in a USING modifier in an
IMPORT command. This warning is now documented in Basic Teradata Query
Reference.
120621
Documentation Only
VARTEXT import rules for workstation operating systems were added to Basic
Teradata Query Reference.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 8: BTEQ DRs
DR
Description
47626
The TDP command does not accept hyphen or dash characters. Support for and
restrictions applying to TDP values in both non-quoted form and quoted forms are
now documented under the TDP command in Basic Teradata Query Reference.
59698
Documentation Only
In Basic Teradata Query Reference, a leading period incorrectly placed before an ECHO
statement was removed.
100721
Batch mode Workstation BTEQ UTF16 sessions now honor = command.
113481
On IBM z/OS, BTEQ incorrectly decreased stdout WIDTH for UTF16 session character
sets. BTEQ was modified and this behavior no longer occurs. See the EXPORT
command in Basic Teradata Query Reference for details.
Teradata Tools and Utilities Release Definition
31
Chapter 2: Product Information
IBM CICS Interface for Teradata
Table 8: BTEQ DRs (continued)
DR
Description
117411
Empty RUN files encountered while using the RUN command were incorrectly
handled. A run-terminating error should result if an empty RUN file is encountered.
BTEQ was modified and this error no longer occurs.
118237
Null characters are now correctly handled in VARTEXT files for UTF8 sessions.
120541
Using 3-BREAK exit no longer leaves echoing off when terminating during the
protected data-entry mode.
125943
For UTF8 workstation sessions, date and time fields were not properly padded when
multi-byte characters appeared in the output for different REPORTALIGN settings.
This problem no longer occurs.
126117
BTEQ was not using the main install directory path when being installed from the
Teradata for Windows Load and Unload CD. This error no longer occurs
127873
BTEQ incorrectly reported an error when displaying non-Unicode multi-byte column
titles greater than 60 bytes. The limit for non-Unicode column titles is now 60 bytes.
134506
The PUT upgrade no longer removes the usr/bin/bteq softlink.
135623
Mainframe BTEQ no longer erroneously omits a result line comprised of all blanks for
the first data-returning statement.
137927
Mainframe BTEQ no longer generates an LSCX373 warning for an IMPORT that
follows a VARTEXT IMPORT.
139907
Interactive use of BREAK followed by ABORT again enables resetting of the input
buffer to be able to re-enter SQL.
141252
Based on reported installation problems, the BTEQ installation package has been
converted to the Basic MSI installation package.
144533
Mainframe BTEQ no longer abends when submitting a wide DDL request read from a
RUN file that was created by an EXPORT with WIDTH set to greater than 258.
IBM CICS Interface for Teradata
The IBM Customer Information Control System (CICS) Interface for Teradata allows CICS
macro (1.7 and 2.1 only) or command level (1.7 and later) application programs to access
Teradata Database resources.
Product Version Number
CICS Interface for Teradata 13.00
Supported Versions of Teradata Database
32
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
IBM IMS Interface for Teradata
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
IBM CICS Interface for Teradata Reference,
B035-2448-088A
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software. There are no RFCs for this product for this release.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates. There are no DRs for this product for this release.
IBM IMS Interface for Teradata
The IBM Information Management System (IMS) Interface for Teradata allows IMS
programs executing in an IMS BATCH, BMP (Batch Message Program), or MPP (Message
Processing Program) region to access data from Teradata Database.
Product Version Number
IMS Interface for Teradata 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
IBM IMS/DC Interface for Teradata Reference,
B035-2447-088A
Release Notes
None.
Teradata Tools and Utilities Release Definition
33
Chapter 2: Product Information
Interactive Teradata Query Utility
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software. There are no RFCs for this product for this release.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates. There are no DRs for this product for this release.
Interactive Teradata Query Utility
Interactive Teradata Query (ITEQ) includes extensions to Teradata SQL that process Teradata
SQL statements interactively without having to develop application software. A user at a
terminal attached to a client computer can use the ITEQ interface to interact directly with
Teradata Database.
Product Version Number
ITEQ 06.00.02
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Interactive Teradata Query Reference,
B035-2451-088A
Interactive Teradata Query User Guide,
B035-2452-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software. There are no RFCs for this product for this release.
34
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
.NET Data Provider for Teradata
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates. There are no DRs for this product for this release.
.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).
Product Version Number
.NET Data Provider for Teradata 13.00.00
Supported Versions of Teradata Database
.NET Data Provider for Teradata is supported by the following versions of Teradata Database:
•
Teradata Database 13.00
•
Teradata Database 12.0
•
Teradata Database V2R6.2
•
Teradata Database V2R6.1
•
Teradata Database V2R6.0
Note: .NET Data Provider for Teradata does not connect to Teradata Database V2R5.1 or
earlier.
Documentation
.NET Data Provider for Teradata Release Definition,
B035-2032-128C
The .NET Data Provider for Teradata Developer’s Guide and the .NET Data Provider for
Teradata Developer’s Reference are included with the product as a single stand-alone help file.
The help file is also integrated into Visual Studio 2005 and Visual Studio 2008.
To access this online help file, select .NET Data Provider for Teradata 13.00.01.00 under Start >
All Programs.
Release Notes
None.
Requests for Change (RFCs)
Requests for Change (RFCs) introduce new features and track changes that enhance the
operation of .NET Data Provider for Teradata software. The following RFCs have been
incorporated in this release.
Teradata Tools and Utilities Release Definition
35
Chapter 2: Product Information
.NET Data Provider for Teradata
Table 9: .NET Data Provider for Teradata RFCs
RFC
Feature or Enhancement
97972
13.00.01 now supports the StatementInfo parcel when receiving data from Teradata.
This enables the provider to make available additional metadata about SQL
statements sent to Teradata.
A new connection string attribute, UseEnhancedSchemaTable, has been added to
prevent compatibility problems with existing applications that are caused by the
additional metadata. The default setting for this attribute is “true” which indicates
that the additional metadata will be available to an application.
115300
New types have been added to the 13.00.01 that support the Period Data Types.
• TdPeriodDate
Database equivalent: PERIOD(DATE)
• TdPeriodTime
Database equivalent: PERIOD(TIME(scale))
• TdPeriodTimeWithTimeZone
Database equivalent: PERIOD(TIME(scale) WITH TIME ZONE)
• TdPeriodTimestamp
Database equivalent: PERIOD(TIMESTAMP(scale))
• TdPeriodTimestampWithTimeZone
Database equivalent: PERIOD(TIMESTAMP(scale) WITH TIME ZONE)
121823
ToTimeZone method has been added to TdTimeWithTimeZone and
TdTimestampWithTimeZone. This method allows the time zone to be changed.
127554
Removed duplicate XML fragments from Visual Studio Data View Support.
127669
The Table Schema Collection returns information about tables that have No Primary
Index.
Discrepancy Reports (DRs)
Discrepancy Reports (DRs) track known issues and problems fixed in the .NET Data Provider
for Teradata software in this release.
Table 10: .NET Data Provider for Teradata DRs
36
DR
Description
121825
Exceptions that are thrown from the Date And Time methods are now documented.
122987
TdException is thrown to indicate that an instance is the null value when the
properties of a Null Date And Time value is accessed.
123430
The DataSet Designer now orders columns of tables in the order that they were
defined in the data definition.
123437
An ArgumentNullException is thrown when a null or String.Empty is passed as the
value parameter to the Parse method of all Date And Time Provider Specific Types.
123610
An ArgumentOutOfRangeException will now be thrown when the property
TdDataAdapter.UpdateBatchSize is set to a negative value.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
.NET Data Provider for Teradata
Table 10: .NET Data Provider for Teradata DRs (continued)
DR
Description
124079
There were many problems with the documentation related to the Provider Specific
Date And Time Types. Some of the exceptions thrown by properties and methods
were not documented, and documentation needed to be clarified for the Parse and
ToString methods.
124081
The TdTimestampWithTimeZone.GetHashCode threw an exception when this
method is called from a Null value. This has been fixed so that when GetHashCode is
called from a Null value, a 0 is returned.
124265
Documentation for the method ToString(IFormatProvider) of all Date And Time
Provider Specific Types has been updated to indicate that the cultural settings
specified in the DateTimeFormatInfo object is ignored.
124448
When parsing a string representation of a TdTime, TdTimeWithTimeZone,
TdTimestamp or TdTimestampWithTimeZone that has a scale which is greater than
6, a FormatException is thrown.
124670
A “Null” string is now parsed by the following types:
• TdDecimal
• TdDate
• TdTime
• TdTimeWithTimeZone
• TdTimestamp
• TdTimestampWithTimeZone
The return value is the type's Null value.
124723
When an application uses the TdDataAdapter, customizes the commands, and defines
parameters the Teradata Database may throw an error if the provider uses Iterated
Requests. A workaround for this problem is described in the page .NET Data Provider
for Teradata Developer’s Guide -- Working With Provider Features -TdCommandBuilder and TdDataAdapter -- Specifying INSERT, UPDATE, DELETE
command.
The .NET Data Provider for Teradata Developer’s Guide and the .NET Data Provider
for Teradata Developer’s Reference are included with the product as a single standalone help file. The help file is also integrated into Visual Studio 2005 and Visual
Studio 2008.
To access this online help file, select .NET Data Provider for Teradata 13.00.01.00 under
Start > All Programs.
124922
The LdapServicePassword is no longer stored in plain text.
126310
Documentation has been added providing a guideline when inserting data of type
decimal into a column defined as a DECIMAL and "GENERATED ALWAYS AS
IDENTITY".
126436
The Teradata Provider now correctly handles the situation when an instance of a
TdCommandBuilder is set to another instance of a TdDataAdapter using the
TdCommandBuilder.DataAdapter property. When
TdCommandBuilder.DataAdapter is used to change the associated TdDataAdapter,
the provider unregisters with the existing one then registers with the new data
adapter.
Teradata Tools and Utilities Release Definition
37
Chapter 2: Product Information
.NET Data Provider for Teradata
Table 10: .NET Data Provider for Teradata DRs (continued)
38
DR
Description
127698
An ArgumentOutOfRangeException is no longer thrown when
TdCommand.UpdateRowSource is set to UpdateRowSource.OutputParameters.
128027
The Teradata Provider will not set the PRIMARY_KEY column of the Indexes Schema
Collection to true for all columns contained in a composite unique primary index. All
the columns in the index must also be defined as NOT NULL.
128080
The provider threw an InvalidCastException when an application attempted to
convert character data to a DateTime when the session character set was UTF8. The
Teradata Database padded the character data with spaces which caused the overall
length to be greater than 10 characters (YYYY-MM-DD). This exception got thrown
when the length was greater than 10.
128112
When the total size of the parameters of a command is greater than what is allowed by
the Teradata Database, the provider threw an InvalidOperationException that
contained an unhelpful error message. This has changed so that a more informative
exception is thrown. A TdException will now get thrown that also contains a more
informative error message.
128146
Problem occurs when the provider is connected to a Teradata Database version 6.2 or
earlier. The TdParameter.ProviderSpecificValue property returned a Provider Specific
Date And Time Type (for example: TdDate, TdTimestamp...) when the
EnableTdDateTime Connection String Attribute was set to false. This has been fixed
so that this property now returns the corresponding .NET Framework type.
128171
TdTransaction.Commit threw an exception in ANSI session mode when the
Connection Isolation level (TdConnection.IsolationLevel) did not match what was
specified at the Transaction level.
128208
The provider supports Batch Update using Multi-Statement and/or Iterated Requests.
When the provider used Iterated Request there was a problem when the session mode
had been set to ANSI. The provider appended a “COMMIT WORK” to the SQL
statement. The Teradata Database returned an error indicating that it expected a
single request.
128225
Silent install is now correctly working. Visual Studio 2005 and 2008 options are no
longer ignored during silent installation.
128235
This problem is related to the Parse method of TdTime/TdTimeWithTimeZone and
TdTimestamp/TdTimestampWithTimeZone. In the string representation of these
types, the sub-seconds did not get correctly parsed when a IFormatProvider of a
culture different from “invariant” was specified.
128274
The provider did not automatically grow an internal buffer when a “CREATE
STORED PROCEDURE” statement was executed and returned a large result set. In
this situation, an application received a Teradata Database error 3115 which indicates
that the internal buffer is to small to hold one record. This has been modified so that
the 3115 error is handled internally and the size of the buffer is automatically adjusted
by the provider.
129130
When the TdParameter.IsNullable property is set to false, the provider checks the
TdParameter.Value property for a DbNull or Null value and throws an exception,
instead of sending the invalid property to Teradata.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
ODBC Driver for Teradata
Table 10: .NET Data Provider for Teradata DRs (continued)
DR
Description
129224
Documentation has been added providing a guideline when data is being inserted into
a database table that contains a column that is defined as NOT NULL with a
DEFAULT.
128313
Visual Studio Change Password feature now correctly works when the Session Mode
is set to ANSI.
129318
The ToString method of the Date and Time types now generates the correct Teradata
literal string representation.
129320
The IConvertible.ToType implementation of the Period types have been fixed. When
this method was invoked, it was possible that the Teradata Provider could go into an
infinite loop.
129794
The LDAP and SPNEGO mechanisms now work when using Query Directory.
ODBC Driver for Teradata
The Open Database Connectivity (ODBC) Driver for Teradata enables Microsoft Windows
and UNIX operating systems to communicate with the Teradata Database across local area
networks (LANs) using the open standard ODBC interface.
Product Version Number
ODBC Driver for Teradata 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
ODBC Driver for Teradata User Guide,
B035-2509-088A
Release Notes
Unicode on UNIX and Linux
The Unicode encoding can be changed from the default of UTF-8 to UTF-16 by doing the
following:
Teradata Tools and Utilities Release Definition
39
Chapter 2: Product Information
ODBC Driver for Teradata
1
Define SQLSHORT:
#define SQLWCHARSHORT
2
Set the SQL_ATTR_APP_UNICODE_TYPE environment attribute to
SQL_DD_CP_UTF16:
// Specify the unicode encoding for the application. SQL calls and
// data are both affected. No other environment variables or
// connection options (includeing DSN options) are needed.
rc = SQLSetEnvAttr(m_henv, SQL_ATTR_APP_UNICODE_TYPE,
(void *) SQL_DD_CP_UTF16, SQL_IS_INTEGER);
Note: If possible, use the SQLWCHAR ODBC type for Unicode strings instead of wchar_t
because SQLWCHAR and wchar_t are not always the same type on all operating systems.
Exception to Length Arguments for Unicode ODBC Functions
The ODBC Driver for Teradata User Guide, B035-2509, currently states the following:
“When a length (transfer size of the data) could refer to string or non-string data, the
length is described in octet lengths...This means that if the argument in question
describes the length of another argument that is always a string (typically represented as
a SQLCHAR), then the length reflects the number of characters in the string.”
The exception to the above rule is for UNIX applications that use UTF-8 encoding. For these
applications, all lengths are in bytes.
For more information about length arguments, go to http://support.microsoft.com/kb/
294169/en-us.
LIBPATH Environment Variable
On AIX platforms, ODBC Driver for Teradata has minimized the value path that needs to be
set in the LIBPATH environment variable for the runtime environment. The LIBPATH values
for the 32-bit and 64-bit ODBC Drivers are:
•
32-bit export LIBPATH: /opt/teradata/client/ODBC_32/lib
•
64-bit export LIBPATH: /opt/teradata/client/ODBC_64/lib
Directory Migration
Teradata Tools and Utilities 13.00.01 introduces a new directory structure. In response,
ODBC Driver for Teradata 13.00 provides scripts that allow previous versions to operate
without impact.
If previous releases of ODBC Driver for Teradata were installed in the default directory, no
migration is required. However, if a non-default directory was used, you must run one of the
following scripts. See the ODBC Driver for Teradata readme.txt file for complete instructions.
40
•
Retain legacy structure - Run the enable_legacy_installdir script to allow legacy .ini files to
work in the new directory structure. The script emulates the legacy directory structure and
allows you to customize the odbc.ini and odbcinst.ini files.
•
64-bit Driver - Run the enable_legacy_installdir script if you installed a previous 64-bit
version of ODBC Driver for Teradata in /usr/odbc, regardless of whether you use the
default directory or a non-default directory.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
ODBC Driver for Teradata
•
Migrate to new structure - Run the convert.ini script to completely convert legacy .ini files
to the new installation directory.
•
Switch between versions - After running convert.ini, no further file migration should be
needed. However, future releases might create the need to switch between multiple
releases. In that case, run the set_default_version script to migrate to a release-independent
directory that allows for the switching between versions.
The scripts are available in the odbc_32 and odbc_64 directories after ODBC Driver for
Teradata 13.00 is installed.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 11: ODBC Driver for Teradata RFCs
RFC
Description
67684
ODBC Driver for Teradata on Sun Solaris with SPARC® supports -compat=5 and
iostream options.
96311
ODBC DSN trace entries are now time stamped.
96376
Documentation Only
ODBC DSN option descriptions were added to ODBC Driver for Teradata User Guide.
99825
LDAP (Lightweight Directory Access Protocol) authentication has been integrated into
the Teradata Database Connect dialog box. See ODBC Driver for Teradata User Guide for
details on the new dialog box options.
108139
ODBC Driver Manager was upgraded to version 5.3.
111221
ODBC Driver for Teradata online help is now provided in HTML format.
114776
ODBC Driver enhanced so that SQLGetData() no longer returns data chunks without
proper character boundary of multi-byte characters.
115298
ODBC Driver for Teradata supports the new Teradata Database 13.00 PERIOD data
types. A PERIOD data type has two values that represent the start and end of the period.
115542
ODBC Driver for Teradata supports Teradata Database geospatial SQL data types.
Note: LOB support must be enabled.
115599
ODBC Driver for Teradata supports scalar sub-queries. Scalar sub-queries are supported
everywhere a value expression is allowed compliant to ANSI syntax.
115600
ODBC Driver for Teradata supports the Teradata Database DDL replication feature.
DDL replication allows utility type names and escape sequences to be expanded in SQL
statements containing the AS USER prefix.
115602
ODBC Driver for Teradata supports the STATISTICS privilege required by the Qualified
Statistics feature.
Teradata Tools and Utilities Release Definition
41
Chapter 2: Product Information
ODBC Driver for Teradata
Table 11: ODBC Driver for Teradata RFCs (continued)
RFC
Description
115607
ODBC Driver for Teradata supports the following Teradata Database 13.00 keywords:
CONDITION, CTCONTROL, CURRENT_ROLE, GEOSEQUENCE, MBR,
OLD_NEW_TABLE, RESET, RESIGNAL, SIGNAL, ST_GEOMETRY, and THROUGH.
120485
64-bit ODBC Driver for Teradata is supported on Hewlett-Packard HP-UX with
Hewlett-Packard PA-RISC.
120634
ODBC applications can now find and use the DBS SHOW privilege in
SQLTablePrivileges.
121092
RESET is no longer a reserved word, so it can now be used as an object name in ODBC
Driver for Teradata.
121156
ODBC Driver for Teradata supports the use of tables without primary indexes (NoPI
tables).
124878
New shortcuts were added to the Start > Programs menu to help differentiate between 32bit and 64-bit versions of ODBC Driver for Teradata.
124879
ODBC Administrator now offers the same options for 64-bit as for 32-bit.
125522
ODBC Driver now checks for successive duplicate IPs in cop discovery.
127594
PERIOD is no longer a reserved word, so it can now be used as an object name in ODBC
Driver for Teradata.
128349
Cop discovery added to UNIX/Linux driver.
136201
ODBC Driver fixed so it no longer fails when using parameterized SQL with Extract
function.
137648
Enhancement added to ODBC Driver that allows fractional seconds in the conversion of
time or timestamp literals from C Char to SQL_TYPE_TIME.
115601
ODBC Driver for Teradata supports RESET WHEN syntax for window functions.
121658
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 12: ODBC Driver for Teradata DRs
42
DR
Description
93327
Previously, certain rules mapped PRIMARY KEY to PRIMARY INDEX and visa versa in
certain circumstances, which resulted in invalid syntax seeming to be valid. The
confusing mapping rules have been removed.
100423
Previously, the ODBC Extensions feature of the ODBC Driver accepted syntax such as
Date {d 'YY-MM-DD'}. When the SQL query included STAT or STATS syntax errors
can result. This problem fixed by removing STAT and STATS from the list of keywords.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
ODBC Driver for Teradata
Table 12: ODBC Driver for Teradata DRs (continued)
DR
Description
110429
The ODBC parser is not converting scalar function to standard DBS function (length as
CHAR_LENGTH) if it is embedded in a DDL. A code fix resolves the problem.
114167
On UNIX, the SQLWithCommentsOrParenthesis=[Yes | No] keyword option has a
default of No. This option is applicable only to SQLExecDirect. See ODBC Driver for
Teradata User Guide for details.
114384
Previously, ODBC Driver for Teradata incorrectly swapped the DSN and DRIVER
keywords in a connection string when the DRIVER keyword appeared first without a
trailing space. ODBC Driver for Teradata was modified and this error no longer occurs.
114662
On Novell® SUSE® Linux Enterprise, ODBC Driver for Teradata failed to connect to
Teradata Database when a UserID was not supplied. ODBC Driver for Teradata was
modified and this error no longer occurs.
115699
Documentation Only
The “DateTimeFormat Compatibility and Precision” section of ODBC Driver for
Teradata User Guide was corrected to indicate fractional truncation from
SQL_TIMESTAMP to SQL_C_TIME is not silent.
115763
Documentation Only
When the ColumnSize or DecimalDigits are outside the range of values supported by
the data source for a column in the SQL data type specified by the ParameterType
argument, ODBC Driver for Teradata truncates the data bound to the parameter and
displays a warning during execution. For more information, see ODBC Driver for
Teradata User Guide.
116045
ODBC Driver for Teradata incorrectly ignored DSN attributes passed while creating a
DSN using the installer API SQLConfigDataSource(). ODBC Driver for Teradata was
modified and this error no longer occurs.
116650
With ODBC Driver, the Create/Replace Stored Procedure would fail with 3927 error if
Max Response Buffer Size was set to 1048576. A code change fixes this problem.
117158
Previously, SQLExecute with param size greater than 1 failed with INVALID
TIMESTAMP error if the last value in array is set as NULL. Now null values for fixedlength data will be sent as having the null indicator set AND a sequence of zero bytes
corresponding to the fixed length. These will be ignored by the database.
119285
Please refer to the ODBC Driver for Teradata product ReadMe files for instructions on
specifying the correct compiler options when compiling a 64-bit application on UNIX
operating systems.
119884
"Major Status=0x1000000 Minor Status=0xe3000205-Inaccessible read" error occurred
with LDAP when using [email protected]@password. A code fix as part of DR128401 prevents
the problem.
120999
The ODBC Driver used to fail with "SQL request exceeds maximum allowed length of 1
MB " even though the size of the request is about 64 KB. Problem has been resolved by
allocating driver request/response buffers wherever needed.
121774
When a simplified Kanji logon was used with LDAP and the authentication parameter
was empty, the logon attempt failed. ODBC Driver for Teradata was modified and this
error no longer occurs.
Teradata Tools and Utilities Release Definition
43
Chapter 2: Product Information
ODBC Driver for Teradata
Table 12: ODBC Driver for Teradata DRs (continued)
44
DR
Description
122752
The use of SQLExtendedFetch causes a coredump on Solaris 64-bit and Linux64. This
issue has been fixed.
124111
ODBC applications that sent an SQL request consisting only of comments began to fail
with the 3748 or 3706 errors after upgrading the ODBC Driver to Version 12. A code fix
lets the driver properly process such requests and prevents the errors.
125264
Previously, the ODBC Driver did not work properly in manual commit mode
(SQL_AUTOCOMMIT is off) for DDL statements, and this caused the driver to autocommit DDLs when running in Teradata mode. The code has been replaced to prevent
this problem.
125770
The ODBC Driver used to display the "10040 WSA MsgSize: Message too long" error
even after the user set the Max Response Buffer Size to 1 MB. Problem has been
resolved by allocating driver request/response buffers wherever needed.
126001
In ODBC Driver SQLDescribeColW() returns an invalid SQLULEN (column size)
when the session characterset is UTF16 and the database release is prior to 12.0. The fix
removes a database version check and associated code that was causing the problem.
126694
In versions 12.0 and 13.0 of the ODBC Driver, SQLDescribeCol () returns incorrect
column length when session characterset is set to UTF8. The ODBC Driver was changed
to set the character length (SQL_DESC_LENGTH) and display size
(SQL_DESC_DISPLAY_SIZE) to the number of characters field in the Statement Info
parcel.
126772
ODBC Driver for Teradata was not using the main install directory path when it was
installed from the Teradata for Windows Load and Unload CD. This error no longer
occurs.
127130
ODBC Driver for Teradata was sending incorrect parameter data records to the
database for every SQL_PARAM_PROCEED row followed by one or more
SQL_PARAM_IGNORE rows. This error no longer exists.
128145
DataDirect DM 5.3 used to modify the value in StrLen_or_IndPtr of the
SQLBindParameter incorrectly. A fix by DataDirect to DM 5.3 resolved the problem.
128182
Previously, in ODBC Driver, a second logon screen appeared when the user logged on
to SQL Assistant. Modified code preserves and processes the password entered initially
and bypasses the second logon screen.
128401
Previously, when an ODBC Driver user used Microsoft Excel to open DSN with the
LDAP mechanism, the LAN password could be stored by Excel as clear text in a .odc
file. A code fix prevents this from happening.
128866
Previously, the Column name was not being displayed in resultset when a query did not
have a space between select and '('. The problem was resolved by always using B mode
execution.
129323
The multi-threaded PowerCenter application was causing a core dump on HP-UX
PA64 RISC. The TRACE and DSN_TRACE macros located in the codbctrace.h file
require a Lock () and Unlock () around the calls to the trace functions. This lock
prevents multiple threads from manipulating the sSprintfBuffer simultaneously and so
prevents the problem from occurring.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
ODBC Driver for Teradata
Table 12: ODBC Driver for Teradata DRs (continued)
DR
Description
130003
Installing tdodbc 13.0 improperly changed /opt/ directory and all the files below it to
root as owner. A code fix ensures that only the files under the odbc_32/odbc_64
directory are modified to root.
130685
Under the ODBC Driver 12.0.0.2, SQLDescribeCol returns incorrect length due to
CHARACTER STRING TRUNCATION with Extended Statement Information enabled
in KANJISJIS_OS. This issue resolved by setting the descriptor field
SQL_DESC_LENGTH to the number of characters for SQL_WCHAR columns in the
result set and to the number of bytes for SQL_CHAR columns.
131762
The ODBC Driver fails with the "Invalid Timestamp" error 6760. A code fix that
suppresses trailing zeros from fractional seconds in timestamps resolved the issue.
131886
The online Help files now install properly on all System Locales.
131955
The ODBC Driver can break multi-byte characters outside character boundaries for
large CREATE/REPLACE procedure requests in KANJISJIS_OS, resulting in a 6705
error. A code fix preserves character boundaries.
132152
The ODBC Driver did not detect a connection failure properly due to a coding error. A
code fix has been applied.
132470
The ODBC option DisableCALLToEXECConversion did not work properly on the
UNIX versions of the ODBC Driver, and failed with the 3855 error. The driver code is
now fixed to prevent this problem.
132599
With the Windows version of the ODBC Driver, some SQLA queries hang due to a
coding error. A code fix has been applied.
132611
The ODBC Driver parser previously did not translate the MOD function consistently. A
code fix resolved the issue.
132857
Previously, ODBC Driver users with special characters in their password could not
authenticate with the LDAP mechanism.The fix lets the driver process such passwords
properly by scanning the password for special characters and placing an escape
character (\) in front of each one.
133353
The Windows ODBC Driver for Teradata did not convert CALL to EXEC if there were
more than 98 spaces between parameters. The problem has been fixed by increasing the
size of the token buffer in the template scanner on Windows.
134558
A problem occurs when inserting numeric data with an ODBC parameterize statement
that uses the function CAST ??? FORMAT. A code fix modifies the driver to handle this
situation properly.
135438
With the ODBC Driver 13.00.00.02 and .03 SQLA freezes if the session is aborted in
Teradata Manager. The coding error responsible for this has been fixed.
135872
With the HP-UX 11.11 ODBC Driver 13.00 an ODBC application could core dump
when it tries to exit.
136309
With the ODBC Driver improper data is retrieved while there is unbound BLOB
column filled with NULL in a row. A code fix lets the driver handle such columns
properly.
Teradata Tools and Utilities Release Definition
45
Chapter 2: Product Information
OLE DB Provider for Teradata
Table 12: ODBC Driver for Teradata DRs (continued)
DR
Description
137254
The ODBC Driver did not take into account that there could be entries in the array that
have been set to SQL_PARAM_IGNORE. The code fix correctly sets status for entries
with SQL_PARAM_IGNORE to SQL_PARAM_UNUSED in accordance with the
specification.
137595
The HP-UX ODBC Driver 13.0 installation includes an update to the csh login script
that causes failures for other applications. A code fix modifies the installation script to
prevent this problem.
137871
ODBC applications could fail with SIGSEGV, Segmentation fault due to defect in
DataDirect DM 5.3. DataDirect has fixed the problem with a code fix.
138726
The ODBC Driver sends COMMIT improperly when used with Siebel CRM application
on AIX. A code fix prevents this from happening.
138975
The ODBC Driver 13.00.00.04 fails to logon with LDAP when the DSN used has not
been saved with LDAP as the mechanism. The applied code fix resolves the error.
139813
The ODBC Driver does not return column names when a multi-statement SQL request
is DIAGNOSTIC NOPRODJOIN ON FOR SESSION. A code fix makes the driver check
for and properly process multi-statement requests.
140664
Multi-threaded PowerCenter ODBC application causes core dump on AIX during
logon to the Teradata Database. An added check for Send and Receive failures during
the logon sequence resolved the issue.
OLE DB Provider for Teradata
The OLE DB Provider for Teradata allows OLE DB-based applications to access Teradata
Database. The OLE DB specification is an API based on Component Object Model (COM)
technology. The OLE DB API is supported only on Microsoft Windows operating systems.
Product Version Number
OLE DB Provider for Teradata 13.00
Supported Versions of Teradata Database
46
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
OLE DB Provider for Teradata
Documentation
OLE DB Provider for Teradata Installation and User Guide,
B035-2498-088A
Release Notes
Documentation Updates
Minor, last-minute changes were added to OLE DB Provider for Teradata Installation and User
Guide. An updated version is available at http://www.info.teradata.com/.
Version Incompatibility
After OLE DB Provider for Teradata 13.00 has been installed, do not install any other version
of OLE DB Provider for Teradata. Doing so makes OLE DB Provider for Teradata 13.00
unusable even though it appears that two versions have been correctly installed. OLE DB
Provider for Teradata 13.00 must be the only version of that software on a single client system.
If OLE DB Provider for Teradata 13.00 becomes unusable because an earlier version of OLE
DB Provider for Teradata was installed, remove OLE DB Provider for Teradata 13.00 and
reinstall it. Installing OLE DB Provider for Teradata 13.00.01 automatically removes earlier
versions.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 13: OLE DB Provider for Teradata RFCs
RFC
Description
93218
OLE DB Provider for Teradata correctly handles DECIMAL values when the user's
default locale includes a decimal separator other than the PERIOD character.
Changing the locale settings (specifically, the decimal separator) while the OLE DB
Provider for Teradata is in use might cause erroneous values to be returned from
OLE DB Provider for Teradata. For more information, see OLE DB Provider for
Teradata Installation and User Guide.
105929
OLE DB Provider for Teradata supports the Unicode Data Dictionary.
137006
The OLE DB Provider installer has been converted to Basic MSI.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Teradata Tools and Utilities Release Definition
47
Chapter 2: Product Information
Teradata Administrator
Table 14: OLE DB Provider for Teradata DRs
DR
Description
87311
OLE DB Provider for Teradata includes a connection option to use column names
instead of column titles. See OLE DB Provider for Teradata Installation and User
Guide for more information.
120698
OLE DB Provider for Teradata was changed to remove trailing pad characters from
INDEXES.COLUMN_NAME.
125893
OLE DB Provider for Teradata 13.00.01 failed to connect to Teradata Database if
OLE DB Provider 12.0 had ever been installed. The connection now works correctly.
Teradata Administrator
The Teradata Administrator provides a Windows®-based graphical interface to Teradata
Database Data Dictionary and allows multiple database administration tasks on Teradata
Database.
Product Version Number
Teradata Administrator 13.00.00.04
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Administrator User Guide,
B035-2502-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
48
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Administrator
Table 15: Teradata Administrator RFCs
RFC
Description
115943
Documentation Only
Information for retrieving User-Defined Type (UDT) data was added to Teradata
Administrator User Guide.
118175
Teradata Administrator supports Teradata Database PERIOD and Geospatial data
types.
118176
Teradata Administrator supports rules by Application Name for query logging.
118177
Access rights for Create Owner Procedure, Show, and Statistics were added to Teradata
Administrator.
118178
Teradata Administrator includes SELECT and INSERT as additional column level
access rights.
118180
Teradata Administrator supports the following new SQL syntax commands:
• Create/Replace/Drop/Show Replication Ruleset
• Set Query_Band
• Set Subscriber
SQL syntax examples for Query Builder were updated to include the new SQL syntax.
124929
Teradata Administrator supports the Teradata Database no primary index (NoPI)
tables feature.
128228
Support for GLOP Sets (a Teradata 13.0.x feature) was added.
128519
Missing Teradata 13.0 options were added to Query Logging rules.
145209
The Teradata Administrator installer has been converted to Basic MSI.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 16: Teradata Administrator DRs
DR
Description
114794
Documentation Only
Teradata Administrator User Guide states that data types used to define an identity
column must be a 4 byte or less numeric type. This appeared to conflict with
information in Database Design, which states that the largest size data type for defining
an identity column is up to DECIMAL(18,0).
Teradata Administrator User Guide was updated to clarify that the DECIMAL(18,0) is a
4 byte or less numeric type.
Teradata Tools and Utilities Release Definition
49
Chapter 2: Product Information
Teradata Access Modules
Table 16: Teradata Administrator DRs (continued)
DR
Description
115880
Documentation Only
When copying a table, Teradata Administrator copies the table structure only and does
not copy data in the table. Teradata Administrator User Guide was updated with this
information.
121067
Documentation Only
Two graphics for Query Builder were updated in Teradata Administrator User Guide.
127249
Code fix corrects problem where it was impossible to type a decimal point in any of the
fields associated with the KB/MB/GB option buttons.
130508
Teradata Administrator now correctly displays NoPI tables in alphabetical order.
130508
NoPI tables were not displayed in alphabetical order. The error no longer occurs.
138672
Teradata Administrator adds typed characters to the contents of a highlighted Password
field instead of replacing the contents. A code fix changes this behavior so that the
existing contents are replaced as expected.
138857
Teradata Administrator now displays UDFs correctly grouped together in reports.
139691
Elapsed time is now correctly displayed on the Status Bar.
139810
Code was removed that incorrectly doubled quotes in the Startup string of Modify User
function.
140425
Installation errors on Windows 7, Vista, and 2008 when run as non-administrator have
been eliminated.
Teradata Access Modules
Teradata Access Modules are software components of the Teradata utility infrastructure that
provide block-level I/O interfaces to data residing on a specific external data storage device.
Each access module is tailored to a specific type of external data storage device and can be
dynamically linked to one or more Teradata utilities.
Product Version Number
Named Pipes Access Module 13.00
Teradata Access Module for JMS 13.00
Teradata Data Connector 13.00
Teradata OLE DB Access Module 13.00
Teradata WebSphere MQ Access Module 13.00
50
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Access Modules
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Tools and Utilities Access Module Reference,
B035-2425-088A
Teradata Tools and Utilities Access Module Programmer Guide,
B035-2424-088A
Release Notes
Support for Teradata Tools and Utilities 13.0
Teradata Access Module for JMS is not included on the product installation CDs. Teradata
Access Module for JMS 13.00 will be available from the Download Center at Teradata.com in
Q4 2009.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 17: Teradata Access Module RFCs
RFC
Description
100091
Access modules built for Teradata load and unload utilities also work with Teradata PT
without any recompiling or relinking.
115851
Access Module installation packages include the Microsoft Visual C++ (x86) 8.0 merge
module, which is required to run Teradata Tools and Utilities 13.00.01 applications.
115853
115854
115849
115852
Data Connector API
133040
An API entry has been added that enables the client utilities to optionally define an I/O
buffer size rather than use the default of 65536 bytes before the open call.
141994
For Windows platforms, the Data Connector installation package is now MSI. This
enables silent installs via CLI, easier distribution across large user bases, easier
customized installs, as well as restoration to the pre-install state in case of a failed install.
Teradata Tools and Utilities Release Definition
51
Chapter 2: Product Information
Teradata Access Modules
Table 17: Teradata Access Module RFCs (continued)
RFC
Description
Named Pipes Access Module
113104
Version identification was incorporated into all source code.
Teradata OLE DB Access Module
50683
Teradata OLE DB Access Module includes a Save As button to save scripts as text files
with a variety of extensions.
53901
The Ctrl+A function can be used to select all data in a Script dialog box.
54819
Teradata OLE DB Access Module displays an error message when a user attempts to
connect to a nonexistent database or with to a database for which the user does not have
the appropriate access permissions.
54861
Teradata Database selected as a source or target correctly displays in the database tree in
the Teradata OleLoad dialog box.
58452
A Refresh button was added to the Teradata OleLoad dialog box that updates the source
database connection and the table selection.
58891
Teradata OLE DB Access Module creates a MULTISET table when the source database
allows duplicate rows.
59179
Teradata OLE DB Access Module supports case-sensitive column names to avoid data
loss for type strings.
116093
Teradata OLE DB Access Module can be used with Teradata PT. Teradata OleLoad can
be used to create simple Teradata PT scripts and start Teradata PT jobs.
116373
Teradata OLE DB Access Module supports the new Teradata Database 13.00 PERIOD
data types. A PERIOD data type has two values that represent the start and end of the
period.
123121
Teradata OLE DB Access Module supports LDAP authentication.
124960
Teradata OLE DB Access Module now allows account-specific logins.
131472
English and Japanese help files are now copied to OLE DB Access Module installation
directory.
144000
OLE DB Access Module packages on Windows were converted to Basic MSI.
Teradata WebSphere MQ Access Module
117858
117889
64-bit Teradata WebSphere MQ Access Module is supported on Hewlett-Packard
HP-UX Intel Itanium (Itanium build).
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
52
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Access Modules
Table 18: Teradata Access Module DRs
DR
Description
Data Connector API
135509
Data Connector installation "Error 1720" on Windows 7, Vista, and 2008 was corrected
when run as a non-administrator.
138850
When installing the Data Connector API on Solaris operating systems, to prevent
installation aborts, ensure that the user-defined installation path in the install script is
not read-only.
Named Pipes Access Module
114822
This issue occurred on Linux operating systems only. Named Pipes Access Module was
enhanced to prevent core dumps caused by overly long file names.
134000
When installing the Named Pipe Access Module on Solaris, if /opt is chosen as the base
installation directory and it is a link to another location, the installation process
removes the link, creates an /opt directory, and installs the product. This has been
corrected.
138848
Named Pipe Access Module installation mounting errors on Solaris were resolved.
140379
Named Pipe Access Module installation "Error 1720" on Windows 7, Vista, and 2008
was corrected when run as a non-administrator.
143043
Named Pipe Access Module used to show the following misleading warning message
"Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html". The
warning message was removed.
Teradata OLE DB Access Module
129469
Previously, restarting Teradata OLE DB Access Module required users to re-enter the
domain name of their ODBC and CLI connections. Now, the domain name is
remembered.
130394
Teradata OLE DB Access Module saved user passwords for Teradata Database even if
option "Allow saving password" was not selected in the connection properties. This
error no longer occurs.
Teradata WebSphere MQ Access Module
118474
Documentation Only
Teradata Tools and Utilities Access Module Reference documents the fact that
multi-volume checkpoint files are not supported.
118476
Documentation Only
The JCL code sample was updated in Teradata Tools and Utilities Access Module
Reference.
134076
When installing the IBM MQ Access Module on Solaris, if /opt is chosen as the base
installation directory and it is a link to another location, the installation process
removes the link, creates an /opt directory, and installs the product. This has been
corrected.
Teradata Tools and Utilities Release Definition
53
Chapter 2: Product Information
Teradata Archive/Recovery Utility
Table 18: Teradata Access Module DRs (continued)
DR
Description
138847
IBM MQ Access Module installation mounting errors on Solaris were resolved.
140380
IBM MQ Access Module installation "Error 1720" on Windows 7, Vista, and 2008 was
corrected when run as a non-administrator.
142727
On z/OS, when a channel name of 20 or more characters is defined, the target storage is
overrun. This has been corrected. Names that are less that 20 characters are now
padded.
Teradata Archive/Recovery Utility
Teradata ARC archives, restores, and recovers databases and tables between Teradata
Database systems.
Product Version Number
Teradata ARC 13.00.00.07
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Archive/Recovery Utility Reference,
B035-2412-088A
Release Notes
Teradata Database Compatibility
Pre-13.00 versions of Teradata ARC are not compatible with Teradata Database 13.00.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
54
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Archive/Recovery Utility
Table 19: Teradata ARC RFCs
RFC
Description
59455
Teradata ARC supports join indexes.
61096
Error code 5312 was reclassified as a warning.
104836
A LINEWRAP runtime parameter was added to specify the number of characters at
which Teradata ARC turns off wrapping or wraps the output log. See Teradata Archive/
Recovery Utility Reference and Teradata Tools and Utilities Command Summary for more
information.
109087
ARC1016 warning is suppressed for excluded tables.
109458
Documentation Only
The list of dictionary rows are archived as part of user databases was incomplete in
Teradata Archive/Recovery Utility Reference; the list was updated.
111002
SKIP RIGHTS CHECK was added to ARCHIVE, COPY, and RESTORE to skip the
validation of access rights before Teradata ARC processes those commands. For more
information, see Teradata Archive/Recovery Utility Reference and Teradata Tools and
Utilities Command Summary.
113005
To improve performance when archiving, Teradata ARC optimizes local sessions when
assigning AMPs.
113323
Teradata ARC redefines the severity of some Teradata Database error codes.
114218
The DBSIZEFILE option was added to the RESTORE command to resize a database
during a restore operation. See Teradata Archive/Recovery Utility Reference and Teradata
Tools and Utilities Command Summary for more information.
115518
Teradata ARC supports Teradata Database buffering enhancements to improve restore
performance to a non-identical configured Teradata Database system.
115523
The following tables that support IUMB changes were added for the backup and restore
of database DBC:
• ReconfigInfo
• ReconfigOrder
• ReconfigTableStats
115526
Teradata ARC supports archiving and restoring individual objects. Copying individual
objects is also allowed, with the exception of triggers.
115943
Documentation Only
Information on UDTs and User-Defined Methods (UDMs) was expanded in Teradata
Archive/Recovery Utility Reference.
117002
QueryStatsTbl and StatsTbl were added for the qualified statistics feature.
117692
Teradata ARC supports the Teradata Database larger partition ID size; partition ID size
was increased from 2 bytes to 8 bytes (16-bit to 64-bit).
117719
Teradata ARC supports the file system fault isolation feature.
Teradata Tools and Utilities Release Definition
55
Chapter 2: Product Information
Teradata Archive/Recovery Utility
Table 19: Teradata ARC RFCs (continued)
RFC
Description
120393
For a partition-level restore, the number of rows actually restored to the table display in
the ActivityCount field of the SUCCESS parcel returned to Teradata ARC. This allows
Teradata ARC to count exactly how many rows were copied into the partition and
match the rows actually written into the Teradata Database table in a partition-level
restore.
120682
Teradata ARC supports new Teradata Database errors generated for the
HUTCKDMPDONE request, which is associated with the online archive feature.
123959
Teradata ARC supports the Teradata Database no primary index (NoPI) tables feature.
127264
ARC now treats an all-AMP cluster archive as an all-AMP archive.
127752
ARC now supports local AMP backup and restore for multi-stream backup.
129227
ARC now supports a new table kind, 'Y', for a GLOP data
set.
134110
A new NOSYNC option has been added to LOGGING ONLINE, ARCHIVE statements.
135015
The 7535 error has been converted to a warning instead of failure.
135627
Additional access rights checks are now turned off in ARC by default.
137690
The check for the NetVault access module has been removed so that NetVault can take
advantage of the ARC "local amp" performance enhancements.
141281
Additional information is shown when tables are skipped due to checksum error.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 20: Teradata ARC DRs
DR
Description
108980
The problem of delays due to repositioning when copying many objects from a backup
was resolved.
111605
Teradata ARC stopped responding when a gateway timeout occurred. This problem was
related to logging on to Teradata ARC sessions, and no longer occurs.
114247
Documentation Only
Teradata Archive/Recovery Utility Reference was updated to reflect that Teradata ARC
does not support object names larger than 30 bytes.
56
114612
When performing a restore of a database with the CATALOG option, the CATALOG
reposition requests failed. This issue was resolved.
114931
When restarting a copy job, Teradata ARC tried to write the restart record to the restart
log file, causing Teradata ARC to abort. This error no longer occurs.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Archive/Recovery Utility
Table 20: Teradata ARC DRs (continued)
DR
Description
115014
Documentation Only
MODIFY TABLE was changed to ALTER TABLE in Teradata Archive/Recovery Utility
Reference.
115258
Documentation Only
The term ARCHIVE privilege was corrected to DUMP privilege in Teradata Archive/
Recovery Utility Reference.
115411
A 7596 error occurred when logging was disabled after a dictionary dump for online
archive. The OVERRIDE option allows the log disable process to proceed, even during
the archive process.
116127
Multi-ARC backup jobs were having a negative effect on Teradata user applications
because Multi-ARC was only logging its control sessions into the specified Teradata
resource partition. This issue was resolved.
116543
Teradata ARC reported incorrect TOTALBLOCKS for the archive output file. This
error no longer occurs.
116969
Teradata ARC failed with an illegal memory access error when a multi-stream
backup is run in DUMMY mode. This issue was resolved.
118133
Teradata ARC failed with an ARC0001 error when attempting to archive a
Teradata 12.0 system using Teradata Tiered Archive and Restore Architecture. This
error no longer occurs.
118873
Teradata ARC was not reporting job failure to the Teradata Tiered Archive and Restore
Architecture server when an error occurred while attaching an access module. This issue
was resolved.
119160
Using the CATALOG feature in Teradata Tiered Archive and Restore Architecture 1.1,
Teradata ARC failed to restore child streams of an object when restoring an individual
table from a database-level backup. An ARC error resulted, indicating an improper
reposition, or an unexpected end-of-archive record. The CATALOG feature now works
correctly.
119751
An 3737 error occurred when Teradata ARC 12.0 was used to copy ALL PARTITIONS
from a selected partitions archive file created from a Teradata Database V2R 6.2 system
using Teradata ARC 8.2. This error no longer occurs.
119929
The text of the Teradata ARC 1240 error code corrects the term “VAMP” to “AMP”.
The term is also corrected in Messages.
120770
An archive with cataloging enabled resulted in a substantial delay in performance. This
issue was resolved.
120776
During a multi-stream restore, Teradata ARC stopped responding when attempting to
restore a database with no data objects. This error no longer occurs.
120808
Documentation Only
The term OTB is changed to Backup Application Software in Teradata Archive/Recovery
Utility Reference.
Teradata Tools and Utilities Release Definition
57
Chapter 2: Product Information
Teradata Archive/Recovery Utility
Table 20: Teradata ARC DRs (continued)
DR
Description
121180
When Teradata ARC was used with a UFT8 character set on MP-RAS operating
systems, the mutlibyte character data set name was unexpectedly truncated or
corrupted. This caused errors about missing files and objects. Sometimes character set
conversion errors resulted. This error no longer occurs.
121557
Teradata ARC stopped responding during the data phase of a restore when restoring or
copying individual partitions from a Teradata Database V2R6.x archive to Teradata
Database 12.0. This issue was resolved.
122499
Online Archive fails in ARC when archiving table in loading state (Mload). Issue has
been resolved.
124676
When running a restart test of a Copy job, the restart fails due to an "ARC0600:Invalid
restart record found in DBCLOG" error. This has been corrected.
124695
Incorrect warning "8258 :Orphan dictionary row discarded" displayed during
dictionary restore. Code fix was implemented.
124781
When performing an archive using the _DUMMY option for FILE=, ARC will crash
with an "*** Internal Failure ARC0001:OpsSHndl:An illegal memory access was
attempted" error, indicating an invalid memory access. A code fix has been
implemented.
125175
Problem has been corrected where TARA for TIVBAR multistream restore of a backup
created with the catalog option fails.
125175
Multi-stream archives/restores with multiple sessions per AMP failed when using the
CATALOG option. The problem no longer occurs.
125221
ARC used to display an Internal Failure ARC0001:SOCConnect: Error 97 in socket()
call. The code fix sets the ai_socktype member of the 'hints' parameter to
SOCK_STREAM; this causes getaddrinfo() to return information consistent with a TCP
connection.
125255
When a table-level object was archived using Netbackup with the CATALOG option
turned on, the restore operation failed. This occurred only when the table size was more
than 1GB.
This error no longer occurs.
58
126121
A Restore failure can occur in cross-platform migrations. The code fix redesigns the
UDT recompiling logic to prevent the problem.
126349
Jobs may fail with one of two errors: "*** Internal Failure ARC0001:Tried to send DReq
pcl on sess which is not READY", if the logon process takes a long time to complete; or
"*** Internal Failure ARC0001:SMCPROCS.SMDBCRcv internal error on session 2", if
a DBS restart occurs. The code fix ensures that all sessions which do not complete the
logon process upon gateway timeout are reset to UNDEFINED, so that the retry will log
that session on again, and that the SMDBCRcv logic properly handles the
DISCONNECTED session state.
126379
When running a restore of a database with empty tables, multiple restarts are shown in
the job output along with the "Warning ARC1217:No data to restore for table" error.
The code fix changes how the ABORT_TABLE status is handled in RestTable when this
situation arises.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Archive/Recovery Utility
Table 20: Teradata ARC DRs (continued)
DR
Description
127864
During installation, InstallShield and the installation scripts used only the first few
digits of the version number, missing any e-fixed versions.
Installation scripts were modified and this error no longer occurs.
128301
When restoring a multi-stream job using NetVault, the restore operation failed if the
CATALOG option was turned on.
This error no longer occurs.
128302
If a database restart occurred during an archive job after one or more checkpoints were
taken, Teradata ARC restarted the archive of the table that was in progress when the
restart occurred; however, the resulting archive had missing data.
This error no longer occurs.
128304
When restarting an Archive job when using a MONITOR session, ARC displays the "***
Internal Failure ARC0001:DBCHWAT said we had a parcel but the fetchcode we got
back on session -1 was 1" error. The code fix adds logic to handle the reset of a
MONITOR session after a DBS restart.
128434
ARC returns an EOF error if Catalog is used in the Restore of a dictionary table. The
issue is resolved.
128823
Online backup fails with ARC syntax error (3707) when archiving a non-table object.
Code fix checks for this situation.
128824
ARC did not report that it had archived the Join/Hash indexes to TARA or NetVault.
The code necessary to prevent errors due to his situation was added.
129243
The Restore of a multi-stream online archive hangs. This issue is resolved.
130184
On a restore, if an error occurs which causes ARC to skip a table (or end it early), ARC
could fail on the next object with an ARC0001 error. This problem has been resolved.
130194
During the dictionary phase of an archive, the process runs slowly, 3-4 seconds per table
because the table header is being read on all AMPs. This issue is resolved.
131392
ARC did not properly handle role access rights. New code fixes the rights check for
nested and default roles.
131997
The ARC softlink is deleted during upgrade on Linux. A code fix prevents this from
occurring.
132606
When restoring between different platforms or releases, ARC may not properly build
join or hash indexes after a restore. This will occur when one of the tables referenced by
the join/hash index is a PPI table. The code fix prevents this by issuing the ALTER
TABLE .. REVALIDATE PRIMARY INDEX statement for any tables on a restore across
platform or release.
133426
RESTORE JOURNAL TABLE returns error 3932 during NPARC migration. The issue is
resolved.
133446
On a dictionary or cluster restore, ARC may return 1278 warning messages. ARC now
skips the PPI revalidate step for dictionary and cluster restores. This step is done (if
appropriate) during the BUILD phase.
Teradata Tools and Utilities Release Definition
59
Chapter 2: Product Information
Teradata Archive/Recovery Utility
Table 20: Teradata ARC DRs (continued)
60
DR
Description
133448
On a cluster or specific-AMP restore, ARC may return an 8210 error indicating an
improper directed request. The code fix prevents this from happening.
133706
"Error 3807:Object 'DBC.AllRoleRightsV' does not exist" occurs during the 'recompile
UDT/UDF/UDM' processing after restoring DBC/SYSUDTLIB during a migration
from V2R6.2 to V13.0. This has been resolved.
133753
In a TARA multi-stream job, when one of the streams fail, ARC continues with the rest
of the streams till all streams are finished. The job is not aborted fully. The issue is
resolved.
134336
A TARA multi-stream job fails with the "ARC0805:Access Module returned error code
9: End-of-file" error. New code fixes this problem.
134368
ARC now properly handles skipped tables in multi-stream restore.
135019
When restoring or copying journal tables using a TARA-launched single-stream or
multi-stream job, ARC may fail with "*** Internal Failure ARC0001:Tried to send DReq
pcl on sess which is not READY" error. This issue is resolved.
135021
Attempting to restore/copy a cluster archive back to the same DBS using the multistream feature and the CATALOG option returns "ARC0119:Catalog row not found for
object <objectname>". New code fixes this.
135024
ARC turns the CATALOG feature on for backup/restore jobs if the NOCATALOG
option is specified before the CATALOGDB parameter. The code fix prevents this from
happening.
138440
ARCMAIN 13 on LINUX/Windows does not print CHKPT: in logs in verbose mode.
The code fix re-enables this feature.
138572
ARCMAIN fails in multi-stream environment when building a logon string if the total
length of the logon string (TDPID/USER,PASS) is an exact multiple of 30 bytes. Code
fix increases the buffer size to prevent the problem.
138926
ARCMAIN fails with 8243 error on cluster restore. The issue has been resolved.
139005
Error BAM 1000: Access Module passed OBJNAME attribute
D"PROD_IGT_PLAYERMANAGEMENT_STG" occurs because the string is too long.
The problem has been fixed.
139006
ARC fails after a DBS restart. Code change fixed the problem.
139512
In Linux a TARA job query gives a segmentation violation if the first object in the
database being queried is a non-data object. This issue is resolved.
139518
Online Logging Info is incorrect in a TARA online backup. The problem has been
resolved.
140799
ARCHIVE is using a large amount of memory above the line. This no longer happens.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Call-Level Interface version 2
Teradata Call-Level Interface version 2
Teradata CLIv2 provides a library of routines that enable an application program to access
data stored on Teradata Database.
Product Version Number
•
Teradata CLIv2 for channel-attached systems (CAS) 13.00
•
Teradata CLIv2 for network-attached systems (NAS) 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems,
B035-2417-088A
Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems
B035-2418-088A
Release Notes
Hewlett-Packard HP-UX 11i v1 (11.11)
To use Teradata CLIv2 for NAS on Hewlett-Packard HP-UX 11i v1 (11.11), you must
download the following patches from the Hewlett-Packard web site: PHCO 24400, 24401,
24402, and PHNE 2412.
HSHSPB Keywords
The HSHSPB default of IBCFBRL was inconsistently 1024 in the distributed assembler source,
but was 2048 in the distributed macro; both defaults are now 1024. If customization had
removed the specification from the assembler source before assembly, the macro value of
2048 would have been used. Although unlikely and negligible, the change from 2048 to 1024
could adversely affect performance by either dynamically increasing the size or requiring
more fetches.
The HSHSPB sequence numbers were changed. Any reference to those sequence numbers (for
example, by SMPs use of the MVS IEBUPDTE utility) require adjustment.
Teradata Tools and Utilities Release Definition
61
Chapter 2: Product Information
Teradata Call-Level Interface version 2
Previously Reserved QEP Byte
Teradata CLIv2 for CAS includes a new query that returns the Teradata Database access path.
A QEP byte previously reserved is now used. If existing applications do not ensure unused
areas are initialized to binary zeroes as required, a Teradata CLIv2 return code 1147 might
occur reflecting an invalid value in the newly assigned field.
Teradata CLIv2 for NAS Application Core Dump
When an earlier version of the libc library is used on Hewlett-Packard HP-UX, the following
error might occur when starting Teradata CLIv2 for NAS applications:
/usr/lib/dld.sl: Unresolved symbol: pthread_mutex_lock (code) from /
usr/lib/libcliv2.sl Abort(coredump)
OR
CLI error: MTDP: EM_GSSINITFAIL(235): call to gss_init failed.
Solution
Update the libc library by applying the HP-UX 11.11 patch PHCO_24400 or later, which is
available from the Hewlett-Packard patch web site.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 21: Teradata CLIv2 RFCs
RFC
Description
Teradata CLIv2 for CAS
105493
Applications using Teradata CLIv2 for CAS can now detect whether the Teradata
Database column correlation feature is supported.
105686
Teradata CLIv2 for CAS passes return codes and parcel definitions in C programming
language.
106071
Teradata CLIv2 for CAS supports job entry subsystem 2 (JES2) job numbers greater
than 65,535.
110155
106460
115070
Teradata CLIv2 for CAS supports Statement Information parcels. A new field was
added at the end of the Statement Information response parcel.
The reserved field in the database-interface extension to the Configuration Response
parcel was replaced with a new field to indicate whether Teradata Database supports
Statement Information parcels in a request.
62
106877
Teradata CLIv2 for CAS supports both SAS/C® and IBM C compilers.
108906
Teradata CLIv2 for CAS includes a new query that returns the Teradata Database
session character set.
109220
Teradata CLIv2 for CAS supports 12 new character sets. See Teradata Call-Level
Interface Version 2 Reference for Channel-Attached Systems for more information.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Call-Level Interface version 2
Table 21: Teradata CLIv2 RFCs (continued)
RFC
Description
113472
Teradata CLIv2 for CAS includes a new query that detects the Teradata Database node
ID associated with a session.
113597
See “HSHSPB Keywords” on page 61.
114988
Teradata CLIv2 for CAS supports temporal tables and queries. In addition, a field was
added to the Statement Information response parcel to reflect the temporality of the
column.
115814
See “Previously Reserved QEP Byte” on page 62.
115943
Documentation Only
Information on UDTs and UDM was expanded in Teradata Call-Level Interface Version
2 Reference for Channel-Attached Systems.
116015
Teradata CLIv2 for CAS supports the new Teradata Database 13.00 PERIOD data types.
118986
Teradata CLIv2 for CAS is supported on IBM CICS® Transaction Server for z/OS 3.2.
Teradata CLIv2 for NAS
105227
The default maximum size of a COPANOMLOG file was changed to 250 MB. When
this limit is reached, the first file is closed and a new one is created to prevent the files
from getting too large for an operating system. Users can change the default file size.
106013
A new runtime environment variable, CLI_RECON_WAIT, was added to allow users to
specify a reconnect time-out value between 1 to 3,600 seconds; the default is 2 seconds.
106139
A loop in configuration response processing was corrected by validating the first 2 bytes
of a response message (Version and Class) to ensure they correspond to the protocol.
These changes improve CLIv2 response time when users log on with an incorrect IP
addresses.
107850
Teradata CLIv2 for NAS includes three new ICU error messages that better define the
current generic (510) loadtdicu errors: Tdicu load library error [527], Tdicu load
symbol error [528], and Tdicu unload error [529].
108586
Applications using Teradata CLIv2 for NAS can now skip the logmech_data_ptr/
logmech_data_Len parameters and log in with logon_ptr alone (LDAP authentication).
111599
Teradata CLIv2 for NAS includes a new query that returns the Teradata Database access
path.
111614
Teradata CLIv2 for NAS includes a new query that returns the Teradata Database
session character set.
111615
Applications using Teradata CLIv2 for NAS can now detect whether the Teradata
Database column correlation feature is supported.
112838
User exits are loaded in a way that makes it easier to determine exit methodology.
113468
Teradata CLIv2 for NAS includes a new query that detects the Teradata Database node
ID associated with a session.
Teradata Tools and Utilities Release Definition
63
Chapter 2: Product Information
Teradata Call-Level Interface version 2
Table 21: Teradata CLIv2 RFCs (continued)
RFC
Description
115324
Teradata CLIv2 for NAS includes a new query that identifies load jobs with LOBs and
makes it more efficient to load them.
115326
A new QEPITSS (50) DBCHQE query was added that determines whether a target
server supports the Teradata Database trusted sessions feature.
115330
Teradata CLIv2 for NAS supports the following new Teradata Database activity types:
119336
•
•
•
•
•
•
115931
Teradata CLIv2 for NAS supports the new Teradata Database 13.00.01 PERIOD data
types.
115943
Documentation Only
Create Operator
Drop Operator
Replace Operator
Rename Operator
Grant Conn. Through
Revoke Conn. Through
Information on UDTs and UDM was expanded in Teradata Call-Level Interface Version
2 Reference for Network-Attached Systems.
119905
Special characters in passwords, such as @, are escaped in the UPN.
135979
13.0 CLIv2 package now provides 12.0 CLIv2_64 dependency on Linux.
141730
The Teradata CLIv2 for NAS installer changed to a Basic MSI package.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 22: Teradata CLIv2 DRs
DR
Description
Teradata CLIv2 for CAS
113421
When using Teradata Tools and Utilities 8.2 against Teradata Database V2R6.2.1.1,
Teradata FastExport exported DECIMAL(18) fields as 8 bytes (15 digits) when
DECIMALDIGITS 18 was not specified.
The default of binary zero was changed from 15 digits to 18 digits to eliminate
incompatibilities in DECIMAL values. See Teradata Call-Level Interface Version 2
Reference for Channel-Attached Systems for details.
115015
Documentation Only
The term MODIFY TABLE was changed to ALTER TABLE in Teradata Call-Level
Interface Version 2 Reference for Channel-Attached Systems.
64
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Call-Level Interface version 2
Table 22: Teradata CLIv2 DRs (continued)
DR
Description
115313
Documentation Only
Security considerations were added to Teradata Call-Level Interface Version 2 Reference
for Channel-Attached Systems.
115428
Documentation Only
The information about certain data types was corrected in Teradata Call-Level Interface
Version 2 Reference for Channel-Attached Systems.
115809
Documentation Only
The information about the ENCODING operand value was clarified and enhanced in
Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems.
116239
Documentation Only
The ElicitFile parcel description was corrected in Teradata Call-Level Interface Version 2
Reference for Channel-Attached Systems.
116760
Documentation Only
Detail about the ContinueRequest function was added to Teradata Call-Level Interface
Version 2 Reference for Channel-Attached Systems.
117929
Information regarding copying a CLIv2 RCB was clarified in Teradata Call-Level
Interface Version 2 Reference for Channel-Attached Systems. The DBCCPR must also
copy the full owner-id enlargement that is populated when the session was established.
119098
Documentation Only
The size of the DataInfoX and PrepInfoX parcel fields was corrected in Teradata CallLevel Interface Version 2 Reference for Channel-Attached Systems.
120168
Documentation Only
Elicit parcels information was clarified in Teradata Call-Level Interface Version 2
Reference for Channel-Attached Systems.
Teradata CLIv2 for NAS
103269
Teradata CLIv2 for NAS was changed to prevent sessions from being cleared when a
node goes down before a timeout.
108062
When a required LDAP parameter is missing from the logon, a question mark appears
in place of the minor error text. The issue has been resolved.
112642
Teradata CLIv2 for NAS distinguishes what character set is used to construct messages
returned in user-defined areas or in the DBCAREA message text area.
115616
Previously, Teradata CLIv2 for NAS stopped responding when attempting to recover
from a CLI 207 (EM_NETCONN) error. Teradata CLIv2 for NAS was modified to set
the session ID and display an error code.
116238
Documentation Only
The ElicitFile parcel description was corrected in Teradata Call-Level Interface Version 2
Reference for Network-Attached Systems.
Teradata Tools and Utilities Release Definition
65
Chapter 2: Product Information
Teradata Director Program
Table 22: Teradata CLIv2 DRs (continued)
DR
Description
116388
On Hewlett-Packard HP-UX, Teradata CLIv2 for NAS did not send the entire text of a
message. The message sent to Teradata Database was shorter than the length indicated
in the lanheader, and a subsequent keep-alive message was interpreted by Teradata
Database as the end of the previous message which caused an 8014 error. Teradata
CLIv2 for NAS was modified and this error no longer occurs.
116719
Teradata CLIv2 for NAS correctly processes the Account ID in a logon string on UTF16
sessions.
116763
Teradata CLIv2 for NAS was modified so it functions correctly when an end-of-line
(0xa0) byte is missing.
119099
Documentation Only
The size of the DataInfoX and PrepInfoX parcel fields was corrected in Teradata CallLevel Interface Version 2 Reference for Network-Attached Systems.
121281
Documentation Only
Several QEPITEM queries were corrected in Teradata Call-Level Interface Version 2
Reference for Network-Attached Systems.
121263
If a negative conn id is assigned and passed to OsRecv (only possible from recvmsg), a
core dump occurs in OsRecv on MP-RAS. This error no longer occurs.
125404
An incorrect isi file causes the attempt to upgrade a CLIv2-32.13 lettered build to
13.0.0.0 to fail. The issue is resolved.
125901
CLIv2 13.0 is incompatible with CLIv2_64 if the latter is already installed. Code fix
solves the problem by removing CLIv2_64 during the install process.
137365
When CLI/libcliv2.so or ODBC/libtdsso.so is loaded, the Solaris OS creates misaligned
trap handlers for the libraries, because they were linked with the -misalign flag. When
ODBC/libtdsso.so is unloaded, the trap associated with it is not removed, and
misaligned calls within the application cause an exception. The problem was solved by
recompiling libtdsso without the -misalign flag.
137623
After upgrading from CLIv2 13.00.00.01 to 13.00.00.03, FastExport and Multiload coredump. The problem (a mislabeled file) has been resolved.
140058
Cliv2 13.10 Installation failed with "Error 1720" on Windows 7, Vista, and 2008 when
run as non-administrator. The Required Execution Option of the setup.exe file changed
to Administrator.
145193
A CLIv2 for NAS file descriptor limit can be exceeded causing CLI to be unable to
connect additional sessions. Code fixes were implemented to prevent this.
Teradata Director Program
TDP is a high-performance interface for messages between the client and the Teradata system.
TDP is the data communications component of Teradata Database.
66
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Director Program
Product Version Number
TDP 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Director Program Reference,
B035-2416-088A
Release Notes
SET LIMIT NORESP
The default value of nn in the SET LIMIT NORESP nn command was changed from 50 to 75.
Use of any SET LIMIT NORESP nn command where nn is less than 76 should be
discontinued.
Deprecation of the IFP interfaces
The external IFP interfaces were deprecated and replaced with CP interfaces. The ATTACH,
DETACH, START, and STOP commands were changed to support the CPnnn operand. The
DISPLAY CP command was extended to include the deprecated DISPLAY IFP functionality.
Automated operations products that depend upon the static content of TDP messages may
require adjustment since many messages have changed; for example, the CPname is now often
enclosed in quotation marks.
z/OS Messages and Descriptor Codes
For compatibility with IBM z/OS, descriptor code 4 was added for command responses.
Automated operations products or operator message routing that depend upon z/OS
descriptor codes may require adjustment because descriptor code 4 was added to command
responses, which affects processing of descriptor codes or the system log.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Teradata Tools and Utilities Release Definition
67
Chapter 2: Product Information
Teradata Dynamic Workload Manager
Table 23: TDP RFCs
RFC
Description
105491
Two internal TDP control blocks were changed to enhance internal diagnostics.
105492
Applications using TDP can now detect whether the Teradata Database column
correlation feature is supported.
106460
A new field was added to the end of the full-layout, self-defining portion of the
Statement Information response parcel.
106662
See “Deprecation of the IFP interfaces” on page 67.
109219
TDP supports 12 new character sets. See Teradata Director Program Reference for more
information.
110570
TDP detects whether Teradata Database supports Statement Information parcels in a
request.
113066
See “z/OS Messages and Descriptor Codes” on page 67.
114403
TDP supports Teradata Database 12.0 result sets.
114988
TDP supports temporal tables and queries.
116015
TDP supports the new Teradata Database 13.00 PERIOD data types. A PERIOD data
type has two values that represent the start and end of the period.
117219
TDP supports the Teradata Database trusted sessions feature.
117306
See “SET LIMIT NORESP” on page 67.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 24: TDP DRs
DR
Description
115810
Information on the ENCODING operand value was enhanced in Teradata Director
Program Reference.
Teradata Dynamic Workload Manager
Using Teradata DWM, you can set up rules that manage database access, increase database
efficiency, and enhance workload capacity. The rules include workload limits on accounts,
users, and objects, such as databases, tables, and more.
68
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Dynamic Workload Manager
Product Version Number
Teradata DWM 13.00.00.07
Supported Versions of Teradata Database
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Dynamic Workload Manager User Guide,
B035-2513-088A
Release Notes
Utility Throttles
When a utility throttle is in effect, the maximum limit (which is 60% of max AWT, normally
48) is used internally for MaxLoadAWT regardless of the DBSControl value. When the
MaxLoadAWT is already set at the maximum, it is unaffected by the active utility throttle.
However, when the MaxLoadAWT is lower than the maximum, it is overridden by active
utility throttle.
The “Utility Throttles” section in Chapter 7 of Teradata Dynamic Workload Manager User
Guide incorrectly states that the throttling rate set for the FastLoad + MultiLoad option is the
only option that overrides the MaxLoadTasks value. However, all the utility throttle options
(FastLoad + MultiLoad, FastLoad, MultiLoad, FastExport, and Archive/Restore) set using
Teradata DWM override the MaxLoadTasks value.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 25: Teradata DWM RFCs
RFC
Description
108585
The Priority Scheduler view includes a check box under a new Active column that
enables dynamic recalculation of Allocation Group (AG) weights. For details, see
Teradata Dynamic Workload Manager User Guide.
111634
Throttle and filters names can now be changed after they have been defined.
111943
Teradata DWM supports wildcard characters in object names used with category 3 rules
only. See Teradata Dynamic Workload Manager User Guide for details.
116248
112186
115960
Specific data objects can be excluded as classification criteria when defining a new
workload. For information on using the Classify by Object dialog box, see Teradata
Dynamic Workload Manager User Guide.
Teradata Tools and Utilities Release Definition
69
Chapter 2: Product Information
Teradata Dynamic Workload Manager
Table 25: Teradata DWM RFCs (continued)
70
RFC
Description
112349
The Filters and Throttles Enabled dialog box was redesigned to include a column for
each system state. For details, see Teradata Dynamic Workload Manager User Guide.
113041
The procedures for creating filters and throttles has changed. See Teradata Dynamic
Workload Manager User Guide for details.
115050
Field names on the Blocker tab were changed from Deadlock Cycles and Deadlock
Action to Block Cycles and Block Action, respectively. All references were updated in
Teradata Dynamic Workload Manager User Guide.
115412
Users can log on to Teradata DWM and work in local mode to view or modify rule sets
without logging on to Teradata Database.
115957
Teradata DWM 13.00.01 is backwards compatible with Teradata Database 12.0.
116242
The Post to Queue Table feature (previously called Queue Table) is now available for
exception processing and event processing.
116247
Queries can now be rejected by for one or more specific states. For details, see Teradata
Dynamic Workload Manager User Guide.
117318
Exceptions can now be renamed after they have been defined.
117320
Exception qualification time must be a multiple of the exception interval. Teradata
DWM displays a warning message before overriding the given value if it is not within
the acceptable range. See Teradata Dynamic Workload Manager User Guide for details.
117322
New icons in the Description tab can be used to specify the throttle type when defining
an object throttle rule. For more information, see Teradata Dynamic Workload Manager
User Guide.
117324
The New Event dialog box was modified to improve usability. See Teradata Dynamic
Workload Manager User Guide for details.
117325
A Split Screen command was added to the View menu that displays two panes: the
bottom pane accesses DIT features and the upper pane displays the state matrix. See
Teradata Dynamic Workload Manager User Guide for details.
117326
A new event can be defined from the Event Combinations and Actions - System
Condition view when defining an event combination. For more information, see
Teradata Dynamic Workload Manager User Guide.
117327
System states are readily visible in the State pane in the Priority Scheduler. See Teradata
Dynamic Workload Manager User Guide for details.
118199
In addition to the default tdwm user, other users with read-only permissions can now
be defined for Teradata DWM. For more information, see Teradata Dynamic Workload
Manager User Guide.
121527
The New Exception dialog box was modified to improve usability. See Teradata
Dynamic Workload Manager User Guide for details.
124982
TDWM now supports tables of type 'O' from DBC.tableV.
128583
A limited features version of TDWM is now available to support 1550/2500/2550
systems.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Dynamic Workload Manager
Table 25: Teradata DWM RFCs (continued)
RFC
Description
145184
The TDWM install has been converted to a Basic MSI package.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 26: Teradata DWM DRs
DR
Description
113927
Teradata DWM dump utility displayed the wrong classify order when Service Level
Goal information was not specified for the current Operating Environment. The
Teradata DWM dump utility now uses the CurrentID of the Operating Environment
for the WD, rather than the ActualID of the Operating Environment for the WD.
In addition, a -t option was added to Teradata DWM dump utility to display delay
queue and throttle statistics. For more information, see Teradata Dynamic Workload
Manager User Guide.
114263
The Rule Set Inquiry dialog box now displays 30 characters for the Rule Set name.
114732
The term penalty box was replaced with the term lower-priority WD.
115045
Documentation Only
The New Event dialog box description was updated to clarify that the number of AMPs
reported as AMP Fatal includes AMPs at fatal, offline, or utility at system startup. See
Teradata Dynamic Workload Manager User Guide for details.
115925
Documentation Only
Previously, the default value for system condition duration time and the event
qualification time was incorrectly documented as 180 seconds. Teradata Dynamic
Workload Manager User Guide was corrected to reflect that the default value for system
condition duration time and the event qualification time is the current event interval
value.
116136
Documentation Only
Teradata Dynamic Workload Manager User Guide includes an “Asynchronous
Operations and Throttle Limits” section that describes what occurs when a throttle
limit is exceeded.
116678
Previously, users could not enter a value greater than 99 in the Limit box in the AMP
Worker Tasks frame of the Priority Scheduler System Level Parameters dialog box even
though the actual limit was 120 AWTs. Teradata DWM was modified to allow the
correct maximum value.
118796
Previously, users could create OpEnv (operating environment), SysCon (system
condition), and states with the same name. Teradata DWM now includes checks to
ensure those names are unique.
Teradata Tools and Utilities Release Definition
71
Chapter 2: Product Information
Teradata Dynamic Workload Manager
Table 26: Teradata DWM DRs (continued)
DR
Description
119893
When a query is rejected by a Teradata DWM rule, Teradata DWM displays a 3150
error message based on the threshold type (time or row count) along with the estimated
value. When the estimated process time exceeds 360000000000.0 CPU seconds or the
row count exceeds 99,999,999,999 rows, Teradata DWM displays one of the following
3150 error messages, indicating an overflow occurred:
Estimated time ************ milliseconds exceeds limit.
Estimated value ************ rows exceeds limit.
72
124149
It is possible for a user to create a WD Classification that has Excluded objects but no
Included objects without any warning. A warning message has been added.
124318
A TDWM problem with Global Exception and Utility WD caused confusion by not
properly updating the interface. This has been fixed.
124321
Several TDWM Help IDs were either missing or led to the wrong topic. They have all
been fixed as needed.
124404
For a Throttle rule when changes are not accepted and an object is deleted, the interface
was not properly updated. This prevented the user from adding new objects to the rule.
The problem has been fixed.
124765
When the user clicks in the tree while the Everyday check box is selected and no days are
checked, the screen does not update properly and the period cannot be corrected. A
code fix corrects the problem.
125341
A Save RuleSet error was occurring when the queryband value had single quotes. A code
fix prevents the error from happening.
126612
The Bypass dialog appeared to freeze up when the system had thousands of users. A
code change prevents this from happening.
129208
TDWM creates a long duration transaction which causes trouble for the WAL purge
task due to an exclusive lock on the TDWM database. This has been changed so there is
no impact on the WAL operation.
132375
TDWM displayed an incorrect warning based on AG weight. The code fix ensures that
it now correctly displays the warning based on REL weight instead.
139098
TDWM Incorrectly set workloads as expedited in the Priority Scheduler screen of the
TDWM Administrator. This has been fixed.
140500
TDWM Admin did not work correctly with Viewpoint Workload Monitor on V12 and
V13 systems due to a missing feature. The Activation time of a ruleset is now recorded
in tdwm.GlobalParams so that the two components work properly together.
141714
TDWM installation errors occurred on Windows 7, Vista, and 2008 when the installer
was run as non-administrator. This has been fixed.
141816
The TDWM GUI displayed incorrect workload classification. The code fix corrects this
problem.
142705
TDWM verify.exe was not properly checking for both FPSPR70.ocx and FPSPRU70.ocx
and would return an error. This has been corrected.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata FastExport
Table 26: Teradata DWM DRs (continued)
DR
Description
144012
After the password for user tdwm was changed, the logon procedure for TDWM
returned an error when the current ruleset was activated. This issue has been resolved.
Teradata FastExport
Teradata FastExport is a command-driven utility that uses multiple sessions to quickly
transfer large amounts of data from tables and views of Teradata Database to a client-based
application.
Product Version Number
Teradata FastExport 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata FastExport Reference,
B035-2410-088A
Release Notes
Documentation Updates
Minor, last-minute changes were added to Teradata FastExport Reference. An updated version
is available at http://www.info.teradata.com/.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 27: Teradata FastExport RFCs
RFC
Description
93546
Teradata FastExport passes .logdata in UTF16 character sets for extended security.
Teradata Tools and Utilities Release Definition
73
Chapter 2: Product Information
Teradata FastExport
Table 27: Teradata FastExport RFCs (continued)
RFC
Description
96414
Teradata CLIv2 is correctly identified as a software dependency for Teradata
FastExport. Teradata software packages now install in order and upgrade operations are
successful.
115943
Documentation Only
Information regarding UDTs and UDMs was added to Teradata FastExport Reference.
116002
Teradata FastExport supports the new Teradata Database 13.00 PERIOD data types. A
PERIOD data type has two values that represent the start and end of the period.
116023
Teradata FastExport no longer directly links to Teradata ICU, and Teradata FastExport
no longer needs to be recompiled and re-linked when Teradata ICU is updated.
100895
Teradata FastExport 13.00.01 is compiled with Microsoft Visual Studio® 2008 and
requires the new Visual Studio runtime libraries. The Teradata FastExport installation
package includes the Microsoft Visual C++ (x86) 8.0 merge module, which is required
to run Teradata Tools and Utilities 13.00.01 applications.
115846
110172
117574
Teradata FastExport allows the ACCEPT or SET commands prior to using a LOGON or
LOGTABLE command.
121177
Teradata FastExport now supports double-quoted strings in commands.
142188
For Windows platforms, the Teradata FastExport installation package is now MSI. This
enables silent installs via CLI, easier distribution across large user bases, easier
customized installs, as well as restoration to the pre-install state in case of a failed install.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 28: Teradata FastExport DRs
DR
Feature or Enhancement
114106
Teradata FastExport correctly processes Unicode data xx1A characters, such as
(U+4F1A) and (U+511A).
114114
Documentation Only
A semicolon cannot be used in an object name because a semicolon designates the
end of a Teradata FastExport command. See Teradata FastExport Reference for
details.
119500
Documentation Only
The IMPORT command syntax diagram in Teradata FastExport Reference was
corrected to remove the APPLY-WHERE clause.
125530
74
It is now possible to generate Teradata MultiLoad scripts with the correct length
for large decimal fields with Teradata FastExport.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata FastLoad
Table 28: Teradata FastExport DRs (continued)
DR
Feature or Enhancement
128222
A new IGNORECONFIGERRORS option allows a job to continue even though
the configuration file contains syntax errors.
128264
Teradata FastExport creates a garbage field in MultiLoad scripts when tables
contains a column defined as BIGINT NOT NULL. The problem no longer occurs.
130367
Scripts generated on a Windows system contained incorrect UTF16 characters.
The problem no longer occurs.
131317
Teradata FastExport was adding extra characters to most of the lines of output
when the following runtime parameters were used: -u utf8, -i utf8, -c utf8. The
problem no longer occurs.
133562
After receiving a 2633 error using the UTF-16 character set, the Teradata
FastExport retry failed with a 3697 error. This was fixed.
134031
When using the UTF-16 character set, Teradata FastExport failed exporting multi
tables on one script with the MLSCRIPT option. This problem has been resolved.
134317
On MPRAS, Teradata FastExport displayed a “RDBMS failure, 3704” message
instead of waiting for available sessions after an RDBMS 2633 error message
occurred. This problem has been resolved, and FastExport now allots for tenacity
time.
136629
When running a Notify Exit routine, Teradata FastExport would terminate the job
with a segmentation violation. This problem has been resolved.
139205
138884
On the Solaris platform, the Teradata FastExport install failed on read only
mounted file systems. This problem has been resolved by including prompts to use
the required installation options.
140367
On Windows Vista, Windows 7, and Windows Server 2008, an "Error 1720"
occurred during Teradata FastExport installation. This problem has been resolved.
140854
Teradata FastExport failed when using the UTF-16 charset with request sizes
greater than 3200 characters in length. This problem has been resolved.
144359
Text sent to the output log file as specified with the .ROUTE MESSAGES TO FILE
statement was being truncated. Additionally, NULL characters were sent to the log
file. This problem has been resolved.
Teradata FastLoad
Teradata FastLoad is a command-driven utility that quickly loads large amounts of data in an
empty table on Teradata Database.
Product Version Number
Teradata FastLoad 13.00
Teradata Tools and Utilities Release Definition
75
Chapter 2: Product Information
Teradata FastLoad
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata FastLoad Reference,
B035-2411-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 29: Teradata FastLoad RFCs
RFC
Description
93544
Teradata FastLoad passes .logdata in UTF16 character sets for extended security.
96411
Teradata CLIv2 is correctly identified as a software dependency for Teradata FastLoad.
Teradata software packages now install in order and upgrade operations are successful.
100894
Teradata FastLoad 13.00.01 is compiled with Microsoft Visual Studio 2008 and requires
the new Visual Studio runtime libraries. The Teradata FastLoad installation package
includes the Microsoft Visual C++ (x86) 8.0 merge module, which is required to run
Teradata Tools and Utilities 13.00.01 applications.
115844
112462
Teradata FastLoad includes a new -w runtime parameter users can use to specify the
width of output messages. Valid values are from 62 bytes to 256 bytes.
114889
Documentation Only
Do not use Notepad to view Unicode or multibyte character sets output from Teradata
FastLoad. Use Word or any other Hex editor instead. See Teradata FastLoad Reference
for more information.
76
116001
Teradata FastLoad supports the new Teradata Database 13.00 PERIOD data types. A
PERIOD data type has two values that represent the start and end of the period.
116021
Teradata FastLoad no longer directly links to Teradata ICU, and Teradata FastLoad no
longer needs to be recompiled and re-linked when Teradata ICU is updated.
128052
To improve debugging, Teradata FastLoad now supports trace levels 1-5 for SA Data
Connector on channel attached and network attached platforms. Previous versions only
supported trace level 5.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata FastLoad
Table 29: Teradata FastLoad RFCs (continued)
RFC
Description
129955
Teradata FastLoad now supports the RUN FILE command to be consistent with the
other Teradata load/unload utilities.
142189
For Windows platforms, the Teradata FastLoad installation package is now MSI. This
enables silent installs via CLI, easier distribution across large user bases, easier
customized installs, as well as restoration to the pre-install state in case of a failed install.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 30: Teradata FastLoad DRs
DR
Description
109001
Teradata FastLoad correctly processes a NULLIF condition specified in a DEFINE
command from a UTF16 session character set.
114112
Teradata FastLoad can now process xx1A characters, such as (U+4F1A) and
(U+511A), in Unicode data.
114114
Documentation Only
A semicolon cannot be used in an object name because a semicolon designates the
end of a Teradata FastLoad command. See Teradata FastLoad Reference for details.
119170
Documentation Only
Teradata FastLoad Reference was corrected to state that the maximum length of a
delimiter is 10 bytes, not 10 characters.
119239
Documentation Only
Teradata FastLoad Reference was updated with the correct compile syntax for
INMODS on a Linux systems:
gcc -shared -fPIC inmod.c -o inmod.so
119500
Documentation Only
The IMPORT command syntax diagram in Teradata FastLoad Reference was
corrected to remove the APPLY-WHERE clause.
126971
Teradata FastLoad intermittently displayed the message “Total processor time used
= 'could not be determined from o.s." This problem no longer occurs.
127562
Parsing rules for the SET QUERY_BAND command were updated to allow
Teradata FastLoad to recognize an equal sign as a word separator, with or without
a proceeding space.
127800
To improve VARTEXT records procession performance, Teradata FastLoad now
scans delimited non-UTF-16 character set fields using pointer arithmetic instead of
scanning via the strlen() function.
Teradata Tools and Utilities Release Definition
77
Chapter 2: Product Information
Teradata Generic Security Services
Table 30: Teradata FastLoad DRs (continued)
DR
Description
127815
A new IGNORECONFIGERRORS option allows a job to continue even though
the configuration file contains syntax errors.
131607
In previous versions, Teradata FastLoad would not parse the NOSTOP keyword
when a delimiter string contained blank or tab characters. This issue has been
resolved with a code update.
138886
On the Solaris platform, the Teradata FastLoad install failed on read only mounted
file systems. This problem has been resolved by including prompts to use the
required installation options.
140376
On Windows Vista, Windows 7, and Windows Server 2008, an "Error 1720"
occurred during Teradata Fastload installation. This problem has been resolved via
a code change.
143771
On Windows and Linux platforms, when loading VARTEXT delimiter records
data using INMOD, Teradata Fastload failed with multibyte characters sets. This
problem has been resolved via a code change.
Teradata Generic Security Services
Teradata GSS is the Teradata implementation of industry-standard Generic Security Services
APIs, which are defined by Internet Engineering Task Force (IETF) Request for Comments
(RFC) 2743, “Generic Security Service Application Program Interface version 2, Update 1.”
TeraGSS provides enhanced security services interfaces between Teradata network clients and
Teradata Database.
There are two libraries for the TeraGSS feature:
•
TeraGSS–C library
•
tdgssjava–Java library
Product Version Number
Teradata GSS 13.00
Supported Versions of Teradata Database
78
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Index Wizard
Documentation
Release Summary,
B035-1098-098A
Security Administration,
B035-1100-098A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software. There are no RFCs for this product for this release.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates. There are no DRs for this product for this release.
Teradata Index Wizard
Teradata Index Wizard allows a Database Administrator to create or identify a workload,
perform index analysis for a workload, and verify and apply index recommendations to
maximize system performance.
Product Version Number
Teradata Index Wizard 13.00.00.04
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Index Wizard User Guide,
B035-2506-088A
Release Notes
None.
Teradata Tools and Utilities Release Definition
79
Chapter 2: Product Information
Teradata Index Wizard
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 31: Teradata Index Wizard RFCs
RFC
Description
112735
Teradata Index Wizard supports new Unicode V-views. See Teradata Index Wizard User
Guide for more information.
114569
Workload definition time is reduced by avoiding redundant statistics collections in
Teradata Index Wizard.
116067
An Index Recommendations report displays instead of the Summary dialog box when
index analysis, partition analysis, and restart analysis are completed.
116562
A Time Limit Expired column was added to the Analysis Summary dialog box. The
values for this column are Yes or No. For more information, see Teradata Index Wizard
User Guide.
116645
An Index Type column was added to the Validation Results window. This column
displays the type of index used during index validation.
117247
Teradata Index Wizard supports analysis of workloads with 1 MB query text.
118777
Restart Analysis supports time limit and checkpoint frequency. See Teradata Index
Wizard User Guide for details.
122165
For SAS, support has been added for database tables that have no primary index (NoPI
tables).
135386
Modified statistics show/update operations, while using the What-IF feature, to support
new sample estimate fields.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 32: Teradata Index Wizard DRs
DR
Description
116563
From and To options were added to the Partition Inputs group of the What-If Analysis
dialog box. See Teradata Index Wizard User Guide for details.
116564
The error message for index analysis was updated to display the following:
Invalid Time Limit. Enter Time Limit between 1 and 2880.
80
116565
The Analysis Summary dialog box columns are left justified for improved readability.
117104
Descriptions for the Filter and List Names options in the Select QueryBand group in
Select Criteria dialog box were updated for better clarity. For details, see Teradata Index
Wizard User Guide.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata International Components for Unicode
Table 32: Teradata Index Wizard DRs (continued)
DR
Description
124791
Existing Indexes workload report did not show information for tables that had only a
Primary Index. The error no longer occurs.
137206
The ParseSQLStatement in CDTIWQueryText is returning error codes when for valid
ANSI comments. This problem was resolved by modifying the validation code for
comments.
140431
Installation fails when Windows Vista, Windows 7, or Windows Server 2008 are
installed using non-administrator privileges. Changed the Required Execution Level
option in setup.exe to require administrator privileges.
144608
Based on reported installation problems, the TIWIZ installation package has been
converted to the Basic MSI installation package.
Teradata International Components for
Unicode
Teradata ICU is based on IBM International Components for Unicode version 3.6 and
provides a C/C++ library for Unicode support. It is an installation prerequisite for Teradata
CLIv2, ODBC Driver for Teradata, and OLE DB Provider for Teradata. Because this library
cannot be accessed directly by an end-user, no documentation is provided.
Product Version Number
Teradata ICU 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
None.
Release Notes
None.
Teradata Tools and Utilities Release Definition
81
Chapter 2: Product Information
Teradata International Components for Unicode
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 33: Teradata ICU RFCs
RFC
Description
117263
The environment variable ICU_DATA to was changed to TD_ICU_DATA to prevent
conflict between Teradata ICU and any another version of ICU a customer might have
on their system.
124304
Support for 81 KANJIEUC characters has been added for AIX, HP UX, Solaris, Solaris
Opteron and Linux platforms (32-bit packages).
132257
TDICU libraries on Linux and HP-UX-IA64 are now built with "-Bsymbolic" option for
resolving all symbols internally.
140643
The TDICU 13.0 installer has been converted to a Basic MSI package.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 34: Teradata ICU DRs
DR
Description
124063
Various multi-byte characters could not be inserted properly using a KANJIEUC_OU
session from the ODBC Driver, resulting in error 6706 “The string contains an
untranslatable character error.” This problem no longer occurs.
124725
The ODBC Driver is no longer able to display hankaku-katakana characters on
Windows using KANJISJIS sessions, even though they were correctly inserted with a
KANJIEUC_OU session. This functionality is now available via TDICU.
125402
Incorrect isi file fails to upgrade TDICU-32.13 lettered build to 13.0.0.0. The issue is
resolved.
127869
When the 13.0 E-Fix package is installed in Windows, the version number in Add or
Remove Programs still shows 13.0 instead of 13.0.0.1. This is now fixed.
140057
TDICU 13.10 Installation fails with "Error 1720" on Windows 7, Vista, and 2008 when
run as non-administrator. The Required Execution Option of the setup.exe file changed
to Administrator.
Copyright Information
ICU License - ICU 1.8.1 and later
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1995-2009 International Business Machines Corporation and others
82
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata JDBC Driver
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software
and associated documentation files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy, modify, merge, publish,
distribute, and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, provided that the above copyright notice(s) and this permission notice
appear in all copies of the Software and that both the above copyright notice(s) and this
permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR
ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY
DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
OF THIS SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in
advertising or otherwise to promote the sale, use or other dealings in this Software without
prior written authorization of the copyright holder.
All trademarks and registered trademarks mentioned herein are the property of their
respective owners.
Teradata JDBC Driver
Teradata JDBC ® (Java Database Connectivity) Driver is a specification for an API that allows
platform-independent Java applications to access database management systems using SQL.
Product Version Number
Type 4 Teradata JDBC Driver 13.00.00.27
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
•
Teradata Database 13.10
Teradata Tools and Utilities Release Definition
83
Chapter 2: Product Information
Teradata JDBC Driver
Documentation
Teradata JDBC Driver User Guide,
B035-2403-088A
Release Notes
Documentation Updates
Minor, last-minute changes were added to Teradata JDBC Driver User Guide. An updated
version is available at http://www.info.teradata.com/.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 35: Teradata JDBC Driver RFCs
RFC
Description
69205
More precise classification occurs for DATE, TIME, and TIMESTAMP values bound to
PreparedStatement question-mark parameter markers beginning with Teradata
Database 12.0 and Teradata JDBC Driver 12.0. This allows Teradata Database to
provide better implicit data type conversion for those data types.
Beginning with Teradata JDBC Driver 12.0 and Teradata Database 12.0, java.sql.Date
values are sent to Teradata Database as DATE values using the ANSIDate DateForm.
This provides Y2K-compliant implicit conversion for java.sql.Date values specified with
the PreparedStatement/CallableStatement setDate or setObject methods, and sent to
destination CHAR/VARCHAR columns and parameters. Legacy applications requiring
non-Y2K-compliant behavior can use Teradata-specific Escape Syntax functions
introduced in Teradata JDBC Driver 12.0.
84
97103
The TDSession object responsible for each log message is identified in Teradata JDBC
Driver log output.
97560
Teradata JDBC Driver provides a mechanism that allows the debug logging to be turned
on or off per request.
98096
The Teradata JDBC Driver was changed to avoid submitting an unnecessary COMMIT
after a request for ANSI mode connections with auto commit enabled.
98176
Teradata JDBC Driver avoids the unnecessary step of explicitly closing the response
spool after all results have been fetched, when the executeUpdate method was called
and/or LOB_SUPPORT=OFF.
99487
The Teradata JDBC Driver now supports PreparedStatement batch updates with
connection parameter LOB_SUPPORT=OFF.
100090
The LOB_SUPPORT=OFF and the LOB_SUPPORT=ON database connection
parameters are handled the same by the Teradata JDBC Driver, such that a larger buffer
size is used for all response messages of a large result set.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata JDBC Driver
Table 35: Teradata JDBC Driver RFCs (continued)
RFC
Description
101075
The Client version (not the JDBC Driver version) has been added to the Client Config
parcel information passed during connect processing, as required by the Query Director
for proper operation.
104643
The Teradata JDBC Driver CallableStatement getObject method was changed to return
Time or Timestamp objects for TIME or TIMESTAMP data types, respectively, when
connected to a Teradata Database V2R6.1 or earlier release.
106221
The Teradata JDBC Driver ResultSet and CallableStatement getDate methods with
Calendar parameter were changed to use the Calendar argument's TimeZone to
construct the returned java.sql.Date values for DATE and TIMESTAMP data values
(without TIME ZONE) from the Teradata Database.
106222
The Teradata JDBC Driver ResultSet and CallableStatement getTime methods with
Calendar parameter were changed to use the Calendar argument's TimeZone to
construct the returned java.sql.Time values for TIME and TIMESTAMP data values
(without TIME ZONE) from the Teradata Database.
106708
Teradata JDBC Driver provides additional timing measurements.
106710
The DatabaseMetaData methods getProcedures and getProcedureColumns have been
enhanced to report on external stored procedures in addition to internal (SQL) stored
procedures.
107027
Teradata JDBC Driver provides a login time-out function using the value set by the
Driver Manager setLoginTimeout or DataSource setLoginTimeout.
108348
Teradata JDBC Driver supports dynamic result sets returned from Java external stored
procedures with Teradata Database 13.00.
110511
When using Teradata Database 12.0, Teradata JDBC Driver sends more complete and
accurate metadata to Teradata Database to describe values bound to PreparedStatement
question mark parameter markers. This facilitates certain Teradata Database features,
such as better implicit data type conversion for certain data types.
111264
Teradata JDBC Driver supports Teradata FastExport protocols. Setting the TYPE
connection parameter to FASTEXPORT instructs the Teradata JDBC Driver to
automatically use the Teradata FastExport protocol for PreparedStatement selects
compatible with Teradata FastExport.
112298
Teradata JDBC FastLoad feature provides additional validation of PreparedStatement
parameter values, in order to reduce the occurrence of rows placed into Teradata
FastLoad error tables by Teradata Database.
Teradata JDBC Driver ignores the TNANO and TSNANO connection parameters for
JDBC FastLoad. Teradata JDBC FastLoad feature sends TIME and TIMESTAMP data
values with the same scale as the destination column.
112566
The [NCR] prefix was removed from Teradata JDBC Driver error messages.
112569
The tdgssjava.jar file is no longer required by the Teradata JDBC Driver. The classes
formerly in tdgssjava.jar reside in terajdbc4.jar. This reduces the number of jar files
from three to two, and simplifies deployment and maintenance.
Teradata Tools and Utilities Release Definition
85
Chapter 2: Product Information
Teradata JDBC Driver
Table 35: Teradata JDBC Driver RFCs (continued)
RFC
Description
113344
Specifying the connection parameter TYPE=FASTLOAD instructs Teradata JDBC
Driver to attempt to use JDBC FastLoad, if possible. However, an SQL request must
meet specific criteria for Teradata JDBC FastLoad to be used. Teradata JDBC Driver
provides an SQL warning to indicate the reason why Teradata JDBC FastLoad could not
be used, in cases where Teradata JDBC FastLoad can not be used.
113678
The following features were added to the CREATE/REPLACE PROCEDURE command
for creating an External Stored Procedure (XSP):
• If errors occur when creating the procedure, then an SQLException chain is
composed and thrown from the execute or executeUpdate method
• If warnings occur when creating the procedure, then an SQL warning chain is
composed and made available to the application using Statement.getWarnings
114154
Teradata JDBC Driver provides the CallableStatement addBatch and executeBatch
methods, working with Teradata Database restrictions. For a batched CALL to a stored
procedure, Teradata JDBC Driver executes the CALL multiple times sequentially. No
performance gain should be expected for a batched CALL to a stored procedure,
because a network round trip must be made to Teradata Database for each set of
parameter values in the batch.
114465
Documentation Only
Four new sections were added to Teradata JDBC Driver User Guide in Chapter 2:
“Session Time Zone,” “Multi-Statement Requests,” “Teradata Database Macros,” and
“Creating User-Defined Functions and External Stored Procedures.”
114956
Teradata JDBC Driver supports the Teradata Database trusted sessions feature (user
impersonation with query banding). A sample program is provided to demonstrate
how to use the SET QUERY_BAND statement with PROXYUSER.
114981
Teradata JDBC Driver includes the error code and SQLState at the beginning of all
SQLException messages.
115269
Teradata JDBC FastLoad was changed so a PreparedStatement executeBatch returns a
BatchUpdateException when all rows are not processed successfully.
A connection rollback does not cause a SQLException when rows are found in the
FastLoad error tables by Teradata JDBC FastLoad. Instead, SQL warnings are added to
the Connection’s warning chain.
86
115627
Teradata JDBC Driver supports Java User-Defined Functions. A sample program is
provided to demonstrate how to use Java User-Defined Functions (UDF) with Teradata
Database 13.00.
115639
The Teradata JDBC Driver now accepts input java.sql.Struct values from an application
as parameter marker values, and provides output java.sql.Struct values from result sets
and stored procedure output for Structured and Internal UDT values.
115664
Teradata JDBC Driver supports LDAP authentication using Novell eDirectory with
Teradata Database 13.00.
115855
The PreparedStatement and CallableStatement setObject methods with targetSqlType
argument send the fractional seconds portion of a java.sql.Time value to Teradata
Database.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata JDBC Driver
Table 35: Teradata JDBC Driver RFCs (continued)
RFC
Description
115943
Documentation Only
Information regarding UDTs and UDMs was added to Teradata JDBC Driver User
Guide.
116276
Teradata JDBC Driver supports using the getConnection parameters username and
password when using LDAP authentication with Teradata Database V2R6.2 and later
releases. Username and password must be specified using the LOGDATA connection
parameter when using LDAP authentication with Teradata Database V2R6.0 and
V2R6.1.
116279
Teradata JDBC Driver provides SQLException error message text in English, by default.
Teradata JDBC Driver provides SQLException error message text in Japanese when the
JVM locale is set using command-line arguments: -Duser.language=ja
-Duser.country=JP.
116489
Teradata JDBC Driver supports new Teradata Database 13.00 SQL keywords and ANSI
SQLStates.
117048
The JDBC Driver has been changed to support Period Data Types using the
java.sql.Struct interface.
118803
The KATAKANAEBCDIC session character set is not supported by Teradata JDBC
Driver. Teradata JDBC Driver User Guide was corrected to remove a reference to the
KATAKANAEBCDIC session character set.
119320
Teradata JDBC Driver returns a result set composed of Teradata Database output, if
any, when an existing UDF is replaced using the REPLACE FUNCTION statement.
120309
Teradata JDBC Driver supports data encryption, LDAP authentication, and Kerberos
authentication for Teradata FastLoad, Teradata FastExport, and Monitor connections.
120378
Teradata JDBC Driver supports a literal IP address as a Teradata Database host name.
121952
The Statement.close method was changed to avoid causing a SQLException when the
Teradata Database connection is already closed.
122317
The Teradata JDBC Driver now supports FastExport Direct Mode with Teradata
Database 13.10.
122340
The Teradata JDBC Driver now supports Teradata Database 13.10 Trusted Sessions
Security.
123191
The Teradata JDBC Driver now supports Teradata Database 13.10 TASM workload
management.
123376
The DatabaseMetaData getColumnPrivileges and getTablePrivileges methods were
changed to support new Teradata Database 13.00 access rights.
123711
All JDBC Sample Programs changed to demonstrate the recommended
CHARSET=UTF8 connection parameter.
Teradata Tools and Utilities Release Definition
87
Chapter 2: Product Information
Teradata JDBC Driver
Table 35: Teradata JDBC Driver RFCs (continued)
88
RFC
Description
124457
The Teradata JDBC Driver now supports the Teradata Database 13.10 feature for
PreparedStatement batch execution to return individual success and error conditions
for each parameter set in the update count array provided with BatchUpdateException.
Good parameter sets are processed by the Teradata Database, and bad parameter sets
are rejected individually, with specific errors for each bad parameter set provided as
SQLExceptions chained to the BatchUpdateException.
127101
The Teradata JDBC Driver now supports the Teradata Database 13.10 Extended Object
Names in Parcels (EONP) feature.
129206
The Teradata JDBC Driver was changed to support the new SQL keywords and
SQLState mappings introduced in Teradata Database 13.10.
131214
The Teradata JDBC Driver now supports incremental fetch for Console connection
result sets.
132251
The Teradata JDBC Driver was changed to improve Thread reference usage for pooled
Statement objects.
132370
The Teradata JDBC Driver DatabaseMetaData getColumns method now supports the
Teradata Database 13.0 Period and Geospatial data types.
133045
The Teradata JDBC Driver was changed to escape certain special characters in
passwords used for LDAP authentication.
133291
The JDBC Sample Program that demonstrates changing the transaction isolation level
was simplified.
133304
The Teradata JDBC Driver was changed to support PreparedStatement setNull with
PreparedStatement setClob or setBlob within the same batch insert request.
133599
The DatabaseMetaData getTables method in the Teradata JDBC Driver has been
enhanced to support a table type of GLOBAL TEMPORARY.
133717
The Teradata JDBC Driver was changed to print query timeout messages at the INFO
logging level, rather than at the ERROR level.
134413
The Teradata JDBC Driver PreparedStatement and CallableStatement setDate methods
with Calendar parameter were changed to use the Calendar argument's TimeZone to
compose the DATE value sent to the Teradata Database.
134573
The Teradata JDBC Driver was changed to enable ResultSet and CallableStatement
getTimestamp methods to perform implicit data type conversion to return a
java.sql.Timestamp for a TIME or TIME WITH TIME ZONE data value from the
database, and to return the TIME value's complete fractional seconds in the
java.sql.Timestamp nanos field.
135093
The Teradata JDBC Driver DatabaseMetaData getColumnPrivileges method was
changed to return leading spaces that may be present in the schema name, table name,
and column name.
137079
The JDBC Driver now supports calling the ResultSet getAsciiStream or
getCharacterStream method for a CLOB column value in accordance with the JDBC 4.0
API Specification.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata JDBC Driver
Table 35: Teradata JDBC Driver RFCs (continued)
RFC
Description
138607
The existing Tdgss and JDBC code incorrectly created multiple instances of the
TdgssConfigApi class. Each new instance caused the TdgssLibraryConfigFile.xml and
TdgssUserConfigFile.xml to be parsed and merged. The code fix has changed this
behavior so the configuration files are parsed only once and initialization performance
is improved.
139320
Support for session charsets KANJISJIS_0S and KANJIEUC_0U has been added in
JDBC FastLoad so it mirrors the same functionality in the standalone FastLoad utility.
139380
JDBC FastExport now supports the same additional session character sets supported by
the standalone FastExport utility.
139774
The Teradata JDBC Driver was changed to reduce finalizer locking for already-closed
ResultSets. No change was made to the behavior for an orphaned ResultSet that was not
closed by the application.
139824
The Teradata JDBC Driver DatabaseMetaData getColumns method was changed to
ignore Teradata Database Error 3523 "The user does not have any access to
dbname.tabname" from a HELP COLUMN request to gather information about a
view's column(s).
140148
The PERIOD type name has been added to the SQLWarning message when attempting
JDBC FastLoad into table with PERIOD data type.
142328
The DatabaseMetaData getColumns method of the Teradata JDBC Driver was changed
to avoid a Teradata Database Optimizer problem that produces a bad query plan when
the Data Dictionary contains hundreds of thousands of tables.
143408
DatabaseMetaData methods now use Data Dictionary V-views in TD 12.0 and later for
better performance.
143576
Connection parameter TYPE=FASTLOADCSV has been added. This greatly improves
the Teradata JDBC Driver performance when loading large amounts of data into the
Teradata Database.
145146
JDBC FastLoad CSV connection parameter FIELD_SEP has been added. This provides
the versatility of defining different field separators (column delimiter characters).
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 36: Teradata JDBC Driver DRs
DR
Description
101194
When the connection property LOB_SUPPORT is set to OFF, Teradata JDBC Driver
automatically downgrades an application request for a scrollable result set from
TYPE_SCROLL_INSENSITIVE or TYPE_SCROLL_SENSITIVE to
TYPE_FORWARD_ONLY, and provide a corresponding SQL warning.
Teradata Tools and Utilities Release Definition
89
Chapter 2: Product Information
Teradata JDBC Driver
Table 36: Teradata JDBC Driver DRs (continued)
DR
Description
102357
Teradata JDBC Driver supports null and non-null values bound to the same parameter
marker for different rows in a PreparedStatement batch, when the parameter marker
refers to an SQL TIME or TIMESTAMP type.
After this change, a combination of PreparedStatement.setTime and
PreparedStatement.setNull method calls can be used to bind values to a TIME column.
In addition, a combination of PreparedStatement.setTimestamp and
PreparedStatement.setNull method calls can be used to bind values by a TIMESTAMP
column.
90
108301
The CallableStatement.setNull method supports a NULL input value bound to a
question mark parameter marker corresponding to a stored procedure INOUT
TIMESTAMP parameter.
118048
With Teradata Database V2R6.2 and earlier, Teradata JDBC Driver 12.0 ResultSet
positioning methods might throw IndexOutOfBoundsException for a ResultSet
containing more rows than could fit into a single response message from the database.
Teradata JDBC Driver was changed and this error no longer occurs.
118571
Teradata JDBC Driver correctly handles the DataSource custom property CHARSET
with respect to PreparedStatement.setString non-ASCII characters.
119000
The ResultSetMetaData.isAutoIncrement method returns true for an identity column
with Teradata Database V2R6.2 and later releases.
120597
Teradata JDBC Driver uses the application-specified Statement setQueryTimeout value
when waiting to read the response from Teradata Database after a query timeout has
occurred for an SQL request, and to close the socket and indicate a communications
failure to the application if a second timeout occurs in that situation.
120705
Teradata JDBC Driver returns a SQLException with error code 832 from the
PreparedStatement setNull method for certain error conditions caused by unsupported
SQL data types.
120929
Teradata JDBC Driver provides correct information from the DatabaseMetaData
getColumns method when using the UTF8 session character set.
121130
Teradata JDBC Driver supports the PreparedStatement getParameterMetaData method
with multi-statement macros and multi-statement requests.
123280
GSSException from initSecContext was not providing any useful information for
troubleshooting. Specifically, the tdgssjava source code discarded the root-cause
exception from the JDK. The code fix provides the root-cause exception from the JDK
as the "cause" of the GSSException that is thrown to the Teradata JDBC Driver. This
makes the root-cause exception available for troubleshooting JDK configuration
problems.
124683
TDGSSJAVA Kerberos was failing when Data Encryption was specified and the server
was MPRAS. This problem no longer occurs.
125601
The DHGKey attribute for the TD2 and LDAP mechanisms was incorrectly specified in
little endian. The code fix ensures that the correct value is specified as big endian.
132356
TDGSS Java LDAP Mechanism did not handle Non US-ASCII characters in logdata,
resulting in a failure. The code fix prevents this from happening.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata JDBC Driver
Table 36: Teradata JDBC Driver DRs (continued)
DR
Description
132545
The JDBC Driver did not send correct charset in Unicode LDAP logons. The Teradata
JDBC Driver was changed to consistently use the Teradata session character set during
LDAP logons, thereby ensuring that if a logon error occurs, the error message can be
properly received from the Teradata Database.
134440
Error 858, 'No value has been set for parameter' might be returned when a query
contains both single and double quotes and one or more question marks are found
within the quotes. The Teradata JDBC Driver was changed to support
PreparedStatement SQL request text containing combinations of single quotes, double
quotes, SQL comments, and question mark parameter markers.
135882
The Teradata JDBC Driver was changed to avoid OutOfMemoryError when the
getMoreResults method is used with a multi-statement request that returns a large
result set.
136276
The Teradata JDBC Driver was changed to restore the behavior of the
ResultSetMetaData getPrecision method in Teradata JDBC Driver version 13.00.00.08
and earlier, so that zero precision is returned for a DATE column.
136380
The Teradata JDBC Driver was changed to restore the implicit data type conversion of
the ResultSet getDate method on a CHAR or VARCHAR column containing integer
date values.
138870
When some invalid JDBC methods are called, they throw a NullPointerException
instead of a invalid method Exception. The Teradata JDBC Driver was changed to avoid
this problem.
140534
A NullPointerException from PreparedStatement setNull Types.STRUCT occurs when
using V2R6.1. A code fix changes the JDBC Driver to throw SQLException from
PreparedStatement setNull for the value Types.STRUCT instead.
141432
The following missing methods and calls have been added:
Missing methods in TeraDataSourceBase
• getSIP_SUPPORT
• setSIP_SUPPORT
Missing code in TeraDataSourceBase.getReference
• ref.add for "sipSupport"
Missing calls in TeraObjectFactory.getObjectInstance
• tds.setLOB_SUPPORT
• tds.setPREP_SUPPORT
• tds.setSIP_SUPPORT
143844
The JDBC Driver used to throw a NullPointerException if executeBatch was called for
an empty batch. The Teradata JDBC Driver has now been changed to throw an
SQLException with a relevant error message when the executeBatch method is called
for an empty batch.
Teradata Tools and Utilities Release Definition
91
Chapter 2: Product Information
Teradata Manager
Teradata Manager
Teradata Manager is a PC-based graphical database management platform containing a suite
of specialized tools and applications that centrally monitor and control Teradata Database.
Product Version Number
Teradata Manager 13.00.00.10
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Manager Installation Guide,
B035-2402-088A
Teradata Manager User Guide,
B035-2428-088A
Release Notes
Grant Privileges if Using Security Mechanism
When logging on to Teradata Manager using an alternate security mechanism, an error
message can display indicating the user does not have the appropriate grant privileges and
adequate permissions to use Teradata Manager.
Workaround: When a security mechanism has been set for a user, access privileges must be
manually granted by running the Teradata Manager Database Setup application or running
the setup script. For instructions on running the setup script, see the “To set up the database
using the Teradata Manager setup script” procedure in Chapter 4 of Teradata Manager User
Guide.
Workload History Report
Changing the active Teradata DWM rule set during a Teradata Manager session causes
“UNKNOWN” to appear in the Workload Names column of a Workload History report.
Workaround: Restart the Teradata Manager service to pick up the new workload names and
IDs.
92
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Manager
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 37: Teradata Manager RFCs
RFC
Description
91927
RSS collection rates can be changed on all systems, not just monitored systems.
96673
All data collection tasks can be updated after configuration or scheduling changes using
a new Refresh button on the Data Collection tab, including changes made by other
people. See Teradata Manager User Guide for details.
99762
The Database Setup application recognizes persistent errors, such as an expired
password, and quickly stops processing.
99923
Window size and position are saved upon exiting and are restored when the specific
Teradata Manager application is started again.
99925
The OK button is disabled until all fields, except the Account ID field, have been
completed in the Logon Information dialog box.
100157
In Teradata Manager, two fields were replaced with a single Node/Vproc field for
entering RSS collection rates. In Performance Monitor, two separate Vproc and Node
monitor rates were replaced with a single collection rate. For more information, see
Teradata Manager User Guide and Performance Monitor online help.
103332
The Exception Query List report was enhanced to accommodate the Abort on Select
action in Teradata DWM.
109419
A Not Idle filter was added to the Session Status report to show sessions that are in any
state except idle.
110516
Documentation Only
Teradata Manager User Guide includes a new “Teradata Manager Server Privileges”
section to assist IT personnel with granting Windows and network privileges when
installing the Teradata Manager Service.
112743
Wrap-around time can be specified in the Workload Trend reports.
114284
Backup Segs Alloc was changed to Maximum I/O Time in the Vproc Utilization Detail
report in Teradata Manager. Backup Segs Alloc was changed to Max I/O Time in
Performance Monitor.
114933
A new filter option was added to display active events or all events in the Event Status
report.
114963
Performance Monitor was enhanced so the Explain text for a session can be saved in
Unicode format.
115191
Documentation Only
Teradata Manager User Guide was updated to clarify that the Teradata Manager client
does not have to be running for the service to perform data collection.
115317
The node status light on the Teradata Manager Dashboard was changed so it turns red
only when the node is down.
Teradata Tools and Utilities Release Definition
93
Chapter 2: Product Information
Teradata Manager
Table 37: Teradata Manager RFCs (continued)
RFC
Description
115995
Teradata Manager supports the new Virtual Storage Services (VSS) vproc type.
115996
Performance Monitor supports the new VSS vproc type.
116584
The Event Status report was changed so the Active Date and Expression Date columns
are blank if the system state is currently inactive and has never been active, and the
Active Time and Expression Time columns are blank for the “Normal” System
Condition and the “Always” Operating Environment.
116611
Spool space data collection can be configured to produce alerts only for users that are
logged on. See Teradata Manager User Guide for more information.
116626
Statistics Collection displays partition information.
116928
In email alerts, the Actual Value field no longer appears for an AlertRequest or
MonitorRequest having null EventValue.
In Run a Program actions, the Actual Value field is blank for an AlertRequest or
MonitorRequest having null EventValue.
In the AlertRequest table, the Value column was renamed Event Value. If the value is
unknown or cannot be represented as a single numeric value, this column is null.
117037
The back and forward navigation buttons were changed to previous and next.
117526
Teradata Manager displays context-sensitive help when using Internet Explorer 7.0 as
the default browser
117932
SQL Assistant .Net was added to the Administer menu.
119036
The Session Detail report was enhanced to display the next session and the previous
session in the same order as in the Session Status report.
120374
Documentation Only
Teradata Manager User Guide includes a new “Install and Configure Windows SNMP
Service” section on setting up the Microsoft SNMP Service to work with Teradata
Manager SNMP traps.
121515
Teradata Performance Monitor was enhanced so SQL can be retrieved from sessions in
an aborting state.
124983
Teradata Manager applications support the no PI tables feature (TableKind = ‘O’),
which will be available with Teradata Database 13.00 or later.
130052
A limited features version of Teradata Manager added to support 1550/2500/2550
systems.
145809
The TMGR 13.0 installer is now a Basic MSI package.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
94
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Manager
Table 38: Teradata Manager DRs
DR
Description
101350
The Locking Logger Report generated by Teradata Manager was recording incorrect
data for session row, userid, account, and logonsource. This was occurring because
there are multiple logon rows in dbc.eventlog for the same session number value (session
numbers are reused). In particular, the activities of the arcmain user were identified as
an “unknown” user. This misidentification no longer occurs.
105755
When an alternate logon ID and password were used while configuring a heartbeat
query from a remote Teradata Manager client PC, the Teradata Manager service
stopped. Teradata Manager was modified to prevent the error, and additional
instructions were added to the Teradata Manager User Guide.
105841
Due to an inability to detect hung logon procedures properly, Teradata Manager
7.0.0.11 stops sending alerts without any apparent errors, and a Policy Refresh Failed
event is logged. A code fix enables Teradata Manager to detect hung DBS logon
attempts and log an appropriate error.
110525
Launching Teradata Performance Monitor (PMon) caused a hung state if any
connected database was offline. This problem no longer occurs.
114010
One of the five types of utilities in the Object Utility Statistics report incorrectly showed
All Utilities, instead of FastLoad + MultiLoad. Teradata Manager was modified, and the
Teradata Manager User Guide was updated.
115612
When the error “Internal Error: Inconsistent Monitor software condition detected.”
occurred, it caused a Teradata Database restart. This error was caused when retrieving
the list of workload definitions from an earlier Teradata DBS that did not support
workload features. This error no longer occurs.
115669
Teradata Manager includes a new Utility Delay Queue List report that shows all
requests in the utility delay queue. See Teradata Manager User Guide for details.
115990
Previously, Teradata Manager could not launch any Apply alert policies that were set to
be executed by the Scheduler. The alert policies now launch properly.
116113
Previously, you could not schedule statistics collection using Teradata Statistics Wizard
with ODBC. An Add schedule operation successful message displayed,
but the dbcmngr scheduling tables were empty, and the Teradata Statistics Wizard log
file contained ODBC errors. Teradata Manager was modified and these error no longer
occur.
116144
Error Log Analyzer stopped responding when more than 200 characters were entered
while creating a new category. Error Log Analyzer was modified so the maximum length
of 30 characters can be entered for a new category, and clarification was added to the
online help.
116456
When Teradata Manager Service was stopped, port 1515 was not released when
scheduled tasks were running. This issue was resolved.
117084
Documentation Only
Teradata Manager User Guide and Performance Monitor online help were updated to
explain what zero means when it appears in the RunVProcNumber field in the Session
Detail report in Teradata Manager and in the RunVProc field in Performance Monitor.
Teradata Tools and Utilities Release Definition
95
Chapter 2: Product Information
Teradata Manager
Table 38: Teradata Manager DRs (continued)
DR
Description
117173
Previously, the Dashboard did not show movement for PE and AMP in the dial and
chart for Virtual Utilization. Teradata Manager was modified and those errors no
longer occur.
117186
Documentation Only
A description of how the Sort by Workload feature works when Teradata ASM
workload categories are enabled or disabled was added to the Performance Monitor
online help.
117227
The Hierarchy report could not be saved in the intended directory. Teradata Manager
was modified and this error no longer occur.
117626
Teradata Manager scheduler displayed a misleading error when a user attempted to
make a change to an object for which they did not hold the required access rights.
Teradata Manager was modified so the correct error code displays.
118115
Previously, an error message displayed after a Teradata Manager client had been
running for several hours. Then, the Teradata Manager Client application would stop
responding after the message was acknowledged. This problem occurred multiple times
per day.
Although there was adequate error checking and recovery to allow the processes to
continue, communication to and from the service was paused when the error message
displayed, and eventually could not be restored.
Teradata Manager was modified to suppress this extraneous error message, which was
intended as a debug tool, and this error no longer occurs.
96
118163
Previously, the Session Information application could not be accessed in client-mode
for user IDs without monitor privileges. Teradata Manager was modified to recognize
the privilege error and prompt the user to connect via the service, if one is available, or
exit Session Information.
118169
Performance Monitor was modified to allow a password to be pasted. Instructions on
using the Backspace key and not the arrow keys or mouse to position the cursor in
the Password field were added to the Performance Monitor online help.
118272
When connecting Teradata Manager 12 client to Teradata Manager 7.2 server, a
misleading Invalid password error message was received. This issue was resolved.
118564
Teradata Database stopped responding while AmpUsage data was being collected. In
addition, AmpUsage data stopped collecting after Teradata Database was restarted. This
issue was resolved.
118825
The Sessions column in Vproc Utilization report was misleading. The Sessions
column was renamed Session Log in the Vproc Utilization report to more accurately
describe the content, and Teradata Manager User Guide was updated.
119222
Teradata Manager stopped responding while attempting to view a DBQL Step Usage
report. This issue was resolved.
119400
In the Space by Database report, the Skew% field displayed negative values when the
database has no tables in it. Teradata Manager was modified so the correct value
displays, and Teradata Manager User Guide was updated.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Manager
Table 38: Teradata Manager DRs (continued)
DR
Description
119418
Documentation Only
Context-sensitive help was not working in some Performance Monitor dialog boxes.
The context-sensitive help has been fixed.
119899
After adding a category set in Error Log Analyzer, the first digit of the error code did not
display when the Modify Category Set dialog box was closed and then reopened. This
issue was resolved.
119921
Teradata Manager aborted all idle sessions chosen for display, even sessions belonging
to the host group that is subject to local filter (before the filter has actually been set). A
code fix prevents this from occurring.
120101
When attempting to log on using the KANJISJIS_0S character set, Teradata
Performance Monitor stopped responding. This issue was resolved.
120285
The logic for the Event Status Record Type Detail report was changed to match the
selected filter type. Teradata Manager was modified, and Teradata Manager User Guide
was updated.
120296
When the logged on user name contained double quotes, moving space operations
failed. Creating a user name with double quotes may cause errors because the database
uses double quotes for object names. Teradata Manager User Guide was updated with
this limitation.
120426
Context-sensitive help was missing from the Session Information dialog boxes. The
Session Information application was modified, and the context-sensitive help was fixed.
120446
An incorrect topic displayed for Physical Resource Usage in Performance Monitor
online help. Performance Monitor was modified, and the correct topic now displays in
the online help.
120569
Database Setup can be used to configure a new tdwm 13, upgrade from tdwm 12 to
tdwm 13, or upgrade from tdwm 6.x to tdwm 13. See Teradata Manager User Guide for
instructions.
120734
Teradata Manager stopped responding when creating a Blocked report. This issue was
resolved.
121069
The contents of multiple Resource Usage Trend reports were incorrect. These issues
were resolved.
121085
Delta CPU displayed as whole numbers in the Session Status report leading users to
believe the numbers were incorrect although the numbers were correct. This issue was
resolved by displaying CPU seconds with two decimal places.
121246
Documentation Only
Teradata Manager User Guide includes a “Limitations” section that documents multiple
long-term product limitations.
121659
CPU usage percentages incorrectly reported as zero in the Resource Usage Trend
reports. This issue was resolved.
121855
When multiple reports were open, Teradata Manager stopped responding after 15
minutes. This issue was resolved.
Teradata Tools and Utilities Release Definition
97
Chapter 2: Product Information
Teradata Manager
Table 38: Teradata Manager DRs (continued)
98
DR
Description
121900
When other profiles existed and were enabled, Database Setup did not recreate the
DEFAULT profile, which had been previously deleted. This issue was resolved.
122074
CPU Skew incorrectly displayed a single digit in the Session Status report even though
all digits correctly appeared in the Session Detail report. This issue was resolved.
122408
Teradata Manager Service stopped responding and terminated unexpectedly during a
regularly scheduled network security scan. This issue was resolved.
123399
Multiple Space Usage reports failed with a dbc.diskspacev does not exist
error message. This issue was resolved.
123594
When logging on using the KANJISJIS_0S character set, the Alert Policy Editor
application stopped responding. This issue was resolved.
123735
No rows returned when the Space by Vproc report was displayed for a Japanese table.
This issue was resolved.
123847
In the Japanese version of Locking Logger, extra spaces appeared between the database
name and table name in the Create Table dialog box, and an error displayed indicating
the database name did not exist. This issue was resolved.
123930
A numeric overflow error occurred when the Workload Definition Query List displayed
which resulted in an empty report. This issue was resolved.
124054
The workload name was incorrectly truncated with single characters such as “W” and
“T” after using the Append Command to Batch File command. This issue was resolved.
124113
Teradata Manager stopped responding when another application window overlaid a
graph, and then the Zoom In control was used in the graph. This issue was resolved.
124133
The LogOnOff Usage application failed to launch and displayed an error message when
the security mechanism was enabled using the UTF16 character set. This issue was
resolved.
124154
Teradata Manager failed to add a new Teradata Database when the username and
password were left empty and the security mechanism was enabled. This issue was
resolved.
124433
The Preview window unexpectedly closed when a Monitor report was opened as a graph
and viewed in Print Preview mode. This issue was resolved.
124435
When printing reports, complete column headers do not print properly. A Print
Preview can cause the client to crash. A code fix was implemented.
124655
Previously, Teradata Manager failed when executing an APPEND to a batch file due to
new security restrictions on Windows Vista systems. This problem no longer occurs.
124818
Modifications to session accounts could not be made as expected through Session
Information because the Server > Modify Account button is always greyed out. The
button is now always available.
124819
Teradata Manager Database Setup only allows the use of the limited 7-bit ASCII
characters (a-z, A-Z, 0-9, $, #, and _) for the super user name.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Manager
Table 38: Teradata Manager DRs (continued)
DR
Description
124901
The Table Growth report contained negative values in three columns for tables
containing large quantities of rows and data. This issue was resolved.
125670
When Teradata Manager is connected as a service, the historical report Analyze >
Resource History > NODE CPU > NodeCpuAverageUse fails with an error that the report
already exists. The duplication that caused the error is now resolved.
125927
Performance Monitor failed to display the SQL for large, complex queries. The buffer
size was increased so the problem no longer occurs.
126157
Teradata Manager and Session Information failed to display the full contents for queries
over 32K in Performance Monitor. Due to a Unicode conversion issue with double-byte
characters, modifications were made to the buffer address to resolve the problem.
126841
Running the Priority Scheduler System or node data collection tasks sometimes caused
a “secondary index uniqueness” error. The duplication no longer occurs.
126841
In Direct to DBS mode, dbcmanager sessions were left open after running tdclient.exe
at the command line. This problem no longer occurs.
127181
In Direct to DBS mode, Teradata Manager failed to log off monitor sessions after the
tdclient.exe command was run at the command prompt. Sessions now terminate
properly.
127533
tdwm migrations failed with the syntax error: Missing/Invalid SQL
statement'E(5315):An owner referenced by user does not have SELECT access to
dbcmngr.Migration_Tablecolumns.Database_name.'. This was caused by single
apostrophes in the description field of rules in a ruleset. The code fix replaces the
apostrophes with double apostrophes for insertion into a SQL command.
127766
The Object Type of throttled Profiles were being displayed in Object Query Statistics as
query bands, while query bands could not be defined. This problem no longer occurs.
128949
Database Setup fails to create all required macros when the NOPI Feature is disabled on
the DBS side. Changes to the dbssetup.exe application and to the dbssetup.scr and
dbsupgrd.scr scripts fixed the problem.
130027
The Monitor > Sessions > Not Idle menu item displayed even though the Sessions View
checkbox of the Teradata Manager Profile was cleared. The problem no longer occurs.
130275
After the upgrade from 7.2.x to 12.0.0.5, an attempt to apply the APE ruleset to the
database results in the 3817 error. This is because the Teradata Manager dbsupgrd.scr
script did not update the dbcmngr.InsAlertSystem macro definition properly. The code
fix corrects this problem.
130420
The database setup routine failed without being captured in the dbssetup log file. This
problem no longer occurs.
130452
After migration to Teradata Manager and Database 12.00, the Priority Scheduler
settings for the non-BASE state were not visible. A change in the migration code fixes
the problem.
130536
After upgrading Teradata Manager, the dbsetup failed. To correct the problem, default
OS settings and dbstype settings were modified.
Teradata Tools and Utilities Release Definition
99
Chapter 2: Product Information
Teradata Manager
Table 38: Teradata Manager DRs (continued)
100
DR
Description
130605
Teradata Manager did not allow the log on procedure with LDAP to run successfully if
the user invoked Alert Policy Editor. Code was modified to enable the log on procedure
to function properly.
130653
The database setup routine failed to define a primary key for the TDWMLock table,
which resulted in getting a TableKind of "O" meaning NO PI (no primary index). This
problem no longer occurs.
130696
The OK button on the Teradata Manager Login dialog wasn’t enabled unless focus
changed from the Profile list box to some other control. The button is now properly
enabled.
130910
The DBC userid was being locked out after failed logons from the Teradata Manager
service when Alert Viewer is started. A code change to Alert Viewer and MonPM API
resolved the issue.
131816
During migration from Teradata Database 12.00 to 13.00, the Database Setup
application does not complete successfully due to an error involving Unicode migration
if the Migration_TableColumns table already exists. A code change corrects the
problem.
132826
When the ruleset is migrated from 6.2 to 12.0, an exception is created for each
exception action defined for each period of the workload. A database crash can occur.
The code fix ensures that there is only one exception for each workload.
133214
tdwm migration fails due to two parameterized GRANT statements that do not have
required double quotes in the database setup code. This error has been corrected.
133418
During the migration from version 6.2 to 13.0, the Database Setup never completes, but
instead becomes caught in a loop displaying a DDL for creation of the Unicode
migration stored procedure in the application window. A correction to the code fixes
the problem.
133487
When the DBC password includes a special character, dbssetup can fail. The code fix
resolves the issue by enclosing passwords in double quotes.
133767
DCTASK400 does not complete due to heavy skewing on
databasespace.currentspoolspace. A code fix enhances DCTASK400 to prevent excessive
skewing.
134338
An error occurs when migrating a ruleset if more than one non-default period are
defined for the same configId. A change to the code prevents the error.
134931
Teradata Manager Monitor/Vprocs AMP worker tasks always display as zero in Direct
Mode. A code fix resolves this problem.
135655
After an upgrade to Teradata Manager 12.00, a Session Filter change in both Direct and
CLient mode takes extended time to update the session screen. A code fix removes
SetReDraw (FALSE) and so resolves the problem.
136697
After upgrade to Teradata Manager 12.00, scheduled commands no long run if the total
command line is greater than 128 characters. A code fix bypasses this limit.
139818
The TDWM GUI truncates the QB name and value to 30 characters when writing to the
database. Code was changed to prevent this from happening.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Meta Data Services
Table 38: Teradata Manager DRs (continued)
DR
Description
140200
The TMGR client was failing to connect to server on IPv6-enabled machine in Window
7. A code change fixes the problem.
141661
Teradata Manager installation errors were occurring on Windows 7, Vista, and 2008
when the installer was run in non-administrator mode. The code fix explicitly sets the
Required Execution Level option on setup.exe to Administrator.
142095
The Teradata Manager service fails to log on to the DBS with LDAP when Tdwm rule
set is activated. The issue has been resolved.
142488
After first heartbeat query 1 (dctask 500) alert is successfully sent, the row from
dbcmngr.alertrequest is not deleted, so the alert is processed and sent again and again
until the row in dbcmngr.alertrequest is manually deleted. This issue has been resolved.
144446
Fully qualified table name was not being stored correctly in tdwm.wlcclassifycriteria
column objectname if dbname.tablename > 30 characters. In addition, the 2802 error
could be returned when saving a TASM ruleset. A code fix increased the character limit
to 300.
Teradata Meta Data Services
Teradata MDS provides a repository for the Teradata warehouse. It is the only repository
optimized for Teradata.
Product Version Number
Teradata MDS 13.00.02.05
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0.x
•
Teradata Database 13.00
Documentation
Teradata Meta Data Services Installation and Administration Guide,
B035-3118-088A
Teradata Meta Data Services Programmer Guide
B035-3047-088A
Teradata Tools and Utilities Release Definition
101
Chapter 2: Product Information
Teradata Meta Data Services
Release Notes
AIMVERSION Attribute
The following documentation changes support the new aimversion attribute:
•
In the MetaXML chapter of Teradata Meta Data Services Programmer Guide, the following
DTD syntax will be added to the MODELDESC section:
!ATTLIST MODELDESC
linkid ID #IMPLIED
action (traverse | add | remove | update) #IMPLIED
transaction (no | yes) #IMPLIED
aimversion CDATA #IMPLIED
•
The following description of aimversion will also be added:
The integer value of the version of this metamodel. This is optional and will be NULL in
the repository until set by the user. When importing, if present and the current action is
add or update, the indicated value will be set for the metamodel repository object. If the
current action is traverse or remove, the value will be ignored. This value maps directly to
the AIMVersion property of the MetaAIMClass in the MDSMetamodel.
Note: Do not modify the aimversion value of any MDS-defined metamodel.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 39: Teradata MDS RFCs
RFC
Description
98597
When loading information into the Client Load Metamodel, Metaclient supports .RUN
syntax for Teradata FastLoad, and .RUN FILE syntax for Teradata MultiLoad and
Teradata TPump scripts.
Previously, the .RUN directive in an initial load script was ignored. Now, any load
utility script information from a .RUN file is scanned, parsed, and imported through
the utility just as if it were in the initial load script.
102
115346
MDS now provides views that allow an administrator to SELECT the contents of
repository tables.
115347
The Database Information Metamodel (DIM) includes the
JoinIndexesReferencesFunctions and ViewColumnReferencesFunctions relationships.
115348
A required option for all unique class properties was added to the MDS engine
(mdsbase). This option ensures the property is given a non-null value when adding or
updating a class object.
115350
Mdsbase supports inclusion and retrieval of a description for relationship object
associations.
115352
The DIM includes the TriggerReferencesTables relationship.
115354
Mdsbase supports filtering on selected columns when retrieving the objects in a class.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Meta Data Services
Table 39: Teradata MDS RFCs (continued)
RFC
Description
116689
Teradata MDS 13.00.01 supports Teradata Database 13.00.
116691
The DIM now includes the Constants and Functions classes, and the
ViewColumnReferencesFunctions relationship so that the value of constants a view
returns for a column are maintained. If a view column can return multiple constant
values, all the possible constant values will be saved in the repository.
116755
User can use MetaSurf to complete a simple compare of database objects (default) or
compare all tables and columns to identify identical tables.
116758
Metaclient supports versioning and labeling when working in a version-enabled
repository.
Previously, when the import of a previously imported script was detected, the script was
deleted from the repository before the new import was completed. Now, instead of
being replaced or overwritten, the previously imported script and all its related meta
data are version updated when the user is running with a version-enabled repository.
116770
The DDL Processor includes new TriggerCreationTimestamp and
TriggerEnableOrDisableTimestamp properties for storing the time when a trigger was
enabled or disabled.
116771
Previously, the DDL Processor allowed views to reference other unresolved objects only.
When any other object types (such as triggers) referenced unresolved objects, an error
was returned, and the affected database was marked as out of sync.
The DDL Processor now supports all object types to reference unresolved objects and
set sync level to zero.
116784
The MetaXML scripting interface and the MetaXML utility supports the export of meta
data objects out from the repository.
116876
Teradata MDS metadata exported with MetaXML can be transformed into CWM XMI
for import into CWM 1.0 XML.
116890
MDS now has a web service interface for internal use only.
117035
The COM API supports the inclusion and retrieval of a description for relationship
object associations.
117144
The DIM includes the HashIndexReferencesTableColumns,
MacroReferencesHashIndexes, and SPReferencesHashIndexes relationships.
117169
The descriptions of the DIM and Client Information Metamodel (CLM) provided by
metacreate, metamigrate, and metaclient were expanded and improved.
117170
The gateway sockets code now provides encryption and decryption. Only the message
header is left unencrypted.
117172
Teradata MetaSurf supports Internet Information Services (IIS) 7.0.
120436
Teradata MDS now supports IPv6 addresses.
121179
Teradata MDS now supports the Teradata Database no primary index (NoPI) table
feature.
Teradata Tools and Utilities Release Definition
103
Chapter 2: Product Information
Teradata Meta Data Services
Table 39: Teradata MDS RFCs (continued)
RFC
Description
121906
Documentation Only
Teradata MDS is no longer supported on MP-RAS. Related information was removed
from Teradata Meta Data Services Installation and Administration Guide.
125213
Metaload now sets the IsRecursive property for DIM views for both initial loads and
resync loads to evaluation whether the views are recursive.
126286
The MDS MetaBridge interface has been extended to support import any metadata
information exported out of the ERWin tool.
127062
The AIMVersion property has been added to MetaAIM class. This property has been
introduced to aid the recognition of the current state of an AIM. By using this property,
the program that maintains the AIM can determine what properties and relationships
already exist in the AIM.
127104
MetaBridge support to include Informatica has been added.
116221
Metaload can be used to restrict the types of data to be loaded by metaload, which
eliminates storing unneeded data in the repository. The DIM includes the
MetaLoadType class and the SystemHasMetaLoadTypes relationship. New dialog boxes
were also added to MetaManager. See Teradata Meta Data Services Installation and
Administration Guide for more information.
117756
117039
117040
117030
117031
The COM API and the Java API support filtering on selected columns when retrieving
the objects in a class.
A required option for all unique class properties was added to the COM API, the Java
API, and the MetaXML API to ensure that the property is given a non-null value when
adding or updating a class object.
117032
115349
117025
The Teradata MDS engine (mdsbase), the COM API, the Java API, and the MetaXML
API allow a Meta Model designer to force objects created in certain classes to have a
Description supplied for them.
117026
117028
115917
116751
116754
126286
Metabridge can be used to import Object Management Group (OMG), Common
Warehouse Metamodel (CWM), and XML Metadata Interchange (XMI) formatted
metadata into the CWM metamodel in the MDS repository. The metadata can be
generated from the following sources:
•
•
•
•
Business Objects Data Integrator 11.52
CA ERwin Datamodeler 7.2
Cognos Framework Manager 8.2
SAS Data Integration Studio 9.13
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
104
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Meta Data Services
Table 40: Teradata MDS DRs
DR
Description
118373
The SignOff call was modified to optionally indicate the specific MDS user to sign off
the repository. This is needed when the original IMetaActive interface object is not
around or in multi-user/multi threaded applications.
125213
The following property has been added to the DIM View class:
Name:
IsRecursive
Description: Indicates if the view is a recursive view, i.e.,
SELECTs from itself.
The values are Y=Yes and N=No.
Property ID: PID_VIEW_ISRECURSIVE
Type: String
Size: 1
This property will be set by metaload and DIM Update when they process a view. When
an existing database in the DIM is being processed by metaload, it will automatically
reevaluate any view that has a NULL value for the property.
126136
MDS DIM Update not fully functional on Linux Kanji system and experienced
numerous problems. The code fix implemented a wide variety of corrections.
126206
When metaload attempts to create the system object and fails due to the repository
database being full, metaload tries to increase the size of the database. Unfortunately,
metaload tries to do that with connection pointers that have not been set up. Metaload
returns a segmentation violation and aborts without displaying any error status.
Metaload has been modified to acquire the connections to the repository before
querying the system object.
126616
MetaSurf was not displaying full names for new Period Data types codes. MetaSurf has
been modified to do this.
127123
The MDS parser now accepts 0x8d 0x8d as a substitute for the 0x7c 0x7c (||)
concatenation operator in order to avoid hangs.
127377
The MDS parser didn’t correctly handle stored procedure calls that contain database
names. This problem no longer occurs.
127391
IMetaActive.GetClassObjectKeys returned frozen objects along with the expected nonfrozen objects. This problem no longer occurs.
128095
Metaload update of a text field in repository entry fails with
META_E_DBACCESS_ERROR. The MDS log indicates that a character failed Unicode
conversion. The code fix changes the MDS engine to ensure that when running in
Unicode mode, Unicode data is always fetched as Unicode data. Not all places in the
engine were properly requesting Unicode fetches.
128343
Metaload hangs after parent process fails with an Unknown Exception because of a
problem in the CMetaLoad::LoadDBSchema routine. The code fix modifies
LoadDBSchema.
Teradata Tools and Utilities Release Definition
105
Chapter 2: Product Information
Teradata Meta Data Services
Table 40: Teradata MDS DRs (continued)
DR
Description
128533
Several MDS parser defects have been occurring:
• The parser returns an Unknown Exception error when it parses SQL contains both a
derived table and a syntax error.
• The parser incorrectly picks up 'AS Locator' instead of 'AS Locator_Id'.
• The parser can return an Unknown Exception error when handling the
current_time(n) and current_timestamp(n) built-ins.
• The MDS Unicode parser truncates the original SQL before logging syntax errors.
Also, part of the syntax error message is still in ANSI, so it does not print correctly.
The code fix resolves all of these issues.
128598
127062
MDS provided no way to set aim-version when metamodel was created, and no simple
way to update it later. A new aimversion attribute was added to the MODELDESC
element to map to the metaaim table AIMVersion property (column).
128702
Class-name and property-name for collection items are no longer case-sensitive.
128821
The MDS parser sometimes returns an Unknown Exception while parsing a stored
procedure that contains a standalone LOCK statement. A standalone LOCK statement
is terminated with a semi-colon, and is not combined with another SQL statement. For
example:
-- get write lock for input_file
LOCK TABLE P_CONTROL.input_file FOR WRITE;
The code fix lets the MDS parser handle standalone LOCK statements correctly.
106
130136
In Metaload AuthenticateUser fails with META_E_DATABASE_FULL error. The code
fix changed metaload to request an increase in the repository size when this occurs.
130864
Because of inefficient code, MetaBrowse can take a significantly long time to display the
list of subclasses available to a class. CMetaStorage::SGetSubClassList was changed to
use CMetaClassCache::GetClassNames instead of issuing one SQL per class.
CMetaClassCache::GetClassNames was added to get the names of a set of classes, either
from cached info or by issuing one SQL for all of the class loids.
131149
Chinese characters are not displayed correctly after a migration of the repository from
6.2 to 12.0.1 because of an error in the way metamigrate transforms data. A code fix to
metamigrate prevents the problem, but can cause a performance degradation.
132289
Due to a bug in the ASP definition, the 006~ASP 0251~Response Buffer Limit
Exceeded~Execution error is displayed for any impact analysis of a table with a large
number of columns and views associated with those columns. The code fix updates the
tblanalysis.asp script to be more efficient.
132798
GetCollectionObjects was returning duplicate relationship names. SGetCollection has
now been changed to request SGetCollectionClass to check for duplicate entries when
calling it for the superclasses and the relationship is ClassHasRelationships. The various
routines that add objects or keys to the return lists now make the check for a duplicate
entry before adding an entry to the return list.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Meta Data Services
Table 40: Teradata MDS DRs (continued)
DR
Description
133331
The gateway sockets code has a routine named GetLastError that conflicts with a
Windows routine of the same name. This conflict caused the RSG and MDS Gateway
processes to reset connections and restart their handshakes continually. The code fix
renames GetLastErrror to GetLastErrorCode to avoid the conflict.
133343
MDS metaload does not reevaluate views when a table is renamed. The view is not
properly resynced so that metaload still indicates that the view references the table’s
original name. The code fix forces metaload to reevaluate the references.
133615
The MDS parser returns an access violation or exception while parsing a stored
procedure with COLLECT STATISTICS statement. The issue has been resolved.
134435
The DDL Processor has problems finding the definitions when views have forward
references. The code fix prevents these problems.
136856
Some stored procedures fail to parse since the MDS parser does not expect anything
other than spaces between the END keyword and the IF keyword. The stored
procedures contain tabs between the END and the IF. The MDS parser was changed to
allow all forms of white space, not just blanks, between END and IF keywords. Also, the
MDS parser now allows extra parentheses inside derived table definitions.
138273
Gateway sockets incorrectly map the external EAI_SERVICE error code to an
insufficient memory error. The code fix changes GetServiceAddress to log the service
name when getaddrinfo returns an error; and fixes ConvertIPv6ErrorToErrno to return
the correct value for EAI_SERVICE.
139949
The MDS DDL processor returned a seg fault while processing an unresolved column in
a CASE statement in a stored procedure. The code fix resolves the issue.
142106
Migrating a 12.0.0 repository fails with the status
META_E_COLUMN_DOES_NOT_EXIST. The code fix enables metamigrate to
handle a 12.0.0 migration properly.
143076
The load of a database terminates with the error META_E_NO_SPL_TEXT. The MDS
log shows that the error was returned by CreateColSqlStr, which generates the SQL for
adding a table column definition to the DIM. The code fix changes CreateColSqlStr to
ignore any errors from processing the identity column.
143395
Metaload fails with META_E_DDL_PARSING_FAILED while resyncing a database.
The MDS log shows that an SQL failed because 'CHECK_BOOL=' is followed by a
comma and not by a quote mark. The code fix changes CompareCheckRows to pass a
NULL_STRING instead of the current prefixStr to SetData2 for any entries that already
have the columnname= placed in the SQL string. This ensures that the equal sign is not
followed by a comma.
144226
Metamigrate tries to do duplicate Unicode conversions for DIM tables and terminates
with META_E_DBACCESS_ERROR. The MDS log indicates that Teradata returned an
'Untranslatable character' error message. The code fix provides better tracking of which
tables and columns within the tables have been converted to Unicode. To do this,
metamigrate now adds a column to the metaroot table to give the name of the last
column that was successfully converted. Combined with the progress indicators, this
enables metamigrate to skip the columns that have already been converted.
Teradata Tools and Utilities Release Definition
107
Chapter 2: Product Information
Teradata MultiLoad
Table 40: Teradata MDS DRs (continued)
DR
Description
144610
Teradata crashes when CGwySockets::Close in the RSG vproc tries to use a null pointer
(this=0x0). The code fix changes all member functions to check for this null pointer.
145659
Metaload aborts with the status META_E_NO_SPL_TEXT. The MDS Log file indicates
that Metaload was attempting to determine the ID column definition for a table. The
code fix makes Metaload ignore the META_E_NO_SPL_TEXT status.
146167
The Metaload DDL parser returns 'empty statement' when terminating semicolon is on
same line as an ANSI comment. The issue has been resolved.
Teradata MultiLoad
Teradata MultiLoad is a command-driven utility that allows fast, high-volume maintenance
on multiple tables and views of Teradata Database.
Product Version Number
Teradata MultiLoad 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata MultiLoad Reference,
B035-2409-088A
Release Notes
Documentation Updates
Minor, last-minute changes were added to Teradata MultiLoad Reference. An updated version
is available at http://www.info.teradata.com/.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
108
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata MultiLoad
Table 41: Teradata MultiLoad RFCs
RFC
Description
93368
On Microsoft Windows operating systems, PUT can be used to install Teradata
MultiLoad.
93534
Teradata MultiLoad passes .logdata in UTF16 character sets for extended security.
110172
Teradata MultiLoad allows the ACCEPT or SET commands prior to using a LOGON or
LOGTABLE command.
117574
113012
Teradata MultiLoad supports the new Teradata Database 13.00 PERIOD data types. A
PERIOD data type has two values that represent the start and end of the period.
113493
Documentation Only
Usage notes for specifying DECIMAL data types were enhanced in Teradata MultiLoad
Reference.
113816
The Teradata MultiLoad configuration file includes an AMPCHECK entry. For details,
see Teradata MultiLoad Reference.
100763
115847
Teradata MultiLoad 13.00.01 is compiled with Microsoft Visual Studio 2008 and
requires the new Visual Studio runtime libraries. The Teradata MultiLoad installation
package includes the Microsoft Visual C++ (x86) 8.0 merge module, which is required
to run Teradata Tools and Utilities 13.00.01 applications.
115943
Documentation Only
Information regarding UDTs and UDMs was added to Teradata MultiLoad Reference.
116012
Teradata MultiLoad no longer directly links to Teradata ICU, and Teradata MultiLoad
no longer needs to be recompiled and re-linked when Teradata ICU is updated.
121177
Teradata MultiLoad no longer fails when creating tables including strings with double
quotes.
123961
The DeleteInit event did not require any data to be sent to the notify exit routine, which
caused problems for Teradata Multi-System Manager. The DeleteInit event now sends
the same data as the Initialize event.
142190
For Windows platforms, the Teradata MultiLoad installation package is now MSI. This
enables silent installs via CLI, easier distribution across large user bases, easier
customized installs, as well as restoration to the pre-install state in case of a failed install.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 42: Teradata MultiLoad DRs
DR
Description
55595
Teradata MultiLoad correctly processes a SIGINT signal on Microsoft Windows
operating systems.
Teradata Tools and Utilities Release Definition
109
Chapter 2: Product Information
Teradata Parallel Data Pump
Table 42: Teradata MultiLoad DRs (continued)
DR
Description
110197
Certain error codes were remapped so Teradata MultiLoad correctly ceases operation
when it encounters a severe error from Teradata CLIv2.
114106
Teradata MultiLoad correctly processes Unicode data xx1A characters, such as
(U+4F1A) and (U+511A).
114114
Documentation Only
A semicolon cannot be used in an object name because a semicolon designates the end
of a Teradata MultiLoad command. See Teradata MultiLoad Reference for details.
121053
Documentation Only
The ANSI/SQL DateTime Specifications were increased by 1 byte. See the FIELD
command in Teradata MultiLoad Reference for details.
127941
A new IGNORECONFIGERRORS option allows a job to continue even though the
configuration file contains syntax errors.
131133
Teradata MultiLoad jobs terminated because they failed to translate data in the NULLIF
field from internal character set to session character set. The problem no longer occurs.
133739
After receiving a 2633 error using the UTF-16 character set, the Teradata MultiLoad
retry failed with a 6705 error. This was fixed.
134151
When a ROUTE MESSAGES...WITH ECHO command exists in the script and input or
output errors occur, Teradata MultiLoad no longer exits with error code 16. It returns
an error code on the remaining available message destination and does not terminate. If
no other message destination is available, Teradata MultiLoad terminates with an error
code of 16.
134587
Teradata MultiLoad now logs I/O error codes into an available message destination so
that the error codes appear and Teradata MultiLoad does not terminate.
135236
MultiLoad now sends user specified QUERYBAND commands on a second SQL
session.
138887
Verify that the user entered installation path is not read-only when installing Teradata
MultiLoad on Solaris operating systems.
140369
Install the Teradata MultiLoad package on Windows operating systems with
administrator privileges.
142842
On the HP-UX platform, running certain scripts resulted in an inaccurate 3604 error
message. This problem has been resolved.
Teradata Parallel Data Pump
Teradata TPump is a data-loading utility that helps maintain the data in Teradata Database
using update, delete, insert, and automatic upsert functions. Teradata TPump maintains near
real-time data in a data warehouse when systems are too busy to devote a designated batch
window to upload data.
110
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Parallel Data Pump
Product Version Number
Teradata TPump 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Parallel Data Pump Reference,
B035-3021-088A
Release Notes
CASE Statement Restriction
Currently, Teradata PT does not support the CASE statement with a CASE WHEN
<condition> THEN NULL ELSE <expression>. Using NULL after a THEN may return
incorrect results or an error.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 43: Teradata TPump RFCs
RFC
Description
93535
Teradata TPump passes .logdata in UTF16 character sets for extended security.
110172
Teradata TPump allows the ACCEPT or SET commands prior to using a LOGON or
LOGTABLE command.
117574
113013
Teradata TPump supports the new Teradata Database 13.00 PERIOD data types. A
PERIOD data type has two values that represent the start and end of the period.
113494
Documentation Only
Usage notes for specifying DECIMAL data types were enhanced in Teradata Parallel
Data Pump Reference.
100764
115848
Teradata TPump 13.00.01 is compiled with Microsoft Visual Studio 2008 and requires
the new Visual Studio runtime libraries. The Teradata TPump installation package
includes the Microsoft Visual C++ (x86) 8.0 merge module, which is required to run
Teradata Tools and Utilities 13.00.01 applications.
Teradata Tools and Utilities Release Definition
111
Chapter 2: Product Information
Teradata Parallel Data Pump
Table 43: Teradata TPump RFCs (continued)
RFC
Description
115943
Documentation Only
Information regarding UDTs and UDMs was added to Teradata Parallel Data Pump
Reference.
116017
Teradata TPump no longer directly links to Teradata ICU, and Teradata TPump no
longer needs to be recompiled and re-linked when Teradata ICU is updated.
117603
Teradata TPump issues a warning about possible restart failure when a checkpoint is
specified as zero. For more information, see Teradata Parallel Data Pump Reference.
119469
Documentation Only
Warnings about statement check phase behavior were added to the “Teradata TPump
Early Error Detection” section in Teradata Parallel Data Pump Reference.
121177
TPump now supports double quoted strings in TPump commands.
124845
The pack factor limit has been raised from 600 to 2430 to improve performance.
132535
TPump now sends the requested buffer size to PIOM on all platforms including z/OS.
134263
TPump now sends the checkpoint value to access modules via the SA Data Connector
so that they know whether they should checkpoint. This eliminates the need for users
to specify checkpoint values in multiple places.
142191
The TPump package on Windows has been converted to Basic MSI.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 44: Teradata TPump DRs
112
DR
Description
99207
Teradata TPump correctly handles unformatted data with variable-length characters in
indicator-mode.
107071
When an error occurs that causes a Teradata TPump job to terminate, Teradata TPump
waits for all outstanding requests to be complete, before ending the session.
107320
Teradata TPump correctly handles Teradata CLIv2 return codes.
108088
Previously, Teradata TPump core dumped when attempting to import a record with a
size greater than 64,000 KB. Now, Teradata TPump returns an error message.
112083
When using the Array Support option in a DML command, Teradata TPump no longer
limits the pack factor to what will fit in a data parcel. Now the pack factor is limited to
how many data parcels can fit in the request buffer.
112243
Teradata TPump accepts quoted table name lengths greater than 29 bytes.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Parallel Data Pump
Table 44: Teradata TPump DRs (continued)
DR
Description
114106
Teradata TPump correctly processes Unicode data xx1A characters, such as (U+4F1A)
and (U+511A).
114114
Documentation Only
A semicolon cannot be used in an object name because a semicolon designates the end
of a Teradata TPump command. See Teradata Parallel Data Pump Reference for details.
115921
Documentation Only
The caution statement in the ERRORTABLE description was updated in Teradata
Parallel Data Pump Reference.
116765
Previously, Teradata TPump jobs failed with Error 3577 when a large packing factor was
specified. Now, Teradata TPump returns to a successful packing factor and continues
the job.
117602
Teradata TPump issues a warning about possible restart failure when a checkpoint is
specified as zero. For more information, see Teradata Parallel Data Pump Reference.
119438
Teradata TPump stopped responding while loading Unicode data from a UTF8 session
with multibyte character set user-id, password, and Teradata Database. Teradata
TPump now adjusts the packing factor if Teradata Database returns Error 3702 during a
test of the packing factor phase.
119504
Teradata TPump no longer skips one input record when the error limit is exceeded and
the job is restarted.
120753
Teradata TPump error messages were updated to reflect the correct product name and
application violation.
121570
Teradata TPump no longer returns a Teradata Database syntax error when a high pack
factor is specified.
123717
Teradata TPump now logs the data-related error codes 6996 and 9102 in the Teradata
TPump error table and continues to process the Teradata TPump job.
126022
Teradata TPump now forces the character set when building its macros.
130618
In Teradata TPump, scripts that used the .TABLE <table name> command caused a
core dump if the target table was a no primary index (NoPI) table. This problem no
longer occurs.
132734
Teradata TPump no longer displays a CLIV2 warning message (The <cliv2130>
package "Teradata CLIV2 Package" is a prerequisite package and should be installed.)
when CLIV2 is already installed.
134903
If the "BEGIN LOAD" command includes "NOTIFY MEDIUM/HIGH/ULTRA MSG,"
Teradata TPump now sends a message to notify events through the tldnotfy() module.
136105
Teradata TPump no longer calls the pmShutDown() function when it terminates with
an error.
138888
Teradata TPump installation mounting errors on Solaris were resolved.
140370
Teradata TPump installation "Error 1720" on Windows 7, Vista, and 2008 was corrected
when run as a non-administrator.
Teradata Tools and Utilities Release Definition
113
Chapter 2: Product Information
Teradata Parallel Transporter
Teradata Parallel Transporter
Teradata PT is an object-oriented client suite that executes multiple instances of data
extracting, loading, and updating functions in a scalable, high-speed, parallel-processing
environment. Teradata PT parallel extract and load capabilities can be extended with
third-party products or customizations.
Teradata PT API is a set of application programming interfaces used to load and export data
to and from Teradata Database systems.
Product Version Number
Teradata PT 13.00
Teradata PT API 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Parallel Transporter Operator Programmer Guide
B035-2435-088A
Teradata Parallel Transporter Reference
B035-2436-088A
Teradata Parallel Transporter User Guide
B035-2445-088A
Teradata Parallel Transporter Application Programming Interface Programmer Guide
B035-2516-088A
Release Notes
Documentation Updates
Teradata Parallel Transporter Operator Programmer Guide and Teradata Parallel Transporter
User Guide incorrectly include references to NCR server and obsolete NCR copyrights.
Corrected versions of both publications are available at http://www.info.teradata.com/.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
114
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Parallel Transporter
Table 45: Teradata PT RFCs
RFC
Description
68262
Teradata PT jobs show error messages for terminated jobs on the console. Users no
longer need to look up error messages in the error log. For details, see Teradata Parallel
Transporter User Guide.
68273
All error messages are stored in the message catalog.
68943
Teradata PT Stream Operator has two new attributes:
• AppendErrorTable: specifies whether or not the Stream Operator will use the
existing error table.
• DropErrorTable: specifies whether or not the Stream Operator will drop the error
table at the end of a job.
For details, see Teradata Parallel Transporter Reference.
91547
The format of the DataConnector log is modeled on the format for the non-I/O-based
operator logs.
95580
Generic operating system output across platforms was enhanced. Output includes the
name of platform as well as node name.
100091
Access modules built for Teradata load and unload utilities also work with Teradata PT
without any recompiling or relinking.
105208
The DDL operator supports every SQL request except for statements that:
• Send data back to the DDL operator.
• Require the DDL operator to send data back to Teradata Database.
108165
Teradata PT Stream operator displays the following new DML options:
114255
• MARK EXTRA ROWS
• MARK EXTRA UPDATE ROWS
• MARK EXTRA DELETE ROWS
• IGNORE EXTRA ROWS
• IGNORE EXTRA UPDATE ROWS
• IGNORE EXTRA DELETE ROWS
For details, see Teradata Parallel Transporter Reference.
108586
With some restrictions, user credentials for external authentication logons can be
entered in either the .logdata statement or the .logon statement. Some Teradata
applications, such as ODBC, do not support use of the .logdata statement in the logon
string.
Previously, LDAP logons required that user credentials be submitted in the .logdata
statement. Now, user credentials for LDAP logons can generally be submitted in the
.logon statement, with some restrictions.
For details, see Teradata Parallel Transporter User Guide and Security Administration.
109308
On IBM z/OS, Teradata PT links routines from DB2 Release 9 Version 1. These routines
are compatible with other releases of DB2.
Teradata Tools and Utilities Release Definition
115
Chapter 2: Product Information
Teradata Parallel Transporter
Table 45: Teradata PT RFCs (continued)
RFC
Description
111278
The Stream Operator supports the TPump -m runtime option. The -m runtime option
tells TPump to keep macros that were created during the job run. These macros can be
used as predefined macros for the same job.
111626
Teradata PT supports automatic mapping of source columns to destination columns.
For details, see Teradata PT Wizard Help in Teradata Parallel Transporter User Guide.
111930
The following 32-bit and 64-bit Teradata PT and PT API components are supported on
Sun Solaris 10 with Solaris Zones:
•
•
•
•
•
•
•
112981
115618
PT API
PT Export Operator
PT ICU Library
PT Load Operator
PT Operator Support Library
PT Stream Operator
PT Update Operator
Teradata PT supports the new Teradata Database 13.00 PERIOD data types. For details,
see the chapter on “Object Definitions and the APPLY Statement” in Teradata Parallel
Transporter User Guide.
115624
115723
119298
113127
The following 32-bit Teradata PT components are supported on Sun Solaris 10 with
Solaris Zones:
•
•
•
•
•
•
•
PT Data Connector Operator
PT DDL Operator
PT Infrastructure
PT ODBC Operator
PT OS Command Operator
PT SQL Inserter Operator
PT SQL Selector Operator
114721
Sample Teradata PT scripts are included in Appendix A of Teradata Parallel Transporter
User Guide.
115177
The Load operator supports the following attributes:
• DropErrorTable
• DropLogTable
For details, see Teradata Parallel Transporter Reference.
116
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Parallel Transporter
Table 45: Teradata PT RFCs (continued)
RFC
Description
115178
The Update operator supports the following attributes:
• DropErrorTable
• DropLogTable
• DropWorkTable
For details, see Teradata Parallel Transporter Reference.
115530
The following Teradata PT components support LOBs loading or extracting:
115583
• DataConnector Operator
• SQL Inserter Operator
• SQL Selector Operator
The Stream Operator does not support loading LOB data.
115589
115637
119175
For details, see Teradata Parallel Transporter User Guide.
115545
Teradata PT operators are valid whether or not a Teradata PT script calls a correct
operator type. If not, the operator terminates with an error. In a Teradata PT script:
A producer operator can be one of the following:
• Export
• Selector
• ODBC
A consumer operator can be one of the following:
• Load
• Update
• SQL Inserter
• Stream
A standalone operator can be one of the following:
• DDL
• Update
• OSCommand
115588
Teradata PT supports buffer-mode exporting and loading. This allows both the
consumer and producer operators to package data in buffers that are readily
transferable to Teradata Database.
115711
Teradata ICU and Teradata PT ICU version numbers can now be obtained from
Teradata PT.
115899
Buffer-mode is supported for the SQL Selector and the Load operators. Both of these
operators now pack data into buffers before putting data into the Teradata PT data
stream instead of putting data row-by-row into the data stream.
116093
Teradata PT supports the Teradata OLE DB Access Module using the Teradata PT
DataConnector operator. For details, see Teradata Parallel Transporter Reference and
Teradata Parallel Transporter User Guide.
Teradata Tools and Utilities Release Definition
117
Chapter 2: Product Information
Teradata Parallel Transporter
Table 45: Teradata PT RFCs (continued)
RFC
Description
116439
Teradata PT supports error messages sent to the console in the following format:
<operator name>: TPTxxxxx: <message text>
where:
• <operator name> is the name given the operator in the DEFINE OPERATOR
definition.
• xxxxx is the number assigned to that error message (as placed in the message table/
catalog).
• <message text> is the text of the error message.
116605
A new -h option was added to the tbuild command for specifying the size of shared
memory to be used by Teradata PT. This option allows users to specify a memory size in
the range of 1 MB to 128 MB. This enables Teradata PT to run jobs that may require
more than 10 M of shared memory, which was the default shared memory limit in prior
versions of Teradata PT.
116703
Previously on Microsoft Windows operating systems, Teradata PT Wizard setup
automatically installed the Java Standard Edition runtime environment (JRE) 1.4.2_06
in the Teradata PT Wizard installation folder. Now, Teradata PT Wizard setup checks
the system to determine whether JRE 1.4.2_06 or higher is already installed.
If JRE 1.4.2_06 or higher is installed on the system, the Teradata PT Wizard setup uses
the JRE version on the system.
If JRE 1.4.2_06 or higher is not installed on the system, the Teradata PT Wizard setup
displays a message that JRE 1.4.2_06 or higher is required and prompts the user to
continue the installation in interactive mode.
If silent installation is used and JRE 1.4.2_06 or higher is not installed on the system,
Teradata PT Wizard setup writes a warning message to the silent install log and
completes the installation process.
118230
A new attribute was implemented that allows users to specify the number of rows to be
skipped at the beginning of each file processed before the first actual row is sent to the
data stream. This is useful for skipping bad data or header records.
118578
When the LOB length specified in the DEFINE SCHEMA statement does not match the
actual data passing into the consumer operators that support LOBs in deferred-mode,
an length error is returned.
118914
Buffer-mode is supported for the Teradata PT DataConnector operator.
119187
Teradata PT SQL Inserter operator validates LOB data file size against the LOB column
size specified in the Teradata PT schema. For details, see Teradata Parallel Transporter
User Guide.
119698
Users no longer need to look up the maximum pack factor of a Stream Operator job in
the trace file before it can be used as the pack factor in subsequent jobs with the same
schema definition.
119697
The maximum pack factor is retrieved when TD_PACKMAXIMUM is set to "Yes," and
retrieves the default pack factor when TD_PACKMAXIMUM is set to "No" (or not set
at all) from the Stream Operator.
118
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Parallel Transporter
Table 45: Teradata PT RFCs (continued)
RFC
Description
123634
The Data Connector Operator supports multiple consumer instances, with a different
output file for each instance based on the FileName attribute and the operator instance.
124643
The Data Connector Operator was streamlined to improve the processing of delimited
data.
125018
A new runtime option for tbuild allows users to redirect log files at the job level.
125313
107507
Support for 32-bit Solaris Opteron has been added.
125319
A new Data Connector Operator attribute called FileList creates a file that contains a
list of other files to be processed.
127722
If script coders use SELECT followed by a list of all of the columns in an input row,
Teradata PT handles the script as if SELECT * was used instead in order to improve
performance.
127774
The syntax requirements have been simplified. When a source and a target table (one of
which is a Teradata table) have the same schema, the declarative section of the job script
is no longer needed. For more information, see Getting Started with Teradata Data
Warehouse Appliance 255x.
128126
For the Selector Operator, the response buffer length has been increased to 1MB,
yielding a performance improvement for data retrieval processes.
128718
The Buffer mode is now supported in the ODBC Operator.
129332
A new command line option, tdload, allows users to load data easily from a delimited
flat file to a Teradata Database table. With only a server name, user name, target table
name, and data file name, Teradata PT automatically generates a script and executes the
load job. For more information, see Getting Started with Teradata Data Warehouse
Appliance 255x.
130416
Teradata PT API is allowed to checkpoint when the master instance has no rows to load
in the Load, Stream, and Update Operators.
130414
130339
132199
The EZ Loader help information and error messages have been enhanced.
132202
Support has been added to include individual column length errors.
132485
New TrimLeadingBlanks and TrimTrailingBlanks attributes allow users to remove
leading and or trailing blank characters from all VARCHAR columns when processing
delimited data.
132722
Support has been added for job variable values consisting of unquoted token strings.
This new feature expands the job variable facility to include a new class of values
(arbitrary job script token strings).
132917
Support added for a new “-C” option for cyclic data delivery.
132918
Support has been added for writing files across multiple directories or disks.
Teradata Tools and Utilities Release Definition
119
Chapter 2: Product Information
Teradata Parallel Transporter
Table 45: Teradata PT RFCs (continued)
RFC
Description
133527
Support added for a new MultipleReaders attribute. When this attribute is defined as
Yes, then a producer operator with more than one instance that is reading a single file
will process the single file using all the producer instances.
134516
Silent installation of Teradata PT API packages is available for Linux operating systems.
137744
The sample blockloading program has been enhanced to test the Stream Driver.
139830
TPT Stream Operator supports a new event that returns a list of the Stream Operator
macro names.
139831
TPTAPI supports a new event that retrieves the Stream Operator macro names.
141801
To improve performance, Teradata PT now dynamically allocates shared memory
based on number of operator instances in a job.
142154
The TPTAPI installation package converted to Basic MSI.
142333
TPTAPI supports the PX_RetryError code.
142720
TPTAPI is now fully dynamically linked for Windows and Unix platforms.
144071
TPT log and checkpoint directories have been enhanced to be writable to all users on
the Windows 7, 2008, and Vista platforms.
Table 46: Teradata PT API RFCs
RFC
Description
89714
Teradata PT API is supported on IBM z/OS operating systems.
110698
Teradata PT API includes a threading example for IBM z/OS.
110703
Teradata PT API includes a multi-node example for IBM z/OS.
114272
When installing Teradata PT API, users can choose between the following 32-bit API
libraries: 32-bit library built with the gcc 2.96 compiler or the 32-bit library built with
the gcc 3.3 compiler.
114964
116133
Teradata PT API supports the new Teradata Database 13.00 PERIOD data types. See
Teradata Parallel Transporter Application Programming Interface Programmer Guide for
details.
116134
Teradata PT API supports the following new DML options:
• MARK EXTRA ROWS
• MARK EXTRA UPDATE ROWS
• MARK EXTRA DELETE ROWS
• IGNORE EXTRA ROWS
• IGNORE EXTRA UPDATE ROWS
• IGNORE EXTRA DELETE ROWS
For more information, see Teradata Parallel Transporter Application Programming
Interface Programmer Guide.
120
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Parallel Transporter
Table 46: Teradata PT API RFCs (continued)
RFC
Description
116137
The TD_APPENDERRORTABLE and TD_DROPERRORTABLE optional attributes
were added to the Stream driver to support using an existing error table across jobs. See
Teradata Parallel Transporter Application Programming Interface Programmer Guide for
more information.
116139
Teradata PT API dynamically creates a schema when using the Teradata PT Export
driver and the schema can be shared with other instances of Teradata PT API using
different drivers.
117623
Teradata PT API applications do not need to store checkpoint data when using the
checkpoint and restart features. The TD_Evt_RowsCheckpointed event returns the
total number of rows each instance has checkpointed. This event is available for the
Load, Update, and Stream drivers.
119675
Documentation Only
Instructions for executing macros using the Stream driver were added to Teradata
Parallel Transporter Application Programming Interface Programmer Guide.
120862
Documentation Only
Teradata PT API is no longer supported on MP-RAS. Related information was removed
from Teradata Parallel Transporter Application Programming Interface Programmer
Guide.
123343
The Load driver supports the following optional attributes:
• TD_DROPERRORTABLE.
• TD_DROPLOGTABLE
The Update driver supports the following optional attributes:
• TD_DROPERRORTABLE
• TD_DROPLOGTABLE
• TD_DROPWORKTABLE
See Teradata Parallel Transporter Application Programming Interface Programmer Guide
for details.
123906
123956
130830
A g++ 4.1 build was added to the 32-bit and 64-bit packages of Teradata PT API to
support the application STL code built with g++ 3.4 and up.
The previously used namespace of ncr::teradata::client::API is supported so partners
can use a single build of their application for both the 12.0 and 13.00.01 versions of
Teradata PT API.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Teradata Tools and Utilities Release Definition
121
Chapter 2: Product Information
Teradata Parallel Transporter
Table 47: Teradata PT DRs
DR
Description
118343
Documentation Only
Error messages were added to the “Troubleshooting” section in Teradata Parallel
Transporter User Guide.
122
123504
If a Teradata PT operator failed at checkpoint time, file archival also failed. This
problem no longer occurs.
124000
When Teradata PT load jobs were run in parallel, a Data Stream error occurred
intermittently. This error no longer occurs.
125166
On Linux and UNIX operating systems, if the environment variable TWB_ROOT was
undefined, the execution of Teradata PT caused a core dump. This error no longer
occurs.
125231
Performance was improved for jobs that contain the TBUILD -S option.
127541
On UNIX and Linux operating systems, Teradata PT jobs failed when the twbclean file
could not be opened for output. This error no longer occurs.
127720
On Windows, if a script contained carriage return characters at the end of SQL
statements, the script failed. This error no longer occurs.
129095
Previously, the Teradata PT ODBC Operator failed with a core dump when processing
more than 500 M rows containing large decimals. The failure was caused by a storage
leak. This error has been corrected.
131220
Previously, the Teradata PT Data Connector Operator would fail when using the
KANJISJIS_0S character set and multiple character delimiters. This error has been
corrected.
135349
An error message would occur when using the Teradata PT Data Connector Operator
to read data input files larger than 4 GB. This error has been corrected.
135841
Teradata PT jobs would exist with a status 8 when running multiple Data Connector
producers due to synchronization issues at end-of-data (EOD) processing time. This
error has been corrected.
136559
TPT Load Operator on mainframe no longer fails with a CLI0188 error with a onecharacter TDPID.
136568
A Teradata PT job invoked within a Microsoft Visual Basic® application occasionally
receives a Microsoft Windows NT runtime exception. The NT structured exception
code now displays in the error message. The maximum stack size was increased to 8 M.
137520
Previously, the ampersand symbol (@) was not accepted as part of the multi-byte
character set in a Teradata PT script. This error has been corrected.
138204
Teradata PT Insert Operator would display an error when the NULL value was entered
into CLOB or BLOB data types. This error has been corrected.
138869
TPT Stream Operator no longer coredumps when the TPT job has the following
characteristics: pack factor greater than the allowed number of records for the job, has
many columns in the target table, and uses multiple DML groups with the first using the
array support feature and the last group not using it.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Preprocessor2
Table 47: Teradata PT DRs (continued)
DR
Description
139460
The Stream operator does not pass the DBS error message text to Teradata PT API
when Teradata PT API calls the Stream Operator's TPT_Evt_DBSError event. This
error has been corrected.
139466
In the Teradata PT API mode, the Stream Operator hangs when the Teradata PT API
application continues to send data rows to the Stream Operator after a DBS failure. For
example, DBS error 2644 - No more room in database <database
name>. This error has been corrected.
140364
The TPTAPI 64-bit 13.0 install was not properly detecting tdicu 13.0. This has been
corrected.
140978
GetTELINFO returns a buffer length value in the 200 MB to 3GB range with multiple
instances and multiple DML groups on all operating systems. This error has been
corrected.
142332
The Teradata PT Operator Support Library does not return the CLI error code and
message to the caller for the TPT_Evt_CLIError event. This error has been corrected.
144293
Fixes "unresolved external symbol error" with methods GetColumns() and
GetDataType() on Windows 7.
144380
New TPT jobs no longer pick up the contents of a previously cancelled job with the
same process ID.
Table 48: Teradata PT API DRs
DR
Description
117343
Documentation Only
Information regarding TIME, TIMESTAMP, and INTERVAL data types conversions
was added to Teradata Parallel Transporter Application Programming Interface
Programmer Guide.
118301
Documentation Only
Information on the TD_LOG_TABLE attribute for the Load, Update, and Stream
drivers was updated in Teradata Parallel Transporter Application Programming Interface
Programmer Guide.
126045
Multi-thread programs failed when exporting data from different tables in parallel. A
variable was modified to resolve the problem.
Teradata Preprocessor2
Teradata Preprocessor2 (PP2) for embedded SQL allows you to incorporate SQL statements
into application programs that access data in Teradata Database. PP2 resolves and expands
Teradata SQL statements incorporated in an application program. Using PP2, you can
Teradata Tools and Utilities Release Definition
123
Chapter 2: Product Information
Teradata Preprocessor2
precompile and execute applications that run on one operating system and access databases
on the same or on a different operating system.
Product Version Number
Teradata PP2 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
SQL Stored Procedures and Embedded SQL
B035-1148-098A
Teradata Preprocessor2 for Embedded SQL Programmer Guide,
B035-2446-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 49: Teradata Preprocessor2 for Embedded SQL RFCs
124
RFC
Description
59763
PP2 is supported on Hewlett-Packard HP-UX Intel Itanium (Itanium build).
89347
Teradata PP2 supports DEFAULT VALUES in INSERT SQL statements.
97693
Teradata PP2 supports the Auto Generated Key Retrieval feature, which allows a client
application to retrieve an identity column value or a whole row from Teradata
Database.
115740
Teradata PP2 allows scalar sub-queries everywhere a value expression is allowed.
115741
Teradata PP2 supports the new Teradata Database 13.00 PERIOD data types. A
PERIOD data type has two values that represent the start and end of the period.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Preprocessor2
Table 49: Teradata Preprocessor2 for Embedded SQL RFCs (continued)
RFC
Description
115742
The Teradata PP2 parser was changed to accept the new request, AS USER <USER
NAME>, before any DDL or Data Manipulation Language statements. This feature
allows Teradata PP2 type names and escape sequences to be expanded in SQL
statements containing the AS USER prefix.
115845
Teradata PP2 supports the Teradata Database trusted sessions feature (user
impersonation with query banding). Changes were made to the SET QUERY_BAND
command to support the Query Band feature. For more information, see Teradata
Preprocessor2 for Embedded SQL Programmer Guide.
115850
Beginning with this release, earlier versions of Teradata PP2 work with new Teradata
Database releases without having to upgrade Teradata PP2.
115943
Documentation Only
Information regarding UDTs and UDMs was added to Teradata Preprocessor2 for
Embedded SQL Programmer Guide.
119274
Teradata PP2 is supported on IBM CICS® Transaction Server for z/OS V3.2.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 50: Teradata PP2 DRs
DR
Description
113575
When a comma was detected while parsing a CASE expression, Teradata PP2
incorrectly assumed the CASE expression was completed and checked that all tokens
were parsed. Teradata PP2 was modified and this error no longer occurs.
114688
Teradata PP2 incorrectly returned a runtime 10302 error while executing GRANT
statement. Teradata PP2 was modified and this error no longer occurs.
115825
A short integer indicdata parcel length can have only the length of the indicator byte
when passed in by a DBCX. In this instance, the overall DBC Extension accounted for
the proper length, but because the data parcel included a length of zero for an
individual field, Teradata CLIv2 looped trying to find the next parcel in the extension.
Teradata PP2 was modified and this error no longer occurs.
122905
Teradata PP2 incorrectly returned the SQL code 0 when an UPDATE or DELETE
statement did not affect any records or rows. Teradata PP2 was modified and now
correctly returns SQL Code 100 when an INSERT, UPDATE, or DELETE statement
does not affect any records or rows.
125392
SQLLEN for embedded SQL failed when SQLLEN was set to 32767. The issue has been
resolved.
128256
A core dump was occurring when EXEC SQL WHENEVER.. CALL was used while
preprocessing in the 64-bit HP-UX and Sun Solaris platforms. Teradata PP2 was
modified and this error no longer occurs.
Teradata Tools and Utilities Release Definition
125
Chapter 2: Product Information
Teradata Query Director
Table 50: Teradata PP2 DRs (continued)
DR
Description
131901
On MPRAS using TSME CD[Tape Storage Management Enablers], SQLPP Installation
failed with .setup.sh. Teradata PP2 was modified and this error no longer occurs.
136355
PP2 was returning wrong decimal values on SOLARIS Opteron. This issue has been
resolved.
138849
Read-only SOLARIS directories were causing the PP2 installation to fail when it tried to
write to those directories. Teradata PP2 was modified and this error no longer occurs.
140088
Preprocessing failed on Windows 2008/Vista if run as a non-administrator. Teradata
PP2 was modified and this error no longer occurs.
140375
The 1720 error occurred on Windows 2000, Windows 7, Vista, and 2008 when the
installation was run as a non-administrator. Teradata PP2 was modified and this error
no longer occurs.
Teradata Query Director
Teradata QD is a session routing tool designed to enhance the availability of multiple systems
using session balancing and failover options.
Product Version Number
Teradata QD 13.02.00.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Query Director User Guide,
B035-2510-119A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
126
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Query Director
Table 51: Teradata QD RFCs
RFC
Description
109361
Teradata QD includes a new trace file called tracelevel4. The trclvl option and the
SockClient update trclvl command allow users to set the trace level to 4. The trace file 4
is optional just like the other trace files. You can have trace 4 with or without any other
trace level set. See Teradata Query Director User Guide for details.
109364
Earlier versions of Teradata Tools and Utilities applications can now connect to later
versions of Teradata Database through Teradata QD. For example, Teradata Tools and
Utilities 7.1 clients can access Teradata Database V2R6.x or later through Teradata QD.
116881
Teradata QD supports Teradata Database 13.00 in a heterogeneous environment with
other Teradata Database versions.
116906
To strengthen Teradata QD security, the SockClient health command was changed; the
-sql option is no longer available.
116909
Teradata QD supports Unicode. International names can be used in userids and
account strings.
116910
Teradata QD recognizes four types of user pattern matching and four types of account
string pattern matching:
• Exact match
• Sub-string wildcard match
• Trailing wildcard match
• Leading wildcard match
For additional information, see Teradata Query Director User Guide.
116911
The lack of an entry in the Teradata QD routing file can not be used to prevent users
from logging on to Teradata Database. If a user is not found in the routing file, then the
routing defaults to ANY. However, you can block unknown users from accessing a
Teradata Database from Teradata QD. For instructions, see Teradata Query Director
User Guide.
116912
Teradata QD sends a logoff message to each connected Teradata Database, when a
client application disconnects.
116914
Teradata QD supports .Net Data Provider for Teradata.
119846
Teradata QD supports Simple and Protected GSS-API Negotiation (SPNEGO). See
Teradata Query Director User Guide for details.
116896
Teradata QD has expanded LDAP support to include Active Directory Application
Mode (ADAM) directories and Novell’s eDirectory.
123952
Teradata QD is available as a service on Linux.
126859
The error code file in Teradata QD can be updated without having to stop or restart the
application.
127253
Previously, Teradata QD users and account strings were defined in the routing rule.
Users can now be arranged in user-defined groups.
Teradata Tools and Utilities Release Definition
127
Chapter 2: Product Information
Teradata Query Director
Table 51: Teradata QD RFCs (continued)
RFC
Description
129786
Routing rules for any user or user group can now be changed without affecting the
routing rules for any other existing userid or usergroup. Several new commands were
added to support this functionality. See Teradata Query Director User Guide for more
information.
129851
Teradata QD includes five new commands that support session relocation and
termination:
•
•
•
•
•
Failover
Kill
Logoff
Move
Untag
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 52: Teradata QD DRs
DR
Description
117109
Previously, Teradata QD did not check the size of the following variables in a routing
file: userid, account string, and Teradata system name. Teradata QD now enforces the
following maximum length defaults:
• 31 characters for userid and account string
• 32 characters for Teradata database name
These limits apply to startup, the configuration file, the routing file, and sockclient
commands.
128
123138
On Windows systems, shutting down Teradata QD caused Error 10038: operation on
non-socket. The problem no longer occurs.
123168
Service param file did not accept parameters with spaces. The problem no longer
occurs.
125639
Teradata QD produced memory allocation errors during ODBC sessions. The errors no
longer occur.
126265
Previously, a Teradata QD LCD command prevented failover when the Host Active
Character Sets did not match. In the case of Named, logon was prevented. The
problems no longer occur.
128555
Sockclient update command now allows spaces in routing file and error code files when
the spaces are enclosed in double quotes; for example,
"C:\Documents and Settings\routing.cfg".
128664
Teradata QD attempted to re-logon after the client logged off. The problem no longer
occurs.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Query Scheduler
Table 52: Teradata QD DRs (continued)
DR
Description
129852
Previously, trace files 1, 2, and 4 contained unspecified columns, negative elapsed times
and inconsistent time stamps. All the issues were resolved.
132027
134330
Previously, trace files did not include log entries that would allow customers to calculate
the time spent by a query in Teradata QD.
Trace files were enhanced to include log entries about the time a query spends in
Teradata QD; for example,
• Entry time to Teradata QD.
• Events that occur within Teradata QD prior to sending the SQL to Teradata
Database.
• Events that occur when a response is sent to the user.
Also, the ses command was enhanced.
See Teradata Query Director User Guide for more information.
133887
Teradata QD now correctly processes files with lines greater than 1024 and files without
a newline marker at the end of a line.
134047
Teradata QD now correctly starts as a service on SUSE Linux when the trclvl parameter
is specified in the qrydir.conf file.
Teradata Query Scheduler
Teradata QS provides a database request scheduling service. Queries can be scheduled
through client applications, such as the Scheduled Request Viewer and Teradata SQL
Assistant. The product consists of client, server, and administrator components.
The Teradata QS Administrator has features to:
•
Migrate earlier versions of the Teradata QS database (dbqrymgr)
•
Schedule requests
•
Set up user profiles
•
Set up time frames in which the requests are executed
The Teradata QS client components have features to schedule and monitor SQL requests.
The Teradata QS server components save, process, and execute Teradata QS client requests
that have been scheduled.
Product Version Number
Teradata QS 13.00.00.04
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
Teradata Tools and Utilities Release Definition
129
Chapter 2: Product Information
Teradata Query Scheduler
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Query Scheduler Administrator Guide,
B035-2511-088A
Teradata Query Scheduler User Guide,
B035-2512-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 53: Teradata QS RFCs
RFC
Description
92935
Teradata QS logs the Request ID and Job ID prior to sending the SQL to Teradata
Database.
103408
A session query band can be assigned to a scheduled request when the target database is
Teradata Database 12.0 or later.
104302
Teradata QS uses the time range from the database to automatically reschedule a query.
If the time range is absent, the query is not automatically rescheduled. From the
Teradata QS Viewer, the status shows Restricted and the database error displays in
the Information column.
118182
Teradata QS supports the new Teradata Database 13.00 PERIOD data types. A PERIOD
data type has two values that represent the start and end of the period.
118226
Teradata QS displays context-sensitive help when using Internet Explorer 7.0 as the
default browser.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
130
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata SQL Assistant
Table 54: Teradata QS DRs
DR
Description
128960
During a release upgrade, the registry entries were not copied during uninstallation of
the previous Teradata Query Scheduler version. Code was modified to retain the
registry entries for the new version.
131123
Previously, Teradata QS removed new lines (0x0A) from the query text. Because singleline comments were terminated with a line break, Teradata QS altered the query and the
end-of-comment was lost. This error has been corrected.
136271
A table is not being created when the query is scheduled through Teradata SQL
Assistant. This issue was resolved by changing the query code to retrieve query text from
the tdwm.SchedRequestsSupl table, and removed trailing semicolons in the query text.
140391
Installation fails when Windows Vista, Windows 7, or Windows Server 2008 are
installed using non-administrator privileges. Changed the Required Execution Level
option in setup.exe to require administrator privileges.
141411
Scheduled queries get timed-out after 100 seconds. This issue was resolved by increasing
the time-out value to 999 seconds.
142187
Based on reported installation problems, the Teradata Query Scheduler installation
package needs to be converted to the Basic MSI installation package. The Basic MSI
installation package is now used for Teradata Query Scheduler.
Teradata SQL Assistant
Teradata SQL Assistant for Microsoft Windows is a query and information discovery tool
used to retrieve data from Teradata Database or any ODBC-compliant database server. Users
can then view, manipulate, or store the extracted data on their desktop PC. .NET Data
Provider for Teradata can also be used to connect to Teradata Database from Teradata SQL
Assistant for Microsoft Windows.
Product Version Number
Teradata SQL Assistant for Microsoft Windows 13.00.00.13
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Teradata Tools and Utilities Release Definition
131
Chapter 2: Product Information
Teradata SQL Assistant
Documentation
Teradata SQL Assistant for Microsoft Windows User Guide,
B035-2430-088A
Release Notes
Product Limitations
For specific limitations that apply to this release of Teradata SQL Assistant for Microsoft
Windows, see Teradata SQL Assistant for Microsoft Windows User Guide or read the
ReleaseNotes.txt file in the install directory.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 55: Teradata SQL Assistant RFCs
RFC
Description
84116
A Page Setup command was added to the File menu that allows users to print output
on legal-size paper. See Teradata SQL Assistant for Microsoft Windows User Guide for
details.
117932
Teradata SQL Assistant has been completely redesigned. It continues to look and act
like previous versions of the product, but now it requires Microsoft .Net. For more
information, see Teradata SQL Assistant for Microsoft Windows User Guide.
122172
Teradata SQL Assistant removes comments enclosed in a /* ... */ string before
submitting the query to an IBM DB2® or Microsoft Access™ data source.
125421
When .Net data provider is not available for Teradata 12.0 and above, a detailed
message is displayed.
126239
In Teradata SQL Assistant, passwords have been masked only if they appear in the first
statement in a query. Now, passwords are masked wherever they appear.
128790
Installing the current version of Teradata SQL Assistant now removes all previous
versions.
129885
In query results, failed statements are now highlighted to make them easier to find.
139616
A -p startup parameter to specify the Data Provider type was added.
145166
SQLA now returns code 0 when the ROLLBACK command runs successfully.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
132
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata SQL Assistant
Table 56: Teradata SQL Assistant DRs
DR
Description
97715
Teradata SQL Assistant stopped responding when you quickly right-clicked twice on a
Tree node. Teradata SQL Assistant was modified and this error no longer occurs.
110866
Previously, directory and file names longer than 128 bytes could not be saved as an
Excel file. Teradata SQL Assistant was modified and file can now be saved.
121382
Previously, queries containing either BEGIN QUERY LOGGING or BEGIN LOGGING
commands were not correctly parsed. Teradata SQL Assistant was modified and this
error no longer occurs.
124110
Decimal values over 28 digits were being rounded to 15 digits followed by zeros. The
code fix adds a new NumText data type to accommodate such values.
124247
SQLA did not automatically handle expired passwords when using the TD.Net
connection. This problem has been resolved.
124312
Various minor interface inconsistencies have been corrected.
124405
Errors occurred when saving empty or invalid SQL Sets from Query Builder. Improved
control over enabled features resolved this issue.
124482
Names beginning with “BEGIN” can be misinterpreted, causing queries to not be
submitted to the DBS. The rules for FOR and BEGIN were modified to resolve this
issue.
124840
SQLA installation fails because of install conditions. This issue was resolved by
removing the install conditions and verifying that SQLA can be installed and the correct
warning messages are displayed.
125099
Some statements in a query were not executed. This issue was resolved by modifying the
the FOR parser rule.
125398
Cutting and pasting of Microsoft Access VBA Editor causes extra invalid text to be
pasted into query. This issue was resolved by modifying the paste function in CodeMax.
125543
Teradata SQL Assistant was only returning data if the statement type was a certain type.
Current logic now returns a result set unless the statement is known as one that never
returns a result.
125604
Any column defined as Decimal(n,m) where n < 29 and m > 14 resulted in output
truncated to only 2 decimal places. The error no longer occurs.
125729
Improvements were made to a variety of functions including menu closing, eliminating
duplicate accelerator keys, improving tab behavior, properly enabling certain menus,
adding Elapse Time to completion messages, improving compatibility with .Net
Provider and ODBC, handling whitespace during parsing, supporting the FOR in
PIVOT clauses, improving the masking of passwords, and improving behavior when
only one statement is returned.
126156
Previously, Teradata SQL Assistant refocused to the beginning of the code in the Query
Window whenever any part of the code was highlighted and executed. This problem no
longer occurs.
126226
Error messages that occur in multi-statement queries are now displayed on the status
bar.
Teradata Tools and Utilities Release Definition
133
Chapter 2: Product Information
Teradata SQL Assistant
Table 56: Teradata SQL Assistant DRs (continued)
134
DR
Description
127110
Teradata SQL Assistant unexpected closes if policy files for Teradata .Net Data Provider
13.00.01 are missing. Also, the application unexpectedly closes when the Shift or Cntl
keys are used in an Answer cell. Neither problem occurs any longer.
127171
New parser rules have been added for the FROM keyword and for the phrase
“BETWEEN aaa AND bbb” to better govern line breaks.
127254
A result message was added for exports to alert users that the operation resulted in no
data being written to the Export file.
127405
Teradata SQL Assistant now loads faster in a Microsoft .Net framework.
127518
Improvements were made to a variety of functions including highlighting Access
functions, correcting cursor behavior, and dialog box behavior.
127609
Previously, Teradata SQL Assistant did not mask passwords that contained syntax
errors, such as including quotation marks. This problem no longer occurs.
129117
When using Teradata .Net Provider 13.00.01, Teradata SQL Assistant displays column
names instead of column titles. The error no longer occurs.
129475
A variety of improvements were made to window behavior, scroll bars, column results,
Explain output, and Answerset output.
129927
Teradata SQL Assistant supports the authentication mechanisms supported by .Net
Data Provider for Teradata, namely SPNEGO, LDAP, and TD2.
130174
Previously, CASE and END CASE did not have a set of scope keywords, which resulted
in errors if the statements ended with semicolons. This error no longer occurs.
130447
The History window was displaying only the first line of SQL text. Two new display
options were added to control how text is displayed.
130448
Columns containing uppercase strings are not wide enough to see all the data. Columns
were resized.
130548
The History window has a new field, SQL Text, that filters for matching rows. Also,
wildcard characteristics were modified, and a Clear button was added.
130571
Duplicate queries were not deleted from the History window after a query was reexecuted. The problem no longer occurs.
130949
Teradata SQL Assistant was not saving the file name when Query files were opened,
which prompted users to have to enter the file name in order to save the query. The
problem no longer occurs.
131047
Query start times are now displayed in Executing messages so users can determine how
long a query has run.
131209
The result code column was displaying incorrect values after a History filter was
applied. The error no longer occurs.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata SQL Assistant
Table 56: Teradata SQL Assistant DRs (continued)
DR
Description
131439
Improvements to the functionality of the graphical user interface include resetting
certain display sizes, improving scroll behavior, successfully capturing Explain
statements that don’t begin with “Explain,” getting accurate results when stopping the
row return limit while executing multiple SELECT statements, eliminating certain
locking and error behaviors, resetting focus, properly displaying Answerset options,
improving readability, and maintaining History after upgrades.
131600
132104
If an ALTER table query was aborted during the commit phase, Teradata SQL Assistant
shows the query as successfully completed, while Teradata Manager shows the query as
aborted. The error no longer occurs.
132431
11 minor user-interface issues in SQLA 13.0.0.5 were resolved.
132518
An error message and an empty or locked answerset window occur after executing a
query. This issue was corrected.
133264
Extra double quotes inserted into queries by a paste operation. This issue was resolved
by creating a compatible clipboard-copy function.
133400
History table rows are not sorted when loaded. This issue was corrected.
133441
Import fails when keyword is less than three characters. This issue was corrected.
133558
An extra line break was being added in large DDL files from SHOW command. This
issue was resolved by controlling line breaks for the SHOW command.
134409
An error message is displayed at startup that contained a long string of alphanumerics.
A code modification was made to check for and manage the condition.
134418
Database error caused by submitting statements in parallel when using the Execute
command. The Begin/End parser rule was modified to correct the issue.
134472
Status message did not display the number of rows processed by an “action” macro. To
resolve this issue, a modification was made to the method of accounting for rows
processed.
134474
Child windows in SQLA did not realize when the main window was maximized or
restored. This issue was corrected.
135162
Errors occurred when copying data containing null cells to the clipboard. This issue was
resolved by modifying the code to replace null cells with empty cells.
135234
The installer runs at program startup if the application was installed by a different user
who did not have administrator permissions. To resolve this issue, all syntax files
(*.syn) were installed into the “All Users” branch.
135341
Query failed or was partially executed when it contained the PPI “NO CASE” clause.
This issue was resolved by adding a parser rule for the CASE keyword.
135432
An application error occurred when executing the SHOW DATABASES query on
MySQL (or other SHOW). This issue was resolved by modifying the MySQL
connection and changing how the SHOW command is processed.
135514
The SQLA application closes, without displaying an error message, when a query is
executed. This issue was resolved by modifying the Form Closing event.
Teradata Tools and Utilities Release Definition
135
Chapter 2: Product Information
Teradata SQL Assistant
Table 56: Teradata SQL Assistant DRs (continued)
136
DR
Description
135950
Duplicate values can be seen in the DataSources.config file. This issue was resolved by a
software modification.
136054
SQLA hangs when returning a result set that contains interval data from an Oracle
device. This issue was resolved by not executing a call and changing a parameter to
False.
136125
When SQLA was started, it went into a loop through an install, and then failed. This
issue was resolved with a software modification.
136198
The SQLA application reports Overflow or NullReference error and might shut down.
This issue was resolved with a software modification.
136264
The user is prompted to continue during an Export operation. This issue was resolved
with a software modification.
136306
The SQLA application defaults to Teradata.Net even though ODBC was the default
connectivity option. to resolve this issue, the provider combobox data value should be
set to ‘Td’ or ‘Odbc’ and saved in Options.Provider.
136391
The fractional portion of seconds was being converted to "ffffff " in SQLA 13.0 when the
result is saved as Excel. This issue was resolved with a software modification.
137108
Duplicate Key error expands Indexes node, but not all indexes displayed. To resolve this
issue, a sequence number was added to the Key used in the tree.
137168
If a query contained only spaces, tabs, and line feeds, the DeleteBlankLines function
returned an error. A code fix prevents the error.
137244
In Windows Server 2008, if a query has previously been opened or saved to a directory
other than to the default directory, a subsequent Open still points to the default location
rather than to where the file actually resides. This issue was resolved with a software
modification.
137245
SQLA prompts to enter Named parameter for Imports even if this option is disabled. A
code fix resolved this problem.
137334
Format text (CTRL-Q) corrupts the SQL if column name starts with 'From' because the
SQLA parser incorrectly identifies FROM as a keyword when it is part of an object
name. A software modification modified the parser rule for FROM and resolved the
issue.
137760
The Schedule dialog was not being invoked when a query was rejected due to TASM
rule from SQLA. This issue was resolved with a software modification.
137791
SQLA 13.0.0.4 and above was truncating trailing spaces from CHAR(n) columns in the
answerset. This issue was resolved with a software modification.
137802
SQL Assistant did not export an answerset that contained errors, even if the 'Write SQL
& result message' option is checked. This issue was resolved with a software
modification.
137835
SQL Assistant 13.00 returned an error when totals were copied and pasted. A code fix
resolved the problem.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata SQL Assistant
Table 56: Teradata SQL Assistant DRs (continued)
DR
Description
137913
A "The Database or the tablename was invalid or is unavailable" error message was not
being cleared and a Null Reference error appeared when an invalid database was
expanded. A code fix resolved the problem.
138288
A Duplicate Key error occurred and incomplete list of tables was displayed when
opening a database explorer tree in Oracle Database. A code fix resolved the problem.
138653
SQLA 13.0.0.7 returned incorrect row counts when a macro returned multiple result
sets. A code fix resolved the problem.
139763
The SQLA install failed when .Net Framework 4.0 was already installed on the system. A
code fix resolved the problem.
140032
Export file reports "#Rows returned=0" for an action statement. A code fix changed this
to a more useful "#rows processed=n."
140138
Decimal values were multiplied by 100 when SQLA was launched from TDAdmin. This
issue was resolved with a software modification.
140388
SQLA install returned 1720 errors on Windows 2000, Windows 7, Vista, and 2008 when
run as non-administrator. A code fix resolved this issue.
140450
Returning large answersets took longer than expected because of the amount of time
spent setting column widths. A code fix resolved this issue.
140568
Application startup loop occurs if SQLA started up using the shortcut in the Start menu
in Windows 7. A code fix resolved the problem.
141113
SQLA 13 on Japanese system displayed connection dialog for .NET even though ODBC
was selected. This issue was resolved with a software modification.
141705
Some result sets were not being returned if a macro contained a SELECT returning no
rows. This issue was resolved with a software modification.
142168
BOM characters were being added when SQLA 13.0 saved file; this made the file
unusable by BTEQ. This issue was resolved with a software modification.
142213
History rows may be missing if the option to store History in separate files by data
source was used. A code fix resolved the problem.
142396
SQLA took a very long time to return control after user selected Yes to Stop Row Limit
when using Execute Parallel. This issue was resolved with a software modification.
142679
"Maximum number of answer rows to display" string is incorrectly translated in the
Japanese version. This has been corrected.
143046
SQLA 13.0 crashed at startup if it fails to create a DataSources.config file. A code fix
resolved this issue.
143057
SQL Assistant sets the background color to Black instead of the System color. This issue
was resolved with a software modification.
143281
Invalid query lines were being displayed after the deletion of a large block of data due to
a screen refresh problem. A software modification fixed the problem.
Teradata Tools and Utilities Release Definition
137
Chapter 2: Product Information
Teradata SQL Assistant/Web Edition
Table 56: Teradata SQL Assistant DRs (continued)
DR
Description
143736
Many error messages from NGEN are displayed in the command window during
installation of SQLA. A code fix prevents this from happening.
143760
Teradata SQL Assistant 13.0 exhibits inconsistent behavior when copying and pasting
text that contains new line characters. A code fix resolved the issue.
143899
A "Database already exists" error occurs when SQLA 13.0 is started through a Citrix
server. A software modification fixed the problem.
144048
SQLA was returning a 3706 syntax error when the password was changed through
Tools>Change Password. A software modification fixed the problem.
144312
SQLA 13.0 imports Chinese characters incorrectly. A code fix resolved the issue.
144584
SQLA crashed if a query is executed immediately after performing a regular expression
Find/Replace operation. A software modification fixed the problem.
144742
Export to Access failed if query contained duplicate column names. A code change
prevents this from occurring.
144808
Focus was not being set to Answerset after results were generated from the List Tables or
List Columns tools and #DNS entries could not be reset. A code change fixed this
behavior.
144923
After an SQLA 13.0 upgrade, the Database Explorer Tree for Sybase would not expand
because data source properties were being set incorrectly. A code fix resolved the
problem.
145162
SQLA was displaying and error with .NET when CLOB value is < 68. This issue has been
resolved.
145466
An export of SHOW statement results in SQLA produced output with extra line feeds
or truncated output. A code fix resolved the problem.
Teradata SQL Assistant/Web Edition
Teradata SQL Assistant/Web Edition is a web-based query tool that allows you to compose
queries, submit them to Teradata Database, and then view the results in a web browser.
Product Version Number
Teradata SQL Assistant/Web Edition 13.00
Supported Versions of Teradata Database
138
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Statistics Wizard
•
Teradata Database 13.00
Documentation
Teradata SQL Assistant/Web Edition User Guide,
B035-2505-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software. There are no RFCs for this product for this release.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 57: Teradata SQL Assistant/Web Edition DRs
DR
Description
106373
Teradata SQL Assistant/Web Edition displayed a Server error when a user cleared the
Close answer set tabs before submitting a new query option and submitted more than
one query. In addition, Teradata SQL Assistant/Web Edition did not populate or handle
the child windows, such as Option and Edit History, properly when user name included
multibyte characters.
Teradata SQL Assistant/Web Edition was modified and these errors no longer occur.
112984
On Microsoft Vista™ Enterprise x64 operating systems, Teradata SQL Assistant/Web
Edition could not connect to Teradata Database. Teradata SQL Assistant/Web Edition
was modified and this error no longer occurs.
Teradata Statistics Wizard
Teradata Statistics Wizard analyzes workloads, automates the collection of new statistics or
re-collection of existing statistics, and makes recommendations to improve workload
performance.
Product Version Number
Teradata Statistics Wizard 13.00.00.05
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
Teradata Tools and Utilities Release Definition
139
Chapter 2: Product Information
Teradata Statistics Wizard
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Statistics Wizard User Guide,
B035-2503-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 58: Teradata Statistics Wizard RFCs
140
RFC
Description
112734
Teradata Statistics Wizard supports new Unicode V-views.
117192
Teradata Statistics Wizard includes Full or Sampled Statistics Recommendations that
retrieves recommendations based on age of collection, table skew, table growth, general
statistics collection rules, table size, unique columns, and unique indices. See Teradata
Statistics Wizard User Guide for more information.
117193
Teradata Statistics Wizard collects statistics on a sample of the data to reduce the
resources required and the time to perform statistics collection. For details, see Teradata
Statistics Wizard User Guide.
117194
Teradata Statistics Wizard performs auto-search of statistics candidates based on new
table and index creations.
117246
Teradata Statistics Wizard supports large query importing. When importing queries
larger than 10 KB, Teradata Statistics Wizard uses the SQL table for workload
definitions.
118781
Teradata Statistics Wizard supports statistics recommendations and collections on join,
hash, and PPI join indexes, which improves plan optimization.
122167
For SAS, support has been added for database tables that have no primary index (NoPI
tables).
135363
Support was added to the export and import statistics operations for the new
OneAMPSampleEst and AllAMPSampleEst histogram fields.
144767
Based on reported installation problems, the Teradata Statistics Wizard installation
package has been converted to the Basic MSI installation package.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata System Emulation Tool
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 59: Teradata Statistics Wizard DRs
DR
Description
125496
The following issues were found in the Teradata Statistics Wizard demo: 1) In the Save
to File option, no confirmation message is displayed and the dialog box is not closed
until Cancel is clicked. 2) The word “Explaination” is misspelled. 3) Text in the View
Details dialog should not be highlighted. 4) Next button is enabled when it should be
disabled. All issues were fixed.
128280
Previously, errors occurred when the objectusecount feature was enabled. This caused
multiple partition rows containing different accesscount and accesstimestamp values
which caused the query to fail. This error has been corrected.
128282
Teradata Statistics Wizard crashed when multi-column statistics were retrieved and the
total amount of column names exceeded the length of 126 characters. This issue has
been resolved.
131794
Processing speed was slow when viewing column information in a table with many
columns. This issue was resolved.
136842
Previously, when collecting table-level statistics for all databases, an error occurred
when the user selected Yes in response to the following dialog message: Collecting
Statistics for all tables may take a long time. Do you want to continue? The error
message was corrected.
137017
Teradata Statistics Wizard errors out when parsing comment lines with double dashes
and a subquery is used. This issues has been resolved.
140432
Installation fails when Windows Vista, Windows 7, or Windows Server 2008 are
installed by a non-administrator user using administrator privileges. Changed the
Required Execution Level option in setup.exe to require administrator users.
Teradata System Emulation Tool
Teradata SET allows you to emulate Optimizer-generated data from a target system, generate
query plans, and then import that information to a test system where you can run queries
without affecting your production system.
Product Version Number
Teradata SET 13.00.00.06
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
Teradata Tools and Utilities Release Definition
141
Chapter 2: Product Information
Teradata System Emulation Tool
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata System Emulation Tool User Guide,
B035-2492-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 60: Teradata SET RFCs
RFC
Description
112732
Teradata SET supports new Unicode V-views. See Teradata System Emulation Tool User
Guide for more information.
115863
Teradata SET reports missing access rights as errors and allows the rights to be granted
after an export, import, or cleanup request has failed. Rights can be granted
automatically or manually on a database or on an object.
116068
117249
Teradata SET supports a more detailed display of Query, Explain Text, Step Report, and
Plan Information in the Import window.
117690
Teradata SET supports consistent display of Explain Text in the Import window for
queries entered manually and queries captured from the QCD.
118778
Teradata SET supports enhanced time-limit and abort capabilities, making it easier to:
• Stop a long-running index analysis before it completes while retaining any identified
recommendations
• Review the recommendations as though the complete analysis was run
• Continue an index analysis from the point at which the analysis was terminated
142
118783
Teradata SET supports improved estimates for statistics during import and export,
which result in improved plan optimization.
122166
For SAS, support was added for database tables that are created with no primary indexes
(NoPI tables).
128242
Teradata SET now supports a session date in either ANSIDATE or INTERGER form.
Previously, an implicit character-to-date conversion could generate errors. This error
has been corrected.
134437
Support was added to the export and import statistics operations for the new
OneAMPSampleEst and AllAMPSampleEst histogram fields.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata System Emulation Tool
Table 60: Teradata SET RFCs (continued)
RFC
Description
144632
Based on reported installation problems, the Teradata SET installation package has
been converted to the Basic MSI installation package.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 61: Teradata SET DRs
DR
Description
124223
1) During import, Teradata SET validates QCD when no plans are selected for import.
2) Teradata SET begins allocating permanent space for QCD when QCD is not selected
in the import options. These issues were resolved by coding an in-depth validation
process for issue 1, and adding validation of the presents of execution plans selected for
import for issue 2.
126517
The import of object definitions continues indefinitely when access privilege errors are
incorrectly resolved. This problem no longer occurs.
126518
Teradata SET did not display error messages when failing to export cost parameters.
This problem no longer occurs.
126519
GRANT Access privileges do not need to be displayed for missing Monitor Access
privileges. This problem no longer occurs.
126643
Teradata SET intermittently failed when object definitions were exported. This problem
no longer occurs.
128142
Teradata SET resolved missing access privilege errors during import of object
definitions by submitting appropriate grant statements. Import of object definitions
failed when grant statements failed. This problem no longer occurs.
130383
An unhandled exception occurs while importing the stored procedure object definition.
This error has been corrected.
131122
Teradata SET no longer displays an input error when the mode value and max value of
interval statistics data located on decimal columns contain negative values.
131883
Statistics imports failed and returned a 5464 error when importing multi-column
Primary Indexes on a Join index after renaming the database. This error has been
corrected.
132819
An exported file, that used a QCD that does not contain execution plans and qoekloads,
can now be imported.
135125
Previously, an error occurred when statistics were exported for a large number of
objects. This error has been corrected.
137197
When importing the Cost Profile, constant values are rounded in error. This issue was
resolved by modifying the contant-value formatting.
Teradata Tools and Utilities Release Definition
143
Chapter 2: Product Information
Teradata Visual Explain
Table 61: Teradata SET DRs (continued)
DR
Description
137863
When a user, who did not have access privileges to profile tables, initiated an export of
cost profiles using a DOS command, an error message displayed. This issue was
resolved by replacing the error message with the Grant Access Privileges dialog box.
138539
The Estimated cost of Execution Plans in the Summary Information display did not
agree with the total estimated time shown in the Explain Test information. This issue
was resolved by modifying computation processes, and changing the sequence of some
call functions.
139396
When selecting QCD data followed by a DDL option, the export operation did not
complete. This issue was resolved by code modification.
140125
When a port number is specified while connecting to the Database using CLI
connectivity, TSET prompts an export filename with a colon character. No illegal
filename error message is displayed. This issue was resolved with a code change that
replaces the colon character with a dot (.) character.
140169
At the completion of the export operation, two help session attributes are incomplete.
To resolve this issue, the index for the new help session was updated into the coding.
140427
Installation fails when Windows Vista, Windows 7, or Windows Server 2008 are
installed by a non-administrator user using administrator privileges. Changed the
Required Execution Level option in setup.exe to require administrator users.
140693
TSET hangs when an exported file from a previous release is to be imported. This issue
was resolved by a software update.
141077
When cost profile data is zero in a file to be imported, TSET crashes. This issue was
resolved by updating the code to skip zero-length cost profile data.
Teradata Visual Explain
Teradata VE allows you to view and analyze the execution plans of complex SQL statements,
and then fine-tune those SQL statements to make sure your Teradata Database accesses data
most effectively.
Product Version Number
Teradata VE 13.00.00.07
Supported Versions of Teradata Database
144
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Visual Explain
Documentation
Teradata Visual Explain User Guide,
B035-2504-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 62: Teradata VE RFCs
RFC
Description
85166
Teradata VE provides access to a partition count. Access is available in the Table icon
pop-up details and Step Information report, making it easier to determine when
partition elimination is used to improve performance.
112733
Teradata VE supports new Unicode V-views. See Teradata Visual Explain User Guide
for more information.
116558
Textual compare reports can be viewed vertically improving readability. Reports can be
displayed side by side or one above the other.
117188
Explain results for execution plans can be viewed graphically or textually directly from
an XML schema or plan logged in DBQL, which improves performance while capturing
query execution plans.
Viewing Execution plans from DBQL is limited to XML plans no larger than 31 K. To
view DBQL XML plans larger than 31 K, users must use the traditional QCD plan
capture method. See Teradata Visual Explain User Guide for details.
117248
Teradata VE provides access to object use counts. Access is available in the View menu,
Table icon pop-up details, and Object Use Count report, making it easier to determine
when and how objects are used.
118590
Teradata VE support the following Query Capture Facility/Query Capture Database
enhancements:
• A relation table for PPI partition count
• A new table for capturing XML plans
• A new table for Restart enhancements
122168
For SAS, support has been added for no primary index (NoPI) tables.
128143
Support has been added for “Actual versus Estimated” data in DBQL and QCD so data
can be compared in XML plans.
135361
Support added for viewing one AMP sample estimate and all AMP sample estimates of
the table cardinality when collecting statistics.
Teradata Tools and Utilities Release Definition
145
Chapter 2: Product Information
Teradata Visual Explain
Table 62: Teradata VE RFCs (continued)
RFC
Description
144673
For Windows platforms, the Teradata VE installation package is now MSI. This enables
silent installs via CLI, easier distribution across large user bases, easier customized
installs, as well as restoration to the pre-install state in case of a failed install.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 63: Teradata VE DRs
146
DR
Description
116553
Teradata VE properly saves and refreshes toolbar settings.
116555
Information in the Summary Information window displays vertically on separate lines to
improve readability.
116556
Teradata VE displays the Complete Information report whenever queries are compared
instead of displaying only the report type listed in the Select item list.
116557
Teradata VE opens other reports in the foreground instead of the background when the
bulk compare summary report is open.
116559
Teradata VE includes a Merge into statement icon used to merge one or more rows into
a table.
123794
The target icon was missing for the Merge delete and Merge update steps of DBQL
plans. This problem has been corrected.
125119
Teradata VE now display current object definitions, captured time, current indexes, and
current statistics for DBQL plans.
125120
Teradata VE now allows browsing Merge Into SQLs from DBQL.
126231
Visual Explain displayed an error message, An exception occurred!
Type:UnexpectedEOFException, and did not open DBQL XML query plans
larger than 20,000 characters. This problem has been corrected.
129106
Teradata VE supports the new QCD relationkind value “O” for no primary index
(NoPI) tables.
133853
The Teradata VE application no longer hangs when processing with multiple column
statistics selected.
140426
Installation errors on Windows 7, Vista, and 2008 when run as non-administrator have
been eliminated.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Workload Analyzer
Teradata Workload Analyzer
Teradata WA helps DBAs identify classes of queries (workloads) and provides
recommendations on workload definitions and operating rules to ensure that database
performance meets Service Level Goals (SLGs). When DBAs can control resource allocations,
they are better able to ensure satisfactory response times for critical queries. Teradata WA
helps DBAs effectively manage distribution of resources using graphical displays, such as the
following:
•
Distribution graphs showing resources distribution for workload queries
•
Histograms showing actual service levels, along with recommended settings
In addition, Teradata WA supports the conversion of existing Priority Definitions (PDs) sets
into new workloads. This is helpful for users of earlier versions of Teradata Priority Scheduler
Administrator, who created PD sets to control allocation and consumption of system
resources.
Product Version Number
Teradata WA 13.00.00.04
Supported Versions of Teradata Database
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Workload Analyzer User Guide,
B035-2514-088A
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software.
Table 64: Teradata WA RFCs
RFC
Description
116065
WHERE classification criteria, such as Data Objects (Database, Tables, Views, Macros,
and Stored Procedures), are automatically included in a workload analysis.
116066
N-level analysis allows for recursive, deeper analysis of workload classifications with
WHO, WHAT, and WHERE classifications until a best-fit candidate workload is
reached.
Teradata Tools and Utilities Release Definition
147
Chapter 2: Product Information
Teradata Workload Analyzer
Table 64: Teradata WA RFCs (continued)
RFC
Description
116110
Teradata WA 13.00.01 works with Teradata Database 12.0. However, new Teradata
Database-driven 13.00 features are not available.
116483
A Statement Type correlation parameter was added to classify multi-statement SQL
requests in a workload.
116484
Objects can be specified to be included or excluded for each classification type. Split
workloads can be modified to include or exclude objects for each classification type.
116485
Standard wild card classifications, such as asterisk (*) and question mark (?), can be
used during classification to avoid working with very long Include or Exclude lists.
118194
Workloads display in the Candidate Workloads tree according to evaluation order.
118748
Teradata WA supports DBQL Dictionary changes for Teradata Database 13.00.
120019
The default number of distribution histogram buckets is now 10, instead of 5.
120020
The full Query band name displays on Correlation report when a query band is selected
for analysis.
120021
The distinct value counts for a workload can be displayed from Teradata WA. The
distinct value counts help quickly identify all possible correlation parameters and
available ranges for distribution parameters. See Teradata Workload Analyzer User
Guide for more information.
144769
For Windows platforms, the Teradata WA installation package is now MSI. This enables
silent installs via CLI, easier distribution across large user bases, easier customized
installs, as well as restoration to the pre-install state in case of a failed install.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates.
Table 65: Teradata WA DRs
148
DR
Description
114660
The Navigation Wizard command was removed from Help menu. However, a Navigation
Help icon is still available.
116409
Normalized CPU Time and Un-normalized CPU Time columns were added to the
Unassigned Request, Workload, and second level cluster analysis reports. In second
level cluster analysis, Normalized CPU Time and Un-normalized CPU Time were
added in the Distribution Parameter list.
116598
Previously, a blank dialog box displayed when the Browse button was clicked in the
View CPU Distribution dialog box. This error no longer occurs.
127166
The pre-validation process of Teradata WA was modified so users are no longer
required to have access to the DBC.
Teradata Tools and Utilities Release Definition
Chapter 2: Product Information
Teradata Access Module for Tivoli
Table 65: Teradata WA DRs (continued)
DR
Description
140433
On Windows Vista, Windows 7, and Windows Server 2008, install failed during
Teradata WA installation as a non-administrator. This problem has been resolved via a
code change, enabling the package to be run imp00licitly as administrator.
Teradata Access Module for Tivoli
Beginning with Teradata Tools and Utilities 13.00.01, Teradata Access Module for Tivoli® is
being renamed Tivoli Storage Manager Teradata Extension. The product is not included on
the Tape Storage Management Enablers CD, and Tivoli Storage Manager Teradata Extension
Installation and User Guide is not included on the Teradata User Documentation CD-ROM.
However, Teradata Access Module for Tivoli 01.00.02, released with Teradata Tools and
Utilities 12.0, is compatible with Teradata Database 13.00. Tivoli Storage Manager Teradata
Extension is released with Teradata TARA 13.00.01.
Transparency Series/Application Programming
Interface
The Transparency Series/Application Programming Interface (TS/API) provides access to
Teradata Database using a selected set of Independent Software Vendors (ISV) products
designed to retrieve data stored in DB2 or SQL/DS databases.
Product Version Number
TS/API 13.00
Supported Versions of Teradata Database
•
Teradata Database V2R6.0
•
Teradata Database V2R6.1
•
Teradata Database V2R6.2
•
Teradata Database 12.0
•
Teradata Database 13.00
Documentation
Teradata Transparency Series/ Application Programming Interface User Guide,
B035-2419-088A
Teradata Tools and Utilities Release Definition
149
Chapter 2: Product Information
Transparency Series/Application Programming Interface
Release Notes
None.
Requests for Change
RFCs introduce new features and track changes that enhance the operation of Teradata Tools
and Utilities software. There are no RFCs for this product for this release.
Discrepancy Reports
DRs track corrections and updates to Teradata Tools and Utilities software and to
documentation affected by the updates. There are no DRs for this product for this release.
150
Teradata Tools and Utilities Release Definition
CHAPTER 3
Teradata Tools and Utilities
Documentation
Teradata Tools and Utilities documentation consists of product-specific user manuals, a
release definition (this document), and a CD. These are available from several sources:
•
As part of a software order
•
By download from www.info.teradata.com
•
By request
Software Orders
With software orders, you receive up to four fully indexed and searchable Teradata User
Documentation CDs, free of charge. The number you receive depends on the size of your
system.
Downloadable Documentation
Free, downloadable versions of Teradata Tools and Utilities documentation are available from
www.info.teradata.com including:
•
Web-only Release Definitions
•
PDF versions of all documentation available for this release
•
An image of the Teradata User Documentation CD for this release
To locate a publication title or ID to use when searching for publications associated with this
release, see “Publication Titles and IDs” on page 154.
Release Definition
Release Definitions are occasionally updated to capture products released asynchronously to
the Teradata GCA date. Updated versions are available on the web.
To view the most recent iteration of this document
1
Go to www.info.teradata.com, and click Data Warehousing under the left menu.
2
Click Teradata Release Definitions in the Data Warehousing list.
Teradata Tools and Utilities Release Definition
151
Chapter 3: Teradata Tools and Utilities Documentation
Downloadable Documentation
3
Click Teradata Tools and Utilities under Teradata Release Definitions. A list of Teradata
Tools and Utilities release definitions appears.
4
Locate Teradata Tools and Utilities Release Definition, B035-2029.
For information on Open Teradata Backup products, use the same process to locate Backup
Application Software Release Definition, B035-3114.
User Manuals
Product-specific user manuals are available from the web. Use the Teradata Information
Products Publishing Library site to view or download the most recent versions of all manuals.
To view specific user manuals or manuals associated with specific products
1
Go to www.info.teradata.com.
2
Click General Search under the left menu.
3
Enter pertinent information about a specific product or manual, such as the title in the
Publication Title, Description, Class, or Keywords box.
4
Click Search.
CD Image
You can download the Teradata User Documentation CD image to burn your own CDs. The
image for this release contains all user documentation for:
•
Teradata Database 13.0
•
Teradata Tools and Utilities 13.0
The Teradata User Documentation CD features an index (accessible through the Search
function in Acrobat Reader) that allows you to search for text strings across all of the
documents on the CD.
Caution:
The image file is large. Depending on your connection, it might take a long time to download.
To download a CD-ROM image
152
1
Go to www.info.teradata.com.
2
Under the Online Publications subcategory, Browse by Category, click Data Warehousing.
3
Click CD-ROM Images in the Data Warehousing list. A list of Teradata CD-ROMs appears
in a new window.
4
Select the CD image for this release.
5
Save the file to your local directory.
Teradata Tools and Utilities Release Definition
Chapter 3: Teradata Tools and Utilities Documentation
Print Documentation and CD-ROMs
Print Documentation and CD-ROMs
You can order printed manuals and CDs from Teradata Information Products Publishing for
a nominal cost. Information on whether printed copies of documentation are available and
how to order them is also accessible from www.info.teradata.com.
When ordering printed documentation or Teradata User Documentation CDs, include the
publication ID number. To locate a publication ID numbers, see “Publication Titles and IDs”
on page 154.
To order printed documentation or CDs
1
Go to www.info.teradata.com.
2
Under Print & CD Publications, click How to Order.
3
Follow the ordering instructions.
Orange Books
Orange Books enhance product-specific manuals by describing the best practices for
completing a task or solving a problem using the tools and features of one or more products.
The content is more technical than that found in white papers.
Orange Books are available to Teradata customers with a service contract, Teradata
Professional Services associates, and Teradata Customer Service associates. Teradata @ Your
Service membership is also required.
To access Orange Books
1
Go to Teradata.com.
2
From the Support Services menu, click Teradata @ Your Service.
3
Follow the instructions to log on or to register.
4
From the Teradata @ Your Service home page, type Orange Books in the Search
Knowledge box, and then click Search.
Teradata Tools and Utilities Release Definition
153
Chapter 3: Teradata Tools and Utilities Documentation
Publication Titles and IDs
Publication Titles and IDs
The following documents are available in support of Teradata Tools and Utilities Release 13.0.
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.
Table 66: Teradata Tools and Utilities 13.0 Documentation
Publication Type
Publication Title
Publication ID
Messages
B035-1096-098A
Teradata Tools and Utilities Release Definition
B035-2029-110C
Teradata Tools and Utilities Command Summary
B035-2401-088A
Teradata User Documentation
Teradata Database 13.0
Teradata Tools and Utilities 13.0
B035-1909-098D
Teradata Tools and Utilities Installation Guide for IBM z/OS
B035-2458-088A
Teradata Tools and Utilities Installation Guide for IBM z/VM
B035-2422-088A
Teradata Tools and Utilities Installation Guide for Microsoft Windows
B035-2407-088A
Teradata Tools and Utilities Installation Guide for UNIX and Linux
B035-2459-088A
General Reference
Installation Guides
Connectivity and Interface Tools
154
Basic Teradata Query Reference
B035-2414-088A
IBM CICS Interface for Teradata Reference
B035-2448-088A
IBM IMS/DC Interface for Teradata Reference
B035-2447-088A
Interactive Teradata Query Reference
B035-2451-088A
Interactive Teradata Query User Guide
B035-2452-088A
ODBC Driver for Teradata User Guide
B035-2509-088A
OLE DB Provider for Teradata Installation and User Guide
B035-2498-088A
Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems
B035-2417-088A
Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems
B035-2418-088A
Teradata Director Program Reference
B035-2416-088A
Teradata JDBC Driver User Guide
B035-2403-088A
Teradata Preprocessor2 for Embedded SQL Programmer Guide
B035-2446-088A
Teradata Tools and Utilities Release Definition
Chapter 3: Teradata Tools and Utilities Documentation
Publication Titles and IDs
Table 66: Teradata Tools and Utilities 13.0 Documentation (continued)
Publication Type
Publication Title
Publication ID
Teradata SQL Assistant for Microsoft Windows User Guide
B035-2430-088A
Teradata SQL Assistant/Web Edition User Guide
B035-2505-088A
Teradata Transparency Series/ Application Programming Interface User Guide
B035-2419-088A
Load and Unload Utilities
Teradata FastExport Reference
B035-2410-088A
Teradata FastLoad Reference
B035-2411-088A
Teradata MultiLoad Reference
B035-2409-088A
Teradata Parallel Transporter Operator Programmer Guide
B035-2435-088A
Teradata Parallel Transporter Reference
B035-2436-088A
Teradata Parallel Transporter User Guide
B035-2445-088A
Teradata Parallel Transporter Application Programming Interface Programmer
Guide
B035-2516-088A
Teradata Tools and Utilities Access Module Programmer Guide
B035-2424-088A
Teradata Tools and Utilities Access Module Reference
B035-2425-088A
Teradata Parallel Data Pump Reference
B035-3021-088A
Database and Query Management Tools
Teradata Administrator User Guide
B035-2502-088A
Teradata Dynamic Workload Manager User Guide
B035-2513-088A
Teradata Index Wizard User Guide
B035-2506-088A
Teradata Manager Installation Guide
B035-2402-088A
Teradata Manager User Guide
B035-2428-088A
Teradata Query Director User Guide
B035-2510-119A
Teradata Query Scheduler Administrator Guide
B035-2511-088A
Teradata Query Scheduler User Guide
B035-2512-088A
Teradata Statistics Wizard User Guide
B035-2503-088A
Teradata System Emulation Tool User Guide
B035-2492-088A
Teradata Visual Explain User Guide
B035-2504-088A
Teradata Workload Analyzer User Guide
B035-2514-088A
Storage Management Tools
Teradata Tools and Utilities Release Definition
155
Chapter 3: Teradata Tools and Utilities Documentation
Publication Titles and IDs
Table 66: Teradata Tools and Utilities 13.0 Documentation (continued)
Publication Type
Publication Title
Publication ID
Teradata Archive/Recovery Utility Reference
B035-2412-088A
Teradata Meta Data Services Installation and Administration Guide
B035-3118-088A
Teradata Meta Data Services Programmer Guide
B035-3047-088A
Teradata MDS
156
Teradata Tools and Utilities Release Definition
CHAPTER 4
Customer Assistance
To help you make the most of your Teradata system, trained professionals are available to
assist you. There are a number of training and support centers you can contact to learn more
about Teradata applications or to get help with your Teradata system. Assistance is also
available at www.Teradata.com/t/At-Your-Service.
Customer Education
Teradata Customer Education delivers training for your global workforce—from scheduled
public courses and customized on-site training to the latest E-learning solutions. For
information on the latest classes, schedules, and the Teradata Certification Program, go to the
Teradata Customer Education web site at: www.teradataeducationnetwork.com.
Customers and Teradata associates can enroll in classes online at
www.TeradataEducationNetwork.com, or by contacting the representative for your region.
To find the representative for your region, use the Contact Us link at the bottom of the
Teradata Education Network page.
Customer Support
Customer support is available around-the-clock, 7 days a week. Trained professionals at a
Remote Services Center (RSC) are available to assist you. To learn more about Teradata
Customer Services, go to Teradata @ Your Service at www.Teradata.com/t/At-Your-Service.
If you purchased an ESS (Enterprise System Support) support contract, a customized support
plan was created for you. Please refer to your support plan for contact information. In
addition, a unique PIN (Personal Identification Number) was given to your site. If you are an
ESS customer, you must contact the regional RSC to request support, and you must use your
PIN.
Note: PINs are not published; if you misplace your PIN, contact your account representative.
Teradata Tools and Utilities Release Definition
157
Chapter 4: Customer Assistance
Customer Support
158
Teradata Tools and Utilities Release Definition