Re: s...port's - problem

Fabrizio wrote:
>
> Hi Daniel,
> the port redirection is true only on windows and it can be avoided
> setting use_shared_socket=true in the windows regedit.
>
> Unix maintains the communication on the listening port so you can keep
> only one port open in your firewall.
>

Don't exactly understand the "port redirection" bit, but the spawned process surely uses another port.
I used Linux client and server, in order to eliminate the possibility of a Windows client causing other ports to be used.

I configured tnsnames with a TCP connection, called fabr (sorry - did not feel like typing your name in full ;) ).

!netstat -e
Active Internet connections (w/o servers)

Proto Recv-Q Send-Q Local Address               Foreign Address
    State       User       Inode
tcp        0      0 csdb01.cs.nl:1522           csdb01.cs.nl:6037
    ESTABLISHED oracle10   7032519
tcp        0      0 csdb01.cs.nl:6037           csdb01.cs.nl:1522

    ESTABLISHED oracle10 7032518

Now, you can clearly see my listener on 1522 (the 9i instance uses a separate listener on 1521, in case you might wornder why 1522) has a connection to my server (the client, actually) on 6037. The reverse is true, too.
Now, after a "connect system/manager_at_fabr", the picture is changed:

SQL> !netstat -e
Active Internet connections (w/o servers)

Proto Recv-Q Send-Q Local Address               Foreign Address
    State       User       Inode
tcp        0      0 csdb01.cs.nl:1522           csdb01.cs.nl:6041
    ESTABLISHED oracle10   7032766
tcp        0      0 csdb01.cs.nl:6037           csdb01.cs.nl:1522
    TIME_WAIT   root       0
tcp        0      0 csdb01.cs.nl:6041           csdb01.cs.nl:1522

    ESTABLISHED oracle10 7032765

There's a new connection, on port 6041! The one on 6037 disappears after a while - no hurry with that, I suppose.

Now unless you mean something completely different with port redirecting, the original answer by Daniel was correct.

use_shared_socket was broken in Windows on 8.1.7 (worked on 8.1.6); Unix was not affected (it's just an ordinary environment variable, afaik). Haven't tested when it was fixed (if at all).

-- 
Regards,
Frank van Bortel