Oracle: listener. ora, sqlnet. ora, tnsnames. ora configuration and example

Oracle: listener. ora, sqlnet. ora, tnsnames. ora configuration and example
1. Solve the problem: TNS or the database cannot log on.
The simplest and most effective method: use the tool netca provided by the Oracle System to configure (delete the original one and reconfigure it)
$ Netca 2. However, I still have questions: how do I specify the directory where 'listener. ora 'is stored? Do not default directory ($ ORACLE_HOME/network/admin)

Add in '. profile'

1. TNS_ADMIN =/f01/oracle11/app/oracle/product/8.0.6/network/admin
2. Export TNS_ADMIN

3. Three configuration files

1) listener. ora

2) sqlnet. ora

3) tnsnames. ora

These three files are all stored in the $ ORACLE_HOME/network/admin directory.

1) sqlnet. ora (client and server)

The function is similar to the nsswitch. conf file of linux or other unix systems. This file is used to determine how to find a connection string that appears in the connection,
　　
For example, we enter
　　
Sqlplus sys/oracle @ orcl
　　
Assume that my sqlnet. ora is like the following:

1. SQLNET. AUTHENTICATION_SERVICES = (CNT)
3. NAMES. DIRECTORY_PATH = (TNSNAMES, HOSTNAME)

Then, the client will first be in tnsnames. find the orcl record in the ora file. If there is no corresponding record, try to treat orcl as a host name, resolve the ip address through the network and connect to the instance GLOBAL_DBNAME = orcl on the ip address. Of course, here, orcl is not a host name.
　　
If I look like this

1. NAMES. DIRECTORY_PATH = (TNSNAMES)

　　
Then the client will only search for orcl records from tnsnames. ora
　　
There are other options in brackets, such as LDAP, which are not commonly used.

2) Tnsnames. ora (customer and server)

This file is similar to the unix hosts file. It provides the tnsname to the host name or ip address, only when the sqlnet. ora file is similar
　　
NAMES. DIRECTORY_PATH = (TNSNAMES), that is, the file will be used only when the client parses the order of the connection string that contains TNSNAMES.
　　
In this example, there are two local IP addresses corresponding to ORCL and another IP address corresponding to SALES, which also defines whether to use the master server or Shared Server Mode for connection. The sentence is as follows:

1. # Enter TNSNAME when you want to connect
3. ORCL =
5. (DESCRIPTION =
7. (ADDRESS_LIST =
9. # The host, port, and Protocol corresponding to this TNSNAME
11. (ADDRESS = (PROTOCOL = TCP) (HOST = 127.0.0.1) (PORT = 1521 ))
13. )
15. (CONNECT_DATA =
17. # Use the dedicated server mode to connect to the server. The connection mode must match the server mode. If not, the connection is based on the server mode.
19. # Automatic Adjustment
21. (SERVER = DEDICATED)
23. # Corresponding service_name, SQLPLUS> show parameter service_name;
25. # View
27. (SERVICE_NAME = orcl)
29. )
31. )
33. # The following is similar
35. SALES =
37. (DESCRIPTION =
39. (ADDRESS_LIST =
41. (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.188.219) (PORT = 1521 ))
43. )
45. (CONNECT_DATA =
47. (SERVER = DEDICATED)
49. (SERVICE_NAME = sales)
51. )
53. )

3) listener. ora (server side) -- configuration file of listener process

The listener process is not much said. The listener process accepts remote database access requests and transfers them to the oracle server process. Therefore, if you do not use a remote connection, the listener process is not required. Similarly, disabling the listener process does not affect the existing database connection.
　　
Example of Listener. ora File

1. # Listener. ora Network Configuration File: # E:/oracle/product/10.1.0/Db_2/NETWORK/ADMIN/listener. ora
3. # Generated by Oracle configuration tools.
5. # The following defines the instance for which the LISTENER process provides services
7. # Here Is ORCL, And it corresponds to ORACLE_HOME and GLOBAL_DBNAME
9. # GLOBAL_DBNAME is not required unless you use HOSTNAME for database connection
11. SID_LIST_LISTENER =
13. (SID_LIST =
15. (SID_DESC =
17. (GLOBAL_DBNAME = boway)
19. (ORACLE_HOME = E:/oracle/product/10.1.0/Db_2)
21. (SID_NAME = ORCL)
23. )
25. )
27. # Listener name. A database can have more than one listener.
29. # Next we will talk to the listener about the protocol, ip address, port, etc. Here we use the tcp1521 port and use the # Host Name
31. LISTENER =
33. (DESCRIPTION =
35. (ADDRESS = (PROTOCOL = TCP) (HOST = boway) (PORT = 1521 ))
37. )

　　
The above example is the simplest, but also the most common. A listener process provides services for an instance (SID.

1 2 3 Next Page