Skip Headers
Oracle® Healthcare Foundation Installation Guide
Release 7.1.1
E79438-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

7 Data Management Assembly for Oracle Data Integrator Upgrade

For a list of the supported upgrade paths, see Supported Upgrade Paths.

To upgrade the OHF Data Management Assembly for Oracle Data Integration (ODI), follow the instructions below:

  1. Check Prerequisites

  2. Prepare the Installer

  3. Run the Installer

  4. Check the Installation and Delete E$_tables

7.1 Check Prerequisites

Checkbox The user is familiar with Oracle Database (DB), ODI, and Linux OS.
Checkbox The OHF Data Model is installed.

Follow the instructions in Chapter 2, "Data Model Installation" or Chapter 2, "Data Model Installation".
Checkbox 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).
Checkbox The password expiry notification message does not display for the system user or existing schemas.
Checkbox The installer is run on the system where the ODI server is installed.
Checkbox 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.
Checkbox 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.
Checkbox Enough space is available in the installation directory and the Oracle Home directory.
Checkbox The Sqlplus utility is available on the installation server.
Checkbox The impdp utility is available on the repository database server.
Checkbox The installation user has read, write, and execute privileges to the $ODI_HOME/bin folder. The installer creates product specific files under this location.
Checkbox For remote installations, where the installation server and the ODI Repository Database server are 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.
Checkbox GLOBAL_NAMES database initialization parameter is set to false.
Checkbox Back up the following csv files under $ODI_HOME/bin if it exists:

  • bus_susp_day.csv

  • daylght_svngs_day.csv

  • hosp_hol_day.csv

  • time_odi.csv
Checkbox If the Terminology Loaders source folder is shared, make a back up 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.
Checkbox If any previous ETLs are in the failed status, make sure that they execute successfully before upgrading.
Checkbox Make sure that the data models are upgraded to OHF 7.1.1.
Checkbox The OUI displays default configuration schema (hmc) names. You must change these schema names to the existing hmc schema names.

The installer upgrades the configuration schemas to OHF 7.1.1.
Checkbox Back up the existing hmc schemas.

Note:

The installer auto-populates some of the user parameters and lets you edit them.

7.2 Prepare the Installer

Checkbox Extract the contents of the OHF media pack to your system.
Checkbox Navigate to the <media_pack_location>/ folder.
Checkbox Unzip the OHF_V711_Linux-x64.zip file where you want to launch the installer using the following command:

unzip -a OHF_V711_Linux-x64.zip
Checkbox Navigate to the Disk1/install folder.
Checkbox Change the protection on files as follows:

chmod 755 *

7.3 Run the Installer

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
Checkbox Welcome Click Next.
Checkbox Select a Product to Install Select the Oracle Healthcare Foundation Data Management Assembly for ODI 7.1.1.0.0 option.
Checkbox Specify Home Details Enter the installation home path.
Checkbox Verify Installation Prerequisites Verify if all the prerequisites are met before proceeding.
Checkbox Select the Oracle Home Configuration Specify the Oracle client home path.
Checkbox 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.
Checkbox Select Database Server for ODI Repository Schemas Select one of the following options for the ODI repository schemas:

  • If the ODI repository database server is on the installation server, select the Installation database server option.

  • Else, select the Remote database server option.
Checkbox 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

  • Mount path in 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 (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 privilege of 755 to the directory.
Checkbox 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 ODI repository schema creation.
Checkbox 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:

  • 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
Checkbox Specify ODI Supervisor Password Specify the supervisor password used for the ODI console login.
Checkbox 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.
Checkbox 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
Checkbox Specify Healthcare Data Model Schema Details Enter values for the following fields:

  • Enterprise schema name

  • Enterprise schema password.
Checkbox Specify Terminology Loader Details Enter values for the following fields:

  • Master repository schema name

  • Master repository schema password

  • Work repository schema name

  • Work repository schema password

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.
Checkbox Specify Warehouse Integration Loader Details Enter values for the following fields:

  • Configuration schema name

  • Configuration schema password

  • Master repository schema name

  • Master repository schema password

  • Work repository schema name

  • Work repository schema password

Enter the existing Configuration schema name to upgrade it.

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.
Checkbox Specify Healthcare Common Data Mart Loader Details Enter values for the following fields:

  • Configuration schema name

  • Configuration schema password

  • Master repository schema name

  • Master repository schema password

  • Work repository schema name

  • Work repository schema password

Enter the existing Configuration schema name to upgrade it.

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.
Checkbox Specify Healthcare Cohort Data Mart Loader Details Enter values for the following fields:

  • Master repository schema name

  • Master repository schema password

  • Work repository schema name

  • Work repository schema password

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.
Checkbox 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
Checkbox Specify the Tablespace Details Specify the tablespace names for repository schemas. The installer creates these tablespaces if they do not exist.

  • Repository schema default tablespace name

  • Repository schema temporary tablespace name
Checkbox 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.
Checkbox 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.
Checkbox Verify Configuration Parameters Click Next.
Checkbox Summary Click Install.
Checkbox End of Installation Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer.

7.4 Check the Installation and Delete E$_tables

Checkbox Review the generated installation log files for errors. For details, see Installation Log Files.
Checkbox Contact Oracle support, if necessary, to resolve any errors.
Checkbox Delete all E$_ tables under HCD schema.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us