Stopping or Terminating Teradata Database Instances
tdc-revokeprior to terminating a Teradata Database instance. See Revoking Licenses for BYOL.
To avoid triggering a node failure, stop or terminate instances before shutting down the database. When a node failure occurs on a single-node system, AWS starts up a replacement automatically unless there are issues with the operating system or in the database itself. To handle these situations, Teradata recommends launching a new Teradata Database MPP system instance. Even if a node does not go down due to a failure, an instance still starts up after you stop or terminate an instance. Stopping instances does not delete attached EBS volumes, but terminating instances detaches and deletes the EBS volumes. Node failures are handled differently on local storage instance types. See Node Failure Recovery.
To stop or terminate instances, you must first shut down the database.
- Stop the database.
# tpareset -x stop systemPutting the database in this state takes a few minutes.
- Wait for the database to shut down.
# psh pdestate -wPDE state: DOWN/HARDSTOP
- From the AWS EC2 Console, terminate or stop the instances associated with the Teradata Database on AWS.
- If you are stopping an orphaned Teradata Database node in response to a node failure, do one of the following:
Orphaned means when a failed node is recovered, but the recovery is too late for the node to rejoin the configuration and so the node is replaced. The node is online, but is no longer part of the system configuration.
- From the AWS EC2 Console, terminate or stop the instances.
- From the command prompt, type
psh init 0to shut down the system.