Set Initialization Parameters

After the upgrade completes:

1. Set the init.ora parameters. See Table 3-1 for parameter values.
2. Stop and then start the database to activate the modified init.ora parameters.

Note:

Do NOT SET the DB_DOMAIN parameter. In Release 5.1 onward, this causes problems with the Patient Data Report generation.

If you set up the EVENT parameter in the init.ora file to trace unique key constraints before upgrading, you should set the event parameter back to its required value. See Table 3-1 for details.

If your init.ora file includes the REMOTE_OS_AUTHENT parameter, make sure that it is not set to TRUE. It can be set to FALSE or be absent.

Table 3-1 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. In 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.
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.