Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about the case analysis of abnormal Oracle19c database monitoring, which may not be well understood by many people. in order to make you understand better, the editor has summarized the following for you. I hope you can get something according to this article.

Overview

Today, I mainly share a recent surveillance problem, which is interesting. Let's take a look at it.

Environment: oracle19c single instance

Use the plsql connection prompt to eliminate firewall and account password problems. The connection string is written in the listening file format.

1. Test monitoring

The server local test monitor found no problem.

two。 View database status

Database status is normal

3. View monitoring status

Found that there is no database service..

4. View database service name

It is suspected that there is a problem with service_name, and there is no exception in the check.

5. View the error log:

The path is: / u01/app/oracle/diag/tnslsnr/ZL-FSL-SRM-TOOLS-DB/listener/alert/log.xml

04-MAR-2020 17:46:23 * ping * 0 WARNING: Subscription for node down event still pending 04-MAR-2020 17:48:53 * (CONNECT_DATA= (CID= (PROGRAM=) (HOST=ZL-FSL-SRM-TOOLS-DB) (USER=oracle)) (COMMAND=status) (ARGUMENTS=64) (SERVICE=LISTENER) (VERSION=318767104)) * status * 0

There is no obvious abnormality in the log.

6. View listener-related parameters in the database

Compare the listener-related parameters of normal and abnormal databases..

You can find it's different.

7. Modify database listening parameters

Ps: dynamic registration is only registered on the default listener by default (name is LISTENER, port is 1521, protocol is TCP), because pmon only dynamically registers listeners with port equal to 1521, otherwise pmon cannot dynamically register listener. If you need to register with non-default listeners, you need to configure the local_listener parameter.

The listening information is added to the tnsnames.ora file. Because pmon reads relevant information from tnsnames.ora when dynamically registering snooping.

Alter system set local_listener=' (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=TCP) (HOST=xx.xx.xx) (PORT=1522) 'scope=both

8. Restart the monitoring and check the monitoring status

Problem solved.

After reading the above, do you have any further understanding of the case analysis of Oracle19c database snooping exceptions? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.