Download Teradata Aster Database 6.20 Release Notes

Teradata Aster® Database 6.20
Release Notes
Product ID: B700-6006-620K
Released: March 2017
Aster Database version: 6.20
Important Feature Support Changes
Backup and Restore of Aster Database Using Teradata Data Stream Architecture (Teradata
DSA-Aster BAR) is no longer a supported feature of AD 6.20.xx.xx releases. Aster Database
customers may continue to use the existing Aster backup utility. For additional information
about this feature support change, contact your Customer Support Representative.
The Disk Quota Monitoring feature is not supported in AD6.20.01. Although this feature is
documented in the AD6.20.01 version of the Teradata Aster® Database User Guide, support for
this feature has been removed from all AD6.20.xx.xx releases until further notice and must be
disabled. See Disk Quota Monitoring must be disabled (page 14) for information on how to
disable this feature.
The ALTER FOREIGN SERVER command of the Foreign Server feature is not supported in
AD6.20. Documentation for this command has been removed from the AD6.20.02 version of
the Teradata Aster® Database User Guide. Support for this command has been removed from
all AD6.20.xx.xx releases until further notice.
Summary
This document describes the new features and enhancements in Aster Database version 6.20,
6.20.01, 6.20.02, 6.20.03, and 6.20.04. It also lists open and fixed issues and provides
information needed to help you upgrade to this new version of Aster Database.
Aster Database 6.20 Release Notes
1
Teradata Aster® Database 6.20 Release Notes
Summary
Aster Database version 6.20.04 introduces these new and expanded features:
•
IBM BigInsights 4.2
•
Teradata Database 16.00
•
CDH 5.8
Aster Database version 6.20.03 introduces these new and expanded features:
•
Mixed Mode Authentication
•
Multi-Level LDAP Authentication
•
Kerberos-Enabled Aster-Teradata Connector
•
Additional Hadoop Version
•
Enhanced Query Monitoring
•
Supported Appliance 5 Operating System Versions
Aster Database version 6.20.02 introduces these new and expanded features:
•
New load_from_hcatalog Function Argument
Aster Database version 6.20.01 introduces these new and expanded features:
•
LDAP Authentication in QueryGrid: Aster-Hadoop Connectors
•
Tracing Query Relationship Hierarchy
•
AMC Storage Monitoring Enhancements
•
SolrCloud Integration
Aster Database version 6.20 introduces these new and expanded features:
•
User Defined Functions
•
System Table Joins
•
Query Pushdown
•
load_to_hcatalog
•
Foreign Server
•
OPS Log Parser
•
Upgrade to JDK 1.8
•
Limiting Disk Space Usage for Temporary Tables and Files
•
Write-Ahead Logging
•
Information About Catalogs
•
Additional ncli sqlh setserverconfig Options
•
Additional Hadoop Versions
•
Data Integrity Verification
Who Should Install This Release of Aster?
Customers using earlier versions of Aster Database should upgrade at their convenience.
Aster Database 6.20 Release Notes
2
Teradata Aster® Database 6.20 Release Notes
Contents
Contents
Important Feature Support Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Who Should Install This Release of Aster? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
What's New? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
AD 6.20.04 New and Expanded Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
AD 6.20.03 New and Expanded Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
AD 6.20.02 New and Expanded Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
AD 6.20.01 New and Expanded Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
AD 6.20 New and Expanded Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Changes in This Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Changed Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Getting and Installing Aster Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Supported Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Supported Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Clusters that Run on the Appliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Clusters that Run on Commodity Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Important Installation and Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Red Hat Install and Upgrade Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Kernel Update Needed for Appliance Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Changes to the Upgrade Path for Backup Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Fixed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Naming Convention for Teradata Aster Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
End-of-Life and Deprecation Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Backup and Restore of Aster Database Using Teradata Data Stream Architecture . . . . . 22
Disallow New Use of HIGH and MEDIUM Compression Levels . . . . . . . . . . . . . . . . . . . 22
Templeton webHCat Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Hadoop Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
ncli node showinterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
ncli system addnode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
AMC: Hard Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Contacting Teradata Global Technical Support (GTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Third Party Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Aster Database 6.20 Release Notes
3
Teradata Aster® Database 6.20 Release Notes
What's New?
Supported Version Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Version History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Copyright and Legal Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
What's New?
For more information on the topics presented in this section, see the Teradata Aster® Database
User Guide.
AD 6.20.04 New and Expanded Features
IBM BigInsights 4.2
Teradata Aster now supports loading data from and to hive tables, created and managed on an
IBM BigInsights 4.2 cluster, using the load_from_hcatalog and load_to_hcatalog Teradata
Aster SQL-MapReduce® functions.
Teradata Database 16.00
Teradata Database version 16.00 is supported with this release.
CDH 5.8
Cloudera Distribution for Hadoop CDH 5.8 is certified with this release.
AD 6.20.03 New and Expanded Features
Mixed Mode Authentication
Mixed authentication mode has been introduced at this release. This new authentication
mode allows you to connect to the Aster Database with multiple types of authentication
simultaneously, making it easier for clients to connect to the database in a mixed mode
environment.
Mixed mode authentication supports GSS+LDAP or GSS+PASSWD authentication.
Multi-Level LDAP Authentication
For additional security, Aster now supports multi-level LDAP authentication, where the server
first binds to the LDAP directory with a fixed user name and password and performs a search
for the user trying to log in to the database.
Kerberos-Enabled Aster-Teradata Connector
Kerberos authentication mechanism has been added to the present set of authentication
methods available for the Aster-Teradata connector, making it more secure.
Additional Hadoop Version
Hadoop version HDP 2.4.2 is supported at this release.
Aster Database 6.20 Release Notes
4
Teradata Aster® Database 6.20 Release Notes
What's New?
Enhanced Query Monitoring
To prevent a query using an analytic function from impacting cluster availability, thresholds
can be set to automatically monitor queries that block other work and warn or kill them if
they are degrading the overall cluster performance.
To set the thresholds, two new configuration variables have been added to the ncli monitor
command. The ncli query cancelprocess command now has an optional parameter,
--reason= that allows a string to be added to the error message you see for the query that is
canceled.
Supported Appliance 5 Operating System Versions
For new and upgraded installations on Appliance 5, this release supports these operating
system versions:
Hardware
Operating System
Operating System Version
Kernel Version
Appliance 5
Teradata SLES 11
SP1 - AD 6.20,
AD 6.20.01, AD 6.20.02,
AD 6.20.03
.53
SP1 - AD 6.20.02,
AD 6.20.03
.91
SP3 - AD 6.20.03
.101
AD 6.20.02 New and Expanded Features
New load_from_hcatalog Function Argument
A new argument, TEMP_DBNAME, has been added to the load_from_hcatalog function. Use
TEMP_DBNAME to save temporary tables created by load_from_hcatalog.
AD 6.20.01 New and Expanded Features
LDAP Authentication in QueryGrid: Aster-Hadoop Connectors
The feature adds LDAP as an additional Hadoop security type. LDAP authentication support
enables access to LDAP-authenticated Hadoop clusters. In this release, Aster supports only
Hadoop clusters where only HiveMetastore is secured with LDAP.
Tracing Query Relationship Hierarchy
This tracing query relationship feature identifies Aster processes (statements and queries)
executed by an invoked Teradata Aster SQL-MapReduce® driver function. It allows you to see
that the processes are all linked.
AMC Storage Monitoring Enhancements
AMC now gives you the ability to see data on table sizes, compression, tuple counts, as well as
data on how a table is distributed among nodes and vWorkers.
Aster Database 6.20 Release Notes
5
Teradata Aster® Database 6.20 Release Notes
What's New?
SolrCloud Integration
This feature enables data stored in Aster to be indexed in an external SolrCloud cluster. Also,
this feature enables a mechanism for querying the index and/or data that is maintained on the
SolCloud.
Two new SQL-MapReduce connector functions, load_from_solr and load_to_solr, are
provided for loading into and querying a SolrCloud collection.
AD 6.20 New and Expanded Features
User Defined Functions
This new feature extends Aster’s capability beyond MapReduce and Graph table function
infrastructures. User defined functions allow easier development of high performance
sophisticated customized functions. See the Teradata Aster® Developer Guide for information
on this feature.
System Table Joins
With this release, joins are allowed between data dictionary views and user tables.
Query Pushdown
Query pushdown allows you to push queries to a Hadoop hive database and get results back to
Aster, automatically mapping hive data types to Aster data types.
load_to_hcatalog
The load_to_hcatalog SQL-MapReduce function copies data from Aster Database to Hadoop
and puts out information about the data copied and any errors generated. It is invoked on
Aster Database. This new function completes the full circle of moving data between Aster and
Hadoop using load_from_hcatalog and load_to_hcatalog.
Foreign Server
The Aster foreign server feature supports easy bi-directional movement to and from the
HCatalog and Teradata foreign data sources.
The SQL-MapReduce connector functions that you use for this movement are:
•
load_from_teradata and load_from_hcatalog to import data from foreign servers
•
load_to_teradata and load_to_hcatalog to export data to foreign servers
OPS Log Parser
A new command, ncli system analyzeopslog, makes it easier to access and extract useful
information from OPS logs.
Upgrade to JDK 1.8
Aster Database now supports JDK1.8.
Aster Database 6.20 Release Notes
6
Teradata Aster® Database 6.20 Release Notes
Changes in This Release
Limiting Disk Space Usage for Temporary Tables and Files
Temporary table disk space usage can increase rapidly in certain situations, having the
potential to bring down a cluster. New in this release is the variable temp_space_limit. Use
it to limit the amount of temporary table and file disk space a query can take.
Write-Ahead Logging
Two new ncli vworker commands are introduced in this release:
•
ncli vworker showwalreplayprogress shows you the number of write-ahead log
segments in each being-activated vworker and its replaying progress.
•
ncli vworker showwalreplaytime shows you the vworker write-ahead segment counts
and the estimated duration for a restart process.
Information About Catalogs
A new ncli command, ncli catalog showcatalogstats, takes a list of databases as input
and shows detailed information on catalogs of the databases specified.
Additional ncli sqlh setserverconfig Options
In support of the Query Pushdown feature, hs2Host and hs2Port are new options added to
the ncli sqlh setserverconfig command.
Additional Hadoop Versions
New Hadoop versions supported:
•
CDH5.3
•
CDH5.4
•
HDP2.3
Data Integrity Verification
For new installations of the 6.20 version of the Aster Database, internal checking for events
that can indicate a rare type of data corruption is performed automatically.
Changes in This Release
Changed Documentation
Aster Developer Guide
A new chapter, “User Defined Functions”, was added.
Aster Database User Guide
The following chapters were added:
•
“Foreign Server”
•
“The SolrCloud Connector”
Aster Database 6.20 Release Notes
7
Teradata Aster® Database 6.20 Release Notes
Getting and Installing Aster Database
The “Backup and Restore of Aster Database Using Teradata Data Stream Architecture” chapter
was removed.
Getting and Installing Aster Database
An Aster Database major release includes significant new features and enhancements, as well
as changes incorporated from earlier versions. Upgrading to a major release involves moving
to a new base version of the Aster Database and all associated patches.
Work with your Account Team to order the new base version of the Aster software for either
the Appliance or commodity hardware. The Aster software will contain the required base
installation files, along with dependency files, in order to perform the Aster Installation:
The Teradata At Your Service (T@YS) website, https://tays.teradata.com/, is an additional
resource that is available to customers and Teradata employees. This is a secure site from
which you can access Orange Books, technical alerts, and knowledge repositories; view and
join forums; and download software packages and documentation.
For detailed information, refer to the Teradata Aster® Database Installation and Upgrade
Guide.
Supported Platforms
For new and upgraded installations, this release supports these appliance platforms:
•
Teradata Aster® Big Analytics Appliance 3 and 3H
•
Teradata Aster® Big Analytics Appliance 4
•
Teradata Aster® Big Analytics Appliance 5
For a list of supported and certified platforms for commodity installations, see the Teradata
Aster® Database Platform/OS Support Matrix, version 6.20.
Supported Operating System
For new and upgraded installations on the appliance, this release supports:
Hardware
Operating System
Operating System Version
Kernel Version
Appliance 3 and 3H
Teradata SLES 11
SP1 - AD 6.20,
AD 6.20.01, AD 6.20.02
.41
SP1 - AD 6.20.03, AD
6.20.04
.91
Aster Database 6.20 Release Notes
8
Teradata Aster® Database 6.20 Release Notes
Supported Upgrade Paths
Hardware
Operating System
Operating System Version
Kernel Version
Appliance 4
Teradata SLES 11
SP1 - AD 6.20,
AD 6.20.01
.41 and .53
SP1 - AD 6.20.02,
AD 6.20.03
.91
SP1 - AD 6.20.04
.97
SP1 - AD 6.20,
AD 6.20.01
.53
SP1 - AD 6.20.02,
AD 6.20.03
.91
SP1 - AD 6.20.04
.97
SP3 - AD 6.20.03 (Contact
your Customer Support
Representative)
.101
SP3 - AD 6.20.04 (Contact
your Customer Support
Representative)
.113
Appliance 5
Teradata SLES 11
For new and upgraded installations on commodity hardware, this release supports:
Release
SLES (Commdity)
SLES11
RedHat
6.5
6.6
AD 6.20
X
AD 6.20.01
AD 6.20.02
6.7
SP2
SP3
X
X
X
X
X
X
X
X
X
X
X
AD 6.20.03
X
X
X
AD 6.20.04
X
X
X
Upgrading requires that a supported version of Red Hat is already installed on the cluster.
Perform any required updates to the RHEL OS prior to initiating the Aster Database upgrade.
Supported Upgrade Paths
Clusters that Run on the Appliance
Supported Direct Upgrades
You can upgrade directly to a recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or
6.20.04 release of the Aster Database if your cluster runs a supported version of the 6.10 release
of the Aster Database on the Aster Appliance and you have successfully redistributed
Aster Database 6.20 Release Notes
9
Teradata Aster® Database 6.20 Release Notes
Supported Upgrade Paths
preexisting data on the cluster. Work with your Account Team to order the recommended base
version of the Aster 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04 software for the Appliance.
Supported Indirect Upgrades
If your cluster is running one of the Aster Database versions listed in this section, you must
perform an indirect, multi-hop upgrade. Work with your Account Team to order the
recommended software for your specific upgrade path.
Notice: Teradata Aster recommends that you back up all data before performing any upgrade. Because of this, in the
case where you will be performing an upgrade that involves two or more hops, you should perform a backup before each
upgrade. This will minimize the number of steps you need to backtrack in case of power failure, network or hardware
failure, or anything else that might disrupt an upgrade.
For indirect upgrades, follow the instructions in the documentation for each release when
upgrading to that release.
If you wish to upgrade from a release that is not listed, contact Teradata Global Technical
Support (GTS) for the upgrade path to follow.
For Upgrades from 6.00.xx.xx
You must upgrade to the recommended version of the 6.10 release of the Aster Database,
redistribute preexisting data on the cluster, and then upgrade to the recommended version of
the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04 release of the Aster Database:
1
Upgrade to the recommended version of the 6.10 release of the Aster Database.
2
Redistribute Preexisting Data on the Cluster.
3
Upgrade to the recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04
release of the Aster Database.
For Upgrades from 5.10.xx.xx
You must perform a two hop upgrade, redistribute preexisting data on the cluster, and then
upgrade to the recommended version of the 6.20 or 6.20.01, 6.20.02, 6.20.03, or 6.20.04
release of the Aster Database:
1
Upgrade to 6.00 or 6.00.01.
2
Upgrade to the recommended version of the 6.10 release of the Aster Database.
3
Redistribute Preexisting Data on the Cluster.
4
Upgrade to the recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04
release of the Aster Database.
For Upgrades from 5.0.2
You must perform a three hop upgrade, redistribute preexisting data on the cluster, and then
upgrade to the recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04 release
of the Aster Database:
1
Upgrade to 5.10.xx.xx.
2
Upgrade to 6.00 or 6.00.01.
Aster Database 6.20 Release Notes
10
Teradata Aster® Database 6.20 Release Notes
Supported Upgrade Paths
3
Upgrade to the recommended version of the 6.10 release of the Aster Database.
4
Redistribute Preexisting Data on the Cluster.
5
Upgrade to the recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04
release of the Aster Database.
Clusters that Run on Commodity Hardware
Supported Direct Upgrades
Clusters that Run on Your Own Hardware: SLES
You can upgrade directly to a recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or
6.20.04 release of the Aster Database if your cluster runs a supported version of the 6.10 release
of the Aster Database on the SUSE Linux Enterprise Server 11 SP2 or SP3 operating system
and you have successfully redistributed preexisting data on the cluster. Work with your
Account Team to order the recommended base version of the Aster 6.20, 6.20.01, 6.20.02,
6.20.03, or 6.20.04 software.
Clusters that Run on Your Own Hardware: Red Hat
You can upgrade directly to a recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or
6.20.04 release of the Aster Database if your cluster runs a supported version of the 6.10 release
of the Aster Database on the RHEL 6.5 or RHEL 6.6 operating system, and you have
successfully redistributed preexisting data on the cluster. Upgrading requires that a supported
version of RHEL is already installed on the cluster. Work with your Account Team to order the
recommended base version of the Aster 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04 software.
Supported Indirect Upgrades
If your cluster is running one of the Aster Database versions listed in this section, you must
perform an indirect, multi-hop upgrade.
For indirect upgrades, follow the instructions in the documentation for each release when
upgrading to that release.
If you wish to upgrade from a release that is not listed, contact Teradata Global Technical
Support (GTS) for the upgrade path to follow.
For Upgrades from 6.00.xx.xx
You must upgrade to the recommended version of the 6.10 release of the Aster Database,
redistribute preexisting data on the cluster, and then upgrade to the recommended version of
the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04 release of the Aster Database:
1
Upgrade to the recommended version of the 6.10 release of the Aster Database.
2
Redistribute Preexisting Data on the Cluster.
3
Upgrade to the recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04
release of the Aster Database.
Aster Database 6.20 Release Notes
11
Teradata Aster® Database 6.20 Release Notes
Important Installation and Upgrade Issues
For Upgrades from 5.10.xx.xx
You must perform a two hop upgrade, redistribute preexisting data on the cluster, and then
upgrade to the recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04 release
of the Aster Database:
1
Upgrade to 6.00 or 6.00.01.
2
Upgrade to the recommended version of the 6.10 release of the Aster Database.
3
Redistribute Preexisting Data on the Cluster.
4
Upgrade to the recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04
release of the Aster Database.
For Upgrades from 5.0.2
You must perform a three hop upgrade, redistribute preexisting data on the cluster, and then
upgrade to the recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04 release
of the Aster Database:
1
Upgrade to 5.10.xx.xx.
2
Upgrade to 6.00 or 6.00.01.
3
Upgrade to the recommended version of the 6.10 release of the Aster Database.
4
Redistribute Preexisting Data on the Cluster.
5
Upgrade to the recommended version of the 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04
release of the Aster Database.
Important Installation and Upgrade Issues
Check the following issues pertaining to installation and upgrade:
Red Hat Install and Upgrade Notification
For new Aster Database installations on clusters running the Red Hat Enterprise Linux
(RHEL) OS, this release requires that you have a supported version of Red Hat installed on the
cluster.
For upgrades to an existing installation of the Aster Database on clusters running the RHEL
OS, this release requires that a supported version of Red Hat is already installed on the cluster.
Perform any required updates to the RHEL OS prior to initiating the Aster Database upgrade.
Kernel Update Needed for Appliance Upgrades
Before upgrading Aster Database on the appliance, call Teradata Global Technical Support
(GTS) to obtain the latest recommended operating system kernel patches. Download and
apply any recommended patches before upgrading.
Aster Database 6.20 Release Notes
12
Teradata Aster® Database 6.20 Release Notes
Notifications
Changes to the Upgrade Path for Backup Manager
You will not be able to restore backups taken with a previous version of Aster Backup after
upgrading. The installer will remove all previous (older version) backups.
If you do not wish to lose previous backups, do one of the following before upgrading Aster
Backup:
•
Archive your backups before upgrading Backup Manager.
•
Do a clean install of Backup Manager on another machine that will be used with Aster
Database 6.20, 6.20.01, 6.20.02, 6.20.03, or 6.20.04 only.
Older backups are not compatible with version 6.20, version 6.20.01, version 6.20.02, version
6.20.03, or version 6.20.04 of Backup Manager.
Notifications
•
Backup and Restore of Aster Database Using Teradata Data Stream Architecture (Teradata
DSA-Aster BAR) is no longer a supported feature of AD 6.20.xx.xx releases. Aster Database
customers may continue to use the existing Aster backup utility. For additional
information about this feature support change, contact your Customer Support
Representative.
•
For upgrades from a release prior to AD6.20 directly to AD6.20, 6.20.01, 6.20.02, 6.20.03,
or 6.20.04, pre-existing SQL-H configurations must be recreated due to the new
configuration options introduced at AD6.20.
•
If you are a Commodity hardware customer and have a mixed 32/64 bit environment, you
must get the latest version of the PUT software from the Teradata Software Server (TSS) at
http://tssprod.teradata.com:8080/TSFS/ under Certified Configs.
•
Effective with the release of AD 6.10, the Hard Restart button in the AMC has been
removed. To obtain similar functionality to that previously provided by the Hard Restart
button, use these commands to shutdown and reboot a cluster:
Shutdown the cluster:
# ncli system softshutdown
Reboot the queen:
# /sbin/reboot
After the queen completes rebooting, reboot the workers and loader nodes:
# ncli node runonother /sbin/reboot
The Soft Restart button remains available in the AMC to perform a soft restart of the
cluster.
•
Support for IBM BigInsights by the Teradata Querygrid: Aster-Hadoop connector begins
at AD6.20.04. Releases prior to AD6.20.04 do not support IBM BigInsights.
•
GenerateDDL still generates commands with MEDIUM and HIGH keywords.
•
CDH 5.4 is certified and works with CDH 5.3 client libraries. These two versions are
compatible and therefore there is no functionality loss.
Aster Database 6.20 Release Notes
13
Teradata Aster® Database 6.20 Release Notes
Known Issues
•
When you connect to the AMC using Firefox as your browser, Firefox consumes a large
percentage of CPU and may not exit gracefully. If you encounter this issue, either update
the operating system to its latest patch or use Chrome instead.
Known Issues
Teradata Aster® Analytics Betweenness function returns error
Issue: BH-8906
Details: The Aster Analytics Betweenness function returns this error if the partition key of
type date is used:
ERROR: cannot use a partitioning key of type "date"
Disk Quota Monitoring must be disabled
Issue: BH-8620
This feature must be disabled. Run the following command on the queen:
Although this feature is documented in the version of the Aster Database User Guide that supports the AD6.20.01
release, support for this feature has been removed from the AD6.20.01 release.
ncli qos pqfeatureoff
If ACT does not respond with a prompt after a short amount of time, enter the following
commands on the queen:
pkill queenExec
pkill QosManagerExec
ncli qos pqfeatureoff
Error generated when reading a snappy compressed table on
BigInsights 4.2 cluster into Aster using load_from_hcatalog
Issue: BH-12732
Details: Reading a snappy compressed table on BigInsights 4.2 cluster into Aster using
load_from_hcatalog gives the following error:
ERROR: SQL-MR function LOAD_FROM_HCATALOG failed: Failed to read data from
hcatalog. task : 0. Details : Failed to create SqlhRecordReader native snappy library not
available: this version of libhadoop was built without snappy support.
Failover to secondary queen node fails if packages are not
identical
Issue: BH-8775
Details: Discrepancies in primary and secondary queen node packages prevent a successful
failover.
Aster Database 6.20 Release Notes
14
Teradata Aster® Database 6.20 Release Notes
Known Issues
Ensure that the packages installed on the secondary queen are identical to that of the primary
queen node for a failover to occur successfully.
Aster Clients and Teradata Aster® R version support on AD6.20.01
Issue: BH-8320
Details: The Aster Client software bundle includes Aster Client packages and Aster R packages.
Depending on your product needs, these versions of the Aster Client software are supported
for use with Aster Database version 6.20.01:
•
To install Aster clients and utilities, use the AC6.20 release of the Aster Client software.
•
To install Aster R, use the AC6.21 release of the Aster Client software.
Refer to the ReadMe file for this release for additional information.
Parent child query tree is affected by filters applied in Processes
tab
Issue ID: BH-7743
Details: Application of a Process Filter in the Processes tab of the AMC is likely to cause
incomplete information in the Parent-Child Process Relationships tree of the Process Details
tab.
ncli system analyzeopslog does not report table failed during post
expand in specific scenarios
Issue: BH-6000
Details: opslogparser is unable to report an error that occurs during the ‘drop original table’
step of a table redistribution or partition split.
It is highly unlikely that an OPS or a redistribution will fail in the ‘drop original table’ step, but
if it does, you can browse the queen nodes’s
/primary/logs/OnlinePartitionSplitting.log file and find the entry:
2015-05-23T01:27:39.657994 INFO 6236 expandTablesExec.cpp:4045
3113011004714234013] Thread 1: TABLE: beehive.claim.claim_att_loaded_all
: drop original table hierarchy Statement drop table
"_ops_done_320156"."claim_att_loaded_all" cascade got Exception …
Use it to manually drop the “original_ops_done_*” table. For example:
drop table "_ops_done_320156"."claim_att_loaded_all";
AMC shows incorrect session user after set role
Issue ID: BH-7354
Details: Statements run by an impersonated user (role) no longer show the impersonated user.
AMC shows the user who originally started the sessions.
changepartioncountcheck may underestimate the space required
for OPS
Issue ID: BH-7185
Aster Database 6.20 Release Notes
15
Teradata Aster® Database 6.20 Release Notes
Known Issues
Details: When OPS is used, partitions compressed at the HIGH or MEDIUM level are
converted to be compressed at the LOW level. The calculations done by
changepartitioncountcheck to estimate disk space requirements do not take into account
the increased space required by the conversion.
To work around this issue, use the ALTER TABLE or ALTER INDEX commands, specifying
COMPRESSION LOW, before partition splitting so that HIGH or MEDIUM compression is
not used.
Unable to connect to AMC
Issue ID: BH-6591
Details: In rare cases, the Aster Management Console (AMC) does not start. If this happens,
your cluster’s Java might not be compatible with Aster’s.
To work around this problem, run the following two commands to restart the AMC:
source /home/beehive/config/asterenv.sh
unset JRE_HOME && JAVA_HOME=/home/beehive/toolchain/x86_64-unknownlinux-gnu/jdk1.8.0_45 CATALINA_BASE=/home/beehive/amc/
webserverCATALINA_OPTS=-Xmx256m /home/beehive/toolchain/noarch/apachetomcat-8.0.24/bin/catalina.sh run &
After connecting to AMC, Firefox consumes CPU and will not exit
Issue ID: BH-7103
Details: After pointing Firefox to a cluster, FireFox starts to consume about 25% of CPU even
when it is not doing anything. Even after exiting Firefox, it continues to run and consume
CPU.
ncli system addnode --clean option, error messages, and help text
not handled properly
Issue ID: BH-5772
Details: The --clean option and MAC address are no longer supported for the ncli system
addnode command. However, using the option does not generate an error.
Wizard to create the Aster Analytics Test Configuration fails to
launch in Luna
Issue ID: BH-5847
Details: The Eclipse 4.4 (Luna) release is not supported on the AD6.10 version of the Aster
Development Environment.
Significant performance degradation during a highly skewed
query
Issue ID: BH-5009
Details: In an extreme data skew case, hash loop join degenerates to a nested loop join.
To work around the problem, rewrite your query to reduce the qualified tuples that participate
in the join.
Aster Database 6.20 Release Notes
16
Teradata Aster® Database 6.20 Release Notes
Fixed Issues
Partition splitting fails intermittently with duplicate key error
Issue ID: BH-4134
Details: A duplicate key error is intermittently returned when a CREATE TABLE statement is
issued for a logically partitioned table.
To work around this issue, retry the partition splitting operation.
ncli sshkeys disable removes keys that are not intra-cluster keys Issue ID: BH-4930
Details: After using ncli sshkeys disable, a worker or loader node can lose keys that are
unrelated to the cluster.
Fixed Issues
FIXED: Archive shows 0.00% complete even when it has
succeeded
Issue ID: BH-7150
Details: Archive shows as 0.00% complete even when the archive process is successful.
FIXED: The ACT client utility may fail when run on RHEL
Issue: CLNT-2313
Details: The AD 6.20.01 software bundle contains a version of the ACT client utility that may
fail when run on Red Hat Enterprise Linux (RHEL).
If you encounter this issue, and run ACT on RHEL, obtain the ACT utility from the AC
6.20.00 client package. Note that you must use AC 6.20.00.00 and not AC 6.21 or any other AC
6.2x release. Contact Teradata Global Technical Support to obtain a copy of AC 6.20.00.00.
FIXED: Remove CGROUP function on Commodity Hardware
(Recommended)
Issue ID: BH-3233
Details: The Aster Database 6.0 and later release uses memory cgroups in order to control
query memory usage. However, on Commodity hardware, processes do not progress as
expected. Therefore, when upgrading to Aster Database 6.0 or later, a consideration should be
made to remove the CGROUP function on Red Hat Linux 2.6.32-279.22.1.el6.x86_64.
To remove the CGROUP function on Red Hat Linux 2.6.32-279.22.1.el6.x86_64 on
Commodity hardware, perform these steps to edit the /etc/cgconfig.conf file to remove
memory = /cgroup/memory;:
1
Install libcgroup if it is not already installed; to install the library run:
$ yum -y install libcgroup
2
$ view /etc/cgconfig.conf
Aster Database 6.20 Release Notes
17
Teradata Aster® Database 6.20 Release Notes
Fixed Issues
3
Remove memory = /cgroup/memory; from the cgconfig.conf file.
Note: Ensure that the line is removed and not just commented out.
4
# ncli node clonefile "/etc/cgconfig.conf"
FIXED: Parent-Child Process Relationship panel is displaying for
standalone queries
Issue ID: BH-8027
Details: The heading for the Parent-Child Process Relationships panel of the Process Details tab
in AMC is shown in cases where the process is neither a parent nor child process.
FIXED: AMC shows an invalid number of tuple counts in Table Info
for dimension tables under the Nodes tab
Issue ID: BH-7952
Details: If a table is created with "DISTRIBUTE BY REPLICATION", Table Info under the Nodes
tab in AMC, shows the tuple count as a sum of number of rows in the table multiplied by the
number of workers. It should show only the number of rows present in the table.
FIXED: ncli system changepartioncountcheck can display negative
disk space sizes
Issue ID: BH-7856
Details: The root cause is an unguarded subtraction to compute partition skew.
FIXED: Partition splitting may leave unbalanced distribution of
primary vworkers
Issue ID: BH-7929
Details: In some cases, the distribution of primary vworkers among worker nodes after
partition splitting will be unbalanced. You should check for this problem after partition
splitting is finished, before returning the cluster for general use. If the primary vworkers are
found to be unevenly balanced, a balance process operation should be performed.
FIXED: Logical restore of a table or partition compressed at the
HIGH or MEDIUM level fails
Issue ID: BH-7324
Details: Restore of a logically backed up table will fail if the table was compressed at the HIGH
or MEDIUM level at the time the logical backup was created. The ncluster_backup show
errors command will display “ERROR: Unsupported compression level specified. Low is the
only supported level.” For help in restoring the table, contact Teradata Global Technical
Support (GTS).
Aster Database 6.20 Release Notes
18
Teradata Aster® Database 6.20 Release Notes
Fixed Issues
FIXED: IOI may crash under certain circumstances
Issue ID: BH-6695
Details: IOI may crash under some circumstances with the following message, “IOI:Assertion
failed, will abort process...(expression: ‘beingFlushed_.empty()”.
This can happen if there are too many open files in your system. The IOI logs would indicate
the same. If this occurs, increase the open file limit for the operating system on the node.
Other reasons for this behavior includes, but is not limited to, a bad hard disk, corrupt file
system or the disk is completely full. Take appropriate action to avoid these situations. You
may need to contact Teradata Global Technical Support (GTS) if you encounter this scenario.
FIXED: Monitoring thresholds are not working
Issue ID: BH-5635
Details: The monitor.filesystem.asterdb.cancelqueries_threshold and
monitor.filesystem.asterdb.killsessions_threshold do not always take effect; queries and
sessions might continue even when disk space is low.
FIXED: After a hard restart, worker nodes go to New state instead
of Prepared state
Issue ID: BH-5759
Details: If nodes come up as Failed or New when hard restarting your cluster, bring them to
the Prepared state by doing a softstartup (not softrestart) or by starting Aster services locally
on each node.
FIXED: Error occurs when load_from_teradata connects to
Teradata
Issue ID: BH-5581
Details: Error 2720 is generated when load_from_teradata connects to Teradata 14.10.00.00.
Refer to the Teradata Messages document for further details on this error.
To work around the problem, use the load_from_teradata spoolmode(‘spool’) argument.
Note that if you use this argument, performance will degrade. This argument should only be
used when this error is observed.
FIXED: Performance degradation for short-running queries
Issue ID: BH-5605
Details: There is significant performance degradation when running short-running queries.
If this issue occurs, the solution is to reboot the queen.
Aster Database 6.20 Release Notes
19
Teradata Aster® Database 6.20 Release Notes
Fixed Issues
FIXED: Disable CGROUP and SWAPACCOUNT functions on
Appliance 2 Hardware
Issue ID: BH-3212
Details: The Aster Database 6.0 and later release uses memory cgroups in order to control
query memory usage. However, on Aster Appliance 2 hardware, user and ARC processes do
not progress as expected. Therefore, when upgrading to Aster Database 6.0 and later, a
consideration should be made to disable the CGROUP and SWAPACCOUNT functions on
TDC SUSE 2.6.32.54-0.29.TDC.1.R.7.
To disable the CGROUP and SWAPACCOUNT functions on SUSE 2.6.32.54-0.29.TDC.1.R.7
on only Appliance 2, perform these steps:
1
Edit the /etc/sysconfig/teradata/bootmenu file to set the CGROUP_DISABLE and
SWAPACCOUNT functions to blank:
•
CGROUP_DISABLE=""
•
SWAPACCOUNT=""
2
Run /sbin/SuSEconfig.
3
Reboot the nodes.
FIXED: Query Execution Time After Admission Control Limit
Reached is Misleading
Issue ID: BH-975
Details: The command “ncli query showrunning” does not show the correct queries after the
admission control limit has been reached. The reported execution time for a query will be
equal to the time waiting in the queue plus the real execution time. That means if a query gets
queued for 600 seconds, and then gets executed in 10 seconds, the reported execution time
will be 610 seconds.
FIXED: Node cannot softrestart after a high disk full is reached
Issue ID: BH-1185
Details: If the disk usage in a disk partition exceeds 90%, after a cluster restart the node may
need to be manually cleaned before it can be incorporated back to the cluster. Please contact
Teradata Global Technical Support (GTS) if you encounter this scenario.
FIXED: After Restart of a Busy Cluster, Some Processes are
Inadvertently Killed
Issue ID: BH-1338
Details: When a cluster running many queries is shut down and restarted, processes may fail,
rather than continuing to execute. This condition is more likely to occur when the cluster has
many nodes or many vworkers and is running many SQL-MapReduce queries just before
shutdown.
If you find that all or most of your queries are failing upon a cluster soft startup or restart, you
may have encountered this problem. The error message when queries fail in such cases is:
Aster Database 6.20 Release Notes
20
Teradata Aster® Database 6.20 Release Notes
Naming Convention for Teradata Aster Releases
I/O exception and statement cannot be retried. Please see log for more
information.
To work around this, do the following to fully clear out the record of the queries that were
running before the shutdown:
1
Wait for the queries to finish. You can use the AMC to ensure that all queries have
completed.
2
Log in to the queen node as root.
3
Run the following command:
# /home/beehive/sqlstore/bin/psql -h localhost -p 8000 -U _bee_sys
-d _bee_stats -c "update _bee_special.beehive_statement set
job_id=null where job_id is not null;
4
You will be prompted for the _bee_sys password. Enter it and press <Enter>.
5
Soft restart the cluster.
FIXED: Error in JSON file
Issue ID: ANLY-1637
Details: A syntax error in a JSON file prevents the CfilterViz analytic function from installing
properly.
To work around this problem, remove the JSON file from the package. The CfilterViz function
will install without the JSON file.
FIXED: Disable Memory CGROUPS on Commodity Hardware
Running the Red Hat Linux OS (Required)
Issue ID: BH-5513
Details: The Aster Database 6.0 and later release uses memory cgroups in order to control
query memory usage. However, on Commodity hardware, processes do not progress as
expected. Therefore, when upgrading to Aster Database 6.0 or later, you must disable the
CGROUP function on commodity hardware running the Red Hat Linux operating system.
To disable MEMORY CGROUPs on Commodity hardware running the Red Hat Linux
operating system, execute this command as a single line on the coordinator:
# ncli node runonall "curl 'http://127.0.0.1:1996/std/
configflags?memorySubsystemEnabled=false'"
Naming Convention for Teradata Aster
Releases
Teradata Aster release naming convention has changed beginning in January 2013. The new
release naming convention is as follows:
•
AD: Aster Database
•
AC: Aster Client
Aster Database 6.20 Release Notes
21
Teradata Aster® Database 6.20 Release Notes
End-of-Life and Deprecation Notices
•
AA: Aster Analytics Foundation
Release numbering for all of the above will follow this convention:
XX.YY.ZZ.nn
where:
•
XX is a major release.
•
YY is a minor release.
•
ZZ is a maintenance release.
•
nn is a efix or hotpatch.
We use this terminology:
•
major release: Major releases of Aster typically introduce new features.
•
minor release: Point releases of Aster Database typically provide feature enhancements
and bug fixes. A point release may also introduce new features.
•
maintenance release: Maintenance releases of Aster typically provide only bug fixes.
•
efix or hotpatch: Hotpatch release are introduced to address customer issues of an urgent
nature.
End-of-Life and Deprecation Notices
This section contains End-of-Life and Deprecation Notices for Aster Database releases only.
Backup and Restore of Aster Database Using Teradata Data Stream
Architecture
Backup and Restore of Aster Database Using Teradata Data Stream Architecture (Teradata
DSA-Aster BAR) is no longer a supported feature of AD 6.20.xx.xx releases. Aster Database
customers may continue to use the existing Aster backup utility. For additional information
about this feature support change, contact your Customer Support Representative.
Disallow New Use of HIGH and MEDIUM Compression Levels
The use of HIGH and MEDIUM levels of compression when new tables and indexes are
created is disallowed with this release. These levels are also disallowed in the ALTER TABLE
and ALTER INDEX commands. However, existing tables and indexes with HIGH and
MEDIUM levels of compression will continue to be supported, so you will not be required to
recreate tables and indexes. However, you are required to change scripts that create and alter
tables and indexes to use only the accepted syntax.
Templeton webHCat Service
The Aster-Hadoop connector no longer uses the HCatalog RESTful service (the Templeton,
webHCat service).
Aster Database 6.20 Release Notes
22
Teradata Aster® Database 6.20 Release Notes
Contacting Teradata Global Technical Support (GTS)
Hadoop Versions
Hadoop versions CDH 4.5, HDP 1.x, and TDH 1.3.2 are deprecated in this release.
ncli node showinterfaces
The ncli node showinterfaces command is no longer supported.
ncli system addnode
The --clean option and adding a node using a mac address are no longer supported.
Hardware
Teradata Aster® MapReduce Appliance 2.
AMC: Hard Restart
Effective with the release of AD6.10, the Hard Restart button is no longer available in the
AMC.
Contacting Teradata Global Technical Support
(GTS)
For assistance and updated documentation, contact Teradata Global Technical Support
(GTS):
•
Support Portal: http://tays.teradata.com/
•
International: 212-444-0443
•
US Customers: 877-MyT-Data (877-698-3282)
Third Party Licenses
Your Aster installation includes a number of open source products. The license text for these
products is available in the Aster Database User Guide, in the chapter "Licenses" and on your
Aster queen, as a set of text files in the /home/beehive/licenses directory.
About This Document
Supported Version Updates
This document supports the AD 6.20, AD 6.20.01, AD 6.20.02, AD 6.20.03, and AD 6.20.04
releases until otherwise indicated in a replacement publication.
Aster Database 6.20 Release Notes
23
Teradata Aster® Database 6.20 Release Notes
About This Document
Version History
This document, which is part of the Aster Database 6.20 documentation library, was updated
in March, 2017.
Table 1-1: Version History Table
Release
Product ID
Date
Note
AD 6.20.04
B700-6006-620K
March 2017
Updated to support
AD 6.20.04
AD 6.20.03
B700-6005-620K
December 2016
Updated to support
AD 6.20.03
AD 6.20.02
B700-6004-620K
August 2016
Updated to support
AD 6.20.02
AD 6.20.01
B700-6003-620K
April 2016
Updated to support
AD 6.20.01
AD 6.20.01
B700-6002-620K
April 2016
Updated to support
AD 6.20.01
AD 6.20.01
B700-6001-620K
February 2016
Updated to support
AD 6.20.01
AD 6.20
B700-6000-620K
November 2015
Copyright and Legal Statement
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, Applications-Within, Aster, BYNET, Claraview, DecisionCast, Gridscale, MyCommerce, QueryGrid, SQL-MapReduce, Teradata
Decision Experts, "Teradata Labs" logo, Teradata ServiceConnect, 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.
Amazon Web Services, AWS, [any other AWS Marks used in such materials] are trademarks of Amazon.com, Inc. or its affiliates in the United
States and/or other countries.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
Apache, Apache Avro, Apache Hadoop, Apache Hive, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks of
the Apache Software Foundation in the United States and/or other countries.
Apple, Mac, and OS X all are registered trademarks of Apple 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.
CENTOS is a trademark of Red Hat, Inc., registered in the U.S. and other countries.
Cloudera, CDH, [any other Cloudera Marks used in such materials] are trademarks or registered trademarks of Cloudera Inc. in the United
States, and in jurisdictions throughout the world.
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.
Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other
countries.
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 Dell 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.
Aster Database 6.20 Release Notes
24
Teradata Aster® Database 6.20 Release Notes
About This Document
Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries.
Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license.
SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries.
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: [email protected].
Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata
Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform,
create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata
Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including
developing, manufacturing, or marketing products or services incorporating Feedback.
Copyright © 2017 by Teradata. All Rights Reserved.
http://www.teradata.com/Teradata-Aster/overview/
Aster Database 6.20 Release Notes
25