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.

Following are examples of errors and possible remedies:
Couldn't login to the ems serverMake 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 termMake 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 availableIf additional TCores are needed, contact your Teradata Account Team.
DBValidateLicenseIn AWS CloudWatch logs, look for the log group: /aws/lambda/stack-name-DBCheckLicenseFunction
Not all nodes activated successfullyContact Teradata Customer Support.

results matching ""

    No results matching ""