Troubleshooting
Problem
When IBM® InfoSphere® Master Data Management is installed with an IBM® Db2® for z/OS® database, the InfoSphere MDM database upgrade target upgrade-mdm-ae-db does not create new tables.
The upgrade-mdm-ae-db target is used by the following targets:
- Upgrade_MasterDataManagement
- upgrade_mdm
- upgrade_physical_mdm
As a result of this issue, new MDM database tables are not created in Db2® for z/OS® when any of these targets are used.
Cause
New MDM database tables are not created in Db2® for z/OS® deployments because the corresponding table spaces are not created.
The SQLID that must be used when creating Db2® for z/OS® table spaces is the administrator user ID (DBA Account). However, the SQLID gets replaced by the table owner (USER Account), which means the table spaces cannot be created.
Environment
The issue occurs when InfoSphere® MDM uses a Db2® for z/OS® database and an MDM database upgrade is performed using the InfoSphere® MDM madconfig targets.
Resolving The Problem
To resolve this issue, complete the following steps before running the upgrade madconfig target.
- Go to <MDM_INSTALL_HOME>/database/Upgrade.
- Edit files in the Upgrade folder to replace <DBA_ACCOUNT> with the administrator user ID. Determine the files that need to be modified based on the InfoSphere® MDM installation version that you are upgrading from.
Note: These changes must be done in the same InfoSphere® MDM environment from which the upgrade target will be run.
Here is the list of files that create table spaces in z/OS®:
- EM_Merge/DB2/ZOS/ddl/CreateEvtMgrDB_zos.sql
- 10.0.0/Level-I/DB2/ZOS/ddl/create_tablespaces_zos.sql
- 10.1.0/Level-II/DB2/ZOS/ddl/create_tablespaces_zos.sql
- 10.1.0/Level-I/DB2/ZOS/ddl/create_tablespaces_zos.sql
- 11.0.0/Level-I/DB2/ZOS/ddl/create_tablespaces_zos.sql
- 11.4.0/Level-I/DB2/ZOS/ddl/create_tablespaces_zos.sql
- 11.6.0/Level-I/DB2/ZOS/ddl/CreateTableSpaces.sql
- 11.6.0.4/Level-I/DB2/ZOS/ddl/create_tables_spaces_zos.sql
- 11.6.0.6/Level-I/DB2/ZOS/ddl/create_tables_spaces_zos.sql - Run the madconfig target that performs the database upgrade. Depending on your upgrade strategy, this could be Upgrade_MasterDataManagement, upgrade_mdm, upgrade_physical_mdm, or upgrade-mdm-ae-db.
Document Location
Worldwide
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"ARM Category":[{"code":"a8m500000008dDQAAY","label":"Install and Upgrade"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
27 April 2022
UID
ibm16434745