Table of Contents

• Title and Copyright Information
• Preface
  • Audience
  • Change Log
  • Documentation accessibility
  • Related resources
  • Diversity and Inclusion
  • Access to Oracle Support
• 1 Prepare to Upgrade Oracle Clinical
  • Supported Upgrade Paths
  • Check Installation Documentation
    • My Oracle Support Articles
  • Architecture
  • Software Requirements
    • Database Tier Operating System Requirements
  • Supported Configurations with Oracle Data Guard and RAC
    • Supported Configurations with Oracle Real Application Clusters (RAC)
      • Node 1: Install and Set Up Everything Required for Oracle Clinical
      • Node 2: Install the Minimum Required as a RAC Node
      • Node 3: Install Everything Required for Oracle Clinical as Backup
    • Supported Configurations with Oracle Data Guard
  • Download the Software
    • Create Staging Areas
    • Download the Oracle Clinical 5.4 Media Pack
    • Download Patches from My Oracle Support
    • Download Oracle Java Development Kit
    • Download the Java Runtime Environment
    • Download Adobe Reader
    • Download JSpell (Optional)
  • Use the Silent Installer (Optional)
  • Choose a Character Set
  • Apply the Latest Oracle Clinical Patches
  • Integrating Oracle Clinical with Other Products and Options
    • Oracle Clinical Remote Data Capture Onsite
    • Oracle Thesaurus Management System
    • Oracle Life Sciences Data Hub
    • SAS
    • Custom Applications for Oracle Clinical
• 2 Upgrade to Release 4.6.6 (If Needed)
  • Upgrade to Release 4.6.2
  • Upgrade to Release 4.6.6
  • Upgrade to Release 5.2.2
• 3 Upgrade Oracle Database Server Code and Databases
  • Stop Processes
    • Stop PSUB
    • Prevent Access to Oracle Clinical Databases
  • Back Up Your Database(s)
  • Upgrade Oracle Database
    • Upgrade the Database to Oracle Database 19c (19.3.0)
      • Upgrade in Place from Oracle Database 11.2.0.4 or 12.1.0.2 to 19c
      • Clone Your Database on a Oracle Database 19c
  • Set Initialization Parameters
  • Create a Secret Store Directory
• 4 Upgrade Oracle Clinical Database Components on UNIX
  • Upgrade the Oracle Clinical Database Server
    • Grant Access for the opapps Account
    • Set Permissions
      • Change Permissions for Running oraenv Script
      • Grant Access to the ORACLE_HOME Directory
      • Set Permissions for the Oracle Inventory Directory
    • Check for an ORA-29548 Error
    • Gather Required Information for Oracle Clinical Database Server
    • Prepare to Install the Oracle Clinical Database Server Software
    • Upgrade the Oracle Clinical Database Server Software
    • Perform Post-Upgrade Tasks
      • Complete the Setup of the opapps Account
      • Limit Permissions on the XMLTEMP Folder
      • Review the opa_settings File
      • Check for Oracle Clinical Databases on a UNIX Server
  • Upgrade Oracle Clinical Databases
    • Gather Required Information
    • Run the Installer
    • Review the Log Files for Upgrade Results and Errors
      • Find Errors
      • Reencrypt Account Passwords
    • Compile Invalid Objects
      • Compile PL/SQL Code Before Running the Script
      • Run the compile_schema_invalid.sql Script
    • Perform Post-Upgrade Database Tasks
      • Set the Database Time Zone
      • Pin Database Packages
      • Migrate Users
      • Run Scripts to Gather Schema Statistics for the Oracle Database Optimizer
      • Regenerate DCI Forms to Access from Microsoft Edge Browser
  • Preserve Your Database Customizations
• 5 Upgrade the Oracle Clinical Database Server on Windows
  • Upgrade the Oracle Clinical Database Server
    • 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
      • Limit Permissions on the XMLTEMP Folder
      • Review the opa_settings.bat File
  • Upgrade Oracle Clinical Databases
    • Check for an ORA-29548 Error
    • Gather Required Information for Oracle Clinical Database
    • Run the Installer
    • Review the Log Files for Upgrade Results and Errors
      • Find Errors
      • Reencrypt Account Passwords
    • Compile Invalid Objects
      • Compile PL/SQL Code Before Running the Script
      • Run the compile_schema_invalid.sql Script
    • Perform Post-Upgrade Database Tasks
      • Set the Database Time Zone
      • Pin Database Packages
      • Migrate Users
      • Run Scripts to Gather Schema Statistics for the Oracle Database Optimizer
      • Regenerate DCI Forms to Access from Microsoft Edge Browser
• 6 Set Up the Parametrized Submission Process
  • Set Up PSUB
    • Create Directories and Enter Values in OCL_STATE Local Reference Codelist
    • Enable Users to Submit PSUB Jobs
    • Enable opapps to Use the at Command (UNIX Only)
    • Set Up Active Directory (Windows Only)
  • Start and Stop the PSUB Service
    • Start and Stop PSUB Automatically in UNIX and Windows
      • Start PSUB Automatically in UNIX
      • Stop PSUB Automatically in UNIX
      • Start PSUB Automatically in Windows
        • Create a System Environment Variable
        • Schedule the Batch File and Testing the Setup
        • Create a Batch File
        • Add a Shortcut
    • Start PSUB Manually in UNIX
    • Start PSUB Manually in Windows
  • Test the PSUB Installation
  • Customize the PSUB Service
  • Run PSUB in a RAC Environment
  • Manually Start the Advanced Queue Process (If You Cloned a Database)
• 7 Set Up SAS
  • Set Up SAS Data Extract
    • Give Users Access to the opapps Account
    • Add the opapps Account to the oclsascr User Group
    • Give opapps Access to the Directory Specified in the RXC_SAS_VIEW Environment Variable
    • Set Up SAS User Authentication and Set OCL_STATE Reference Codelist Values
    • Changes in SAS Data Extract Implementation
  • Install SAS on a UNIX Computer
    • Modify SAS 9.4 and opa_settings on UNIX
      • Prepare the SAS Template File
    • Install SAS on the Same UNIX Computer as Oracle Clinical
      • Set REMOTE_OS_AUTHENT to FALSE
      • Set Up a SAS Connection
    • Install SAS on a Different UNIX Computer from Oracle Clinical
      • Establish the Connection to SAS on a Different Computer
      • Set Up SAS Security on a Different Computer
      • Configure Private and Public Keys for Using SSH with SAS
  • Install SAS on a Windows Computer
    • Modify the opasettings.bat file
    • Install SAS on the Same Windows Server Computer
      • Set REMOTE_OS_AUTHENT to FALSE
      • Set System Path
      • Edit the SAS Config File and Grant Permissions
    • Install SAS on a Different Windows Server Computer
      • Set REMOTE_OS_AUTHENT to FALSE
      • Enable Executing Data Extract PSUB Jobs
      • Edit the SAS Config File and Grant Permissions
      • Set Values in OCL_STATE Reference Codelist
• 8 Upgrade and Configure the Oracle Application Tier
  • Before You Start
    • Identify a Single Account to Perform All Application Tier Installation Tasks
  • Gather Required Information
  • Restart Computer and Stop All Servers
  • Install Oracle Java Development Kit
  • Install Oracle WebLogic Server 12.2.1.4
  • Install the Oracle Fusion Middleware Infrastructure Software
  • Install the Oracle Forms and Reports Servers
  • Run Pre-Upgrade Readiness Check
  • Upgrade the Domain Schema
  • Run the Reconfiguration Wizard
  • Upgrade the Forms Server
• 9 Upgrade the Oracle Clinical Front End
  • Gather Required Information for Oracle Clinical Front End
  • Install the Oracle Clinical Front End Components
    • Review the Installation Log Files
    • Set Remote Method Invocation (RMI) JDBC Security to Secure
    • Restart the Computer
    • Add WebLogic Data Sources If Using Multiple Databases
  • Make the Java Runtime Environment Available for Download
  • Make the Oracle Clinical PDF Plug-in Available to Users
  • Share the RDC Directory for Image Access
    • Share the Directory Across Multiple Computers
    • Set Up the Image Directory on a Single Computer
  • Install and Configure JSpell Spell Checker SDK (Optional)
    • Install JSpell on Oracle Application Server
    • Install the JSpell WAR File on the WebLogic Server
    • Update the mod_wl_ohs.conf File for JSpell
    • Stop and Start Oracle HTTP Server (OHS)
    • Test the JSpell Servlet
    • Update the formsweb.cfg File for JSpell
    • Update the Windows System Registry for JSpell
    • Test JSpell in the Graphic Layout Editor
  • Verify and Fix Environment Variables
    • Check Values
    • Correct Values
  • Set Up Automatic Startup
    • Create boot.properties
    • Increase the Delay for Auto Start OPADomain and FRDomain
    • Set Up Scripts to Execute Automatically at Machine Startup
    • Test Autostart
  • Start Servers Manually
    • Start the FRDomain Node Manager
    • Start the FRDomain Admin Server
    • Start the Forms Server
    • Start the Reports Server
    • Start the OPADomain Node Manager
    • Start the OPADomain Admin Server
    • Start the Managed Server of OPADomain
    • Start the OHS Server
  • Verify the Application Tier Installation
  • Stop Servers
    • Stop the Forms Server
    • Stop the Reports Server
    • Stop the FRDomain Admin Server
    • Stop the Managed Server of OPADomain
    • Stop the OPADomain Admin Server
• 10 Upgrade the Oracle Clinical Reports Server
  • Gather Required Information for Oracle Clinical Reports Server
  • Restart the Computer
  • Start the WebLogic FRDomain Admin Server
  • Install the Oracle Clinical Reports Server
    • Review the Installation Log File
  • Restart the Computer
  • Set Up the Reports Server for Access and File Viewing
    • Create the Reports Server Root Directory
    • Share and Grant Access to Each Reports Server Root Directory
    • Configure the Reports Server and Forms Server for DCI Form Generation
    • Configure the Reports Server to Send Output to a Printer
  • Add the Reports Server to the Database Reference Codelist
  • Test the Reports Server Installation
  • Set Up Automatic Startup of Services
• 11 Set Up Clients
  • Configure Personal Firewall
  • Use Safari on an iPad
  • Set Up for Proxy Usage on Fully Qualified Application Tier Names
  • Download Required Applications for Clients
    • Download the Java Runtime Environment
    • Configure Java Security Settings for Oracle Clinical
    • Download the Oracle Clinical PDF Plug-in
    • Download Adobe Reader
  • Map Network Drive for Image Browsing
  • Enable Report Generation from the Command Line
  • Log in to the Application