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
- 584 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
- 666 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
very bad performance describe "package"

I just installed the newest version of SQL Developer / Data Modeler and SQLcl (18.3) and I was amazed by the pretty bad performance of desc(ribe)
"desc dbms_job" ran 50 seconds within SQL Developer ind SQLcl. "information dbms_job" is showing the result quite immediatly - the result is not very readable.
A crosscheck with sql*plus (11.2.0.3.0) showed the "desc dbms_job" result immediatly.
Answers
-
Yes SQL Developer version 18.1.0 took around 16 sec but same in version 3.0.04 took 0.5 sec..
You can use older version or putty to get result quick and format is also good
-
To see the difference between INFO vs DESC, just look at the actual SQL getting executed in View -> Log -> Statements. And do not be so quick to assume there is a huge performance difference between the two commands. Try closing SQL Developer, opening it again, and re-executing the commands. INFO was still a bit faster for me, but both ran in under 1 second against a local 11g XE database.
-
That is, having the database warmed up and something already in the database cache makes a big difference.
-
SQL Dev/Data Modeler/SQLcl all uses JDBC for their DB connection and the way of working is different when compared with SQL*plus.
Few known issues that possibly fixed the issue has described in below articles you can try.
Describes Of Dictionary And Fixed Objects Very Slow Using SQL Developer Against 12c Database (Doc ID 2147939.1)
How To Troubleshoot Slow Performance From DESC Command In SQL Developer (Doc ID 2410577.1)