Previous Next JavaScript must be enabled to correctly display this content

## 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 26.1 requires an Oracle Database release 19c with Database Release Update 19.18 (January 2023) or newer. On Oracle AI Database 26ai, APEX requires at least Database Version 23.26.0 (October 2025). APEX runs on all database editions, including Enterprise Edition (EE), Standard Edition 2 (SE2), and Oracle AI Database 26ai Free. 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) 26.1.1 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 26.1 requires an Oracle Database release 19c with Database Release Update 19.18 (January 2023) or newer. On Oracle AI Database 26ai, APEX requires at least Database Version 23.26.0 (October 2025). APEX runs on all database editions, including Enterprise Edition (EE), Standard Edition 2 (SE2), and Oracle AI Database 26ai Free. APEX can be installed in single-instance database and in Oracle Real Application Clusters (Oracle RAC) database.

- Checking the Memory Settings of the Target Database
  Oracle APEX requires the system global area (SGA) to be at least 1200 MB and program global area (PGA) to be at least 300 MB.
- 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`.
- Installing APEX in Databases where Database Vault is Enabled
  Complete additional configuration steps to install Oracle APEX in databases where Oracle Database Vault is enabled.

Parent topic: Oracle APEX Installation Requirements

#### 2.1.1 Checking the Memory Settings of the Target Database

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

Databases typically have two parameters to control the memory allocation: `SGA_TARGET` and `PGA_AGGREGATE_TARGET`. For full details on Oracle Database memory configuration, consult the Oracle AI Database Administrator’s Guide to find out how to configure manual memory parameters (for example, `SGA_TARGET`, `PGA_AGGREGATE_TARGET`, `SHARED_POOL_SIZE`).

To check the memory parameters of the target database:

1. Start the database:

       SQL> STARTUP

2. (Optional) 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.

3. Determine the current values of the memory parameters, then do one of the following:

       SQL> SHOW PARAMETER SGA_TARGET
       SQL> SHOW PARAMETER PGA_AGGREGATE_TARGET

   - If the value of `SGA_TARGET` is `0`, your database is using automatic memory management. Consult Using Automatic Memory Management in Oracle AI Database Administrator’s Guide to learn how to configure an equivalent memory size using the `MEMORY_TARGET` parameter. Stop this procedure.
   - If the values of `SGA_TARGET` or `PGA_AGGREGATE_TARGET` are lower than the recommended sizes, then you must increase them depending on whether your database is using a server parameter file or the initialization parameter file. Proceed to the next step.
4. To determine whether your system uses a server parameter file or initialization parameter file:

       SQL> SHOW PARAMETER PFILE;

   - If the file begins with the prefix `sp` for server parameter, then issue:

         SQL> ALTER SYSTEM SET SGA_TARGET='1200M' SCOPE=spfile;
         SQL> ALTER SYSTEM SET PGA_AGGREGATE_TARGET='300M' SCOPE=spfile;

   - Otherwise, the system is using an initialization parameter file. Change the value of the `MEMORY_TARGET` parameter to at least 300 MB in the initialization parameter file (`init<sid>.ora`).

5. Shut down the database:

       SQL> SHUTDOWN

6. Restart the database:

       SQL> STARTUP

7. Confirm the new memory settings:

       SQL> SHOW PARAMETER SGA_TARGET
       SQL> SHOW PARAMETER PGA_AGGREGATE_TARGET

See Also:

Using Automatic Memory Management in Oracle AI 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 SQLcl and connect to the database as `SYS` specifying the `SYSDBA` role. For example:

   - On Windows:

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

   - On UNIX and Linux:

         $ sql /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 AI Database Reference

Parent topic: Oracle Database Requirements

#### 2.1.3 Installing APEX in Databases where Database Vault is Enabled

Complete additional configuration steps to install Oracle APEX in databases where Oracle Database Vault is enabled.

To begin, see Integrating Oracle Database Vault with Oracle APEX in Oracle AI Database Vault Administrator’s Guide.

You must also complete additional configuration steps for some APEX features, including workspace provisioning and SQL Workshop.

The Database Vault security controls protect application data from unauthorized access and help you to comply with privacy and regulatory requirements. Database Vault is a licensable option of Oracle AI Database Enterprise Edition. Its purpose is to mitigate the potential impact of privileged account abuse, misuse, insider and external threats, and human error on your sensitive data.

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) 26.1.1 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.

As of Oracle APEX 26.1, Oracle now recommends in new installations, ORDS should be installed before APEX.

Tip:

APEX-based REST Services were desupported in release 22.1. Oracle REST Data Services (ORDS) release 21.4.2 and newer now ship 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: 670 MB if using English only download (`apex_26.1_en.zip`) and 1,178 MB if using full download (`apex_26.1.zip`).
- Free space in APEX tablespace: 260 MB
- Free space in `SYSTEM` tablespace: 128 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