Before starting the teradata database you need to check the status of the PDE state.
This can be done by using below command:
# pdestate -a
1) If the teradata is already in ruuning state the the following message will be displayed:
2) If the teradata in not in running state than either of the following messages will be dispayed:
a) PDE state is STOP/KILLTASKS
b)PDE state is DOWN/HARDSTOP
Teradata database can be hardstopped using:
# tpareset -x {comments } --- comments show the reason to bring down the database later if someone needs to know the cause for database down.
Now check if the database if down or still running.
# pdestate -a
PDE state is STOP/KILLTASKS
For restarting the Teradata Database you have to run the following commands:
# /etc/init.d/tpa start
OR
# service tpa start
This show the below display:
To bring back the teradata database after doing HARDSTOP using the below command:
# tpareset -f
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:
Debug the problem as per the log message and do another tpa start and check the pdestate if it started running.
tail /var/log/messages
You will get a below error in the end.
DEGRADED: TdatTools: 29003 #PdeMain NOT started, PANIC-LOOP-DETECTED. Please delete file "/var/opt/teradata/tdtemp/PanicLoopDetected", after resolving the panic issue.
Remove the file PanicLoopDetected using below command:
rm /var/opt/teradata/tdtemp/PanicLoopDetected
Now start the teradata database again using:
service tpa start or /etc/init.d/tpa start
pdestate -a
PDE state is RUN/STARTED.
DBS state is 5: Logons are enabled - The system is quiescent
The issue will be resolve hopefully.
You can also check the storage using :
You will get message something like.
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.
If all the nodes on the system are not getting verified den debug the problem as per the error message generated after verifying pdisks.
The various start up level of pdestate you can see after submitting the pdestate -a commands are:
1) # pdestate -a
PDE state is START/RECONCILE.
This can be done by using below command:
# pdestate -a
1) If the teradata is already in ruuning state the the following message will be displayed:
PDE state is RUN/STARTED.
DBS
state is 5: Logons are enabled - The system is quiescent2) If the teradata in not in running state than either of the following messages will be dispayed:
a) PDE state is STOP/KILLTASKS
b)PDE state is DOWN/HARDSTOP
Teradata database can be hardstopped using:
# tpareset -x {comments } --- comments show the reason to bring down the database later if someone needs to know the cause for database down.
You are about to shutdown
the database
on the system
's10-1310'
Do
you wish to continue (default:
n) [y,n] yNow check if the database if down or still running.
# pdestate -a
PDE state is STOP/KILLTASKS
For restarting the Teradata Database you have to run the following commands:
# /etc/init.d/tpa start
OR
# service tpa start
This show the below display:
Teradata Database Initiator
service is starting...
Teradata
Database Initiator service started successfully.To bring back the teradata database after doing HARDSTOP using the below command:
# tpareset -f
You are about to restart
the database
on the system
's10-1310'
Do
you wish to continue (default:
n) [y,n] yIf still the pdestate is like DOWN/HARD/KILLTASK than you can troubleshoot the problem by checking the log file by using the following command:
Debug the problem as per the log message and do another tpa start and check the pdestate if it started running.
tail /var/log/messages
You will get a below error in the end.
DEGRADED: TdatTools: 29003 #PdeMain NOT started, PANIC-LOOP-DETECTED. Please delete file "/var/opt/teradata/tdtemp/PanicLoopDetected", after resolving the panic issue.
Remove the file PanicLoopDetected using below command:
rm /var/opt/teradata/tdtemp/PanicLoopDetected
Now start the teradata database again using:
service tpa start or /etc/init.d/tpa start
pdestate -a
PDE state is RUN/STARTED.
DBS state is 5: Logons are enabled - The system is quiescent
The issue will be resolve hopefully.
You can also check the storage using :
# verify_pdisks
You will get message something like.
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.
The various start up level of pdestate you can see after submitting the pdestate -a commands are:
1) # pdestate -a
PDE state is START/RECONCILE.
2) # pdestate -a
PDE
state is START/STARTTPA.
3) # pdestate -a
PDE state is RUN/STARTED.
DBS
state is 1/5: DBS Startup - Voting for Transaction Recovery
4) # pdestate -a
5) # pdestate -a
Please let me know if it is helpful to you or if you are facing any difficulty.
PDE state is RUN/STARTED.
DBS
state is 1/4: DBS Startup - Starting PE Partitions5) # pdestate -a
PDE state is RUN/STARTED.
DBS
state is 5: Logons are enabled - The system is quiescentPlease let me know if it is helpful to you or if you are facing any difficulty.