Database server requirements

The database server houses the MainView Middleware Monitor (MVMM) database, which stores history data and configuration data.

The MVMM 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 MVMM installation and to the database server.

MVMMservices 64-bit applications on both Linux and Windows. A 64-bit database client must be available for Windows or Linux servers running MVMM.





10.5, 11.1, 11.5

For Linux and Windows.

Note that the DB2 database needs to have a user temporary tablespace with a page size of 16K or greater. See Required roles and permissions for installation for more information.


11.2, 12.1, 12.2, 18, 19

For Linux and Windows.

Microsoft SQL Server

2012, 2014, 2016

The MVMM services must be on Windows.

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

Microsoft SQL Server2017, 2019

For Linux and Windows.

Windows: Using SQL Server Client Driver (ODBC), set the Default Database to the MVMM database when creating the ODBC DSN. You need to define a 64-bit ODBC connection. For more details, see Microsoft SQL Server specific concepts.

Linux: Using Microsoft ODBC Driver 17 for SQL Server for Linux (Download ODBC Driver for SQL Server, Installing the Microsoft ODBC Driver for SQL Server on Linux and macOS), install the 64-bit ODBC driver and configure an ODBC DSN pointing to the MVMM database. For more details, see Creating and initializing a Microsoft SQL Server database.

Contact BMC Support for assistance with:

  • Sizing help if you are considering running the database server on the same computer as the other MVMM 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 MVMM 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 the Shared or dedicated database server section.

Database connection requirements

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

When you use MVMM to store history data, the database collects data continually and any outage might result in the loss of data. For this reason, MVMM 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, MVMM 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 MVMM database on a separate server or on the same server as the MVMM 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 the Database performance section 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