The new Automated Shared Server Configuration feature provides additional flexibility if you are using two server models. You can now easily switch between shared server and dedicated server without having to start a dispatcher.
When the Oracle Database 10g shared server (previously multi-threaded server or MTS) is configured and a client connection request arrives while no dispatchers are registered, a dedicated server process handles the request. To ensure that a particular database server’s clients always connect to a dispatcher, configure the connect_data section of the connect descriptor as follows:
(SERVER=shared)
For example, using our test database instance:
test= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=test-server)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=test.us.rmapant.com) (SERVER=shared) ) )
When no dispatcher process is available to service the requested connection, then the client connection request is rejected when SERVER=shared is set.
If the database is configured for shared server and a particular client requires a dedicated server, you can configure the client to use a dedicated server in one of the following ways:
Configure a net service name with a connect descriptor that contains (SERVER=dedicated) in the connect_data section. For example:
test= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=test-server)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=test.us.rampant.com) (SERVER=dedicated) ) )
Configure the client profile (sqlnet.ora file) with use_dedicated_server on. This parameter tells Oracle to add (SERVER=dedicated) to the connect_data section of the connect descriptor the client uses.
If dispatchers have been configured, the default value of shared_server is 1.
Shared Server Information – For more information about the Shared Server


Whitehorses is specialized in succesfully implementing Oracle SOA solutions: BPEL, OSB, WebLogic & BPM