Discussions
Categories
- 197.1K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.7K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.3K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 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
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 466 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
SQL Develpoer - Showing Empty SQL script when generating DDL
Greetings,
I have encountered a problem when trying to generate SQL(with DDL) for a table. I noticed the problem only occurs when I'm not logged into same schema as the table whose SQL script I try to generate. But I can see all the data from tables and other stats. For the ones I don't have privileges I get an error which expected behavior. Here are some screenshots.
In the 'SQL' tab:
When I generate it with 'Quick DDL':
When using 'Save to Clipboard' I get an empty result. When saving to file:
Also when saving to Worksheet I get an empty result.
Has anyone encountered the same problem? Is this expected behavior or could it be a bug?
I'm using:
- SQL Developer Version: 22.2.0.173 Build 173.2018
- Java(TM) Platform 11.0.15.1
- Oracle IDE 22.2.0.173.2018
- Versioning Support 22.2.0.173.2018
Answers
-
It's probably a privileges issue. DBMS_METADATA requires a fairly high level in order to generate DDL for objects that you do not own.
