7.oracle Learning Introduction series of seven---network Management and configuration

Oracle Learning Starter Series VII

Network Management and Configuration

We learned about patterns and users, including pattern definitions and the role of patterns. In this article, I look at the network management and configuration in the Oracle database, but this seems to have no inheritance from the previous article.

Ok, actually ... we're going to go down here.

The network configuration of the database is relatively basic but also very important, if a database is not connected to the external world, then he is an isolated resource, basically can confirm that this is a useless database system.

As we have said in the database definition, the database needs to be shared by many users, and there is no network to share it. Right, that must not be the database.

The previous summary has explained why the network is needed, so let's look at how to configure the network.

I e-mail:[email protected]

Public Number: Hoptoad

Welcome to communicate with all

1 Network configuration

Because it is the entry series, it is not easy to go deep, to tell the configuration we say the configuration, not the other.

Oracle network is very convenient, and when we have completed the Oracle database, we can bring up the network configuration interface through the Oracle user input NETCA command. (about how the database is installed, you can follow up to see the Toad Environment Deployment series, here no longer wordy)

This interface allows us to configure the Oracle network from now on to the road of no return, mother no longer have to worry about us to configure the Oracle network.

However, the network, the general is sent to receive, like our network programming, you create a socketserver that you have to socketclient, or the server is waiting (but the job of the server is to wait).

Oracle network configuration mainly involves two files one is Listener.ora one is Tnsnames.ora. One is configured on the database system side, and one is configured on the client.

1.1 File Listener.ora

The UI configuration interface can be paged out via Oracle user input NETCA.

Select Listener configuration is the monitoring of the database, very convenient.

Configurations include add, reconfigure, delete, rename, and the most common are additions and deletions.

Add a new Listener.ora file in the $oracle_home/network/admin/directory

Delete is the deletion.

Of course, if there is a file under the path you can go to the editor to see.

After the configuration is completed by default will be started, through the command Lsnrctl status can be viewed, whether a service is started.

Only the monitoring is normal, the client can be a barrier-free link.

It had to be long-winded, when Toad just contacted Oracle, I have a colleague listening to each processing is not good, and then found a thing. This colleague is very impatient, every time through the command Lsnrctl start, immediately with the command lsnrctl status View, found that the server up, immediately in the client with tnsping service, found that not through. Colleagues apart lsnrctlstop off, and then change Listner.ora files, and then start, and sometimes succeed, the colleague kept complaining about the rotten Oracle.

Later Toad also to support the colleague, found this problem, told the colleague not too urgent, and so on. Sure enough, in fact, a little bit of the client's tnsping on the pass, they also need time to start.

1.2 File Tnsnames.ora

This file is configured on the client side via the NETCA command, which brings up the UI after configuration and is not adjourned.

7.oracle Learning Introduction series of seven---network Management and configuration