映射端口远程去访问Oracle数据库

oracle服务器在内网，外面通过路由的端口转到1521端口去访问，但是tnsping能通，telnet 1521也可以连上，但就是提示“访问超时”，查了半天资料终于找到原因：

Windows Platform Considerations
Windows does not implicitly support inheritance of network endpoints. To do this, the registry entry USE_SHARED_SOCKET must be set to TRUE to allow multiple connections to use a single socket. When the value is FALSE (default), bequeath connections are not possible so a redirect session is initiated instead.
If the USE_SHARED_SOCKET entry is set to TRUE, Windows can initiate bequeath connections but there are some caveats to consider. If a number of connections are initiated and for some reason the listener is stopped, the listener will not be able to be restarted until the connections are cleared. This is because the existing connections are using the same port number that the listener needs to listen on. This is a limitation with Microsoft’s implementation of TCP/IP using Windows Sockets API (WINSOCK2).

先来看一下oracle的重定向访问：

Oracle服务器的默认侦听端口为1521，但实际通讯时使用的端口分为两种情况，具体如下：
专用模式（windows下安装oracle服务器默认运行在这个模式）下，通讯端口与侦听端口不同；
共享模式 MTS (UNIX下安装oracle服务器默认运行在这个模式)下，通讯端口和侦听端口相同。
所以，在对oracle服务器做端口映射和防火墙规则配置时，让oracle运行在共享模式下比较方便。

资料一、 近来由于工作需要，在Windows XP平台上安装了Oracle9i数据库作为测试之用，一切正常。但当客户机连接服务器时却总是超时，我首先想到了防火墙，当我打开1521端口时，连接操作仍然失败。我又怀疑网络有问题，用telnet server_ip:1521尝试，连接被接受，说明1521端口已经被打开。 没有办法，查询Oracle资料后才明白，network listener 只起一个中介作用，当客户连接它时，它根据配置寻找到相应的数据库实例进程，然后spawned一个新的数据库连接，这个连接端口由network listener传递给客户机，此后客户机就不再和打交道了，即使listener停止了工作。这个新的连接端口是不可预知的，因而会被防火墙阻止。

indows Socket2 规范有一个新的特性，就是Shared Socket， 所谓共享套接字是指一个进程共享另一个进程的套接字(详见MSDN相关参考）。如果让network listener与数据库服务进程共享套接字，那么连接端口就不会变化。 如何设置 Shared Socket? 在注册表：HKEY_LOCAL_MACHINESOFTWAREORACLEHOME0上新建一个字符串值：USE_SHARED_SOCKET=true。如果安装了多个目录，则每个类似的目录都要设置：HKEY_LOCAL_MACHINESOFTWAREORACLEHOMEx (x目录编号） 设置后要求重新启动实例（只重启listener发现没有效果） 引用资料：典型问题：when a client connects to a listener it uses port 1521 at the client machine. the listener then returns to the client thru a different port. The 1521 port is closed and the db connection uses the new port for communicating with the client. i want the listener to return to the client using port 1521， how? metalink says use the use_shared_socket parameter， but its still not working. i set the parameter to true in the sys env and in the registry. .... oracle USE_SHARED_SOCKET You can set the USE_SHARED_SOCKET parameter to TRUE to enable the use of shared sockets. If this parameter is set to TRUE， the network listener passes the socket descriptor for client connections to the database thread. As a result， the client does not need to establish a new connection to the database thread and database connection time improves. Also， all database connections share the port number used by the network listener， which can be useful if you are setting up third-party proxy servers. On Windows NT 4.0 Service Pack3 or earlier， enabling this option precludes bringing the network listener up or down in a case where a database connection spawned by the network listener is active. Therefore， you may need to shut down all of the databases serviced by a network listener before you can bring down and restart a network listener. This results from the way shared sockets have been implemented in WINSOCK2. WINSOCK2 does not allow a reliable thread to a network listener on any port on which other connections are also active. This is not an issue on Windows NT 4.0 Service Pack 4 orlater. oracle recommends that you upgrade to Windows NT 4.0 Service Pack 4 if you intend to set this parameter. This parameter only works in dedicated server mode in a TCP/IP environment. If this parameter is set， you cannot use the 8.1.5 listener to spawn oracle 7.x databases. To spawn an oracle 8.0.x database from an 8.1.5 listener

oracle客户端连接服务器，首先去找1521监听端口，服务器的1521监听端口再向server process进程发出请求，并返回一个随机端口，返回给客户端，客户端再来连接这个端口。 这样就给服务器上的防火墙设置带来了麻烦，这个端口是随机的，如何开放? windows 平台上的这个问题成了一大难题，很多都有人问，但很少有人能解决。 unix平台不用担心，系统自动会解决这个问题. windows 平台上的这个问题成了一大难题，很多都有人问，但很少有人能解决。 unix平台不用担心，系统自动会解决这个问题. Matalink上提供了三种解决办法，实际上USE_SHARED_SOCKET 是最有效最方便的。但经过无数次实现，仍然没有成功，最后终于发现是Oracle 8.1.7的bug 需要打补丁，升级到Oracle 8.1.7.1.2 需要在MTS模式下（共享模式） 需要在MTS模式下（共享模式） oracle默认是专用模式。 经试验发现，如果不在init文件中设参数的话，Oracle仍然会要求一个随机端口和1521端口来共同通只是这个随机端口，并不随客户端会话和登录的变化而变化，在没有重启服务器时，是固定的。 经试验发现，如果不在init文件中设参数的话，Oracle仍然会要求一个随机端口和1521端口来共同通只是这个随机端口，并不随客户端会话和登录的变化而变化，在没有重启服务器时，是固定的。 （试验发现，在专用模式下，每次连接，oracle服务器会按+1方式，提供一个非1521的端口。） 所以，还需要在init.ora文件的最后加上一条参数： mts_dispatchers=“"(address=(protocol=tcp)(host=myoradb)(port=1521))(dispatchers=1)“" 这样才真正实现只用一个端口，穿过防火墙。 这样才真正实现只用一个端口，穿过防火墙。 参考资料: oracle uses dynamic ports under windows NT because of a bug in windows， so oracle can’t use shared sockets. This bug got fixed with service pack 3 I think. By default， oracle uses the dynamic ports without caring which service pack is installed. There is a registry setting to force oracle to use shared sockets. The parameter is (what a surprise!) USE_SHARED_SOCKET in LOCAL_MACHINESoftwareOracleHomeX where X is your desired homedir. This parameter should be set to TRUE. There’s a whitepaper from oracle for this too， somewhere on their site. Anyway， this parameter doesnt work for 8.1.7 Some users reported that it worked with 8.1.6.3， but 8.1.7 termiates every conection immediately... oracle uses dynamic ports under windows NT because of a bug in windows， so oracle can’t use shared sockets. This bug got fixed with service pack 3 I think. By default， oracle uses the dynamic ports without caring which service pack is installed. There is a registry setting to force oracle to use shared sockets. The parameter is (what a surprise!) USE_SHARED_SOCKET in LOCAL_MACHINESoftwareOracleHomeX where X is your desired homedir. This parameter should be set to TRUE. There’s a whitepaper from oracle for this too， somewhere on their site. Anyway， this parameter doesnt work for 8.1.7 Some users reported that it worked with 8.1.6.3， but 8.1.7 termiates every conection immediately... Contributed by Arne Brutschy