Update(11th July 2018)
One of the visitors said the following:
“Just some minutes after my post I found a clue. The problem for my was that my machine name was longer than 15 characters!! If your computer name is longer than that then this error rises. I don’t understand why this should be a problem nowadays.” visitor Ax is referring to the area of the post where I am discussing about Admin Share related issues.
As I never had a box having names longer the limited number of characters, haven’t had this experience. Thanks Ax for the great tip!
Have you noticed the major changes with the installation media of Oracle 12c database release 2? Oracle has made it as a single package, eliminating the user to merge the folders from 2 different installation media to get it done. While I welcome such a move from Oracle with whole heart, once again there are few difficulties getting the software installed properly.
One of the major issues is, when the administrator decides to disable hidden admin shares to secure the box from accessed using C$, D$ calls from a remote machine with domain/local administrative privileges. Disabling the admin shares are handled by tweaking the registry & easily forgotten in the long run. Lack of earlier experiences with installing Oracle software could force one to finally formatting the box to address the registry tweaking for disabling the admin shares.
Few of the errors present are like following:
And the error message reads like following:
Cause – Failed to access the temporary location. Action – Ensure that the current user has required permissions to access the temporary location. Additional Information:
– PRVG-1901 : failed to setup CVU remote execution framework directory “C:\Users\username\AppData\Local\Temp\CVU_220.127.116.11.0_username\” on nodes “hostname” – Cause: An operation requiring remote execution could not complete because
the attempt to set up the Cluster Verification Utility remote
execution framework failed on the indicated nodes at the
indicated directory location because the CVU remote execution
framework version did not match the CVU java verification
framework version. The accompanying message provides detailed
failure information. – Action: Ensure that the directory indicated exists or can be created and
the user executing the checks has sufficient permission to
overwrite the contents of this directory. Also review the
accompanying error messages and respond to them. Summary of the failed nodes hostname- Version of exectask could not be retrieved from node “hostname” – Cause: Cause Of Problem Not Available – Action: User Action Not Available – Version of exectask could not be retrieved from node “hostname” – Cause: Cause Of Problem Not Available – Action: User Action Not Available
Hence, the 1st place to look for is the registry, precisely, Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and to make sure that a REG DWORD named “AutoShareWks” exists with a value “0”. If yes, change the value to “1” and restart the box.
2nd, if you have a 32bit Oracle client installed prior attempting to install the 12c/11g 64Bit database, make sure you Stop “OracleRemExecServiceV2” service using the Windows Service console. There is a conflict between the 32Bit & 64Bit installation procedures and unless this particular service is stopped, the 64Bit installation will not proceed.
Now attempt the 12c/11g 64Bit database installation.
If you come across more errors, please update us using the comments section and we would love to investigate them.