Always shutdown TD database before powering off, rebooting, or shutting down Linux on AWS/Azure/TDVM

Teradata Database on Azure
Teradata Employee

Always shutdown TD database before powering off, rebooting, or shutting down Linux on AWS/Azure/TDVM

Product Categories  
Teradata on Amazon Web Services (AWS),Teradata on Azure,Teradata on VMWare  
 
 
 
 
   

It is very important to shutdown the database on teradata (tpareset -x comment) before powering off, rebooting, or shutting down Linux on AWS/Azure/TDVM/Physical Systems.
Failure to do so can lead to many problems including:

  • Offline Vprocs
  • Fatal Vprocs
  • NFR (Node Failure Recovery) nodes automatically starting up similar to HSN (Hot Standby Nodes) on physical systems.
  • Ghost or phantom nodes joining the database configuration
  • Data loss / Data Corruption
  • Billable charges by Teradata to recover data
 
 
 
   
Teradata on AWS (Amazon Web Service)
Teradata on Azure (Microsoft Cloud)
TDVM (Teradata on VMWARE)
Teradata physical hardware​
 
     
       
 
 
   
Before powering down or rebooting any nodes from any GUI (Graphical User Interface)​, ssh to one of your Teradata nodes, switch to user root (sudo su -) and issue a tpareset -x comment.
 
Example:
 
# /usr/pde/bin/tpareset -x Shutting down Teradata for maintenance
 
Usually with-in a minute or so the database should show that it is down (DOWN/HARDSTOP state). Here is how to check:
 
# pdestate
PDE state: DOWN/HARDSTOP