Licensing errors may occur when scaling out or scaling in a system. Nodes and the associated licenses are automatically removed from the system so new nodes and new licenses can be assigned. During this process, Teradata strongly suggests you monitor the AWS CloudWatch logs. In AWS CloudWatch logs, look for log group Teradata/DBS/stack-name and log stream telm_stack-name . Teradata Database automatically fixes most issues and activates the new licenses. There may be a delay during this process.
Following are examples of errors and possible remedies:
| Errors | Remedies |
|---|---|
| An error occurred revoking the license | The Teradata EMS server attempts to automatically revoke the license. There may be a delay of up to 1 hour in response. If the AWS CloudWatch logs indicate a revocation was attempted twice, then revoke the license manually using tdc-revoke. |
| Error: No nodes were revoked | Make sure port 443 is open to https://slem.teradata.com so Teradata can verify BYOL entitlement, and verify your system can access the port. The instance will attempt to reactivate itself periodically. If you are still having issues, contact Teradata Customer Support. |
| An error occurred removing the license files | Revoke the license manually using tdc-revoke. |
| Unable to activate licensing for node: nodename | Make sure port 443 is open to https://slem.teradata.com so Teradata can verify BYOL entitlement, and verify your system can access the port. The instance will attempt to reactivate itself periodically. If you are still having issues, contact Teradata Customer Support. |