Installing the Data Management Assembly with Pre-Created User Schemas

Check Prerequisites

-	Steps
	The user is familiar with Oracle Database (DB), Informatica, and Linux OS.
	The Oracle Healthcare Foundation Data Model is installed. Follow the instructions in `Data Model Installation` or `Data Model Upgrade`.
	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.
	The Informatica domain is running and no user is connected to the Informatica Admin Console.
	Informatica 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).
	You can connect the database using EZCONNECT syntax. For example, sqlplus user/password@hostname:port/service name.
	The password expiry notification message does not display for the system user or pre-created schemas.
	The installer is run on the system where the Informatica 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.
	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 installation user has read, write, and execute privileges to the $INFA_HOME/server folder. The installer creates product-specific folders and parameter files under this location.
	For remote installations, where the installation server and the Informatica Repository Database are on different machines, make sure that: The remote database server directory is mounted to the installation server with appropriate read and write privileges. The remote directories are accessible after mounting from the installation server. The Linux user of the remote server, who executes the Oracle process, has privilege 755 for the directory (datapump). The Oracle user has privilege for the mount path directory. If the repository DB is on an Exadata machine, the repository DB single node (the node which is mounted) TNSENTRY should be added to the tnsnames.ora file on the installation server. After installation, revert TNSENTRY to the original entry.
	GLOBAL_NAMES database initialization parameter is set to false.
	Back up the following csv files under `$INFORMATICA_HOME/server/infa_shared/SrcFiles` if it exists: `bus_susp_day.csv` `daylght_svngs_day.csv` `hosp_hol_day.csv` `time_am.csv` `time_pm.csv`
	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.

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

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
infarep_ts	Yes	Default tablespace for the Repository schema
infarep_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

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

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
wil_rep_82	Warehouse Integration Loader Repository schema	infarep_ts	infarep_temp
hcd_rep_82	Healthcare Common Data Mart Repository schema	infarep_ts	infarep_temp
cdm_rep_82	Healthcare Cohort Data Mart Repository schema	infarep_ts	infarep_temp

Parent topic: Installing the Data Management Assembly with 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 `<media_pack_location>/Disk3/stage/Components/oracle.hsgbu.hc.dma.infa/8.2.2.0.0/1/DataFiles/Expanded/filegroup1` directory.
	Unzip the dma_infa_master_install.zip file.
	Navigate to the dma_infa_master_install/hmc_infa_install/ directory.
	Connect to the system user and execute the following scripts: `@infa_hdi_user_privilege.sql HDI_SCHEMA_NAME` `@infa_hmc_user_privilege.sql WIL_HMC_SCHEMA_NAME HCD_HMC_SCHEMA_NAME` `@infa_rep_user_privilege.sql WIL_INFA_REP_DB_USER HCD_INFA_REP_DB_USER CDM_INFA_REP_DB_USER`
	Navigate to the media_pack_location/Disk1/install folder.
	Change the protection on files as follows: `chmod 755 *`

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

Run the Installer

Start the Oracle Universal Installer by running the following command:

If the Informatica repository database or the Oracle Healthcare Foundation data model database is on the database instance of the installation server, execute:
sh runInstaller.sh -local dba_tasks=false
If the Informatica repository schemas to be created are 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 Informatica 8.2.2.0.0 option.
	Select the Informatica Home Location	Enter or select the installation home path.
	Verify Installation Prerequisites	Verify if all the prerequisites are met before proceeding.
	Oracle Home Configuration	Specify the Oracle client home path.
	Specify the Informatica Home Location.	Specify the Informatica home location. The Informatica home should be one level above the /server directory. For example, `path/Informatica/961/`.
	Specify the Informatica Shared Path	The Informatica Shared Path should be one level above the SrcFiles folder. For example, path/Informatica/961/server/infa_shared. Note: Before starting installation ensure that all required subfolders are created under infa_shared folder. For example: `SrcFiles`, `TgtFiles`, `SessLogs`, `WorkflowLogs`, and so forth.
	Select Database Server for Informatica Repository Schemas	Select one of the following options for the Informatica repository schemas: If the Informatica repository database server is on the installation server, select the Installation database server option. For remote installations, select the Remote database server option.
	Specify Mount Path Details (applicable only for remote installations)	Enter the following mounted directory configuration details in which the remote server directory is mounted: Mount path in the repository database server - Remote server path Mount path in the installation server - Path on the installation server where the mounting is performed 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 (datapump) directory of the remote database server should be mounted to the installation server with appropriate read and write privileges for the IMPDB utility (folder with dba group). Make sure that the remote directories are accessible after mounting from the installation server. If the remote server mounted path is displayed as /, provide the absolute mounted path of the remote server. The remote server Linux user that executes the Oracle process must have minimum privileges of 755 to the directory.
	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 Select this database instance for repository schema creation If you select Yes, the installer uses the same Data Model database instance for Informatica repository schema creation.
	Specify Informatica 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 number Service name
	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 Repository name Repository schema name Repository schema password Provide the pre-created hmc schema details. If you enter an existing repository name, the installer removes the repository and the corresponding integration service (Is_Repository name). It creates a repository service (Repository name) and integration service (Is_Repository name). If you enter an existing repository schema name, the installer overwrites the content with the new one, and you will lose the existing objects.
	Specify Healthcare Common Data Mart Loader Details	Enter values for the following fields: Configuration schema name Configuration schema password Repository name Repository schema name Repository schema password Provide the pre-created hmc schema details. If you enter an existing repository name, the installer removes the repository and the corresponding integration service (Is_Repository name). The installer creates a repository service (Repository name) and integration service (Is_Repository name). If you create an existing repository schema name, the installer overwrites the content with the new one, and you will lose the existing objects.
	Specify Healthcare Cohort Data Mart Loader Details	Enter values for the following fields: Repository name Repository schema name Repository schema password The configuration schema is not required for CDM. If you enter an existing repository name, the installer removes the repository and the corresponding integration service (Is_Repository name). The installer creates a repository service (Repository name) and integration service (Is_Repository name). If you enter an existing repository schema, the installer overwrites the content with the new one, and you will lose the existing objects.
	Specify Informatica Domain Details	Specify the following parameters: Domain name Domain code page ID Node name License name Informatica host name Informatica port number Informatica administrator user name Informatica administrator password Contact your Informatica Administrator for the Domain Code Page ID and provide a valid Code Page ID. Make sure that the code page is compatible with the domain code page for creating the Integration Service. For a domain compatible code page, see any existing and active integration service code pages from the Informatica admin console. A list of sample code pages and their IDs are as follows: US-ASCII (ID 1) - 7-bit ASCII Latin1 (ID 4) - ISO 8859-1 Western European JapanEUC (ID 18) - Japanese Extended Unix Code (including JIS X 0212) UTF-8 (ID 106) - Unicode Transformation Format, multibyte MS932 (ID 2024) - MS Windows Japanese, Shift-JIS MS1252 (ID 2252) - MS Windows Latin1 (ANSI), superset of Latin1
	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 with 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 with Pre-Created User Schemas

Revoke Privileges

After the Data Management Assembly for Informatica installation, run the following scripts from System user:

@OHF_Install_Home/dma_infa_master_install/hmc_infa_install/dma_directory_drop.sql

@OHF_Install_Home/dma_infa_master_install/hmc_infa_install/dma_revoke_privilege.sql WIL_INFA_REP_DB_USER HCD_INFA_REP_DB_USER CDM_INFA_REP_DB_USER

where,

OHF_Install_Home - Oracle Healthcare Foundation installation home directory

WIL_INFA_REP_DB_USER - Warehouse integration loader repository schema name

HCD_INFA_REP_DB_USER - Healthcare common data mart loader repository schema name

CDM_INFA_REP_DB_USER - Cohort data mart loader repository schema name

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