Resolved issues track corrections and updates to Teradata Tools and Utilities software and to documentation affected by the updates.
| Issue | Description |
|---|---|
| Teradata Access Module for S3 | |
| There are no issues for this module for this release. | |
| Teradata Access Module for Azure Blob | |
| There are no issues for this module for this release. | |
| Teradata Access Module for Google Cloud Storage | |
| There are no issues for this module for this release. | |
| Teradata Access Module for JMS | |
| There are no issues for this module for this release. | |
| Teradata Access Module for Kafka | |
| SA-52940 | The Teradata Kafka Access Module doesn't throw '!ERROR! dlopen failed: libsasl2.so.2: cannot open shared object file: No such file or directory' error. |
| Teradata Access Module for Named Pipes | |
| There are no issues for this module for this release. | |
| Teradata Access Module for OLE DB | |
| SA-52067 | The Teradata OLEDB Access Module does not drop the leading zero in the fraction part while mapping SQLServer TIMESTAMP(3) datatype to Teradata TIME(3) datatype. |
| SA-53167 | The Append checkbox is available in the "Save As" window to append multiple OLEDB Access Module jobs to an OLEDB Access Module .amj file. |
| Teradata Access Module for WebSphere MQ | |
| There are no issues for this module for this release. | |