Upgrading an existing InfoSphere RDM database on DB2 for UNIX or Linux

Follow these steps to upgrade your InfoSphere® MDM Reference Data Management database on DB2® for UNIX or Linux® to version 11.6.

1. Navigate to the RDM_INSTALL_HOME/database/RDMDBScripts/Upgrade directory in your Version 11.6 installation.
2. Select the folder of the version that you want to upgrade to. For example, if you are running version 10.1, select the 11.0.0 folder because you must upgrade to version 11.0, and then from version 11.0 to version 11.3, before you can upgrade from version 11.3 to version 11.4, and then 11.4 to 11.5, and then from version 11.5 to 11.6.
3. Navigate to the RDM_INSTALL_HOME/database/RDMDBScripts/Upgrade/UpgradeVersion/Level-I/myDBMS/Standard/ddl directory
4. If you are running on UNIX, run the dos2unix command on all the scripts in the directory to ensure that the files are in UNIX format.
5. Connect to the RDM database that you want to upgrade using the same credentials and schema name that the RDM instance is using.
6. Roll back triggers and metadata for the RDM version you are running on.
   Refer to the ReadMe file README.txt for details.
   1. As necessary, in your SQL files, replace the SCHEMA placeholders or the db2admin schema with the schema name that is used in the database that you are upgrading.
   2. Run the scripts in the order that they are listed, where Version is the version whose triggers you are rolling back (such as 10.01 or 11.0) and log_file_name is the name of your log file.

      1. db2 –v –td@ -f Version_Rollback_RDM_TRIGGERS_DB2.sql 
         –l log_file_name

      2. db2 –tvf Version_Rollback_RDM_MetaData_DB2.sql 
         -l log_file_name

      3. db2 –tvf Version_Rollback_RDM_CODETABLEVALUE_DB2.sql
         -l log_file_name

7. Migrate your databases. Run these scripts in the order that they are listed, where VXX_TO_VXX is one of these migration sequences: V11.5.0_TO_V11.6.0_, V11.4.0_TO_V11.5.0_, V11.3.0_TO_V11.4.0_, V11.0.0_TO_V11.4.0_, V10.1.0_TO_V11.0.0_, or V10.0.0_TO_V10.1.0; and log_file_name is the name of your log file.
   Note: These scripts contain version-specific files. Files that are not required for a specific version do not display in the script for that version.
   1. db2 -tvf VXX_TO_VXX_RELEASE_MIGRATION_Create_RDM_Tables_DB2.sql -l log_file_name
   2. db2 -tvf VXX_TO_VXX_RELEASE_MIGRATION_Create_RDM_FK_Constraints_DB2.sql -l log_file_name
   3. db2 -v -td@ -f VXX_TO_VXX_RELEASE_MIGRATION_DDL_DB2.sql -l log_file_name
   4. db2 -tvf VXX_TO_VXX_RELEASE_MIGRATION_DML_DB2.sql -l log_file_name
   5. db2 -tvf VXX_TO_VXX_RELEASE_MIGRATION_Create_RDM_Index_DB2.sql -l log_file_name
8. Navigate to the RDM_INSTALL_HOME/database/RDMDBScripts/db2 directory in your Version 11.5 installation.
   This directory contains the metadata for non-English languages.
9. Repopulate the triggers and metadata. Run these scripts in the order that they are listed:

   1. db2 –v -td@ -f RDM_TRIGGERS_DB2.sql 
      –l log_file_name

   2. db2 –tvf RDM_METADATA_DB2.sql 
      –l log_file_name

   Note: To load English error messages, run the script RDM_ERRORS_100_ORACLE.sql:

   oracle -tvf 
   RDM_ERRORS_100_ORACLE.SQL 
   -l log_file_name
   

   If you do not wish to load any additional languages, skip the remaining steps.
10. For each additional language that you want to support, open the corresponding folder, such as the de folder.
    The folder contains files with these names:

    • RDM_CODETABLES.sql
    • RDM_ErrorMessages.sql
11. Run these commands in the order that they are listed:

    1. db2 -tvf 
       RDM_CODETABLES.SQL 
       -l log_file_name
       

    2. db2 -tvf 
       RDM_ErrorMessages.sql 
       -l log_file_name

12. Repeat Steps 10 and 11 for every language that you want to support.