How to open the Oracle service port on the firewall

The Oracle service port has many problems. The following describes how to open the Oracle service port on the firewall. It is helpful for you to learn about the Oracle service port.

To enable the Oracle client to connect to an Oracle server installed on windows with a firewall, it is not enough to open a 1521 or custom listening port.

Sometimes we need to map the port to remotely access the Oracle database. There is a firewall problem here. There is no problem on unix, but it cannot be accessed correctly on win platform, the following can solve this problem ,:

Recently, the Oracle9i database has been installed on the Windows XP platform for testing. However, when the client connects to the server, it always times out. First, I think of the firewall. When I open port 1521, the connection operation still fails. I suspect that the network is faulty. I tried using telnet server_ip: 1521 and the connection was accepted, indicating that port 1521 has been opened.

No way. After querying the Oracle data, you can understand that network listener only plays an intermediary role. When the customer connects to it, it finds the corresponding database instance process according to the configuration, then spawned a new database connection. The connection port is passed to the client by the network listener, and the client will no longer deal with it, even if the listener stops working. This new connection port is unpredictable and will be blocked by the firewall.

The Windows Socket2 specification has a new feature: Shared Socket. The so-called Shared Socket refers to the Socket where one process shares another process (For details, refer to the MSDN reference ). If you want the network listener to share the socket with the database service process, the connection port will not change.

How to Set Shared Socket?

Create a new string value in the Registry: HKEY_LOCAL_MACHINE \ SOFTWARE \ ORACLE \ HOME0: USE_SHARED_SOCKET = true. If multiple directories are installed, set HKEY_LOCAL_MACHINE \ SOFTWARE \ ORACLE \ HOMEx (x Directory number) for each similar directory)

After setting, you must restart the instance and only restart listener)

When the Oracle client connects to the server, it first finds the 1521 listening port. The server's 1521 listening port then sends a request to the server process and returns a random port to the client, connect the client to this port. In this way, the firewall settings on the server are troublesome. This port is random. How can this port be opened?

This problem on windows has become a major problem. Many forums have asked, but few can solve it. There is no need to worry about unix platforms, and the system will automatically solve this problem. Matalink provides three solutions. In fact, USE_SHARED_SOCKET is the most effective and convenient. However, after numerous implementations, it was still unsuccessful. Finally, it was found that Oracle 8.1.7 had to be patched and upgraded to Oracle 8.1.7.1.2.

Shared Mode is required in MTS mode. Oracle adopts dedicated mode by default.

The test showed that if the parameter is not set in the init file, Oracle still requires a random port to communicate with port 1521, but this random port, it does not change as the client session and logon change. It is fixed when the server is not restarted. The experiment found that in dedicated mode, each connection, the oracle server will provide a non-1521 port in the + 1 mode .) Therefore, you must add the following parameter at the end of the init. ora file:
Mts_dispatchers = "(address = (protocol = tcp) (host = myoradb) (port = 1521) (dispatchers = 1 )"
Restart the instance.

Oracle Log File Management

Oracle Password File Management

Oracle read/write file bfilename instance

Oracle XE built-in database creation process

Entire Process of creating acle materialized views