Stopping or Terminating Teradata Database Instances

The node failure recovery process automatically starts up a replacement instance when a node goes down for Teradata Database single-node systems. Node failures are handled differently on local storage instance types. For more information, see Node Failure Recovery.

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. To terminate or stop instances, you must first stop the database.

  1. Stop the database.
    # tpareset -x stop system
    Putting the database in this state takes a few minutes.
  2. Wait for the database to shut down.
    # psh pdestate -w
    PDE state: DOWN/HARDSTOP
  3. From the AWS EC2 Console, terminate or stop the instances associated with the Teradata Database on AWS.
  4. If you are stopping Teradata Database in response to a node failure, do one of the following:
    • From the AWS EC2 Console, terminate or stop the instances.
    • From the command prompt, type psh init 0 to shut down the system.

results matching ""

    No results matching ""