Oracle Network Monitoring

This explains my understanding of the Oracle Network (static listening):

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/86/57/wKioL1e8W1XhBxylAABNjdsDQZs648.png "title=" Qq20160823221132.png "alt=" Wkiol1e8w1xhbxylaabnjdsdqzs648.png "/>

How the Listener works:

listening to the white, is a socket +protocol (protocol)

Sockets are the cornerstone of communication and are the basic units that support TCP/IP protocol network communication. You can treat sockets as endpoints for process bidirectional communication between different hosts.

A complete network communication must have 5 basic features, such as protocol, local address, local port, remote address, remote port, and protocol, when the socket is created, the protocol type is determined, and the binding socket determines the local address and local port, the remote address, and the remote port. Sockets are ip+port.

1, after the database started (data files, control files, log files) There is another thing, is Oracle's monitoring, it is a separate Oracle module, it has no intrinsic connection with Oracle database, Oracle data hangs, monitoring can exist, Monitoring off the Oracle database can still be run.

2, the user is connected to the monitoring, listening to know where the database, the user connection on the monitoring, monitoring is responsible for forwarding the user's request, forwarded to the DB instance, the database instance will start a server process process for this listener (and the server The address of the process tells the Listener (listener) that the listener will tell the client the address of the server process, and the client will connect to the server process directly after it has received the address. At this point: the client will give its user name and password to the server process, the server process to get this user name and password to server-side verification, validation passed, the connection is formally established. Since then the operation, and monitoring has nothing to do, once the connection is established, it is useless (even if it is closed), it is only responsible for forwarding, GU Oracle database monitoring almost useless load, under normal circumstances.

3. There is no long link between the listener and the instance, it just knows where the instance of the database is.

4, listening to the database (Server) side only need Listener.ora to the database client will only need to Tnsnames.ora often on the server side also has Tnsnames.ora (because it can also act as a client) listener configuration can be through NETCA (actually generated three files Listerner.ora, Tnsnames.ora, Sqlnet.ora)

Sqlnet.ora not discuss here.

5, monitoring is configured on the server side, through the socket (Ip+port) to provide services outside

Configuring static monitoring First you need to know a few names in the database ....

Show parameter name; (pick a few typical here)

Db_name-----is the name of the database, Oracle itself is more useful, for static monitoring, it is not much use. In the creation of the database, it is recommended to specify the appropriate db_name, late to change very cumbersome, Db_name also has a very important role is to dynamically register the monitoring, regardless of whether the service_name is specified, or the value of server_name, Pmon will use Db_name to dynamically register for monitoring, this should be noted.

Instance_name: DB instance name (and Oracle_sid configured in environment variable)

This name is used by dynamic registration monitoring.

Service_names Database service Name: The service name is a complex number, meaning service_name

Can have more than one.

So please look at the copy from the official website static monitoring example, Global_name should fill in what? Listener.ora

Listener=

(description=

(address_list=

(Address= (PROTOCOL=TCP) (host=192.168.3.3) (port=1521))

)

)

Sid_list_listener=

(sid_list=

(sid_desc=

(global_dbname=prod)

(oracle_home=/u01/app/oracle/product/11.2.0/dbhome_1)

(Sid_name=prod)

)

####################################################################

This is my Tnsnames.ora profile.

Main =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.3.3) (PORT = 1521))

(Connect_data =

(SERVER = dedicated)

(service_name = Pord)

)

)

It is clear here that when configuring the static listener registration, you need to input the global database name (global_dbname) input anything, as long as the Listerner.ora in the Global_dbname and Tnsnames.ora Service_ Name remains consistent

Yes, here's a look at the effect: first I show parameter name; look at each name

[email protected]>show parameter name;

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

Db_file_name_convert string

Db_name string PROD

Db_unique_name string PROD

Global_names Boolean FALSE

instance_name string PROD

Lock_name_space string

Log_file_name_convert string

Processor_group_name string

Service_names string PROD

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/86/73/wKiom1e-5UDRYKDLAABbIbaIyoI144.png "title=" capture. PNG "alt=" wkiom1e-5udrykdlaabbibaiyoi144.png "/> Connection succeeded.

At this point I change the global_dbname in my Listener.ora file to Nimei and change service_name in Tnsnames.ora to Nimei (the two names must be the same) otherwise the connection is not on the instance.

Listener.ora as follows:

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/86/73/wKiom1e-5q-RkRFVAABPrJ4sBM0629.png "title=" capture. PNG "alt=" Wkiom1e-5q-rkrfvaabprj4sbm0629.png "/>

Tnsnames.ora as follows:

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/86/73/wKiom1e-5x2i7oB-AAAr01y1uXk723.png "title=" capture. PNG "alt=" Wkiom1e-5x2i7ob-aaar01y1uxk723.png "/>

At this time do link test ... You can use Tnsping First test to resolve the alias if there is a problem, here I directly connected to the test.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/86/73/wKiom1e-6DnC5OQ-AABV_7eq3Xw794.png "title=" capture. PNG "alt=" Wkiom1e-6dnc5oq-aabv_7eq3xw794.png "/>

Connection Successful!

This article from the "Linux-related technology" blog, declined to reprint!

Oracle Network Monitoring