Installing the Data Management Assembly with Pre-Created User Schemas
Complete the following:
Check Prerequisites
- | Steps |
---|---|
The user is familiar with Oracle Database (DB), Oracle Data Integrator, and Linux OS. |
|
The Oracle Healthcare Foundation Data Model is installed. Follow the
instructions in |
|
The Data Management Assembly installer is run on the system where the Oracle Data Integrator server is installed. |
|
Make sure that the database compatible parameter is set to 19.3.0.0.0 by connecting to the DBA user and running the query below:
If the parameter is not set to 19.3.0.0.0, ask your database administrator to set it. |
|
Oracle Data Integrator services can connect to the Data Model 8.2.2 database mentioned
in the Oracle TNS file (TNS entries of the required database must be available
in the installation server |
|
The password expiry notification message does not display for the pre-created schemas or system user. |
|
The terminology loaders source file location exists. The installer creates an archive directory. For example,
|
|
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. |
|
Check write permissions on oraInventory is granted to “others”. If write permissions are not granted then add the user that the oracle software being installed to the group of the inventory owner (for instance - oinstall) as root:
|
|
The installation user has
read, write, and execute privileges to the
|
|
For remote installations, where the installation server and the Oracle Data Integrator Repository Database server are different machines, make sure that:
|
|
GLOBAL_NAMES database initialization parameter is set to false. |
|
In the case of an Oracle Healthcare Foundation upgrade, back up the following csv files under
|
|
In the case of an Oracle Healthcare Foundation upgrade, if the Terminology Loaders source folder is shared, make a backup 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 Default and Temporary Tablespaces
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. |
|
wil_odi_ts |
Yes |
Default tablespace for Oracle Data Integrator temporary objects for Warehouse Integration loaders. |
|
hcd_odi_ts |
Yes |
Default tablespace for Oracle Data Integrator temporary objects for Healthcare Common Data mart loaders. |
|
cdm_odi_ts |
Yes |
Default tablespace for Oracle Data Integrator temporary objects for Cohort Data mart loaders. |
|
tl_odi_ts |
Yes |
Default tablespace for Oracle Data Integrator temporary objects for terminology loaders. |
Create User Schemas
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 |
|
ohf_master_rep_80 |
Warehouse Integration Loader Master Repository schema |
odirep_ts |
odirep_temp |
|
ohf_work_rep_80 |
Warehouse Integration Loader Work Repository schema |
odirep_ts |
odirep_temp |
Prepare the Installer
- | Steps |
---|---|
Extract the contents of the Oracle Healthcare Foundation media pack to your system. |
|
Navigate to media_pack_location/ folder. |
|
Unzip the
|
|
Navigate to the |
|
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 the files as follows: chmod 755 * |
Run the Installer
Start the Oracle Universal Installer by running the following command:
- If the Oracle Data Integrator 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 Oracle Data Integrator repository database or Oracle Healthcare Foundation 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 8.2.2.0.0 option. |
|
Specify Home Details |
Enter the installation home path. |
|
Verify Installation Prerequisites |
Verify if all of the prerequisites are met before proceeding. |
|
Select the Oracle Home Configuration |
Specify the Oracle client home path. |
|
Select the Oracle Data Integrator Home Location |
Specify the Oracle Data Integrator home location. The Oracle Data Integrator home should be one level above the
|
|
Select Database Server for Oracle Data Integrator Repository Schemas |
Select one of the following options for the Oracle Data Integrator repository schemas:
|
|
Specify Mount Path Details (applicable only for remote installations) |
Enter the configuration details for the mounted remote server directory:
To obtain the available storage drives, on the Linux machine, execute the
For example:
Note:
|
|
Specify Healthcare Data Model Database Instance Details |
Enter values for the following fields:
|
|
Specify Oracle Data Integrator 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 Oracle Data Integrator Supervisor Password |
Specify the supervisor password used for the Oracle Data Integrator 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 pre-created schemas:
|
|
Specify Healthcare Data Model Schema Details |
Enter values for the pre-created schemas:
|
|
Specify Warehouse Integration Loader Details |
Enter values for the pre-created schemas:
The installer imports loaders into the pre-created warehouse integration loaders repository schemas. |
|
Specify Healthcare Common Data Mart Loader Details |
Enter values for the pre-created schemas:
The installer imports loaders into the pre-created common data mart loaders repository schemas. |
|
Specify Healthcare Cohort Data Mart Loader Details |
Enter values for the pre-created schemas:
The installer imports loaders into the pre-created cohort data mart loaders repository schemas. The configuration schema is not required for CDM. |
|
Specify RCU Prefix and Password |
Specify an RCU prefix to be prepended to the schemas created by the Oracle Data Integrator Repository Creation Utility (RCU). The RCU creates 3 schemas:
Note: The RCU Prefix must be unique. The prefix should be alphabetic only. It cannot have special characters and cannot start with a number. The length of the prefix must not exceed 8 characters. Specify a password for schemas created using the Oracle Data Integrator Repository Creation Utility (RCU). Note: The password must be between 8 and 12 alphanumeric characters long and must include at least one number. The password cannot start with a number. |
|
Specify Tablespace for Creation of Oracle Data Integrator Temporary Objects |
Specify tablespace names for the creation of temporary objects used by the Oracle Data Integrator loaders. The installer creates the following tablespaces if they do not exist:
Oracle recommends that you provide different tablespace names for each component. |
|
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. |
Check the Installation
- | Steps |
---|---|
Review the generated installation log files for errors. For details, see
|
|
Contact Oracle support, if necessary, to resolve any errors. |
Revoke Privileges
After the Data Management Assembly for Oracle Data Integrator 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
- Oracle Healthcare Foundation 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