Hello,
We have run into some issues previously and opened Oracle SRs in regards to this and never really got a good answer and hoping perhaps we can get to the bottom of it.
Let me describe a couple scenarios and see if these could be caused by a common thread:
1. We installed a standalone ODI installation on a Windows 2012 server along with a Java JDK (I think version 8.141 at the time) and were able to completely setup and configure a repository. The version of Java was updated to 8.161 and no matter what we did when trying to run the config.cmd it continually referenced the original java path C:\Program Files\Java\jdk1.8.0_141 even after manually setting the PATH system variable and JAVA_HOME variable to the new C:\Program Files\Java\jdk1.8.0_161.
-Solution at the time was to uninstall JDK 8.161 and re-install the JDK 8.141 and we were able to create the domain
2. We installed another standalone ODI installation on a Windows 2012 server, but this time we needed to install the applications on the D:. Java was installed in a Program Files on D as well as installing Oracle. We ran into issues running the RCU referencing looking a path D:\Oracle\Middleware\Oracle_Home\jdk\jre\bin to find the Java.exe so to workaround that we copied over the contents of the D:\Program Files\Java\jdk1.8.0_161\bin. We were successful in running the RCU and creating a repository. Now we are running into what seems like a similar issue, but the error we get when running the config.cmd is:
'D:\Program" is not a valid application
It appears that the space in the path to the JDK is causing an issue when the config.cmd is pulling from a preference file somewhere with the original path. I checked the following:
A. product.conf in the user's roaming appdata folder located C:\Users\mfanning\AppData\Roaming\odi\12.2.1
B. Setting the JAVA_HOME to the directory we moved the files from the Java install to get the RCU to run
Any ideas? Is there a directory/file/registry entry that contains a java path?
It seems like the path with the space is causing issues, but we have never run into this when installing Java on C:?
Thank you for any assistance.
Matthew Fanning