Stopping or Terminating Teradata Database Instances

For BYOL, you must revoke the licenses before you terminate a Teradata Database instance. To revoke licenses that have been activated on a system, run tdc-revoke prior to terminating a Teradata Database instance.

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 deploying 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.

To stop or terminate instances, you must first shut down 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 Software for AWS.
  4. If you are stopping an orphaned Teradata Database node 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.
    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.

results matching ""

    No results matching ""