3.5.3 Configuring Storage

Instance administrators can configure the following Storage options: require a new schema when requesting a workspace, auto extend tablespaces, automaticaly approve storage requests, or delete uploaded files in a specified number of days.

3.5.3.1 Requiring a New Schema

Control if a user requesting a workspace can select an existing schema or must request a new schema.

To require a new schema when creating a workspace:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. From Require New Schema, select one of the following:
    • Yes - Requires users to request a new schema when they request a new workspace.
    • No - Enables users to select an existing schema when they request a new workspace.
  6. Click Apply Changes.

3.5.3.2 Configuring Instance Tablespace

Specify the name of an existing data tablespace to use for the database user for all new workspaces.

To configure Instance Tablespace:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. Instance Tablespace - Enter the name of an existing data tablespace, or comma separated list of tablespaces, to use for the database user for all new workspaces. When not set, a new tablespace is created.
  6. Click Apply Changes.

3.5.3.3 Enabling Auto Extend Tablespaces

Enable Auto Extend Tablespaces.

If Auto Extend Tablespaces is enabled, tablespaces provisioned with APEX are created with a data file that is one tenth the requested size. The data file automatically extends up to the requested size. For example, if a user requests a 100 MB workspace, the initial size of the data file is 10 MB and automatically extends up to a maximum size of 100 MB.

To enable Auto Extend Tablespaces:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. To enable Auto Extend Tablespaces, select Yes.
  6. Click Apply Changes.

3.5.3.4 Enabling Bigfile Tablespaces

Enable support for bigfile tablespaces.

When a workspace is provisioned, APEX creates the associated database user, tablespace, and data file. If Bigfile Tablespaces is enabled, tablespaces provisioned with APEX are created as bigfile tablespaces. A bigfile tablespace is a tablespace with a single, but very large data file. Traditional smallfile tablespaces, in contrast, can contain multiple data files, but the files cannot be as large.

Tip:

Oracle does not recommend using bigfile tablespaces on platforms that do not support large file sizes and can limit tablespace capacity. Refer to your operating system specific documentation for information about maximum supported file sizes.

To enable bigfile tablespaces:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. For Bigfile Tablespaces, select Yes.
  6. Click Apply Changes.

See Also:

Available Parameter Values in Oracle APEX API Reference to learn about the BIGFILE_TABLESPACES_ENABLED parameter

3.5.3.5 Enabling Encrypted Tablespaces

Enable support for encrypted tablespaces.

If Encrypted Tablespaces is enabled, tablespaces provisioned with APEX are created as encrypted tablespaces using the Oracle database feature Transparent Data Encryption (TDE). TDE encrypts sensitive data stored in data files. To prevent unauthorized decryption, TDE stores the encryption keys in a security module external to the database.

To be able to exploit this feature in APEX, an encryption wallet must be created and with a master encryption key set. Additionally, the encryption wallet must be open before provisioning a new APEX workspace.

To enable Encrypted Tablespaces:

  1. Sign in to Oracle APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. For Encrypted Tablespaces, select Yes.
  6. Click Apply Changes.

See Also:

Available Parameter Values in Oracle APEX API Reference to learn about the ENCRYPTED_TABLESPACES_ENABLED parameter

3.5.3.6 Enabling Automatic Approval of Storage Requests

Automatically enable the approval of storage requests up to the selected size.

To use this option, the workspace Provisioning Method must be set to Automatic. If the workspace Provisioning Method is set to Manual or Request then storage requests cannot be automatically approved.

To automatically enable the approve storage requests:

  1. Sign in to Oracle APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. For Automatically Approve Requests, select a value.
  6. Click Apply Changes.

3.5.3.7 Deleting Uploaded Files

Specify the number of days after which APEX automatically deletes uploaded files. 

Use Delete Uploaded Files After (days) to specify the number of days after which APEX automatically deletes uploaded files. Note this automatic deletion process applies to all workspaces in an APEX instance. The types of files that are deleted include:

  • Application Export
  • CSS Export
  • Images Export
  • Page Export
  • Plug-in
  • Script Export
  • Spreadsheet / Text Data Import
  • Static Files Export
  • Themes
  • User Interface Defaults
  • Workspace Export
  • XML Data Import

To configure when export and import files are deleted:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. In Delete Uploaded Files After (days), enter the number of days after which APEX deletes uploaded files.

    Enter a positive, whole number. If this setting is null, then no files are automatically deleted.

  6. Click Apply Changes.

Tip:

To view a summary of deleted files, see the Automatic File Delete Log. See Monitoring Activity Across an Instance