Open Terminal and execute this (without the quotes): "/usr/libexec/java_home -v 1.8"
You have to see the Java home path (something line this: /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home)
Copy it and then execute this: /Applications/OracleDataModeler.app/Contents/Resources/datamodeler/datamodeler/bin/datamodeler
It will ask for Java home path, paste it and hit Enter. Data Modeler will start normally.
That's it. Next time you will be able to open Data Modeler as usual.
Thanks, helped me as well.
It is not working for me. Can you please look into this and help me troubleshoot it. The download tells me that the package is damaged. Tried many times.
There are MD5 checksum hashes for every downloads on Oracle Data Modeler download page.
Download Data Modeler for MacOS and then open Terminal, navigate to download folder and execute: md5 datamodeler-220.127.116.11.1216-macosx.app.zip
If the hash (after = sign) matches the one published on the download page you are good to go.
Thank you Ivan,
The MD5 checksum has always been matching. However, the "datamodeler-18.104.22.168.1216-macosx.app" would still complain as being damaged.
I had to right click this file and then select: "Show Package Contents" in order to extract the "OracleDataModeler.app" file to the Applications folder.
Then running this in an initial terminal session:
prompted to type full java path.
Executing this: "/usr/libexec/java_home -v 1.8" in a second terminal session provides the full java path which needs to pasted into the initial terminal session to set the full java path.
That provided a working solution for me.
I hope this helps others.
Thanks!, It worked!, well, more-less.
The actual paths in my Mac were somewhat different. The full path for the java_home, in my case was:
/System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java_home -v 1.8
the rest of the process worked as adviced. Thank you so much!, I learned to use Data <modeler in a windows laptop, I wanted to use it in my Mac.
By the way, I have the new macOS Catalina 10.15.2 update, maybe that's the cause of the difference in the paths.