Oracle SQLcl 25.3.1 Release Notes

Version 25.3.1.311.1257

November 2025

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

 

25.3.1 New Features

  • New RESTRICT Level zero: sql -mcp -r 0 By default, MCP server starts in RESTRICT Level 4. This new level allow users full access to all features over MCP.
  • New Schema-Information tool in MCP server which concisely describes the current schema.
  • The Fleet Agent command (RCV) now supports Recovery Appliance (RA) migration scenarios.

Bugs Fixed

  • 38450934 Prevent LLM from misusing tool results from MCP server
  • 38599903 Fix for NULL issues with color printing of SQLcl results using ansiconsole sqlformat
  • 38550645 Fix version recognition for 26ai connections over MCP server
  • 38526525 Liquibase generate-apex-object now supports -dir to save files as well as cwd
  • 38335431 Default column widths on results match SQL*Plus defaults

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.