Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.4K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 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
- 442 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
APEX schema problem

Hi,
I'm new in APEX and I got a problem with my schema. I have an existing database with lots of data, lots of table. These tables owned by one schema. When I try to create an application using that schema and I select an existing table, I get the following error message:
"Ajax call returned server error ORA-20987: APEX - Invalid schema name - Contact your application administrator. for Execute Server-Side Code."
Is there any settings (grants, privilege, etc.) for a schema that makes it to not working? What should I do? Is there any solution to fix this schema or is it possible for another schema to use this schema's tables for creating APEX applications?
Thanks for the answeres!
Andrew
Comments
-
What is the problematic schema name?
-
The schema name is: WORK
-
The schema name is: WORK
WORK
is an Oracle keyword and therefore a poor choice of identifier that is likely to cause problems.What is being entered as the table name in the page wizard? All that is visible in the screenshot is
T. proba
, which appears to have nothing to do with theWORK
schema and isn't a valid identifier.Please do not attempt to describe problems using screenshots—especially cropped, context-free ones. These are not accessible to visually impaired members of the community, cannot be indexed by search engines, or copied/pasted to reproduce the problem. If you must post screenshots (primarily to demonstrate layout and presentation problems that cannot be reproduced on apex.oracle.com), post the entire window to preserve context.