Limitations in APEX Services in Autonomous Database in OCI(Oracle Cloud Infrastructure)
by Himansu Behera · Published · Updated
The APEX Service offers a cost-effective solution for production use for customers leveraging the APEX low-code platform to manage their organizations. However, there are certain limitations when using this service in Oracle Cloud Infrastructure (OCI).
No Oracle Database Client Support: Inbound Oracle Net Services (SQL*Net) connections are not supported.
No Database Client Connection Storage: Storing SQL*Net database client connections in the Connections service is not available.
No Customer-Managed ORDS Deployment: Deployment of customer-managed Oracle REST Data Services (ORDS) is not supported.
Cloning Restrictions: Full and metadata instance (database) cloning is supported, but refreshable clones are not available.
No Oracle Machine Learning (OML) Zeppelin Notebook: The OML Zeppelin notebook is not included.
No Oracle DataSafe Endpoint Registration: Registering as an Oracle DataSafe endpoint is not supported. If upgrading from Always Free Oracle Autonomous Transaction Processing to APEX Service, and the instance was previously registered as a DataSafe endpoint, de-registration is required during the upgrade process.
No Autonomous Data Guard Standbys: Setting up Autonomous Data Guard standbys is not supported.
Restricted REST-SQL Endpoint Access: Direct access to the pre-configured REST-SQL endpoint (with URLs ending in /sql) is not permitted.
No Graph Studio: Graph Studio functionality is not included.
No Read-Only Mode: The database cannot be set to read-only mode.
No MongoDB-Compatible APIs: Support for MongoDB-compatible APIs is not available.
No Data Transforms in Data Studio: Data Transforms functionality under Data Studio is not supported.