To access this download, you must login.

About this download

Teradata Studio is an administration toolkit that helps users to create and administer database objects. It also provides a SQL Editor and Result Set Viewer for retrieving and displaying data fron your Teradata Database systems (Teradata, Aster, and Hadoop). It is built on the Eclipse Rich Client Platform (RCP). For more information on Teradata Studio, refer to the article Teradata Studio.

Teradata Studio contains several open-source components. A package containing the source code and licenses for these components is also available for download. This package does not contain proprietary Teradata source code.

Teradata Studio is a fully supported product by Teradata. 

For community support, please visit the Teradata Studio Forum.

► NOTE: This version requires Java Runtime Environment(JRE) 10. Mac OSX platforms 10.7 or greater does not provide an Apple JRE. Users must install Oracle's Java Developer Kit (JDK) 10 before installing Studio.

Access the Java downloads at Java SE Downloads.

README

 
Teradata Studio 16.20.09.00 release information.
 
Supported Platforms:
==================================== 
     Windows Server - Microsoft Windows Server 2012 and 2016 64-bit
     Windows 7      - Microsoft Windows 7,8,8.1 and 10 64-bit
     Ret Hat Server - Red Hat Advanced Server 6.0 and 7.0 64-bit
     Red Hat Platform - Red Hat Advanced Platform 6.0 and 7.0 64-bit
     SUSE Linux Enterprise - SUSE Linux Enterprise 11 64-bit
    - SUSE Linux Enterprise 12 64-bit
     CentOS 6        - CentOS 6 and 7 64-bit
     
     Apple Mac      - OSX 10.7, 10.8, 10.9, 10.10, 10.11, 10.12 and 10.13
 
 
Minimum Memory Required:
====================================
     4GB Memory, but 6GB Memory desired
 
Supported Teradata Databases Versions:
====================================  
     Teradata Database 15.0
     Teradata Database 15.10
     Teradata Database 16.0
     Teradata Database 16.10
     Teradata Database 16.20
     Teradata Database 16.20.00 Feature Update 1
     Teradata Database 16.20.00 Feature Update 2
    
Supported Aster on Hadoop Versions:
====================================  
      Aster on Hadoop 7.00.02
 
 
 
Supported Hadoop:
=============================================
     HDP 2.4, 2.5, 2.6, 2.6.4, 2.6.5
     Cloudera 5.11, 5.12.1, 5.13, 5.14, 5.15
 
Required Software:
====================================  
     - Java Runtime Environment (JRE) version 10
     - Mac OsX 10.7 or greater does not provide the Apple JRE. Users must
     install Oracle's JDK (not JRE) 10.
 
Install Instructions:
==================================== 
     Download the Teradata Studio zip file from the download site.
 
  For Windows install:
     1) Unzip the Teradata Studio package to your local file system.
     2) Run the setup.exe to launch the Teradata Studio installation.
     3) Teradata Studio is installed in the Program Files directory.
        For example, C:\Program Files\Teradata\Client\16.20\Teradata Studio. 
When Teradata Studio is started, a 'workspace' directory is created in your 
home directory (C:\Users\<user>\workspace-studio). This directory contains 
workspace files, including the SQL project folder. The teradata.log file is 
located in the install \workspace-studio\.metadata\Teradata directory.
 
 
  For Linux install:
    1) Unzip and untar the Teradata Studio package to your local file system.
 
        gunzip TeradataStudio__linux_x86.16.20.09.00.00-1.tar.gz
        tar -xvf TeradataStudio__linux_x86.16.20.09.00.00-1.tar
 
    2) Change directories (CD) to the TeradataStudio.16.20.09.00 directory
 
        cd TeradataStudio.16.20.09.00
 
    3) Switch to Super User or Root and run the Studio install script, passing
       the Studio RPM (Package Management) package:
 
        su 
        ./studioinstall TeradataStudio-16.20.09.00-1.x86.rpm
 
    4) Provide the path to where you would like to install Teradata Studio. 
       The default location is /opt/teradata. When Teradata Studio is started, a workspace 
       directory is created in the location where you launched Teradata Studio (TeradataStudio) from, 
       called workspace-studio. This directory contains workspace files, including the SQL project folder. 
       The teradata.log file is located in the install /workspace-studio/.metadata/Teradata directory.
 
    Note: To check whether Teradata Studio is installed or not, run the following RPM command:
 
        rpm -qa TeradataStudio64
    
    To remove the Teradata Studio product from your Linux system, run the following RPM command:
 
        rpm -e TeradataStudio64
 
  For Mac OSX Install:
    1) Unzip the Teradata Studio package to your local file system.
    2) Double click on the Teradata Studio.pkg package to invoke the Teradata Studio installer
    3) You can change the install location or use the default install location, which is the
       /Applications/TeradataStudio folder. When Teradata Studio is started, a 'workspace-studio' folder 
       is created in the user's Documents folder. This folder contains the workspace files, including the
       SQL project folder. The teradata.log file is located in the install workspace-studio\.metadata\Teradata directory.
    
    To uninstall Studio on the Mac OSX, open a Terminal window and run the Studio uninstall script:
 
       . ./studio_uninstall.sh
 
 
Running Teradata Studio:
==================================== 
    Windows:
       Double click the Teradata Studio desktop icon shortcut.
 
    Linux:
       Update your path variable to include the TeradataStudio directory. Execute TeradataStudio.
 
    Mac:
       Execute Teradata Studio in the TeradataStudio directory.
 
 
Changing the Teradata Studio Workspace and/or Configuration information directories
    - (using Roaming Profiles):
====================================================================================
When Teradata Studio is launched, it creates a workspace directory (called workspace-studio) in your 
USER HOME directory. If you want to change the location of your workspace directory, you must pass
the -data option into the TeradataStudio executable. You can do this by changing the Target parameter in the
Windows desktop shortcut or in the command window when launching Teradata Studio. For example:
 
"C:\Program Files\Teradata\Client\16.20\Teradata Studio\TeradataStudio.exe" -data "c:\Teradata Studio\My Workspace"
 
There is another directory (called .eclipse) created in your USER HOME directory that contains configuration 
information and jars for launching Teradata Studio. If you want to change the location of your configuration
directory, you must pass the -configuration option into the TeradataStudio executable. You can do this by changing
the Target parameter in the Windows desktop shortcut or in the command window when launching Teradata Studio.
For Example:
 
"C:\Program Files\Teradata\Client\16.20\Teradata Studio\TeradataStudio.exe" -configuration "c:\Teradata Studio"
 
You can combine both the -data and -configuration options on a single command line as well. This is often needed
when using a Roaming Profile that is not always accessible when running applications.
 
New Features
====================================
IDE-22279: Enabled Data Encryption by default for Teradata Connections.
[NOTE*: Users may experience significant Performance Lag as Encryption of all data traffic will put more overhead to the application.]
 
IDE-22389: Studio support Java 10 version. In order to install Studio user need to install Java 10 on their machines.
[NOTE*: Discontinued support of 32-bit platforms since there is no 32-bit Java 10 distribution from Oracle.]
 
IDE-22272: Supported and Certified Singed Builds for Windows platform.
 
Bug Fixes
==================================== 
The following bugs were fixed in 16.20.09.00:
 
IDE-22391 : Misleading error box and no error should be shown.
IDE-22381 : QVCI Error when trying to open View definition from Studio administration window once QVCI feature is disabled.
IDE-22415 : Studio application (on Mac 10.13) crashes while performing cut or delete operations on text in SQL Editor.
IDE-22410 : Result Set: Sort order is not intended according to sort arrow image for Date Columns in Studio and Express.
 
Hadoop Configuration Support:
=============================
Teradata Studio provides an option to transfer data to and from Hadoop systems using its feature called the
Smart Loader for Hadoop. The Smart Loader for Hadoop uses the Teradata Connector for Hadoop (TDCH), which is
installed on the Hadoop node, to provide the data transfer to and from the Hadoop system. The following are the system requirements of TDCH:
 
    Supported Teradata Database versions:
 
        Teradata Database 15.0
Teradata Database 15.10
        Teradata Database 16.0
 
        Teradata Database 16.10
Teradata Database 16.20
Teradata Database 16.20.00 Feature Update 1
Teradata Database 16.20.00 Feature Update 2
 
    Supported Hortonworks Data Platform (HDP) versions:
         HDP  2.4, 2.5, 2.6, 2.6.4, 2.6.5
    
    Supported Cloudera Hadoop (CDH) versions:
        CDH 5.11, 5.12.1, 5.13, 5.14, 5.15
 
 
Teradata Connector for Hadoop Setup:
====================================
The TDCH must be installed and configured on the Hadoop system. Studio
uses Oozie to submit the data transfer workflow on the Hadoop System. Please follow these instructions
to configure the Hadoop System and create the Oozie workflow files.
 
1) If the script is not already on your Hadoop system, download and install the TDCH onto your Hadoop system.
2) Navigate to the TDCH scripts folder in the TDCH install directory (default location: /usr/lib/tdch/1.5/scripts)
3) Execute the configureOozie.sh script as root user, providing the locations of your Hadoop services.
    
The usage of the configureOozie.sh script is as follows (this is all a single line):
 
    Usage: ./configureOozie.sh nn=nameNodeHost [nnHA=fs.default.value] [rm=resourceManagerHost] [oozie=oozieHost] [webhcat=webHCatalogHost] [webhdfs=webHDFSHost]
        [nnPort=nameNodePortNum] [rmPort=resourceManagerPortNum] [ooziePort=ooziePortNum] [webhcatPort=webhcatPortNum] [webhdfsPort=webhdfsPortNum] 
        [hiveClientMetastorePort=hiveClientMetastorePortNum] [kerberosRealm=kerberosRealm] [hiveMetaStore=hiveMetaStoreHost] 
        [hiveMetaStoreKerberosPrincipal=hiveMetaStoreKerberosPrincipal]
 
(The parameters are entered on a single line. The parameters surrounded by [ ] are optional. The “[“ and “]” are not part of the command.)
 
    nn - The Name Node host name (required)
    nnHA - If the name node is HA (High Availability), specify the fs.defaultFS value found in core-site.xml
    rm - The Resource Manager host name (uses nn parameter value if omitted)
    oozie - The Oozie host name (uses nn parameter value if omitted)
    webhcat - The WebHCatalog host name (uses nn parameter value if omitted)
    webhdfs - The WebHDFS host name (uses nn parameter value if omitted)
    nnPort - The Name node port number (8020 if omitted)
    rmPort - The Resource Manager port number (8050 if omitted)
    ooziePort - The Oozie port number (11000 if omitted)
    webhcatPort - The WebHCatalog port number (50111 if omitted)
    webhdfsPort - The WebHDFS port number (50070 if omitted)
    hiveClientMetastorePort - The URI port for hive client to connect to metastore server (9083 if omitted)
    kerberosRealm - name of the Kerberos realm
    hiveMetaStore - The Hive Metastore host name (uses nn parameter value if omitted)
    hiveMetaStoreKerberosPrincipal - The service principal for the metastore thrift server (hive/_HOST if ommitted)
 
The port numbers are HDP’s defaults. So, if the system being set up has all the services
hosted on a single system on the default ports, only the nn parameter is needed.
 
The script will exit with an error message if the TDCH is not in its expected location.
Otherwise the script will display a message indicating the parameters values. A sample
message is as follows:
 
The following is the specification of the Hadoop services used by the Oozie workflows:
{
        "Distribution":"HDP",
        "DistributionVersion":"2.4",
        "TeradataConnectorForHadoopVersionÓ:Ó1.5.3Ó,
        "WebHCatalog":"hostname",
        "WebHCatalogPort":50111,
        "WebHDFS":"hostname",
        "WebHDFSPort":50070,
        "JobTracker":"hostname",
        "JobTrackerPort":8050,
        "NameNode":"hostname",
        "NameNodePort":8020,
        "NameNodeHA":"fs.defaultFS",
        "NameNodeHAConfigured":true,
        "Oozie":"hostname",
        "OoziePort":11000,
        "HiveClientMetastorePort":9083
        "HiveMetaStoreKerberosPrincipal":"hive/_HOST",
        "KerberosRealm":"",
        "HiveMetaStore":"hostname"
}
 
** You must also make sure the Teradata IDE/Studio client machine can access the Hadoop system services (hostnames and ports provided to configureOozie script).
Thus, you may need to add the Hadoop services host names and IP addresses to your host file or DNS service. 
 
 
HORTONWORKS SELF_SIGNED CERTIFICATES:
=====================================
 
The certificate used by the Knox server needs to be added to the Java runtime's certificate store. You can save the certificate with a web browser. 
For example, with Chrome, you can:
• Enter the Knox server:port in the address bar. It will say that the connection is not private
• Click Advanced, then click on the Proceed to site link
• Click on the lock in the address bar and select Details
• Click View certificate
• Select the Details tab in the resulting dialog and click the Copy to file... button
• In the resulting Certificate Export Wizard, save the certificate as Base-64 encoded
 
(Other browsers have similar methods to get to the Certificate Export Wizard)
 
Alternatively, on the Knox server, run the command:
 
     keytool -export -alias gateway-identity -rfc -file knox.crt -keystore <path to gateway.jks keystore (eg. /usr/lib/knox/data/security/keystore/gateway.jks)>
 
To install the certificate into your Java Runtime certificate store, run the command:
     %JDK_HOME%\bin\keytool.exe -importcert -alias "TDH240 Knox self-signed certificate" -file cert_location/<filename>.txt -keystore %JRE_HOME%\lib\security\cacerts
Where %JDK_HOME% is an environment variable with the location of a JDK and %JRE_HOME% is the location of the JRE used to run Studio.
 
The keytool.exe will ask for the password to the certificate store. It is “changeit” unless you’ve changed it