Error starting service. OracleMTSRecoveryService not found

Question

I get this error when installing oracle 11g Enterprise Edition on Windows 7 Professional 64 bit. I checked the registry, as some people say, but the right thing is already there. If you try to start the service from Services.msc, then it also will not report that the wss service was not found.

Answer 1

I ran into this problem and solved:

When you get the error popup, leave it open, open regedit and change ImagePath in the following key to indicate the correct location:

computer\hkey_local_machine\system\controlset001\service\OracleMTSRecoveryService

The correct location might be something like this:

C:\app\myaccount\product\11.2.0\dbhome_1\bin\omtsreco.exe

All loans: http://yuanmengblog.blogspot.com/2011/08/oracle-standard-db-install-issue-with.html

Answer 2

The oracle load was divided into two parts. If you tried to install only one part, this will display a lot of errors and after installation oracle will not work. Download the two parts of the oracle from the official site and remove it in the same place. Files are automatically merged into one folder.

Now install oracle. If you already installed oracle once. It was supposed to go the next way.

On my system, " E: \ app \ INDP \ product \ 11.2.0 \ dbhome_1 ... "

If you install the second time, the installation will take the path, " E: \ app \ INDP \ product \ 11.2.0 \ dbhome_2 ... "

Now the aforementioned erorr will appear due to the registry. So now you need to change the registry value as shown below.

• ctrl + R will display a run window. Type regedit and click ok
• Then, under "Computer," select HKEY_LOCAL_MACHINE → SYSTEM → ControlSet001-> Services → OracleMTSRecoveryService.
• Double-click ImagePath. This will bring up a window with the old path or the wrong path for the data values.
• Now you need to edit it using the current path as shown below.
• E: \ app \ INDP \ product \ 11.2.0 \ dbhome_2 \ bin \ omtsreco.exe OracleMTSRecoveryService

Now click the "try again" button in the window that showed this error. Now it will work like a charm.