Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Describe system dynamic views v$ failed
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?
Comments
-
Looks like a bug. As a workaround, use the INFO or INFO+ command in place of DESCRIBE
-
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
-
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
-
Thank you, Glen, for the investigation.