4 Creating an Oracle Clinical Database

This chapter describes how to create a new Oracle database for use with Oracle Clinical.

Oracle Database 11g and the Oracle Clinical Database Server installations must be complete before you can install the Oracle Clinical database. (See the Oracle Database 11g documentation and Chapter 2 for UNIX instructions or Chapter 3 for Windows instructions.)

This chapter includes the following topics:

• Section 4.1, "Reviewing Prerequisites"

• Section 4.2, "Reviewing Database Requirements and Recommendations"

• Section 4.3, "Installing Oracle Clinical 4.6 Database Objects"

• Section 4.4, "Performing Post-Installation Database Tasks"

• Section 4.5, "Completing File Viewing Tasks in the Database"

• Section 4.6, "Adding the Reports Server to the Database Reference Codelist"

4.1 Reviewing Prerequisites

Before you begin a database installation:

• Review Chapter 1, "Preparing to Install Oracle Clinical" to ensure that your system is up to date.

• Check My Oracle Support for the latest changes to the installation instructions.

• Review the Configuring Oracle Clinical Remote Data Capture Onsite 4.6 for Performance and Scalability white paper (Article ID 873743.1), which is available on My Oracle Support.

4.2 Reviewing Database Requirements and Recommendations

Before you install the Oracle Clinical database component, review the requirements and recommendations — such as SID names, tablespace sizes, memory management, and initialization parameters — listed in this section.

Note:

Repeat these instructions for each new database you create.

4.2.1 Start with a New Database Instance

Oracle recommends that you set up a new database instance so that neither Oracle Clinical 4.6 nor its installation process interferes with other applications. However, you can install Oracle Clinical on an existing database instance.

4.2.2 Decide on Lowercase or Uppercase SID Name for UNIX

On UNIX systems, when you define the Oracle Clinical SID name, consider these options:

• If you define the Oracle Clinical SID name using lowercase letters only, there are no conflicts in the Oracle Clinical Data Extract module.

• If you define the Oracle Clinical SID name using uppercase letters, you must create symbolic links. These links are required so that the path to the SAS_VIEW directory is recognized. For information on creating these links, see the Oracle Clinical Administrator's Guide.

4.2.3 Check Required Tablespaces

Table 4-1 lists the tablespaces, along with their minimum size, required for Oracle Clinical. Make sure the database contains these tablespaces. The best practice is to create them with the Autoextend On option, to avoid running out of space.

In addition, you may need to increase the minimum sizes for your installation.

Table 4-1 Required Tablespaces and Sizes

Tablespace	Minimum Size
SYSTEM	900 MB
TEMP	100 MB
UNDOTBS1	700 MB
USERS	500 MB
SYSAUX	500 MB

4.2.4 Use the Database Configuration Assistant

To create a new database, use the Database Configuration Assistant. For instructions about the Database Configuration Assistant, see the Oracle Database 11g documentation, including online help and the Oracle Database Installation Guide 11g Release 1 (11.1) for the appropriate operating system.

Note:

The Database Configuration Assistant prompts you to "Keep the enhanced 11g default security settings (recommended)." Information on security settings is included in the Oracle Database 2 Day + Security Guide 11g Release 1 (11.1).

4.2.5 Select Required Components

When you create an Oracle Clinical database, select the following mandatory components:

• Oracle Text

• Oracle JVM

• Oracle XML DB

4.2.6 Use Automatic Memory Management

Oracle recommends that you use Oracle Database 11g's Automatic Memory Management feature for a new or an upgraded Oracle Clinical database.

In addition, download the following white paper from My Oracle Support for more information on memory management:

Title:	Configuring Oracle Clinical Remote Data Capture Onsite 4.6 for Performance and Scalability
Article ID:	873743.1

    

4.2.7 Review opa_settings

Review the entries in the opa_settings file. Ensure that the default settings are applicable to the installation or create specific settings applicable to the specific database. See Section 2.7, "Performing Post-installation Tasks" for more information.

Note:

The default settings for all databases or the specific settings for a particular database, such as NLS_LANG, must be correct in the opa_settings file.

4.2.8 Set Initialization Parameters

Table 4-2 lists the required and recommended init.ora parameter settings for Oracle Clinical. For those parameters that accept a value from within a range, the values in the table are minimum values.

Tip:

Table 4-2 arranges the parameters in alphabetical order. In the Database Configuration Assistant, you can select the Parameter column to sequence the parameters in the same order.

Note:

If you make any changes to the initialization parameters, be sure to stop and restart the database in order to acquire the new parameter settings.

Table 4-2 Required and Recommended init.ora Parameter Settings

Parameter	Value	Comments
COMPATIBLE	11.1.0.7.0	Specifies the release with which the Oracle server must maintain compatibility.
DB_BLOCK_SIZE	16384 bytes	You cannot change this value after you create the database.
DB_CACHE_SIZE	150 MB	Recommended value for 50 to 60 concurrent users. Adjust this value according to your organization's needs.
DB_DOMAIN	company.com	Make this value the same as your company domain name.
DB_FILES	200	Oracle adds needed space to the control files up to the number specified in the DB_FILES parameter.
EVENT	31151 trace name context forever, level 0x100	Required for HTML generation.
JAVA_POOL_SIZE	50 MB	Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation. (Set greater than 150 MB with Oracle AERS, minimum.)
JOB_QUEUE_PROCESSES	10	Developer-specific parameter. You can change the value of this parameter after installation.
LARGE_POOL_SIZE	50 MB	Recommended value for 50 to 60 concurrent users.
MEMORY_MAX_TARGET	1000 MB (minimum)	Adjust this value according to your organization's needs.
MEMORY_TARGET	1000 MB (minimum)	Adjust this value according to your organization's needs.
NLS_DATE_FORMAT	DD-MON-RRRR (default value)	Determines the format in which client applications running on the Windows server transfer date information to and from the database. The format must specify the year as RRRR.
NLS_LENGTH_SEMANTICS	BYTE	The CHAR value for this parameter is not supported.
OPEN_CURSORS	800 or greater	You can change the value of this parameter after installation.
OPTIMIZER_FEATURES_ENABLE	9.2.0	Acts as an umbrella for enabling a series of optimizer features based on an Oracle release number. Oracle Clinical uses the optimizing features of Oracle9i.
OPTIMIZER_MODE	CHOOSE	If you run Oracle Clinical's statistics-gathering scripts, the CHOOSE value sets Oracle9i's Optimizer to apply the execution plan that best minimizes response time. See the Oracle9i Concepts Guide and the Oracle9i Tuning Guide for more information. (CHOOSE is the default value when you specify 9.2.0 as the value of OPTIMIZER_FEATURES_ENABLE.)
OS_AUTHENT_PREFIX	"OPS$"	Enter the double quotes symbol (").
PGA_AGGREGATE_TARGET	200 MB	Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation.
REMOTE_LOGIN_PASSWORDFILE	EXCLUSIVE	The database must be set up to use password file authentication.
REMOTE_OS_AUTHENT	TRUE	If you intend to use Oracle Clinical and have SAS on a different computer, DX SAS jobs fail unless you set this parameter to TRUE. However, REMOTE_OS_AUTHENT is an obsolete parameter. When you start up a database that has this setting, Oracle Clinical displays the following warning: ORA-32004: obsolete and/or deprecated parameter(s) specified. ORACLE instance started. You can safely ignore this warning.
SEC_CASE_SENSITIVE_LOGON	FALSE	Lets you enter passwords without case sensitivity.
SESSIONS	500 or greater	You can change the value of this parameter after installation.
SGA_MAX_SIZE	600 MB (minimum)	Recommended value for 50 to 60 concurrent users. Adjust this value according to your organization's needs.
SGA_TARGET	600 MB (minimum)	Recommended value for 50 to 60 concurrent users. Adjust this value according to your organization's needs.
SHARED_POOL_SIZE	150 MB	Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation.
UNDO_MANAGEMENT	AUTO	Specifies which undo space management mode the system uses. When set to AUTO, the instance starts in Automatic Undo Management (AUM) mode.
UTL_FILE_DIR	opa_home\ xmltemp	Specifies each directory you access. If you share this environment with Oracle Clinical or Oracle AERS, you must specify entries to support Oracle Clinical PDF layout generation and Oracle AERS. If this environment is exclusively a Thesaurus Management System environment, you do not have to set this parameter. For Windows environments, samples of the valid syntax are as follows: UTL_FILE_DIR=c:\e2b\import UTL_FILE_DIR=c:\opapps\xmltemp For UNIX environments, UTL_FILE_DIR requires an entry with two specified paths: one with and one without a trailing slash. Add these lines before any other UTL_FILE_DIR entries: UTL_FILE_DIR=/usr/opapps/oc/xmltemp/ UTL_FILE_DIR=/usr/opapps/oc/xmltemp

4.2.9 Modify tnsnames.ora

Add an entry to the tnsnames.ora file for the database. Add the tnsnames entry to file tnsnames.ora on any existing Oracle Clinical 4.6 Forms Servers or Reports Servers. The tnsnames.ora entry must match the Oracle SID.

4.3 Installing Oracle Clinical 4.6 Database Objects

Follow these instructions to add Oracle Clinical database objects to this database.

4.3.1 Transfer the Oracle Clinical 4.6 UNIX Media

If you are installing on a UNIX computer and you have not yet transferred the Database Server software from the media pack to this computer, see Section 2.6.2, "Transfer the Oracle Clinical 4.6 Database Server Software" for installation instructions.

4.3.2 Customize the Installer

Before you install database objects, you may want to modify some of the default SQL scripts used by the Installer.

4.3.2.1 Edit Tablespace Sizes

The Installer creates several new tablespaces with default sizes. To create larger databases, edit the following files:

UNIX:	OPA_HOME/oc/46/install/opadba2.sql OPA_HOME/oc/46/install/rxcdba2.sql
Windows:	OPA_HOME\oc\46\install\opadba2.sql OPA_HOME\oc\46\install\rxcdba2.sql

You can either increase the size of the data files or remove the autoextend clause from the data files. The default value is an autoextend of 1M and an unlimited maximum size.

4.3.2.2 Edit the User Account Creation Script

The Installer prompts to create accounts in this database. If you select Yes, the Installer runs a script that creates default guest accounts. Prior to running the Installer, edit the rxcdba4.sql script to customize the accounts that get created and their default settings:

UNIX:	OPA_HOME/oc/46/install/rxcdba4.sql
Windows:	OPA_HOME\oc\46\install\rxcdba4.sql

See the Oracle Clinical Administrator's Guide for more information about enrolling users.

4.3.3 Start the Installer

Follow these instructions to set the correct installation environment and start the Installer. Where the platforms have different instructions, there are separate sections.

The Installer acts in two phases. In the first phase, the Installer collects information about your system. During this phase, you can move back and forward through the screens, revising your entries. During the second phase, the Installer runs the scripts to set up the Oracle Clinical software according to the information you provided in the first phase.

4.3.3.1 Starting the Installer on a UNIX Server

To start the Installer on a UNIX server:

1. Log in to the server computer as the opapps user.

2. Change the primary group of the opapps account to the group that owns the Oracle Inventory:

   newgrp inst_group

   where inst_group is the name of the group that owns the Oracle Inventory. You specified the name during the Oracle Database 11g installation. Typically, this user group is oinstall.

   This temporary change is necessary so that the Installer can update the Oracle inventory.

3. Set the X Window display output to the IP address of your local computer. Use the standard format for IP addresses, and add ":0" to the end of the address. For example:

   setenv DISPLAY 123.45.67.89:0

4. Navigate to this location in the folder where you extracted the server code:

   server_code_platform\Disk1\install

5. Change protections on files to 755.

   chmod 755 *

6. Start the Universal Installer:

   ./runInstaller

7. Follow the instructions on the installation screens. For additional information on each screen, see Section 4.3.4, "Attend to the Oracle Clinical Database Installation Screens."

4.3.3.2 Starting the Installer on a Windows Server

To start the Installer on a Windows server:

1. Log in to the server computer using an account with system administrator privileges.

2. Insert Disk V17174-01 of the Oracle Clinical 4.6 and Oracle Thesaurus Management System 4.6.1 Media Pack.

3. Locate and execute the setup.exe file:

   oc\server_code\win\install\setup.exe

   The Installer opens to the Welcome screen.

4. Follow the instructions on the installation screens. For additional information on each screen, see Section 4.3.4, "Attend to the Oracle Clinical Database Installation Screens."

4.3.4 Attend to the Oracle Clinical Database Installation Screens

This section describes the Installer's prompts for installing an initial Oracle Clinical database. The instructions are the same for all platforms.

Welcome

The Installer opens to the Welcome screen. Click Next.

Select a Product to Install

Select OC Database Install 4.6.0.0.XX (where XX is the build number). Click Next.

Specify Home Details

Select or enter the ORACLE_HOME location, which is where you installed Oracle Database 11g.

Choose Directory OPA Home

Check that the displayed value is the correct location of the Oracle Clinical Database Server installation. If not, click Browse and locate the Oracle Clinical server installation. Click Next.

Choose Directory SAS view

Specify the directory to create for locating Data Extract files. (See Chapter 8, "Setting Up SAS" for more information.) Click Next.

Choose Database Enter connect string for database to be installed

Enter the Oracle SID. Click Next.

Choose Directory for data tablespace datafiles

Enter the path for the directory where the Installer creates the data tablespace datafiles. The installer validates that the specified directory exists on the server.

In addition, the Installer creates the tablespaces with the default sizes defined in the opadba2.sql and rxcdba2.sql scripts. To increase the size of the initial database, edit these scripts before running the installer. For more information, see Section 4.3.2, "Customize the Installer."

Click Next.

Choose Directory for index tablespace datafiles

Enter the path for the directory where the Installer creates files to hold tablespaces for Oracle Clinical indexes. The installer validates that the specified directory exists on the server.

In addition, the Installer creates the tablespaces with the default sizes defined in the opadba2.sql and rxcdba2.sql scripts. To increase the size of the initial database, edit these scripts before running the installer. For more information, see Section 4.3.2, "Customize the Installer."

Click Next.

Enter Password for SYS

Enter and confirm the password for the SYS user to perform database administration activities during the installation. The Installer validates the password against the database before performing the install. Click Next.

Enter Password for SYSTEM

Enter and confirm the password for the SYSTEM user to perform database administration activities during the installation. The Installer validates the password against the database before performing the install. Click Next.

Note:

In the installation screens that follow, the Installer prompts for the passwords for many user accounts. Note that:

• The Installer encrypts and stores the passwords in the database.

• Passwords cannot contain the following characters: { } | ; @

• Passwords cannot contain spaces.

Choose Password RXC_MAA

Enter and confirm the password for the account that creates and maintains data access accounts during data extract.

Click Next.

Choose Password for RXC_PD

Enter and confirm the password for the account that creates stored procedures during validation procedure definition. Click Next.

Choose Password for RXC_REP

Enter and confirm the password for the account that manages distributed study conduct. Click Next.

Choose Password for RXC_DISC_REP

Enter and confirm the password for the account that manages disconnected replication. Click Next.

Choose Password for RXCLIN_MOD

Enter and confirm the password for the database role that controls write access to the Oracle Clinical database. Click Next.

Choose Password for BC4J_INTERNAL

Enter and confirm the password for the account that stores product objects. Click Next.

Choose Password for OPA

Enter and confirm the password for the account that stores product objects. Click Next.

Choose Password for RXC

Enter and confirm the password for the account that stores product objects. Click Next.

Choose Password for TMS

Enter and confirm the password for the account that stores product objects. Click Next.

Choose Password for RXA_DES

Enter and confirm the password for the account that stores product objects. Click Next.

Choose Password for RXA_LR

Enter and confirm the password for the account that stores product objects. Click Next.

Enter Value Database Seed Number

Each database in an Oracle Clinical installation (or group of databases that are replicating with each other) must have a unique seed starting number. The seed number must be an integer between 1 and 99. Click Next.

Enter Database Configuration Parameters

Enter the full name of the host where the database is located, and enter the SQL*Net port used to connect to this database. The port number is specified in the tnsnames.ora file for this database. Click Next.

Enter Location a unique code for this location

Enter a unique code for the location of this database. The location code cannot exceed 15 characters, and is converted to all uppercase characters.

The default value is the value of ORACLE_SID. Click Next.

Enter Global Library Location a unique code for the Global Library location

Enter a unique code for the location that owns the Global Library. The location code cannot exceed 15 characters, and is converted to all uppercase characters.

The default value is the location code entered in the previous screen. Click Next.

Yes/No Do you want to create accounts in this database?

This setting controls whether the Installer runs the rxcdba4.sql script and creates the user accounts defined in the script. Prior to running the Installer, you can edit the script to customize the accounts that get created and their default settings. See Section 4.3.2, "Customize the Installer" for more information.

You can also create user accounts after the installation. Click Next.

Yes/No Ignore Tablespace Creation Errors

This setting controls whether the Installer ignores errors that occur when creating the tablespaces. Tablespace creation can fail for several reasons.

The default value is No. In general, you do not want the Installer to ignore tablespace creation errors. For example, you want the Installer to report an error if there is not enough space to create the tablespace.

On the other hand, if you are reinstalling into an existing Oracle Clinical database, the tablespace creation fails because the tablespace already exists. In this case, you do not need to know about the error.

Click Next.

Information

This screen reports that the Installer will start an SQL*Plus session to complete the database installation. The screen confirms the name of the database installation, the location of the scripts used for the installation, and the location of the log file that you can view for the progress of the installation. Click Next.

Summary OC Database Install 4.6.0.0.XX (Note: XX is the build number.)

This screen provides information about the global settings, languages, space requirements, and products for this installation.

Click Install. The Installer starts an SQL*Plus session to complete the installation.

The Installer configures the installed database to work with the Oracle Clinical 4.6 Database Server code by adding an entry to the following file:

UNIX:	opapps/bin/opa_settings
Windows:	opapps\bin\opa_settings.bat

End of Installation

The Installer displays this screen when it finishes. This screen provides information about the installation, including whether the processes completed without errors, the name of the PSUB service created, and the location of the log file for your review.

Note:

You may need to modify or create some additional default entries in the opa_settings file for this database. See the Oracle Clinical Administrator's Guide for more information.

4.3.5 Remove Group Privileges from this Session (UNIX Only)

Recall that before you started this installation on UNIX, you changed the primary group of the opapps account to the group that owns the Oracle Inventory (see Section 4.3.3.1). This temporary change was necessary so that the Installer could update the Oracle inventory.

To reset the privileges for the opapps account, enter the following command:

newgrp group

where group is the name of your original primary group for the opapps account.

4.4 Performing Post-Installation Database Tasks

Follow the instructions in this section to complete your database installation.

4.4.1 Review the Log Files for Installation Errors

The Installer generates numerous log files and saves the files to the following location:

UNIX:	OPA_HOME/oc/46/install
Windows:	OPA_HOME\oc\46\install

Check the following log files for error messages and invalid objects. In each file name, database is the database SID.

• oclinst_database.log

• reall_database.log

• oclconfig_database.log

• flt_seeddata_database_timestamp.log

• html_dialg_templ_database_timestamp.log

• html_blob_seeddata_database_timestamp.log

• xmlp_clob_seeddata_database_timestamp.log

• xml_clob_seeddata_database_timestamp.log

• compile_all_invalid_database.log

• load_olsardcstatemachine_jar_database.log

• install_database_timestamp.log

• opaconnectcheck_system_database.log

4.4.2 Change Default Passwords

To improve security and to protect system access:

• Change the default passwords of all schemas and roles

• Use the set_pwd utility to encrypt the passwords in the database

See the Oracle Clinical Administrator's Guide for details about setting up user accounts and roles, changing passwords, and encrypting passwords.

4.4.3 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.

Note:

Oracle Clinical 4.6 pins additional packages. The new packages are included in the updated rxcdbinit.sql script.

4.4.3.1 Pin UNIX Database Packages

To pin the database packages located on a UNIX server:

1. Log in to the UNIX server computer as opapps.

2. Set the UNIX environment:

   opa_setup database 46

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

3. Change to the RXC_INSTALL directory:

   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:

   start rxcdbinit.sql

   The script pins the database packages and exits upon completion.

   Note:

   You must reexecute this script each time you restart the database. Consider creating an entry in the database startup script that runs rxcdbinit.sql.

4.4.3.2 Pin Windows Database Packages

To pin the database packages located on a Windows server:

1. Set the Windows environment:

   set p1=database

   set p2=46

   opa_setup

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

2. Change to the drive where Oracle Clinical 4.6 is installed. For example:

   X:

3. Start an SQL*Plus session, and connect to the database in the RXC account:

   sqlplus rxc/password

4. Run the rxcdbinit.sql script to pin the database packages:

   start %RXC_INSTALL%\rxcdbinit.sql

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

4.4.4 Configure and Start the PSUB Process

The Parameterized SUBmission (PSUB) process schedules reports and batch processing. Note that:

• You start one PSUB process for each Oracle database instance supporting an Oracle Clinical installation.

• Each database instance can have only one PSUB process.

• You must locate PSUB on the same computer as the database installation.

4.4.4.1 Starting PSUB on UNIX

To start PSUB as a UNIX process:

1. Log in to the server as rxcprod.

2. Enter the following command:

   start_psub database code_environment

   For example:

   start_psub prod 46

4.4.4.2 Changing the Startup of the PSUB Service on Windows

To change the startup of the PSUB service on Windows:

1. Log in as Administrator.

2. Set the PSUB service parameters:

   1. Open the Administrative Tools control panel.

   2. Double-click Services.

   3. From the list of services in the Services dialog box, double-click the name of the database for this service. It is in this form:

      PSUB Service database

   4. For Startup type, select Manual.

   5. Click the Log On tab.

   6. For Log on as, select This account and then enter RXCPROD in the field.

      (The task of creating the RXCPROD account occurs during the installation of the Database Server. See Section 3.2.1, "Create the RXCPROD Account" for more information).

   7. In the Password and Confirm Password fields, enter the RXCPROD password.

   8. Click OK to close the dialog box.

3. Exit from the Services dialog box.

4. Log off this Administrator session. You start PSUB from the RXCPROD account.

4.4.4.3 Configuring Windows Registry Setting for PSUB

To be able to start PSUB on Windows, the OSAUTH_PREFIX_DOMAIN setting in the Windows System Registry must be set to FALSE. Otherwise, the operating system authentication prefix is OPS$hostname\ instead of OPS$.

The OSAUTH_PREFIX_DOMAIN registry setting is located at:

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HomeX\

where HomeX is the Home number of your Oracle Database 11g installation.

4.4.4.4 Starting the PSUB Service on Windows

To start PSUB as a Windows process:

1. Log in to the computer as user RXCPROD. (You set up the PSUB service to start as the RXCPROD user, but in Windows you can start the service when logged on as another user.)

2. Set the PSUB service parameters:

   1. Open the Administrative Tools control panel.

   2. Double-click Services.

   3. From the list of services in the Services dialog box, double-click the name of the database for this service. It is in this form:

      PSUB Service database

   4. Enter values for the Log On parameters:

      database code_environment [verbose | noverbose] value-of-RXC_ROOT

      For example: prod 46 verbose c:\\opapps\\oc\\46

      Note:

      If your entry requires a backslash (\), you must enter two (\\). Alternatively, you can enter the path using single forward slashes, for example, c:/OPA_HOME/oc/46.

3. Click Start.

4. Exit from the Services dialog box.

4.4.4.5 Configuring PSUB for Automatic Startup

By default, the PSUB service does not start automatically when you restart a server computer. However, you can configure the PSUB service to start automatically. For information about managing the PSUB process and defining automatic startup parameters, see the Oracle Clinical Administrator's Guide.

4.4.4.6 Changing PSUB Job Numbering

You can change Oracle Clinical's default job numbering algorithm. See the Oracle Clinical Administrator's Guide for details.

4.4.5 Enroll Users

See the Oracle Clinical Administrator's Guide for more information about enrolling users.

4.4.6 Check Disconnected Replication Tablespace

If you implement disconnected replication, you might need to increase the size of the DISC_REP_DATA tablespace to fit the amount of replicated data. Installing Oracle Clinical 4.6 creates the RXC_DISC_REP user account to manage disconnected replication. DISC_REP_DATA is the default tablespace for RXC_DISC_REP. For more information about distributed study conduct and disconnected replication, see the Oracle Clinical Administrator's Guide.

4.4.7 Review Optimization Statistics

Oracle Clinical provides scripts that analyze the storage characteristics of tables and indexes, and compute statistics. As you accumulate statistics for this database, run these scripts periodically. See the Oracle Clinical Administrator's Guide, Appendix E, "Collecting Statistics for Optimization" for more information.

4.4.8 Consider Implementing Partitioning

Oracle Clinical supports partitioning of the responses data entry table. Before implementing partitioning to responses data for your Oracle Clinical 4.6 installation, consider your requirements and options in migrating from a non-partitioned, pre-Oracle Clinical 4.0 responses table to Oracle Clinical 4.6.

To migrate your data from a non-partitioned responses table into a partitioned one, first backup your existing responses table, indexes, and data.

4.5 Completing File Viewing Tasks in the Database

You must install an Oracle Clinical Forms Server and Reports Server before you can continue. See "File Viewing" in the Oracle Clinical Administrator's Guide for more information.

4.6 Adding the Reports Server to the Database Reference Codelist

Before performing this step, you should have installed, or at least determined where you intend to install one, many, or all of the Reports Servers that you access from this database. For each Reports Server that you add and that you want to access from this database, you must repeat the steps in this section.

To set the Reports Server values:

1. Start Oracle Clinical.

2. Navigate to Admin, Reference Codelist, and then Local Codelist to open the Maintain Reference Codelists form.

3. Query for REPORT_SERVER in the Name field.

4. Complete the Short Value and Long Value fields as follows:

   • For each Short Value listed in Table 4-3, enter in the Long Value field the connection string of the Reports Server that you want to use as the default for the specified function.

   • To add additional, non-default Reports Servers, add rows to the reference codelist and specify a unique name in the Short Value field and the connection string in the Long Value field.

     Table 4-3 REPORT_SERVER Reference Codelist Values

     Short Value	Enter in Long Value Field
     REPORT_SERVER	The connection string for the Reports Server you want to use as the default for Oracle Reports.
     JOB_SET_SERVER	The connection string for the Reports Server you want to use as the default for job sets.
     PSUB_SCHEDULER	The connection string for the Reports Server you want to use as the default for PSUB jobs.

     
     

5. Click Save.