Teradata Multi-System Manager is an application for monitoring and administration of single and multi-system environments. TMSM Report Viewer allows TMSM (Teradata Multi-System Manager) users to create and view reports about the Teradata ecosystem using data collected by TMSM. The TMSM data model is in Appendix E of the Configuration Guide.  For more information about TMSM, please read this article.

This article provides information about TMSM reporting capabilities, shows how to create custom reports, and reviews the out-of-the-box reports provided.

The Teradata Named Pipe Access Module (NPAM) provides an inter-process communication link between a writer process (such as FastExport) and a reader process (such as FastLoad).

Teradata Unity 13.10, the latest enabling technology of the Teradata Analytical Ecosystem was formally announced at PARTNERS Conference 2011.  The product’s focus is to simplify the analytical ecosystem by removing the everyday complexities involved in query management and data synchronization across multiple Teradata systems.  Teradata Unity delivers on this strategy by way of product automation.

The Unicode™ standard defines five encodings (the first three encodings are currently supported by Teradata):

The Teradata RDBMS can return a variety of errors. Some of these errors are retryable (that is, the request can be resubmitted); the simplest example of this is a 2631 (Transaction aborted due to %VSTR) caused by a deadlock condition. Other errors are not retryable; data-related errors (constraint violations, etc.) are an example.

For certain retryable error codes, BTEQ will, by default, retry the failing request. The user can disable such retries via the SET RETRY command. For example, if a 2631 occurs, and retries have not been disabled, BTEQ will resubmit the request.