Manually upgrading the database on Db2 for z/OS from 11.6.0.1 to 11.6.0.2

Follow the steps to upgrade the version 11.6.0.1 InfoSphere® MDM database to the version 11.6.0.2 InfoSphere MDM database on DB2® for z/OS®.

Before you begin

If applicable, upgrade your MDM database from version 11.6.0.0 to version 11.6.0.1 before beginning this procedure.

Procedure

  1. To connect to Db2 for OS/390® and z/OS server from a Db2 Linux®, UNIX, or Windows server, Db2 Connect must be installed on the server you are connecting from. Enterprise editions contain Db2 Connect. To connect to the database, enter the following information:
    • Host name or IP address
    • Db2 port (default = 446)
    • Database name
    • Subsystem location name
    • User ID and password
  2. On the client server, catalog the database by running the following commands in this order:
    1. db2 catalog tcpip node YOUR_NODE_NAME remote Z/OS_HOSTNAME/IP_ADDRESS server Z/OS_PORT
    2. db2 catalog db YOUR_DB_NAME at node YOUR_NODE_NAME authentication dcs
    3. db2 catalog dcs db YOUR_DB_NAME as Z/OS_LOCATION_NAME
  3. If you are using this user ID to connect to the Db2 subsystem for the first time, rebind the packages for the database by following either of these steps:
    1. Rebind all the packages by running the command: db2rbind YOUR_DB_NAME all /u USER_NAME /p PASSWORD /r any
    2. Rebind individual packages by running the command: db2 bind package_name
  4. Change the placeholder tags in the all of the scripts:
    • Replace <DBA_ACCOUNT> with the user ID of the database administrator.
    • Replace <USER_ACCOUNT> with the user ID of the table owner.
    • Replace <db_prefix> with the three character database prefix.
    • Replace <STOGROUP_NAME> with the storage group name.
    • Replace <SCHEMA> with the schema name, in uppercase characters.
  5. From the upgrade folder, run the following scripts using the command format db2 -tvf script_name -1 log_file_name
    Important: You must run the scripts in the order that they are listed. 
    db2 -tvf alter_tables_zos.sql -1 log_file_name
db2 -tvf populate_grouping_display_name_zos.sql -1 log_file_name
    • alter_tables_zos.sql modifies existing table definitions.
    • populate_grouping_display_name_zos.sql populates values for the DISPLAY_NAME column in the GROUPING table.
  6. Verify whether your implementation of InfoSphere MDM uses simple triggers or compound triggers, then run the following scripts to upgrade the triggers, using the following command format: 
    db2 -v -td@ -f script_name -1 log_file_name
    • If your system uses simple triggers:
      1. Run CreateTriggers_simple.sql to create simple triggers for updates.
      2. Run CreateTriggers_delete_simple.sql to create simple triggers for deletions.
    • If your system uses compound triggers:
      1. Run CreateTriggers_compound.sql to create compound triggers for inserts and updates.
      2. Run CreateTriggers_delete_compound.sql to create compound triggers for deletions.
  7. Navigate to the MDM_INSTALL_HOME/database/Upgrade/11.6.0.2/Level-I/DB2/ZOS/ddl directory.
  8. In the folder name, CODE_LANG is the language that is currently installed.
    Note: If any of the directories are empty, no data was generated and you do not need to run the scripts.
    • MDM_INSTALL_HOME/database/Upgrade/11.6.0.2/Level-I/DB2/ZOS/ddl/data_req_CODE_LANG/data
    • MDM_INSTALL_HOME/database/Upgrade/11.6.0.2/Level-I/DB2/ZOS/ddl/data_CODE_LANG/data-industry
    • MDM_INSTALL_HOME/database/Upgrade/11.6.0.2/Level-I/DB2/ZOS/ddl/data_opt_CODE_LANG/data

    If you are loading English data only, set the CODE_LANG to en. Otherwise, set the CODE_LANG to the language code of the language you are loading.

  9. To load the common data from the command line, run the scripts in the MDM_INSTALL_HOME/database/Upgrade/11.6.0.2/Level-I/DB2/ZOS/ddl/data_req_en/data directory. Use the command: db2 -tvf script_name-l log_file_name:
    1. The insert.sql script inserts new data.
    2. The update.sql script updates existing table data.
    3. The delete.sql script deletes obsolete table data.
  10. To load the English industry data from the command line, run the scripts in the MDM_INSTALL_HOME/database/Upgrade/11.6.0.2/Level-I/DB2/ZOS/ddl/data_en/data-industry directory. Use the command: db2 -tvf script_name -l log_file_name:
    1. The insert.sql script inserts new data.
    2. The update.sql script updates existing table data.
    3. The delete.sql script deletes obsolete table data.
  11. If you are loading industry data for a language other than English, from the command line, run the scripts in the MDM_INSTALL_HOME/database/Upgrade/11.6.0.2/Level-I/DB2/ZOS/ddl/data_CODE_LANG/data-industry directory.
    Use the command: db2 -tvf script_name -l log_file_name
    1. The insert.sql script inserts new data.
    2. The update.sql script updates existing table data.
    3. The delete.sql script deletes obsolete table data.
  12. If you are loading code table data for a language other than English, from the command line, run the scripts in the MDM_INSTALL_HOME/database/Upgrade/11.6.0.2/Level-I/DB2/ZOS/ddl/data_opt_CODE_LANG/data directory. Use the command: db2 -tvf script_name -l log_file_name:
    1. The insert.sql script inserts new data.
    2. The update.sql script updates existing table data.
    3. The delete.sql script deletes obsolete table data.
  13. Repeat the previous step for each non-English language that is installed.