Oracle 12c Installation failed to access the temporary location

Question

I have Windows 8.1 64-bit OS running on 64-bit architecture. I am installing a fresh copy of Oracle 12C, means I haven\'t installed any version before on my system.

Answer 1

My problem was that I had the Server service stopped and this gave exactly this same issue. So started the Server service and the installation worked.

Answer 2

Try cleaning your hosts file.

I spent about half a day on this, and none of these answers worked for me. I finally found the solution hinted at on OTN (the last place I look when I run into Oracle issues), and someone mentioned looking at the hosts file. I had recently modified the hosts file because this particular machine didn't have access to DNS.

I had a line for this host:

123.123.123.123     fully.qualified.domain.name.com     hostname

Commenting out the line above allowed me to install the Oracle client.

Answer 3

The error is caused due to administrative shares are being disabled. If they cannot be enabled then perform the following workaround:

6.2.23 INS-30131 Error When Installing Oracle Database or Oracle Client

If the administrative shares are not enabled when performing a single instance Oracle Database or Oracle Client installation for 12c Release 1 (12.1) on Microsoft Windows 7, Microsoft Windows 8, and Microsoft Windows 10, then the installation fails with an INS-30131 error.

Workaround:

Execute the net share command to ensure that the administrative shares are enabled. If they are disabled, then enable them by following the instructions in the Microsoft Windows documentation. Alternatively, perform the client or server installation by specifying the following options:

• For a client installation:

  -ignorePrereq -J"-Doracle.install.client.validate.clientSupportedOSCheck=false"

• For a server installation:

  -ignorePrereq -J"-Doracle.install.db.validate.supportedOSCheck=false"

This issue is tracked with Oracle bug 21452473.

Source: Oracle Database Release Notes (Section 6.2.23)

Answer 4

You can configure setup.exe to skip this check using the parameters below -

setup.exe -ignorePrereq -ignorePrereq -J"-Doracle.install.db.validate.supportedOSCheck=false"

Answer 5

(Solution) Same problem: Windows 10 vs. Oracle 11g (11.2.0.4)

The problem arises again with the final release of Windows 10 (and Server 2016 Preview 3 too) using e. g. Oracle 11g (11.2.0.4, 64 bit) after installation tasks worked fine with several preview builds of Windows 10. All things said above are o. k. resp. do not work.

The ultimate cause is an incompatibility of OracleRemExecService (vs. RemoteExecService.exe): as known, at the beginning of installation process it is created via %TEMP%\oraremservice. If you watch it e. g. with Sysinternals' ProcessMonitor using an appropriate filter, you can see several crashes (the most of them with "buffer Overflow") and restarts, and there are also corresponding with messages in Windows' "System" event log.

If you start (after deleting the HKLM\Software\oracle in the registry) the installation several times (more than three times - see below) it suddenly works. The reason for this behaviour is Windows' "Fault Tolerant Heap" mechanism (see https://msdn.microsoft.com/de-de/library/windows/desktop/dd744764(v=vs.85).aspx) that creates after three attempts within 60 minutes (see http://blogs.technet.com/b/askperf/archive/2009/10/02/windows-7-windows-server-2008-r2-fault-tolerant-heap-and-memory-management.aspx) a FTH entry in HKLM\Software\Microsoft\FTH\State and a corresponding shim in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers. Although the content of the FTH entry is related to the current process of RemoteExecService.exe you can import the registry keys to a system before you start the DB installation. If you set Windows' %TEMP% environment variable and also %TMP% (due to the fact that Oracle uses both directories while creating the things around OracleRemExecService) to a predefined value (e. g. C:\TEMP) you are able to use this for all your installation tasks as follows (unfortunately, it works only with Windows 10, not Server 2016 - updated 2015-09-24, see below):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\Temp\\oraremservice\\RemoteExecService.exe"="FaultTolerantHeap"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\FTH\State]
"C:\\Temp\\oraremservice\\RemoteExecService.exe"=hex:10,00,00,00,10,00,00,00,\
  0c,b4,ff,0c,52,00,65,00,6d,00,6f,00,74,00,65,00,45,00,78,00,65,00,63,00,53,\
  00,65,00,72,00,76,00,69,00,63,00,65,00,2e,00,65,00,78,00,65,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00

Update 2015-09-24: With Server 2016 (Preview 3), it's a little bit more tricky: first you also have to set the environment variable %TEMP% e. g. to C:\Temp and to import the registry keys above (after this, it's no bad idea to restart the system). Than you start the Oracle installation using an additional parameter:

setup.exe -debug

If you watch what happens in %TEMP% you can see that the folder %TEMP%\oraremservice\ is created twice: after first creation, the installer seems to notice that the service does not work, deletes the folder and creates it again. After this, the Installation process works as expected.

Update 2015-11-27: - Using Windows Server 2016 Preview 4, the workaround via "setup.exe -debug" is not necessary anymore; you can proceed as described for Windows 10. - Of course, you do not need the procedure with new C:\TEMP vs. %TEMP% and %TMP% if you have a defined user (e. g. Administrator). Then you can use modified registry items like this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\Users\\Administrator\\AppData\\Local\\Temp\\oraremservice\\RemoteExecService.exe"="FaultTolerantHeap"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\FTH\State]
"C:\\Users\\Administrator\\AppData\\Local\\Temp\\oraremservice\\RemoteExecService.exe"=hex:10,00,00,00,10,00,00,00,\
  0c,b4,ff,0c,52,00,65,00,6d,00,6f,00,74,00,65,00,45,00,78,00,65,00,63,00,53,\
  00,65,00,72,00,76,00,69,00,63,00,65,00,2e,00,65,00,78,00,65,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00

Update 2017-01-31: Tested all builds of Windows 10 (Insider Preview) until now, so we have seen a new problem coming up with build 15002: the Oracle setup isn't able to determine the PATH variable anymore (the variable itself, not a wrong content or so on!). So all attempts to install the Oracle DB fail. Comparing the registry of the Windows versions and "playing around" with this variable and their contents did not help. The only work-around is to edit the related XML file \64bit|32bit\stage\cvu\cvu_prereq.xml and delete in the section all tags ... (or this tag only in the last item "Windows Server 2012"). And btw: despite of we are primary using Oracle 11g this new installation problem also occurs using the up to date setup of Oracle 12c...

Answer 6

Looking at Oracle's support site, it could be one of two things (may be #2 in your case, but including both).

Problem 1:

1. Enable administrative share for C$ (Please check with your System Admin to do this or See Microsoft document http://support.microsoft.com/kb/314984)

2. Check that it is ok:

   • net use \\c$ should work
   • the current user (i.e. user in administrator group) should have all privileges on the default share

3. Retry the installation

4. Remove the administrative share again

Problem 2: Remove the OracleRemExecService before doing the Oracle Client 12c Release 1 32-bit or 64-bit installation on the same Microsoft Windows x64 (64-bit) after installing the Oracle 64-bit or 32-bit software .

• Go to the Windows 'Services'
• Stop OracleRemExecServiceV2

( This service is having a intelligence .Once someone tries to stop it this service gets deleted. This is due to the fact ,that this service is not running from the Oracle Home like other oracle services ,but from temp . For example : C:\Users\AppData\Local\Temp\oraremservi... )

• Then try to install the Oracle 12c 32-bit or 64-bit on the same Microsoft Windows x64 (64-bit)