|Lesson 4||Configuring the dispatchers for MTS, part 3|
|Objective||Explain the function of the remaining dispatcher parameters|
mts_max_dispatchersparameter sets the maximum number of dispatcher processes (out of the total number of network protocols) that can be started for the duration of an instance. You can create as many dispatcher processes as you need, but the total number of processes cannot exceed the host operating system's limit on the number of running processes (normally the
maxuprocUNIX parameter). To estimate the maximum number of dispatcher processes an instance will require, use the following formula:
|MTS_MAX_DISPATCHERS||=||maximum number of
connections per dispatcher
mts_serversparameter determines the number of shared server processes that start at instance startup. The appropriate number of shared server processes for a database system depends on how many users typically connect to it and how much processing each user requires.
mts_serversto at least 1. If you omit the parameter or set it to 0, Oracle does not start any shared servers at all. However, you can set
mts_serverssubsequently to a number greater than 0 while the instance is running.
mts_max_serversparameter establishes during instance startup the maximum number of shared server processes that can be started for the duration of an instance. In general, set this parameter to allow an appropriate number of shared server processes during times of greatest activity. Whenever an instance is to be bounced, stop the listener, shut down the instance, restart the listener, and start up the instance. The listener reads the MTS parameters only if it is running before startup of the instance. Therefore, bouncing the listener without bouncing the database will disable the MTS and the listener will restart in dedicated mode.