topic Re: dual listeners in Operating System - HP-UX

dual listeners

David Bellamy — Thu, 09 Nov 2000 19:09:46 GMT

i'm having trouble implementing three listeners(3 instance). any pointers
thx

Re: dual listeners

John Eaton — Thu, 09 Nov 2000 20:54:03 GMT

I'm not a DBA, but I beat my DBA's into doing this in a MC/SG clustered system.
For Oracle, the different database listeners are defined in the listener.ora file, EACH WITH IT'S OWN PORT. For example: abd01 is port 1522, and efg01 is port 1523.
You want to avoid using port 1521. Leave this for the default listener.
Hope this helps.

Re: dual listeners

Tom Danzig — Thu, 09 Nov 2000 20:57:54 GMT

Be sure to name each listener something different. The default is "LISTENER".

We have 5 running on a V class without issue.

Re: dual listeners

Geetam — Fri, 10 Nov 2000 09:30:45 GMT

Are you sure you want three listeners (you are talking about Oracle Listeners, I assume)

One listener can listen for requests for more then one database.

Re: dual listeners

Vladislav Demidov — Fri, 10 Nov 2000 09:43:12 GMT

Create listener configuration file in $ORACLE_HOME/network/admin/listener.ora and specify in that file all instances for the listener.
Example of listener.ora
LISTENER =
(ADDRESS_LIST =
(ADDRESS= (PROTOCOL= IPC)(KEY= my_openview.aaa.com))
(ADDRESS= (PROTOCOL= IPC)(KEY= openview))
(ADDRESS= (PROTOCOL= IPC)(KEY= my_test.aaa.com))
(ADDRESS= (PROTOCOL= IPC)(KEY= test))
(ADDRESS= (PROTOCOL= TCP)(Host= my)(Port= 1527)
(COMMUNITY = TCP.aaa.com))
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME= my_openview.aaa.com)
(ORACLE_HOME= /app/oracle/product/7.3.4)
(SID_NAME = openview)
(PRESPAWN_MAX = 0)
)
(SID_DESC =
(GLOBAL_DBNAME= my_test.aaa.com)
(ORACLE_HOME= /app/oracle/product/7.3.4)
(SID_NAME = test)
(PRESPAWN_MAX = 0)
)
)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = OFF

Re: dual listeners

Dan Peters — Thu, 16 Nov 2000 16:07:51 GMT

Although you can implement only one listener for multiple database, if you have sufficient load, it is warranted to create multiples.
Note that it is a good idea to instantiate a listener for each version of the database that you are running.
IE: we have 4 Instances of 7.3.4, and two of 8.1.5, so we are running two listeners (LISTENER and LISTENER8).
The oracleSID will determine which listener we can work with.
If we use a 7.3.4 environ, then lsnrctl will start with the LISTENER set as current.
If we want to modify the LISTENER8, then first, change the SID to one of the 8.1.5 DB's, then start lsnrctl. Use the command "set current_listener LISTENER8" to change the current listener, then you can issue the normal commands, like start, status, etc.

Re: dual listeners

Dan Peters — Thu, 16 Nov 2000 16:12:08 GMT

A couple additions to previous posts:
No real need to multiple listeners unless:
Using more than one version on same server
Very heavy user load.
Ie: we use 4x 7.3.4 Instances, and 2x 8.1.5
There are two listeners (LISTENER and LISTENER8). To start/modify LISTENER, change the OracleSID to one of the 7.3.4 instances, and run lsnrctl. This will start the ctl program with LISTENER set as the current listener.
To modify LISTENER8, change SID to one of the 8.1.5 instances, run lsnrctl then the following command:
set current_listener LISTENER8
This will allow you to start/stop/status the other listener.