Resizing an Instance

Prerequisite
Before starting, ask your IAM administrator to grant you the ec2:ModifyInstanceAttribute permission so you can resize an instance.
You should resize only supported instance types. See Amazon User Guide for Linux Instances.
Note
If you resize to unsupported instance types, database performance may be impacted. Data loss will occur if resizing local storage instance types.

You must stop an instance before you can change the instance type. Resizing has no affect on Teradata software that is running on an instance.

For BYOL, resizing an instance is not supported in the AWS public cloud.

  1. Stop the database on a single instance in the system.
    # tpareset -x stop system
    It may take a few minutes to put the database in this state.
  2. Wait for the database to shut down.
    # psh pdestate -w
    PDE state: DOWN/HARDSTOP
  3. Do one of the following to stop all instances at the same time.
    OptionActions
    Using the command lineOn a single instance in the system:
    1. # psh init 0
    Using the AWS EC2 Console
    1. In the navigation pane, click Running Instances.
    2. Select the check box next to all instances.
    3. Select Actions > Instance State > Stop.
    4. In the confirmation box, click Yes, Stop.

      It may take a few minutes for the instances to stop.

  4. From the AWS EC2 Console, select the check box next to all instances.
  5. Select Actions > Instance Settings > Change Instance Type.
  6. Select the EBS-optimized check box which enables EBS optimization.
  7. Click Apply.
  8. From the AWS EC2 Console, select the check box next to all instances.
  9. Select Actions > Instance State > Start.
  10. In the confirmation box, click Yes, Start.
    It may take a few minutes for the instances to start.
    If you did not change the default Teradata Database start behavior, all instances start and the Teradata Database returns to a running state.

results matching ""

    No results matching ""