7. oracle learning starter Series 7-network management and configuration, 7. oracle Network Management

7. oracle learning starter Series 7-network management and configuration, 7. oracle Network Management

Chapter 7 of oracle learning starter Series

Network Management and Configuration

In the previous article, we learned about models and users, including the definition of models and the role of models. In this article, I will take a look at the network management and configuration in the ORACLE database. However, this article does not seem to inherit from the previous article. What should I do?

OK, actually ..... Cough ..... Let's continue.

The network configuration of a database is basic but important. If a database cannot connect to the outside world, it is an isolated resource, basically, it can be confirmed that this is a useless database system.

As we have mentioned in the definition of the database, many users need to share the database. Why not share the database over the Internet? No, it must be a database.

The preceding summary explains why the network is needed. Let's see how to configure the network.

My mailbox: appdevzw@163.com

Public Account: HopToad

Welcome from all walks of life

 

1. Network Configuration

As it is an entry-level series, it is not easy to go into depth. Let's talk about the configuration, and we will not talk about other configurations.

The ORACLE network is very convenient. After installing the ORACLE database, you can run the netca command to bring up the network configuration interface. (For details about how to install the database, you can check the deployment series of the environment in the future. I will not hesitate here)

This interface allows us to configure the ORACLE network from now on. Mom no longer has to worry about configuring the ORACLE network.

However, the network is generally sent and received. Just like our network programming, If you create a SOCKETSERVER, you have to use SOCKETCLIENT, otherwise, the SERVER is waiting (but the SERVER is waiting ).

ORACLE network configuration involves two files: listener. ora and tnsnames. ora. One is configured on the database system, and the other is configured on the client.

1.1 file listener. ora

You can enter netca in ORACLE to call up the UI configuration interface.

Selecting Listener configuration is very convenient to configure database listening.

Configuration includes adding, resetting, deleting, and renaming. The most common configuration is adding and deleting.

Add a new listener. ora file in the $ ORACLE_home/network/admin/directory.

Delete is Delete.

Of course, if there is a file under this path, you can edit it.

After the configuration is complete, it is started by default. You can run the lsnrctl status Command to check whether the service is started.

The client can provide accessible links only when the listener is normal.

I had to make a fuss about it. When I first got in touch with ORACLE, I had a colleague who listened to it and failed to handle it each time. Then I found something. This colleague was very anxious. After each command of lsnrctl start, he immediately used the command lsnrctl status to check and found that the server was up, and immediately used the tnsping service on the client. My colleague did not talk about lsnrctlstop, changed the listner. ora file, and started it again. Sometimes it was successful, and my colleague complained about the bad ORACLE.

Later, I came to support this colleague. When I found this problem, I told the colleague not to worry too much. Wait. Sure enough, in fact, the client's tnsping will be okay, and people also need time to start it.

 

1.2 file tnsnames. ora

This file is configured on the client. after calling the UI through the netca command, the configuration is not complete yet.