Database schema migration

If the fix pack needs database schema migration, complete the steps that are listed here.

Before you begin

Important:
  • Ensure that the database user for Product Master application has appropriate database privileges as mentioned DB2® privileges or Oracle privileges. If the database privileges are modified for any reason, the migration script fails.
  • Ensure that the Product Master application is stopped on the local server.
  • Identify the version of fix pack that you are migrating from.

Procedure

  1. Run the migrateToInstalledFP.sh in the $TOP/bin/migration directory.

    Fix Pack 3 later
    migrateToInstalledFP.sh --fromversion=BASE, FP1, FP2, FP3
    • fromversion - Depends on the version you are migrating from.
    Fix Pack 2 earlier
    migrateToInstalledFP.sh --fromversion=BASE, FP1, FP2 [--dbpassword=<database password>]
    • fromversion - Depends on the version you are migrating from.
    • dbpassword (Optional) - Stores the encrypted database password in the Product Master.
  2. Check the migration messages in the console to verify successful migration.
    Types of migration messages
    Message type Message
    Migration successful 
    --------------------------------------
 Summary of the migration:  
--------------------------------------
 Migration to IBM Product Master 12.0.0 successful.
    Migration failed 
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 Migration Failed :  xxxx
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 Please see the file for further details :
    /home/pimuser/mdmcs12/logs/errfile.log
    Migration failed for specific modules 
    --------------------------------------
 Summary of the migration:  
--------------------------------------
 Migration of the following modules failed : <module names>
    • Review the errfile.log file for more messages.
    • Review the $TOP/logs/migrateToInstalledFP.log file for more details.
    • For SQL errors, find the detailed error message from the SQL error code, correct the error, and run the migration script again.
    • For more information, see Troubleshooting migration issues.
    • Contact IBM Software Support if the problem persists after you correct the errors.