My Oracle Support Banner

Unable to Import Workspace That Was Previously Deleted: "Workspace Exists and Will not be Created." (Doc ID 2181859.1)

Last updated on FEBRUARY 09, 2023

Applies to:

Oracle Application Express (APEX) - Version and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


Copying workspace from DEV to TEST database instances. Used APEX GUI to export. During the workspace import via GUI, a message that indicates that "workspace exists" and will not be created".

Both the DEV and TEST environments are refreshed approximately once a month from PROD using the following method:

** The customer has a method they use where the refresh DEV and TEST from Prod
- Refresh the database from PROD
- Reinstall APEX
- Reinstall ORDS
- Import App / Workspaces


Other information

o APEX Version is 5.0.4. 

o The APEX administration page shows only a the INTERNAL / ADMIN  workspace and user exist in the installation. There are no other workspaces / users listed on the page.
o The same methodology has been used for several years and is done approximately once a month
  - Dev was most recently refreshed 
  - Test was refreshed too

How to get around this and keep the same workspace ID of 100050 and switch to a different primary schema?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.