This site is currently read-only as we are migrating to Oracle Forums for an improved community experience. You will not be able to initiate activity until January 30th, when you will be able to use this site as normal.

    Forum Stats

  • 3,889,831 Users
  • 2,269,775 Discussions
  • 7,916,823 Comments

Discussions

Describe system dynamic views v$ failed

danutz_68
danutz_68 BucharestMember Posts: 10 Blue Ribbon
edited Aug 21, 2020 4:19AM in SQLcl

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:

[email protected] > desc v$sessionMar 23, 2020 12:48:00 PM oracle.dbtools.raptor.newscriptrunner.ScriptExecutor runSEVERE: java.util.regex.Matcher.appendReplacement(Matcher.java:857)java.lang.IllegalArgumentException: Illegal group referenceat 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?

danutz_68User_AMSSX

Comments

  • Glen Conway
    Glen Conway Member Posts: 859 Gold Badge
    edited Mar 23, 2020 11:04AM

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

    danutz_68danutz_68
  • User273940_Dagmar
    User273940_Dagmar Member Posts: 5 Blue Ribbon
    edited Jul 10, 2020 6:34AM

    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
    Glen Conway Member Posts: 859 Gold Badge
    edited Jul 10, 2020 9:55AM

    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

    User_AMSSX
  • User273940_Dagmar
    User273940_Dagmar Member Posts: 5 Blue Ribbon
    edited Aug 21, 2020 4:19AM

    Thank you, Glen, for the investigation.