Quite interesting problem was reported by our developers.
After 15 minutes of execution of long running server side procedure called from Apex(Oracle Application Experss) this call ends with:
ORA-01013: user requested cancel of current operation
According to 18604.1 ORA 1013 user requested cancel of current operation, we have next explanation:
Cause: The user interrupted an Oracle operation by entering CTRL-C, Control-C, or another canceling operation.
This forces the current operation to end.
This is an informational message only.
Action: Continue with the next operation.
but it’s absolutely clear that nobody has requested this cancellation (BTW – this fact has been additionally checked ;)) and what it more important – how can we “Continue with the next operation”, if previous didn’t completed successfully and it’s required for next operation ?
After some digging into the possible causes of ORA-01013(most of them will be discussed in next post) the issue was fixed and for those who has the same issue, please check for fix that helped us:
go to Application Express Listener Admin console, URL is something like this
Connection -> Database Connection -> JDBC Settings: Abandoned Connection Timeout:
change the value 900 seconds to something more appropriate, like 3600, as we did.
I don’t recommend to set “unlimited” value, because you will lose the possibility to control this feature.
- there are more reasons for ORA-01013 – they will be discussed in next post.
- if You have some suspected facts, like “15 minutes before ORA-01013″, and these facts are consistent, then it much more easier to troubleshoot problem than if you don’t have consistent facts