8/8

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.0 Standard to OHSCDA 3.2"

3.1 Upgrading from OHSCDA 3.0 Standard to OHSCDA 3.2

The Installer automates the upgrade of the warehouse and the Informatica mappings. After running the Installer, to complete the upgrade from OHSCDA 3.0 to OHSCDA 3.2, perform the steps mentioned in Section 3.1.3, "Performing Next Steps" through Section 3.1.7, "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.1, "Technology Stack and System Requirements".

3.1.2 Running the Installer in Upgrade Mode

1. Run the OHSCDA Installer as described in Section 2.1.1, "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. Perform the steps listed in Section 3.1.4, "Migrating Data from OHSCDA 3.0 Standard to OHSCDA 3.2".

3. Perform the steps listed in the following sections:

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

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

     Note:

     If you are upgrading from OHSCDA 3.0 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.

   • Section 2.1.6, "Configuring Maps"

   • Section 2.1.7, "Creating Security Groups and Application Roles for OHSCDA"

3.1.4 Migrating Data from OHSCDA 3.0 Standard to OHSCDA 3.2

Perform the following steps to migrate data from OHSCDA 3.0 Standard to OHSCDA 3.2:

Note:

Data migration scripts are available in OCDA_HOME\oracle.pharma.ocda\OCDA_Standard\DataModels\Migration_Scripts3.0_to_3.2.zip.

1. Log on to the OHSCDA warehouse schema.

   <warehouse_user>/<warehouse_password>@<SID>
   

2. Create the following database links:

   • sc_dblink for Siebel Clinical source

     Example (SC):

     create database link <sc_dblink>connect to <sc_username>  identified by <sc_password>using '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=<portno>))(CONNECT_DATA=(SID=<sidname>)))';
     

   • if_dblink for InForm source

     Example (IF):

     create database link <if_dblink>connect to <inform_username>  identified by <inform_password>using '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=<portno>))(CONNECT_DATA=(SID=<sidname>)))';
     

3. Connect to the warehouse schema.

4. Execute the following migration scripts in the sequence as mentioned:

   1. drv_Migrate_CDA30_to_32_SC_Set1.sql

   2. drv_Migrate_CDA30_to_32_SC_Set2.sql

   3. drv_Migrate_CDA30_to_32_IF.sql

   4. drv_Migrate_CDA30_to_32_Cleanup.sql

5. Execute the following command:

   update  W_RXI_RACT_CATEGORY_D set SBR_FLG='N' where row_wid=-1;
   commit;
   

3.1.5 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 the what you had executed in OHSCDA 3.0.

3.1.6 Merging Changes into a New Oracle-supplied Repository

Each OHSCDA release, and some patches, includes a copy of the OHSCDA Repository. If you do modify your copy of the OHSCDA Repository, you must merge your changes into the Oracle-supplied Repository each time you receive a release or patch of OHSCDA that includes a repository. At upgrade time, use the OBIEE Merge Repository Wizard (accessed through File > Merge) in the Repository Administration Tool to merge your modified RPD with the Oracle-supplied RPD.

For information on comparing and merging Repositories, refer to Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11g.

3.1.7 Executing the ETL Load Plan

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