| Property | Description |
|---|---|
|
Parameter type |
Boolean |
|
Default value |
|
|
Modifiable |
|
|
Range of values |
|
|
Basic |
No |
|
Oracle RAC |
If specified, all instances must use the same value |
USE_DEDICATED_BROKER determines how dedicated servers are spawned. When this parameter is set to false, the listener spawns a dedicated server directly.
When this parameter is set to true, the listener hands the connection to a dedicated connection broker that spawns the dedicated server. Unlike the listener, the dedicated connection broker is a database process, and hence it can implement policies leveraging database information before the spawn.
To enable the dedicated connection broker using the USE_DEDICATED_BROKER initialization parameter, you must:
Set the USE_DEDICATED_BROKER initialization parameter to true.
Set the DEDICATED_THROUGH_BROKER_listener-name parameter to on in the listener.ora file.
Performing these two steps configures the Connection Broker Process (Nnnn).
Note:
When multithreaded Oracle is enabled, the dedicated connection broker process is also enabled and used.
Configuration of the brokers is controlled by the CONNECTION_BROKERS initialization parameter.
See Also:
"CONNECTION_BROKERS" for more information about configuring brokers
Table F-1 for more information about the Connection Broker Process (Nnnn)
"THREADED_EXECUTION" for more information about enabling multithreaded Oracle
Oracle Database Net Services Reference for more information about the DEDICATED_THROUGH_BROKER_listener-name parameter in the listener.ora file
Multithreaded Oracle is enabled by setting the THREADED_EXECUTION initialization parameter to true.