How to modify monitoring in oracle

Oracle database listener is a program responsible for monitoring database services. Its main function is to provide ports and connections for client operations and maintain communication between the database and the client. When modifications to a listener are required, there are a number of factors and steps that need to be taken into consideration.

Factors that trigger listener modifications usually include: network topology changes, database instance parameter modifications, and security configuration changes. In order for the new configuration to take effect and fill client requests, the listener configuration needs to be modified appropriately. The specific steps are as follows:

Step 1: Check the status of all listeners

Before modifying the listener, First check the status of all listeners. Use the command lsnrctl status to view the current status of the listeners, such as:

LSNRCTL> status Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=yourhost)(PORT=1521))) STATUS of the LISTENER ------------------------ Alias LISTENER Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production Start Date 26-MAY-2019 09:21:48 Uptime 0 days 0 hr. 8 min. 29 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora Listener Log File /u01/app/oracle/diag/tnslsnr/yourhost/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=yourhost)(PORT=1521))) Services Summary... Service "orcl" has 1 instance(s). Instance "orcl", status READY, has 1 handler(s) for this service... Service "orclXDB" has 1 instance(s). Instance "orcl", status READY, has 1 handler(s) for this service... The command completed successfully

Through the above command, you can view the status, version, startup time, service summary and other information of the listeners. If the listener is not running, you need to use the command lsnrctl start to start the listener.

Step 2: Modify the listener configuration file

The listener configuration file is located in the $ORACLE_HOME/network/admin directory and the file name is listener.ora. Before modifying this file, back up the original configuration file. You can use a text editor to open the listener.ora file and modify the configuration. For example, add a new service monitor:

# 添加一个新的服务监听 SID_LIST_LISTENER= (SID_LIST= (SID_DESC= (SID_NAME=test) (ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1) (PROGRAM=oracle) ) ) # 添加监听的IP地址和端口 LISTENER= (DESCRIPTION_LIST= (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=192.168.1.10) (PORT=1521) ) ) ) # 添加新服务的信息 SID_DESC_LISTENER (SID_DESC = (GLOBAL_DBNAME=test) (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1) (SID_NAME = test) )

In addition, you can also modify the parameters of the listener, such as modifying the port number of the listener, using parameter files, etc. Other devices in the network such as switches, routers, firewalls, etc. may also affect the listener and need to be set accordingly according to the actual situation.

Step 3: Restart the listener

After modifying the listener configuration file, you need to restart the listener to make the new configuration take effect. You can stop the listener with the command lsnrctl stop and start it with the command lsnrctl start.

LSNRCTL> stop Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=yourhost)(PORT=1521))) The command completed successfully LSNRCTL> start Starting /u01/app/oracle/product/11.2.0/dbhome_1/bin/tnslsnr: please wait... TNSLSNR for Linux: Version 11.2.0.1.0 - Production System parameter file is /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora Log messages written to /u01/app/oracle/diag/tnslsnr/yourhost/listener/alert/log.xml Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=yourhost)(PORT=1521))) Services summary... Service "orcl" has 1 instance(s). Instance "orcl", status READY, has 1 handler(s) for this service... Service "orclXDB" has 1 instance(s). Instance "orcl", status READY, has 1 handler(s) for this service... The command completed successfully

Step 4: Test the new configuration

After completing the modification and restart of the listener configuration, some tests need to be performed to verify whether the new configuration takes effect. You can use the tnsping tool or a database client connection to test whether the listener can accept client requests. For example, use the tnsping "test" command to test whether the newly added service monitoring is normal.

tnsping test

If information similar to "OK" is returned, it means that the newly configured listener can accept client requests and return responses, indicating that the configuration has taken effect.

It should be noted that when modifying the listener configuration, you need to operate with caution to avoid the loss of the original configuration information and the instability of database access. In actual operations, certain security measures can be taken, such as backing up configuration files, testing modification results, etc., to ensure the normal operation of the database.

The above is the detailed content of How to modify monitoring in oracle. For more information, please follow other related articles on the PHP Chinese website!