Siebel Performance Tuning Guide > Tuning the Web Server Computer for All UNIX and Linux Platforms >

Tuning the Siebel Server for All UNIX and Linux Platforms

For all Siebel Server computers running on supported UNIX platforms, setting the environment variables described in this topic can help you manage your server resources appropriately and stay within appropriate CPU-usage limits.

Environment Variable for Siebel Assert Creation

For Siebel Server computers or Web server computers, the environment variable SIEBEL_ASSERT_MODE determines whether assert files are created. With the default setting of 0, the creation of assert files is disabled, which conserves disk space and improves performance.

Set this variable to a nonzero value only if you are performing system diagnostics, and only in consultation with Oracle Global Customer Support. For more information about this variable, see Siebel System Monitoring and Diagnostics Guide.

Environment Variable for Operating System Resource Limits

Set the environment variable SIEBEL_OSD_MAXLIMITS using one of the following methods (define the variable in the applicable profile for the Siebel Server):

• C Shell:

  setenv SIEBEL_OSD_MAXLIMITS 1

• Korn Shell or Bourne Shell:

  SIEBEL_OSD_MAXLIMITS=1;export SIEBEL_OSD_MAXLIMITS

Setting this variable to 1 specifies that operating system maximum values for resources will apply. Such resources might include coredumpsize, cputime, filesize, descriptors, maxmemory, and others.

Environment Variable for Operating System Latches

Depending on the total number of tasks on the Siebel Server, you might need to set the environment variables described here in order to manage these loads. SIEBEL_OSD_NLATCH controls named latches and SIEBEL_OSD_LATCH controls unnamed latches. Latches, which are similar to mutexes (mutual exclusion objects), are used for communication between processes.

If SIEBEL_OSD_NLATCH and SIEBEL_OSD_LATCH are not defined, then the values are 5000 and 1000, respectively. If these values are sufficient for the total number of tasks on the Siebel Server, then you do not set these variables. Do not set these variables to values lower than their default values.

NOTE:  Before changing these variables, stop the Siebel Server, then using the stop_server command, run the cleansync utility.

Set SIEBEL_OSD_NLATCH and SIEBEL_OSD_LATCH on the Siebel Server computer based on the following formulas (define the variables in the applicable profile for the Siebel Server):

• SIEBEL_OSD_NLATCH = (7 times (cumulative MaxTasks for all components)) plus 1000
• SIEBEL_OSD_LATCH = 1.2 times (cumulative MaxTasks for all components)

Assume, for example, that you have enabled two multithreaded server components on the same Siebel Server: SCCObjMgr_enu and WfProcMgr. For SCCObjMgr_enu, MaxTasks = 700 and, for WfProcMgr, MaxTasks = 150. In this example, parameter values must be as follows:

• SIEBEL_OSD_NLATCH = 6950 = (7 times (700 plus 150)) plus 1000
• SIEBEL_OSD_LATCH = 1020 = 1.2 times (700 plus 150)

NOTE:  Although the formulas presented here are expected to work for most deployments, in certain cases you might need to increase (for example, double) the values of these variables, and then monitor system behavior with the adjusted values. (An error message such as SBL-OSD-00217: Error exceeded maximum number of latches can sometimes be generated even when the variables are set according to the recommended formulas.)