1. Installation Guide
  2. Oracle APEX Installation Requirements

2 Oracle APEX Installation Requirements

Before installing Oracle APEX in a local self-managed installation you must verify your configuration meets the minimum installation requirements.

  • Oracle Database Requirements
    Oracle APEX release 22.2 requires an Oracle Database release 12.1.0.2 or later. APEX runs on all database editions, including Enterprise Edition (EE), Standard Edition (SE) and Express Edition (XE). APEX can be installed in single-instance database and in Oracle Real Application Clusters (Oracle RAC) database.
  • Browser Requirements
    Oracle APEX requires a JavaScript-enabled browser and supports the current and prior major release of Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge.
  • Web Server Requirements
    Oracle APEX requires Oracle REST Data Services (ORDS) 20.x or later.
  • Disk Space Requirement
    Oracle APEX disk space requirements are described in this section.
  • Oracle XML DB Requirement
    Oracle XML DB must be installed in the Oracle database that you want to use if you are installing a full development environment. If you are using a preconfigured database created either during an installation or by Database Configuration Assistant (DBCA), Oracle XML DB is already installed and configured.

2.1 Oracle Database Requirements

Oracle APEX release 22.2 requires an Oracle Database release 12.1.0.2 or later. APEX runs on all database editions, including Enterprise Edition (EE), Standard Edition (SE) and Express Edition (XE). APEX can be installed in single-instance database and in Oracle Real Application Clusters (Oracle RAC) database.

If you are upgrading an Oracle Database version 12.1 CDB, you must download from My Oracle Support the one off patch for bug 20618595. Search for 20618595 on the Patches tab.

Parent topic: Oracle APEX Installation Requirements

2.1.1 Checking the MEMORY_TARGET of the Target Database

Oracle APEX requires the system global area (SGA) and program global area (PGA) to be at least 300 MB.

Databases typically use automatic memory management, where the memory can be controlled by the server parameter MEMORY_TARGET. If your database does not use automatic memory management, consult the Oracle Database Administrator's Guide to find out how to configure manual memory parameters (for example, SGA_TARGET, PGA_AGGREGATE_TARGET, SHARED_POOL_SIZE) instead, for a similar result.

To check the MEMORY_TARGET of the target database:

  1. Start SQL*Plus and connect to the database as SYS specifying the SYSDBA role. For example:

    • On Windows:

      SYSTEM_DRIVE:\ sqlplus /nolog
SQL> CONNECT SYS as SYSDBA
Enter password: SYS_password

    • On UNIX and Linux:

      $ sqlplus /nolog
SQL> CONNECT SYS as SYSDBA
Enter password: SYS_password
  2. Start the database: 
    SQL> STARTUP
  3. If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora): 
    SQL> SHOW PARAMETER PFILE;

    This command displays the name and location of the server parameter file or the initialization parameter file.

  4. Determine the current values of the MEMORY_TARGET parameter: 
    SQL> SHOW PARAMETER MEMORY_TARGET
  5. If the value is 0, your database is using manual memory management. Consult the Oracle Database Administrator’s Guide to learn how to configure an equivalent memory size using manual memory management, instead of continuing with the steps that follow.

    If the system is using a server parameter file, set the value of the MEMORY_TARGET initialization parameter to at least 300 MB: 

    SQL> ALTER SYSTEM SET MEMORY_TARGET='300M' SCOPE=spfile;
  6. If the system uses an initialization parameter file, change the value of the MEMORY_TARGET parameter to at least 300 MB in the initialization parameter file (initsid.ora).
  7. Shut down the database: 
    SQL> SHUTDOWN
  8. Restart the database: 
    SQL> STARTUP

See Also:

Using Automatic Memory Management in Oracle Database Administrator’s Guide

Parent topic: Oracle Database Requirements

2.1.2 Checking the WORKAREA_SIZE_POLICY of the Target Database

For the Oracle APEX installation or upgrade process, the WORKAREA_SIZE_POLICY session parameter must be set to AUTO.

To check the WORKAREA_SIZE_POLICY of the target database:

  1. Start SQL*Plus and connect to the database as SYS specifying the SYSDBA role. For example:

    • On Windows:

      SYSTEM_DRIVE:\ sqlplus /nolog
SQL> CONNECT SYS as SYSDBA
Enter password: SYS_password

    • On UNIX and Linux:

      $ sqlplus /nolog
SQL> CONNECT SYS as SYSDBA
Enter password: SYS_password
  2. Check the current value of the WORKAREA_SIZE_POLICY parameter:
    SQL> SHOW PARAMETER WORKAREA_SIZE_POLICY
  3. If the value of the parameter is MANUAL, change it to AUTO for the current database session. For example:
    SQL> ALTER SESSION SET WORKAREA_SIZE_POLICY = AUTO;
  4. Within the same database session, perform the installation or upgrade of Oracle APEX.

Note:

If you are installing Oracle APEX in a CDB, WORKAREA_SIZE_POLICY must be set system-wide. For example:

SQL> ALTER SYSTEM SET WORKAREA_SIZE_POLICY=AUTO SCOPE=BOTH;

Then, if needed, change it back to MANUAL after Oracle APEX installation or upgrade.

See Also:

WORKAREA_SIZE_POLICY in Oracle Database Reference

Parent topic: Oracle Database Requirements

2.2 Browser Requirements

Oracle APEX requires a JavaScript-enabled browser and supports the current and prior major release of Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge.

Parent topic: Oracle APEX Installation Requirements

2.3 Web Server Requirements

Oracle APEX requires Oracle REST Data Services (ORDS) 20.x or later.

Oracle REST Data Services (ORDS) is Java-based web server. Oracle REST Data Services features the ability to emit RESTful web services, offers improved file upload capability, and is certified with Oracle WebLogic Server and Apache Tomcat.

Tip:

APEX-based REST Services were desupported in release 22.1. Oracle REST Data Services (ORDS) release 21.4.2 now ships with migration scripts that enable you to upgrade any remaining APEX-based REST Services to ORDS-based Services. To learn more, see Migration of Oracle APEX RESTful Service Modules in Oracle REST Data Services Release Notes.

Parent topic: Oracle APEX Installation Requirements

2.4 Disk Space Requirement

Oracle APEX disk space requirements are described in this section.

APEX disk space requirements are as follows:

  • Free space for APEX software files on the file system: 510 MB if using English only download (apex_22.2_en.zip) and 890 MB if using full download (apex_22.2.zip).
  • Free space in APEX tablespace: 190 MB
  • Free space in SYSTEM tablespace: 125 MB
  • Free space in APEX tablespace for each additional language (other than English) installed: 60 MB

Parent topic: Oracle APEX Installation Requirements

2.5 Oracle XML DB Requirement

Oracle XML DB must be installed in the Oracle database that you want to use if you are installing a full development environment. If you are using a preconfigured database created either during an installation or by Database Configuration Assistant (DBCA), Oracle XML DB is already installed and configured.

Tip:

The installer does a prerequisite check for Oracle XML DB and will exit if it is not installed.

Tip:

The installation of Oracle XML DB creates the user ANONYMOUS. In order for Oracle APEX workspace provisioning to work properly, the ANONYMOUS user must not be dropped from the database.

Tip:

For more information about manually adding Oracle XML DB to an existing database, see Administration of Oracle XML DB in Oracle XML DB Developer’s Guide

Parent topic: Oracle APEX Installation Requirements