Upgrade Oracle Clinical Databases
This section describes how to run Installer to upgrade each database.
Note:
If you are upgrading to a RAC environment, you must import your database(s) to a single RAC node before running the Installer to upgrade it.If you are upgrading your database using export and import, do the following:
For more information, see:
- Gather Required Information
- Run the Installer
- Review the Log Files for Upgrade Results and Errors
- Compile Invalid Objects
- Perform Post-Upgrade Database Tasks
Parent topic: Upgrade Oracle Clinical Database Components on UNIX
Gather Required Information
Make sure you have the information below before you start the Installer. The information is not in quite the same order as displayed in the Installer for upgrading databases but it is the same information.
You have the option to skip the upgrade but rerun all recreatable object scripts (views, packages, functions, and so on) against the database.
Parent topic: Upgrade Oracle Clinical Databases
Run the Installer
To start the upgrade of an Oracle Clinical database on a UNIX database server:
Parent topic: Upgrade Oracle Clinical Databases
Review the Log Files for Upgrade Results and Errors
The Installer generates numerous log files and saves the files to the following location:
$ORACLE_BASE/oraInventory/logs
For example:
/u01/app/oraInventory/logs
The rest of this section describes finding errors in the log files (as logfile
), and descriptions of known errors.
For more information, see:
Find Errors
To simplify reviewing upgrade results:
Parent topic: Review the Log Files for Upgrade Results and Errors
Reencrypt Account Passwords
If the installation fails to reencrypt any password, it does not list them as errors. Instead, it lists them in the log files in a section titled, "Passwords for the following schema accounts were not converted."
Normally, if you are upgrading from 5.0 or higher and have not changed the location of the Secret Store directory, you do not need to rerun set_pwd.
Parent topic: Review the Log Files for Upgrade Results and Errors
Compile Invalid Objects
When upgrading the Oracle Clinical database, the Installer calls and runs compile_all_invalid.sql to compile invalid objects. However, to reduce the time required to run the script and to ensure that the installation completes in a timely manner, the compile_all_invalid.sql script does not compile these invalid objects:
- Packages owned by RXC_PD (that is, the validation and derivation procedures that you have created). The package name starts with RXC_PD.
- Data Extract views that belong to a study. In the database, these views are owned by an internal user whose name starts with study_name$.
- Objects owned by any ops$ account. The compile_all_invalid.sql script ignores objects if the owner has a dollar symbol ($) in the name.
To view the list of invalid objects:
To compile the remaining invalid objects, use instructions in the following sections:
Parent topic: Upgrade Oracle Clinical Databases
Compile PL/SQL Code Before Running the Script
If you have any PL/SQL code referenced from your generated procedures, ensure that these objects are valid before running the compile_schema_invalid.sql script.
For example, if you created a schema named X that contains all the PL/SQL code referenced from your generated procedures, first run:
compile_schema_invalid.sql X
Then run:
compile_schema_invalid.sql RXC_PD
Parent topic: Compile Invalid Objects
Perform Post-Upgrade Database Tasks
Note:
Make sure that you have installed the latest CPU certified for release 5.4 before performing any of the instructions below. For information on the latest certified CPU, see Oracle Health Sciences Applications Supported Technology Stack (Document ID 180430.1) on My Oracle Support > section Oracle Health Sciences Critical Patch Updates (CPU) Notes in the PDF file.Perform each of the following 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
Parent topic: Upgrade Oracle Clinical Databases
Set the Database Time Zone
The Oracle Clinical Remote Data Capture Onsite (RDC Onsite) application uses the dbtimezone value for internal calculations when the Display timestamps in local timezone preference is set.
Oracle recommends setting time zone to a named location rather than a numeric offset so that standard and daylight time adjustments are made automatically.
You can find valid named location strings in the V$TIMEZONE_NAMES view. For example, to find a time zone in the United States, enter the following query:
SELECT distinct tzname FROM V$TIMEZONE_NAMES WHERE tzname like 'US/%'
To set the time zone in the database:
Parent topic: Perform Post-Upgrade Database Tasks
Pin Database Packages
To improve performance, some of Oracle Clinical's packages are pin-able packages; Pinning allocates a stable memory location so that a package cannot be subjected to being swapped out of memory. Oracle Clinical provides the rxcdbinit.sql script in the rxc_install directory to pin the database packages.
To pin the database packages located on a UNIX server:
Parent topic: Perform Post-Upgrade Database Tasks
Migrate Users
The requirements for users who need to run PSUB jobs changed in Release 5.0.
Parent topic: Perform Post-Upgrade Database Tasks
Run Scripts to Gather Schema Statistics for the Oracle Database Optimizer
After upgrading to Oracle Clinical 5.4 and setting initialization parameter optimizer_features_enable (see Set Initialization Parameters):
For more information on gathering statistics and using dynamic sampling to improve performance, see the Oracle Clinical Administrator's Guide.
Parent topic: Perform Post-Upgrade Database Tasks
Regenerate DCI Forms to Access from Microsoft Edge Browser
For information, see the Oracle Clinical Remote Data Capture Onsite Administrator's Guide.
Parent topic: Perform Post-Upgrade Database Tasks