Scheduled Requests Running for END_DATED Users 100% CPU and Giving ORA-01002
Last updated on OCTOBER 20, 2016
Applies to:Oracle Concurrent Processing - Version 126.96.36.199 to 188.8.131.52 [Release 11.5]
Information in this document applies to any platform.
***Checked for relevance on 05-Mar-2013***
When a user or responsibility is end-dated, if there are any schedule requests against the user or responsibility which has been end-dated, the scheduled request still runs, which causes 100% CPU.
Log files shows
Cause: UPDATE_STATUS failed due to ORA-01002: fetch out of sequence.
On the application :
The SQL statement being executed at the time of the error was:
update fnd_concurrent_requests set phase_code = :phase ,status_code = :status, completion_text = :text where request_id = :reqid
and was executed from the file &ERRFILE.
APP-FND-01564: ORACLE error 1002 in UPDATE_STATUS
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms