Migrating from prior versions

You can migrate to IBM® InfoSphere® Master Data Management Collaboration Server Version 11.4 from specific prior versions.

The following migration paths are supported for Version 11.4:
  • Migrating from V9.0 Fix Pack 8 to V11.4
  • Migrating from V9.1, Fix Pack 2 or later to V11.4
  • Migrating from V10.0 Fix Pack 1 or later to V11.4
  • Migrating from V10.1, GA and all Fix Pack levels to V11.4
  • Migrating from V11.0, GA and all Fix Pack levels to V11.4
  • Migrating from V11.3, GA to V11.4

If you are migrating to a higher release, not a fix pack of the same release, you must use a new installation directory to avoid JAR file version mismatches.

It is a good practice to delete old InfoSphere MDM Collaboration Server data before migrating to avoid running out of log space. You must have a $TOP/logs directory before running any migration scripts.

If you are migrating from an older fix pack version, ensure that you are not using any deleted APIs in your Excel scripts. The following APIs are not available in the latest POI JAR file:
  • public String getExcelCellEncoding();
  • public void setEncoding(String encoding);
  • public String getExcelCellEncoding(Object cellObj) throws AustinException;
Note:
  1. The InfoSphere MDM Collaboration Server Excel Parser is supported through a third-party .jar file named poi-3.7-20101029.jar. This library supports Microsoft Excel 2007 format, which allows more than 255 columns per data sheet. You must run the Rich Search Result Report script. When you run this script, use the Default Rich Search Results Report Script (Excel 2007 - xlsx format) option to export items with more than 255 attributes.
  2. You can export Rich Search Results to files in the Excel 2003 format by using the Default Rich Search Results Report Script option. However, with this format, the report fails if items have more than 255 attributes.
  3. Excel 2010 .xlsx is not supported by this JAR.
Important: Before you run the migration scripts, you must ensure that you are using the correct database version. See the system requirements for details: http://www-01.ibm.com/support/docview.wss?uid=swg27035486. You must also ensure that the InfoSphere MDM Collaboration Server database user has appropriate privileges as mentioned in the installation guide. Consult with your DBA team for any changes in database user privileges because of any security policy.
You must use the DB2® or Oracle database version as mentioned in the system requirements. See the system requirements for details: http://www-01.ibm.com/support/docview.wss?uid=swg27035486. You can refer to the DB2 or Oracle documentation for upgrading your DB2 and Oracle database to the supported version.

Steps for migrating collaborative MDM with custom table spaces are used in DB2 and Oracle

If you are using custom table space names instead of the default USERS or INDX, you must manually modify the table space names in the following SQL files before you start the migration to InfoSphere MDM Collaboration Server.

You must verify that you have at least 30% free space in the database before you start the migration.

Audit logs are not migrated to V11.4. Because of a new format of audit log descriptions that were introduced in V9.1.0, the audit log descriptions present in releases before V9.1.0 are not viewable in V11.4. Hence they are deleted from the database during migration. The old audit logs can be viewed by using the release from which you are migrating.

You must manually perform the following steps to ensure successful migration:
  1. Manually migrate the following property files. Because property files are part of the local file systems, the migration method does not support exporting property files. Modify each customized property from previous releases to the corresponding file in the new version. Do not overwrite the property files from an older version to a new version because new parameters are introduced in V11.4. Refer to the InfoSphere MDM Collaboration Server documentation for details on each property file.
    • $TOP/etc/default/common.properties
    • $TOP/etc/default/logs.xml
    • $TOP/etc/default/docstore_mount.xml
    • $TOP/etc/default/user_jars.list
  2. Manually copy the contents of the $TOP/public_html/suppliers/<cmp code>/ctg_files directory to the new instance for each company. Because these files are part of the local file system, the migration method does not support exporting the ctg_files directory.
  3. Manually add the required user JAR files to the new instance. Because these files are part of the local file system, the migration method does not support exporting user JAR files. For more information about adding JAR files to your deployment, see Deploying a custom user .jar file.
  4. Manually redo any changes that you had made to the Default Rich Search Results Report Script to customize it. Migrating to InfoSphere MDM Collaboration Server V11.4 overwrites the existing script available in the InfoSphere MDM Collaboration Server docstore directory, /scripts/report. This script is used for exporting InfoSphere MDM Collaboration Server object search results to an Excel sheet. For more information about this script, see Exporting search results to Excel.
  5. Ensure that there is no verbose compilation option that is set for compiling scripts. Verify that in the common.properties file you do not use verbose as the value for the script_compiler_options parameter. For more information about this parameter, see script_compiler_options parameters.
  6. Run the setup.sh script to check if the version of PERL installed on your computer is compatible with the version of InfoSphere MDM Collaboration Server that you have installed. This script is in the $TOP directory. If the current version of PERL is not compatible, you must install a new version.
  7. If you install the new version of InfoSphere MDM Collaboration Server in a new directory, you must update the value of TOP and PERL5LIB variables in the .bash_profile file. You must set the PERL5LIB variable to $TOP/bin/perllib directory.

Last updated: 22 Jul 2017