This chapter describes the steps required to install the OHF Data Management Assembly for Oracle Data Integration (ODI). There are two ways to install the Data Management Assembly for ODI, depending on how you create the user schemas. The installer can create the user schemas during the installation or you can create them manually, prior to the installation. The two methods are described below:
Installing the Data Management Assembly without Pre-Created User Schemas
Installing the Data Management Assembly with Pre-Created User Schemas
The user is familiar with Oracle Database (DB), ODI, and Linux OS. | |
The OHF Data Model is installed.
Follow the instructions in Chapter 2, "Data Model Installation" or Chapter 9, "Data Model Upgrade". |
|
Make sure that the database compatible parameter is set to 12.1.0.2.0 by connecting to the DBA user and running the query below:
select * from v$parameter where name = 'compatible'; If the parameter is not set to 12.1.0.2.0, ask your database administrator to set it. |
|
ODI services can connect to the Data Model 7.1.1 database mentioned in the Oracle TNS file (TNS entries of the required database must be available in the installation server tnsnames.ora file). | |
The password expiry notification message does not display for the system user. | |
The installer is run on the system where the ODI server is installed. | |
The terminology loaders source file location exists. The installer creates an archive directory. For example,
/scratch/home/oemora/TL_Source is the source file location specified during installation, which already exists. /scratch/home/oemora/TL_Archive_Files is created by the installer as the archive directory. |
|
The path of the data file (Configuration schema/Repository schema tablespace) mentioned when creating the tablespace is correct. Make sure that the database user has write privileges. | |
Enough space is available in the installation directory and the Oracle Home directory. | |
The Sqlplus utility is available on the installation server. | |
The impdp utility is available on the repository database server. | |
The installation user has read, write, and execute privileges to the $ODI_HOME/bin folder. The installer creates product specific files under this location. | |
For remote installations, where the installation server and the ODI Repository Database server are different machines, make sure that:
|
|
GLOBAL_NAMES database initialization parameter is set to false. | |
Back up the following csv files under $ODI_HOME/bin if it exists:
|
|
If the Terminology Loaders source folder is shared, make a back up of the following files:
The installer will overwrite any existing files from the list above. |
Note:
The installer auto-populates some of the user parameters and lets you edit them.Extract the contents of the OHF media pack to your system. | |
Navigate to the <media_pack_location>/ folder. | |
Unzip the OHF_V711_Linux-x64.zip file where you want to launch the installer using the following command:
|
|
Navigate to the Disk1/install folder. | |
Change the protection on files as follows:
|
Start the Oracle Universal Installer by running the following command:
If the ODI repository schemas (master and work) to be created are on the database instance of the installation server, execute:
sh runInstaller.sh -local
If the ODI repository database or OHF data model database is on the database instance of another server, execute:
sh runInstaller.sh -local remote_installation=true
where, the -local
option is to install on the local node irrespective of the cluster nodes specified on the installer machine.
Screen | Action | |
---|---|---|
Welcome | Click Next. | |
Select a Product to Install | Select the Oracle Healthcare Foundation Data Management Assembly for ODI 7.1.1.0.0 option. | |
Specify Home Details | Enter the installation home path. | |
Verify Installation Prerequisites | Verify if all the prerequisites are met before proceeding. | |
Select the Oracle Home Configuration | Specify the Oracle client home path. | |
Select the ODI Home Location | Specify the ODI home location.
The ODI home should be one level above the /bin directory and should point to the /agent directory. For example, <path>/Oracle_ODI1/oracledi/agent. |
|
Select Database Server for ODI Repository Schemas | Select one of the following options for the ODI repository schemas:
|
|
Specify Mount Path Details (applicable only for remote installations) | Enter the following mounted directory configuration details in which the remote server directory is mounted:
To obtain the available storage drives, on the Linux machine, execute the <Remote Server name>:<Remote server path> <total size> <used up space> <Available space> <use%> <Path in installation server where mounting was done> For example, abc:/scratch/dump 191G 138G 44G 76% /installation server Note:
|
|
Specify Healthcare Data Model Database Instance Details | Enter values for the following fields:
|
|
Specify ODI Repository Database Instance Details (applicable only if you selected No in the previous screen for Select this database instance for repository schema creation) | Enter values for the following fields:
|
|
Specify ODI Supervisor Password | Specify the supervisor password used for the ODI console login. | |
Select Terminology Loaders Source Location | Specify the Terminology loaders source file location.
This location is used to read the terminology loaders source data files. You can change this location when required. The installer creates an archive directory at the same level as the source directory. Make sure that the create directory privileges exist for the installation user. |
|
Specify Healthcare Data Model Schema Details | Enter values for the following fields:
|
|
Specify Healthcare Data Model Schema Details | Enter values for the following fields:
|
|
Specify Terminology Loader Details | Enter values for the following fields:
Specify the new schema names for the Master and Work repository. The installer creates the Master and Work repository schemas, and imports loaders into them. |
|
Specify Warehouse Integration Loader Details | Enter values for the following fields:
The installer creates the configuration schema if it does not exist. Specify the new schema names for the Master and Work repository. The installer creates the Master and Work repository schemas, and imports loaders into them. |
|
Specify Healthcare Common Data Mart Loader Details | Enter values for the following fields:
The installer creates the configuration schema if it does not exist. Specify the new schema names for the Master and Work repository. The installer creates the Master and Work repository schemas, and imports loaders into them. |
|
Specify Healthcare Cohort Data Mart Loader Details | Enter values for the following fields:
Specify the new schema names for the Master and Work repository. The installer creates the Master and Work repository schemas, and imports loaders into them. The configuration schema is not required for CDM. |
|
Specify the Tablespace Details | Specify the tablespace names for the configuration schemas. The installer creates these tablespaces if they do not exist.
|
|
Specify the Tablespace Details | Specify the tablespace names for repository schemas. The installer creates these tablespaces if they do not exist.
|
|
Specify Tablespace Location for Configuration Schemas | Specify the tablespace location for configuration schemas.
The location should be present in the data model database server with write privileges. If the OHF data model database is not on the installation server, you must enter the location manually. |
|
Specify Tablespace Location for Repository Schemas | Specify the tablespace location for the ODI repository schema.
The location should be present in the repository database server with write privileges. If the repository database is not on the installation server, you must enter the location manually. |
|
Verify Configuration Parameters | Click Next. | |
Summary | Click Install. | |
End of Installation | Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer. |
Review the generated installation log files for errors. For details, see Installation Log Files. | |
Contact Oracle support, if necessary, to resolve any errors. |
Perform the following steps to create a new ODI repository login:
Navigate to ODI > File > New > Create a New ODI Repository Login. | |
Click OK. The Repository Connection Information screen is displayed. | |
Enter the following values:
|
|
Click OK. The login name is created with the name specified at the previous step. | |
Navigate to ODI > Connect > ODI Studio. | |
Enter the following details:
|
Similarly, follow the above steps to create the login for the Terminology loaders, Common Data Mart loader, and Cohort Data Mart loader.
The user is familiar with Oracle Database (DB), ODI, and Linux OS. | |
The OHF Data Model is installed.
Follow the instructions in Chapter 2, "Data Model Installation" or Chapter 9, "Data Model Upgrade". |
|
Make sure that the database compatible parameter is set to 12.1.0.2.0 by connecting to the DBA user and running the query below:
select * from v$parameter where name = 'compatible'; If the parameter is not set to 12.1.0.2.0, ask your database administrator to set it. |
|
ODI services can connect to the Data Model 7.1.1 database mentioned in the Oracle TNS file (TNS entries of the required database must be available in the installation server tnsnames.ora file). | |
The password expiry notification message does not display for the pre-created schemas or system user. | |
The installer is run on the system where the ODI server is installed. | |
The terminology loaders source file location exists. The installer creates an archive directory. For example,
/scratch/home/oemora/TL_Source is the source file location specified during installation, which already exists. /scratch/home/oemora/TL_Archive_Files is created by the installer as the archive directory. |
|
The path of the data file (Configuration schema/Repository schema tablespace) mentioned when creating the tablespace is correct. Make sure that the database user has write privileges. | |
Enough space is available in the installation directory and the Oracle Home directory. | |
The Sqlplus utility is available on the installation server. | |
The impdp utility is available on the repository database server. | |
The installation user has read, write, and execute privileges to the $ODI_HOME/bin folder. The installer creates product specific files under this location. | |
For remote installations, where the installation server and the ODI Repository Database server are different machines, make sure that:
|
|
GLOBAL_NAMES database initialization parameter is set to false. | |
Back up the following csv files under $ODI_HOME/bin if it exists:
|
|
If the Terminology Loaders source folder is shared, make a back up of the following files:
The installer will overwrite any existing files from the list above. |
Note:
The installer auto-populates some of the user parameters and lets you edit them.Create the following default and temporary tablespaces with appropriate quotas. You can use different tablespace names than the ones listed below.
Note:
The hmc_ts and hmc_temp tablespaces must be created in the Data Model database instance.Tablespace Name | Big File Tablespace | Description | |
---|---|---|---|
odirep_ts | Yes | Default tablespace for the Repository schema | |
odirep_temp | Yes | Temporary tablespace for the Repository schema | |
hmc_ts | Yes | Default tablespace for the Configuration schema | |
hmc_temp | Yes | Temporary tablespace for the Configuration schema |
Create the following user schemas and assign the appropriate default and temporary tablespaces. Refer to Create Default and Temporary Tablespaces for details. If you created tablespaces with different names, use those instead.
Schema Name | Schema Description | Default Tablespace | Temporary Tablespace | |
---|---|---|---|---|
wil_hmc | Warehouse Integration Loader Configuration schema | hmc_ts | hmc_temp | |
hcd_hmc | Healthcare Common Data Mart Configuration schema | hmc_ts | hmc_temp | |
tl_master_rep_7 11 | Terminology Loader Master Repository schema | odirep_ts | odirep_temp | |
tl_work_rep_7 11 | Terminology Loader Work Repository schema | odirep_ts | odirep_temp | |
wil_master_rep_711 | Warehouse Integration Loader Master Repository schema | odirep_ts | odirep_temp | |
wil_work_rep_711 | Warehouse Integration Loader Work Repository schema | odirep_ts | odirep_temp | |
hcd_master_rep_711 | Healthcare Common Data Mart Master Repository schema | odirep_ts | odirep_temp | |
hcd_work_rep_711 | Healthcare Common Data Mart Work Repository schema | odirep_ts | odirep_temp | |
cdm_master_rep_711 | Healthcare Cohort Data Mart Master Repository schema | odirep_ts | odirep_temp | |
cdm_work_rep_711 | Healthcare Cohort Data Mart Work Repository schema | odirep_ts | odirep_temp |
Extract the contents of the OHF media pack to your system. | |
Navigate to the <media_pack_location>/ folder. | |
Unzip the OHF_V711_Linux-x64.zip file where you want to launch the installer using the following command:
|
|
Navigate to the <media_pack_location>/Disk1/stage/Components/oracle.hsgbu.hc.dma.odi/7.1.1.0.0/1/DataFiles/Expanded/filegroup1 directory. | |
Unzip the dma_odi_master_install.zip file. | |
Navigate to the dma_odi_master_install/hmc_odi_install/ directory. | |
Connect to the system user and execute the following scripts:
|
|
Navigate to the <media_pack_location>/Disk1/install folder. | |
Change the protection on files as follows:
|
Start the Oracle Universal Installer by running the following command:
If the ODI repository schemas (master and work) to be created are on the database instance of the installation server, execute:
sh runInstaller.sh -local dba_tasks=false
If the ODI repository database or OHF data model database is on the database instance of another server, execute:
sh runInstaller.sh -local remote_installation=true dba_tasks=false
where, the -local
option is to install on the local node irrespective of the cluster nodes specified on the installer machine.
Screen | Action | |
---|---|---|
Welcome | Click Next. | |
Select a Product to Install | Select the Oracle Healthcare Foundation Data Management Assembly for ODI 7.1.1.0.0 option. | |
Specify Home Details | Enter the installation home path. | |
Verify Installation Prerequisites | Verify if all the prerequisites are met before proceeding. | |
Select the Oracle Home Configuration | Specify the Oracle client home path. | |
Select the ODI Home Location | Specify the ODI home location.
The ODI home should be one level above the /bin directory and should point to the /agent directory. For example, <path>/Oracle_ODI1/oracledi/agent. |
|
Select Database Server for ODI Repository Schemas | Select one of the following options for the ODI repository schemas:
|
|
Specify Mount Path Details (applicable only for remote installations) | Enter the following mounted directory configuration details in which the remote server directory is mounted:
To obtain the available storage drives, on the Linux machine, execute the <Remote Server name>:<Remote server path> <total size> <used up space> <Available space> <use%> <Path in installation server where mounting was done> For example, abc:/scratch/dump 191G 138G 44G 76% /installation server Note:
|
|
Specify Healthcare Data Model Database Instance Details | Enter values for the following fields:
|
|
Specify ODI Repository Database Instance Details (applicable only if you selected No in the previous screen for Select this database instance for repository schema creation) | Enter values for the following fields:
|
|
Specify ODI Supervisor Password | Specify the supervisor password used for the ODI console login. | |
Select Terminology Loaders Source Location | Specify the Terminology loaders source file location.
This location is used to read the terminology loaders source data files. You can change this location when required. The installer creates an archive directory at the same level as the source directory. Make sure that the create directory privileges exist for the installation user. |
|
Specify Healthcare Data Model Schema Details | Enter values for the following fields:
|
|
Specify Healthcare Data Model Schema Details | Enter values for the following fields:
|
|
Specify Terminology Loader Details | Enter values for the following fields:
The installer imports loaders into the pre-created terminology loaders repository schemas. |
|
Specify Warehouse Integration Loader Details | Enter the pre-created schema values for the following parameters:
The installer imports loaders into the pre-created warehouse integration loaders repository schemas. |
|
Specify Healthcare Common Data Mart Loader Details | Enter the pre-created schema values for the following parameters:
The installer imports loaders into the pre-created common data mart loaders repository schemas. |
|
Specify Healthcare Cohort Data Mart Loader Details | Enter the pre-created schema values for the following parameters:
The installer imports loaders into the pre-created cohort data mart loaders repository schemas. The configuration schema is not required for CDM. |
|
Verify Configuration Parameters | Click Next. | |
Summary | Click Install. | |
End of Installation | Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer. |
Review the generated installation log files for errors. For details, see Installation Log Files. | |
Contact Oracle support, if necessary, to resolve any errors. |
After the Data Management Assembly for ODI installation, run the following scripts from a user with DBA privileges:
@<OHF_Install_Home>/dma_odi_master_install/hmc_odi_install/dma_directory_drop.sql
@@<OHF_Install_Home>/dma_odi_master_install/hmc_odi_install/dma_revoke_privilege.sql <WIL_MASTER_REP_USR> <HCD_MASTER_REP_USR> <CDM_MASTER_REP_USR> <HLI_MASTER_REP_USR>
where,
<OHF_Install_Home>
- OHF installation home directory
<WIL_MASTER_REP_USR>
- Warehouse integration loader master repository schema name
<HCD_MASTER_REP_USR>
- Healthcare common data mart loader master repository schema name
<CDM_MASTER_REP_USR>
- Cohort data mart loader master repository schema name
<HLI_MASTER_REP_USR>
- Terminology loader master repository schema name