Install Oracle Database

To install Oracle Database 19.3.0, follow the instructions in the respective Oracle Database Installation Guide, making selections appropriate for TMS as noted in the following sections.

TMS requires:

  • Oracle Database Enterprise Edition

  • Oracle Database Text Option

Oracle Database Grid Infrastructure is optional.

You can configure database(s) as part of the database software installation or after, using the Database Configuration Assistant (DBCA).

Oracle Thesaurus Management System supports installation on either a Container Database (CDB) containing a Pluggable Database (PDB) or a non-CDB database.

For information on pluggable and container databases, see:

For an explanation of which options require an additional license, see the Database Licensing Information User Manual at https://docs.oracle.com/en/database/oracle/oracle-database/19/dblic/index.html.

For more information, see:

Install and Configure Oracle Database

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

When you configure the database, select the following options for Oracle Thesaurus Management System:

  • Custom Database template (recommended)

  • Oracle JVM (required)

  • Oracle Text (required for TMS only)

  • Check that required tablespaces exist, and have Autoextend on:

    • SYSTEM

    • TEMP

    • UNDOTBS1

    • USERS

    • SYSAUX

  • Initialization Parameters. Table 2-1 shows the required or recommended values for Oracle Thesaurus Management System. For parameters that accept a value within a range, the minimum values are given.

    Tip:

    Parameters are listed in alphabetical order. In the Database Configuration Assistant, you can click the Parameter column to display the parameters in the same order. You may need to select Advanced Parameters to see all of them.

    Note:

    If you make any changes to the initialization parameters, restart the database for the new settings to take effect.

    • Automatic Memory Management (recommended)

    • Sizing: From the Block Size drop-down, select 16384 Bytes.

    • Character Set: See Choose a Character Set.

The following get installed by default in Oracle Database 19.3.0 with the Custom Database template selected:

  • Distributed Database Option and Advanced Replication Option (only if you are using Oracle Clinical Distributed Study Conduct (Replication))

  • Oracle Partitioning

  • Oracle XML DB

  • Oracle Text, Java Virtual Machine (JVM), and Oracle XML DB are configured automatically if you select the Custom Database template.

Table 2-1 Required and Recommended Initialization Values in the init.ora File

Parameter Value Comments

COMPATIBLE

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

null

DO NOT set this value.

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.

NOTE: Do not include the EVENT parameter when you create the database. Once the database is created, you can add the EVENT parameter to the init.ora file.

JAVA_POOL_SIZE

50 MB

Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation.

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_DYNAMIC_SAMPLING

2 or greater

The default setting is 2. Oracle recommends using dynamic sampling for Batch Data Load temporary tables; see the Oracle Clinical Administrator's Guide.

OPTIMIZER_FEATURES_ENABLE

19.1.0.0

Acts as an umbrella for enabling a series of optimizer features based on an Oracle release number.

OPTIMIZER_ADAPTIVE_STATISTICS

FALSE

Controls adaptive statistics. Setting this parameter to false disables the following adaptive features: SQL plan directives, Statistics feedback for joins, and Adaptive dynamic sampling for parallel execution.

OPTIMIZER_ADAPTIVE_PLANS

FALSE

Controls adaptive plans. Adaptive plans are execution plans built with alternative choices that are decided at run time based on statistics collected as the query executes.

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.

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 (minimum)

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.

Modify the tnsnames.ora File on the Database Server

There is a tnsnames.ora file in at least two locations in the installation. Oracle recommends maintaining a master file and copying it to each location whenever you add a database. See Modify the tnsnames.ora File on the Application Server for the application server locations.

  1. Navigate to the tnsnames.ora file in the following directory on the database server:

    Oracle_Home/network/admin

  2. Enter a connect string for each database that matches the database's service name.
  3. If there are multiple Oracle homes, maintain tns entries for all databases in a central location; for example: /etc/tnsnames.ora.

Create the oinstall User Group

Use instructions in the Oracle Database 19.3.0 Installation Guide chapter "Configuring Users, Groups and Environments for Oracle Database."

  1. Check if the oinstall user group exists.
  2. If it does not exist, create it.

Check Required Tablespaces

Table 2-2 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 2-2 Required Tablespaces and Sizes

Tablespace Minimum Size

SYSTEM

900 MB

TEMP

100 MB

UNDOTBS1

700 MB

USERS

500 MB

SYSAUX

600 MB

Performance Tuning Step for Pluggable Databases

To prevent performance issues, specifically with accessing dba_synonyms view, take these steps. See My Oracle Support doc ID 2033658.1 for more information.

  1. Run the following statement:
    alter system set "_common_data_view_enabled" = false scope=both;
    
  2. Restart the database.