Oracle Database Listener Configuration

Listener is a server-based network service of Oracle. It is mainly used to listen for connection requests from clients to database servers. Since it is a server-based service

Listener is a server-based network service of Oracle. It is mainly used to listen for connection requests from clients to database servers. Since it is a server-based service

1. LISTENER (LISTENER)

Listener is a server-based network service of Oracle. It is mainly used to listen for connection requests from clients to database servers. Since it is a server-based service, it only exists on the database server, and listener settings are also completed on the database server.

2. Local Service name (Tnsname)

The connection between the Oracle client and the server is a connection request sent by the client. The server listener checks the client connection request legally. If the connection request is valid, the connection is performed. Otherwise, the connection is rejected.

The local service name is a type of network configuration for the Oracle client, as well as the Oracle Names Server. The common client configuration in Oracle is the local service name. This article describes the configuration based on the local service name.

Iii. Oracle network connection Configuration

Both the Oracle server and client can be configured in their own graphical Oracle Network Manager (Oracle Net Manager) (we strongly recommend that you configure the Oracle server or client with this graphical tool ). In Windows, click Start/Program/Oracle-OraHome92/Configuration and Migration Tools/Net Manager to start the Oracle network Manager tool. In Linux/Unix, use the netmgr command to start the graphical Oracle network manager, for example:

$ Netmgr

In Windows, the Net Manager image window is displayed as follows:

Figure (1)

1. Oracle LISTENER configuration (LISTENER)

As shown in figure (1), select the listener item in the tree directory, click "+" on the upper left side to add the listener, and click the listener directory, by default, the added LISTENER name is LISTENER (this name can also be named by any valid character ). Select the name, select "listener location" from the drop-down menu on the right of the window, and click the Add address button. Select "TCP/IP" from the Protocol drop-down option in the Network Address Bar, and enter the host name or IP address in the host text box (if the host is used as the server or as the client, either of the two items is valid. If the host acts as the server and needs to be connected over the network, we recommend that you enter an IP address.) in the port text box, enter a digital port. The default value is 1521, you can also customize any valid digital port. The configured listening location is shown as follows:

Figure (2)

Select "Database Service" from the drop-down list on the right of the window, and click "add Database. In the displayed database column, enter the global database name, for example, myoracle. Note that the global database name is different from the data warehouse SID. The global database name actually controls the uniqueness of the global database name in the same network segment through the domain name, such as the domain name controller in Windows, for example, enter myoracle.192.168.1.5. You can enter the SID for the Oracle main directory, for example, myoracle. Shows the complete database service configuration:

Figure (3)

Save the preceding configurations. By default, you can find the Listener Configuration file in the Oracle Installation Directory (for example, D: oracleora92networkadminlistener in Windows. ora, $ ORACLE_HOME/network/admin/listerer in Linux/Unix. ora ). So far, the Listener Configuration for the Oracle server has been completed.