APEX Application Fails with "ORA-00040 Active Timeout Reached. Call Aborted" on the Database Cloud Schema Service
(Doc ID 1606668.1)
Last updated on OCTOBER 17, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Cloud Schema Service - S20 - Version N/A and later
Oracle Database Cloud Schema Service - S50 - Version N/A and later
Information in this document applies to any platform.
Symptoms
When uploading data through an APEX application on the Database Cloud Schema Service, the application fails with the following error:
1 error has occurred
ORA-00040: active time limit has exceeded.
This error does not occur when using a on a smaller .csv file that has a smaller amount of data, but fails with a larger .csv file that contains a larger amount of data.
This failure occurs when running through the customer application, but not when running through the standard data loading in SQL Workshop.
A similar error can also be at install time when importing large applications. The error seen is:
ORA-20001: WWV_FLOW_API.ERR_REPORT_LAYOUT_CREATE ORA-00040: active time limit exceeded - call aborted
Return to application.
In some cases an error similar to the following may be seen when using data load in an application:
ORA-10260: limit size (1048576) of the PGA heap set by event 10261 exceeded
Changes
Migrating an APEX application from on-premise to the Oracle Database Cloud Service (DBCS) and Application Express (APEX).
OR
Loading data into the Schema Service using an APEX Data Loading application.
OR
Running an application (APEX REST or APEX application) that is processing a large amount of data.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |