Hi
whats the purpose of having multi listener ???
will it increase the posting speed in server, when it receives bulk data from 2 clients ???
thanks in advance
Himaja
Printable View
Hi
whats the purpose of having multi listener ???
will it increase the posting speed in server, when it receives bulk data from 2 clients ???
thanks in advance
Himaja
Depends. Is the listener process consuming a lot of CPU?
We use it to differentiate projects, so that certain databases/applications, use a particular port.Quote:
Originally Posted by Himaja
hi
while setting multi listener, i changed only the host.
i dint change the port.
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.9.100.1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.9.100.2)(PORT = 1521))
is it the right way of setting multi listener ??
thanks in advance
himaja
Hi,
read
http://download-west.oracle.com/docs...ts.htm#1041193
In that also read
Enhanced Service Accessibility with Multiple Listeners
I think it will Halp you in your question
Rgds
Parag
Correct me if I'm wrong, but isn't the address list (above) for using 2 network cards (each with it's own IP) in 1 server?Quote:
Originally Posted by Himaja
Or failover for a RAC environment...
From "Enhanced Service Accessibility with Multiple Listeners" link above:
"For some configurations, such as Oracle9i Real Application Clusters, multiple listeners on multiple nodes can be configured to handle client connection requests for the same database service. In the following example, sales.us.acme.com can connect to sales.us.acme.com using listeners on either sales1-server or sales2-server."
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))
(ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com)))
Sorry, but I'm confused.
Certanly not! Data to be inserted/updated/deleted/retrived fint/from the database *never* goes through the listener. Database server and the client talk directly to each other, no listener is involved in that. Listener only take its part between the client and the database during the connection time. Once the session is established listener is no longer needed - you can even shut it down and the connected sessions will still happily comunicate with the database.Quote:
Originally Posted by Himaja
jmodic,
Yea, I guess he wasn't concerned about overloading a nic or a port with new connections.
I agree that the listener has nothing to do with established connections data throughput. The listener's job is to start the user's server process and step aside.
That's what I was going to say until I thought maybe they're connecting each time before they insert (don't laugh, I've seen it).Quote:
Originally Posted by jmodic