Teradata Express 14.0 for Amazon EC2 Configuration Guide

The Teradata Database channel includes discussions around advanced Teradata features such as high-performance parallel database technology, the optimizer, mixed workload management solutions, and other related technologies.
Teradata Employee

Teradata Express 14.0 for Amazon EC2 Configuration Guide

Cloud Computing is a computing service provisioning and delivery model in which users get access to dynamically scalable computing capacity over the network in a pay-as-you-use payment scheme. While its attractiveness may differ depending on whom you've talked to, its service-oriented nature gives users two important benefits: ease of application deployment (someone else's hard works laying down the hardware and software foundation) and on-demand access anytime from anywhere. These characterstics make Cloud Computing ideally suited for developers who want to quickly try something out in an isolated "good" environment without the overhead of system setup or the capital expenses of paying for systems they no longer need after they are done. 

Teradata Express 14.0 for Amazon EC2 runs on top of Novell SLES10 and the industry-leading Amazon EC2 Cloud Computing platform. It has Teradata database 14.0 and client utilities pre-installed and sample databases included. The old Express Edition limitation with 4GB storage has now been expanded to 1TB, giving developers more freedom to experiment with larger datasets and with more real-life development and testing needs. If you are interested, this post will show you how to automatically setup Teradata Express 14.0 for Amazon EC2 using an automated script.  Note, this article assumes that you have some working knowledge of Amazon EC2 platform.

Please note that while this product is not officially supported, you can talk to other users and get help in the Cloud Computing forum.


  1. Have your Amazon AWS account credential ready (if you don't yet have an account, sign up at http://aws.amazon.com/).
  2. An SSH client (ssh, Putty, etc) will be needed to complete the Initialization porcess
  3. Register with us for Teradata Express 14.0 for Amazon EC2.
  4. Once you receive a confirmation email from us, proceed to the next section.

How to Connect to Amazon AMI Instance(s)

After receiving the confirmation from Teradata, log in to your Amazon EC2 account and go to your EC2 Dashboard.

Launch a New Instance of Teradata Express 14.0 for Amazon EC2

  1. Click the "Launch Instance" button on the EC2 Dashboard.
  2. Select "Classic Wizard" and then "Continue".
  3. Choose "My AMIs" and select "Private Images" from the pull-down menu.
  4. Select "ami-99f65af0".
  5. Cluster Compute (cc1.4xlarge, 23GB) is the smallest configuration needed to support TD Express 14.0.
  6. Select your Availability Zone preference. If you pick "No Preference" remember which one you get because you must create the disk volumes in the same zone as your TD Express 14.0 image. Click "Continue".
  7. No Advanced Instance Options are required to run TD Express 14.0. Hit "Continue".
  8. Add Tags if desired. No tags are required to run TD Express 14.0. Hit "Continue".
  9. Create a Key Pair if desired. A key pair is not required to run TD Express 14.0. You may want to use a key pair for added security for your instance. Click "Continue".
  10. Choose an existing Security Group or create a new one. The security group you choose must have the following ports open:
    • 22 - for SSH conncetivity
    • 80 - standard web port (HTTP) for Viewpoint connectivity
    • 1025 - Teradata database access port, for client tools and utilities
    • 8080 - alternate HTTP port.

  1. Hit "Launch".


Creating and Attaching Disk Volumes

  1. Return to your EC2 Dashboard.
  2. Under Elastic Block Storage select "Volumes".
  3. Click "Create Volume".

  4. You will need to create two (2) volumes, each half the size of your desired database; e.g. for a 40GB database create two 20GB volumes.
  5. Important. The Availability Zone must be the same as the instance of TD Express 14.0 you wish to attached it to.
  6. No Snapshot needed. Click Yes, Create.
  7. Repeat for the second Volume.
  8. Highlight the first of the new Volumes and hit Attach Volume under the More Menu.
  9. Choose your instance of TD Express 14.0 launched above.
  10. For the first device name it /dev/xvdf.
  11. Repeat for the second Volume, but name it /dev/xvdg.
  12. Wait for the volumes to complete the Attach process. To ensure that the process has completed, select each volume individually in the console, and under the Details tab, wait for the Attachment value to change to attached.

Configure the Database

You are ready to connect to the instance and complete the initialization process. You can use a SSH client (ssh, Putty, etc) to connect to the external IP address of the instance, make sure you specify your rsa key file with the connection attempt if you have set one up. Setup scripts automatically run at the first log-in.

  1. Start your SSH client (ssh, PuTTy, etc.)
  2. From your EC2/Instances dashboard, hit the checkbox on your new instance.
  3. Get the public DNS for the instance you checked above in the form ec2-174-XXX-XXX-XXX.compute-1.amazonaws.com
  4. Copy and past the instance public DNS into your SSH client. Or if you have ssh installed on the command line, enter: ssh root@ec2-174-XXX-XXX-XXX.compute-1.amazonaws.com
  5. Connect to the TD Express image via your SSH client.
  6. Your username and password are both: root
  7. Set-up script will run and the first thing you will see is the Teradata Express License Agreement. Accept by hitting the Enter key.
  8. You will now see the set up screen below. Select ([x]) each of the two drives using the space bar and arrow keys.
  9. Tab to the next section to set the super user password.
  10. Keep or disable the sample database and Viewpoint as desired.
  11. Tab to Next and hit Enter.

12. If you get an error indicating that Linux does not recognize one of your disks, type reboot into the console. Wait two minutes and login again using the SSH client and you should see the screen below. Note that it may take a significant length of time for the configuration process to complete. Wait until this happens as seen below. When complete, select Done. You hopefully now have a running Teradata instance!

Test your initialized Teradata Express instance

BTEQ is the standard Teradata command line query tool, and can be used to test your Teradata installation. Login to the EC2 instance as above.

  • From the shell prompt: TDExpress14.0_Sles10:~ # bteq
  • When asked for your logon: .logon
  • When asked for your password: dbc
  • You should now be in the bteq session (you'll see a message *** Logon successfully completed).
  • Now, let's execute some SQL, e.g. select * from dbcinfo; and you should see results similar to:
select * from dbcinfo;

*** Query completed. 3 rows found. 2 columns returned.
*** Total elapsed time was 1 second.

InfoKey InfoData
------------------------------ --------------------------------------------

Or, similarly if you have downloaded TTU 13.10, you can use the SQL Assistant tool to run the same command. 

Monitoring Teradata Express on EC2 using Viewpoint

You can connect to the Viewpoint running on the virtual machine. To see all you can do with Viewpoint look here.

The Viewpoint services are started automatically when you start up the virtual machine if you have configured it during the set-up process above. To login to Viewpoint follow the steps below.

  1. Get the public DNS for your EC2 instance (it shoudl be of the form ec2-174-XXX-XXX-XXX.compute-1.amazonaws.com).
  2. Open a new browser window
  3. Paste the DNS into the top box.
  4. Login to Viewpoint as username = admin and password = teradata.
  5. Towards the upper right of the main Viewpoint portal page, select Admin > Teradata Systems.
  6. Add a System. Go to the Setup > General form.
    • System Nickname - TDExpres
    • Check the System Enabled checkbox next to the System Nickname.
    • TDPID is set to only monitor localhost and cannot be modifed.
    • Login Name = "viewpoint"
    • Login Password = "viewpoint"
    • Check Enable all data collectors
    • Click Apply.
  7. Under Setup Data Collectors. Set all data collectors to delete data after 50 MB and 1 week.
  8. Under Setup/Monitor rates. Check Enable Session.

See the General Set Up Screen Bleow

Warning on Disk Space Data Collector

When starting yout TD EC2 instance for the first time, a timing error during initialization can occur. This will show up as a warning triangle next to the "Disk Space" data collector. When you click on the triangle the warning text is:

“Unable to retrieve Teradata database version or retrieved unknown Teradata database version null! Retrieved unknown Teradata database version null!”

This warning will clear itself during the next 12 hours as the system refreshes itself. You can also manually clear this warning by doing the following:

  1. Go back to your SSH interface.
  2. From the shell prompt: TDExpress14.0_Sles10:~/etc/init.d/dcs restart 
  3. Wait to complete.
  4. Repeat Step 2.

The initialization glitch should now be cleared and should not return.

Starting a Portlet

  1. On the top right of your Viewpoint screen you will see a link "<< Back to Portal". Click it.
  2. You are now on the main Viewpoint screen and can now start adding portlets.
  3. Click on the "Add Content" pulldown menu
  4. Select "Monitoring:
  5. Select "Canary Response Times"

This portlet will periodically submit a query to the system and measure its response time. Sometimes called a system heartbeat.


You now have a fully functioning version of Teradata 14 running in the Amazon cloud. Have fun! And don't forget to terminate your instance if you are done with it. If you leave it running you will incur usage charges! Note: If you terminate your instance you will have to go through the setup again, and you will lose all your data.  Make sure you backup your data and any needed Teradata configuration files in /etc/opt/teradata/tdconfig.

Also, please note that while the Teradata Express family of products is not officially supported, you can talk to other users and get help in the Cloud Computing forum.

Not applicable

Re: Teradata Express 14.0 for Amazon EC2 Configuration Guide

Thanks for this useful EC2 Configuration guide. It works fine in a day but when I stopped and re-start the instance, I can't anymore use the Teradata EC2 v14.0. It has a warning on the TD system and most of the collectors.

It is also giving me a "RDBMS CRASHED OR SESSIONS RESET".

I have to terminate and re-install again.
Teradata Employee

Re: Teradata Express 14.0 for Amazon EC2 Configuration Guide


When you restart the instance, log into the linux kernel and type the following command

/etc/init.d/tpa start

This will start the database.

See if that helps.

Re: Teradata Express 14.0 for Amazon EC2 Configuration Guide

Before you do a tpa start take a look for /var/opt/teradata/tdtemp and delete the file panicloopdetected if it is there. If you do a tpa start with it present it won't start.

Not applicable

Re: Teradata Express 14.0 for Amazon EC2 Configuration Guide

Can you provide a schema for trial?


Re: Teradata Express 14.0 for Amazon EC2 Configuration Guide

Hello, I am uanble to connect to my EC2 instance via SSH. I keep getting network time out error.

Issue: Database configuration, step 4

Any help will be appreciated.



Teradata Employee

Re: Teradata Express 14.0 for Amazon EC2 Configuration Guide

Do you have port 1025 open? See the User Guide for all of the ports and their configuration.

Re: Teradata Express 14.0 for Amazon EC2 Configuration Guide

Once this is configured can it be stopped then restarted and retain all the data.  The reason being that this is required for demo purposes and I don't want to keep the instance running all the time due to cost reasons.

Teradata Employee

Re: Teradata Express 14.0 for Amazon EC2 Configuration Guide

You can stop and start without losing data.


Re: Teradata Express 14.0 for Amazon EC2 Configuration Guide

I install TD Express AMI on AWS i2.xlarge instance. However, we have to restart the database by executing "/etc/init.d/tpa start" twice this week.

I have two block devices (500GB each) attached to this instance. The rest of the configurations are the same as this guide. Anything I can check to debug the issue?