Key Changes in System Behavior - Teradata Tools and Utilities

Teradata Tools and Utilities Release Definition

Product
Teradata Tools and Utilities
Release Number
15.10
Published
December 2016
Language
English (United States)
Last Update
2018-05-15
dita:mapPath
ygi1475183176353.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2029
lifecycle
previous
This section includes key changes in system behavior made to the Teradata Tools and Utilities suite of products, as well as deprecated/removed features.
The information provided in this section is only a subset of the changes included in this release, and should not be considered a comprehensive list of all possible changes that may affect your applications.
The following table lists key changes in system behavior made to the Teradata Tools and Utilities suite of products.
Key Changes in System Behavior
Key Change Description
Client Installation
N/A The Teradata Tools and Utilities (TTU) Products can now be installed at a location provided by the user.
Teradata Basic Query Utility
BTEQ-6517 BTEQ has historically been partially lenient in batch mode for certain command syntax violations and attempts to somewhat honor a "do what I meant" principle. This was not done consistently, however. And as BTEQ's command syntax expanded, certain leniencies became impossible to continue to provide. Eventually it became clear that new command validation behaviors had to be made strict upfront to ensure extensibility. So as an aid for identifying poorly written existing scripts that may eventually require correction, BTEQ will now generate actionable warning messages to indicate in detail when it has been lenient about invalid syntax.
Examples:
.QUIT junk

 *** Warning: Invalid command token 'JUNK' found.
              Expected a return code number or keyword.
              The value given has been ignored.
              Future BTEQ versions may not be able to be lenient 
              about this invalid syntax. Correct the script to
              ensure it can continue to work.

.EXPORT REPORT FILE="foo.exp" extrajunktext ;

 *** Warning: Ignoring extra text found starting at 'extrajunktext'.
              The current instruction's remaining text has been discarded.
              Future BTEQ versions may not be able to be lenient
              about this invalid syntax. Correct the script to
              ensure it can continue to work.
BTEQ-6635 BTEQ: Workstation BTEQ now exits with a fatal error when the default DBS charset is UTF16 and charset has not been explicitly defined via BTEQ command line option (-c), or via the SET SESSION CHARSET command or via clispb.dat settings.
Teradata Index Wizard
DBM-29242 While displaying the existing indexes report for a workload, TIWIZ 15.10 displays the index type as ‘Primary AMP Index’, if the workload refers to a column partitioned table. ‘Primary AMP Index’ is the new index choice introduced in Database for specifying the hash distribution of rows to AMPS for a column-partitioned table.
Teradata JDBC Driver
DR 148961 Support backslash ( \ ) as LIKE ESCAPE character in pattern arguments of DatabaseMetaData methods.
DR 167410 Provide ResultSet SQLWarning when row count exceeds Integer.MAX_VALUE.
DR 174526 Improve ClientProgramName identification.
DR 179413 DatabaseMetaData getImportedKeys/getExportedKeys provide PK_NAME if available.
Teradata ODBC Driver
ODBC-16876 The new lightweight parser transforms the ODBC Scalar functions within the ODBC Escape Sequence syntax to the Teradata Database specific functions. The ODBC Escape Sequence for calling a scalar function is:

{fn scalar-function}

The new lightweight parser ignores ODBC scalar functions outside of the ODBC escape sequence (i.e. scalar-function vs. {fn scalar-function} ) and the query is passed as is to the Teradata Database. The query executes successfully if the Teradata Database supports the ODBC scalar function; otherwise the query produces an error. Please refer to Teradata Database Functions, Operators, Expressions and Predicates user guide for the list of the Teradata Database supported scalar functions.
Teradata Query Scheduler
DBM-32399 Remove MDS Parser dependency for TQS 15.10.
Teradata System Emulation Tool
DBM-30904 TSET 15.10 implements emulation of Stored Procedures (SP) and external Stored Procedures (XSP) using command line operation. The limitation of exporting execution plans alone for USING queries (parameterized queries) is removed in TSET 15.10. TSET15.10 can capture object definitions also for parameterized queries.
DBM-30939 BLCBlkURatio (decompression ratio) is renamed as BLCCompRatio (compression ratio) in statistics display, as compression Ratio field title “BLCCompRatio” is more intuitive for customers and is easier to compare with value returned by Ferret utility.
DBM-30989 TSET 15.10 implements emulation of ‘InMemoryEnabled’ and ‘AVX2Supported’ flags data related to In-Memory Feature by exporting and importing the same during export and import operations respectively. (Ref : DBM-30989 /DBM-30979).
Teradata Workload Analyzer
DBM-30941 In TWA 15.10, workload classification is enhanced to include IPE criteria. User can classify a workload based on whether workload is qualified to use Incremental Planning and Execution feature of the Optimizer.

Deprecated/Removed Features

The following table lists the features that have been deprecated or removed from the Teradata Tools and Utilities 15.10.04 release.

Deprecated/Removed Features
Feature Description
Legacy ODBC SQL Parser

The Legacy ODBC SQL parser has been deprecated. The EnableLegacyParser DSN option has been added to still allow using Legacy parser, if desired, however, the default value has been set to the new parser.

Teradata ODBC 15.10 Driver users are strongly advised to test existing applications with the new ODBC SQL parser, and modify them if the SQL does not conform to the ODBC Specification or the Teradata Database SQL Syntax/Scalar Functions. The new applications or enhancements to existing applications must conform to the new parser.

The Legacy ODBC SQL parser has been capped to support Teradata Database features for Releases 15.00 and prior. The Database features for Releases 15.10 and above are not supported. Users are strongly advised to retain the default value for the EnableLegacyParser DSN option when using the Teradata ODBC 15.10 driver with Teradata Database 15.10 or later. Support for the capped Legacy ODBC SQL parser will be maintained through Teradata ODBC 16.xx release program, but discontinued afterwards.