| # | Date | Forum | Type | Thread | Post |
|---|---|---|---|---|---|
| 6 | 09 Aug 2016 @ 05:06 PDT | Teradata Database on AWS | Reply | pkg_resources.DistributionNotFound: td-aws-ins-config==1.0.0 | Address this issue by downgrading to python 2.6. If someone find solution for running tdc-init on Python 2.7, would appreciate your comment. |
| 5 | 08 Aug 2016 @ 05:11 PDT | Teradata Database on AWS | Reply | AWS instance unreachable for Teradata Database Developer (Single Node) | Thank you for fixing this bug. The AMI of 08/05/2016 deploys fine now. |
| 4 | 05 Aug 2016 @ 05:33 PDT | Teradata Database on AWS | Reply | pkg_resources.DistributionNotFound: td-aws-ins-config==1.0.0 | I do not need to use exactly tdc-init and tdc-start, maybe there is other tools and scripts to init, reinit and start Teradata DB (f.i. vprocmanager and tpa). If so kindly ask you... |
| 3 | 05 Aug 2016 @ 01:45 PDT | Teradata Database on AWS | Reply | pkg_resources.DistributionNotFound: td-aws-ins-config==1.0.0 | mc200018, thank you for your reply! But all my links are in proper state. They link to python2.7. There are either no python 2.6 or links to python 2.6 in the system: ... |
| 2 | 04 Aug 2016 @ 06:21 PDT | Teradata Database on AWS | Topic | pkg_resources.DistributionNotFound: td-aws-ins-config==1.0.0 | After upgrade python from 2.6 to 2.7 on Teradata Database Developer (Single Node) AMI could not execute tdc-init, tdc-start: td-aws-ins-config is missing. Is there any chance to download it separa... |
| 1 | 23 Jul 2016 @ 03:36 PDT | Teradata Database on AWS | Reply | AWS instance unreachable for Teradata Database Developer (Single Node) | The same issue for me. Any Teradata ami's at AWS could not pass checks after launching. It goes on for 9 days. Instances that had been launched before 9 days ago are working fine. Please... |