1. Database Reference
  2. Initialization Parameters
  3. Initialization Parameters
  4. USE_DEDICATED_BROKER

1.362 USE_DEDICATED_BROKER

USE_DEDICATED_BROKER determines how dedicated servers are spawned.

Property Description

Parameter type

Boolean

Default value

False unless multithreaded Oracle is enabledFoot 1

Modifiable

ALTER SYSTEM

Modifiable in a PDB

No

Range of values

true | false

Basic

No

Oracle RAC

If specified, all instances must use the same value

Footnote 1

Multithreaded Oracle is enabled by setting the THREADED_EXECUTION initialization parameter to true.

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:

  1. Set the USE_DEDICATED_BROKER initialization parameter to true.

  2. 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: