Upgrade the Oracle Clinical Database Server

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

The Oracle Universal Installer performs the following operations:

• Creates the Oracle Clinical directory structure
• Installs the Oracle Clinical database server
• 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

For more information, see:

• Gather Required Information on Oracle Clinical Database Server for Windows
  
• Upgrade the Oracle Clinical Database Server Software
  
• Review the Log Files
  
• Oracle Clinical Database Server Directory Structure for Windows
  
• Perform Post-Upgrade Tasks
  

Gather Required Information on Oracle Clinical Database Server for Windows

You must have the following information ready to enter in the Installer screens:

1. Home Details: The ORACLE_HOME location where you installed Oracle Database 19c (19.3.0.0.0).

   For example: drive:\app\oracle\product\19.3.0.0\dbhome_1

2. OPA Home: The directory where Oracle Clinical will be installed. Oracle recommends:
   drive:\opapps
3. SAS View: The directory where Oracle Clinical will generate SAS views. Oracle recommends:
   drive:\opapps\sas_view
4. Oracle Wallet location and password: The Installer uses these to create the database Wallet in the location you specify. The database Wallet stores the password for:
   • The OCPSUB proxy account, which is used for database access for parametrized submission (PSUB) jobs. Its credentials are created in the Wallet on the database server during Oracle Clinical database installation.

     Note:

     If you have already created a Wallet through a previous installation of Oracle Clinical 5.0 or higher, you can continue using it instead of creating a new one by entering the location and password for the existing Wallet.

Upgrade 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 and extract the .zip file for your database 19c if you have not already done so.
3. Run the following file as an administrator:

   Disk1\install\setup.exe

   The Installer opens to the Welcome screen.

   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.
4. In the Select a Product to Install page, select OC Server for Windows 5.4.1.0.x.
5. Follow the instructions on the installation screens, providing the information you assembled in Gather Required Information on Oracle Clinical Database Server for Windows.

Review the Log Files

1. Review the generated log files located at:
   \Oracle\Inventory\logs

   For example:

   C:\Program Files\Oracle\Inventory\logs

Oracle Clinical Database Server Directory Structure for Windows

The Installer creates the following directory structure:

OPA_HOME
      \bin
      \xmltemp
      \oc
         \541
            \bin      (Executables)
            \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)
            \tools    (Miscellaneous tools)
  

Note that OPA_HOME refers to the root installation directory of the Oracle Life Sciences products, which were formerly known as Oracle Pharmaceutical Applications (OPA). You specify the root installation directory when you install the Oracle Clinical database server. Typically, you specify the path to the opapps login directory, for example, drive:\opapps.

Perform Post-Upgrade Tasks

To complete the upgrade of Oracle Clinical database server on a Windows computer, perform the following tasks:

• Limit Permissions on the XMLTEMP Folder
  
• Review the opa_settings.bat File
  

Limit Permissions on the XMLTEMP Folder

By default, a Windows installation grants read and write privileges to the XMLTEMP database folder to everyone. To reduce security risks, limit permissions on the XMLTEMP folder for all Windows database server installations.

1. Use Windows Explorer to locate the XMLTEMP folder in the OPA_HOME directory.
2. Right-click on the XMLTEMP folder, and then select Properties from the menu.
3. Click the Sharing tab, then click Advanced Sharing.
4. Select the Share this folder check box to enable sharing with other users on your network.
5. Click Permissions.
6. Give Read and Write (Change) permissions to user oracle.
7. Click OK to save your changes and close the Permissions dialog box.
8. Click OK to save your changes and close the Advanced Sharing dialog box.
9. Click Close to close the Properties dialog box.

Review the opa_settings.bat File

On Windows systems, configurations are defined in the opa_settings.bat file. This file contains the commands to set environment variables at startup and execution of the PSUB service.

1. Review the opa_settings.bat file in the following directory:
   Drive:\opapps\bin
2. Adjust the default values, if necessary.
   See the Oracle Clinical Administrator's Guide for a list of the settings and for information about changing, adding, and verifying values.

   Note:

   • The db_env_setting records in opa_settings.bat define a default value for particular environment variables that are set when the application calls opa_setup. You can override the default values for all databases or for a particular database.
   • See Choose a Character Set for important information.
   • NLS_DATE_FORMAT must be set to DD-MON-RRRR. It is possible to override this setting for display in RDC Onsite, the Patient Data Report, and Oracle Clinical data entry, but the value in opa_settings must be DD-MON-RRRR.