My Oracle Support Banner

Scheduled Requests Still Running for END_DATED Users Consuming 100% CPU and Giving Error ORA-01002 (Doc ID 1097550.1)

Last updated on DECEMBER 23, 2023

Applies to:

Oracle Concurrent Processing - Version to [Release 11.5]
Information in this document applies to any platform.
11G Database version.
Library version 115.43


This document has been consolidated into <Note 1080047.1>.


When a user or responsibility is end-dated, if there are any scheduled requests against the user or responsibility which has been end-dated, the scheduled request will still run, which causes 100% CPU.

You will see the below errors :

In the internal manager log file:
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


Upgraded to 11G Database.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.