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

Note:

You must upgrade OHSCDA 3.1 to OHSCDA 3.1.1 before upgrading to OHSCDA 3.2.

3.1 Upgrading from OHSCDA 3.1.1 Standard to OHSCDA 3.2

The Installer automates the upgrade of the warehouse. After running the Installer, to complete the upgrade from OHSCDA 3.1.1 to OHSCDA 3.2, perform the steps mentioned in Section 3.1.3, "Performing Next Steps" through Section 3.1.6, "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. Perform the steps listed in Section 3.1.4, "Migrating Data from OHSCDA 3.1.1 Standard to OHSCDA 3.2".

3. Perform the steps listed in the following sections:

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

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

     Note:

     If you are upgrading from OHSCDA 3.1.1 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 Release 1.

   • Section 2.9, "Configuring Maps"

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

3.1.4 Migrating Data from OHSCDA 3.1.1 Standard to OHSCDA 3.2

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

1. Log on to the OHSCDA warehouse schema.

   <warehouse_user>/<warehouse_password>@<SID>
   

2. Create the following database links:

   • oc_dblink for Oracle Clinical source

     Example (OC):

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

   • 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 ocda_if_src  identified by ocda_if_src
     using '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=<portno>))(CONNECT_DATA=(SID=<sidname>)))';
     

3. Connect to the warehouse schema.

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

   Note:

   Driver scripts are available in <OCDA_HOME>\OCDA_ODI\Database\Migration_Scripts3.1.1_to_3.2.zip.

   1. drv_Migrate_CDA311_to_32_SC_Set1.sql

   2. drv_Migrate_CDA311_to_32_SC_Set2.sql

   3. drv_Migrate_CDA311_to_32_IF.sql

   4. drv_Migrate_CDA311_to_32_OC.sql

   5. drv_Migrate_CDA311_to_32_Cleanup.sql

5. Connect to the Siebel Clinical source schema and execute ocda_sc_del_trigger.sql located at <OCDA_HOME>\OCDA_Common\OCDA_Common_Scripts\Delete_Script.

3.1.5 Upgrading ODI Topology and Work Repository

Note:

Before upgrading the ODI work repository and topology to OHSCDA 3.2, back up the complete topology and work repository.

For information on how to back up, see Oracle Data Integrator User's Guide.

1. Perform smart export of customizations you want to apply.

   Note:

   Before exporting the customizations, Oracle recommends that you organize all customizations into a single folder with a unique object name. For example, prefix the object name with cust_.

   For information on how to smart export, see Oracle Data Integrator User's Guide.

2. Upgrade the topology and work repository to OHSCDA 3.2.

   To do so, perform steps 3 through 24 in Section 2.4, "Setting Up Oracle Data Integrator".

3. Perform smart import of the customizations which you had exported in earlier step.

4. Update the load plan with required customizations.

3.1.6 Executing the ETL Load Plan

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