{"id":4238,"date":"2018-10-27T09:22:27","date_gmt":"2018-10-27T09:22:27","guid":{"rendered":"https:\/\/dbtut.com\/?p=4238"},"modified":"2018-11-27T21:39:21","modified_gmt":"2018-11-27T21:39:21","slug":"how-to-start-and-stop-teradata-database","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2018\/10\/27\/how-to-start-and-stop-teradata-database\/","title":{"rendered":"How To Start and Stop Teradata Database"},"content":{"rendered":"
<\/p>\n
There can be different scenario’s where Teradata database needs to be stopped and started by database administrator or the database restarted automatically. So there are basically two types of restarts:<\/p>\n
\n
Scheduled restarts : User may input command to bring the database down for maintenance or software patch upgrades and bring it up and running once activity complete.<\/li>\n
Unscheduled restarts : System reboots automatically without user input. This may happen due to different reasons like power failure, hardware failure etc.<\/li>\n<\/ol>\n
In both the cases, database administrator needs to execute commands to check the status of the system and take appropriate actions depending on its current state.<\/p>\n
This can be done by using below command:<\/p>\n
# pdestate -a<\/pre>\n
<\/p>\n
1) If the teradata is already in ruuning state the the following message will be displayed:<\/p>\n
PDE state is RUN\/STARTED.<\/em> \nDBS state is 5: Logons are enabled – The system is quiescent<\/em><\/p>\n
2) If the teradata in not in running state than either of the following messages will be dispayed:<\/p>\n
a) PDE state is STOP\/KILLTASKS – indicates database has been intentionally stopped due to some reason.<\/em> \nb) PDE state is DOWN\/HARDSTOP\u00a0 — indicates system is halted due to some problem instead of controlled shutdown<\/em><\/p>\n
If you want to stop the Teradata database due to some reason like software patch upgrade, then use the below command:<\/p>\n
#tpareset -x {comments } --- comments show the reason to bring down the database later if someone needs to know the cause for database down.\r\nYou are about to shutdown the database<\/em>\r\non the system\u00a0<\/em>'<systemname>'<\/em>\r\nDo you wish to continue (default: n) [y,n] y<\/em><\/pre>\n
<\/p>\n
Now check its current state to make sure that database is down.<\/p>\n
#pdestate -a\r\nPDE state is STOP\/KILLTASKS<\/pre>\n
<\/p>\n
Now, once the schedule activity is completed, the Teradata Database needs to be started using below command:<\/p>\n
#\/etc\/init.d\/tpa start\r\nTeradata Database Initiator service is starting...<\/em>\r\nTeradata Database Initiator service started successfully.<\/em><\/pre>\n
<\/p>\n
Automatic\/Unscheduled Restarts<\/span><\/h3>\n
If database is halted due to some problem and current pdestate is DOWN\/HARDSTOP. Should you bring back the teradata database up and running, use the below command:<\/p>\n
# tpareset -f\r\nYou are about to restart the database\r\non the system\u00a0'<systemname>'\r\nDo you wish to continue (default: n) [y,n] y<\/pre>\n
<\/p>\n
If still the pdestate is like DOWN\/HARD\/KILLTASK than you can troubleshoot the problem by checking the log file by using the following command:<\/p>\n
Debug the problem as per the log message and do another tpa start and check the pdestate if it started running.<\/p>\n
tail \/var\/log\/messages<\/pre>\n
You will get a below error in the end.<\/p>\n
#PdeMain NOT started, PANIC-LOOP-DETECTED.<\/p>\n
Please delete file “\/var\/opt\/teradata\/tdtemp\/PanicLoopDetected<\/span>“, after resolving the panic issue.<\/p>\n
Remove the file PanicLoopDetected using below command:<\/p>\n
Now start the teradata database again using:<\/p>\n
service tpa start or \/etc\/init.d\/tpa start<\/pre>\n
#pdestate -a\r\nPDE state is RUN\/STARTED.\r\nDBS state is 5: Logons are enabled - The system is quiescent<\/pre>\n
<\/p>\n
The issue will be resolve hopefully.<\/p>\n
You can also check the storage using :<\/p>\n
#verify_pdisks<\/pre>\n
You will get message something like.<\/p>\n
Unable to open TVSA file \/etc\/opt\/teradata\/tdconfig\/tvsa_data<\/span> for reading. \nError getting TVSA system-id from \/tvsa_data file. But will continue to verify Pdisks.<\/p>\n
All pdisks on this node verified.<\/p>\n
If all the nodes on the system are not getting verified then troubleshoot the problem as per the error message generated after verifying pdisks.<\/p>\n
<\/p>\n
The various start up level of pdestate you can see after submitting the pdestate -a commands are:<\/p>\n
1) #pdestate -a<\/code> \nPDE state is START\/RECONCILE.<\/em><\/p>\n
2) #pdestate -a<\/code> \nPDE state is START\/STARTTPA.<\/em><\/p>\n
3) #pdestate -a<\/code> \nPDE state is RUN\/STARTED.<\/em> \nDBS state is 1\/5: DBS Startup – Voting for Transaction Recovery<\/em><\/p>\n
4) #pdestate -a<\/code> \nPDE state is RUN\/STARTED.<\/em> \nDBS state is 1\/4: DBS Startup – Starting PE Partitions<\/em><\/p>\n
5) #pdestate -a<\/code> \nPDE state is RUN\/STARTED.<\/em> \nDBS state is 5: Logons are enabled – The system is quiescent<\/em><\/p>\n
<\/p>\n
Tracking Restarts<\/span><\/h3>\n
To check the restart that have occurred in the past:<\/p>\n
\n
“tpatrace” command can be used to see information about restarts. For example “#tpatrace 5<\/code>” show last 5 restart information.<\/li>\n
\u00a0DBC.Software_Event_LogV view can be used to view past restarts.<\/li>\n<\/ol>\n\n