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.

Activated licenses are automatically revoked if a licensing failure occurs. If activated licenses did not get revoked, you can revoke them manually. See Revoking Licenses for BYOL. After revoking the licenses from the instances, you can delete the AWS CloudFormation Stack. See Deleting an AWS CloudFormation Stack.

Following are examples of errors and possible remedies:
Errors Remedies
Couldn't login to the ems server Make sure port 443 is open to the Teradata EMS server (https://slem.teradata.com/ems) and verify your system can access the port. See Security Groups for Teradata Database.
License doesn't have requested tier or term Make sure the term you selected when you launched matches the email confirmation. See Bring Your Own License.

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 See Accessing AWS CloudWatch Logs. Look for the log group: /aws/lambda/stack-name-DBCheckLicenseFunction
Not all nodes activated successfully Contact Teradata Customer Support.

results matching ""

    No results matching ""