Perform Database Post-Installation Tasks

To complete the installation of your Oracle Clinical database, perform the following tasks:

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:

  1. Connect to the database as any user that has ALTER DATABASE privileges.
  2. Enter the following command:

    alter database set time_zone='tzname_value’;

    For example:

    alter database set time_zone='US/Eastern’;

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 to pin the database packages.

To pin the database packages located on a Windows server:

  1. Log in to the Windows server computer as an administrator.
  2. Set the Windows environment:

    set p1=database

    set p2=522

    opa_setup

    where database is the name of this database instance, and 522 is the alias for the version of Oracle Clinical.

  3. Change to the drive where Oracle Clincal is installed. For example:
    cd %RXC_INSTALL%
  4. Start an SQL*Plus session, and connect to the database in the RXC account:
    sqlplus rxc/password
  5. Run the rxcdbinit.sql script to pin the database packages:
    start rxcdbinit.sql

If you are continuing the installation, note that you perform the next task in this environment.

Set Up Disconnected Replication (Optional)

Do the following only if you plan to use disconnected replication:

Check Tablespace Size

Installing Oracle Clinical creates the RXC_DISC_REP user account to manage disconnected replication. DISC_REP_DATA is the default tablespace for RXC_DISC_REP.

If you use disconnected replication:

  1. Increase the size of the DISC_REP_DATA tablespace to fit the amount of replicated data.

    For more information about disconnected replication, see the Oracle Clinical Administrator's Guide.

Create a Wallet Credential for the RXC_DISC_REP Database User

The system stores these credentials in the same Wallet as the one created for OCPSUB.

  1. Log in as opapps.
  2. Set environment variables.
    set p1=database_connect_string
    set p2=522
    opa_setup
    
  3. Create an alias for the disconnected replication wallet alias in tnsnames.ora. The disconnected replication wallet alias is the name of the database appended with:
    _disc.

    For example, if the database name is ny123x, the tnsnames entry would look something like:

    ny123x, ny123x_disc, ny123x.world, ny123x.domain.com =  (DESCRIPTION=
        (ADDRESS=(PROTOCOL=tcp)(HOST=myhost.us.example.com)(PORT=1124))
        (CONNECT_DATA=(service=ny123x))
    

    See Modify the tnsnames.ora File on the Database Server.

  4. For the disconnected replication wallet alias, enter tnsping wallet_alias to test that it returns success. For example:
    tnsping ny123x_disc
    
  5. Create the credentials for the disconnected replication wallet alias and account.
    mkstore -wrl %walletpath% -createCredential wallet_alias  rxc_disc_rep rxc_disc_rep_password
    

Test Wallet Connection for RXC_DISC_REP

  1. Set tns_admin:
    set TNS_ADMIN=%walletpath%
    
  2. For the disconnected replication wallet alias run sqlplus /@wallet_alias. for example:
    sqlplus /@ny123x_disc 
    

    The connection should be a success.

  3. Run show user
    This should display the rxc_disc_rep user.

Add Reference Codelist Value

In the OCL_STATE reference codelist:

  1. Add a value called DISC_REP_WALLET. See the Oracle Clinical Administrator's Guide for more information.
  2. Enter the wallet_alias you just created as the long value.

Consider Implementing Partitioning

  1. Partition the Oracle Clinical RESPONSES table, which contains all patient data entered for all studies in an Oracle Clinical installation.
    See the Oracle Clinical Administrator's Guide for more information.