A Restrictions and Limitations for Oracle APEX
This section lists restrictions and limitations of Oracle APEX when running in the Oracle Autonomous AI Database configured for all workload types, including Oracle APEX Application Development (APEX Service).
- Oracle APEX Limitations on Oracle Autonomous AI Database
This section summarizes restrictions and limitations of Oracle APEX included in Oracle Autonomous AI Database and APEX Service. - Autonomous AI Database Limitations in APEX Service
This section summarizes key restrictions and limitations of Autonomous AI Database in APEX Service.
Oracle APEX Limitations on Oracle Autonomous AI Database
This section summarizes restrictions and limitations of Oracle APEX included in Oracle Autonomous AI Database and APEX Service.
Tip:
This section does not apply to co-managed databases (for example, OCI Base Database Service) and Oracle Autonomous AI Database on Dedicated Exadata Infrastructure.In a fully managed environment (such as Oracle Autonomous AI Database), 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_ADMINprocedures and functions are supported:ADD_AUTHORIZED_URLADD_SCHEMAADD_WORKSPACECREATE_CLOUD_CREDENTIALCREATE_OR_UPDATE_ADMIN_USERDISABLE_WORKSPACEENABLE_WORKSPACEFREE_WORKSPACE_APP_IDSGET_AUTHORIZED_URLSGET_PARAMETERGET_SCHEMASGRANT_EXTENSION_WORKSPACEREMOVE_APPLICATIONREMOVE_AUTHORIZED_URLREMOVE_SAVED_REPORTSREMOVE_SAVED_REPORTREMOVE_SCHEMAREMOVE_SUBSCRIPTIONREMOVE_WORKSPACERESERVE_WORKSPACE_APP_IDSREVOKE_EXTENSION_WORKSPACESET_LOG_SWITCH_INTERVALSET_PARAMETERUNLOCK_USERVALIDATE_EMAIL_CONFIG
See APEX_INSTANCE_ADMIN in Oracle APEX API Reference.
-
The following application authentication schemes are supported with limitations:
-
LDAP Directory, including
APEX_LDAPAPI: With the same restrictions that apply to theDBMS_LDAPpackage.See PL/SQL Packages Notes for Autonomous AI Database in Using Oracle Autonomous AI Database Serverless.
-
SAML Sign-In: Only when using a customer managed ORDS.
See About Customer Managed Oracle REST Data Services on Autonomous AI Database in Using Oracle Autonomous AI Database Serverless.
-
-
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_LINKPL/SQL API.See Use Database Links Autonomous AI Database in Using Oracle Autonomous AI 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 AI Database Limitations in APEX Service
This section summarizes key restrictions and limitations of Autonomous AI Database in APEX Service.
APEX Service includes an optimized version of Oracle Autonomous AI Transaction Processing.
-
Restrictions of the 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 AI Transaction Processing to APEX Service, and the Oracle Autonomous AI Transaction Processing instance was registered as a DataSafe endpoint previously, then the user is required to de-register as part of the upgrade process.
-
Directly accessing the pre-configured REST-SQL endpoint (with URL ending in
/sql) is prohibited. -
Fusion Application integration using the Database Tools service is not supported. You can manually complete the equivalent integration by separately configuring the Fusion identity domain and the APEX Service instance.
-
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 AI Transaction Processing.
Parent topic: Restrictions and Limitations for Oracle APEX