How to Configure DRCP Broker to Use a Specific Listening IP Address (Doc ID 1333553.1)

Last updated on NOVEMBER 17, 2024

Applies to:

Goal

In 11g was introduced the Database Resident Connection Pool (DRCP).
The architecture of DRCP include a background process called DRCP Connection Broker.
The name of the process is ora_n00X_<SID>, where X=1,2.. as an instance can have multiple Connection Brokers started.

This process appear also as handler for database services in 'lsnrctl services':


Service "<SERVICE_NAME>.oracle.com" has 1 instance(s).
    Instance "<instance>", status READY, has 2 handler(s) for this service...
        Handler(s):
        "DEDICATED" established:5777 refused:0 state:ready
              LOCAL SERVER
        "N000" established:0 refused:0 current:0 max:40000 state:ready
             CMON <machine: <hostname>.com, pid: 27958>
             (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>.com)(PORT=27402))

from this output we find out the OS PID and the IP where the Broker is listening for incoming connections.

The DRCP Connection Broker receives clients connections REDIRECTED by the listener.  These are  clients who specifically requested SERVER=POOLED in their connect descriptor.
From the client perspective a connection is first initiated to the listener IP then, after a REDIRECT from the listener, a new connection is opened to the Broker IP.
By default, the IP used by the Broker to listen for incoming connections is the hostname of the machine and it isn't configurable.

This can create problems on servers with multiple IPs, where listener is listening on an IP different from the hostaname of the server:
  - exadata machines who use the hostname IP as a management network closed to clients access
  - servers behind a firewall where only the listener IP is opened for the clients


We need to be able to specify the IP where DRCP Connection Broker will bind waiting for client connections.

Solution