IBM InfoSphere Master Data Management, Version 11.3

Migrating from V10.0.0 to V11.3.0

To migrate to IBM® InfoSphere® Master Data Management Collaboration Server Version 11.3.0 from IBM InfoSphere Master Data Management Server for Product Information Management Version 10.0.0, you must run the appropriate migration script.

Before you begin

Before you can migrate from InfoSphere MDM Collaboration Server V10.0.0 to V11.3.0, you must ensure that you are specifically using Fix Pack 1 or later for V10.0.0. If you are using V10.0.0 GA, you must migrate to V10.0.0 Fix Pack 1 or later following the instructions in the appropriate release notes.

You can configure the error log file location by modifying the _ERROR_LOGS variable in the migrateFrom1000.sh migration script. This variable is set to $TOP/logs/errfile.log by default.

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.

Table 1. SQL files to modify when you use custom table space names
SQL files to modify when DB2® is the back-end database	SQL files to modify when Oracle is the back-end database
Modify the table space names from USERS, INDX, and BLOB_TBL_DATA to appropriate custom table space names in the following SQL files in the $TOP/src/db/schema/dbscripts/db2 directory: addSstShared.sql addCaeStepEntryDate addObhCompanyId.sql	Modify the table space names from USERS, INDX, and BLOB_TBL_DATA to appropriate custom table space names in the following SQL files in the $TOP/src/db/schema/dbscripts/oracle directory: addSstShared.sql add_icm_index.sql add_lot_index.sql redefine_ctg_indexes.sql modifyIcm1Index.sql

About this task

The following steps are the only way to migrate from InfoSphere MDM Collaboration Server V10.0.0 to V11.3.0, and no other means. You cannot use the environment export and import tool.

Procedure

Back up the existing database schema.
Install InfoSphere MDM Collaboration Server V11.3.0 into a different directory.
Point the InfoSphere MDM Collaboration Server V11.3.0 instance to the V10.0.0, Fix Pack 1 or later database schema. To point the instance to the database, add the database parameters in the env_settings.ini file. For more information, see Setting the common database parameters.
Run the migrateFrom1000FP.sh migration script. This script is available in the $TOP/bin/migration directory. See the Results section for the migration summary. If the migration was not successful, you can run the migration script again.
Run the test_db.sh script to verify the database schema, the connectivity between InfoSphere MDM Collaboration Server and databases, and to check for JDBC and native client connections. For more information, see test_db.sh script.
Start the InfoSphere MDM Collaboration Server V11.3.0 instance.

Results

All messages, such as the status of individual migration components and the overall migration summary, are displayed in the console.

After you run the migration script, messages are displayed in the console that indicates whether the migration succeeded or failed.

This message is displayed if the migration succeeded:

-----------------------------------------------------------
Summary of the migration
-----------------------------------------------------------
Migration to IBM InfoSphere Master Data Management 
Collaboration Server Version 11.3.0 is complete. Check the
messages for any errors.

Generating database verification report...

___________________________________________________________

Changed tables

===========================================================
There are no changed tables 
___________________________________________________________


___________________________________________________________

Missing Tables

===========================================================
There are no missing tables
___________________________________________________________


___________________________________________________________

Changed Indexes

===========================================================
There are no changed indexes
___________________________________________________________


___________________________________________________________

Missing Indexes

===========================================================
There are no missing indexes
___________________________________________________________

LOG FILE: $TOP/logs/default/default.log

This message is displayed if the migration failed:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 Migration Failed :  xxxx
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 Please see the file for further details :  /home/pimuser/mdmcs11/logs/errfile.log

This message is displayed if the migration of specific modules failed:

-----------------------------------------------------------
Summary of the migration
-----------------------------------------------------------
Migration of the following modules failed :
<module names>

This message is displayed if there is a discrepancy in database tables or indexes.

Generating database verification report...

___________________________________________________________

Changed tables

===========================================================
<table names>
___________________________________________________________


___________________________________________________________

Missing Tables

===========================================================
<table names>
___________________________________________________________


___________________________________________________________

Changed Indexes

===========================================================
<index names>
___________________________________________________________


___________________________________________________________

Missing Indexes

===========================================================
<index names>
___________________________________________________________

LOG FILE: $TOP/logs/default/default.log

Review the errfile.log file for more messages. For SQL errors, find the detailed error message from the SQL error code, correct the error, and run the migration script again. For recommended action on migration failures, refer to Troubleshooting migration issues. Contact IBM Software Support if the problem persists after you rectify the errors.

Last updated: 1 Aug 2014