Performance Tuning Siebel Software on the Sun Platform

● UpperThreshold - Recommended value: 25
● LoadBalanced - Recommended value: true (default value, of course)
● Driver.Count (at client) - Recommended value: 4
7.3 <strong>Siebel</strong> Server Scalability Limitations and Solutions
7.3.1 The <strong>Siebel</strong> MaxTasks Upper Limit Problem
In order to configure <strong>Siebel</strong> server to run over 8000 concurrent users, the <strong>Siebel</strong>
parameter MaxTasks has to be set to a value of 8800. When this is done, the <strong>Siebel</strong>
object manager processes (that is, the <strong>Siebel</strong> servers) failed to start and logged error
messages. This failure was not due to any resource limitation from the Solaris OS, as
there were ample amounts of CPU, memory, and swap space on the machine. The
failure to start was due to the E2900 with 12 CPU, 48Gbytes RAM.
<strong>Siebel</strong> enterprise server logged the following error messages and failed to start:
GenericLog GenericError 1 2004-07-30 21:40:07 (sissrvr.cpp 47(2617)
err=2000026 sys=17) SVR-00026: Unable to allocate shared memory
GenericLog GenericError 1 2004-07-30 21:40:07 (scfsis.cpp 5(57)
err=2000026 sys=0) SVR-00026: Unable to allocate shared memory
GenericLog GenericError 1 2004-07-30 21:40:07 (listener.cpp 21(157)
err=2000026 sys=0) SVR-00026: Unable to allocate shared memory
Explanation
To understand what occurred, it is necessary to review some background on the <strong>Siebel</strong>
server process siebsvc:
The siebsvc process runs as a system service that monitors and controls the state of
every <strong>Siebel</strong> server component operating on that <strong>Siebel</strong> server. Each <strong>Siebel</strong> server is an
instantiation of the <strong>Siebel</strong> Server System Service (siebsvc) within the current <strong>Siebel</strong>
Enterprise Server. <strong>Siebel</strong> server runs as a daemon process in a UNIX environment.
During startup, the <strong>Siebel</strong> Server System Service (siebsvc) performs the following
sequential steps:
1. Retrieve configuration information from the <strong>Siebel</strong> Gateway Name Server.
2. Create a shared memory file located in the "admin" subdirectory of the
<strong>Siebel</strong> server root directory on UNIX. By default, this file has the name
Enterprise_Server_Name.<strong>Siebel</strong>_Server_Name.shm.
The size of this file *.shm is directly proportional to the MaxTask setting. The higher the
number of concurrent users the higher the MaxTask.
The <strong>Siebel</strong> Server System Service deletes this .shm file when it shuts down.
<strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 30