For those new to Teradata, Teradata Express for VMware Player and Teradata Express for Amazon EC2 are great ways to get started with our database. These preconfigured, ready to go virtual images make getting started quick and painless. All that's left to do is fire up a query tool and write some SQL, right? Well, that is mostly true, but what if something doesn't seem to be working properly? What do you do then? For these situations, I've compiled this short "2 minute guide" to help get you over some basic issues.  These are all command line tools, so first open a Linux terminal session and let's get started.

Checking Teradata Status

Let's start with the basic status tool, pdestate:

# pdestate -a

If all is well and Teradata is running, you will see this output:

DBS state is 5: Logons are enabled - The system is quiescent


Stopping the database

Should you need to stop the database in a controlled manner, the command is:

# tpareset -x bringing down the database


The syntax for this command is tpareset -x {comment}, where the comments can be used for logging/auditing purposes to capture the reason that the database was stopped.

Here is output from this command.  Notice the prompt as a last check to make sure that this is what you really want to do.

You are about to shutdown the database
on the system
Do you wish to continue (default: n) [y,n] y

Once the database has been stopped, you can check the status of the database like we did earlier:

# pdestate -a

But if there was a problem that halted Teradata instead of a controlled shutdown, you will see this message from pdestate:

#pdestate -a
"down/hardstop" is down


Restarting Teradata

To restart Teradata after manually stopping the database or to restart after a 'hardstop' event, run this command:

# /etc/init.d/tpa start

Which should give this output:

Teradata Database Initiator service is starting...
Teradata Database Initiator service started successfully.


To restart Teradata if it is any state other than "down/hardstop" use the command:

# tpareset -f restarting

This asks for a confirmation before beginning the restart process:

You are about to restart the database
on the system
Do you wish to continue (default: n) [y,n] y


You can then issue the watch the various start up levels by issuing the pdestate command every few seconds..

# pdestate -a


# pdestate -a


# pdestate -a
DBS state is 1/5: DBS Startup - Voting for Transaction Recovery


# pdestate -a
DBS state is 1/4: DBS Startup - Starting PE Partitions


# pdestate -a
DBS state is 5: Logons are enabled - The system is quiescent



If you are running into problems getting Teradata started, the first place to check for clues is in the log file:

tail /var/log/messages

And finally, to check your storage, use the verify_pdisks command:

# verify_pdisks
All pdisks on this node verified.

You may see some warning messages with this, but what we're looking for is the final 'verified' message.

mohammad101 1 comment Joined 11/13
25 Nov 2013

is there a similar which can be done on windows 7 please ?

Mohammad Rabie

pbbass 2 comments Joined 05/11
21 Mar 2014

I'm new to VMWare.   How do I take a spreadsheet on my Windows 7 Desktop and load to the
TD 14.10 VMware image so the spreadsheet data could be loaded into Teradata ?

SmarakDas 25 comments Joined 02/12
08 Sep 2014

Hello Mike,


Thanks for your article. Just have a few question:


(a) The command "tpareset -x" or "tpa start" are executed at the root level and they shall bring down and bring up all the nodes in the system. Are the same command applicable within a node ? 


(b) If I want to bring down a specific node, can I do a "ssh <node>" and execute the same command ? 


(c) Is there any way to bring a node down from the root level ?




SmarakDas 25 comments Joined 02/12
08 Sep 2014

Also Mike, can you tell us which document lists the various PDE States & DBS States along with their meaning ? 
I am trying the understand the difference between PDE & DBS settings during the Database Up & Down scenario. 

Langaliya.Nirav 1 comment Joined 04/11
09 Dec 2014

Hi Mike, 
I am getting below msgs

TDExpress14.0.3_Sles10:~ # verify_pdisks

Unable to open TVSA file /etc/opt/teradata/tdconfig/tvsa_data for reading.

Error getting TVSA system-id from /tvsa_data file.  But will continue to verify Pdisks.

All pdisks on this node verified.


--Nirav Langaliya

21 Apr 2015

How can I prevent Teradata database (and service) from starting everytime I start the virtual machine?

nkardos 4 comments Joined 10/10
13 Aug 2015

I also have the TVSA file problem on official TVME virtual machines.
Is there any solutions for that?

Ashwin4tera 18 comments Joined 11/11
25 Aug 2015

Good Article! Kind quick Refrence!

You must sign in to leave a comment.