Licensing Issues During or After Deployment
If you receive licensing errors during or after deployment, access the AWS CloudWatch logs (look for log group Teradata/DBS/stack-name and log stream telm_stack-name).
If a problem occurs during deployment, the stack is rolled back and activated licenses are automatically revoked.
During deployment, activated licenses are automatically revoked if a failure occurs. If activated licenses did not get revoked, you can revoke them manually. After revoking the licenses from the instances, you can delete the AWS CloudFormation Stack.
|Couldn't login to the ems server||Make sure port 443 is open to the web-based Teradata EMS server and verify your system can access the port.|
|License doesn't have requested tier or term||Make sure the term you selected when you deployed matches the email confirmation.
The Teradata Database license tier is determined when you select the AMI.
|Not enough tcores available||If additional TCores are needed, contact your Teradata Account Team.|
|DBValidateLicense||In AWS CloudWatch logs, look for the log group: /aws/lambda/stack-name-DBCheckLicenseFunction|
|Not all nodes activated successfully||Contact Teradata Customer Support.|