Oracle Utilities cloud services have some time and data size limits.

In the online application, pages have a default timeout limit of two minutes. This is to prevent an endlessly running transaction, and is often an indication that there is an underlying performance issue (for instance a slow-running SQL) or inherent limit on how much work can be accomplished in the time period (such as attempting to generate a bill online for an account with hundreds of service agreements, which should be done in batch).

The table below lists a number of pre-set limits in Analytics Publisher for reporting:

The table below lists a number of pre-set limits related to use of Oracle REST Data Services (ORDS), including Database Actions (formerly known as SQL Developer Web):

The table below lists a number of pre-set limits related to use of web services:

* The timeout limit for web service calls can be extended up to 5 minutes if a Service Request is submitted to the Cloud Operations team.

Note: Customers and implementers should review any HTTP request that is timing out as this would suggest the underlying service has issues and consider asynchronous methods vs synchronous where appropriate.

The table below lists SQL timeouts for batch processing for different types of thread pool workers.

* The SQL timeout limit for the NOCACHE TPW can be extended upon request by submitting a Service Request to the Cloud Operations team. Custom batch processes must be tested with production data to ensure they adhere to the SQL timeouts listed above. For example, the SQL timeout for a custom batch process run using the DEFAULT TPW must not exceed 15 minutes and 30 seconds. Refer to Reviewing and Tuning SQL Statements for guidelines.