Oracle SQLcl Release Notes 23.3

Release Notes

Oracle SQLcl 23.3.0.270.1251

Date: October 2023

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

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

Getting Started

Documentation on getting started with SQLcl is provided on the oracle.com web site. Click here, navigate to the documentation section and access the book titled 'Oracle SQLcl getting started'.

Requirements

New Features in 23.3.0

Named Connections

The connmgr command was introduced in 23.2.0 and it has been extended to include more support for importing connections from SQL Developer.

For handling ecrypted connections, the following have been added

For example:

SQL>secret  set mysecret oracle

Secret mysecret stored
SQL>secret list
mysecret
SQL>connmgr import -key mysecret Connections.json
Importing connection conn1: Success
Importing connection conn2: Success
Importing connection conn3: Success
Importing connection conn4: Success
4 connection(s) processed
SQL>

Enhanced Error Reporting

As part of 23c Database release, all oracle errors were updated with better explanations and recommendations. In this SQLCL release, links have been added to help clarify error codes that are thrown when there is an issue with a command. The index for all Oracle Errors is now published here

For a SQL query, this looks like

SQL>select * from non-existing-tables;


Error starting at line : 1 in command -
select * from non-existing-tables
Error at Command Line : 1 Column : 18
Error report -
SQL Error: ORA-00933: SQL command not properly ended
00933. 00000 -  "SQL command not properly ended"
*Cause:    
*Action:

More Details :
https://docs.oracle.com/error-help/db/ora-00933/
SQL>

For any other Oracle errors thrown, we will display the link to the appropraite page. E.g., for PL/SQL

SQL> BEGIN

       non-existing-procedure;
     END;
/
Error starting at line : 1 in command -
BEGIN
non_existing_procedure;
END;
Error report -
ORA-06550: line 2, column 1:
PLS-00201: identifier 'NON_EXISTING_PROCEDURE' must be declared
ORA-06550: line 2, column 1:
PL/SQL: Statement ignored
06550. 00000 -  "line %s, column %s:\n%s"
*Cause:    Usually a PL/SQL compilation error.
*Action:

More Details :
https://docs.oracle.com/error-help/db/ora-06550/
https://docs.oracle.com/error-help/db/pls-00201/
SQL>

Enhanced OCI configuration Support

Blockchain & Immutable Tables with Certificates

In this release, we are including support for managing blockchain and immutable tables and certificates which are used in them.

The commands create a user friendly way to manage these objects and use extensions of the PL/SQL packages DBMS_BLOCKCHAIN_TABLE, DBMS_IMMUTABLE_TABLE and DBMS_USER_CERTS

Get more details by using the help for each command

help certificate

help blockchain_table
help immutable_table

CODESCAN Command

Check .sql, .pls, .plb files in the directory for SQL Best Practices violations.

This command identifies issues with code using the Trivadis Coding Guidelines which are available on github

For example:

SQL>set codescan on

SQL>BEGIN
    BEGIN
        null; 
    END;
 END;
/

SQL best practice warning (1,7): G-1010: Try to label your sub blocks 

PL/SQL procedure successfully completed.

Then fix the problem

SQL >begin

     <<label>> 
        BEGIN
           NULL;
        END label;
     END;
/

PL/SQL procedure successfully completed.
SQL>

You can also codescan a directory

SQL> cd <my code dir>

SQL> CODESCAN
***** /Users/user/source/file1.sql
*** 1 distinct warnings
Warning (25,14): G-2180: Never use quoted identifiers
***** /Users/user/source/file2.sql
*** 1 distinct warnings
Warning (3,15): G-2180: Never use quoted identifiers
***** /Users/user/source/file3.sql
*** 2 distinct warnings
Warning (6,4): G-3130: Try to use ANSI SQL-92 join syntax
Warning (14,4): G-3145: Avoid using SELECT * directly from a table or view

Issues Fixed in 23.3.0

Restrictions

This section describes the restrictions on use that upgrading has introduced.

ORACLE_HOME usage

When using sqlcl in an ORACLE_HOME, it must be a minimum version of 21c.

Feedback

At Oracle SQLDeveloper SQLcl on oracle.com you will find links to forums and social media channels where you can discuss topics with the SQLcl community around the world and leave feedback for the development team.

In the forums, 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.

Oracle Chatbot
Disconnected