You may remember from a previous episode that we added the ability to scan your code for SQL Injection Vulnerabilities.
New Feature: SQL Performance Health Checks The database does all the work, we just kick things off via the PL/SQL API. And since there’s a PL/SQL API, that means we (Oracle, in this case, the Data Guard team), can build a SQLcl command for it. If you’re on 19c or higher, the Data Guard Broker is now available to be managed via it’s PL/SQL API. New Feature: Data Guard commands for the Broker If you don’t have JAVA_HOME set, we’ll default to the Registry (on Windows) to tell us where it is. Java Runtime only recognizes class file versions up to 52.0 If you continue to try to run with Java 8, you’ll see a variation of: Error: A JNI error has occurred, please check your installation and try againĮxception in thread "main" : oracle/dbtools/raptor/scriptrunner. If you’re using JAVA_HOME, make sure it’s set to at least Java 11. On Windows we’ll inspect the JAVA_HOME OS environment variable. It’s easier to tell SQLcl where to find Java now on Windows.
That means we build and test for those versions of the Oracle Java runtime and development kits. Officially we will support Oracle Java 11 and 17. Starting with the 22.1 release cycle, Oracle Database Tools (ORDS, SQLcl, SQL Developer, Data Modeler) will no longer support Java 8. We now have long term support releases 11 & 17 as well. Java 1.8 or Java 8 has been around since 2014. SQLcl gets quarterly updates and it’s again that time of year!ĭOWNLOAD NOW - this is the ‘latest’ link, you can permanently bookmark this.
0 kommentar(er)
