The shared server architecture also enables existing applications to scale up without making any changes to the application itself. When using shared server, clients do not communicate directly with a database's server process—a database process that handles a client's requests on behalf of a database. Instead, client requests are routed to one or more dispatchers. The dispatchers place the client requests on a common queue. An idle shared server from the shared pool of server processes picks up and processes a request from the queue. This means a small pool of server processes can serve a large number of clients. The following two figures show the basic difference between the shared server connection model and the traditional dedicated server connection model. In the shared server model, a dispatcher can support multiple client connections concurrently.
2 - Articles Related
Enabling Session Multiplexing
Oracle Database creates server processes to handle the requests of user processes connected to an instance. A server process can be either of the following:. Your database is always enabled to allow dedicated server processes, but you must specifically configure and enable shared server by setting one or more initialization parameters. Figure , "Oracle Database Dedicated Server Processes" illustrates how dedicated server processes work. In this diagram two user processes are connected to the database through dedicated server processes. In general, it is better to be connected through a dispatcher and use a shared server process. A shared server process can be more efficient because it keeps the number of processes required for the running instance low.
Dedicated Server Processes
When client load causes a strain on memory and other system resources, database administrators can alleviate load issues by starting shared server resources. The shared server architecture enables a database server to allow many client processes to share very few server processes, so the number of users that can be supported is increased. With the shared server architecture, many client processes connect to a dispatcher. The dispatcher directs multiple incoming network session requests to a common queue. An idle shared server process from a shared pool of server processes picks up a request from the queue. This means a small pool of server processes can serve a large number of clients. This is useful when a system is overloaded or has limited memory. Shared memory resources for dispatchers, virtual circuits, and shared servers are preconfigured enable shared servers at runtime. You do not need to restart the instance after setting the parameters.
Implement both shared server and dedicated connections Oracle Database Tips by Donald BurlesonApril 28, Question: What do I do to set up my instance to support both MTS connections shared servers and dedicated connections? I would like to deploy both dedicated connections and shared server connections. See MTS dispatchers configurations That will deploy both dedicated connections and shared server connections. Java connections. The shared servers method is slower. For an Oracle client, the choice of connections methods MTS vs, dedicated depends on the setting in their tnsnames. Here, we changes a client tnsnames. Oracle Training from Don Burleson The best on site " Oracle training classes " are just a phone call away!