The throw
command produce a javastack instead of something like an error report as second example.
SQL> show version
Oracle SQLDeveloper Command-Line (SQLcl) version: 21.2.2.0 build: 21.2.2.223.0914
SQL> script
2 throw "error";
3* /
2021-09-30 13:38:39.882 SEVERE oracle.dbtools.raptor.newscriptrunner.ScriptExecutor run oracle.dbtools.scripting.ScriptCommand.runScript(ScriptCommand.java:185)
java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
at oracle.dbtools.scripting.ScriptCommand.runScript(ScriptCommand.java:185)
at oracle.dbtools.scripting.ScriptCommand.handleEvent(ScriptCommand.java:70)
at oracle.dbtools.raptor.newscriptrunner.CommandRegistry.fireListeners(CommandRegistry.java:334)
at oracle.dbtools.raptor.newscriptrunner.ScriptRunner.run(ScriptRunner.java:226)
at oracle.dbtools.raptor.newscriptrunner.ScriptExecutor.run(ScriptExecutor.java:344)
at oracle.dbtools.raptor.newscriptrunner.ScriptExecutor.run(ScriptExecutor.java:227)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.processLine(SqlCli.java:341)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.runSqlcl(SqlCli.java:1049)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.main(SqlCli.java:369)
SQL> script
2 throw "error<eval>:111:222";
3* /
"Error at line : 111 Column : 222
in <eval> at line number 1 at column number 0
"SQL>