- You must be granted the following permissions by your IAM administrator:
- ec2:DescribePlacementGroup: Allows you to see if a placement group exists and to get information about it.
- ec2:DeletePlacementGroup: Allows you to roll back if an issue occurs.
- ec2:CreatePlacementGroup: Allows you to create a placement group to migrate new instances.
- [BYOL only] You must have a valid, active license with sufficient TCore for a scaled up system.
You can migrate placement groups as an alternative to scaling instances up or down manually if you do not want to stop the instances.
- [BYOL only] Revoke the license.
-
Stop the database on a single instance in the system.
# tpareset -x stop system -
Verify the database is stopped.
# psh pdestate -w
PDE state: DOWN/HARDSTOP -
Start the placement group migration.
# tdc-migrate-placement-group --instance_type <desired instance type>where the desired instance type is m4.4xlarge, m4.10xlarge, or m4.16xlarge. The old system remains running. The original instance names have -migrated appended to them. - SSH into the system to verify the new instances are working as expected. After verifying the new system, you can stop or terminate the old instances.
-
[BYOL only] Reactivate the license.
-
Run the activate command.
sudo su - eval "$(grep "tdc-telm -m activate" /var/lib/cloud/instance/scripts/part-001)"
-
Run tdlem-util -r on all nodes in the system:
Option Command Run on one node to affect all nodes sudo su - pcl -s tdlem-util -r
Run separately on each node sudo su - tdlem-util -r
- Log into the Teradata EMS server at https://slem.teradata.com/ecp and verify the quantity of available TCores decreased by the number of activated TCores.
-
If the database shuts down between revoking and activating the license, restart the database.
sh /etc/init.d/tpa start
-
Run the activate command.