Oracle SQLcl 24.3.1 Release Notes

SQLcl on OTN | Getting Started Video | Downloads | FAQ | Forum

Issues Fixed in 24.3.1

This patch addresses PROJECT command issues and various bugs fixes:

• 37233653 LIQUIBASE VERSION NOT WORKING PROPERLY
• 37234129 ORA-17090 INSERTING/UPDATING BLOBS
• 36952914 RUNORACLESCRIPT/RUNAPEXSCRIPT NOT WORKING ON WINDOWS
• 37122176 MAKE CONNECTION INITIALIZATION CONSISTENT ACROSS COMMANDS
• 36508290 CALLING A SCRIPT WITH LIQUIBASE HAS PATHING ISSUE ON WINDOWS
• 37209287 CHANGELOGGENERATIONEXCEPTION: UNRECOGNIZED CHARACTER ESCAPE '*'
• 36049881 RUNORACLESCRIPT CHANGESETS WITH RUNONCHANGE RERUN IF PLATFORM CHANGES
• 37107468 GENERATING SQL CHANGESET TRIES TO WRITE TO LINUX DIRECTORY ON WINDOWS
• 36680641 INCONSISTENT DATABASECHANGELOG.FILENAME VALUES FOR RUNORACLESCRIPT




If your bug fix isn’t listed above, please refer to My Oracle Support to check its status.

Support

You are supported by Oracle Support under your current Oracle Database Support license.

Log Oracle SQLcl bugs and issues using My Oracle Support. To determine the version of SQLcl run this command: sql -version

Documentation

Documentation on using SQLcl is provided on the oracle.com website here.

Requirements

• Supported Java Version
  • Oracle SQLcl requires Java 11 or 17 or 21. The supported Java Runtime Environments are:
    • Oracle Java 11
    • Oracle Java 17
    • Oracle Java 21
    • Oracle GraalVM Enterprise Edition for Java 11
    • Oracle GraalVM Enterprise Edition for Java 17
    • Oracle GraalVM Enterprise Edition for Java 21
• JavaScript support requires Oracle Java 11 or GraalVM for Java 17 with the JavaScript Runtime Plugin

Restrictions

This section describes the restrictions on use.

ORACLE_HOME usage

When using an ORACLE_HOME or instant client with SQLcl, the client version must be 23ai.

Liquibase usage with APEX

Liquibase support for APEX requires APEX version 18 and above.

Feedback

In the forum, you can discuss topics with the SQLcl community around the world and leave feedback for the development team.

Be sure to use clear subject lines to initiate a thread. Provide a complete and clear description of the issue, including steps to reproduce the issue.

Try to avoid using old, unrelated threads for a new issue.