How to Move APEX Schemas to a New Tablespace During APEX Upgrade
(Doc ID 760404.1)
Last updated on MAY 08, 2020
Applies to:Oracle Application Express (APEX) - Version 1.6.0 and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
This should work for any APEX upgrade.
Checked for relevance on 21-Aug-2010.
APEX objects exist in two schemas: FLOWS_FILES and FLOWS_NNNNNN / APEX_NNNNNN where the value of NNNNNN depends on the version of APEX:
1.6 -> FLOWS_010600
2.0 -> FLOWS_020000
2.2 -> FLOWS_020200
3.0 -> FLOWS_030000
3.1 -> FLOWS_030100
3.2 -> APEX_030200
4.0 -> APEX_040000
4.1 -> APEX_040100
4.2 -> APEX_040200
5.0 -> APEX_050000
(For the remainder of this note we'll assume one is upgrading from 3.0 to 3.1).
The goal of the note is to describe how the default tablespace for FLOWS_FILES and FLOWS_030000 can be changed during an upgrade to APEX 3.1.
Also, we'll assume that FLOWS_FILES and FLOWS_030000 objects are in the SYSAUX tablespace and the goal is to move them to the USERS tablespace.
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