Forum Stats

  • 3,770,408 Users
  • 2,253,104 Discussions
  • 7,875,445 Comments

Discussions

Adding a schema to a workspace

Ivan2405
Ivan2405 Member Posts: 92
edited Jun 5, 2014 8:18AM in APEX Discussions

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

  • Billy Verreynne
    Billy Verreynne Software Engineer Member Posts: 28,601 Red Diamond

    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?

  • Ivan2405
    Ivan2405 Member Posts: 92

    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

  • Billy Verreynne
    Billy Verreynne Software Engineer Member Posts: 28,601 Red Diamond

    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.

    Billy Verreynne
  • Ivan2405
    Ivan2405 Member Posts: 92

    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

This discussion has been closed.