Skip to Main Content
  • Questions
  • Inability to Export/Import our APEX APP

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Ana.

Asked: June 05, 2025 - 11:13 am UTC

Last updated: June 09, 2025 - 11:31 am UTC

Version: Oracle APEX 24.2.5

Viewed 100+ times

You Asked

Hi everyone,

We’re developing an APEX app that handles Excel files, and we’ve run into a problem when trying to export the app from one Workspace and import it into another.

The main issue:
When we export the app and attempt to import it into a different Workspace, the import fails with various errors, and ultimately the app does not load.


Has anyone experienced similar issues or have any advice on how to resolve this? Being able to seamlessly transfer the app across Workspaces would greatly improve our workflow.

Additional details:

We export the entire application using default export options.

During import, we select “Import as Application” in the Import Wizard.

After some loading time, an error appears—although the exact error message varies. Examples include:

- Internal Server Error - Write
The server encountered an internal error or misconfiguration and was unable to complete your request.
Reference #4.73a2f17.1748513046.f1d44d4
https://errors.edgesuite.net/4.73a2f17.1748513046.f1d44d4

- Execution of the statement was unsuccessful. ORA-02091: transaction rolled back

begin wwv_flow_imp.import_end(p_auto_install_sup_obj => nvl(wwv_flow_application_install.get_auto_install_sup_obj, false)); 
commit; 
end;



We encounter the same problem even when exporting and importing a single page into a blank app. Clicking “Install Page” triggers the same ORA-02091 error as above.

Any guidance, tips, or workarounds would be highly appreciated. Thanks so much for your help!






and Connor said...

The most common cause is the handling of ID's between workspaces.

Check out this MOS note 3034956.1 for full details and how to mitigate, but the first thing to try is toggling the "Original ID" option on export

Rating

  (2 ratings)

Comments

Follow-up on Import/Export Issue

Ana, June 10, 2025 - 10:58 am UTC

Hi there,

Thank you for your prompt response and suggested solution.

We've tested toggling the OriginalID tab as recommended, but unfortunately the issue persists. Interestingly, we've observed that some applications from the problematic Workspace do export successfully to other Workspaces, which suggests this may be an application-specific issue rather than a Workspace-wide problem.

Could you please advise on additional troubleshooting steps we might try, or if there are specific application configurations that could be causing this selective export failure?

Thank you again for your continued assistance.

Just had the same issue

Joe, June 11, 2025 - 4:49 pm UTC

We just had the same issue and resolved it. In the Apex Dev Environment, and click on my account > Administration > Monitor Activity > Application Errors. This lists any errors in the environment, including import problems. Digging into it, we had this:

ORA-02291: integrity constraint (APEX_240200.WWV_FLOW_THEME_CURRENT_TS_FK) violated - parent key not found
ORA-06512: at "APEX_240200.WWV_FLOW_SECURITY", line 2217
ORA-06512: at "APEX_240200.WWV_FLOW_IMP", line 1281
ORA-06512: at "APEX_240200.WWV_FLOW_IMP", line 1308
ORA-06512: at "APEX_240200.WWV_FLOW_IMP", line 1348
ORA-06512: at line 2
ORA-06512: at "SYS.DBMS_SQL", line 1721
- Backtrace: ORA-06512: at "APEX_240200.WWV_FLOW_SECURITY", line 2217
ORA-06512: at "APEX_240200.WWV_FLOW_IMP", line 1281
ORA-06512: at "APEX_240200.WWV_FLOW_IMP", line 1308
ORA-06512: at "APEX_240200.WWV_FLOW_IMP", line 1348
ORA-06512: at line 2
ORA-06512: at "SYS.DBMS_SQL", line 1721
ORA-06512: at "APEX_240200.WWV_FLOW_APP_INSTALL_INT", line 167


Turns out, we had an older theme that had a "dangling" pointer to a them style that didn't exist. Once we fixed this in our development environment, we re-exported and were able to bring this into our production environment.


More to Explore

PL/SQL demos

Check out more PL/SQL tutorials on our LiveSQL tool.

PL/SQL docs

PL/SQL reference manual from the Oracle documentation library