Skip to Main Content
Forums

SQLcl: MCP Server & SQL Prompt

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Describe system dynamic views v$ failed

danutz_68Mar 23 2020 — edited Aug 21 2020

Hi. I'm using the lasted version of sqlcl (SQLcl: Release 19.4 Production on Mon Mar 23 12:47:47 2020) and every time I try to describe any dynamic view the output is failing with the following error:

SYSTEM@XEPDB1 > desc v$session
Mar 23, 2020 12:48:00 PM oracle.dbtools.raptor.newscriptrunner.ScriptExecutor run
SEVERE: java.util.regex.Matcher.appendReplacement(Matcher.java:857)
java.lang.IllegalArgumentException: Illegal group reference
at java.util.regex.Matcher.appendReplacement(Matcher.java:857)
at java.util.regex.Matcher.replaceAll(Matcher.java:955)
at java.lang.String.replaceAll(String.java:2223)
at oracle.dbtools.raptor.newscriptrunner.commands.DescribePrep.compileViewIfRequired(DescribePrep.java:1391)
at oracle.dbtools.raptor.newscriptrunner.commands.DescribePrep.parseDescribe(DescribePrep.java:294)
at oracle.dbtools.raptor.newscriptrunner.commands.DescribePrep.handleEvent(DescribePrep.java:79)
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.process(SqlCli.java:407)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.processLine(SqlCli.java:418)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.startSQLPlus(SqlCli.java:1252)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.main(SqlCli.java:494)

Is there bug for this error or I have some client misconfiguration?

Comments

Glen Conway

Looks like a bug.  As a workaround, use the INFO or INFO+ command in place of DESCRIBE

1 person found this helpful
User273940_Dagmar

info and info+ work, but only on v_$ views:

info v$system_fix_control

Object Not Found: v$system_fix_control

info v_$system_fix_control

Columns

NAME                       DATA TYPE           NULL  DEFAULT    COMMENTS

BUGNO                     NUMBER              Yes

VALUE                     NUMBER              Yes

SQL_FEATURE               VARCHAR2(64 BYTE)   Yes

DESCRIPTION               VARCHAR2(64 BYTE)   Yes

OPTIMIZER_FEATURE_ENABLE  VARCHAR2(25 BYTE)   Yes

EVENT                     NUMBER              Yes

IS_DEFAULT                NUMBER              Yes

CON_ID                    NUMBER              Yes

Glen Conway

Even in SQL Developer 20.2, where the DESCRIBE command does work a bit better than 19.4, there is still a bug.

If you look into the SQL statements shown in the View > Log > Statements - Log tab (on either 19.4 or 20.2), you can see that:

1) INFO is looking for the uppercase object name in ALL_SYNONYMS, but not ALL_OBJECTS.

2) DESC is looking for the uppercase object name in ALL_OBJECTS, but the predicate matching on object owner is bad: UPPER(owner) = UPPER('').

Looks like a double WHUPS. I ran this test using 19.4 against an Oracle 19.3 database.  Best to get a bug logged through My Oracle Support if you are able.

Cheers

1 person found this helpful
User273940_Dagmar

Thank you, Glen, for the investigation.

1 - 4

Post Details

Added on Mar 23 2020
4 comments
327 views