Information Management IBM InfoSphere MDM Custom Domain Hub, Version 10.1

To manually install the core database on Oracle

  1. Navigate to the MDM/database/CoreData/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. Change the following placeholders:
    1. <DBNAME> to the name of the database.
    2. <SCHEMA> to a database user with the required privileges
    3. <NEWPASSWORD> to the password of the schema user
    4. <TABLE_SPACE> to the tablespace name where base and history table data will be stored
    5. <INDEX_SPACE> to a tablespace name where indexed data will be stored
    6. <LONG_SPACE> to a tablespace 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 located 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 lower case:
      • banking
      • insurance
      • telco
      • manufacturing
    9. <CONFIG_LANG> to the configuration 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
    11. <DBUSER> to a database user with DBA Authority
    12. <DBPASSWORD> to the password of the dbuser
  3. From the command line in MDM/database/CoreData/Oracle/Standard/ddl, run the commands in the order that they are listed:
    1. sqlplus <DBUSER>/<DBPASSWORD>@<DBNAME> @create_schema_ora.sql>> <LOG_FILE_NAME> creates the database schema.
    2. sqlplus <SCHEMA>/<NEWPASSWORD>@<DBNAME> @create_tables_ora.sql>> <LOG_FILE_NAME> creates the base tables and primary key definitions.
    3. sqlplus <SCHEMA>/<NEWPASSWORD>@<DBNAME> @create_hist_tables_ora.sql>> <LOG_FILE_NAME> creates the history tables and primary key definitions.
    4. sqlplus <SCHEMA>/<NEWPASSWORD>@<DBNAME> @create_ix_ora.sql>> <LOG_FILE_NAME> creates all indexes, including unique index constraints.
    5. sqlplus <SCHEMA>/<NEWPASSWORD>@<DBNAME> @create_fk_ora.sql>> <LOG_FILE_NAME> creates the foreign keys.
    6. sqlplus <SCHEMA>/<NEWPASSWORD>@<DBNAME> @create_chk_ora.sql>> <LOG_FILE_NAME> creates the check constraints.
    7. sqlplus <SCHEMA>/<NEWPASSWORD>@<DBNAME> @create_eME_ora.sql>> <LOG_FILE_NAME> creates the InfoSphere® MDM Probabilistic Matching Engine objects
  4. If your application is running across different time zones, or your data has time values under different time zones, you must enable the multi-time zone feature. If you do not need to use the multi-time zone feature, you must disable it when you install the database
    • To disable the multi-time-zone feature:
      1. Navigate to the .ddl subdirectory.
      2. From the command line, run the script:

        sqlplus <SCHEMA>/<NEWPASSWORD>@<DBNAME>

        @Create_function_utc_disabled.sql >> <LOG_FILE_NAME>

    • To enable the multi-time zone feature:
      1. Navigate to the .ddl subdirectory.
      2. From the command line, run the script:

        sqlplus <SCHEMA>/<NEWPASSWORD>@<DBNAME>

        @Create_function_utc_enabled.sql >> <LOG_FILE_NAME>

  5. Run the commands for either compound triggers or simple triggers.
    • To install simple triggers, run the scripts:
      • 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.
  6. 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 entered in the <DTYPE> placeholder, and the configuration data in the language entered in the <CONFIG_LANG> placeholder.
  7. Choose whether to install code table date for languages other than English.
    • If you are only installing the product in English, skip this step.
    • To install code table data for languages other than English for the industry entered in the <DTYPE> placeholder and the language code 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.
  8. Optional: To enable non case sensitive searching, run the script:
    sqlplus <SCHEMA>/<NEWPASSWORD>@<DBNAME> @Insensitive_search_enabled.sql >> 
    <LOG_FILE_NAME>
    Note: The create_schema_ora.sql statement creates two separate table spaces for the InfoSphere MDM Probabilistic Matching Engine, as follows: <TABLE_SPACE>E and <INDEX_SPACE>E


Feedback

Timestamp Last updated: November 2012

Topic URL: