Shulou(Shulou.com)06/01 Report--

This article introduces the relevant knowledge of "how to solve the error report of oracle monitoring". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

The monitoring of the ORACLE database could not report errors, which was quickly solved. Record the problems encountered here for reference. Should I enter the IP address or the host name after HOST in the database listener.ora file? Many people may have different practices. My experience is that it is best to use a hostname. For example, if a machine is bound with more than one IP address, and you write the IP address after the HOST, then the listener of ORACLE will only listen for access requests with a specified IP address, and connections to other IP addresses on the machine will be rejected. And when you create a listener, the listener.ora file creates the hostname by default. If HOST is followed by a hostname in the listener.ora file, it will have something to do with the file / etc/hosts.

The problem this time is due to the fact that the R & D staff accidentally changed the host name and did not change the correspondence between the host name and IP in the / etc/hosts file.

We read the wrong screenshot of the newspaper:

PMON is found when you look up port 1521 (by default, PMON registers service information with the local listener at the default local address of TCP/IP, port 1521).

# netstat-antp | grep 1521

Tcp 0 1 192.168.1.252:36842 202.106.0.20:1521 SYN_SENT 28794/ora_pmon_orcl

Check 202.106.0.20 where on earth did this ip come from?

I can't believe there is this record in / etc/hosts

202.106.0.20 wxtest

I don't know who added it, but there has never been such a deployment requirement. Forget it, just comment out this sentence.

Restart the database, restart the listening, everything is fine!

Attached picture:

Add: several errors related to / etc/hosts file.

1. / etc/hosts file oracle does not have permission to access

At this time, oracle users will report the following error when they start listening.

TNS-12545: Connect failed because target host or object does not exist

TNS-12560: TNS:protocol adapter error

TNS-00515: Connect failed because target host or object does not exist

Linux Error: 13: Permission denied

2. The IP address corresponding to the hostname in the / etc/hosts file is not properly bound locally

At this time, oracle users will report the following error when they start listening.

TNS-12535: TNS:operation timed out

TNS-12560: TNS:protocol adapter error

TNS-00505: Operation timed out

Linux Error: 110: Connection timed out

This is the end of the content of "how to solve the oracle Monitoring error report". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.