7.oracle Learning Portal Series Seven---network Management and configuration

Oracle Learning Portal Series Seven

Network Management and Configuration

We learned about patterns and users. Contains the schema definition and the role of the pattern.

Let's take a look at the network management and configuration in the Oracle database. It seems that this article and the previous article did not inherit AH. How does that look?

Ok, in fact ... we're going to go down.

The network configuration of the database is a relatively basic but also important. Assuming a database is not connected to the outside world, then he is an isolated resource that basically confirms that this is a useless database system.

As we have said before in the database definition, the database needs to be shared by many users, and there is no network to share it. Yes, not right. That must not be a 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, not easy to go deep, talk about the configuration we say the configuration, not the other.

The Oracle network is convenient, and when we have completed the Oracle database installation, we are able to bring up the network configuration interface through the Oracle user input NETCA command.

(about how the database is installed or not.) Be able to view the Toad Environment Deployment series. No longer wordy here.)

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

Just say the network, is generally sent by the receive, just like our network programming. If you create a socketserver then you have to socketclient. Otherwise the server is waiting (just the server's job 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. One is configured on the client.

1.1 File Listener.ora

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

Check listener configuration is the monitoring of the database, very convenient.

Configurations include add, reconfigure, delete, rename, and most often use Add and remove.

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

Delete is the deletion.

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

After the configuration is finished, it will be started by default, LSNRCTL status can be viewed by command, and service is started.

Just have the monitor normal, the client ability Barrier-free link to.

It had to be wordy, when Toad was just touching Oracle. I have a colleague who listens to a bad deal every time, and then discovers a thing.

The colleague was very impatient. Each time through the command Lsnrctl start, immediately with the command lsnrctl status View, found the server up, immediately in the client with tnsping service. Found not to pass. 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 in the client, through the NETCA command, bring up the UI after configuration, not to be continued.

Copyright notice: This article Bo Master original article. Blog, not reproduced without consent.

7.oracle Learning Portal Series Seven---network Management and configuration