Release Definition - Teradata Documentation

Teradata Database
Release Definition
Release 13.0
B035-1725-098K
June 2012
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, Active Enterprise Intelligence, Applications-Within, Aprimo, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast,
Gridscale, Managing the Business of Marketing, MyCommerce, Raising Intelligence, Smarter. Faster. Wins., SQL-MapReduce, Teradata
Decision Experts, "Teradata Labs" logo, "Teradata The Best Decision Possible" logo, "Teradata Raising Intelligence" logo, Teradata Source
Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and
other countries.
Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda
Access, Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and
Maximum Support are servicemarks of Axeda Corporation.
Data Domain, EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.
GoldenGate is a trademark of Oracle.
Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.
Intel, Pentium, and XEON are registered trademarks of Intel Corporation.
IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation.
Linux is a registered trademark of Linus Torvalds.
LSI is a registered trademark of LSI Corporation.
Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the
United States and other countries.
NetVault is a trademark or registered trademark of Quest Software, Inc. in the United States and/or other countries.
Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.
Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates.
QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation.
SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.
SPARC is a registered trademark of SPARC International, Inc.
Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States
and other countries.
Unicode is a registered trademark of Unicode, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN "AS-IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION
MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL,
OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
The information contained in this document may contain references or cross-references to features, functions, products, or services that are
not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features,
functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions,
products, or services available in your country.
Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or
updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this
information at any time without notice.
To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this
document. Please email: teradata-books@lists.teradata.com.
Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata
Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display,
transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis.
Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose
whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback.
Copyright © 1996 - 2012 by Teradata Corporation. All Rights Reserved.
Release Definition
Table of Contents
Introduction ...................................................................................................... 7
Audience ..................................................................................................................................................7
Supported Software Release ....................................................................................................................7
Revision History ......................................................................................................................................7
Additional Information ............................................................................................................................8
Release Numbering Changes ...................................................................................................................9
Understanding This Release ....................................................................................................................9
References to Supported Operating Systems .........................................................................................10
References to Teradata Platforms ..........................................................................................................10
Items Available with this Release ................................................................. 11
Software CD-ROMs/DVDs ...................................................................................................................11
Teradata Database Software CD-ROM/DVD ................................................................................... 11
Other Software CD-ROMs/DVDs .................................................................................................... 11
Bill of Materials ................................................................................................................................ 12
User Documentation CD-ROM .............................................................................................................13
Teradata Client Software .......................................................................................................................13
MultiTool .......................................................................................................................................... 13
Teradata .Net Data Provider Release 4.0 .......................................................................................... 13
Software and Hardware Requirements ....................................................... 14
Supported Operating Systems and Platforms ........................................................................................14
CD-ROM and DVD Drive ................................................................................................................ 14
Supported Third-Party SMP Platforms ..................................................................................................14
Restrictions ....................................................................................................................................... 15
SLES 64-Bit Specifications .............................................................................................................. 15
Windows Server 2003 64-Bit Specifications .................................................................................... 16
Coexistence and Coresidence Systems ..................................................................................................18
Teradata Platform Upgrades ..................................................................................................................18
Operating System Requirements............................................................................................................19
SLES 9 .............................................................................................................................................. 19
SLES 10 ............................................................................................................................................ 19
Windows Server 2003 64-Bit............................................................................................................ 19
Adding Microsoft Windows Hotfixes............................................................................................... 19
Installing Windows ProcExp, PsList, and WinObj Tools................................................................. 19
Mixed Operating Systems ......................................................................................................................20
Hot Standby Nodes ................................................................................................................................21
AWS Requirements ...............................................................................................................................21
AWS Operating System Requirement .............................................................................................. 21
AWS Configurations ......................................................................................................................... 22
AWS Software Requirements ........................................................................................................... 22
BIOS and Node Firmware for Teradata 5350 through Teradata Active EDW 5600 Nodes .................23
Page 3
Updated June 26, 2012
Release Definition
Node Memory Recommendations .........................................................................................................23
Existing Systems ............................................................................................................................... 23
New Systems ..................................................................................................................................... 24
Memory-Consuming Features ...............................................................................................................25
Disk Space Requirements ......................................................................................................................25
Additional Disk Space for Trace Files ...................................................................................................25
SWAP Space Requirements ...................................................................................................................25
MP-RAS............................................................................................................................................ 26
SLES ................................................................................................................................................. 26
External Disk Arrays..............................................................................................................................26
Backup and Restore (BAR) Requirements ............................................................................................27
Supported Hardware ......................................................................................................................... 27
Supported Software ........................................................................................................................... 27
Unloading the CRASHDUMPS Database ........................................................................................ 27
Compilers ...............................................................................................................................................28
Software Restrictions ..................................................................................... 29
Temporary Restrictions ..........................................................................................................................29
Object Name Limit ........................................................................................................................... 29
Amp Worker Task (AWT) Default ................................................................................................... 29
Global and Persistent Data Feature ................................................................................................... 29
GLOP Feature Usage .............................................................................................................................29
Geospatial Data Types ...........................................................................................................................29
Non-Certified Software ..........................................................................................................................30
Possible Errors in Certain SELECT Queries .........................................................................................30
Possible Result Overflow with SELECT Sum.......................................................................................30
System-Level Software Restrictions ......................................................................................................31
Security-Related Restrictions.................................................................................................................32
Logon Requirements Change for External User Authentication ...................................................... 32
New Mechanism for Logons through .Net Applications .................................................................. 32
LDAP Support .................................................................................................................................. 33
Kerberos Authentication Setup ......................................................................................................... 33
Kerberos Multiple LAN Adapter Restriction ................................................................................... 33
Distributing Edited Copies of TDGSS and TeraGSS Configuration Files ....................................... 34
Custom Authentication Mechanisms ................................................................................................ 34
Row Size and Data Type Widths Increase for the 64-bit Architecture..................................................34
Obsolete and Unsupported Utilities, Options, and Record Types .........................................................35
Teradata Virtual Storage ........................................................................................................................36
Changes in Behavior ...................................................................................... 37
Views and Derived Tables that Specify RADIANS or DEGREES Function .......................................37
Derived Tables That Specify Ambiguous Column Names ....................................................................38
Recompiling Stored Procedures .............................................................................................................38
System Tables and Views ......................................................................................................................38
Statistics Collection Incompatibility ......................................................................................................38
Teradata SQLRestrictedWords UDF Package .......................................................................................39
Creating Objects during an Online Archive...........................................................................................39
Updated June 26, 2012
Page 4
Release Definition
Installation, Upgrade, Migration, and Backdown (IUMB) ....................... 40
IUMB Release Requirements ................................................................................................................40
IUMB Planning ......................................................................................................................................40
Parallel Upgrade Utility (PUT) ......................................................................................................... 41
Windows Upgrade Restriction ...............................................................................................................41
Replication-Related Upgrades ...............................................................................................................41
Upgrading from Older Releases.............................................................................................................41
Operating System Upgrades ..................................................................................................................42
Returning to an Older Release ...............................................................................................................42
Retaining tdatuser and tdatudf for UDFs ...............................................................................................42
System Performance ...................................................................................... 44
Running Teradata Database with Other Applications ...........................................................................44
Software Maintenance Schedule .................................................................. 46
Maintenance Support .............................................................................................................................46
Teradata Database Maintenance Roadmap ............................................................................................46
User Documentation ...................................................................................... 47
Downloading a Document .....................................................................................................................47
Downloading a List of User Publications ..............................................................................................47
DRs and RFCs........................................................................................................................................48
Customer Education ...................................................................................... 49
Customer Support .......................................................................................... 50
Technical Alerts and Orange Books ......................................................................................................50
White Papers ..........................................................................................................................................50
List of Acronyms ............................................................................................ 51
Page 5
Updated June 26, 2012
Release Definition
Introduction
Audience
This document is intended for Teradata customers, field engineers (FEs), and support staff interested in
the requirements, dependencies, and support resources for Teradata Database.
Supported Software Release
This document supports Teradata® Database 13.0.
Revision History
Date
June 2012
March 2012
May 2011
February 2011
January 2011
Page 7
Description
• Added information on the need to rewrite certain SELECT queries to avoid non-deterministic
results in Possible Errors in Certain SELECT Queries.
• Added information on possible SQL problem in Possible Result Overflow with SELECT Sum.
• Added restriction on use of the Global and Persistent Data (GLOP) feature.
• Simplified platform listings for Hot Standby Nodes and External Disk Arrays.
• Removed the note from System Tables and Views.
• Revised Teradata Client Software. Removed the Limits to Compatibility with Older Teradata
Client Software topic and merged pertinent information into Teradata Client Software.
• Updated instructions for accessing the latest software versions required for AWS support.
• Removed obsolete information from Upgrading from Older Releases.
• Updated instructions on accessing the Teradata Maintenance Release Roadmap.
• Updated instructions for accessing the latest software versions required for AWS support.
• Replaced the Supported Operating Systems and Platforms table with a link to the Teradata
Platform and Minimum Database Version Compatibility Matrix.
• Updated service pack information for SUSE Linux Enterprise Server 10.
• Updated GLOP restrictions.
Updated June 26, 2012
Release Definition
Date
September 2010
March 2010
November 2009
August 2009
May 2009
Description
• For third party SUSE Linux Enterprise Server SMPs, clarified table headings and added SUSE
Linux Enterprise Server 10.
• Added pointers on where to find information on updates to system tables and views.
• Added information on statistics collection incompatibility and references to associated knowledge
articles/tech alerts.
• Added information on the Teradata SQLRestrictedWords UDF package.
• Added pointers to more information on creating objects during an online archive.
• Added ONE_DIMENSIONAL migration to the list of memory-consuming features.
• Added that GSS must approve implementation of Teradata Virtual Storage.
• Removed the known regression, as it was closed out long ago.
• Removed the NoPI tables restriction.
• Added a link to accessing platform documentation.
• Updated availability date for Replication Services.
• Added that stored procedures must be recompiled for this release.
• Updated platforms and BYNET requirements.
• Revised the restriction on hyper-threading support on third part SMP platforms.
• Added that the customer is responsible for procurement and support of third-party hardware and
operating system software.
• For SUSE Linux Enterprise Server 9, clarified that Service Pack 3 kernel 286 is required for all
nodes running Release 12.0.
• Updated the BAR supported hardware and software. Removed the Tape Backup topic.
• Clarified that Teradata supports customer-performed maintenance and patch upgrades.
• Clarified that you can migrate data from your current Teradata Database release to a later release
as long as you do not migrate across more than 2 major releases.
• Removed the reference to the Move operation for SUSE Linux Enterprise Server upgrades.
• Added a disclaimer on certified platforms and platform discontinuation.
• Updated Teradata platform names.
• Updated Teradata @ Your Service links. Changed TSS links to Teradata @ Your Service links.
• Updated the “New Mechanism for Logons through .Net Applications” section.
• Added a statement to clarify the difference between VARCHAR(128) and 30 bytes object name
limit.
• Clarified that it is mandatory to install a C++ compiler on at least one node configured with a PE
vproc.
• Updated how to find critical information on Teradata @ Your Service.
• Changed the Teradata University link to the Teradata Education Network link, and updated the
description.
First publication.
Additional Information
URL
http://www.info.teradata.com/
Updated June 26, 2012
Description
Use the Teradata Information Products site to:
• View or download a manual:
1. Under Online Publications, select General Search.
2. Enter your search criteria and click Search.
• Download a documentation CD-ROM:
Page 8
Release Definition
URL
http://www.teradata.com
http://www.teradata.com/t/TEN/
http://developer.teradata.com/
Description
1. Under Online Publications, select General Search.
2. In the Title or Keyword field, enter CD-ROM, and click Search.
• Order printed manuals: Under Print & CD Publications select How
to Order.
The Teradata home page provides links to numerous sources of information
about Teradata. Links include:
• Executive reports, case studies of customer experiences with Teradata,
and thought leadership
• Technical information, solutions, and expert advice
• Press releases, mentions and media resources
Teradata Customer Education designs, develops and delivers education that
builds skills and capabilities for our customers, enabling them to maximize
their Teradata investment.
Teradata Developer Exchange provides articles on using Teradata products,
technical discussion forums, and code downloads.
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: teradata-books@lists.teradata.com
Release Numbering Changes
As of release 12.0, Teradata adopted a single, unified numbering system for Teradata Database and all
associated tools and utilities. Teradata made this change to reduce the confusion caused in previous
releases by multiple numbering sequences. For example, the entire collection of Teradata products-including Teradata Database and Teradata Tools and Utilities--is now called Teradata 13.0.
Understanding This Release
Before you install or upgrade to this release of Teradata Database, you should read the following
publications.
Book
Release Definition
Description
Provides information about basic system requirements.
This revision of Release Definition is applicable to Teradata Database 13.0. It contains
references to features, functions, and requirements that may not apply to releases prior to 13.0.
Release Summary
Note: If you are upgrading from an older release of Teradata Database, you should read the
Release Definition for every intervening release.
Provides information on new features and changes to existing Teradata Database features that
may affect the way you use Teradata Database.
If you are upgrading from an older release of Teradata Database, you should also read Release
Summary for every intervening release to understand how the features in this release differ from
features in your current version.
Page 9
Updated June 26, 2012
Release Definition
Introduction to Teradata
Provides an overview of Teradata Database features, functions, and capabilities, If you are new
to Teradata Database, read this book before implementing this release.
You can access Teradata Database user documentation at:
http://www.info.teradata.com/
References to Supported Operating Systems
Unless more specificity is needed to identify differences in requirements, this book uses the following
conventions to refer to Teradata Database 13.0 supported operating systems.
Supported Operating System Name
MP-RAS 3.03
Windows Server 2003 R2 Enterprise (x64) Edition (64-bit)
• Novell SUSE Linux Enterprise Server 9 (64-bit)
• Novell SUSE Linux Enterprise Server 10 (64-bit)
Reference Used in this Book
MP-RAS
Windows Server 2003 64-bit
• SLES 9
• SLES 10
• SLES (where not version specific)
Note: The following operating systems are no longer supported by Teradata Database 13.0:
•
•
MP-RAS 3.02
Windows 2000; Windows Server 2003 (32-bit)
References to Teradata Platforms
Full Teradata Platform Name
Teradata Active Enterprise Data Warehouse 5550/5555/5600
Teradata Data Warehouse Appliance 2550/2555/2580
Teradata Extreme Data Appliance 1550/1555/1600
Teradata Data Mart Appliance 550
Updated June 26, 2012
Abbreviated Teradata Platform Name
Teradata Active EDW 5550/5555/5600
Teradata DW Appliance 2550/2555/2580
Same as full name
Teradata Data Mart 550
Page 10
Release Definition
Items Available with this Release
You can find additional software and software updates via Teradata @ Your Service:
http://www.teradataatyourservice.com/.
Software CD-ROMs/DVDs
Teradata Database Software CD-ROM/DVD
You will receive a Teradata Database software CD-ROM/DVD that includes one of the following
Teradata Database software variations based on your order:
•
•
•
Teradata Database for SUSE Linux Enterprise Server (SLES)
Teradata Database for MP-RAS
Teradata Database for Windows Server 2003 64-bit
Other Software CD-ROMs/DVDs
Based on your system requirements, other software CD-ROMs/DVDs may accompany your order.
Software
Operating system
Optional Teradata Tools
and Utilities
Administration
Workstation (AWS)
CD-ROMs
Includes one of the following sets (not supplied for non-Teradata SMPs):
• MP-RAS operating system (2 CD-ROMs)
• SLES 9 operating system, service packs, and third-party software
• SLES 10 operating system, service packs, and third-party software
One or more CD-ROMs depending on software purchased.
Two CD-ROMs.
Note: All required Windows operating system support software is included on the Teradata Database for
Windows Server 2003 64-bit CD-ROM, except the required C++ compiler. See Compilers for details.
Page 11
Updated June 26, 2012
Release Definition
Bill of Materials
Package Name
bteq
bteq130
BYNET (bynet)
cliv2
cliv2130
dul
dultape
ebcafw
fastId130
pbcafw
pbsa4fw
pbsafw
PDE
pdegpl
pdegplsrc
piom
piom130
ppc2fw
PUTJRE
PUTSRC
SM3G_KCS
sm3gnode
tchn
tchndiag
tchneipc
TDBMS
tdgss
tdicu
tdicu130
TDput
teradata-osutils
teradata-tas
teradata-tvia
TeraGSS
tgtw
TNT
TVIA
Windows TDput
WinTools
SLES 9
CD 1
X
CD 2
SLES 10
CD 1
X
X
CD 2
MP-RAS
CD 1
X
X
X
X
X
X
X
X
X
CD 2
Windows
CD 1
X
CD 2
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Updated June 26, 2012
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Page 12
Release Definition
User Documentation CD-ROM
You will receive user documentation on a CD-ROM entitled Teradata User Documentation: Teradata
Database 13.0 and Teradata Tools and Utilities 13.0 with your initial order or upgrade of Release 13.0
software.
Teradata Client Software
Customers with active Service Agreements can find information on Teradata Database and Teradata
Tools and Utilities release and client product compatibility in the Teradata Maintenance Release
Roadmap on Teradata @ Your Service (http://www.teradataatyourservice.com).
Customers without support agreements should contact their sales or support team.
Note: For detailed BAR compatibility information, see the BAR application software compatibility
matrix located at http://sl02.teradata.com/skb/i/S11000CFF6E.
For detailed information on the full range of tools and utilities, and the individual Teradata client
product versions compatible with Teradata Database 13.0, see Teradata Tools and Utilities 13.0 Release
Definition at http://www.info.teradata.com/.
MultiTool
The MultiTool software package is no longer supported.
Teradata .Net Data Provider Release 4.0
Sites that implement Teradata .Net Data Provider Release 4.0 on clients as they upgrade to Teradata
Database 13.0 may need to make minor changes to the system security setup, and to the logon options
offered to users.
Page 13
Updated June 26, 2012
Release Definition
Software and Hardware Requirements
Supported Operating Systems and Platforms
The platforms listed in this document are certified with Release 13.0, regardless of future platform
discontinuation notices. For more information on platform discontinuation, see the Knowledge Base
Tech Note entitled “Teradata Hardware Discontinuation Roadmap.” Note that this Knowledge Base
Tech Note is available to Teradata personnel only.
See KAP1B3136 “Teradata Platform and Minimum Database Version Compatibility Matrix” for the
minimum database/PDE version supported on a particular platform for specific operating systems.
For related information, see Teradata Platform Upgrades.
CD-ROM and DVD Drive
All systems need at least one CD-ROM drive to enable installation of Teradata Database software.
Existing systems need at least one DVD drive per cabinet to install Teradata Database for SLES.
A DVD drive is factory-installed on each new SLES Server platform:
Teradata SMP
• Teradata 540S
• Teradata Data Mart 550P/550S
Teradata MPP
• Teradata 5400E/5400H/5450E/5450H/5500
• Teradata DW Appliance 2550/2555/2580
• Teradata Active EDW 5550/5555/5600
• Teradata Extreme Data Appliance 1550/1555/1600
The customer is responsible for procurement and support of third-party hardware and operating system
software.
Supported Third-Party SMP Platforms
In addition to the Teradata platforms listed in the previous section, you can run Teradata Database 13.0
software on selected third-party Symmetric Multi-Processor (SMP) platforms.
These recommendations should result in a functional, reasonably performing system. System
performance is dependent on hardware and customer workload. Tuning for optimal performance can be
addressed through Teradata Services.
Updated June 26, 2012
Page 14
Release Definition
Restrictions
•
•
•
Third-party SMP platforms support no more than four processors, including hyper-threaded
processors.
Teradata Database for MP-RAS is not supported on third-party SMP platforms.
Channel connection is not supported for third-party SMP platforms. You can only use channel
connection with Teradata servers running Teradata drivers and adapters.
Important: The customer is responsible for all procurement and support of third-party hardware.
SLES 64-Bit Specifications
Component
Processors and Server
Technology
Operating System
Requirements
Operating System Disk
(Non-Database)
Teradata SMP
2 Intel Xeon EM64T CPU (3.4 GHz or
greater)
Teradata Data Mart Appliance
• 550: 1 or 2 Intel X
• eon EM64T Dual Core CPU (2.33GHz or
greater)
• 551: 1 Intel Xeon EM64T Quad Core CPU
(2.33GHz or greater)
Hardware must be certified with appropriate Novell 64-bit SLES release. Certified products
can be found at http://www.novell.com/, and the web site of the hardware manufacturer.
Teradata certified Novell operating
• 550: Teradata certified Novell operating
system version SLES 9 SP3 (Kernel
system version SLES 9 SP3 (Kernel 2.6.52.6.5-7.286 or later.
7.286 or later)
• 551: Teradata certified Novell operating
system version SLES 10 SP1 or SP3
Supported kernel versions are available via Teradata @ Your Service:
http://www.teradataatyourservice.com/
Memory size (540): Up to 8 GB: 1 x 73 GB mirrored set (2 disks)
Memory size (550):
• Up to 8GB: 1 x 73 GB mirrored set (2 disks)
• 8 to 16GB: 1 x 146 GB mirrored set (2 disks)
Memory size (551): Up to 32GB: 1 x 146GB mirrored set (2 disks)
Distribution Media
Page 15
Note the following:
• 20GB is reserved for Teradata Database.
• Write cache must be disabled on internal and external drives. Some drives with cache
enabled have a tendency to lock up, resulting in data corruption. Consult your hardware
documentation or check with your hardware vendor.
DVD
Updated June 26, 2012
Release Definition
Component
Database/Storage Disk
Teradata SMP
RAID1 recommended
Teradata Data Mart Appliance
Generally 4 disk drives are recommended for every unit of parallelization (VAMP). The
performance assumption for the disk drives is 15 MB per sec on a 96 K IO size, 80/20
read/write random workload.
Teradata Database supports Linux udev persistent device naming convention only.
Customer
SMP Server
PE
PE
Boardless BYNET
AMP
AMP
AMP
AMP
Storage
Interconnect
Disk
Storage
Disk
Storage
Disk
Storage
32 15K RPM disks to balance Teradata
Database with the I/O subsystem
Disk
Storage
•
•
Storage Host Bus Adapter
Minimum of one 4Gbps or two 2Gbps
fiber channel links to support 400 MB
per second
•
•
Remote Support
550: 48 15K RPM disks to balance Teradata
Database with the I/O subsystem (maximum
64 disks).
551: 64 15K RPM disks to balance Teradata
Database with the I/O subsystem (maximum
64 disks).
550: Minimum of two 4Gbps or four 2Gbps
fiber channel links to support 800MB per
second.
551: Minimum of four 4Gbps fiber channel
links to support 800MB per second.
Driver support for appropriate SLES kernel
• 1Gb Ethernet adapter in SMP node
• Windows PC with 1Gb Ethernet adapter
• VPN connection
• 4 mm SCSI DAT tape
Windows Server 2003 64-Bit Specifications
Component
Processors and Server
Technology
Memory
Operating System
Requirements
Updated June 26, 2012
Teradata SMP
2 Intel Xeon EM64T CPU (3.4GHz or
greater)
Teradata Data Mart Appliance
• 550P: 1 or 2 Intel Xeon EM64T Dual Core
CPU (2.33GHz or greater)
• 551P: 1 Intel Xeon EM64T Quad Core CPU
(2.33GHz or greater)
Hardware must be certified for Windows server 2003 64 bit
See Node Memory Recommendations.
See Operating System Requirements.
Page 16
Release Definition
Component
Operating System Disk
(Non-Database)
Teradata SMP
Teradata Data Mart Appliance
Memory size (540): Up to 8GB: 1 x 73 GB mirrored set (2 disks)
Memory size (550):
• Up to 8GB: 1 x 73GB mirrored set (2 disks)
• 8 to 16GB: 1 x 146GB mirrored set (2 disks)
Memory size (551): Up to 32 GB: 1 x 146GB mirrored set (2 disks)
Distribution Media
Database/Storage Disk
Note the following:
• 20GB is reserved for Teradata Database.
• Write cache must be disabled on internal and external drives. Some drives with cache
enabled have a tendency to lock up, resulting in data corruption. Consult your hardware
documentation or check with your hardware vendor.
DVD
RAID1 recommended
Generally 4 disk drives are recommended for every unit of parallelization (VAMP). The
performance assumption for the disk drives is 15MB per sec on a 96K IO size, 80/20
read/write random workload.
Customer
SMP Server
PE
PE
Boardless Bynet
AMP
AMP
AMP
AMP
Storage
Interconnect
Disk
Storage
Disk
Storage
Disk
Storage
32 15K RPM disks to balance Teradata
Database with the I/O subsystem.
Disk
Storage
•
•
Storage Host Bus Adapter
Minimum of one 4Gbps or two 2Gbps
fiber channel links to support 400MB
per second.
•
•
Remote Support
Page 17
•
•
•
•
550: 48 15K RPM disks to balance Teradata
Database with the I/O subsystem (maximum
64 disks).
551: 64 15K RPM disks to balance Teradata
Database with the I/O subsystem (maximum
64 disks).
550: Minimum of two 4Gbps or four 2Gbps
fiber channel links to support 800MB per
second
551: Minimum of four 4Gbps fiber channel
links to support 800MB per second.
1GB Ethernet adapter in SMP node
Windows PC with 1GB Ethernet adapter
VPN connection
4mm SCSI DAT tape
Updated June 26, 2012
Release Definition
Component
Authorized Hardware
Teradata SMP
Teradata Data Mart Appliance
To view the Microsoft authorized Windows hardware compatibility list (HCL):
1. Log onto: http://www.windowsservercatalog.com/.
2. From the Hardware Testing Status menu, select Servers.
3. Check the list to see if your hardware is approved for use with Windows 2003.
Also check the hardware vendor for operating system version compatibility requirements.
Coexistence and Coresidence Systems
You may already have a Teradata Database system and wish to add more nodes. Systems employing a
mixture of older and newer model hardware are referred to as coexistence or coresidence systems:
•
•
Coexistence allows different node models to operate together in the same system.
Coresidence allows different node types to operate together in the same cabinet.
Determining whether a node can coexist or coreside with another node depends on the performance
class, the operating system, and the installed version of BYNET on each one.
Documentation on coexistence and coresidence is not part of the standard user documentation set, and is
only available to Teradata personnel at http://infocentral.daytonoh.teradata.com/tsd-library/isupr.cfm.
Teradata Platform Upgrades
Some platforms can be upgraded to achieve higher performance. The following table shows approved
upgrade paths for Teradata platforms supported for this release.
Platform Model
Teradata 4950
Teradata 4980
Teradata 5300
Teradata 5350
Teradata 5380
Teradata 5400E
Teradata 5400H
Teradata 5450E
Teradata DW Appliance 2550, 2555
Teradata Active EDW 5500C
Teradata Active EDW 5500EC
Teradata Active EDW 5500EH
Teradata Active EDW 5500H/5550H, 5555C/5555H
Teradata Extreme Data Appliance 1550/1555
Updated June 26, 2012
Upgrade Path
Teradata 5350
Teradata 5380 (node replacement)
Teradata 5350 or 5380 (node replacement)
Teradata 5380 (node replacement)
N/A
Teradata 5400H, 5450E, 5450H
Teradata 5450H
Teradata 5450H
Teradata DW Appliance 2580
Teradata Active EDW 5500H, 5550H
Teradata Active EDW 5500C
Teradata Active EDW 5500H, 5550H
Teradata Active EDW 5600
Teradata Extreme Data Appliance 1600
Page 18
Release Definition
Note: Teradata 4900 and 5300 platforms must be upgraded as shown in the table above to support
Teradata Database 13.0.
Operating System Requirements
SLES 9
Service Pack 3 kernel 286 is required for all nodes running Release 13.0.
SLES 10
Release 13.00.00.025 and up is required for Service Pack 3.
Windows Server 2003 64-Bit
Service Pack 2 is required for all nodes running Release 13.0.
Notes:
•
•
Windows Server 2003 64-bit is delivered on the WS03 Service Pack 2 CD and the R2 New Features
CD.
Do not load the R2 features. Teradata Database is not certified to work with these optional features
installed.
Adding Microsoft Windows Hotfixes
You can access hotfixes via Teradata @ Your Service:
http:\\www.teradataatyourservice.com
Installing Windows ProcExp, PsList, and WinObj Tools
Install the Microsoft Windows ProcExp, PsList, and WinObj tools from the following URLs to the
primary distribution node. The customer is responsible for accepting the license agreement as part of the
installation.
•
•
•
ProcExp: http://www.microsoft.com. Search for download bb896653 (Process Explorer)
PsList: http://support.microsoft.com/kb/927229
WinObj: http://www.microsoft.com/technet/sysinternals/SystemInformation/WinObj.mspx
Page 19
Updated June 26, 2012
Release Definition
Mixed Operating Systems
A mixed operating system includes both Trusted Parallel Application (TPA) nodes and non-TPA nodes.
Following are the basic system requirements for mixed operating systems:
•
•
•
•
•
•
All operating systems supported for TPA nodes are also supported for non-TPA nodes. All TPA
nodes must run the same operating system, but you can mix non-TPA nodes in any combination of
the allowable operating systems. TPA nodes need not run on the same operating system as non-TPA
nodes.
MP-RAS non-TPA nodes can be converted to Windows or SLES non-TPA nodes if running on a
Teradata 54xx and up platform.
Mixed OS allows use of two consecutive generations of nodes/storage across TPA and/or non-TPA
nodes.
All external storage must be from the same vendor.
The same version of BYNET must be deployed across the system.
Teradata Active EDW 5600 only supports SLES 10 (SP1 or SP3).
The following requirements apply to mixed operating system implementation.
TPA Nodes
SLES
Non-TPA Nodes Allowed
Any combination of SLES, Windows Server 2003 32-bit,
Windows Server 2003 64-bit, and MP-RAS
MP-RAS
Windows Server
2003 64-bit
Any combination of Windows Server 2003 32-bit and MP-RAS
Any combination of Windows Server 2003 32-bit, Windows
Server 2003 64-bit, and SLES
Other Requirements
• PUT 3.04.06.22 or later
• Teradata AWS 4.1 or later
PUT 3.04.06.22 or later
• PUT 3.04.06.22 or later
• Teradata AWS 4.1 or later
You can either convert or replace existing MP-RAS non-TPA nodes with Windows 64-bit non-TPA
nodes.
Mixed operating systems are supported on the following platform groups:
•
•
•
•
•
Teradata 5350, 5380
Teradata 5400E/5400H, 5450E/5450H
Teradata 5500EC/5500EH, 5500C/5500H
Teradata Active EDW 5550H, 5555C/5555H
Teradata Active EDW 5600C/5600H
Allowable platform combinations are the same as those shown in coexistence and coresidence systems.
Mixed operating systems are not supported on earlier models because they do not support Windows
AWSs.
Exception: SLES and Windows Server 2003 64-bit are not supported on Teradata 49xx or 53xx nodes.
Updated June 26, 2012
Page 20
Release Definition
Hot Standby Nodes
A hot standby node is a node that is reserved for use as a backup node in case a TPA node fails. You can
use PUT to designate a node as either TPA or Hot Standby during Teradata Database software
installation. For more information, see Parallel Upgrade Utility (PUT).
The hot standby nodes feature (maximum one node per clique) is only supported on new system
installations of Teradata Database or new coexistence nodes.
Storage requirements for hot standby nodes are the same as for normal database nodes.
For detailed node/storage compatibility requirements, see External Disk Arrays.
Operating System
MP-RAS
SLES 9
SLES 10
Teradata MPP
Teradata Active EDW 5350 through 5555
Teradata Active EDW 5400 through 5555
Teradata Active EDW 5400 and up
BYNET Version
V2 or V3
V3
V3
SLES 10
BYNET Protocol Emulation (BPE)
over 1Gb Ethernet or V4 > 46 nodes
SLES10
• Teradata Active EDW 2550 through 2650
• Teradata Extreme Data Appliance 1xxx
Teradata DW Appliance 4600
SLES10
Windows Server 2003 64-bit
Teradata Active EDW 5600 and above
Teradata Active EDW 5450 through 5555
BPE over 10 Gb Ethernet or V4 > 46
nodes
V4 > 46 nodes
V3
Teradata Extreme Data Appliance 1600 and Teradata Active EDW 5600 support hot standby nodes, but
the Teradata DW Appliance 2580 does not.
AWS Requirements
An AWS is required for every Massively Parallel Processing (MPP) system.
For information on AWS configuration requirements, see the spreadsheet under Software and Hardware
Requirements.
AWS Operating System Requirement
For systems that use the following platforms running Teradata 13.0, the AWS must run Windows Server
2003 32-bit with AWS 4.5 or later software, because these platforms do not support an AWS running on
MP-RAS or Windows 2000:
•
•
•
Teradata Extreme Data Appliance 1550/1555/1600
Teradata DW Appliance 2550/2555/2580
Teradata 5400/5450/5500
Page 21
Updated June 26, 2012
Release Definition
•
Teradata Active EDW 5550/5555
Note: Teradata Active EDW 5600 supports SWS.
Systems that run on older Teradata 5350/5380 node hardware still support an AWS running on MP-RAS
or Windows 2000.
AWS Configurations
The following AWS configurations are supported for this release.
Operating System
SLES
MP-RAS
Windows Server 2003 64-bit
Allowable AWS Configuration
Teradata AWS on Windows Server 2003 32-bit
•
MP-RAS 3.02 or 3.03 AWS (not with Teradata 5400/5450/5500 or Active EDW
5550/5555/5600 database nodes)
•
Teradata AWS on Windows 2000 (not with Teradata 5400/5450/5500 or Active
EDW 5550/5555/5600 database nodes)
•
Teradata AWS on Windows Server 2003 32-bit Standard Edition
Teradata AWS on Windows Server 2003 32-bit Standard Edition
AWS Software Requirements
You must install software to support the AWS on all MPP systems installing or upgrading to this
release. Most of the required software packages are contained on the Teradata Database software CDROM. However, software requirements vary depending on the combination of operating systems
running on the AWS and Teradata Database nodes.
To access the latest software versions required for AWS support, arranged by AWS/node operating
system combination, go to Teradata @ Your Service (http:\\www.teradataatyourservice.com). Select
Downloads, and then select the Certified tab.
Note: Upgrading an AWS from AWS 4.3 or before requires that you follow the procedure documented
in KAP19B222, available via:
http://pc03.teradata.com/support/general/newcase.nsf/0/4e89181c2f35e6de8525748a0073fb39?OpenDo
cument&highlight=KAP19B222
Updated June 26, 2012
Page 22
Release Definition
BIOS and Node Firmware for Teradata 5350
through Teradata Active EDW 5600 Nodes
Use TDC M-PCD 01.02.06 or later on MP-RAS, Linux, and Windows systems to meet minimum BIOS
and related node firmware requirements. For further information, see Multi-Platform CD and Service
Partition User Guide, B035-5535-019K.
For Teradata Active EDW 5600 nodes, see the latest Teradata BIOS Configuration Guide for Intel
Baseboard S5520UR (B035-5358) for BIOS and firmware requirements located at the following link
under 5600:
http://infocentral.daytonoh.teradata.com/tsd-library/iPlatform.cfm
Node Memory Recommendations
Release 13.0 generally supports continuing operation of the existing database configuration with the
existing node memory. However for best performance, Teradata recommends that each node should
have at least the minimum random access memory (RAM) shown in the table below.
Existing Systems
Operating System
MP-RAS
SLES
Minimum RAM Per SMP
• 4 GB for Teradata 540/Teradata Data
Mart 550 class
• 2 GB, 3 GB, or 4 GB for older
Teradata SMPs, depending on
platform
• 6 GB for Teradata 540 class
• 8 GB for Teradata Data Mart 550 class
Minimum RAM Per MPP
2 GB, 3 GB, or 4 GB for older Teradata MPPs,
depending on platform
•
•
•
•
•
•
•
Windows Server
2003 64-bit
Page 23
•
•
6 GB for Teradata 540 class
8 GB for Teradata Data Mart 550 class
•
•
•
•
•
•
6 GB for Teradata 5400 class
8 GB for Teradata 5500 class
16 GB for Teradata Active EDW 5550 class
32 GB for Teradata Active EDW 5555 class
48 GB for Teradata Active EDW 5600 class
(supports up to 96 GB)
32 GB for Teradata Extreme Data Appliance
1550/1555
48 GB for Teradata Extreme Data Appliance
1600
32 GB for Teradata DW Appliance 2550/2555
96 GB for Teradata DW Appliance 2580
6 GB for Teradata 5400 class
8 GB for Teradata 5500 class
16 GB for Teradata Active EDW 5550 class
32 GB for Teradata Active EDW 5555 class
Updated June 26, 2012
Release Definition
Note: The memory recommendations shown are for systems using Teradata platforms. For memory
requirements on third-party SMP platforms, see Supported Third-Party SMP Platforms.
While this release can run on a system with the recommended minimum RAM, the small memory might
compromise performance, depending on the configuration of your system and the Teradata Database
features you use. Determining the appropriate amount of memory for your particular system requires
that you factor in the following to make the optimum choice:
•
•
•
Workload
Performance requirements
Cost of memory
New Systems
All new 64-bit MPP systems are configured as follows:
64-Bit MPP System
Teradata 5400/5450
Teradata 5500
Teradata Active EDW 5550
Teradata Active EDW 5555/5600
Teradata Extreme Data Appliance 1550/1555
Teradata Extreme Data Appliance 1600
Teradata DW Appliance 2550/2555
Teradata DW Appliance 2580
Memory per Node
6 GB
8 GB
16 GB
48 GB (the 5600 supports up to 96 GB)
32 GB
48 GB
32 GB
96 GB
Since May 1, 2004, all new 32-bit MPP systems have been factory-configured with 4 GB of memory per
node. The memory is included in the cost of the node. SMP systems can be configured with less than the
standard configuration and non-TPA 32-bit Windows nodes can be configured with up to 6 GB of
memory.
For SMP systems that will be deployed to support a traditional data warehousing workload, that is,
strategic decision support with bulk loading of data, 3 GB is the minimum recommended memory.
However, you might want to take into account that to upgrade memory to 4 GB later would require
system downtime and potential part swaps, both of which could be more costly than simply purchasing 4
GB initially. Teradata recommends you install 4 GB.
The recommended memory per node is 4 GB for systems that will be deployed to support an active data
warehouse, which by definition includes both traditional data warehousing with bulk data loading and
tactical/event driven decision making with continuous feeding of data.
Updated June 26, 2012
Page 24
Release Definition
Memory-Consuming Features
Be aware that the following features may require more memory to perform optimally:
•
•
•
•
•
•
•
•
•
•
•
LOBs and UDFs (first available in V2R5.1)
PPI and multi-value compression (first available in V2R5.0)
Join index, hash-join, stored procedures, and 128K data blocks (available prior to V2R5.0)
Cylinder read (first available in V2R5.0)
1 MB response buffer (first available in V2R6.0)
Larger than 1 MB plan cache (first available in V2R6.0)
External stored procedures (first available in V2R6.0)
Table functions (first available in V2R6.0)
Array INSERT (first available in V2R6.0)
Java stored procedures (available in Release 12.0)
ONE_DIMENSIONAL migration
Disk Space Requirements
For information on the amount of free disk space required on each Teradata Database node to upgrade to
this release, see Teradata Knowledge Article IDA00108C82.
Additional Disk Space for Trace Files
The Write Ahead Logging (WAL) feature requires 5 MB per AMP of disk space for File System trace
files. For example, if there are 10 AMPs per node, then trace files require 50 MB per node of additional
disk space, located as shown in the following table.
Operating System
SLES
MP-RAS
Windows
Trace File Space Location
/var/opt/teradata/tdtemp
/nssoft/tpi-data
C:\Program Files\NCR\TDAT\tdtemp
Note: Replace C if Teradata Database is installed on a different drive.
SWAP Space Requirements
Use these formulas to determine the total amount of required SWAP space.
Page 25
Updated June 26, 2012
Release Definition
MP-RAS
SWAP space (MB) ≥ 200 + (Number of AMPs X 132) + (Number of PEs X 324)
SLES
SWAP space ≥ 2 GB for each one of the first 2 gigabytes of memory (4 GB) + 1 GB for each GB of
memory thereafter.
Examples
6 GB memory requires (2 x 2 GB) plus (4 X 1 GB) = 8 GB swap space
8 GB memory requires (2 x 2 GB) plus (6 X 1 GB) = 10 GB swap space
External Disk Arrays
Disk Array
Supported Platform
SLES
MP-RAS
EMC2 6276/6278
EMC2 6290-843X
EMC2 6290-853X
EMCC 6291-0801
EMC2 6291-1000
EMCC 6291-1001
EMCC 6291-1002
EMCC 6291-1003
EMCC 6291-200x
EMC 6293-300x
EMC 6294-300x
EMC 6295-400x
6284 Deskside
6287 Deskside
All Teradata 52xx/53xx
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata 540S
• Teradata 540S
• Teradata Data Mart 550S/550P
Teradata Data Mart 551P
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
N/A
N/A
N/A
N/A
N/A
N/A
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Windows Server
2003 64-bit
N/A
N/A
N/A
N/A
N/A
N/A
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
N/A
N/A
Yes
N/A
Yes
Yes
Yes
N/A
N/A
Yes
Yes
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Teradata Active EDW 5400 and above
Yes
Yes
Yes
Yes
Yes
N/A
Yes
Yes
N/A
6287 Deskside
WES 6840
Teradata 6841-2456
Teradata 68416456/7456
Teradata 6841
Teradata 6842
Teradata 6843
Updated June 26, 2012
Page 26
Release Definition
Disk Array
Supported Platform
SLES
MP-RAS
Teradata 6844
Teradata Active EDW 56xx
Yes
N/A
Windows Server
2003 64-bit
N/A
Notes:
•
•
•
The Teradata DW Appliance 2550 and higher platforms are bundled with storage media and are not
separately configurable.
All supported external disk arrays are compatible with both RAID 1 and RAID 5, except Teradata
DW Appliance 2550/2555/2580 platforms, which do not use external disk arrays and therefore do
not support RAID 5.
Teradata 6844 does not support RAID 5.
Backup and Restore (BAR) Requirements
Supported Hardware
•
•
•
•
•
•
9200 SL500
9202 SL8500
9208 SL3000
9209 Key Management System Tape Encryption
9205 EMC Disk Library
9211 Teradata Managed Server for BAR
Supported Software
Vendor
BakBone
Symantec
IBM
Required
NetVault 8.2.x
NetBackup 6.5
Tivoli 6.1
Other Supported Options
NetVault 7.4.x
NetBackup 6.0
• Tivoli 5.5
• Tivoli 5.4
Unloading the CRASHDUMPS Database
On MP-RAS systems, either dul or dultape is required to unload the CRASHDUMPS database. For
information on handling crash dumps, see Database Administration.
For information on backup/restore software products compatible with this release, see Open Teradata
Backup Release Definition for Teradata Tools and Utilities, available from:
http://www.info.teradata.com/
Page 27
Updated June 26, 2012
Release Definition
Compilers
You must install a C++ compiler on at least one node configured with a PE vproc. Add or upgrade a
C++ compiler according to the following guidelines:
•
•
MP-RAS, SLES 9 and SLES 10 C++ compilers are included with each release. The GNU Compiler
Collection (GCC) version 4.0 is compatible with SLES 9.
Windows Server 2003 64-bit C++ compilers are not included with this release. If a compatible
compiler is not already installed, customers must download one of the following Visual Studio 2005
compiler versions from the Microsoft web site:
o Standard Edition
o Professional Edition
o Team Edition
Note: Microsoft does not include ml64.exe in the 64-bit Windows Platform SDK (included with C++
compilers), but it is required for stored procedures compilation. Customers who require compilation of
stored procedures on 64-bit Windows platforms must obtain ml64.exe directly from Microsoft.
Updated June 26, 2012
Page 28
Release Definition
Software Restrictions
Temporary Restrictions
The following restrictions are temporarily in effect and will be lifted in a later release.
Object Name Limit
The VARCHAR(128) object name limit is reserved for future expansion. The internal object name limit
is still 30 bytes in the Latin, Kanji1, or server character sets. See Names in SQL Fundamentals for
additional information.
Amp Worker Task (AWT) Default
The AWT default remains at 80 for initial releases of Teradata Database 13.0. The upper limit will
change to between 120 and 150, depending on final test results, in a future 13.00.xx maintenance
release.
Global and Persistent Data Feature
The Global and Persistent Data (GLOP) feature is available only on SLES.
GLOP Feature Usage
The Global and Persistent Data (GLOP) feature may cause the database to hang when used in a UDF in
certain high-concurrency situations. To avoid possible database hangs, do not execute the DIPGLOP
script to enable GLOP unless you plan on using GLOP as part of SAS services.
Note: Sites already using GLOP with SAS embedded services, for example, SAS Analytics Accelerator,
are unaffected by this problem and can continue use of the feature.
Geospatial Data Types
Geospatial data types, introduced in Release 13.0, are not supported on MP-RAS. Similar functionality
is still available for such systems through the use of user-defined functions (UDFs).
Page 29
Updated June 26, 2012
Release Definition
Non-Certified Software
It is strongly recommended that customers do not install non-certified software on a Teradata Database
node running Microsoft Windows. The interaction of non-certified Windows applications with the
parallel operation of the database will in some cases result in system failure and invalidation of the
customer service contract. Certified software is only the software advertised as part of a Teradata
Database solution.
Possible Errors in Certain SELECT Queries
Teradata Database may erroneously allow invalid SQL syntax in certain types of SELECT queries.
For example, given the table definitions:
CREATE TABLE t1(a1 int, b1 int, c1 int, d1 int);
CREATE TABLE t2(a2 int, b2 int, c2 int, d2 int);
The following invalid query syntax is currently allowed by Teradata Database:
SELECT min(a1) as i, max(b1) as j from t1
GROUP BY c1
HAVING 30 >= (sel count(*) from t2 where t1.d1=5);
The example query syntax uses the outer expression t1.d1 (which appears non-aggregated) inside a subquery in the HAVING clause. Because a non-GROUP BY column reference can return any value for a
given group, this syntax may cause the query to return non-deterministic results.
Error checking will be enhanced to disallow this syntax in a future Teradata Database release.
To avoid possible non-deterministic results, you should rewrite any queries that use the format shown in
the preceding example to use the following form:
SELECT min(a1) as i, max(b1) as j from t1
GROUP BY c1, d1
HAVING 30 >= (sel count(*) from t2 where t1.d1=5);
Possible Result Overflow with SELECT Sum
When using an Aggr Sum, Csum, Msum, or Windows Sum, the result can create an overflow depending
on how the type and format are defined for the queried table. For example:
CREATE Multiset TABLE t2
Updated June 26, 2012
Page 30
Release Definition
(
Salary DECIMAL(8,2) FORMAT 'ZZZ,ZZ9.99' )
PRIMARY INDEX ( Salary );’
INSERT INTO t2 (999999);
INSERT INTO t2 (999999);
…
The overflow occurs for a sum on the Salary (decimal operand) column because Decimal Sum resultant
data type and format are not in sync, for example:
SELECT Sum(Salary) FROM t2;
Sum(Salary)
----------**********
This happens because the Decimal Sum Resultant datatype and format are not in sync.
SELECT Type(Sum(Salary)) FROM t2;
Type(Sum(Salary))
--------------------------------------DECIMAL(15,2)
DECIMAL(15,2)
SELECT Format (sum(salary)) FROM t2;
Format(Sum(Salary))
-----------------------------ZZZ,ZZ9.99
ZZZ,ZZ9.99
To avoid possible overflows, construct the query to specify a format large enough to accommodate the
Decimal Sum resultant data type, for example:
SELECT Sum(Salary) (Format ‘$Z,ZZZ,ZZZ,ZZ9.99’) FROM t2 ;
System-Level Software Restrictions
•
•
•
•
Only one instance of the Teradata Database is supported on a system.
Teradata Tools and Utilities, including utilities running on mainframes, must be installed at or
upgraded to Teradata Tools and Utilities 13.0 to take advantage of all Teradata Database 13.0
features and functions.
Teradata client software is licensed on a per-node basis. A license for Teradata Tools and Utilities
software should be purchased for each node that has a Teradata Database license.
For coexistence and coresidence systems, all nodes within a single MPP system must run the same
version of the operating system and the Teradata Database software.
Page 31
Updated June 26, 2012
Release Definition
•
•
•
•
For additional restrictions, dependencies, and performance considerations when running the Teradata
Database applications, see Running Teradata Database with Other Applications.
Backup and restore management utilities are not provided as part of Teradata Database but are
available as separate products. For further information, see Open Teradata Backup Release
Definition for Teradata Tools and Utilities, available from the Teradata Information Products web
site at http://www.info.teradata.com/.
A maximum of 1200 concurrent sessions from LAN connections are allowed per node.
Mainframe channel connections allow a maximum of 120 sessions per connection, with a limit of 8
channel connections per adapter. This may be further limited by the number of available slots in the
node.
Security-Related Restrictions
Only the following directories are certified for use with this release.
•
•
•
•
Active Directory
Active Directory Application Mode (ADAM)
Sun Java System Directory Server version 5.2
Novell eDirectory
Note: Integration of other LDAPv3-compliant directories with Teradata Database requires assistance
from Teradata Professional Services
Logon Requirements Change for External User Authentication
Beginning with Release 12.00.00.12, external user authentication no longer requires submittal of user
credential information in the .logdata statement of the logon string. Users are now able to enter
username and password information in the .logon statement for all logon types, with some restrictions.
Teradata Database continues to allow submittal of credential information for external authentication in
the .logdata statement to minimize the impact on applications and individuals already using the .logdata
method. For more information, see Security Administration.
Note: Logons that specify additional information, such as user=, realm=, or profile=, must still use the
.logdata method.
New Mechanism for Logons through .Net Applications
For Teradata Database 13.0, users that log on through .Net applications can no longer use the KRB5 or
NTLM authentication mechanisms. On systems that implement .Net Data Provider for Teradata
Database Release 12.0 and up, users that log on through .Net applications can no longer use the KRB5
or NTLM authentication mechanisms.
Updated June 26, 2012
Page 32
Release Definition
Sites that use Kerberos authentication for Single Sign-on (SSO) or Sign-on As logons must use the new
SPNEGO mechanism on clients configured with .Net Data Provider for Teradata Release 12.0 and up.
NTLM authentication is not supported for logons from .Net managed clients.
The following table provides configuration requirements for Teradata Database on different operating
systems.
Operating System
Linux and MP-RAS
Windows
Description
You must manually add the SPNEGO mechanism to the TdgssUserConfigFile.xml on every
Teradata Database node, and on the Query Directory (if applicable), to enable it for use.
The SPNEGO mechanism is enabled by default.
Note: Although Teradata SQL Assistant 13.0 requires installation of Teradata .Net Data Provider, the
presence of this combination by itself does not require use of the SPNEGO mechanism. SPNEGO is
required only for logons from clients fully managed by .Net.
For more information on SPNEGO configuration and use, see Security Administration.
LDAP Support
Beginning with Teradata Database 12.00.00.12, the Teradata client interface to LDAP directories
changed. As a result of this change, administrators may need to make minor changes to the LDAP
configuration and to the logon options available to users, depending on the current system configuration.
For more information, see Security Administration.
Kerberos Authentication Setup
KRB5 (Kerberos) authentication, which can be used for single sign-on and Sign-on As logons, is now
available for use with Teradata Database running on SLES 10 or MP-RAS 3.03, but only after you
execute the special setup procedure provided in Security Administration.
This feature is not available on SLES 9.
Kerberos Multiple LAN Adapter Restriction
Kerberos authentication using the KRB5 or SPNEGO mechanisms may fail when clients try to connect
to servers with more than one LAN adapter. For proper function of Kerberos authentication, the
Teradata Database servers can have only one LAN adapter and the machine name must correspond to
the host name associated with the target adapter.
If you decide to continue using multiple LAN adapters, you may find it useful to disable the KRB5 and
SPNEGO mechanisms. Note that this may eliminate the use of Kerberos-dependent logon features, such
as Single Sign-on and Sign-on As.
Page 33
Updated June 26, 2012
Release Definition
Distributing Edited Copies of TDGSS and TeraGSS Configuration Files
If you are upgrading or migrating from V2R6.1.X or earlier, there is a new procedure for making
TDGSS configuration changes on Teradata Database servers and TeraGSS configuration changes on
clients. For more information, see Security Administration.
Custom Authentication Mechanisms
You must purchase the Teradata Security Software Developer’s Kit to develop and deploy a custom
authentication mechanism for use with this release.
Development and deployment of a custom authentication mechanism creates a custom encryption
software product. Distribution of a custom encryption product outside the U.S. and Canada is regulated
by the U.S. Department of Commerce (DOC). An export authorization must be filed for and obtained
from DOC in order to export such custom products. For information on obtaining an export
authorization, please see the DOC web site at http://www.bis.doc.gov/encryption/default.htm.
If additional information is required, customers should contact their local Teradata representative.
Teradata representatives needing help should contact Corporate Export Compliance in the Law
Department in WHQ.
Row Size and Data Type Widths Increase for the
64-bit Architecture
Customers migrating data form Teradata Database on MP-RAS or Windows Server 2003 32-bit to SLES
or Windows Server 2003 64-bit should be aware that some data type widths and row header fields have
expanded to accommodate the 64-bit architecture.
A pilot project using the largest 6 of the 8 tables from the Transaction Processing Council TPC-H
benchmark suite indicated an average row size increase ranging from 2.6% to 4.9%, but studies with
more realistic customer data in the field indicate that the identical row on a 64-bit system is likely, on
average, to increase 7% over its size on a 32-bit system.
The following fields cause a 2-byte overhead in the 64-bit row format.
Field Type
DAY TO SECOND
MINUTE TO SECOND
SECOND
TIME
TIMESTAMP
Updated June 26, 2012
Required Size
10
6
6
6
10
Alignment
4
4
4
4
4
Allocated Size
12
8
8
8
12
Page 34
Release Definition
The following table lists the predefined data types that have different sizes for 32-bit and 64-bit
architectures. If a data type is not listed in the table, its size is identical for 32-bit and 64-bit systems.
Data Type
TIME
TIME WITH TIMEZONE
TIMESTAMP
TIMESTAMP WITH TIMEZONE
INTERVAL YEAR
INTERVAL YEAR TO MONTH
INTERVAL MONTH
INTERVAL DAY
INTERVAL DAY TO HOUR
INTERVAL DAY TO MINUTE
INTERVAL DAY TO SECOND
INTERVAL HOUR
INTERVAL HOUR TO MINUTE
INTEVAL HOUR TO SECOND
INTERVAL MINUTE
INTERVAL MINUTE TO SECOND
INTERVAL SECOND
Alignment
4
4
4
4
2
2
2
2
2
2
4
2
2
4
2
4
4
32-Bit Size (Bytes)
6
8
10
12
2
4
2
2
4
8
10
2
4
8
2
6
6
64-Bit Size (Bytes)
8
8
12
12
2
4
2
2
4
8
12
2
4
8
2
8
8
Obsolete and Unsupported Utilities, Options, and
Record Types
Utility
dbscontrol
dbscsp
DUL/DULTAPE
Filer
gdoviewer
gtwcontrol
rcvmanager
tdssearch
xschmon
vpacd
Page 35
Description
SHAPasswordEncryption field is obsolete.
The dbscsp tool, used on MP-RAS systems only, is no longer supported. The executable
/usr/ntos/bin/dbgcsp now links to fdlcsp instead of dbscsp.
dbs64 option is no longer necessary, because DUL now detects the type of database
automatically.
• CSA WAL log record type is not supported.
• /V option of the FIB command is not supported.
Utility is unsupported.
Removed -b option. Deprecated logons are no longer allowed.
F7 help is not available.
Due to limited functionality, tdssearch has been replaced by ldapsearch, which is included with
Teradata Database 13.0.
Utility is no longer supported.
For older hardware, rarely used. Will not be used by new customers unless it is ported to openPDE (Linux).
Updated June 26, 2012
Release Definition
Teradata Virtual Storage
GSS must approve implementation of Teradata Virtual Storage (VS).
Customers may not use Teradata VS without a separately purchased license. Customers should contact
their Teradata sales representative to purchase and enable Teradata VS. The fact that this feature may be
included in product CDs or downloads, or described in documentation that customers receive, does not
authorize them to use it without purchasing the appropriate license.
Updated June 26, 2012
Page 36
Release Definition
Changes in Behavior
Views and Derived Tables that Specify RADIANS
or DEGREES Function
This release fixes a precision error where the RADIANS or DEGREES function in the select list of a
derived table or view definition produced a different result from the same RADIANS or DEGREES
function in the select list of a simple SELECT statement.
If you have views that specify the RADIANS or DEGREES function, recreate the view using the
REPLACE VIEW statement to avoid the precision error. For example, consider the following view
definition:
CREATE VIEW calc_view ( i ) AS
SELECT RADIANS ( i ) FROM angles_table;
To avoid the precision error, recreate the view as follows:
REPLACE VIEW calc_view ( i ) AS
SELECT RADIANS ( i ) FROM angles_table;
Queries that select from the view, or a similarly specified derived table, may produce results that are
different from earlier releases.
Suppose angles_table.i has the following value:
i
------30.
In earlier releases, queries of the following form produced erroneous results because the result of the
RADIANS function was different for each occurrence:
(SELECT RADIANS ( i ) FROM angles_table)
MINUS
(SELECT i FROM calc_view);
(1.74532925199433E-002*i)
------------------------5.23598775598299E-001
In this release, the query returns no rows because the result of the RADIANS function is now the same
for each occurrence.
Page 37
Updated June 26, 2012
Release Definition
Derived Tables That Specify Ambiguous Column
Names
In the past, derived tables that specified ambiguous columns would execute if they were spooled instead
of returning a 3809 error. A 3809 error was only returned if the query was not spooled. This behavior is
not correct.
In this release, a query that specifies ambiguous column names in a derived table always returns a 3809
error, even if the query ran successfully in earlier releases.
Recompiling Stored Procedures
You must recompile stored procedures when you upgrade or migrate to Release 13.0.
System Tables and Views
Some Teradata Database releases make changes to system tables and views.
•
•
See "Changes to this Book" in Data Dictionary for a list of changes to system tables and views for
this release.
See Tech Alert 2288 for changes to system views in maintenance or efix releases.
Statistics Collection Incompatibility
Due to extrapolation logic enhancements, the statistics collected on Release 13.0.0.22 and above are
incompatible on Release 13.0.0.19 or lower. Statistics collected on Release 13.0.0.19 or lower can be
handled by Release 13.0.0.22 or higher.
For more information and workarounds, see the following at Teradata @ Your Service
(http://www.teradataatyourservice.com/):
•
•
•
•
KAP1AF27E/Tech Alert 2235
KAP1AEB6A/Tech Alert 2275
KAP1AED4E/Tech Alert 2287
KAP1B06AA/Tech Alert 2320
Updated June 26, 2012
Page 38
Release Definition
Teradata SQLRestrictedWords UDF Package
You can now obtain a Restricted Words list from Teradata Database for any supported release.
Restricted words include Teradata reserved words, Teradata non-reserved words, and Teradata future
reserved words. To download the Teradata SQLRestrictedWords UDF package, and for information on
setting up your system and obtaining the Restricted Words list, go to http://developer.teradata.com/.
Creating Objects during an Online Archive
You can create objects when online archive logging is enabled. You can also FastLoad a table when
online archive logging is enabled.
For more information, see the Release 12.0 versions of these books:
•
•
•
Database Administration
Database Design
SQL Data Definition Statements
Page 39
Updated June 26, 2012
Release Definition
Installation, Upgrade, Migration, and
Backdown (IUMB)
Teradata supports customer-performed maintenance and patch upgrades. Contact your sales or customer
support representative (CSR) for questions.
For changes in behavior that impact upgrade or migration, see Changes in Behavior.
IUMB Release Requirements
Teradata Database 13.0 supports the following IUMB activities:
•
•
•
Installation on all supported platforms and operating systems
Direct upgrade from Release 12.0 and up. For information on upgrades from older releases, see
Upgrading from Older Releases.
Migration from V2R6.0.x and later.
IUMB Planning
•
•
•
•
•
•
Refer to the planning section in each IUMB manual, and perform all preparatory activities before
beginning any IUMB procedure. IUMB manuals are available to Teradata personnel only.
Some installation, upgrade, and migration procedures are operating system-specific. Use the IUMB
document appropriate to your operating system on http://infocentral.daytonoh.teradata.com/tsdlibrary/isupr.cfm (this site is available to Teradata personnel only).
Minimum starting versions (efix levels) for an upgrade are contained in Knowledge Article
IDA00108C82 in Teradata @ Your Service (http://www.teradataatyourservice.com/). If your current
Teradata Database version is not listed as an approved upgrade starting version, you must first
upgrade to an approved starting version before upgrading to this release. Contact the Teradata
Support Center for details.
Upgrade scripts and upgrade estimator tool are available from http://www.teradata.com. The scripts
include the Reserved Word scripts and other inspection scripts you must run before the upgrade or
migration.
Teradata @ Your Service (http://www.teradataatyourservice.com/) provides access to copies of other
items required for IUMB procedures such as:
o The Certified List of software packages for each supported Teradata Database version,
including recently updated versions of software packages
o Required application and operating system software patches, firmware, drivers, service packs
and hotfixes.
You must upgrade your Teradata Client software before or at the same time as you upgrade to this
release.
Updated June 26, 2012
Page 40
Release Definition
Parallel Upgrade Utility (PUT)
You can use PUT to aid installation or upgrade of Teradata Database, supporting software such as
Administration Workstation (AWS), BYNET, and the other software options that are part of a release.
PUT is provided with each copy of this release, but you should download the latest version of PUT
applicable to your operating system via Teradata @ Your Service
(http://www.teradataatyourservice.com/) before installing or upgrading to this release.
Windows Upgrade Restriction
Upgrading to Release 13.0 on Windows platforms is not supported. Sites planning an upgrade to Release
13.0 on Windows Server 2003 64-bit must instead perform a data migration:
1. Back up existing data.
2. Perform a fresh installation of Release 13.0 on all nodes.
3. Restore the data.
Refer to the migration procedure for details.
Replication-Related Upgrades
Before you upgrade to Release 13.0, you must resolve all in-doubt transactions. After you resolve all indoubt transactions, you must delete the entire contents of the DBC.IndoubtResLog table. For more
information, see the Teradata Database upgrade documentation on
http://infocentral.daytonoh.teradata.com/tsd-library/isupr.cfm (note that this site is available to Teradata
personnel only).
Upgrading from Older Releases
Special requirements apply if you want to upgrade to Release 13.0 from V2R6.2 and previous releases.
Upgrading from such older versions of Teradata Database requires a multi-stage implementation to
facilitate the data conversion necessary for moving through intermediate releases.
All customers upgrading to Release 13.0 from V2R6.2 and previous releases will automatically receive a
copy of the intermediate versions of Teradata Database to use during the multi-stage upgrade process.
This additional CD is labeled according to the operating system on which Teradata Database is running,
and is for upgrade purposes only.
Page 41
Updated June 26, 2012
Release Definition
Customers are licensed to use the interim software CD only as part of the upgrade process. After the
upgrade is complete, customers should dispose of the CD. If the CD is not required because the
customer is upgrading from a newer Teradata Database version, it should be disposed of immediately.
Operating System Upgrades
If you are running SLES 9 on a Teradata Data Mart 550S SMP and you want to upgrade to SLES 10 as
part of upgrading to Teradata Database 13.0:
1.
2.
3.
4.
Archive your data.
Install SLES 10.
Upgrade to Release 13.0.
Restore your data.
Returning to an Older Release
Although the conversion to a new release is automated, there is no automated way to reverse the
conversion, and thus no automated way to move backward across a conversion boundary. This is
because upgrade or migration to a new major release involves file system conversions or DBS System
Table changes.
User data in Teradata Database 13.0 and later releases cannot be used by an earlier major release of
Teradata Database. The only way to return to an earlier major release is to restore the data from an
archive:
1. Archive the data from the starting release, such as Release 12.0, and upgrade or migrate to Release
13.0.
2. If you need to return across a major release boundary, reinstall Teradata Database 12.0, which
includes a sysinit operation that destroys the existing data.
3. Restore the archived data to the Release 12.0 system.
Note: In some cases, minor releases may also contain conversions that prevent returning to a previous
release.
Contact Teradata Customer Services to arrange assistance for this type of migration.
Retaining tdatuser and tdatudf for UDFs
During installation and upgrade to Release 12.0 and up, a new operating system-native local user,
tdatuser, is created on each node on which the database runs, and is associated with default processes for
Updated June 26, 2012
Page 42
Release Definition
running user-defined functions (UDFs) in protected mode. In addition to tdatuser, the installation
process also creates a new group on each node called tdatudf.
Do not:
•
•
•
•
Delete tdatuser or tdatudf.
Change the password for tdatuser on Microsoft Windows.
Add a password on the MP-RAS version (this prevents logon to the user on UNIX systems).
Make any changes to either tdatuser or tdatudf if you want the database to function correctly and you
want to create UDFs. Before making changes, first consult the Teradata Support Center.
The user tdatuser has no special privileges on the system. No one should be able to log on as tdatuser.
On Microsoft Windows, tdatuser has no subfolder under Documents and Settings. On MP-RAS, tdatuser
has a /home/tdatuser directory, which is used for core dumps of a protected-mode UDF that crashes.
For more information on tdatuser, see SQL External Routine Programming.
Page 43
Updated June 26, 2012
Release Definition
System Performance
To find out the latest information about regressions that have been identified for this release and how
they may affect your system, see Technical Alerts and Orange Book.
Running Teradata Database with Other
Applications
Other applications (including Teradata applications) may execute concurrently with the Teradata
Database on approved system platforms. However, this is not encouraged, as it may negatively impact
database:
•
•
Throughput and response time performance
Availability
It is highly recommended that you do not run applications that are large consumers of system resources
(such as other databases) concurrently without understanding the performance and availability impact to
both the applications and Teradata Database.
If you run applications on the same system or node as the Teradata Database:
•
•
•
•
The system or node may need additional hardware (for example, memory) to support the
applications.
Monitoring and tuning the system may be more complex.
You may need to make compromises (for example, in the settings of tuning parameters) to provide
satisfactory and consistent performance for both Teradata Database and applications.
If a problem does occur, it may be necessary to determine whether the problem also occurs in
isolation.
If an application does not run properly or interferes with Teradata Database, you may need to move it to
another node or system. For instance, such applications may:
•
•
•
•
•
•
Require a different version of the operating system
Require a different set of operating system-level patches
Require different settings of tuning parameters
Be unable to obtain adequate system resources, or obtain too many system resources due to UNIX
scheduler or other OS-specific resource limitations.
Adversely affect performance
Require significant use of the BYNET bandwidth
Reliability and availability may be a concern if an application failure tends to bring down UNIX and
thereby bring down Teradata Database, or vice versa.
Updated June 26, 2012
Page 44
Release Definition
By default, the Teradata memory allocation algorithms are based on Teradata Database using 100% of
the memory on a node. If other applications use a significant amount of node memory, you may need to
add memory, and you should adjust the option controlling this percentage. For these reasons, avoid
running non-Teradata applications on nodes running Teradata Database, if possible, as shown below.
Software Type
Non-Teradata applications
Teradata applications and
Teradata client software
Run on Nodes That Run
Teradata Database?
No
Yes
Considerations
Run on nodes that do not run Teradata Database, or run on a
separate client or server, so that:
• Expected throughput, expected response time, and
parallel efficiency are not impacted.
• Detrimental impact on the system is reduced.
• Problems can be more easily isolated.
• Fixes needed by one application can be made without
having to apply them to nodes that do not need those
fixes (or for which those fixes are detrimental).
Run on nodes that run Teradata Database if the software:
• Puts a very small load on a system.
• Evenly distributes the workload across the nodes.
• Is used periodically for system maintenance.
• Has an impact that is well-understood and acceptable.
Note: Even if applications are run on separate nodes (non-TPA nodes), they may still share the BYNET
and thereby potentially interfere with Teradata Database or vice versa.
Page 45
Updated June 26, 2012
Release Definition
Software Maintenance Schedule
Purchasers of Teradata Database software are entitled to a period of continuing support after initial
installation or upgrade.
Maintenance Support
Maintenance releases collect and extensively test all e-fixes created since the previous major, minor, or
maintenance release.
Major and minor releases are typically limited to 2 maintenance releases, approximately 5 months apart.
The term of support for the base release and each maintenance release for the major/minor release
families, excluding the last maintenance release, is:
•
•
•
Twelve months for certified e-fixes
Two months of e-fix availability
Three additional months of support with crashdump analysis
The last maintenance release in a major/minor family will have support for:
•
•
•
Twenty-two months of certified e-fixes
Two months of e-fix availability
Three months of crashdump analysis
Therefore, the term of code-level remedy (certified and uncertified e-fix availability) for a complete
major/minor family is a minimum of 34 months.
Teradata Database Maintenance Roadmap
The Teradata Maintenance Release Roadmap shows the detailed code-level remedy and support for each
Teradata Database version. The times shown for code-level remedies are defined in terms of
maintenance releases. Longer periods of support may be offered depending on the schedule for
subsequent releases and whether they are delayed.
Customers with active Service Agreements can find the Teradata Maintenance Release Roadmap on
Teradata @ Your Service (http://www.teradataatyourservice.com).
Customers without support agreements should contact their sales or support team.
Updated June 26, 2012
Page 46
Release Definition
User Documentation
Software orders include, free of charge:
•
•
•
PDF versions of all user documents downloadable from the Teradata Information Products Web site
at http://www.info.teradata.com/
User Documentation CD-ROM image downloadable from the Teradata Information Products Web
site at http://www.info.teradata.com/
Up to 4 fully indexed and searchable CD-ROMs (the number of copies depends on system size)
To order publications, go to http://www.info.teradata.com/HardCopy/eHowToOrder.cfm.
Documentation on IUMB is not part of the standard user documentation set (only available to Teradata
personnel) at http://infocentral.daytonoh.teradata.com/tsd-library/isupr.cfm.
Platform documentation is not part of the standard user documentation set (only available to Teradata
personnel) on the web at http://infocentral.daytonoh.teradata.com/tsd-library/iPlatform.cfm.
Downloading a Document
To download a document for the current release from the Teradata Information Products Web site:
1.
2.
3.
4.
5.
Go to http://www.info.teradata.com/.
Select Data Warehousing.
Select Teradata Database.
Select the current release.
Select the desired document.
Downloading a List of User Publications
A list of user publications for each release of Teradata Database is available on the Teradata Information
Products Web site. To download a list for the current release:
1.
2.
3.
4.
Go to http://www.info.teradata.com/.
Select Data Warehousing.
Select Documentation Lists.
Select the desired release.
Page 47
Updated June 26, 2012
Release Definition
DRs and RFCs
Discrepancy Reports (DRs) document areas of the Teradata Database software that require change. DRs:
•
•
Fix an identified software problem
Record a Request for Change (RFC) that adds a new feature to the software
Teradata Database Discrepancy Reports Summary lists the DRs and RFCs that were incorporated into
this release. Go to:
• http://infocentral.daytonoh.teradata.com/Discrepancy-Reports/iD-reports.cfm (this site is available to
Teradata personnel only)
• Teradata @ Your Service (http://www.teradataatyourservice.com/). Select Support Information.
Under Tool & Reports, select Discrepancy Reports.
Updated June 26, 2012
Page 48
Release Definition
Customer Education
Teradata Customer Education delivers training for your global workforce—from scheduled public
courses, customized on-site training, to the latest E-learning solutions. For more information on the
latest classes, schedules, the Teradata Certification Program, and to enroll in classes online, go to the
Teradata Customer Education Web site at http://www.TeradataEducationNetwork.com.
The representative for your region can also assist you. To find the representative for your region, use the
Contact Us link at the bottom of the Teradata Education Network page.
Page 49
Updated June 26, 2012
Release Definition
Customer Support
Customer support is available at all hours, 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 (http://www.teradataatyourservice.com/).
Remote Service Centers (RSCs) were formerly called MSCs.
If you purchased an ESS 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.
PINs are not published. If you inadvertently misplace your PIN, contact your account representative.
Technical Alerts and Orange Books
Customers can access technical alerts and Orange Books on Teradata @ Your Service
(http://www.teradataatyourservice.com/).
White Papers
White papers are executive level documents that target business or technical management, and address
why a feature is valuable for an active data warehouse.
Customers can access white papers through http://www.teradata.com by searching for white paper.
Updated June 26, 2012
Page 50
Release Definition
List of Acronyms
Acronym
AWS
BAR
BTEQ
CDC
CLI
CS-RSC
DR
EBCA
EMEA
GB
GCA
GPL
GSC
GSS
HCL
IUM
JRE
LAN
MCCA
MPP
OS
PDE
PDF
PIN
PM/API
PUT
RAID
RAM
RFC
SMP
SUPR
SUSE
TDGSS
TPA
TSS
TUP
TUVT
VMF
WAL
Page 51
Definition
Administration Workstation
Backup and Restore
Basic Teradata Query Language
Change Data Capture
Call-level Interface
Customer Services Remote Service Center
Discrepancy Report
EISA Bus Channel Adapter
Europe, Middle East, Africa
Gigabyte
General Customer Availability
General Purpose Language
Global Support Center
Global Sales Support
Hardware Compatibility List
Installation, Upgrade, and Migration
Java Runtime Environment
Local Area Network
Micro-Channel Channel Adapter
Massively Parallel Processing
Operating System
Parallel Database Extensions
Portable Document Format
Personal Identification Number
Performance Monitor/Applications Programming Interface
Parallel Upgrade Tool
Redundant Array of Inexpensive Disks
Random Access Memory
Requests for Change
Symmetric Multi-processor
Single Unified Procedures Repository
German acronym for the business unit of Novell, Inc. that publishes SUSE Linux Enterprise Server.
Teradata Generic Security Services
Trusted Parallel Application
Teradata Software Server
Teradata Utilities Pack
Teradata Utilities Verification Tool
Version Migration and Fallback
Write Ahead Logging
Updated June 26, 2012
Release Definition
Updated June 26, 2012
Page 52
Download PDF
Similar pages