1. Getting Started with Oracle APEX Application Development
  2. Restrictions and Limitations for Oracle APEX

A Restrictions and Limitations for Oracle APEX

This section lists restrictions and limitations of Oracle APEX when running in the Oracle Autonomous Database Serverless configured for all workload types, including Oracle APEX Application Development (APEX Service).

Oracle APEX Limitations on Autonomous Database

This section summarizes restrictions and limitations of Oracle APEX included in Oracle Autonomous Database, including for the APEX Service.

Tip:

This section does not apply to co-managed databases (for example, OCI Base Database Service) and Oracle Autonomous Database on Dedicated Exadata Infrastructure.

In a fully managed environment (such as Oracle Autonomous Database Serverless), certain limitations are required to protect the security and performance of your Oracle APEX environment.

  • Administration Services - The following Oracle APEX Administration Services configuration options are disabled, or have been predefined by Oracle and cannot be altered.

    • Manage Instance, Feature Configuration:

      • Monitoring - Web Service Activity Logging, Enable Application Tracing

    • Manage Instance, Security, Security Settings:

      • Security - Unhandled Errors

      • Authentication Control:

        • HTTP Protocol - Require Outbound HTTPS

        • General - Single Sign-On Logout URL

    • Manage Instance, Manage Logs and Files:

      • SQL Workshop Log

      • Page View Activity Log

      • Developer Activity Log

      • External Click Counting Log

      • Login Access Log

      • Web Service Activity Log

      • REST Synchronization Log

      • Automation Log

    • Manage Instance, Instance Settings - Storage - All tablespace settings

    • Manage Instance, Workspace Purge Settings

    • Manage Workspaces, Existing Workspaces, Edit Workspace Information:

      • Login Control

      • Session Timeout

      • Workspace Isolation

  • Only the following APEX_INSTANCE_ADMIN procedures and functions are supported:

    • ADD_AUTHORIZED_URL
    • ADD_SCHEMA
    • ADD_WORKSPACE
    • CREATE_CLOUD_CREDENTIAL
    • CREATE_OR_UPDATE_ADMIN_USER
    • DISABLE_WORKSPACE
    • ENABLE_WORKSPACE
    • FREE_WORKSPACE_APP_IDS
    • GET_AUTHORIZED_URLS
    • GET_PARAMETER
    • GET_SCHEMAS
    • GRANT_EXTENSION_WORKSPACE
    • REMOVE_APPLICATION
    • REMOVE_AUTHORIZED_URL
    • REMOVE_SAVED_REPORTS
    • REMOVE_SAVED_REPORT
    • REMOVE_SCHEMA
    • REMOVE_SUBSCRIPTION
    • REMOVE_WORKSPACE
    • RESERVE_WORKSPACE_APP_IDS
    • REVOKE_EXTENSION_WORKSPACE
    • SET_LOG_SWITCH_INTERVAL
    • SET_PARAMETER
    • UNLOCK_USER
    • VALIDATE_EMAIL_CONFIG

    See APEX_INSTANCE_ADMIN in Oracle APEX API Reference.

  • The following application authentication schemes are supported with limitations:

  • Disabled options in SQL Workshop:

    The ability to create and manage database links in Object Browser is disabled. To create a database link, use the DBMS_CLOUD_ADMIN.CREATE_DATABASE_LINK PL/SQL API.

    See Use Database Links Autonomous Database in Using Oracle Autonomous Database Serverless.

  • Runtime environment:

    Oracle APEX is only available as a Full Development environment. Converting into a Runtime environment, which minimizes the installed software footprint and removes UI components such as App Builder and Administration Services, is not supported.

    See About the Differences Between Runtime and Full Development Environments in Oracle APEX App Builder User’s Guide to learn more.

Parent topic: Restrictions and Limitations for Oracle APEX

Autonomous Database Limitations in APEX Service

This section summarizes key restrictions and limitations of Autonomous Database in APEX Service.

APEX Service includes an optimized version of Oracle Autonomous Transaction Processing.

  • Restrictions of the Autonomous Database included with APEX Service:

    • No support for Oracle Database clients. Inbound Oracle Net Services (SQL*Net) connectivity is not available.

    • No ability to store database client connections (SQL*Net) in Connections service.

    • Deployment of the customer managed Oracle REST Data Services is not supported.

    • Full and metadata instance (database) cloning is supported, but refreshable clones are not.

    • Oracle Machine Learning (OML) Zeppelin notebook not included.

    • No support for registering as an Oracle DataSafe endpoint. If you upgrade from Always Free Oracle Autonomous Transaction Processing to APEX Service, and the Oracle Autonomous Transaction Processing instance was registered as a DataSafe endpoint previously, then the user is required to de-register as part of the upgrade process.

    • No ability to set up Autonomous Data Guard standbys.

    • Directly accessing the pre-configured REST-SQL endpoint (with URL ending in /sql) is prohibited.

    • Graph Studio not included.

    • No support for putting the database in read-only mode.

    • No support for MongoDB compatible APIs.

    • No support for Data Transforms under Data Studio.

  • Service packaging and licensing capabilities:

    • No BYOL license type

    • No Dedicated Infrastructure version

    • Not included in Oracle Cloud@Customer offerings

To access the capabilities described in the previous list, upgrade APEX Service to Oracle Autonomous Transaction Processing.

Parent topic: Restrictions and Limitations for Oracle APEX