User`s guide

Introducing Oracle Net Services
Oracle Net Services 9-3
9.1.3 Using the TCP/IP Protocol
The TCP/IP protocol support implements a standard interface that is used to resolve
the equivalent communication functions between the TCP/IP protocol and Oracle's
Net Foundation Layer.
After the TCP/IP protocol is installed for the particular system, you can use the
TCP/IP–specific parameter
s with the TNS connect descriptors to identify nodes within
a TCP/IP-based community.
The specific TCP/IP connection parameters are part of the
ADDRESS keyword-value
pair. The three TCP/IP–specific parameters can be entered in any order within the
ADDRESS construct. The syntax used by Oracle's TCP/IP protocol support is:
(ADDRESS=
(PROTOCOL=TCP)
(HOST=hostname)
(PORT=port#)
)
where
PROTOCOL specifies the supported protocol. For TCP/IP, the value is TCP .
HOST specifies the host name or the host's IP address.
PORT specifies the TCP/IP port number.
The following is an example of the TCP/IP ADDRESS specifying a client on the
sales-server host:
(ADDRESS=
(PROTOCOL=TCP)
(HOST=sales-server)
(PORT=1521)
)
9.1.4 Bequeath Protocol
The Bequeath technique enables clients to connect to a database without using the
network listener. Oracle's Bequeath protocol internally spawns a server process for
each client application. It does the same operation that a remote network listener does
for the connection locally.
Note: Starting with Oracle Database 10g the BEQ protocol uses the
handoff technique which makes this protocol incompatible with the
BEQ protocol of prior versions. As a consequence of this
enhancement, Oracle Database 11g applications cannot directly spawn
a process of a version prior to Oracle Database 10g and connect to it
through the BEQ protocol.
9.1.4.1 Overview of the Bequeath Protocol
The Bequeath protocol
■ Does not use a network listener (therefore, no listener configuration is required).
■ Automatically spawns a dedicated server