Exporting Application Components

Create a Component Export to back up a component before editing it, or create an export that functions as a patch to another Oracle APEX instance.


If you wish to export an application and some components, such as pages, that are not yet ready for testing, Oracle recommends you use Build Options to include or exclude various application components.

To export shared components or page components:

  1. Navigate to the Component Export page:
    1. On the Workspace home page, click the App Builder icon.
    2. Select an application.
    3. Click Shared Components.
    4. From the Tasks list, click Export Application Components.
  2. On the Component Export page, click the appropriate tabs and select the components to export:
    • Components displays shared application components and entire pages. Use the navigation bar at the top of the page to search for components.
    • Components by Page lists components of the selected page. Navigate to a specific page by making a selection from the Page list
    • Build Option Status displays available build options. Use this page to turn build options on and off.
  3. For each tab, select the appropriate components and click Add to Export.
  4. Review your selections. To continue, click Next.
  5. For Component Export:
    1. Export as Zip - Options include:
      • On - Exports the components as a ZIP archive containing separate files for each component.

      • Off - Exports as a single SQL file containing all the selected components.


      To learn more about the Zip archive, see Splitting Export Files into Separate Scripts.

    2. Include Installation files - Only displays if Export as Zip is set to On. Options include:
      • On - Generates a ZIP archive including installation files specifically for the exported page (for example, install_component.sql, set_environment.sql and end_environment.sql).

      • Off - Generate a ZIP file without the installation files.

        Oracle recommends Off when saving the files to a version control system so that application installation files are not overwritten.

    3. As of - Specify a time in minutes to go to back to for your export. This option enables you to go back in time in your application, perhaps to get back a deleted object.

      This utility uses the DBMS_FLASHBACK package. Because the timestamp to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the startup parameter UNDO_RETENTION (the default is three hours). However, this only influences the size of the undo tablespace. While two databases may have the same UNDO_RETENTION parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo tablespace, forcing older data to be archived.

    4. File Character Set - Indicates the character set in which the export file will be encoded. When importing this file you will need to specify the same character set.
    5. Click Export Components.


    For translated applications, the Export Translations field displays. To export the selected shared components for the primary language application and all translated applications, from Export Translations field, select Yes. To ensure text strings and markup are up-to-date, remember to synchronize the translated applications prior to exporting the translated components.

  6. Import the Component Export into the target instance.