Migrating to IBM Product Master Version 14.0

To migrate to IBM® Product Master Version 14.0, you must run the appropriate migration script.

Before you begin

Ensure that you complete the following steps.

You have adequate permissions to,
- Create and modify tables and indexes in the database,
- Create and delete files in the sub directories of the $TOP directory.
You have at least 30% available space in the database.
You have deleted old Product Master data before you migrate to avoid running out of log space.
You have a $TOP/logs directory.
You have the appropriate Db2® or Oracle database Version as mentioned in the system requirements. For more information, see System requirements - Db2 databases and System requirements - Oracle databases.
For upgrading your Db2 and Oracle database to the supported Version, see the Db2 or Oracle documentation.
You have ensured that the Product Master database user has appropriate privileges. Consult with your database Administrator team for any changes in database user privileges because of any security policy.
While migrating to a higher release, and not a fix pack of the same release, you must use a new installation directory to avoid JAR file Version mismatches.

About this task

Following are the possible migration scenarios.

Migration scenarios	What to do?
A fresh installation for the IBM Product Master Version 14.0 release.	Install by using the appropriate full build.
Migrating from the IBM Product Master Version 12.0 release to the IBM Product Master Version 14.0 release.	Run the appropriate migration script. For more information, see Product Master instance and migration script mapping table. After migration, you must run the resetPassword.sh script if your IBM Product Master Version is earlier than 12.0 Fix Pack 3.
Migrating from the InfoSphere® Master Data Management Collaboration Server - Collaborative Edition 11.6 release to the IBM Product Master Version 14.0 release.	Run the appropriate migration script. For more information, see Product Master instance and migration script mapping table. After migration, you must run the resetPassword.sh script when migrating from InfoSphere Master Data Management Collaboration Server - Collaborative Edition 11.6 release (and fix packs).

Procedure

Stop the running Product Master instance.
Back up the existing database schema.
Install Product Master Version 14.0 into a different folder.
Point the Product Master Version 14.0 instance to the database schema of an existing instance, by adding the database parameters in the env_settings.ini file. For more information, see Setting the common database parameters.

Run the appropriate migration script at $TOP/bin/migration folder. If the migration was not successful, you can run the migration script again. See Results for the migration summary.

Table 1. Product Master instance and migration script mapping
Product Master instance	Migration script
Version 12.0	`migrateFrom1200FP --fromversion` Example `./migrateFrom1200FP.sh --fromversion=BASE` `./migrateFrom1200FP.sh --fromversion=FP8`
Version 11.6	`migrateFrom1160FP` Example `./migrateFrom1160FP.sh`

Run the test_db.sh script to verify the database schema, connectivity between Product Master and databases, and to check for JDBC and native client connections. For more information, see test_db.sh script.
Start the IBM Product Master Version 14.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, the message that is displayed in the console indicates whether the migration was successful.

Successful migration message

-----------------------------------------------------------
Summary of the migration
-----------------------------------------------------------
Migration to IBM Product Master 14.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/ipm.log

Migration failed message

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

Migration of specific modules failed message

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

Discrepancy in the database tables or indexes message

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/ipm.log

What to do next

For more messages, either review the errfile.log file or the log file mentioned in the migration failed message.
For SQL errors, find the detailed error message from the SQL error code, correct the error, and run the migration script again.
Contact IBM Software Support if the problem persists after you rectify the errors.