7 Notes

This section provides additional resources when implementing RDS.

APEX

For more information around building performant APEX applications, refer to the Managing Application Performance section of the APEX App Builder User's Guide.

For full details on developing APEX applications, refer to the APEX documentation.

Visual Builder Studio

For full details on developing Visual Builder applications, refer to the Visual Builder Studio documentation.

APEX and Autonomous Databases

Because RDS is built using Oracle Autonomous Data Warehouse (ADW), there are limitations with functionality provided by Oracle Application Express. These limitations are documented at https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/apex-restrictions.html

Known Limitations and Issues

Limits on Service Initiated Queries and PL/SQL Blocks

  1. Service initiated queries and PL/SQL blocks (i.e., the service source) must complete in less than 300 seconds. This limitation is standard timeout and not configurable. Queries and blocks of longer durations must be run asynchronously and report results using other approaches (i.e., an output table populated by one service and queried by another, output to object storage, and so on).

  2. Service source is limited to 4000 characters. Character count for GET oriented queries can be reduced using views without sacrificing the automatic to JSON translation.

Importing of Services

The importing of services from the APEX UI does not work as expected. If the service does not exist, the import fails with a "no data found". Service exporting, however, does work and the exported services are just SQL scripts. These scripts can be run in the APEX SQL Workshop > SQL Scripts tool. Running the scripts will create the services.

Note:

Exported scripts include schema names. If the workspace in which the script will be run is not in the same schema as that from which the service was exported, the SQL script will need to be edited to change the source schema to the target schema.