Upgrading the existing database for Initiate Master Data Service

When you install the new version of InfoSphere® MDM, you must point to a new database. Do not provide the connection information for the existing database that you are upgrading.

About this task

The installation and upgrade process uses a temporary database for the new version of InfoSphere MDM, where it creates new, empty tables. Pointing to the existing database can create the risk that existing data will be overwritten.

After the installation is complete, stop the server and node in which you installed.

  1. Conducting the pre-upgrade tasks
    Before you upgrade the Initiate® database, there are a few tasks that you must complete.
  2. Upgrading the Initiate database
    After creating the initial runtime environment, you must upgrade the existing database. Before beginning, it is helpful to understand the upgrade process.
  3. DB2: Adding new InfoSphere MDM database objects to the upgraded Initiate database
    As part of setting up the database, you must add some database objects from your new InfoSphere MDM installation to the existing Initiate database. The steps that follow apply to systems that use DB2® databases.
  4. Oracle: Adding new InfoSphere MDM database objects to the upgraded Initiate database
    As part of setting up the database, you must add some database objects from your new InfoSphere MDM installation to the existing Initiate database. The steps that follow apply to systems that use Oracle databases.
  5. SQL Server: Adding new InfoSphere MDM database objects to the upgraded Initiate database
    As part of setting up the database, you must add some database objects from your new InfoSphere MDM installation to the existing Initiate database. The steps that follow apply to systems that use Microsoft SQL Server databases.
  6. Oracle: Updating the matching type in the configelement table
    As part of the process for updating the matching type, you must obtain the ID of the EBA file. The following steps explain the process as well as the process for updating the information in the configelement table. The steps that follow apply to systems that use Oracle databases.
Previous topic: Updating custom code for new security requirements
Next topic: Modifying server configuration and updating configuration tables

Last updated: 22 Apr 2016