Saturday, August 06, 2005

How to run Oracle listener on non-default port

You can able to run Oracle listener on non default oracle port.
open listener.ora file you can find that in oracle_home/network folder

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = test)(PORT = 1577))
)
)
)

change port=

then open tnsnames.ora in the same directory.
test =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = test)(PORT = 1577))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = test)
)
)

mention same port no.

Now oracle listen on non-default oracle port.

Also you can run multiple listener for one database.
change your listener.ora
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = test)(PORT = 1577))
)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = test)(PORT = 1521))
)
)
)


I had asked thomas kyte for proc and cros there input as below.
Hi Tom,

If two listener on two port i.e. 1521 and 1522 are listening for one (X
database) database.

What are the pros and cros if one database have 2 listener and have 1 listener ?

Regards,
Nikunj

Followup:
pros - extreme cases.

cons - extra work, maintainance, monitoring.

if and only if a single listener was getting so nailed, hit so hard, that it
built up a queue of requests and started failing the requests because the queue
was too long would I consider another listener.

And even then, it would likely be on another machine, for another instance,
using the same database - if you are nailing a listener that hard....

No comments: