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.

  • 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 Transaction Processing.