PO Output For Communication Concurrent Program in Running status with INACTIVE session in gv$session
(Doc ID 2559858.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.
PO Output for Communication requests ( about 1,2% ) will stay in Running status but there is no db activity. The session associated with the request_id is INACTIVE in gv$session
Customer has to cancel those requests after 2 hours, and user must resubmit them manually. On resubmission, the requests complete under 1 second.
Same problem has been observed with AP’s Payment Format Instructions concurrent program, though less frequent.
The resulting inactive/pending concurrent programs would hold up the standard managers queue, and would cause others concurrent programs to stuck in waiting.
Run following query to find the concurrent program status and db session status:
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