How to solve the problem that monitoring cannot be started after reinstalling oracle

This article introduces how to solve the problem that monitoring can not be started after reinstalling oracle. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

You need to uninstall the existing oracle and then reinstall oracle.

I just heard a friend say that if you uninstall the registry when you uninstall oracle, otherwise you can't install it normally. I thought I didn't believe it at that time, but I encountered this kind of problem today.

Reinstalled oracle, found that OEM can not enter, and can not practice with SQL Devloper, error message shows: connection adapter error, listening can not start normally, check the local name, found that everything is normal. Check the service, start OracleTNSListener manually and find that it cannot be started. Right-click to check the properties and find that the path of the executable file points to the directory of the previous oracle (maybe you won't have this problem when you install it from the original directory when you install it again), and finally find the problem.

Modify method:

1.regedit.exe

two。 Open the registry and modify to find HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/

The location of OracleTNSListener's ImagePath

In addition, in a previous blog post, I learned from the command sc that introduced the windows manipulation system service, such as:

Sc create Tomcat binPath= F:/apache-tomcat/bin/startup.bat start= auto

Sc delete Tomcat

I believe he can also be effective in solving this problem.

Quick setup of Windows2000/xp/2003 system Services

Sc.exe Management system Services

Windows adds system services and glassfish bat startup files

This is how to solve the problem that monitoring cannot be started after reinstalling oracle. I hope the above content can be helpful to you and learn more knowledge. If you think the article is good, you can share it for more people to see.