I usually run ODI Studio in a Windows VM or just in an RDP session on a Windows server. But, I run a Mac (a lovely MacBook Pro) and am embarking on something of a local development project, and decided to run ODI Studio natively.
I’m hardly the first one to the party. In fact, I found some great instructions that got me 95% of the way up and running over on a blog article from 2011. I couldn’t quite get ODI to run, however. My default Java JDK is 1.8, but the version of ODI Studio I was trying to run is 126.96.36.199 (yeah yeah, it’s older, I’ll get 12c up and running soon enough…). In short, this version of ODI Studio wants a 1.6 JDK.
So the trick was how to leave my system default JDK at 1.8 but then force ODI to use the 1.6 JDK that’s also installed (just not default).
Normally you can use a SetJavaHome option in a conf file, but this didn’t seem to change anything. I think the ODI launcher tool (which is based on a generic Oracle IDE launcher system) just kept quickly seeing that I have a JAVA_HOME set to a 1.8 JDK, so it was just running with that and not trying anything else. So I dug through the files and found that the launcher will respect a special Java home variable named OIDE_JAVA_HOME, and use that first. So without making any other change, this following can be used on a Mac to force the use of a 1.6 JDK when there is a higher version installed as the default:
Then just run ODI as normal:
After that, ODI Studio launched like a champ with no error messages:
I’m not sure how many people will find this useful (not many), but if this post is like many of my others, I’ll be stuck on this in a couple of years, Google around for a solution, then find my own article and be amazed that I forgot that I solved it…
Hi. Do you have ODI 12c running on Mac OSX Yosemite already? Any help will be greatly appreciated. Thanks!
Hi, just recently switched from Windows 7 to Mac Osx and still using ODI 188.8.131.52. Had it working but somehow it switched to the most recent Java 8 SDK that resulted in errors.
The setting of OIDE_JAVA_HOME in my command script helped a lot!
Good tip, it works on 184.108.40.206.0 as well.
OIDE_JAVA_HOME=`/usr/libexec/java_home -v 1.8`
I tried this on MacOS Sierra and get :
ERROR Exception initializing ‘oracle.odi.ui.OdiAddin’ in extension ‘ODI Navigator
while starting ODI 220.127.116.11.0.
I tried installing ODI locally to see what happens (MacOS Mojava) and I see the same error. The entire ODI Studio interface seems a little glitchy. Even though it showed the error it still actually loaded but it was hard to read the menus. I managed to pull up the ODI Preferences using Cmd+, and changed the theme to Mac OS X (instead of Oracle). This helped a lot of with the menu rendering, but still there is the error. And it doesn’t seem that a lot of things work, for example, I can’t seem to actually connect to a repository, and I can’t even create a new repository. I’m not sure if Oracle is investing a lot of time or energy into maintaining ODI Studio on a Mac. This seems like kind of a shame because it almost seems to work, but for a few issues.