Editing the upgrade properties file

Manually edit the UpgradePaths.properties properties file to allow the ant script to perform the database upgrade.

1. Navigate to the MDM_INSTALL_HOME/mds/scripts directory.
2. Open the UpgradePaths.properties file in your preferred text editor.
3. See the instructions in the comments within the file itself for more information about each parameter. The specific parameter names are listed here:
   • mdm.upgrade.basedir - The base directory where the upgrade SQL scripts are located. The path that you specify here will end in the folder named upgrade. The subfolders in the upgrade folder correspond to the version numbers of previous InfoSphere® MDM releases.
   • rdm.upgrade.basedir - This parameter is commented out by default. Do not uncomment or change the parameter. It is available to enable future functionality.
   • mdm.ae.locales - When it was installed, your current installation of InfoSphere MDM was configured to use one or more locales. Specify the same locales here that were specified with the original installation.
   • mdm.ae.industry - When it was installed, your current installation of InfoSphere MDM was configured to include one or more industry data sets. The values can be banking, insurance, telco, or manufacturing. Use the same value or values that were used with the original installation.
   • mdm.ae.triggers - When it was installed, your current installation of InfoSphere MDM was configured to use either simple triggers, compound triggers, or no triggers. Refer to your installation notes for the types of triggers that are installed in InfoSphere MDM and enter the same value for this parameter. The type you specify here must match what is already configured for InfoSphere MDM.
   • mdm.ae.delete.triggers - As with mdm.ae.triggers, choose compound, simple, or none depending on how your current InfoSphere MDM installation is configured.
   • db.type - The supported values are DB2 or Oracle.
   • db.subtype - The supported value is Standard.
   • db.driver.class
   • db.driver.path
   • db.jdbc.url
   • db.uid - The user ID that is used to connect to the database and to run the upgrade scripts. Ensure that it has sufficient privileges to alter schemas and perform other necessary operations.
   • db.pwd - The password that corresponds to the user ID you provided.
   • db.name - The name of the database you to which the scripts will connect, for example, MDMDB.
   • starting.version.number - Enter the version of InfoSphere MDM that you will be upgrading. InfoSphere MDM version 11.4 includes the scripts that are necessary to upgrade from version 8.5.0. The correct version numbers to use for the starting.version.number parameter are 8.5.0, 9.0.1. 9.0.2, 10.0.0, 10.0.1, 11.0.0, and 11.3.0.
   • upgrade.path.8.5.0 - Do not edit this value.
   • upgrade.path.9.0.1 - Do not edit this value.
   • upgrade.path.9.0.2 - Do not edit this value.
   • upgrade.path.10.0.0 - Do not edit this value.
   • upgrade.path.10.1.0 - Do not edit this value.
   • upgrade.path.11.0.0 - Do not edit this value.
   • upgrade.path.11.3.0 - Do not edit this value.
   • SCHEMA - Some table names in the upgrade scripts are qualified with the SCHEMA name or the DBUSER name. The two terms mean the same thing. Some older scripts used the term DBUSER while others used the term SCHEMA.
   • DBUSER - See previous note.
   • TABLE_SPACE - Enter name of the User Data table space name. Provide the value that was used when the MDM database was first created. Refer to the database. The default pool size is 8K.
   • INDEX_SPACE - Enter the name of Index Table space. Provide the value that was used when the MDM database was first created. Refer to the database.
   • LONG_SPACE - Enter the name of the log data table space. Provide the value that was used when the MDM database was first created. Refer to the database.
   • TABLE_SPPMD - Enter the name of the tablespace to contain the new Probabilistic Matching Engine tables. The upgrade process will create the tablespace for you.
   • TABLE_SPPMI - Enter the name of the tablespace to contain the new Probabilistic Matching Engine indices. The upgrade process will create the tablespace for you.
   • DB_OS - Enter the desired default value for /IBM/DWLCommonServices/DataBase/OS
   • DB_TYPE - The current release supports DB2 and Oracle.
     Note: The DB_TYPE element is part of the configuration of InfoSphere MDM at runtime. The db.type parameter mentioned previously identifies the folder in the upgrade scripts for the database you want to upgrade. The two parameters should always refer to the same type of database (for example, use Oracle for Oracle, and DB2 for DB2) but the specific syntax of each parameter might differ.
   • DB_VERSION - Enter the desired default value for /IBM/DWLCommonServices/DataBase/version. See the link at the end of this topic for more information about the elements in the Configuration and Management component.
   • DEFAULT_TIMEZONE - Enter the desired default value for /IBM/DWLCommonServices/MultiTimeZoneDeployment/defaultTimeZone. See the link at the end of this topic for more information about the elements in the Configuration and Management component.
   • TIMEZONE_ENABLED - The current release supports a value of false.
   • NLS_SYS_LANG - Enter the desired default value for /IBM/DWLCommonServices/NLS/system_Default_Data_Locale. See the link at the end of this topic for more information about the elements in the Configuration and Management component.
   • DSRC_CODE - Enter desired default value for /IBM/ThirdPartyAdapters/EAS/dsrcCode. See the link at the end of this topic for more information about the elements in the Configuration and Management component.
   • EXCLUSIVE_CIENT_SYSTEMS - Enter desired default value for /IBM/ThirdPartyAdapters/EAS/exclusiveSourceSystem. See the link at the end of this topic for more information about the elements in the Configuration and Management component.
4. Save and close the file.