Oracle_Apps: How To Kill runaway processes After Terminating Concurrent Request

Share via:

How To Kill runaway processes After Terminating Concurrent Request

 

 

Every concurrent Request uses some resources for running.

 

If we decided and terminate the conc request which is taking long time and not progress any more further.
after terminate it from front end, some times the resources may not be released soon. these processes are called runway process which will be create blocking other sessions.
so we need to manually kill the processes at DB and OS level.

Once terminate the concurrent request from the front end.

Then
SQL>select request_id,oracle_process_id,os_process_id from fnd_concurrent_requests where request_id=’&Req_Id’;
SQL>select p.spid , s.sid , s.serial# from v$session s , v$process p where s.paddr = p.addr and s.process = &os_process_id ;

 

Kill session id in Database

SQL> alter system kill session ‘session-id,session-serial’

 

kill pid at OS level
$ kill -9 <server pid>
Note: If you have any questions regarding above topic please comment below or contact me (jnamashivaya@gmail.com)

Share via:
Note: Please test scripts in Non Prod before trying in Production.
1 Star2 Stars3 Stars4 Stars5 Stars (27 votes, average: 5.00 out of 5)
Loading...

8 thoughts on “Oracle_Apps: How To Kill runaway processes After Terminating Concurrent Request

  1. I am not sure where you are getting your info, but good topic.
    I needs to spend some time learning more or understanding more.
    Thanks for excellent information I was looking
    for this information for my mission.

Add Comment