3 Upgrading Oracle Health Sciences Clinical Development Analytics

This chapter provides procedures that explain how to upgrade OHSCDA. It includes the following section:

• Section 3.1, "Upgrading from OHSCDA 3.2 to OHSCDA 3.2.1"­­

3.1 Upgrading from OHSCDA 3.2 to OHSCDA 3.2.1

The Installer automates the upgrade of the warehouse and the Informatica mappings. After running the Installer, to complete the upgrade from OHSCDA 3.2 to OHSCDA 3.2.1, perform the steps mentioned in Section 3.1.3, "Performing Next Steps" through Section 3.1.5, "Executing the ETL Load Plan".

Note:

OHSCDA 3.2 is certified on Oracle Database 12.1.0.2.0. For detailed certification information, see Finding Certification Information.

3.1.1 Prerequisites

For information, see Section 1.2, "Technology Stack and System Requirements".

3.1.2 Running the Installer in Upgrade Mode

1. Run the OHSCDA Installer as described in Section 2.2, "Running the OHSCDA Installer".

3.1.3 Performing Next Steps

After running the installer, perform the following steps:

1. To enable multi-byte character support, execute the Database Migration Assistant for Unicode (DMU) on the CDA warehouse schema.

   For information, see Oracle Database Migration Assistant for Unicode Guide.

2. Merging your RPD and Webcatlog Changes into the 3.2.1 Oracle-supplied OBIEE RPD and Webcatlog.

   If you are upgrading from OHSCDA 3.2 and have modified the OBIEE repository or Web Catalog, merge your changed objects into the 3.2.1 Oracle-supplied OBIEE RPD and Webcatlog.

   For more information, refer to Oracle® Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11g.

3. Perform the steps listed in the following sections:

   • Section 2.6, "Emplacing the OHSCDA Help and Image Files"

   • Section 2.7, "Preparing the OBIEE Web Catalog and Repository for OHSCDA"

     Note:

     If you are upgrading from OHSCDA 3.2 and have modified the OBIEE repository or Web Catalog, merge these objects. For more information, refer to Oracle® Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11g.

3.1.4 Importing the OHSCDA Warehouse Application Metadata into the DAC Repository

1. Unzip <ocda_home>\ oracle.pharma.ocda.standard\DAC_Code\CDA_Warehouse.zip into a local folder.

2. Start the Data Warehouse Administration Console (DAC) client.

3. From the Tools menu, select DAC Repository Management, and then select Import.

4. Click Change import/export folder to navigate to the folder where you unzipped CDA_Warehouse.zip.

5. Click OK to display the Import dialog box.

6. Select the following categories of metadata you want to import: Update existing records, Logical, Overwrite log file, and User Data.

7. Deselect the System check box.

8. Click OK.

9. Enter the verification code and OK in the secondary window that is displayed after the import.

10. Select one of the following execution plan and click Build.

    • CDA - Complete Warehouse

      Note:

      Complete warehouse has InForm source extractions ETL added.

    • CDA - Siebel Clinical Warehouse

    • CDA - Oracle Clinical Warehouse

    • CDA - InForm Warehouse

11. Execute the execution plan which you built in the earlier step.

    Note:

    The execution plan must be same as what you had executed in OHSCDA 3.2.

3.1.5 Executing the ETL Load Plan

For information, see Oracle Health Sciences Clinical Development Analytics Administrator's Guide.