Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 
 

Oracle listener.ora parameters tips

Oracle Database Tips by Donald BurlesonFebruary 10, 2015

 

A basic listener.ora file might look like the following:

LISTENER=
(description=
(address_list)=
(address=(protocol=tcp)(host=fu-bar)(port=1521))
(address=(protocol=ipc)(key=extproc))))
sid_list_listener=
(sid_list=
(sid_desc=
(sid_name=plsextproc)
(oracle_home=/oracle11g)
(program=extproc)))

Oracle Net Manager can be used to customize the listener.ora file.

Listener.ora parameters for RAC:

The listener.ora file contains the information needed by the SQL*Net listener file to identify the instances for which connection requests are being serviced. If no instances are listed in the listener.ora, the listener process will wait for the instances to self-register (instances have been capable of self-registering since Oracle8i). Below is shown a basic listener.ora file for use with RAC.

LISTENER=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=aultlinux1)
(PORT=1521)))

If advanced features such as load balancing and automatic failover are desired, there are optional sections of the listener.ora file that must be present. For example, to configure load balancing, the listener.ora file (using an instance name of "test") would be appropriate. The listener file must be the same on the servers that are participating in the load balancing for RAC. The second listener, "listener_test1" allows use of Oracle Enterprise Manager with the instance.

You should never configure the global_dbname parameter with Oracle RAC if you wish to use connect time failover or transparent application failover. Setting this parameter will disable these capabilities.

For the second server, the second listener would be called "listener_test2", and all instance specific references would be changed to "test2", while all server specific references would be changed to "testlinux2".

Listener_Test=
(description=
(load_balance=on)
(address=(protocol=tcp)(host=testlinux1)(port=1521)
(address=(protocol=tcp)(host=testlinux2)(port=1521)
(connect_data=
(service_name=test)))
listener_test1=
(description=
(address=(protocol=tcp)(host=testlinux1)(port=1521)
sid_list_listener_test1=
(sid_list=
(sid_desc=
(oracle-home=/u01/app/oracle/product/9.2.0.2)
(sid_name=test1)))

If a port other than 1521 is utilized, then the local_listener parameter in that instances local init.ora file must be set to the same port value. For example, if we used port 1525 instead of 1521, all references to port 1521 in the listener.ora would be changed to 1525, and the following entry would have to be added to the local init.ora:

local_listener="(address=(port=1525)(protocol=tcp)(host=testlinux1))"

 

queuesize parameter in listener.ora

If it is expected that the listener will receive large numbers of requests for connection, a queue may be specified for the process. This enables the listener to handle larger numbers of simultaneous connection requests. The number of requests the listener can store while Oracle works to establish a connection is specified by the queuesize parameter. The value of this parameter should be equivalent to the number of expected simultaneous connections. Below is an example of the queuesize parameter in the listener.ora file:

LISTENER =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = marvin)
(PORT = 1521)
(QUEUESIZE = 32)
)
)

Use of queuesize can be disadvantageous since more resources and memory is used. The parameter pre-allocates resources for anticipated connection requests. For this reason, if high-volume connections into a dedicated listener are anticipated, it may be beneficial to implement the Multi-Threaded Server (MTS) and use pre-spawned Oracle connections.

 

For example, to configure one or more Listening Protocol Addresses, use the following steps by accessing the Net Services Administration page in Oracle Enterprise Manager:

  1. From the Administer list, select Listeners
    Select the Oracle home that contains the location of the configuration files
  2. Click Go to access the Listeners page
  3. Select a listener
  4. Click Edit to access the Edit Listener page
  5. In the Addresses section, configure protocol support:
    1. Click Add to access the Add Address page
    2. From the Protocol list, choose the protocol upon which the listener is configured to listen
    3. Enter the parameter information for the selected protocol.
      The default port of 1521 should be used when configuring the listener to listen on TCP/IP. Failure to do so requires configuration of the local_listener parameter in the initialization parameter file and resolving the listener name through a naming method.
    4. For computers with more than one IP address, if it is important for the listener to listen on all available IP addresses, you will need to configure TCP/IP or TCP/IP with SSL and enter the host name of the computer in the host field.
  6. Click OK to add the protocol address to the Addresses section.

This can be repeated as many times as necessary to add listener protocol addresses.

 
Get the Complete
Oracle SQL Tuning Information 

The landmark book "Advanced Oracle SQL Tuning  The Definitive Reference"  is filled with valuable information on Oracle SQL Tuning. This book includes scripts and tools to hypercharge Oracle 11g performance and you can buy it for 30% off directly from the publisher.