Updated 23 March 2023
SQLcl version 22.1 now has a minVer of 11 for Java. However, we ALSO support the other long term support release of Java, which is currently 17.
Java 11 support expires this September. In addition, Java 17 EE is free. For these two reasons, we recommend you use Java 17 for both ORDS and SQLcl.
However, if you are using Java 17, you may run into a problem if you want to use one of SQLcl’s most powerful features.
- creating custom sql outputs – a Card Format
- loading files from a directory to BLOBs in a table
- exporting BLOBs from a table to a directory
For example in just a few lines of code…
No support for Nashorn in Java 17
The feature was deprecated in Java 11. It was completely removed in Java 15.
Since SQLcl ONLY supports Oracle Java 11 or 17 today, so you need to run 11 if you want to use the script command to work with js. Or do you…
What happens if you try with Java 17?
How to fix it
You have two options:
- Downgrade to Java 11, yeah don’t do that
I’ve picked 17 and Windows, and I simply copied the archive contents to my other GraalVM ‘homes’ –
The download is a single JAR file.
Go to your GraalVM install and its bin directory.
Run this –
gu -L install js-installable-svm-svmee-java17-windows-amd64-22.3.1.jar
Now start SQLcl back up and let’s try running some JS again in SQLcl.
Using JAVA_HOME to tell SQLcl where to find Java
On Windows, the native EXE was previously setup read the Windows Registry to look for Java. It made switching between versions of Java on Windows painful.
IF you use a Windows Installer to put down Java 11/17, it should setup your Windows machine to use it by default, and SQLcl will be impacted by that.
But for any version of SQLcl 22.1 and higher, you can now simply set JAVA_HOME to the Java Home you want the sql.exe to use, and you’re good. Turloch, if you’re reading this, we all say, ‘Thank you!’
c:\>set JAVA_HOME=C:\1-GraalVM\graalvm-ee-java17-22.3.1 c:\>echo %JAVA_HOME% C:\1-GraalVM\graalvm-ee-java17-22.3.1