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. Customers, who are upgrading, must review this section for potential impacts that may require action on their part.
17.10 Key Changes in System Behavior
|Basic Teradata Query Reference||Starting with TTU 17.10, only a 64-bit version of AIX BTEQ is available. Any previously created user exits in use, such as for BTEQ's NOTIFY control or CLI LOGON, must be recompiled to be 64-bit rather than 32-bit so that they can be successfully loaded at run-time and therefore continue to work as needed.|
|.NET Data Provider||The .NET Data Provider no longer supports .NET Framework 4.5.2. The minimum required version is .NET Framework 4.6.1.
The Teradata Entity Framework Core Provider no longer supports .NET Core 2.2. The minimum supported version is .NET Core 3.1.
|TTU Installer||The name of the TTU installer script is now setup.sh on UNIX/Linux platforms. Previously it was known as setup.bat.|
|TTU Installer||TTU Windows bundle does not contain #.bat script. setup.bat script is the replacement for #.bat script.|
|TTU Installer||TTU installer script (setup.sh) no longer supports "install all products except tdwallet (w)" option on UNIX/Linux platforms. It now supports the following two options along with installing selected packages: