Understanding SQL*Net
Increasing the Queue Size for the Listeners
You can increase the listening queue, or backlog, for a listening process (that is, for TNSLSNR, INTLSNR, NAMES) to dynamically handle larger numbers of concurrent connection requests by adding a (QUEUESIZE=n) parameter to the end of any listening address in LISTENER.ORA, TNSNET.ORA, or NAMES.ORA. The parameter must be added as the last parameter in the network address (see sample files).
Note: Currently, you need to add this parameter manually to LISTENER.ORA, TNSNET.ORA, and NAMES.ORA--you cannot set it through Network Manager.
Note: Currently, you can configure the QUEUESIZE parameter for listeners on DECnet and TCP/IP protocols only. Also, if the QUEUESIZE parameter is not present in the appropriate configuration file (TNSNET.ORA, LISTENER.ORA, or NAMES.ORA), TCP/IP defaults to 17.
Increasing the Queue Size for the Listener
This section describes how to increase the queue size for the network listener. Add this parameter as the last parameter in the network address (see sample file). Currently, you need to add this parameter manually to LISTENER.ORA--you cannot set it through Network Manager. For information on other configuration parameters in LISTENER.ORA refer to "Configuring the Network Listener: LISTENER.ORA" in this chapter.
LISTENER.ORA
################
# Filename......: listener.ora
# Node..........: mike.world
# Date..........: 11-OCT-94 14:23:45
################
LISTENER_mike.world=(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=IPC)
(KEY=prod.world)
)
(ADDRESS=
(PROTOCOL=IPC)
(KEY=db1)
)
(ADDRESS=
(PROTOCOL=tcp)
(HOST=mike.world)
(PORT=1521)
(QUEUESIZE=20)
)
)
Increasing the Queue Size for the Interchange Listener
This section describes how to increase the queue size for the Interchange listener. Add this parameter as the last parameter in the network address (see sample file). Currently, you need to add this parameter manually to TNSNET.ORA--you cannot set it through Network Manager. For information on other configuration parameters in TNSNET.ORA, see the Oracle MultiProtocol Interchange Administrator's Guide.
TNSNET.ORA
################
# Filename......: tnsnet.ora
# Node..........: heather.world
# Date..........: 11-OCT-94 14:23:45
################
COMMUNITY_COST =
(COMMUNITY_COST_LIST =
(COMMUNITY_DESC =
(COMMUNITY = spxcom.world)
(COST = 10)
)
(COMMUNITY_DESC =
(COMMUNITY = tcpcom.world)
(COST = 10)
)
)
INTCHG_1.world =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = spxcom.world)
(PROTOCOL = SPX)
(Service = heather_INT_1)
)
(ADDRESS =
(COMMUNITY = tcpcom.world)
(PROTOCOL = TCP)
(Host = heather)
(Port = 1526)
(QUEUESIZE=20)
)
)
Increasing the Queue Size for the Oracle Names Server
This section describes how to increase the queue size for the Names Server. The parameter should be added as the last parameter in the network address (see sample file). Currently, you need to add this parameter manually to NAMES.ORA; you cannot set it through Network Manager. For information on other configuration parameters in NAMES.ORA, see Chapter 6 in the Oracle Names Administrator's Guide.
NAMES.ORA
names.server_name = NameServer.us.oracle.com
names.admin_region = (REGION=
(NAME= LOCAL_REGION.world)
(TYPE= ROSDB)
(USERID= NETADMIN)
(PASSWORD= netadmin)
DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(COMMUNITY=TCPCOM.us.oracle.com)
(PROTOCOL=TCP)
(Host=deer.us.oracle.com)
(Port=1521)
(QUEUESIZE=20)
)
)
(CONNECT_DATA=(SID=ds)
)
)
(DOCNAME=deer)
(VERSION= 34611200)
(RETRY = 600))
names.config_checkpoint_file= cfg00406
names.trace_level= OFF
names.trace_unique= FALSE