Installing the Data Management Assembly without Pre-Created User Schemas

Complete the following:

• Check Prerequisites
  
• Prepare the Installer
  
• Run the Installer
  
• Check the Installation
  

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 12.2.0.1.0 or higher 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.2.0.1.0 or higher, 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 7.3 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.
	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.
	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 privileges 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.

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 OHF_V80_Linux-x64.zip file where you want to launch the installer using the following command: unzip -a OHF_V80_Linux-x64.zip
	Navigate to the Disk1/install folder.
	Change the protection on files as follows: chmod 755 *

Run the Installer

Start the Oracle Universal Installer by running the following command:

• If the Informatica repository schemas to be created are on the database instance of the installation server, execute:

  sh runInstaller.sh -local

• If the Informatica 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 Informatica 8.0.0.0.0 option.
	Specify Home Details	Enter or select the installation home path.
	Verify Installation Prerequisites	Verify if all of the prerequisites are met before proceeding.
	Oracle Home Configuration	Specify the Oracle client home path.
	Select 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/.
	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 the minimum privilege 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 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 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 Service name System user password
	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 The installer creates a configuration schema if it does not exist. Provide the new Repository schema name.
	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 The installer creates a configuration schema if it does not exist. Provide the new Repository schema name. If you provide 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). The installer creates a repository schema if it does not exist in the database. If you enter an existing repository schema, the installer overwrites the content with the new one, and you will lose all 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. Provide the new Repository schema name.
	Specify Tablespace Details (if prompted)	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 Tablespace Details (if prompted)	Specify the tablespace names for repository schemas. The installer creates these tablespaces if they do not exist in the database. Repository schema default tablespace name Repository schema temporary tablespace name
	Specify Tablespace Location for Configuration Schema (if prompted)	Specify the tablespace location for the Configuration schema. The location should be present in the Oracle Healthcare Foundation 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 Schema (if prompted)	Specify the tablespace location for the repository schemas. When the repository database is not on the installation server, you must enter the location manually. The location should be present on the repository database server with write privileges.
	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.

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.