Oracle SQLcl 25.3 Release Notes

Version 25.3.0.274.1210

October 2025

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

 

25.3 New Features

  • RCV command "Oracle Database backup integration with Zero Data Loss Autonomous Recovery Service." Learn more here
  • Project verification feature (project verify) now offers more comprehensive error checking with your snapshots, stages, and artifacts
  • Project CI/CD feature now supports DBMS_SCHEDULER objects including jobs, programs and schedules
  • Projects can now export ORDS schema objects using ORDS_ADMIN API

 

Bugs Fixed

  • 38329182 MCP CONNECTIONS ARE NOT CLOSED AFTER CALLING CLOSE FUNCTION
  • 37884237 SOME STATEMENTS IN A SQL FILE ARE NOT EXECUTED WHEN USING SET DEFINE
  • 37481464 SELECT /*INSERT*/ CONCATENATES BLOB COLUMN LEADS TO ORA-01465
  • 38343426 CANNOT CONNECT AND SAVE A CLOUD WALLET CONNECTION
  • 37339395 USING "ORAPKI" WITH JDK 21 AND JDK 23 FAILS "SECURITY MANAGER IS DEPRECATED"
  • 37998699 CANNOT DROP OR REPLACE A TYPE WITH TABLE DEPENDENTS
  • 38049779 INVALID DROP STATEMENTS FOR THE INDEX
  • 37679187 LOGON HELP SYNTAX DOES NOT INCLUDE SYSBACKUP AND SYSDG ROLES
  • 38413946 HELP SET DDL COMMAND TEXT HAS FORMATTING PROBLEMS
  • 36486442 LIQUIBASE GENERATE-SCHEMA SUPPRESSES BYTE INFORMATION FROM VARCHAR2 DATA TYPE
  • 37301575 LIQUIBASE SQL CHANGESET DOESN'T PRINT DBMS_OUTPUT
  • 37338222 LIQUIBASE FAILS TO GENERATE ALL APEX APPLICATIONS IN A WORKSPACE
  • 37423209 LIQUIBASE GENERATE-SCHEMA -GRANTS COMMAND DOES NOT EXPORT GRANTS
  • 37355977 LIQUIBASE UPDATE -CHANGELOG-FILE APEX_INSTALL.XML FAILS WHEN CHANGESET GENERATED USING -EXPTYPE PARAMETER
  • 37423209 LIQUIBASE GENERATE-SCHEMA -GRANTS COMMAND DOES NOT EXPORT GRANTS
  • 38292404 LIQUIBASE EXPORT OF ORDS MODULE FAILS WHEN MODULE NAME IS LOWERCASE
  • 37820786 PROJECT CONFIGURED CONNECTION NOT HONORED AFTER DISCONNECT
  • 38273504 PROJECT EXPORTS GENERATES INSTALL.SQL THAT REFERENCES SHOWS LIQUIBASE XML INSTEAD OF .SQL FILE
  • 37894895 PROJECT DEPLOY SUPPRESSES IMPORTANT ERROR DETAILS
  • 37902682 PROJECT DEPLOY CREATES LOG FILE IN TEMP DIRECTORY
  • 38154484 PROJECT SXML NOT CONSISTENT WITH CASE CAUSING UNNECESSARY DIFFS
  • 37800584 PROJECT UNABLE TO EXECUTE THE GENERATED/EXPORTED ORDS SQL FILES
  • 38331290 PROJECT EXPORT TABLE CAUSES INVALID XML
  • 38189337 PROJECT STAGE FAILS TO GENERATE ALTER STATEMENTS WHEN BUILT-IN SQL FUNCTIONS LIKE EMPTY_CLOB() ARE USED AS DEFAULTS
  • 38441783 PROJECT STAGE CREATES WRONG ALTER SQLS FOR XMLTYPE DATA TYPE COLUMNS
  • 38440775 PROJECT STAGE INCORRECT DDL FOR TABLE COLUMN WHEN SET FROM NOT NULL TO NULL
  • 38063924 PROJECT SCRIPTS USING HOST AND SPOOL COMMANDS FAIL UNEXPECTEDLY
  • 37862505 PROJECT EXPORT LIST NOT PROPERLY SORTED
  • 38386782 PROJECT EXPORT SCHEMA LEVEL TRIGGERS (BEFORE DROP ON...) NOT INCLUDED

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 17 or 21. The supported Java Runtime Environments are:
      • Oracle Java 17
      • Oracle Java 21
      • Oracle GraalVM Enterprise Edition for Java 17
      • Oracle GraalVM Enterprise Edition for Java 21
  • JavaScript support requires 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.