We are pleased to announce the release of Teradata Multi-System Manager (TMSM) release 13.11 on September 28, 2011.    This release allows TMSM to integrate with our newest product in the Dual Systems / Analytical Ecosystem family – Teradata Unity.   TMSM was also enhanced to provide additional table validation options and support for other client platforms.   Additionally, we have added integration with the Common Alerting Mechanism (CAM) / Teradata Alerts that was released with Viewpoint.

The above diagram shows several of the Teradata TMSM portlets and integration with Teradata Unity

What is Teradata Multi-System Manager?

TMSM provides a powerful solution for monitoring, administration, and control of single and multiple Teradata data warehouse environments (ecosystems)

  • Key Features
    • Provides the user with a unified view of their data warehouse environment
    • Monitors Teradata systems, supporting servers, processes, and applications
    • Simple point-and-click controls to manage state of system-wide resources and query routing
    • Monitors load jobs and data synchronization status
    • Provides the ability to group processes together and track dependent processes
    • Monitors thresholds and reports of discrepancies
    • Enables user routing based on application readiness (data currency/process completion)
    • Supports graceful failover and failback during Planned and Unplanned Outages
    • Integrated with Teradata Viewpoint, Teradata Unity, Teradata Data Mover, Teradata Query Director

Details of the TMSM 13.11 release:

Enhanced Integration with other Teradata products and features

Support and integration with Teradata Unity

  • During configuration, Teradata Unity auto-registers itself with TMSM
  • TMSM Portlet enhancements provide visual indication of which applications/processes flow through Unity
  • Updated TMSM portlets for Unity:
    •  Application Health, Table Health, Log View and Component Monitoring.   


TMSM Component Health Portlet

Table Health Portlet shows table status across TD systems, including if the table is managed by Unit

TMSM Internal Repository upgraded to Teradata 13.10

The TMSM repository, which is an internal instance of the Teradata database, has been upgraded from Teradata 12 to Teradata 13.10

 Integration with the Common Alerting Mechanism (CAM) / Teradata Alerting

Consolidates alert and user definitions, users no longer need to define in two applications  (Viewpoint and TMSM) when setting up alerts

  • Simplifies alert administration by providing a single location for configuration, instead of requiring definitions in two locations
  • All external communication definitions are consolidated, such as who receives an email on a certain alert or what SNMP traps are issued. 

Enhanced Usability – convenience and productivity features

New TMSM client packages for the following platforms.  These packages are installed on servers in the Teradata Analytical Ecosystem allowing TMSM to monitor hardware condition and processes on that server.   TMSM supports the following platforms:

  • RedHat   4.1, EL 6
  • SUSE     10, 11 and higher
  • Solaris   9 and 10 (SPARC, Opteron)
  • Windows   7, XP, Windows 2003 server
  • Windows Server 2008
  • AIX   5.1, 6.0, 6.1
  • MVS z/OS V1R8.0-V1R9.0
  • HP-UX 11iv3

Additional options for table validation

  • Provides easier configuration when selecting several tables for data validation and specifying certain columns.  i.e. – validate the first n-number of columns for the tables selected
  • Support for Where clause in Table validation to specify a subset of rows to validate.
  • Added the ability to assign table validation configuration and validation triggers to multiple tables at once.
  • Added the ability of using a WHERE clause in the table validation to enable partial table validations.
  • Partial validations can use TMSM tokens that are dynamically replaced at validation time to provide automatically changing conditions, i.e. WHERE LastUpdateTS > ‘[UOW_FROMTS]’
  • The following tokens are provided:

[DB] - database name that is being validated
[TBL] - table name that is being validated
[TDP_ID] - TDPID of the system on which table validation SQL will run.
[UOW_ID] - UOWId associated to the validation.
[UOW_TS] - the Unit of Work timestamp.
[UOW_FROMTS] - the Unit of Work from timestamp (if none was specified for the UOW, it will be equal to UOW_TS).
[UOW_DATE] - the date part of the Unit of Work timestamp
[UOW_CLASS] - Unit of Work class (if none was specified for the UOW it defaults to the ResourceId of the process that created it).

  • The following only apply to table validations triggered by a process event and will be replaced with a zero length string if validation was triggered by a fixed schedule.

[RES_ID] - ResourceId of the process that triggered the table validation
[RES_TYPE] - ResourceType of the process that triggered the table validation
[EVENT_TYPE] - Event type of the event that triggered the validation

 Want more information?  

Access the following documents from the Teradata Publications Website: 

     Multi-System Manager 13.10 publications

Product ID

Teradata Multi-System Manager User Guide


Teradata Multi-System Manager Installation Guide


Teradata Multi-System Manager Configuration Guide


Teradata Multi System Manager API Specification



geethareddy 145 comments Joined 10/11
14 May 2013

We are upgrading the TMS (VP,TMSM,Unity,DataMover) to new version. So far we haven't open the other system (site in another state) in Dual Active Environment. 
I would like to know the process for configuring the TMSM and Unity porlets in Viewpoint. Is that mentioned anywhere in the manuals/documents?


You must sign in to leave a comment.