Install Oracle Database 19.3.0
To install Oracle Database 19.3.0, follow instructions in the Oracle Database Installation Guide, making selections appropriate for Oracle Clinical as noted in the following sections.
You can configure database(s) as part of the database software installation or after, using the Database Configuration Assistant (DBCA).
Oracle Clinical supports installation on either a Container Database (CDB) containing a Pluggable Database (PDB) or a non-CDB database.
Note:
For information on pluggable and container databases, see:
- Oracle Database New Features Guide for 19c at https://docs.oracle.com/en/database/oracle/oracle-database/19/newft/index.html
- Oracle Database Concepts for 19c at https://docs.oracle.com/en/database/oracle/oracle-database/19/cncpt/index.html
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
- Modify the tnsnames.ora File on the Database Server
- Create the oinstall User Group
- Check Required Tablespaces
Parent topic: Install Oracle Database
Install and Configure Oracle Database
Oracle recommends that you set up a new database instance so that neither Oracle Clinical nor its installation process interferes with other applications. However, you can install Oracle Clinical on an existing Oracle database.
When you configure the database, select the following options for Oracle Clinical:
- Custom Database template (recommended)
- Oracle JVM (required)
- Oracle Text (required for TMS only)
- Service name requirements for Oracle Clinical include:
- The service name must be less than 15 characters long.
- It must not include the domain.
- It must be all lowercase.
-
Check that required tablespaces exist, and have Autoextend on:
- SYSTEM
- TEMP
- UNDOTBS1
- USERS
- SYSAUX
-
Initialization Parameters. The Table 2-3 table below shows the required or recommended values for Oracle Clinical. 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:
For an existing database, 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
- 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-3 Required and Recommended Initialization Values in the init.ora File
| Parameter | Value | Comments |
|---|---|---|
|
COMPATIBLE |
19.3.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. From Release 5.1 onward, setting this value causes problems with the Patient Data Report generation. |
|
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. Set this parameter to a value as per the number of concurrent users accessing the system. |
|
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_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. |
|
OPTIMIZER_ADAPTIVE_STATISTICS |
FALSE |
Controls adaptive statistics. Some query shapes are too complex to rely on base table statistics alone, so the optimizer augments these statistics with adaptive statistics. |
|
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 |
Acts as an umbrella for enabling a series of optimizer features based on an Oracle release number. |
|
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. |
Parent topic: Install Oracle Database 19.3.0
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.
Parent topic: Install Oracle Database 19.3.0
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."
- Check if the oinstall user group exists.
- If it does not exist, create it.
Parent topic: Install Oracle Database 19.3.0
Check Required Tablespaces
The table below 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-4 Required Tablespaces and Sizes
| Tablespace | Minimum Size |
|---|---|
|
SYSTEM |
900 MB |
|
TEMP |
100 MB |
|
UNDOTBS1 |
700 MB |
|
USERS |
500 MB |
|
SYSAUX |
600 MB |
Parent topic: Install Oracle Database 19.3.0