Discussions
Categories
- 381.6K All Categories
- 2.1K Data
- 206 Big Data Appliance
- 1.9K Data Science
- 447.1K Databases
- 220.7K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 23 Multilingual Engine
- 516 MySQL Community Space
- 463 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 460 SQLcl
- 3.9K SQL Developer Data Modeler
- 185.8K SQL & PL/SQL
- 20.9K SQL Developer
- 292.3K Development
- 7 Developer Projects
- 119 Programming Languages
- 289.1K Development Tools
- 94 DevOps
- 3K QA/Testing
- 645.4K Java
- 20 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.8K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 14 Java Essentials
- 142 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 197 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 217 LiveLabs
- 34 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 166 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
Schema not registered with ORDS
APEX 20.2
On more than one occasion, when I click on SQL Workshop / RESTFul Services in the APEX Builder, I get this message saying the schema is not registered with ORDS. This is incorrect and sure enough when I navigate around a bit, log out and log in and such, the message clears up.
What is going on here? Which schema is it complaining about and why?
Thanks
Best Answer
-
Maybe a better question for the APEX community, but it would be whatever schema your workspace is registered to, or end of day, who you are logged in as in the database.
Seems like an apex bug to me...
Answers
-
Maybe a better question for the APEX community, but it would be whatever schema your workspace is registered to, or end of day, who you are logged in as in the database.
Seems like an apex bug to me...