Thursday 15 December 2016

Oracle E-Business Suite Concurrent Request That Shows Running or Hanging, but has Completed

SOLUTION:

1. Stop the concurrent managers only from the primary node. It should stop the concurrent manager
on the secondary node.

a. Run the Concurrent Manager Recovery within Oracle Applications Manager.

Navigate:

Oracle Applications Manager > Concurrent Managers OR Concurrent Requests > Site Map > Diagnostics and Repair > Concurrent Manager Recovery

See Concurrent Manager Recovery Troubleshooting Wizard (Document 134007.1)

b. Restart the concurrent managers on the primary node.


NOTE: If the above does not clear it up, then proceed to step 2.  ATTENTION: Manual updates to Application tables from sqlplus are not supported.

2. Backup the fnd_concurrent_requests table.

3. For the request_id that is running/hanging where 'request_id' is to be replaced with the actual concurrent request id:

SQL>update FND_CONCURRENT_REQUESTS
set STATUS_CODE='D', PHASE_CODE='C'
where request_id='request_id';


4. After commiting the update above, verify the request is now resolved.



Reference: How To Clear Up a Request That Shows Running, but has Completed (Doc ID 1684368.1)

No comments:

Post a Comment