Installing the domain database manually on Oracle

Manually install the domain database on Oracle by replacing several placeholder values and running a number of commands.

Before you begin

Before you start the installation:
  • Make sure that you created the core database, and that you have the correct level of access to it. The domain database assets are added to the same database.
  • Read the manual installation of the physical MDM database topic, and make the same decisions on the optional steps as you made when you install the core database.

Procedure

  1. Go to the MDM_INSTALL_HOME/database/Full/Oracle/Standard/ddl directory:
  2. Edit all of the scripts in this directory by replacing the placeholder values with the values you want to use in your database as follows:
    1. Replace DBNAME with the name of the database.
    2. Replace SCHEMA with the schema name assigned to hold the database assets.
    3. NEWPASSWORD to the password of the schema user.
    4. TABLE_SPACE to the table space name where base and history table data will be stored.
    5. INDEX_SPACE to a table space name where indexed data will be stored.
    6. LONG_SPACE to a table space where long user column data like CLOB and XML will be stored
    7. TABLESPACE_LOCATION to the location where the table space will be created. This is usually in the database directory that is in ORACLE_HOME. For example, D:/Oracle/product/10.2.0/oradata/MDMDB where MDMDB is the name of the database and 10.2.0 is the version of Oracle being used.
    8. DTYPE to the type of data to be loaded. Specify one of the following values in lowercase:
      • banking
      • insurance
      • telco
      • manufacturing
    9. CONFIG_LANG to the language to be used. For example, for English use en; for French use fr.
    10. CODE_LANG to the language of any additional code table data to be loaded. For example, for Japanese use ja; for French use fr.
  3. From the command line in MDM_INSTALL_HOME/database/Full/Oracle/Standard/ddl, run these commands in the order that they are listed:
    1. sqlplus SCHEMA/NEWPASSWORD@DBNAME @create_tables_ora.sql>> LOG_FILE_NAME creates the base tables and primary key definitions
    2. sqlplus SCHEMA/NEWPASSWORD@DBNAME @create_hist_tables_ora.sql>> LOG_FILE_NAME creates the history tables and primary key definitions
    3. sqlplus SCHEMA/NEWPASSWORD@DBNAME @create_ix_ora.sql>> LOG_FILE_NAME creates all indexes, including unique index constraints
    4. sqlplus SCHEMA/NEWPASSWORD@DBNAME @create_fk_ora.sql>> LOG_FILE_NAME creates the foreign keys
    5. sqlplus SCHEMA/NEWPASSWORD@DBNAME> @create_chk_ora.sql>> LOG_FILE_NAME creates the check constraints
    6. sqlplus SCHEMA/NEWPASSWORD@DBNAME @create_eME_ora.sql>> LOG_FILE_NAME creates the InfoSphere® MDM Probabilistic Matching Engine objects.
      Important: Before you run the create_eME_ora.sql script in the next step, edit the script and replace the place holders TABLE_SPACE and INDEX_SPACE with the table space and index space names created for the InfoSphere MDM Probabilistic Matching Engine database objects.
  4. Run the scripts for either compound triggers or simple triggers:
    • To install simple triggers:
      • sqlplus SCHEMA/NEWPASSWORD@DBNAME @create_triggers_simple_ora.sql>> LOG_FILE_NAME installs simple triggers
      • Optional: sqlplus SCHEMA/NEWPASSWORD@DBNAME @create_delete_triggers_simple_ora.sql>> LOG_FILE_NAME installs simple triggers for deletes
    • To install compound triggers, run the scripts:
      • sqlplus SCHEMA/NEWPASSWORD@DBNAME @create_triggers_compound_ora.sql>> LOG_FILE_NAME installs compound triggers for inserts and updates.
      • Optional: sqlplus SCHEMA/NEWPASSWORD@DBNAME @create_delete_triggers_compound_ora.sql>> LOG_FILE_NAME installs compound triggers for deletes.
  5. Convert the ImpReqData.script file to a shell script, and run the shell script from the command line. This script populates the required code tables and required system configuration tables with English code table data for the industry that is entered in the DTYPE placeholder, and the configuration data in the language that is entered in the CONFIG_LANG placeholder.
  6. Choose whether to install code table date for languages other than English.
    • If you are installing the product in English only, skip this step.
    • To install code table data for languages other than English for the industry that is entered in the DTYPE placeholder and the language code that is entered in the CODE_LANG placeholder, convert the Imp_CodeTables_Data.script file to a shell script, and run the shell script from the command line. Repeat this step for each language you want to install.
  7. To populate the configuration manager table with English language data, the data path is entered in the DEL_DATA_PATH placeholder (if you did not modify the directory location, the path is /data) and the logs are entered in the DEL_DATA_LOGS placeholder. Convert the ImpReqDataCfgMgr.script file to a shell script, and run the shell script from the command line. This script populates the required system configuration tables with English data.
  8. If you enabled non-case sensitive searching in the core database, you must run the following script: 
    Sqlplus SCHEMA/NEWPASSWORD@DBNAME @Insensitive_search_enabled.sql >> LOG_FILE_NAME