Oracle® Internet Directory Administrator's Guide 10g (9.0.4) Part Number B12118-01 |
|
Tuning Considerations for the Directory, 7 of 12
This section describes the other tunable parameters available to an Oracle Internet Directory installation.
The following table gives a quick overview of the recommended values of RDBMS parameters for various client loads. These parameters are configurable in the initialization parameter file.
This section describes each of the RDBMS tunable parameters in more detail. It contains these topics:
Configure the OPEN_CURSORS parameter as follows:
OPEN_CURSORS=200
The Oracle9i default of 50 or so is too small to accommodate Oracle Internet Directory server cursor cache. Note that this value is not dependent on other Oracle Internet Directory server parameters, such as # SERVERS and # WORKERS. The value of 200 is sufficient for any size DIT.
Configure the SESSIONS parameter as follows:
PROCESSES = (# OID server processes for each instance) x(# DB Connections for each server + 1) x (# of OID instances) + 20SESSIONS = 1.1 * PROCESSES + 5
Each Oracle Internet Directory server process requires a number of concurrent database connections equal to the number of worker threads configured for that server plus one. The total number of concurrent database connections allowed must therefore include this number for each server, for each instance. The additional 20 connections added to the parameter value accounts for the Oracle background processes plus other Oracle Internet Directory processes such as OID Monitor, OID Control, Oracle directory replication server, and bulk tools.
Depending on the total number of concurrent database connections required, and as determined by the setting for the SESSIONS parameter, enabling shared server process may help balance overall system load better. If the total number of concurrent database connections required is over 300, then configure the shared server. One shared server should be configured for every 10 database connections required.
The main parameters that contribute to the SGA are discussed in "Memory Tuning". The following are a few more parameters that may be tuned:
Set to 262144 (256k) to ensure sufficient sort area available to prevent sorts on disk.
Set to 32768 (32k) as an initial estimate. If log write performance becomes a performance problem, use a large enough value to make sure (redo log space requests / redo entries) > 1/5000 to prevent the LGWR process from falling behind. This overall has little size effect on the variable SGA size, so making this a little bit too large should not be a problem.
|
![]() Copyright © 1999, 2003 Oracle Corporation. All Rights Reserved. |
|