Database server requirements

The database server houses the TrueSight Middleware and Transaction Monitor (TMTM) database, which stores history data and configuration data.

The TMTM database stores information about:

  • your SOA environment configuration
  • what you are monitoring
  • short-term and long-term history
  • audit information
  • history and event templates and rules
  • contacts
  • type and attribute definitions
  • journal data

Supported databases

Database clients must be appropriate to the TMTM installation and to the database server.

TMTM services are 64-bit applications on Windows and Linux (SLES, RHEL). Therefore, on a machine running TMTM services a 64-bit database client must be available.

For all supported database types, the clients and servers version level and fix pack numbers must match. Non-matching combinations might work, but are not supported by BMC.





10.1, 10.5, 11.1, 11.5

Supported by TMTM services running on either Linux or Windows.


11.2, 12.1, 12.2, 18 and 19

Supported by TMTM services running on either Linux or Windows.

Note that Oracle 12.2, 18, and 19 should use database type Oracle 12.1.

Microsoft SQL Server

2008 R2, 2012, 2014, 2016, 2017

The TMTM services must be on Windows.

Using SQL Native Client (SNAC/ODBC). Set the Default Database to the TMTM database when creating the ODBC DSN. On Windows you need to define a 64-bit ODBC connection. See Microsoft SQL Server specific concepts for more details.

Contact BMC Support for assistance with:

  • Sizing help if you are considering running the database server on the same computer as the other TMTM components.
  • The appropriate fix pack or patch set for your database.

Database performance

The database interacts with BMC services and must be available when the services are running.

Database performance is critical to product performance. Routine monitoring and capacity planning is a requirement. See Database performance recommendations.

The TMTM server must be in close physical proximity to the database server with a network latency of less than 5MS between them. A gigabit LAN is recommended. See also Shared or dedicated database server.

Database connection requirements

TMTM is designed with the expectation that the database is available 24x7.

When you use TMTM to store history data, the database collects data continually and any outage might result in the loss of data. For this reason, TMTM expects a continuous database connection.

The BMC services are designed to reconnect to the database if the database goes offline temporarily. If the database comes back online after an extended offline period, the application might automatically re-establish the connection but stability cannot be guaranteed.

In the event of a planned database outage, TMTM services should be in a stopped state while the database is unavailable. In the event of an unplanned database outage, services should be stopped and started once the database is made available again.

Database size

Some parts of the database could be considered a data warehouse with a live continual history data feed. It is not uncommon for the database to grow in size to many gigabytes with tables containing hundreds of millions of rows. 

Shared or dedicated database server

You can run the TMTM database on a separate server or on the same server as the TMTM services.

BMC recommends that you run your database and services on different servers. Consider using the same server only if you are working with a small configuration.

Refer to the caution under Database performance for information about latency.

If you select to run services on the same system as the database, set a dependency for each of the services to start after your database starts. Services cannot start before the database. If required, contact BMC Support for assistance in configuring this requirement.

Was this page helpful? Yes No Submitting... Thank you