Re: Multi-homed interface and Oracle listener

"Jeff Traigle" <traigle_at_si.umich.edu> wrote in message news:BA51C9D2.3ECA5%traigle_at_si.umich.edu...
>
> Ok. I think I understand how this is working now. Results of netstat -an:
>
> tcp 0 0 19.63.4.222.1521 19.63.50.184.1220 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.50.152.1049 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.51.102.3197 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.50.109.1071 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.91.31.1048 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.91.31.1044 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.91.31.1040 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.50.176.1039 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.50.176.1035 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.51.160.1087 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.51.157.1035 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.91.188.2506 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.5.123.1673 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.51.160.1060 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.51.213.1277 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.5.123.1659 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.51.53.1279 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.50.98.3723 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.91.41.1081 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.91.236.1282 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.50.85.1250 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.90.110.1033 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.50.156.1032 ESTABLISHED
> tcp 0 0 136.17.216.21.1521 19.63.51.53.1036 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.51.216.1118 ESTABLISHED
> tcp 0 0 19.63.4.222.1521 19.63.91.154.1035 ESTABLISHED
> tcp 0 0 *.1521 *.* LISTEN
>
> As Rick suspected, it looks like the listener is watching on any address
> configured on the system. (This is, in fact, a 7.3.2.3.0 database, but this
> seems to be consistent on my two other servers running 7.3.4.5.0 also.) As
> you can see, there are connections from both PCs that got their tnsnames.ora
> file updated to the new address and ones that did not.
>
> The confusion in behavior stems from the configuration of addresses in the
> listener apparently having nothing to do with the addresses it will actually
> listen on. The address configuration in listener.ora appears to only verify
> that the addresses configured are, in fact, active addresses on some
> interface on the server. (If one isn't present on the server, the listener
> fails to start.) However, once the listener starts successfully, it listens
> on any address configured on the system just like any other generic UNIX
> daemon.
>
> Not sure if that's true for 8.X and above of Oracle RDBMS since I don't have
> anything that new running. Or if there is some parameter in the listener.ora
> file that will restrict the listener to only the addresses configured in the
> listener.ora file. (If there is and someone knows it offhand, it would be
> nice to know what it is so feel free to share the knowledge.) It's been a
> few years since I took over DBA functions in my current position and took
> the 8.0 classes so don't even recall if this was something touched on in the
> networking class back then or not.

How is your listener.ora?

What about putting an explicit IP address instead of the hostname?

Umberto Received on Sat Jan 25 2003 - 09:22:48 CST