DB2 or Microsoft SQL Server: Adding new InfoSphere MDM database objects to the upgraded Initiate database

As part of setting up the database, you must add some database objects from your new InfoSphere® MDM installation to the existing Initiate® database. Follow the steps to create the tables, indexes, foreign keys, and triggers. The steps that follow apply to systems that use DB2® or Microsoft SQL Server databases.

1. After you have installed the physical MDM database tables, update the configuration manager table in the schema for the Initiate database with values from the schema for the new InfoSphere MDM installation. For example, if your database is DB2, run MDM_INSTALL_HOME/database/CoreData/Full/DB2/Standard/ddl/UpdCfgMgrData_temp.sql. The script updates values in the CONFIGELEMENT table rows with names such as /IBM/DWLCommonServices/DataBase/OS, /IBM/DWLCommonServices/DataBase/type, and so on.
   Note: The UpdCfgMgrData_temp.sql file is not available for DB2 for z/OS®. If you are using DB2 with z/OS, run SQL statements as a replacement for the UpdCfgMgrData_temp.sql file. The example that follows indicates an upgrade from version 10.1:

   UPDATE CONFIGELEMENT SET VALUE_DEFAULT = 
   'AIX', LAST_UPDATE_DT = CURRENT TIMESTAMP, 
   LAST_UPDATE_USER='INSTALLATION' WHERE NAME = 
   '/IBM/DWLCommonServices/DataBase/OS';
   
   UPDATE CONFIGELEMENT SET VALUE_DEFAULT = 
   'DB2', LAST_UPDATE_DT = CURRENT TIMESTAMP, 
   LAST_UPDATE_USER='INSTALLATION' WHERE NAME = 
   '/IBM/DWLCommonServices/DataBase/type';
   
   UPDATE CONFIGELEMENT SET VALUE_DEFAULT = 
   '10.1.0.0', LAST_UPDATE_DT = CURRENT TIMESTAMP, 
   LAST_UPDATE_USER='INSTALLATION' WHERE NAME = 
   '/IBM/DWLCommonServices/DataBase/version';
   
   UPDATE CONFIGELEMENT SET VALUE_DEFAULT = 
   'EST5EDT', LAST_UPDATE_DT = CURRENT TIMESTAMP, 
   LAST_UPDATE_USER='INSTALLATION'  WHERE NAME = 
   '/IBM/DWLCommonServices/MultiTimeZoneDeployment/defaultTimeZone';
   
   UPDATE CONFIGELEMENT SET VALUE_DEFAULT = 
   'true', LAST_UPDATE_DT = CURRENT TIMESTAMP, 
   LAST_UPDATE_USER='INSTALLATION'  WHERE NAME = 
   '/IBM/DWLCommonServices/MultiTimeZoneDeployment/enabled';
   
   UPDATE CONFIGELEMENT SET VALUE_DEFAULT = 
   'en', LAST_UPDATE_DT = CURRENT TIMESTAMP, 
   LAST_UPDATE_USER='INSTALLATION'  WHERE NAME = 
   '/IBM/DWLCommonServices/NLS/system_Default_Data_Locale';
   
   UPDATE CONFIGELEMENT SET VALUE_DEFAULT = 
   '', LAST_UPDATE_DT = CURRENT TIMESTAMP, 
   LAST_UPDATE_USER='INSTALLATION' WHERE NAME = 
   '/IBM/ThirdPartyAdapters/EAS/dsrcCode';
   
   UPDATE CONFIGELEMENT SET VALUE_DEFAULT = 
   '', LAST_UPDATE_DT = CURRENT TIMESTAMP, 
   LAST_UPDATE_USER='INSTALLATION' WHERE NAME = 
   '/IBM/ThirdPartyAdapters/EAS/exclusiveSourceSystem'; 

2. To validate the changes, view ELEMENT_ID to determine whether the placeholder <DB_OS> in default_value was replaced with the actual database operating system.
3. Verify the schema with the new version of IBM® InfoSphere MDM.