PL/SQL Developer Connection Oracle database detailed configuration method

In recent times, many users have raised the issue of monitoring configuration, client terminal (client) can not connect to the server side (server). This article is a brief introduction to the monitoring configuration, give the SQL Developer Connection Oracle database detailed configuration method, and put forward some customer terminal can not connect the server-side of the solution, willing to the vast number of netizens and readers have some help.

First, Listener (LISTENER)

The listener is an Oracle server-based network service that listens to client connection requests to the database server side. Since it is based on server-side services, it only exists on the database server side, and the listener settings are also done on the database server side.

Second, Local Service name (Tnsname)

The Oracle client-server connection is a connection request made through the client, a client connection request is legitimately checked by the server-side listener, and the connection is rejected if the connection request is valid.

The Local Service name is one of the Oracle client network configurations, plus the Oracle name server (Oracle Names server).  Oracle's Common client configuration is the local service name, and is primarily based on the local service name configuration.

Third, Oracle Network Connection Configuration method

Configuring the Oracle Server side and client can be done in their own graphical Oracle Network Manager (Oracle Net Manager) (it is highly recommended to complete the configuration of the Oracle service side or client under this graphical tool). The Windows Startup Net Manager graphics window looks like this:

1. Oracle Listener configuration (LISTENER) as shown, select the Listener in the tree directory, and then click on the upper left "+" button to add listeners, click on the Listener directory, the default new listener name is listener (the name can also be named by any legal characters). Select the name, select "Listening Location" in the drop-down option in the right column of the window, and click the Add Address button. Select "TCP/IP" in the Protocol drop-down option in the network address bar that appears, enter the host name or the address in the Host text box (if the host is used as the server as the client, one of the two entries is valid; If the host is a server and requires a network connection, the IP address is recommended), Enter a digital port in the Port text box, which is 1521 by default, or you can customize any valid digital port. The configured listener locations are as follows:

Select "Database Service" in the drop-down option in the right column of the window and click the Add Database button. Enter the global database name in the database column that appears, such as MyOracle. Note that the global database name differs from the database SID, and the global database name actually controls the uniqueness of the global naming of the database within the same network segment, such as the domain controller under Windows, where you can enter myoracle.192.168.1.5. The Oracle home directory can be entered without filling in the SID, such as MyOracle. The complete database service configuration is as follows:

Save the above configuration, the default is to locate the listener profile under the Oracle installation directory (Windows D:/oracle/ora92/network/admin/listener.ora

At this point, the Oracle server-side listener configuration is complete.

2. Local Service name configuration (tnsnames)

The local service name is based on the Oracle client-side network configuration, so if the client needs to connect to the database server for operation, the client needs to be configured to be attached to any PC that wants to connect to the database server or to the database server itself. As described earlier, the Oracle client configuration can be completed using the graphical management tools Net Manager that comes with Oracle. Select the service name in (a), then click the "+" button on the top left to pop up the dialog box as shown:

Enter the net service name, such as MyOracle, and click Next to enter the Display dialog box:

Select TCP/IP (Internet Protocol) and click Next, as shown in:

Enter the host name and port number. Note that the hostname and port number must be the same as the host name and port number configured by the database server-side listener. Click Next, as shown in:

Select the (oracle8i or later) service name and enter the service name. The service name here is actually the global database name in the database server-side listener configuration, which must be the same as the former. Connection types usually choose a dedicated server, depending on the configuration of the database server, if the configuration of the shared database server, the connection type here is the choice of a shared server, otherwise it is recommended to select a dedicated server (for the introduction of a dedicated server see related documents). Once configured, click Next, as shown in:

If the database server-side related services are started, you can click the Test button to test the connection. Oracle defaults to a test connection through the Scott/tiger user, and since the Scott user is a sample user with Oracle, the user may not be configured for a formal business database or a professional test database, so changing to a valid user login is likely to test successfully. If the test connection here is unsuccessful, it does not matter, first click Finish button to end the configuration. Go back to the Oracle Network Manager (Oracle Net Manager) main window and save the configuration by default to locate the local Service name profile under the Oracle installation directory (Windows d:/oracle/ora92/network/ Admin/tnsnames.ora). Configure the completed local service name as shown:

Service naming under the tree directory can be changed to a service name consisting of any legal character by renaming the menu in the Edit menu, note that the service name must not have a space character before it may not connect to the database server.

  After the configuration is complete, oracle client should be able to connect to remote oracle  database.

3, using pl/sql developer connecting database

You can connect to the database.

Go to: http://www.cnblogs.com/DebugLZQ/archive/2012/06/27/2565476.html

PL/SQL Developer Connection Oracle database detailed configuration method