Installing the Data Management Assembly without Pre-Created User Schemas

Complete the following:

Parent topic: Data Management Assembly for Oracle Data Integrator Installation

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 `Data Model Installation` or `Data Model Upgrade`.
	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: `select * from v$parameter where name = 'compatible';` 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 tnsnames.ora file).
	The password expiry notification message does not display for the system user.
	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: `usermod -a -G <ORA inventory owner> <installation_user>`
	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/odi/agent/bin` folder. The installer creates product specific files under this location.
	For remote installations, where the installation server and the Oracle Data Integrator Repository Database server are different machines, make sure that: A directory from the remote database server is mounted to the installation server with appropriate read and write privileges. The remote directory is accessible from the installation server on mounting. The user that owns Oracle db services on the remote server has privilege 755 for the directory that was mounted on the installation server. If the database is on an Exadata machine, provide the database single node (the node which is mounted) as the host name when prompted during installation.
	GLOBAL_NAMES database initialization parameter is set to false.
	In case of an Oracle Healthcare Foundation upgrade, back up the following csv files under `$ODI_HOME/odi/agent/bin` if it exists: `bus_susp_day.csv` `daylght_svngs_day.csv` `hosp_hol_day.csv` `time_odi.csv`
	In case of an Oracle Healthcare Foundation upgrade, if the Terminology Loaders source folder is shared, make a backup of the following files: `Code Axes.txt` `Code Descriptions.txt` `Code Hierarchy.txt` `Code.txt` `Related Entity.txt` `Relations Type.txt` `Relations.txt` `Relationship Type.txt` `time.txt` 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.

Parent topic: Installing the Data Management Assembly without Pre-Created User Schemas

Prepare the Installer

-	Steps
	Extract the contents of the Oracle Healthcare Foundation media pack to your system.
	Navigate to the media_pack_location/ folder.
	Unzip the `OHF_V821_Linux-x64.zip` file where you want to launch the installer using the following command: `unzip -a OHF_V821_Linux-x64.zip`
	Navigate to the Disk1/install folder.
	Change the protection on the files as follows: `chmod 755 *`

Parent topic: Installing the Data Management Assembly without Pre-Created User Schemas

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
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

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 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 `/oracle_common` directory. For example: `/u01/app/oracle/Oracle_ODI1`.
	Select the Database Server for the Oracle Data Integrator Repository Schemas	Select one of the following options for the Oracle Data Integrator repository schemas: If the Oracle Data Integrator repository database server is on the installation server, select the Installation database server option. Else, select the Remote database server option.
	Specify Mount Path Details (applicable only for remote installations)	Enter the configuration details for the mounted remote server directory: Mounted directory path on the remote server Mount path on the installation server To obtain the available storage drives, on the Linux machine, execute the `df -h` command. If the remote server directory is mounted on the installation server, the mounting is displayed as follows: `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: The directory of the remote database server should be mounted to the installation server with appropriate read and write privileges for the IMPDB utility. If the remote server mounted path is displayed as /, provide the absolute mounted path of the remote server.
	Specify Healthcare Data Model Database Instance Details	Enter values for the following fields: Host name - By default, the system host name appears. For remote installations, set this value to the host name of the remote machine. Port number Service name System user password Select this database instance for repository schema creation If you select Yes, the installer uses the same Data Model database instance for Oracle Data Integrator repository schema creation.
	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: Host name - By default, the system host name appears. For remote installations, set this value to the host name of the remote machine. Port Service name System user password
	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 following fields: Interface table schema name Interface table schema password Data warehouse schema name Data warehouse schema password Common data mart (hcd) schema name Common data mart (hcd) schema password Cohort data mart (cdm) schema name Cohort data mart (cdm) schema password
	Specify Healthcare Data Model Schema Details	Enter values for the following fields: Enterprise schema name Enterprise schema password.
	Specify Warehouse Integration Loader Details	Enter values for the following fields: Configuration schema name Configuration schema password: Specify WIL configuration schema user and password details. Installer creates new schema for a fresh installation. Specify existing schema user and password details for upgrade.
	Specify OHF Repository Schema Details	Specify OHF repository schema details OHF ODI repository schema name OHF ODI repository schema password Specify the OHF Repository schema user and password details. The Installer creates new Repository schema.
	Specify Healthcare Cohort Data Mart Loader Details	Enter values for the following fields: Configuration schema name Configuration schema password Specify the new schema names for the HCD configuration schema, for upgrade specify the existing HCD configuration schema name.
	Specify RCU Prefix and Password	Specify an RCU prefix to be appended to the schemas created by the Oracle Data Integrator Repository Creation Utility (RCU). The RCU creates 3 schemas: RCU prefix_STB RCU prefix_WLS RCU prefix_WLS_RUNTIME 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 the Tablespace Details	Specify the tablespace names for the configuration schemas. The installer creates these tablespaces if they do not exist. Configuration schema default tablespace name Configuration schema temporary tablespace name
	Specify the Tablespace Details	Specify the tablespace names for repository schemas: wil_odi_ts - Default tablespace for Oracle Data Integrator temporary objects for Warehouse Integration Loaders hcd_odi_ts - Default tablespace for Oracle Data Integrator temporary objects for Healthcare Common Data mart Loaders cdm_odi_ts - Default tablespace for Oracle Data Integrator temporary objects for Cohort Data mart Loaders tl_odi_ts - Default tablespace for Oracle Data Integrator temporary objects for Terminology Loaders
	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 these tablespaces if they do not exist. Warehouse Integration Loaders Healthcare Common Data mart Loaders Cohort Data mart Loaders Terminology Loaders Oracle recommends that you provide different tablespace names for each component.
	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 Oracle Healthcare Foundation 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 Oracle Data Integrator 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.

Parent topic: Installing the Data Management Assembly without Pre-Created User Schemas

Check the Installation

-	Steps
	Review the generated installation log files for errors. For details, see `Installation Log Files`.
	Contact Oracle support, if necessary, to resolve any errors.

Parent topic: Installing the Data Management Assembly without Pre-Created User Schemas

Create a New Oracle Data Integrator Repository Login

Perform the following steps to create a new Oracle Data Integrator repository login:

-	Steps
	Navigate to ODI > File > New > Create a New ODI Repository Login.
	Click OK. The Repository Connection Information screen is displayed.
	Enter the following values: Login Name - For example, OHF_REPOSITORY_LOGIN User - SUPERVISOR Password - Provide the Oracle Data Integrator Login password entered during installation (see `Run the Installer`) User - database schema created for the master repository Password - database schema password created for the master repository Driver List - Select OracleJDBC Driver from the drop-down list Driver Name - oracle.jdbc.oracledriver Url - Set appropriate values based on your database details Work Repository - Select the Work Repository option, browse to select the work repository shown (for example, for Warehouse Integration loader, select OHF_WORK_REPOSITORY), and click OK.
	Click OK. The login name is created with the name specified in the previous step.
	Navigate to ODI > Connect > ODI Studio.
	Enter the following details: Login Name - Select OHF_REPOSITORY_LOGIN User - Supervisor Password - Provide the Oracle Data Integrator login password that was entered during installation (see `Run the Installer`).

Similarly, follow the above steps to create the login for the Terminology loaders, Common Data Mart loader, and Cohort Data Mart loader.

Parent topic: Installing the Data Management Assembly without Pre-Created User Schemas