Oracle客戶穿越防火墻難題
2024-08-29 13:29:23
供稿：網友
近來由于工作需要，在windows xp平臺上安裝了oracle9i數據庫作為測試之用,一切正常。但當客戶機連接服務器時卻總是超時，我首先想到了防火墻，當我打開1521端口時，連接操作仍然失敗。我又懷疑網絡有問題，用telnet server_ip:1521嘗試，連接被接受，說明1521端口已經被打開。
沒有辦法，查詢oracle資料后才明白，network listener 只起一個中介作用，當客戶連接它時，它根據配置尋找到相應的數據庫實例進程，然后spawned一個新的數據庫連接，這個連接端口由network listener傳遞給客戶機，此后客戶機就不再和打交道了，即使listener停止了工作。這個新的連接端口是不可預知的，因而會被防火墻阻止。
windows socket2 規范有一個新的特性，就是shared socket， 所謂共享套接字是指一個進程共享另一個進程的套接字(詳見msdn相關參考）。如果讓network listener與數據庫服務進程共享套接字，那么連接端口就不會變化。
如何設置 shared socket?
在注冊表：hkey_local_machine oftware/oracle/home0上新建一個字符串值：use_shared_socket=true。如果安裝了多個目錄，則每個類似的目錄都要設置：hkey_local_machine oftware/oracle/homex (x目錄編號）
設置后要求重新啟動實例（只重啟listener發現沒有效果）
引用資料：
http://www.computer-book-authors.org/aud_450.htm
典型問題：
http://www.lazydba.com/oracle/0__37815.html
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
==============
