Discussions
Categories
- 382.3K All Categories
- 2.1K Data
- 209 Big Data Appliance
- 1.9K Data Science
- 448K Databases
- 221K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 25 Multilingual Engine
- 520 MySQL Community Space
- 467 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 492 SQLcl
- 3.9K SQL Developer Data Modeler
- 186.2K SQL & PL/SQL
- 21K SQL Developer
- 293.3K Development
- 7 Developer Projects
- 128 Programming Languages
- 290K Development Tools
- 95 DevOps
- 3K QA/Testing
- 645.5K Java
- 24 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.9K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 16 Java Essentials
- 144 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
- 198 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 266 LiveLabs
- 36 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
- 230 Portuguese
Adding a schema to a workspace
Hi!
I have just created a second workspace in APEX and when I try to add a new schema, I follow the instructions and at the end I get this:
Error with: ORA-44003: invalid SQL name
ORA-44003: invalid SQL name
Does anyone know why this happens?
I haven't done anything different then before...
Regards,
Ivan
Answers
-
Follow which instructions?
How/where are you attempting to assign a schema to an Apex workspace?
What is the schema name? It is case sensitive?
-
Managing Workspace to Schema Assignments
Under Editing an Existing Schema and Workspace Assignment.
Like I said it worked for me before every time, but since I added a new workspace, it doesn't worn on either of them.
I have APEX 4.2.2.
Shema name is CM, everything is in capital letters.
Regards,Ivan
-
Not an easy error to resolve as it does not seem to be related to user input.
The error library says:
44003, 0000, "invalid SQL name"
// *Document : Yes
// *Cause : The input parameter string was not a valid simple SQL name.
// *Action : Check with the DBMS_ASSERT spec to verify that the parameter
// string is a valid simple SQL name.Cannot recall running into this exception myself. But it likely is a result to a cursor parse - which implies the error is a result to a dynamically created SQL by Apex.
This should not happen - unless there are something missing or misconfigured in Apex (assuming you have not run into an unknown bug).
I suggest you try manually (via SQL*Plus) using an Apex API call. See APEX_INSTANCE_ADMIN. If this throws an exception, we should have an error and call stack that will provide additional details as to what went wrong where.
-
Thanks Billy!
I managed to add the schema to workspace this way, but the error still persists.
I guess I'll just have to it this way from now on...Regards,
Ivan