Install the Oracle Clinical Database Server

This section describes how to install and set up the Oracle Clinical database server.

The Installer performs the following operations:

  • Creates the Oracle Clinical directory structure (see Oracle Clinical Database Server Directory Structure for UNIX for details)
  • Installs the Oracle Clinical database server
  • Builds the executables
  • Sets permissions on the directories
  • Creates the environment setup files
  • Modifies the environment setup files
  • Creates the Oracle Wallet to store credentials for OCPSUB and RXC_DISC_REP
  • Creates the directory for storing the SAS files

In this section:

Gather Required Information

Have the following information ready to enter in the Installer:

  1. Home Details: The OPA_HOME location where you installed Oracle Database 12c Release R2 (12.1.0.2) or ORACLE_HOME location where you installed Oracle Database 19c (19.3.0.0).

    For example:

    • For Oracle Database 12c: /pharm/home/opapps
    • For Oracle Database 19c: root:/app/oracle/product/19.3.0.0/dbhome
  2. If you are installing in a RAC installation, the names of all RAC nodes where the same product(s) should be installed.
  3. OPA Home: the directory where Oracle Clinical will be installed; Oracle recommends:
    /pharm/home/opapps
  4. Owner of Oracle Clinical Server Code must be opapps
  5. Location for files oratab, tnsnames; for example:
    • /etc
    • $ORACLE_HOME/network/admin
  6. RXC_USER: Choose directory for RXC_USER; Oracle recommends:
    /pharm/home/opapps
  7. Oracle Wallet location and password: The Installer uses these to create the database Wallet in the location you specify. If you are upgrading, you can enter the existing location and password.
    The database Wallet stores the password for two accounts:
    • The OCPSUB proxy account, which is used for database access for parametrized submission (PSUB) jobs. If your installation includes multiple databases using either replication or RAC, each database needs an OCPSUB account. Its credentials are created in this Wallet by the Installer.
    • The RXC_DISC_REP account. If you use disconnected replication you must insert credentials for this account manually. See Set Up Disconnected Replication (Optional).

Prepare to Install the Oracle Clinical Database Server Software

  1. Log in to the database server as the opapps user.
  2. Change the primary group of the opapps account to the group that owns the Oracle Inventory:

    Note:

    Make a note of the current group so that you can set it back after the installation.

    newgrp inst_group

    where inst_group is the name of the group that owns the Oracle Inventory. You specified the name during the Oracle Database installation. Typically, this user group is oinstall. See Create the opapps Account and Add It to Groups.

    This temporary change is necessary so that the Installer can update the Oracle Home.

  3. Set the X Window display output to the IP address of your local computer. Use the standard format for IP addresses.
    5.1: Removed "and add ":0" to the end of the address."

    For example:

    setenv DISPLAY 123.45.67.89

  4. Locate the Oracle Clinical software in the directory in the staging area on the database server where you downloaded it; see Download the Software.
  5. Perform one of the following:
    • For Oracle Database 12c: Open the ldflags file at root: app/oracle/product/12.1.0.2/lib and add the -lnnz12 flag.
    • For Oracle Database 19c: Open the ldflags file at root: app/oracle/product/19.3.0.0/lib and add the -lnnz19 flag.

Install the Oracle Clinical Database Server Software

  1. Log in to the server computer using the opapps account.
  2. In the staging area, locate the directory where you downloaded Oracle Clinical (see Download the Software) and extract the .zip file if you have not already done so.

    Note:

    If you are installing on Oracle Database 12c, use the 12c installer. If you are installing on Oracle Database 19c, use the 19c installer
  3. Navigate to this location:

    server_code_platform\Disk1\install

  4. Change protections on all files to 755:

    chmod 755 *

  5. Run one of the following commands, depending on whether or nor you are using Oracle Real Application Cluster (RAC):
    • For a non-RAC installation:
      ./runInstaller
      

      Or, if the database server has multiple Oracle Homes, then enter:

      ./runInstaller -invPtrLoc ORACLE_HOME/oraInst.loc
      

      For example:

      ./runInstaller -invPtrLoc /u01/app/oracle/product/121010_qa/oraInst.loc
      
    • For a RAC installation:
      ./runInstaller -local
      

      Or, if the database server has multiple Oracle Homes, then enter:

      ./runInstaller -local -invPtrLoc ORACLE_HOME/oraInst.loc
      

      For example:

      ./runInstaller -invPtrLoc /u01/app/oracle/product/121010_qa/oraInst.loc
      

      This ensures that the installation is performed only on the local node.

    Note:

    See Use the Silent Installer (Optional) for instructions for running the Installer as a file with pre-entered parameter values.

    Note:

    Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Clinical or Oracle Clinical Remote Data Capture (RDC) Onsite.
  6. In the Select a Product to Install page, select OC Server for UNIX 5.2.2.0.x.
  7. Follow the instructions on the installation screens, providing the information you assembled in Gather Required Information.
  8. You can review the progress of the installation:
    1. Open another terminal session as the opapps user.
    2. To review the relinking progress, run the following:

      tail -f $OPA_HOME/oc/522/relink_rxc.log

    3. Open the installActionstimestamp.log in the oraInventory/logs directory.

Save the Installation Information

  1. Save the following information displayed in the Installer. You need it for several post-installation tasks.
    • Location of the OPA_HOME directory
    • Location of the OPA_HOME/bin directory
    • Name of the code environment

Review the Installation Log Files

  1. Review the generated installation log files located at:
    $ORACLE_BASE/oraInventory/logs

    For example:

    /u01/app/oraInventory/logs

Work with Oracle Health Sciences Support, if necessary, to resolve any errors.

Oracle Clinical Database Server Directory Structure for UNIX

The Installer creates the following directory structure for an Oracle Clinical database server on UNIX:

OPA_HOME
      /bin
      /xmltemp
      /oc
         /522
            /bin      (Symbolic links to the executables)
            /common   (Common files)
            /dcd      (Data Collection Definition)
            /des      (Design)
            /dm       (Data Management)
            /dx       (Data Extract)
            /glib     (Global Library)
            /install  (Install and upgrade scripts)
            /log      (PSUB log files)
            /lr       (Lab Ranges)
            /patch    (Patches to Oracle Clinical)
            /pd       (Procedure Definition)
            /psub     (Parameterized Submission process)
            /release  (Server code release marker)
            /sec      (Security tools)
            /tools    (Miscellaneous tools)

Remove Group Privileges from this Session

  1. To reset the privileges for the opapps account, enter the following command:
    newgrp group

    where group is the name of your original primary group for the opapps account.