Troubleshooting the MDM database

One of the major components of an InfoSphere® MDM implementation is the database. Problems can occur during installation or configuration of the MDM database that require investigation and correction.

InfoSphere MDM supports the following database platforms:

  • Oracle Database
  • IBM® DB2®
  • IBM DB2 for z/OS® (partial installation support, for the application server component only)
  • Microsoft SQL Server (supported by InfoSphere MDM Standard Edition only)

From InfoSphere MDM Version 11.0 onwards, there is a combined schema for Standard Edition (virtual MDM) and Advanced Edition (physical MDM). The combined InfoSphere MDM database installation creates 953 tables. There are 153 tables to support virtual MDM and the remaining tables support physical MDM. Optionally, the installation also creates a set of database triggers. These triggers are used in Advanced Edition deployments.

The MDM database has the following configuration restrictions:

  • Changing the number of tablespaces for DB2 and Oracle database are not supported.
  • Using different schemas for physical MDM data and virtual MDM data is not supported.

Database creation scripts

All of the InfoSphere MDM Advanced Edition database scripts (for all database platforms) are located in the <MDM_INSTALL_HOME>/database folder, grouped as either Core or Full.

  • The Core subfolder contains only scripts required for the core physical MDM data.
  • The Full subfolder contains all of the scripts required for core physical MDM and all of the MDM domain data.

Database creation logs

All of the InfoSphere MDM database object creation logs are available in the folder <MDM_INSTALL_HOME>/logs/database.

  • /CMData stores logs that correspond to physical MDM configuration and management object creation.
  • /CoreData stores logs that correspond to physical MDM core data.
  • /DomainData stores logs that correspond to physical MDM domain data. The physical MDM domains manage information related to parties, products, and accounts.
  • /RDMScripts stores logs that correspond to InfoSphere MDM Reference Data Management Hub.
  • /Virtual stores logs that correspond to virtual MDM data.
Note: Depending on the details of your installation, you may not have all of the subfolders shown here.

If you encounter any problems when creating the database, look for corresponding .err files in the subfolders of <MDM_INSTALL_HOME>/logs/database.

If your implementation of InfoSphere MDM uses the WebSphere® Application Server default messaging engine, then there will be extra SIB tables. These SIB tables are created by WebSphere Application Server when the server that hosts InfoSphere MDM is started. If you are using same schema multiple times because of previous failed installations, remember to remove these tables after every installation.

If your installation encounters errors when creating virtual MDM tables, look in the folder <MDM_INSTALL_HOME>/logs/database/Virtual. If the installation has not rolled itself back after a failure, then look for log files at the location <MDM_INSTALL_HOME>/mds/log to find information about why the rollback did not occur.

To recreate the virtual MDM database tables, try running the virtual MDM madconfig target. To run the madconfig target:
  1. Open a command-line prompt from the <MDM_INSTALL_HOME>/mds/scripts folder.
  2. Run the virtual MDM madconfig target:
    ./madconfig.sh bootstrap_datasource

Last updated: 8 Mar 2019