Re: Oracle 8 and MTS: how to set the dispatcher port

On 7 Aug 2003 08:19:26 GMT, Holger Marzen <holger_at_marzen.de> wrote:

> Hi all,
>
> after an upgrade from Oracle 8.1.7.0 to 8.1.7.4 (Solaris) the MTS
> feature worked. I set it up as follows:
>
> |large_pool_size = 25M
> |mts_dispatchers="(protocol=tcp)"
> |mts_service=INS1
> |mts_listener_address="(ADDRESS=(PROTOCOL=tcp)(port=1521))"
>
> and I guess I misunderstood the docs and made a mistake. What I observed
> is this:
>
> - clients connect to port 1521 and get redirected to port 32830
> - the dispatcher ora_d000_INS1 is listening on port 32830
>
> That makes sense but introduces another problem. The firewall has to be
> opened for clients that want to connect to the Oracle machine. Without
> MTS it was only destination port 1521, but now we had to open port 32830
> as well. So far, so good. But what happens if I restart Oracle? Will
> another dispatcher port be randomly choosen? That woul be bad because we
> would have to change the firewall rules after every restart of Oracle.
>
> Would be
>
> |mts_listener_address="(ADDRESS=(PROTOCOL=tcp)(port=32830))"
>
> the right approach to force the dispatcher port to 32830.
>

No. That port number is the port of the Listener (where the dispatcher goes to register itself). That parameter is also obsolete (and was obsolete even in 8.0.6). It's replacement is LOCAL_LISTENER.

And it's completely unnecessary in your case.

The default listener listens on TCP/IP at port 1521. If you don't change those parameters, then dispatchers already know where to go to register themselves with the listener. You only need to set local_listener when you have a listener which is using either a different protocol or a different listening address. It appears you have neither different, so you don't need the local_listener parameter (and you certainly don't need the mts_listener_address version of it).

~QM Received on Thu Aug 07 2003 - 04:30:17 CDT