Forum Stats

  • 3,770,053 Users
  • 2,253,055 Discussions
  • 7,875,284 Comments

Discussions

How to change default schema of a workspace?

Michael Horn
Michael Horn Member Posts: 12 Blue Ribbon
edited Sep 6, 2012 8:48AM in APEX Discussions
We have a workspace associated with two schemas SCHEMA_A and SCHEMA_B. We started off (many years ago) with schema SCHEMA_A (default schema), later SCHEMA_B (additional schema) was added to the workspace. Unfortunately SCHEMA_A is no longer used, all the work is done in SCHEMA_B.

How do I change the default schema of a workspace? I found the following discussion (2190414 which solves the mystery of how to delete a schema association (last entry in the thread). One "simple" solution would be to drop the the current workspace and create a new one with the same name, however this is not feasible, as we have to many developers, applications and database servers, where we would have to implement those "changes".

Thanks in advance ...
Tagged:

Best Answer

  • Hari_639
    Hari_639 Member Posts: 1,484 Silver Trophy
    Accepted Answer
    Hello,

    You can't delete Primary Schema Assignment. However you can change it.

    <li> Log-in to INTERNAL Workspace
    <li> Goto Manage Workspace -> Manage Schema Assignments
    <li> Delete schema Assignment for SCHEMA_B (You may need to ensure no app is using this schema as parsing schema?)
    <li> Change Schema Assignment of SCHEMA_A to SCHEMA_B

    Regards,
    Hari

Answers

  • Hari_639
    Hari_639 Member Posts: 1,484 Silver Trophy
    Accepted Answer
    Hello,

    You can't delete Primary Schema Assignment. However you can change it.

    <li> Log-in to INTERNAL Workspace
    <li> Goto Manage Workspace -> Manage Schema Assignments
    <li> Delete schema Assignment for SCHEMA_B (You may need to ensure no app is using this schema as parsing schema?)
    <li> Change Schema Assignment of SCHEMA_A to SCHEMA_B

    Regards,
    Hari
  • Michael Horn
    Michael Horn Member Posts: 12 Blue Ribbon
    Thanks, we didn't have the courage to "delete" the second schema assignment, because all our applications use it. But it works fine!
This discussion has been closed.